Prometheus Alertmanager
message
. #3597api/v1/
endpoints. These endpoints now log and return a deprecation message and respond with a status code of 410
. #2970--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
alertmanager_inhibition_rules
that counts the number of configured inhibition rules. #3681alertmanager_alerts_supressed_total
that tracks muted alerts, it contains a reason
label to indicate the source of the mute. #3565webhook_url_file
. #3555webhook_url_file
. #3555summary
. #3616reason
, contextCanceled
and contextDeadlineExceeded
. #3631auth_password_file
are now trimmed of prefixed and suffixed whitespace. #3680scheme required for webhook url
when using amtool with --alertmanager.url
. #3509AlertmanagerFailedToSendAlerts
, AlertmanagerClusterFailedToSendAlerts
, and AlertmanagerClusterFailedToSendAlerts
to make sure they ignore the reason
label. #3599The Alertmanager v1
API has been deprecated since January 2019 with the release of Alertmanager v0.16.0
. With the release of version 0.27.0
it is now removed.
A successful HTTP request to any of the v1
endpoints will log and return a deprecation message while responding with a status code of 410
.
Please ensure you switch to the v2
equivalent endpoint in your integrations before upgrading.
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 running amtool 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.
message
. #3597api/v1/
endpoints. These endpoints now log and return a deprecation message and respond with a status code of 410
. #2970--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
alertmanager_inhibition_rules
that counts the number of configured inhibition rules. #3681alertmanager_alerts_supressed_total
that tracks muted alerts, it contains a reason
label to indicate the source of the mute. #3565webhook_url_file
. #3555webhook_url_file
. #3555summary
. #3616reason
, contextCanceled
and contextDeadlineExceeded
. #3631auth_password_file
are now trimmed of prefixed and suffixed whitespace. #3680scheme required for webhook url
when using amtool with --alertmanager.url
. #3509AlertmanagerFailedToSendAlerts
, AlertmanagerClusterFailedToSendAlerts
, and AlertmanagerClusterFailedToSendAlerts
to make sure they ignore the reason
label. #3599The Alertmanager v1
API has been deprecated since January 2019 with the release of Alertmanager v0.16.0
. With the release of version 0.27.0
it is now removed.
A successful HTTP request to any of the v1
endpoints will log and return a deprecation message while responding with a status code of 410
.
Please ensure you switch to the v2
equivalent endpoint in your integrations before upgrading.
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 running amtool 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.
api_url
is now optional. #2981ParseMode
default is now HTML
instead of MarkdownV2
. #2981url
is now marked as a secret. It will no longer show up in the logs as clear-text. #3228reason
for alertmanager_notifications_failed_total
metric to indicate the type of error of the alert delivery. #3094 #3307--cluster.label
, to help to block any traffic that is not meant for the cluster. #3354bot_token_file
for loading this secret from a file. #3226url_file
for loading this secret from a file. #3223url_file
. #3363device
and sound
(sound was previously supported but undocumented). #3318user_key_file
and token_file
for loading this secret from a file. #3200CORS
and Cache-Control
HTTP headers to all version 2 API routes. #3195{{ .Annotations }}
and {{ .Labels }}
. #3256trimSpace
which removes leading and trailing white spaces. #3223amtool silence query
now supports the --id
flag to query an individual silence. #3241alertmanager_nflog_maintenance_total
and alertmanager_nflog_maintenance_errors_total
to monitor maintenance of the notification log. #3286alertmanager_silences_maintenance_total
and alertmanager_silences_maintenance_errors_total
to monitor maintenance of silences. #3285receivers
and inhibit_rules
would cause the alertmanager to crash. #3209title
function. It is now race-safe. #3278api/v2/receivers
API endpoint. #3338404
instead of 500
. #3352tls_client_config
is empty. #3443api_url
is now optional. #2981ParseMode
default is now HTML
instead of MarkdownV2
. #2981url
is now marked as a secret. It will no longer show up in the logs as clear-text. #3228reason
for alertmanager_notifications_failed_total
metric to indicate the type of error of the alert delivery. #3094 #3307--cluster.label
, to help to block any traffic that is not meant for the cluster. #3354bot_token_file
for loading this secret from a file. #3226url_file
for loading this secret from a file. #3223url_file
. #3363device
and sound
(sound was previously supported but undocumented). #3318user_key_file
and token_file
for loading this secret from a file. #3200CORS
and Cache-Control
HTTP headers to all version 2 API routes. #3195{{ .Annotations }}
and {{ .Labels }}
. #3256trimSpace
which removes leading and trailing white spaces. #3223amtool silence query
now supports the --id
flag to query an individual silence. #3241alertmanager_nflog_maintenance_total
and alertmanager_nflog_maintenance_errors_total
to monitor maintenance of the notification log. #3286alertmanager_silences_maintenance_total
and alertmanager_silences_maintenance_errors_total
to monitor maintenance of silences. #3285receivers
and inhibit_rules
would cause the alertmanager to crash. #3209title
function. It is now race-safe. #3278api/v2/receivers
API endpoint. #3338404
instead of 500
. #3352tls_client_config
is empty. #3443parse_mode
value from MarkdownV2
to HTML
for Telegram. #2981api_url
field optional for Telegram. #2981proxy_url
support for OAuth2 in HTTP client configuration. #3010--web.systemd-socket
flag to systemd socket activation listeners instead of port listeners (Linux only). #3140enable_http2
support in HTTP client configuration. #3010min_version
support to select the minimum TLS version in HTTP client configuration. #3010max_version
support to select the maximum TLS version in HTTP client configuration. #3168--data.maintenance-interval
flag to define the interval between the garbage collection and snapshotting to disk of the silences and the notification logs. #2849/-/healty
and /-/ready
endpoints. #3039…
ellipsis character instead of the 3-dots string ...
. #3072source
field to the PagerDuty configuration. #3106api_key
and api_key_file
are defined at the same time. #2910alertmanager_alerts
metric to avoid counting resolved alerts as active. Also added a new alertmanager_marked_alerts
metric that retain the old behavior. #2943api_url
is empty for OpsGenie. #2910parse_mode
value from MarkdownV2
to HTML
for Telegram. #2981api_url
field optional for Telegram. #2981proxy_url
support for OAuth2 in HTTP client configuration. #3010--web.systemd-socket
flag to systemd socket activation listeners instead of port listeners (Linux only). #3140enable_http2
support in HTTP client configuration. #3010min_version
support to select the minimum TLS version in HTTP client configuration. #3010max_version
support to select the maximum TLS version in HTTP client configuration. #3168--data.maintenance-interval
flag to define the interval between the garbage collection and snapshotting to disk of the silences and the notification logs. #2849/-/healty
and /-/ready
endpoints. #3039…
ellipsis character instead of the 3-dots string ...
. #3072source
field to the PagerDuty configuration. #3106api_key
and api_key_file
are defined at the same time. #2910alertmanager_alerts
metric to avoid counting resolved alerts as active. Also added a new alertmanager_marked_alerts
metric that retain the old behavior. #2943api_url
is empty for OpsGenie. #2910/api/v2
prefix to all endpoints in the OpenAPI specification and generated client code. #2696github.com/prometheus/alertmanager/client
Go package. #2763--cluster.tls-config
experimental flag to secure cluster traffic via mutual TLS. #2237time_intervals
rather than mute_time_intervals
(the latter is deprecated but it will be supported until v1.0). #2779update_alerts
field to the OpsGenie configuration to update message and description when sending alerts. #2519--cluster.allow-insecure-public-advertise-address-discovery
feature flag to enable discovery and use of public IP addresses for clustering. #2719entity
and actions
fields to the OpsGenie configuration. #2753opsgenie_api_key_file
field to the global configuration. #2728teams
responders to the OpsGenie configuration. #2685createdBy
author. #2718--http.config.file
flag to configure HTTP settings. #2764mute_time_intervals
in JSON marshaling. #2765email.default.html
) to match with the canonical source. #2798/api/v2
prefix to all endpoints in the OpenAPI specification and generated client code. #2696github.com/prometheus/alertmanager/client
Go package. #2763--cluster.tls-config
experimental flag to secure cluster traffic via mutual TLS. #2237time_intervals
rather than mute_time_intervals
(the latter is deprecated but it will be supported until v1.0). #2779update_alerts
field to the OpsGenie configuration to update message and description when sending alerts. #2519--cluster.allow-insecure-public-advertise-address-discovery
feature flag to enable discovery and use of public IP addresses for clustering. #2719entity
and actions
fields to the OpsGenie configuration. #2753opsgenie_api_key_file
field to the global configuration. #2728teams
responders to the OpsGenie configuration. #2685createdBy
author. #2718--http.config.file
flag to configure HTTP settings. #2764mute_time_intervals
in JSON marshaling. #2765email.default.html
) to match with the canonical source. #2798