Integration & Dashboards¶
The exporter exposes metrics on http://<host>:9099/metrics. Scrape this
endpoint with Prometheus or any other OpenMetrics compatible collector.
Prometheus example¶
Grafana Alloy example¶
discovery.relabel "meraki" {
targets = [{"__address__" = "meraki-dashboard-exporter:9099"}]
}
prometheus.scrape "meraki" {
targets = discovery.relabel.meraki.output
forward_to = [prometheus.remote_write.default.receiver]
scrape_interval = "30s"
scrape_timeout = "25s"
}
prometheus.remote_write "default" {
endpoint { url = "http://prometheus:9090/api/v1/write" }
}
Prometheus and Grafana configuration examples are available in the docker-compose.yml. The compose file ships only the exporter container; integrate the scrape job into your existing Prometheus/Grafana stack.
Scrape interval
Align your Prometheus scrape interval with the exporter’s update tiers to avoid unnecessary load (see Metrics Overview).
Dashboards¶
Pre-built Grafana dashboards live in the dashboards directory. Import them to get instant visibility into your organisation. Bundled dashboards include:
organization-overview.json– org-wide rollupnetwork-overview.json– network inventory and statusnetwork-health-performance.json– network health, RF, and performancemr-access-points.json– MR (wireless) APsms-switches.json– MS switchesmx-security-appliances.json– MX appliances and uplinksmt-sensors.json– MT environmental sensorsmv-security-cameras.json– MV camerasmg-cellular-gateways.json– MG cellular gatewaysclient-overview.json– client trackingassurance-alerts.json– alerts and assuranceapi-usage-licensing.json– API usage and licensingexporter-monitoring.json– self-monitoring of the exporter
Alerting¶
Use PromQL rules with metrics such as meraki_device_up or meraki_exporter_collection_errors_total to trigger alerts.
For more metrics see the Metrics Reference. Configuration options are documented in the Configuration guide. OpenTelemetry tracing is documented in OpenTelemetry.