Grafana Agent reached End-of-Life on November 1, 2025 and no longer receives security or bug fixes. The current docker-compose.yml relies on Grafana Agent internally, leaving users on an unmaintained collector.
Add docker-compose.alloy.yml as an opt-in alternative setup using Grafana Alloy, the official open-source successor to Grafana Agent.
The new setup uses three separate official images instead of a single bundled custom image:
| Service | Image |
|---|---|
| Metrics collector | grafana/alloy:v1.16.1 |
| Storage | prom/prometheus:v3.11.3 |
| Visualization | grafana/grafana:13.0.1 |
Alloy scrapes the Supabase Metrics API every 60s over HTTPS, then pushes metrics to Prometheus via remote write. Grafana reads from Prometheus for visualization.
docker-compose.alloy.yml — new compose filealloy/config.alloy — Alloy pipeline configurationgrafana/datasource.alloy.yml — Grafana datasource provisioningdocs/alloy-setup.md — quick start guide.env.example — added SUPABASE_API_KEY for the new Secret key formatdashboard.json — added DS_PROMETHEUS template variable for Grafana 13 compatibilityhttps://github.com/JiminByun0101/supabase-grafana/compare/feat/add-alloy-support
Tested locally with WSL2. All dashboard panels render correctly with live Supabase project data.
<img width="939" height="246" alt="Alloy UI showing two healthy components" src="https://github.com/user-attachments/assets/9be2fd74-0054-4b2f-9e39-9b12e0fc0de8" /> <img width="949" height="880" alt="Grafana dashboard with live Supabase data" src="https://github.com/user-attachments/assets/9e7d4c9e-b6c9-4f3a-aea0-2a1218b03d48" />Jimin Byun suggests adding Grafana Alloy support as an alternative to the deprecated Grafana Agent. The proposal includes a new docker-compose.alloy.yml setup using Grafana Alloy, Prometheus, and Grafana images. This change aims to maintain a secure and updated metrics collection pipeline for Supabase projects.