We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
route.ID()
What did you do?
It is possible to write an Alertmanager configuration file where route.ID() returns conflicting IDs. For example, the configuration file:
receiver: test routes: - matchers: - foo=bar continue: true routes: - matchers: - bar=baz - matchers: - foo=bar continue: true routes: - matchers: - bar=baz
gives the following Route IDs:
{} {}/{foo="bar"}/0 {}/{foo="bar"}/{bar="baz"}/0 {}/{foo="bar"}/1 {}/{foo="bar"}/{bar="baz"}/0
What did you expect to see?
It should give these IDs instead:
{} {}/{foo="bar"}/0 {}/{foo="bar"}/0/{bar="baz"}/0 {}/{foo="bar"}/1 {}/{foo="bar"}/1/{bar="baz"}/0
The text was updated successfully, but these errors were encountered:
Route.ID()
No branches or pull requests
What did you do?
It is possible to write an Alertmanager configuration file where
route.ID()
returns conflicting IDs. For example, the configuration file:gives the following Route IDs:
What did you expect to see?
It should give these IDs instead:
The text was updated successfully, but these errors were encountered: