ruckus-unleashed-exporter

Prometheus exporter for Ruckus Unleashed access points.

Scrapes the Unleashed AJAX API via aioruckus and exposes metrics for Prometheus.

Quick Start

docker run -d \
  --name ruckus-exporter \
  --restart unless-stopped \
  -p 9785:9785 \
  -e RUCKUS_HOST=192.168.1.5 \
  -e RUCKUS_USER=admin \
  -e RUCKUS_PASS=your_password \
  ccmpbll/ruckus-unleashed-exporter

Environment Variables

Prometheus Scrape Config

Each scrape triggers a live API call to the Unleashed controller. Set scrape_timeout high enough to cover the round trip — 30s is a safe default. scrape_interval controls how often metrics are collected.

Add to your prometheus.yml:

scrape_configs:
  - job_name: ruckus-unleashed
    scrape_interval: 60s
    scrape_timeout: 30s
    static_configs:
      - targets:
          - ruckus-exporter:9785

Endpoints

Metrics

System

Per-AP

Per-Radio

Per-Client

Note on per-client session metrics: These are Gauges, not Counters. The Unleashed API reports cumulative totals since the client's current association — they reset to zero each time a client disconnects and reconnects. rate() will work correctly during a stable session, but will produce a transient dip to zero at reconnect events. For most home and small-office deployments where clients reconnect infrequently, this is negligible in practice.

Per-VAP (SSID)

Grafana Dashboard

A pre-built dashboard is available at dashboards/ruckus-unleashed.json. Import it via Dashboards → Import in Grafana and select your Prometheus datasource when prompted.

Overview Row

Radio Performance Row

Radio Health Row

VAP / SSID Row

Connected Clients Row

Client Traffic Row

Client Detail Row

Known Potential Issues

• Per-client session metrics reset on reconnect: ruckus_client_session_rx_bytes, ruckus_client_session_tx_bytes, and related session metrics count from the client's most recent association event — not from AP boot. A client disconnect/reconnect resets them to zero. These are exposed as Gauges rather than Counters for this reason. rate() works correctly during a stable session but will show a brief dip to zero at reconnect events.

• ruckus_radio_tx_power reports unexpected values in Auto mode: When a radio is set to Auto TX power, the AP may report the current dynamically-chosen power level (e.g. 25 on 2.4GHz) rather than 0. This causes the metric to show a negative value instead of 0. Radios set to Full or a manual reduction step behave as expected.

• ruckus_radio_phy_errors_total is not a true monotonic counter: Despite the _total suffix, PHY error values appear to reflect a rolling measurement window rather than a cumulative count since boot. Values may decrease between scrapes. This is a limitation of what the Unleashed API exposes.

• ruckus_vap_tx_drop_packets_total mirrors ruckus_vap_tx_errors_total: The underlying API fields tx-data-drop-pkts and tx-errors return identical values and increment together. They appear to be the same counter exposed under two names. Both metrics are retained for completeness but should be treated as equivalent.

Tested On

• Ruckus R850, Unleashed 200.18.7.101.244