Grafana dashboards¶
The repository ships importable dashboards under utils/grafana/:
| Directory | Backend | Dashboards |
|---|---|---|
influx1_dashboards/ | InfluxDB v1 | System, call logs, router logs |
influx2_dashboards/ | InfluxDB v2 | System, call logs, router logs, home automation |
questdb_dashboards/ | QuestDB | System, call logs, router logs, home automation |
Import workflow¶
- Create a Grafana datasource for the selected backend.
- Import the JSON files from the matching directory.
- Map the dashboard datasource variable to the datasource where prompted:
DS_INFLUXDBfor InfluxDB exports orDS_QUESTDBfor QuestDB exports. - Set the measurement variable to the serial-derived name, for example
fritzbox_<sanitized-serial>. - Select a time range after the first successful collection cycle.
The InfluxDB dashboards use the datasource type influxdb; the QuestDB dashboards use the official QuestDB datasource. The JSON files are source artifacts: edit them in utils/grafana/, not in an exported copy stored by Grafana. The QuestDB dashboards are generated from the influx2_dashboards/ sources; after changing those, run python3 tools/build_questdb_dashboards.py from the repository root.
The QuestDB dashboards read the tables fritzbox_<serial>_metrics and fritzbox_<serial>_events (see QuestDB).
Dashboard coverage¶
- System: CPU, memory, uptime, temperatures, connection and traffic.
- Call logs: incoming and outgoing telephone entries.
- Router logs: FRITZ!Box log entries grouped by log type.
- Home automation: supported temperature, heating, battery, and device-state metrics.
If a dashboard is empty, verify the datasource, time range, measurement/table variable, and that the matching collector is supported by the FRITZ!Box model and firmware.