alertmanager-signal-receiver
alertmanager-signal-receiver copied to clipboard
Bump github.com/prometheus/alertmanager from 0.26.0 to 0.27.0
Bumps github.com/prometheus/alertmanager from 0.26.0 to 0.27.0.
Release notes
Sourced from github.com/prometheus/alertmanager's releases.
0.27.0 / 2024-02-28
- [CHANGE] Discord Integration: Enforce max length in
message
. #3597- [CHANGE] API: Removal of all
api/v1/
endpoints. These endpoints now log and return a deprecation message and respond with a status code of410
. #2970- [FEATURE] UTF-8 Support: Introduction of support for any UTF-8 character as part of label names and matchers. Please read more below. #3453, #3483, #3567, #3570
- [FEATURE] Metrics: Introduced the experimental feature flag
--enable-feature=receiver-name-in-metrics
to include the receiver name in the following metrics: #3045
alertmanager_notifications_total
alertmanager_notifications_failed_totall
alertmanager_notification_requests_total
alertmanager_notification_requests_failed_total
alertmanager_notification_latency_seconds
- [FEATURE] Metrics: Introduced a new gauge named
alertmanager_inhibition_rules
that counts the number of configured inhibition rules. #3681- [FEATURE] Metrics: Introduced a new counter named
alertmanager_alerts_supressed_total
that tracks muted alerts, it contains areason
label to indicate the source of the mute. #3565- [ENHANCEMENT] Discord Integration: Introduced support for
webhook_url_file
. #3555- [ENHANCEMENT] Microsoft Teams Integration: Introduced support for
webhook_url_file
. #3555- [ENHANCEMENT] Microsoft Teams Integration: Add support for
summary
. #3616- [ENHANCEMENT] Metrics: Notification metrics now support two new values for the label
reason
,contextCanceled
andcontextDeadlineExceeded
. #3631- [ENHANCEMENT] Email Integration: Contents of
auth_password_file
are now trimmed of prefixed and suffixed whitespace. #3680- [BUGFIX] amtool: Fixes the error
scheme required for webhook url
when using amtool with--alertmanager.url
. #3509- [BUGFIX] Mixin: Fix
AlertmanagerFailedToSendAlerts
,AlertmanagerClusterFailedToSendAlerts
, andAlertmanagerClusterFailedToSendAlerts
to make sure they ignore thereason
label. #3599Removal of API v1
The Alertmanager
v1
API has been deprecated since January 2019 with the release of Alertmanagerv0.16.0
. With the release of version0.27.0
it is now removed. A successful HTTP request to any of thev1
endpoints will log and return a deprecation message while responding with a status code of410
. Please ensure you switch to thev2
equivalent endpoint in your integrations before upgrading.Alertmanager support for all UTF-8 characters in matchers and label names
Starting with Alertmanager
v0.27.0
, we have a new parser for matchers that has a number of backwards incompatible changes. While most matchers will be forward-compatible, some will not. Alertmanager is operating a transition period where it supports both UTF-8 and classic matchers, so it's entirely safe to upgrade without any additional configuration. With that said, we recommend the following:
If this is a new Alertmanager installation, we recommend enabling UTF-8 strict mode before creating an Alertmanager configuration file. You can enable strict mode with
alertmanager --config.file=config.yml --enable-feature="utf8-strict-mode"
.If this is an existing Alertmanager installation, we recommend running the Alertmanager in the default mode called fallback mode before enabling UTF-8 strict mode. In this mode, Alertmanager will log a warning if you need to make any changes to your configuration file before UTF-8 strict mode can be enabled. Alertmanager will make UTF-8 strict mode the default in the next two versions, so it's important to transition as soon as possible.
Irrespective of whether an Alertmanager installation is a new or existing installation, you can also use
amtool
to validate that an Alertmanager configuration file is compatible with UTF-8 strict mode before enabling it in Alertmanager server by runningamtool check-config config.yml
and inspecting the log messages.Should you encounter any problems, you can run the Alertmanager with just the classic parser enabled by running
alertmanager --config.file=config.yml --enable-feature="classic-mode"
. If so, please submit a bug report via GitHub issues.0.27.0-rc.0 / 2024-02-14
- [CHANGE] Discord Integration: Enforce max length in
message
. #3597- [CHANGE] API: Removal of all
api/v1/
endpoints. These endpoints now log and return a deprecation message and respond with a status code of410
. #2970- [FEATURE] UTF-8 Support: Introduction of support for any UTF-8 character as part of label names and matchers. Please read more below. #3453, #3483, #3567, #3570
- [FEATURE] Metrics: Introduced the experimental feature flag
--enable-feature=receiver-name-in-metrics
to include the receiver name in the following metrics: #3045
alertmanager_notifications_total
alertmanager_notifications_failed_totall
alertmanager_notification_requests_total
alertmanager_notification_requests_failed_total
alertmanager_notification_latency_seconds
- [FEATURE] Metrics: Introduced a new gauge named
alertmanager_inhibition_rules
that counts the number of configured inhibition rules. #3681- [FEATURE] Metrics: Introduced a new counter named
alertmanager_alerts_supressed_total
that tracks muted alerts, it contains areason
label to indicate the source of the mute. #3565
... (truncated)
Changelog
Sourced from github.com/prometheus/alertmanager's changelog.
0.27.0 / 2024-02-28
- [CHANGE] Discord Integration: Enforce max length in
message
. #3597- [CHANGE] API: Removal of all
api/v1/
endpoints. These endpoints now log and return a deprecation message and respond with a status code of410
. #2970- [FEATURE] UTF-8 Support: Introduction of support for any UTF-8 character as part of label names and matchers. Please read more below. #3453, #3483, #3567, #3570
- [FEATURE] Metrics: Introduced the experimental feature flag
--enable-feature=receiver-name-in-metrics
to include the receiver name in the following metrics: #3045
alertmanager_notifications_total
alertmanager_notifications_failed_totall
alertmanager_notification_requests_total
alertmanager_notification_requests_failed_total
alertmanager_notification_latency_seconds
- [FEATURE] Metrics: Introduced a new gauge named
alertmanager_inhibition_rules
that counts the number of configured inhibition rules. #3681- [FEATURE] Metrics: Introduced a new counter named
alertmanager_alerts_supressed_total
that tracks muted alerts, it contains areason
label to indicate the source of the mute. #3565- [ENHANCEMENT] Discord Integration: Introduced support for
webhook_url_file
. #3555- [ENHANCEMENT] Microsoft Teams Integration: Introduced support for
webhook_url_file
. #3555- [ENHANCEMENT] Microsoft Teams Integration: Add support for
summary
. #3616- [ENHANCEMENT] Metrics: Notification metrics now support two new values for the label
reason
,contextCanceled
andcontextDeadlineExceeded
. #3631- [ENHANCEMENT] Email Integration: Contents of
auth_password_file
are now trimmed of prefixed and suffixed whitespace. #3680- [BUGFIX] amtool: Fixes the error
scheme required for webhook url
when using amtool with--alertmanager.url
. #3509- [BUGFIX] Mixin: Fix
AlertmanagerFailedToSendAlerts
,AlertmanagerClusterFailedToSendAlerts
, andAlertmanagerClusterFailedToSendAlerts
to make sure they ignore thereason
label. #3599Removal of API v1
The Alertmanager
v1
API has been deprecated since January 2019 with the release of Alertmanagerv0.16.0
. With the release of version0.27.0
it is now removed. A successful HTTP request to any of thev1
endpoints will log and return a deprecation message while responding with a status code of410
. Please ensure you switch to thev2
equivalent endpoint in your integrations before upgrading.Alertmanager support for all UTF-8 characters in matchers and label names
Starting with Alertmanager
v0.27.0
, we have a new parser for matchers that has a number of backwards incompatible changes. While most matchers will be forward-compatible, some will not. Alertmanager is operating a transition period where it supports both UTF-8 and classic matchers, so it's entirely safe to upgrade without any additional configuration. With that said, we recommend the following:
If this is a new Alertmanager installation, we recommend enabling UTF-8 strict mode before creating an Alertmanager configuration file. You can enable strict mode with
alertmanager --config.file=config.yml --enable-feature="utf8-strict-mode"
.If this is an existing Alertmanager installation, we recommend running the Alertmanager in the default mode called fallback mode before enabling UTF-8 strict mode. In this mode, Alertmanager will log a warning if you need to make any changes to your configuration file before UTF-8 strict mode can be enabled. Alertmanager will make UTF-8 strict mode the default in the next two versions, so it's important to transition as soon as possible.
Irrespective of whether an Alertmanager installation is a new or existing installation, you can also use
amtool
to validate that an Alertmanager configuration file is compatible with UTF-8 strict mode before enabling it in Alertmanager server by runningamtool check-config config.yml
and inspecting the log messages.Should you encounter any problems, you can run the Alertmanager with just the classic parser enabled by running
alertmanager --config.file=config.yml --enable-feature="classic-mode"
. If so, please submit a bug report via GitHub issues.
Commits
0aa3c2a
Cut Alertmanager version 0.27 from the rc.0 (#3740)1234193
Merge branch 'main' into release-0.270fbd018
Fix flaky test TestClusterJoinAndReconnect/TestTLSConnection (#3722)d352d16
Fix flaky test TestClusterJoinAndReconnect/TestTLSConnection (#3722)b379b29
more worthsmithing6d52bcf
small fixes824de35
Release: Cut 0.27.0-rc.0c2cf3db
Support UTF-8 label matchers: Update the docs on how to use UTF-8 in label ma...4d6ddd2
Fix panic in acceptance tests (#3592)604d442
Fix log line in featurecontrol (#3719)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)