DEV-48976 - Make-context-deadline-on-AlertNG-service-startup-configurable #120
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
…able Cherrypick from: Alerting: Make context deadline on AlertNG service startup configurable (grafana#96053) grafana@1fdc48f
Author
|
run-test |
kotkovkirill
approved these changes
Sep 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This fix is due to issues where getting panic due to
context deadline exceededwhen alertmanager for orgs are loading in server init.It seems the hard-coded 30 seconds timeout is not enough, and we need to raise it.
Cherrypick from:
Alerting: Make context deadline on AlertNG service startup configurable (grafana#96053) grafana@1fdc48f
Make alerting context deadline configurable
Change default timeout
Update tests