Skip to content
Machine BehaviorCTO
Menu

Observability stack

serviceupdated 2026-10-13edit the YAML

One Docker Compose project on a home server: Alloy, Prometheus, Loki, Tempo and Grafana, with 17 alert rules and the public dashboards behind a reverse proxy that passes only the shared paths. No Alertmanager runs, so no alert pages anyone.

Owner
Stefan Coetzee
Tier
Tier 2 Keeps the platform observable and the research running: data, dashboards, search, the agents. Fixed the same day.
Lifecycle
Production
System
Observability
Address
public dashboard
Repository
uncovertechtalent/agent-observability
Dashboard
Host (Grafana)
Current state
on the status page

Docs

Runbooks

SRE principles applied

Each principle, how this platform applies it and where it falls short: Principles in practice.

Service level objectives

None defined. Health is read from the records listed on the status page. Why that is a gap and what closes it: Service level objectives.

Dependencies

Depends on

No other service in this catalog.

Outside the catalog: Docker Compose.

Used by

Service catalog · built from services/observability-stack.yml by build_inside.py · services.json