Repository navigation
Feature Request: Repeat Panel by Variable #12604
MikaelEngvall
started this conversation in
Ideas
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.
Problem
When monitoring many services on a single dashboard (e.g., 20+ microservices), users must manually create one panel per service — all with identical configuration except the service filter. Adding or removing a service requires editing every panel individually. This doesn't scale.
Grafana solves this with "Repeat panel by variable" where a single template panel auto-clones at render time — one instance per value of a multi-select dashboard variable.
Proposed Solution
Add a
repeatconfiguration field to the panel/widget definition:{ "id": "svc-template", "title": "{{service}} - Status Over Time", "panelTypes": "graph", "repeat": { "variable": "service", "direction": "vertical", "maxPerRow": 1 }, "query": { "promql": [{ "query": "rate(http_requests_total{service=\"{{.service}}\"}[5m])" }] } }At render time, if a panel has
repeatconfigured:directionClones are runtime-only — never persisted. Dashboard save stores only the template.
Substitution Patterns
Support standard SigNoz/Grafana variable syntax:
{{variable}}and{{.variable}}in titles and queriesUse Case
We monitor 23 services and currently maintain 23 nearly-identical panels. With repeat-by-variable, we'd have 1 template panel + a CUSTOM variable listing service names. Adding a new service = adding one value to the variable.
Scope
Phase 1 (MVP):
Phase 2:
maxPerRowTechnical Approach
A
useRepeatExpanderhook between the dashboard store andGridCardLayout.tsxthat expands template panels before rendering. No backend changes needed — purely client-side.Prior Art
Willingness to Contribute
I have a working proof-of-concept implementation and am willing to contribute this feature via PR.
All reactions