N

homelab · case study

Home Lab Monitoring and Visualisation

Built end-to-end OS observability for the home lab, with the TICK stack collecting, Grafana visualising and Discord receiving alerts.

What shipped.

  • /01

    OS-level metrics (CPU, memory, disk I/O, network) collected by Telegraf into InfluxDB.

  • /02

    Grafana dashboards covering the whole fleet.

  • /03

    Kapacitor-driven alerts piped into Discord via webhooks for low-friction notifications.

  • /04

    All deployments managed by Ansible and shipped through GitLab CI.

How it fits together.

Hover a node to highlight its connections. Click one to read what it does and why it is there.

TICK stackquerieswebhookcomputeHomelab fleetobservabilityTelegrafdataInfluxDBobservabilityChronografobservabilityKapacitorobservabilityGrafanaexternalDiscord channelgitopsAnsiblegitopsGitLab CI

The brief

I wanted the homelab to tell me when something broke, instead of me finding out the slow way. The answer was the TICK stack plus Grafana, with alerts going into Discord because that is where I already am.

What I built

  • Telegraf agents on every host pushing metrics into InfluxDB.
  • Chronograf for quick data exploration. Kapacitor for alert logic.
  • Grafana for the dashboards I actually come back to.
  • Discord webhooks receiving alerts in a dedicated channel.
  • Ansible and GitLab CI handling deployment and config drift.

Why it mattered

The TICK stack is a real production tool, the same stack Orange runs as its centralised observability platform for managed customers. Building and operating it at home meant I understood how Telegraf agent config, InfluxDB retention policy and Kapacitor alert logic connect before I was tuning them in customer environments. The TICK era has since been replaced by Prometheus, Loki and OpenTelemetry, but the mental model for how metrics flow from host to alert carried across stacks.