Alerting: Feature toggle to disallow sending alerts externally #87982
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.
What is this feature?
Adds a feature toggle to disallow sending alerts to external Alertmanager datasources.
Note that when reading the admin configuration, the persisted configuration is returned. I'm not entirely convinced this is correct, perhaps we should return the effective configuration.
Note this commit does not include frontend changes. We will likely want to modify the Settings page to not show the option to configure external Alertmanagers.
Why do we need this feature?
Site policy may dictate that alerts should be handled only internally, or if they are sent externally, should be done via the new Remote Alertmanager feature.
Note: There is no intention to remove the ability to send externally, this is merely being provided as an option for site administrators who want to disallow it.
Who is this feature for?
Site administrators of Grafana instances.
Special notes for your reviewer:
Please check that: