Add start_period to Prometheus healthcheck to prevent cold-start timeouts - #1092
Open
aarush-murari wants to merge 1 commit into
Open
Add start_period to Prometheus healthcheck to prevent cold-start timeouts#1092aarush-murari wants to merge 1 commit into
aarush-murari wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
start_period: 60sto Prometheus healthcheck to prevent cold-start failuresOn first deploy, Prometheus needs time to initialize its TSDB before responding to healthchecks. Without a startup grace period, Docker marks it unhealthy after ~30s, causing
dependency failed to start: container prometheus is unhealthyand killing the entire compose stack.start_period: 60sgives Prometheus a grace window where failed healthchecks don't count toward the retry limit.