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`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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@mbecker20 commented on GitHub (Aug 26, 2025):
This is now the case, alerts won't be sent when stack is still deploying