Grafana Network Monitoring Dashboard Creation

Setup grafana and, victoriametrics on own test envirnoment deliverable is JSON export from the dashboard! One shared Grafana instance serves multiple clients. Data source is **VictoriaMetrics** (use Grafana's built-in **Prometheus** datasource type — VictoriaMetrics is API-compatible). Metrics are collected by **Telegraf** (SNMP input for switch/network devices, plus host metrics for the collector appliance itself). ## Required panels 1. **Port status (up/down) per switch port** - Panel type: **State timeline** - One row per port. - Color by value mapping using status colors only: up = green ("good"), down = red ("critical"). Do not use arbitrary/categorical colors here. - Legend/label must show the port name — never rely on color alone. 2. **Interface bandwidth (in/out)** - Panel type: **Time series** (line) - Two series: `in` and `out`, same unit (bits/sec or bytes/sec), **one shared** **y-axis**. - Fixed color order: `in` = first categorical color, `out` = second — consistent across all instances of this panel. - Do **not** combine with CPU/memory on a second (dual) y-axis, even if it seems convenient — that goes in a separate panel (see below). 3. **CPU utilization (collector host)** - Current value: **Stat** or **Gauge** panel, scaled 0–100%. - Trend: separate **Time series** (line) panel, own axis, not combined with memory or bandwidth panels. 4. **Memory utilization (collector host)** - Current value: **Stat** or **Gauge** panel, scaled 0–100%. - Trend: separate **Time series** (line) panel, own axis — same rule as CPU, kept in its own panel. ## Hard rules (please follow exactly) - **One y-axis per panel, always.** Never a dual-axis chart. Two measures of different scale = two separate panels, not one panel with two axes. - **Status colors (up/down) are reserved** — green/red for state, never reused as a generic series color elsewhere on the dashboard. - Every multi-series panel needs a visible legend; single-series panels don't need one (the panel title names it). - Hover tooltips must be enabled (Grafana's default on Time series / State timeline) — don't disable them. ## Multi-tenancy — important This dashboard must work for **all clients from one single dashboard** **definition** — not a separate dashboard per client. - Add a Grafana **dashboard/template variable** (e.g. `client\_id`) that filters every panel's query by that label. - All queries must reference `$client\_id` (or the chosen variable name) consistently — no hardcoded client names/IDs anywhere in any query. ## Deliverable - Exported Grafana dashboard **JSON** (importable via Grafana's dashboard import feature). - Short note listing: the expected datasource variable/UID placeholder, the template variable name used, and the exact metric/field names each panel queries (so we can confirm they match our Telegraf output before wiring it up for real).

Project ID: 40559582