-
Notifications
You must be signed in to change notification settings - Fork 28
Exposing IBM Storage Scale (GPFS) Metrics to IBM Cloud Monitoring Using Sysdig Agent
IBM Storage Scale exposes cluster performance data through the internal ZiMon performance monitoring subsystem.
The IBM Storage Scale Bridge for Grafana bridges this gap. It reads raw ZiMon metric data and re-exposes it in Prometheus exposition format on port 9250. The Sysdig Agent (dragent - the agent process managing metric collection and forwarding to IBM Cloud Monitoring) - already deployed - scrapes that endpoint and forwards every GPFS metric to your IBM Cloud Monitoring instance.
This gives you a single-pane-of-glass view for GPFS disk I/O, CPU, NSD, filesystem throughput and cluster health - with alerting and capacity planning - without needing a standalone Grafana or Prometheus server.
┌─────────────────────────────────────────────────────────────────┐
│ IBM Storage Scale Cluster │
│ │
│ ┌─────────────────────────────────────┐ │
│ │ Management Node │ │
│ │ │ │
│ │ ┌──────────────────────────────┐ │ │
│ │ │ ZiMon / pmcollector │ │ │
│ │ │ REST API :9980 (HTTPS) │ │ │
│ │ └──────────┬───────────────────┘ │ │
│ │ │ queries / JSON │ │
│ │ ▼ │ │
│ │ ┌──────────────────────────────┐ │ │
│ │ │ Grafana Bridge │ │ │
│ │ │ Prometheus exporter :9250 │ │ │
│ │ │ (HTTPS + Basic Auth + TLS) │ │ │
│ │ └──────────┬───────────────────┘ │ │
│ │ │ scrape /metrics │ │
│ │ ▼ │ │
│ │ ┌──────────────────────────────┐ │ │
│ │ │ Sysdig dragent │ │ │
│ │ │ (promscrape.yaml.d/) │ │ │
│ │ └──────────────────────────────┘ │ │
│ └─────────────────────────────────────┘ │
│ │
│ ┌──────────────────────┐ │
│ │ Worker Nodes (N) │ │
│ │ Sysdig dragent │ ← host metrics only (CPU, mem, net) │
│ └──────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
│ GPFS + host metrics (HTTPS :6443)
▼
┌─────────────────────────────────┐
│ IBM Cloud Monitoring │
│ Ingestion endpoint :6443 │
│ Dashboards · Alerts · Metrics │
└─────────────────────────────────┘
Runs on the pmcollector node only. Translates ZiMon data into Prometheus format. Also auto-generates a ready-to-use scrape config at GET /prometheus.yml covering all GPFS sensor groups (GPFSFilesystem, GPFSNSD, GPFSNetwork etc)
IBM Cloud Monitoring agent. Installed on every scale node. On the management node it is additionally configured with a custom prometheus scrape directory (/opt/draios/etc/promscrape.yaml.d/) to also forward GPFS metrics.
Instead of manually writing Prometheus scrape configs, the automation fetches the auto-generated prometheus.yml directly from the running bridge, extracts the scrape_configs block, and writes it to /opt/draios/etc/promscrape.yaml.d/scale_bridge.yaml The GPFSPDDisk job is stripped for non-ESS clusters.
Bridge is up and serving metrics:
curl -sk -u svc_osprey_scraper:<password> https://127.0.0.1:9250/metrics | head -30Sysdig scrape config was injected:
cat /opt/draios/etc/promscrape.yaml.d/scale_bridge.yamlAgent forwarding to IBM Cloud Monitoring:
systemctl status dragent
journalctl -u dragent --since "5 min ago" | grep -i "prometheus\|scrape\|gpfs"In IBM Cloud Monitoring: filter by metric namespace gpfs_* or tag cluster:ibm_storage_scale. Metrics appear within 60–90 seconds of agent startup.
[vpcuser@npr-scale27-strg-mgmt-850a-001 promscrape.yaml.d]$ cat /opt/draios/etc/dragent.yaml
customerid: "47e36686-c492-445a-8a4b-278620e90b89"
collector: "ingest.jp-tok.monitoring.cloud.ibm.com"
collector_port: 6443
tags: "cluster:ibm_storage_scale,nodeclass:managementnodegrp"
sysdig_capture_enabled: false
remotefs: true
prometheus:
enabled: true
yaml_dir: /opt/draios/etc/promscrape.yaml.d
first two values are endpoints of cloud monitoring instance


Visit the IBM Storage Scale Knowledge Center for getting more info about the latest product updates
-
- Setup classic Grafana
- Make usage of Grafana Provisioning feature
-
- Installing RedHat community-powered Grafana operator from OperatorHub
- Creating Grafana instance using the RedHat community-powered Grafana-operator
- Creating Grafana Datasorce instance from Custom Resource managed by the RedHat community powered Grafana operator
- Importing the predefined dashboard from the example dashboards collection
- Exploring Grafana WEB interface for CNSA project in a k8s OCP environment
- How to setup Grafana instance to monitor multiple IBM Storage Scale clusters running in a cloud or mixed environment
- API key authentication
- Configurable bridge settings
- CherryPy builtin HTTP server settings
- How to setup HTTPS(SSL) connection
- Start and stop grafana-bridge with systemd
- Configure PrometheusExporter for scraping linux sensor metrics
- Refresh IBM Storage Scale cluster configuration data cached by grafana bridge
- Accelerate the PrometheusExporter data retrieval time
- Optimize the performance of PrometheusExporter by using scrape_job params settings
- Grafana Dashboard Panel shows no metric values for a particular entity
- Missing Grafana-Operator on an OpenShift cluster
- Missing CherryPy packages
- What to do if your system is on Python < 3.8
- Grafana-bridge fails to start with Python3.8
- Grafana-bridge container time is different from a host time
- Grafana-bridge container does not return metrics for sensors restricted to a subset of nodes
- Verify that the grafana-bridge returns data as expected
- Grafana-bridge HTTP REST Api interface
- How to monitor performance of the IBM Storage Scale bridge for Grafana