You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visiting the Mimir alertmanager UI, for a tenant that uses the fallbackConfig when configured with msteams receiver causes alertmanager to crash. Removing the msteams fixes it.
To Reproduce
Steps to reproduce the behavior:
Deploy mimir helm chart into Kubernetes cluster using the mentioned helm chart and version
Enable Mimir alertmanager with configuration (using the fallbackConfig option in the helm chart)
Visit Alertmanager ui for a tenant without it's own alertmanager config (falling back on the fallbackConfig) or reproduce an api call done by the frontend using curl
I tried to reproduce it with upstream alertmanager locally, with the same alertmanager config but couldn't. The version of upstream manager tested with:
alertmanager, version 0.27.0 (branch: HEAD, revision: 0aa3c2aad14cff039931923ab16b26b7481783b5)
build user: root@22cd11f671e9
build date: 20240228-11:51:20
go version: go1.21.7
platform: linux/amd64
tags: netgo
Describe the bug
Visiting the Mimir alertmanager UI, for a tenant that uses the
fallbackConfig
when configured withmsteams
receiver causes alertmanager to crash. Removing themsteams
fixes it.To Reproduce
Steps to reproduce the behavior:
fallbackConfig
option in the helm chart)fallbackConfig
) or reproduce an api call done by the frontend using curlExpected behavior
Mimir alertmanager to not crash when web UI visited, given MS teams was introduced as supported integration in
2.10.0
.Environment
mimir-distributed
helm chart version5.3.0
mimir version2.12.0
Additional Context
Logs from the mimir alertmanager instance.
The text was updated successfully, but these errors were encountered: