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
What did you do?
Tried to format the output from amtool config routes test as JSON using the --output=json flag.
amtool config routes test
--output=json
What did you expect to see?
The list of matched routes as a JSON list, instead of the comma separated strings, e.g.
# amtool config routes test --output=json --config.file=alertmanager-config.yaml --verify.receivers=Default,slack-default namespace=example alertname=KubePodNotReady ["Default", "slack-default"]
What did you see instead? Under which circumstances?
The default comma separated string where being shown, e.g.
# amtool config routes test --output=json --config.file=alertmanager-config.yaml --verify.receivers=Default,slack-default namespace=example alertname=KubePodNotReady Default,slack-default
Environment
Linux 6.7.6-arch1-1 x86_64
alertmanager, version 0.26.0 (branch: tarball, revision: 0.26.0) build user: someone@builder build date: 20230825-18:04:14 go version: go1.21.0 platform: linux/amd64 tags: unknown
not relevant for this issue
The text was updated successfully, but these errors were encountered:
Create a formatter for config test routes (fixes prometheus#3741)
d1a8adc
No branches or pull requests
What did you do?
Tried to format the output from
amtool config routes test
as JSON using the--output=json
flag.What did you expect to see?
The list of matched routes as a JSON list, instead of the comma separated strings, e.g.
What did you see instead? Under which circumstances?
The default comma separated string where being shown, e.g.
Environment
not relevant for this issue
not relevant for this issue
not relevant for this issue
not relevant for this issue
The text was updated successfully, but these errors were encountered: