[v10.4.x] Alerting: Make context deadline on AlertNG service startup configurable #96058
Conversation
This file contains 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
fayzal-g
added
area/backend
add to changelog
backport
fayzal-g
requested review from
papagian,
zserge and
undef1nd
and removed request for
a team
alexander-akhmetov
approved these changes
Nov 7, 2024
grafana-delivery-bot bot
pushed a commit
that referenced
this pull request
Nov 8, 2024
…configurable (#96058) * Alerting: Make context deadline on AlertNG service startup configurable (#96053) * Make alerting context deadline configurable * Remove debug logs * Change default timeout * Update tests (cherry picked from commit 1fdc48f) * remove file * Remove go.work.sum change * Fix backport * No cyclo flag (cherry picked from commit 880e332)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport 1fdc48f from #96053
What is this feature?
Adds a new field
unified_alerting.initialization_timeoutthat allows the context deadline for theAlertNGservice to be configurable. The default timeout is30swhich is the current hardcoded value, but can be extended in cases where users are hitting this timeout, which can be seen in cases where there are a high number of orgs.Who is this feature for?
Users that are hitting errors such as:
Which issue(s) does this PR fix?:
Fixes #69080
Special notes for your reviewer:
Please check that: