Skip to content

Lift moratorium on AlertManager receivers with long-term maintenance plan #2561

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roidelapluie merged 2 commits into from
May 4, 2021
Merged

Lift moratorium on AlertManager receivers with long-term maintenance plan #2561

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1599ab3
Lift moratorium on AlertManager notifiers
Apr 29, 2021
1b35d05
Add a note explaining new reciever requirments
Apr 29, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -426,7 +426,7 @@ A `tls_config` allows configuring TLS connections.

Receiver is a named configuration of one or more notification integrations.

__We're not actively adding new receivers, we recommend implementing custom notification integrations via the [webhook](#webhook_config) receiver.__
Note: As part of lifting the past moratorium on new receivers it was agreed that, in addition to the existing requirements, new notification integrations will be required to have a committed maintainer with push access.

```yaml
# The unique name of the receiver.
Expand Down