StackStateChange unnecessarily sent during bigger stack redeployment #145

New Issue

GiteaMirror · 2025-10-31T15:03:15-05:00

GiteaMirror commented

2025-10-31 15:03:15 -05:00

Originally created by @gitcatpeter on GitHub (Dec 1, 2024).

"From running To unhealthy"

In my experience that only happens during big stack redeployments (my librenms=9 services).
In that case pulling new images and recreating containers could take significant time and trigger the warning.

In my opinion this notification should be disabled for the duration of the redeployment of a stack or timeout increased.

probably during compose up Stage 4 of 4 37.6 seconds

Originally created by @gitcatpeter on GitHub (Dec 1, 2024). "From running To unhealthy" In my experience that only happens during big stack redeployments (my librenms=9 services). In that case pulling new images and recreating containers could take significant time and trigger the warning. In my opinion this notification should be disabled for the duration of the redeployment of a stack or timeout increased. `probably during compose up Stage 4 of 4 37.6 seconds`

GiteaMirror added the seen 👀 label 2025-10-31 15:03:15 -05:00

GiteaMirror closed this issue

2025-10-31 15:03:15 -05:00

GiteaMirror commented

2025-10-31 15:03:17 -05:00

@mbecker20 commented on GitHub (Aug 26, 2025):

This is now the case, alerts won't be sent when stack is still deploying

@mbecker20 commented on GitHub (Aug 26, 2025): This is now the case, alerts won't be sent when stack is still deploying

GiteaMirror referenced this issue

2025-10-31 15:18:48 -05:00

[PR #145] [MERGED] 1.16.2 #696

Sign in to join this conversation.