Add Grafana Alloy support as alternative to deprecated Grafana Agent #46135
Unanswered
JiminByun0101
asked this question in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
Grafana Agent reached End-of-Life on November 1, 2025 and no longer receives security or bug fixes. The current
docker-compose.ymlrelies on Grafana Agent internally, leaving users on an unmaintained collector.Solution
Add
docker-compose.alloy.ymlas 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:
grafana/alloy:v1.16.1prom/prometheus:v3.11.3grafana/grafana:13.0.1Pipeline
Alloy scrapes the Supabase Metrics API every 60s over HTTPS, then pushes metrics to Prometheus via remote write. Grafana reads from Prometheus for visualization.
Changes
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— addedSUPABASE_API_KEYfor the new Secret key formatdashboard.json— addedDS_PROMETHEUStemplate variable for Grafana 13 compatibilityImplementation
https://github.com/JiminByun0101/supabase-grafana/compare/feat/add-alloy-support
PR
supabase/supabase-grafana#83
Testing
Tested locally with WSL2. All dashboard panels render correctly with live Supabase project data.
Beta Was this translation helpful? Give feedback.
All reactions