Let the dashboard match a rolled api container by pattern #96

New issue

Closed

opened 2026-10-10 05:32:57 +00:00 by ahmad · 0 comments

ahmad commented

2026-10-10 05:32:57 +00:00

Owner

Context

grafana-dashboard's "API errors" Loki panel matches the api container by exact name ({container="<api-container>"}). A service deployed with deploy-vps's rolling-services has no fixed name: compose numbers each replica (rihla-api-2, rihla-api-3, …), so after the first swap the panel shows nothing. Needed for suhba/rihla#417.

Scope

In: match api-container as a regular expression (=~), and say so in the input's description and the README.
Out: the other panels.

Acceptance criteria

Given api-container: rihla-api-.*, when the dashboard is pushed, then the panel shows errors from whichever replica is running.
Given an existing consumer passing an exact name, when the dashboard is pushed, then the panel matches that container as before.

### Context grafana-dashboard's "API errors" Loki panel matches the api container by exact name (`{container="<api-container>"}`). A service deployed with deploy-vps's `rolling-services` has no fixed name: compose numbers each replica (`rihla-api-2`, `rihla-api-3`, …), so after the first swap the panel shows nothing. Needed for suhba/rihla#417. ### Scope - In: match `api-container` as a regular expression (`=~`), and say so in the input's description and the README. - Out: the other panels. ### Acceptance criteria - [ ] Given `api-container: rihla-api-.*`, when the dashboard is pushed, then the panel shows errors from whichever replica is running. - [ ] Given an existing consumer passing an exact name, when the dashboard is pushed, then the panel matches that container as before.

ahmad added the

labels

2026-10-10 05:32:57 +00:00

ahmad self-assigned this

2026-10-10 05:32:57 +00:00

ahmad referenced this issue from a pull request that will close it,

2026-10-10 05:33:45 +00:00

feat: Match the dashboard api container by pattern #97