Observability And Alerting
Last updated: 2026-06-21
This diagram shows how the monitoring stack collects data, displays dashboards,
and sends Discord notifications.
Metrics Flow
flowchart TB
subgraph Sources["Observed systems"]
Synology["Synology host\nNode exporter"]
Docker["Docker containers\ncAdvisor"]
Blackbox["HTTP/TCP/DNS probes\nBlackbox exporter"]
Tdarr["Tdarr DB/API exporter"]
Tautulli["Tautulli/Plex exporter"]
UniFi["UniFi Integration API exporter"]
PiHole["Pi-hole DNS probes\nPiHolePi4 + PiHole4B"]
SynologyLogs["Synology log exporter\nDSM/Btrfs/core/storage signals"]
Backups["Backup freshness metrics\nPi-hole/appdata/report checks"]
end
subgraph Observability["Synology Volume 5 observability stack"]
Homepage["Homepage portal\nservice + dashboard launchpad"]
Prometheus["Prometheus\nscrape + rules"]
Grafana["Grafana dashboards"]
Alertmanager["Alertmanager"]
DiscordBridge["Discord alert bridge"]
end
Discord["Discord #vhnic-alerts\nwarning alerts only"]
Synology --> Prometheus
Docker --> Prometheus
Blackbox --> Prometheus
Tdarr --> Prometheus
Tautulli --> Prometheus
UniFi --> Prometheus
PiHole --> Prometheus
SynologyLogs --> Prometheus
Backups --> Prometheus
Homepage --> Grafana
Prometheus --> Grafana
Prometheus --> Alertmanager
Alertmanager --> DiscordBridge --> Discord
Dashboard Coverage
flowchart LR
Grafana["Grafana"]
Service["VHNIC Service Health"]
SynDocker["VHNIC Synology and Docker Metrics"]
Pihole["VHNIC Pi-hole DNS Health"]
Unifi["VHNIC UniFi Network Health"]
Tdarr["VHNIC Tdarr Progress"]
Footprint["Container footprint review\nHomepage docs"]
Plex["VHNIC Plex Activity"]
Infra["VHNIC Infrastructure Overview"]
Alerts["VHNIC Alert Watch"]
Public["VHNIC Public Exposure"]
Storage["VHNIC Storage Integrity"]
Stack["VHNIC Observability Stack Health"]
BackupDash["VHNIC Backup and Optional Node Health"]
Homepage["Homepage\nVHNIC portal"]
Homepage --> Grafana
Grafana --> Service
Grafana --> SynDocker
Grafana --> Pihole
Grafana --> Unifi
Grafana --> Tdarr
Homepage --> Footprint
Grafana --> Plex
Grafana --> Infra
Grafana --> Alerts
Grafana --> Public
Grafana --> Storage
Grafana --> Stack
Grafana --> BackupDash
Alerting Rules Of Thumb
- Discord currently receives
severity="warning"alerts only. severity="info"alerts are visible in Grafana/Prometheus but muted from- Known historical Volume 1 Btrfs counters are treated as baseline context; new
- Disk busy alerts can be real during Tdarr/Plex/media workloads. Correlate
- Backup freshness and optional-node probes are monitoring signals, not repair
- The active monitoring compose project now runs from
- Tautulli exporter now reads
/volume3/docker/tautulli/config.ini, and Tdarr
Discord to avoid routine noise.
counter growth is what should trigger concern.
disk busy with active streams, Tdarr queues, and recent scans before changing
workloads.
actions. Investigate stale metrics before deleting or moving backup files.
/volume2/docker-v5/projects/observability-compose, with appdata under
/volume2/docker-v5/appdata/observability. Historical
/volume3/docker/observability data is rollback/reference only unless
explicitly restored.
exporter reads the Volume5-role Tdarr database under
/volume2/docker-v5/appdata/tdarr.