Skip to content
New issue

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

JSON output flag not implemented for amtool config routes test #3741

Open
tongpu opened this issue Feb 28, 2024 · 0 comments
Open

JSON output flag not implemented for amtool config routes test #3741

tongpu opened this issue Feb 28, 2024 · 0 comments

Comments

@tongpu
Copy link

tongpu commented Feb 28, 2024

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.

# 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

  • System information:
Linux 6.7.6-arch1-1 x86_64
  • Alertmanager version:
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
  • Prometheus version:

not relevant for this issue

  • Alertmanager configuration file:

not relevant for this issue

  • Prometheus configuration file:

not relevant for this issue

  • Logs:

not relevant for this issue

zecke added a commit to zecke/alertmanager that referenced this issue May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant