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
3 changed files with 3 additions and 4 deletions
+1 -1
View File
@@ -9,7 +9,7 @@ export LOKI_YML_VERSION=v3
export PROMETHEUS_YML_VERSION=v2
export MATRIX_ALERTMANAGER_CONFIG_VERSION=v1
export MATRIX_ALERTMANAGER_ENTRYPOINT_VERSION=v1
export GF_ALERTS_NODE_VERSION=v4
export GF_ALERTS_NODE_VERSION=v5
export CONFIG_ALLOY_VERSION=v3
# migrates secrets from old names to new names by reading values from the
+1 -2
View File
@@ -71,8 +71,7 @@ groups:
description: ""
runbook_url: ""
summary: Less than {{ env "ALERT_NODE_DISK_SPACE_LEFT" }}% disk space left on {{`{{ $labels.instance }}`}} ({{`{{ (index $values "A").Value }}`}}% left)
labels:
"": ""
labels: {}
isPaused: false
{{ end }}
{{ if (env "ALERT_NODE_MEMORY_USAGE") }}
+1 -1
View File
@@ -48,7 +48,7 @@ services:
interval: 5s
timeout: 10s
retries: 3
start_period: 10s
start_period: 300s
Review

Do we really need 300s?

Do we really need 300s?
Review

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
configs:
gf_custom_ini: