Network graph & geomap with metrics#
π‘ Physical Topology#
- Device-to-device links aggregated into fiber optic lines (FOLs)
- Exact routes with segment comments
π§ Logical Topology#
- Interfaces of connected devices with gradient load visualization
- Device statuses
- Cluster icons with aggregated status info by groups of devices
- Layers for any task: markers, lines, arcs, polygons
- Node graph with auto-layout on a non-geo (abstract) basemap
ποΈ Grafana Field Config#
Thresholdsβ value ranges with associated colors to visually indicate statusMappingβ rename displayed valuesUnitsβ measurement unit conversionOverridesβ custom settings for specific metricsDataLinksβ links to external dashboards or graphs
Style colors, marker sizes, line width and icons dynamically with value-based rules that can apply globally or be overridden per field or device group
π Required Data Format#

Each source dataframe record should contain:
coordinatesof the device or node. Non-geo (abstract) node graph layout is autogenerated.parent idor a full path with intermediate node IDs or coordinatesedge idis optional. Used to support parallel connectionsstatusmetrictransmitandreceivemetrics for link load
π οΈ Data Preparation#
Use Grafanaβs built-in transformations to prepare and merge data from:
- Postgres
- Prometheus
- Zabbix
- Any datasource
Tutorial: Observing Zabbix events on a Geospatial Map Prometheus datalinks example
πΉοΈ Demo Playground#
Explore interactive Grafana panels with open configuration
π² Plugin Tiers#
Compare available features across plans
πΈ Screenshots#
