Skip to content

monitoring: use v2 APIs in examples where they are equivalent #2538

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.

Sign up for GitHub

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

Merged
eschabell merged 1 commit into from
Apr 7, 2026
Merged

monitoring: use v2 APIs in examples where they are equivalent #2538

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions administration/monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -382,7 +382,7 @@ The command prints a similar output like this:
Query internal metrics in Prometheus Text 0.0.4 format:

```shell
curl -s http://127.0.0.1:2020/api/v1/metrics/prometheus
curl -s http://127.0.0.1:2020/api/v2/metrics/prometheus
```

This command returns the same metrics in Prometheus format instead of JSON:
Expand Down Expand Up @@ -557,7 +557,7 @@ pipeline:
Use the following command to call the health endpoint:

```shell
curl -s http://127.0.0.1:2020/api/v1/health
curl -s http://127.0.0.1:2020/api/v2/health
```

With the example configuration, the health status is determined by the following equation:
Expand Down
Loading