Network geomap with metrics & alert states#
π‘ 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 row in the source dataframe should include:
coordinates
of the device or node. Non-geo (abstract) node graph layout is autogenerated.parent id
or a full path with intermediate node IDs or coordinatesedge id
is optional. Used to support parallel connectionsstatus
metrictransmit
andreceive
metrics 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#