All Products
Search

This Product

    Container Service for Kubernetes:Enable FUSE client metrics for Fluid JindoRuntime

    Document Center

    Container Service for Kubernetes:Enable FUSE client metrics for Fluid JindoRuntime

    Last Updated:Jun 24, 2026

    Expose FUSE client metrics and view them on the Fluid JindoRuntime dashboard in ARMS.

    Fluid ships a JindoRuntime dashboard that collects monitoring metrics for each JindoCache distributed cache engine in your ACK cluster. It covers server-side cache engine metrics and Filesystem in Userspace (FUSE) client metrics. FUSE client metrics are disabled by default for performance and do not appear until you enable them.

    Enable FUSE client metrics collection and view them on the Fluid JindoRuntime dashboard. After you complete the three steps below, metrics appear in FUSE Metrics (via CSI) (MountPod mode) and FUSE Metrics (via Sidecar) (Sidecar mode).

    Prerequisites

    You need:

    Important

    Uninstall open-source Fluid before installing ack-fluid to avoid conflicts.

    Step 1: Integrate Fluid with ARMS

    1. Log on to the ARMS console.

    2. In the left-side navigation pane, choose Integration Center. In AI, click the Fluid card.

    3. Select your cluster in Select a Kubernetes cluster. Skip the remaining steps in this section if Fluid is already installed.

    4. In Configuration Information, set the following parameters and click OK.

      Parameter Description
      Name (Not required) Unique Fluid exporter name. Optional.
      metrics collection interval (seconds) Monitoring data collection interval.

    5. Verify the integration on the Integration Management page in the ARMS console.

      1. Log on to the ARMS console.

      2. In the left-side navigation pane, choose Integration Management. On the Integrated Addons tab, click the Fluid card.

      3. On the Environments tab, click View Details in the Actions column to check Fluid component status and alert rules in your cluster.

    Step 2: Configure metrics exposure and scraping policy

    When deploying JindoRuntime, set spec.fuse.metrics.enabled and spec.fuse.metrics.scrapeTarget to expose FUSE client metrics and define the scraping policy.

    Choose your scraping policy before writing the YAML. The scrapeTarget value determines which dashboard sections receive data:

    • Use MountPod for non-Serverless workloads in MountPod mount mode.

    • Use Sidecar for Serverless workloads in Sidecar mount mode.

    • Use All to scrape both mount modes.

    • Use None (default) to disable FUSE client metrics scraping.

    Warning

    Use caution when setting scrapeTarget to Sidecar or All in Serverless environments. In Sidecar mount mode, each pod starts a FUSE sidecar container. When concurrent pod count is high, scraping metrics from all FUSE sidecar containers can create significant overhead and place considerable pressure on your Managed Service for Prometheus instance.

    Example YAML with scrapeTarget: All:

    apiVersion: data.fluid.io/v1alpha1
kind: JindoRuntime
metadata:
  name: hadoop
spec:
  replicas: 2
  fuse:
    metrics:
      enabled: true
      scrapeTarget: All
  tieredstore:
    levels:
      - mediumtype: MEM
        path: /dev/shm
        volumeType: emptyDir
        quota: 2Gi
        high: "0.99"
        low: "0.95"

    Metrics-related parameters:

    Parameter Description Default value
    spec.fuse.metrics.enabled Whether to expose FUSE client metrics. When set to true without a port in spec.fuse.args (for example, -ometrics_port=8080), Fluid assigns an available port to the FUSE client and configures it for external metrics services. false
    spec.fuse.metrics.scrapeTarget Scraping policy for FUSE client metrics. Valid values: None, MountPod, Sidecar, All. See the decision guidance above. None
    Note

    See Use JindoFS to accelerate access to OSS for all JindoRuntime parameters.

    Step 3: View the Fluid JindoRuntime dashboard

    1. Log on to the ACK console. In the left-side navigation pane, choose Clusters.

    2. On the Clusters page, click your cluster name. In the left-side pane, choose Operations > Prometheus Monitoring.

    3. On the Prometheus Monitoring page, open the Others tab, then the Fluid JindoRuntime Dashboard tab. The dashboard shows FUSE client metrics in these sections based on your scrapeTarget setting:

      • FUSE Metrics (via CSI): Metrics from FUSE pod clients. Populated when scrapeTarget is MountPod or All.

      • FUSE Metrics (via Sidecar): Metrics from FUSE sidecar container clients. Populated when scrapeTarget is Sidecar or All.

    Next steps