coop-cloud/monitoring-ng
3
0
Fork 4
Code Issues 5 Pull Requests 5 Packages Projects Releases Wiki Activity

increase grafana healthcheck start_period and reduce error logs #55

Merged
ammaratef45 merged 1 commits from quality-of-life into main 2026-10-26 17:40:03 +00:00
Conversation 2 Commits 1 Files Changed 3
+3 -4
ammaratef45 commented 2026-10-24 23:59:28 +00:00
Owner
Copy Link
Copy Source

  1. fixed the error 2026-10-24T23:47:32.683863981Z monitoring-ng_test_radmin_live_grafana.1.9ffwj6zjs143@test-radmin | logger=ngalert.state.manager rule_uid=coopcloud_node_disk_space_left org_id=1 t=2026-10-24T23:47:32.683673573Z level=warn msg="Rule contains empty label key, using fallback key" fallbackKey=__empty_label_key__

  2. new apps take about 5 tries for grafana to finish and the database migration job keeps getting interrupted, so I increated the start_period to give the container time to start cleanly

1. fixed the error `2026-10-24T23:47:32.683863981Z monitoring-ng_test_radmin_live_grafana.1.9ffwj6zjs143@test-radmin | logger=ngalert.state.manager rule_uid=coopcloud_node_disk_space_left org_id=1 t=2026-10-24T23:47:32.683673573Z level=warn msg="Rule contains empty label key, using fallback key" fallbackKey=__empty_label_key__` 2. new apps take about 5 tries for grafana to finish and the database migration job keeps getting interrupted, so I increated the start_period to give the container time to start cleanly
ammaratef45 added 1 commit 2026-10-24 23:59:28 +00:00
increase grafana healthcheck start_period and reduce error logs 202400c4da
CODEOWNERS rules requested review from Ghost 2026-10-24 23:59:28 +00:00
compose.grafana.yml
@@ -49,3 +49,3 @@
timeout: 10s
retries: 3
start_period: 10s
start_period: 300s
p4u1 commented 2026-10-25 08:33:34 +00:00
Owner
Copy Link
Copy Source

Do we really need 300s?

Do we really need 300s?
ammaratef45 commented 2026-10-25 09:20:32 +00:00
Author
Owner
Copy Link
Copy Source

a new deployment took 5 retries, with 10s timeout, 3 retries, and 5s intervals, I felt like 5 minutes are a fair enough grace for a new container

reminder that the healthceck passes early if the container was ready and doesn't wait the full 300s, it's more like a timeout for the first healthceck to pass

a new deployment took 5 retries, with 10s timeout, 3 retries, and 5s intervals, I felt like 5 minutes are a fair enough grace for a new container reminder that the healthceck passes early if the container was ready and doesn't wait the full 300s, it's more like a timeout for the first healthceck to pass
ammaratef45 requested review from p4u1 2026-10-25 09:20:41 +00:00
ammaratef45 merged commit 8c7afe5d8f into main 2026-10-26 17:40:03 +00:00
ammaratef45 deleted branch quality-of-life 2026-10-26 17:40:04 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
p4u1
dannygroenewegen
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) BornDeleuze (Born Deleuze) Brooke cas (Cassowary) coopcloud dannygroenewegen (Danny Groenewegen) decentral1se (d1) devydave fauno (fauno) hex (Josh Dukes) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower moritz notplants oxaliq (sorrel) p4u1 (p4u1) renovate-bot (Comrade Renovate Bot) simon stevensting (stevensting) trav (Trav Fryer) yksflip
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/monitoring-ng#55