This guide walks you through setting up PowerScale Data Insights from scratch: creating a OneFS user, configuring the collectors, setting up InfluxDB and Grafana, and seeing your first dashboards.
- A Dell PowerScale cluster running OneFS 9.x or later
- Network access from the machine running the collectors to the cluster's PAPI port (TCP 8080 by default)
- InfluxDB v1.8+ or v2.x
- Grafana 10+
Create a dedicated user on your OneFS cluster with the minimum required privileges. See OneFS Setup for detailed instructions.
At minimum, the user needs:
| Privilege | Required by | Purpose |
|---|---|---|
ISI_PRIV_STATISTICS |
gostats | Read cluster statistics |
ISI_PRIV_PERFORMANCE |
goppstats | Read Partitioned Performance data |
ISI_PRIV_NFS (read-only) |
goppstats (optional) | Resolve NFS export IDs to paths |
# Create the database
influx -execute "CREATE DATABASE isi_data_insights"Create a bucket named isi_data_insights and generate an API token with
write access. InfluxQL compatibility must be enabled (it is by default in
InfluxDB v2).
This brings up InfluxDB, Grafana, and both collectors in one step.
cd docker/
cp gostats.example.toml gostats.toml
cp goppstats.example.toml goppstats.tomlEdit both config files — at minimum, update the [[cluster]] section:
[[cluster]]
hostname = "your-cluster.example.com"
username = "statsuser"
password = "your-password"
verify-ssl = falseThen start the stack:
docker compose up -dSkip to Step 5 — InfluxDB and Grafana are pre-configured.
Requires Go 1.25+.
git clone https://github.com/Isilon/powerscale_data_insights.git
cd powerscale_data_insights
make buildThis produces bin/gostats, bin/goppstats, and bin/dashgen.
Download the latest release from the GitHub Releases page for your platform.
Copy the example configs and edit them:
cp configs/gostats.example.toml idic.toml
cp configs/goppstats.example.toml goppstats.tomlIn each file, update:
[[cluster]]— your cluster hostname, username, and password[influxdb]— your InfluxDB host (defaultlocalhost:8086)
See Configuration Reference for all options.
Start the collectors:
# Collect cluster statistics
./bin/gostats -config-file idic.toml
# Collect Partitioned Performance data (in a separate terminal)
./bin/goppstats -config-file goppstats.tomlYou should see log output indicating successful connection to each cluster and stats being written to InfluxDB.
Open http://localhost:3000 and log in with admin / admin. The dashboards are already provisioned under the PowerScale folder.
-
Open Grafana and add an InfluxDB datasource:
- URL:
http://localhost:8086 - Database:
isi_data_insights
- URL:
-
Import the dashboards from
dashboards/influxdb/:- Go to Dashboards > Import
- Upload each JSON file or paste its contents
- Select your InfluxDB datasource when prompted
The four core dashboards are:
| Dashboard | Description |
|---|---|
| PowerScale - Cluster List | Multi-cluster overview with health, CPU, capacity, protocol stats |
| PowerScale - Cluster Detail | Single cluster deep dive with CPU, network, disk, cache, protocol panels |
| PowerScale - Cluster Capacity | Storage utilization across clusters |
| PowerScale - Protocol Overview | Cluster-level protocol performance for a single cluster |
If you have Partitioned Performance datasets configured on your cluster,
use dashgen to generate dashboards for them:
# List datasets (check the PAPI directly or use the OneFS UI)
# Then generate a dashboard for a specific dataset ID:
./bin/dashgen \
-host your-cluster.example.com \
-user statsuser \
-password your-password \
-dataset 1 \
-out pp-dataset-1.jsonImport the generated JSON file into Grafana. See Dashboards for more details on dashgen usage.
- Configuration Reference — all config options
- Dashboards — dashboard descriptions and dashgen guide
- Deployment — systemd, Docker, Kubernetes
- Migrating from v1 — if upgrading from the Python connector