Skip to content
Merged
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ These instructions apply to remotely-managed and locally-managed tunnels running
cloudflared tunnel diag
```

If multiple instances of `cloudflared` are running on the same host, specify the [metrics server IP and port](/cloudflare-one/connections/connect-networks/monitor-tunnels/metrics/#check-the-metrics-server-address) for the instance you want to diagnose. For example:
If multiple instances of `cloudflared` are running on the same host, specify the [metrics server IP and port](/cloudflare-one/connections/connect-networks/monitor-tunnels/metrics/#configure-the-metrics-server-address) for the instance you want to diagnose. For example:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This page: http://localhost:1111/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/diag-logs/
has a broken internal link to: http://localhost:1111/cloudflare-one/connections/connect-networks/monitor-tunnels/metrics/.
The fragment check-the-metrics-server-address does not exist.

By looking at the page: http://localhost:1111/cloudflare-one/connections/connect-networks/monitor-tunnels/metrics/
The best fragment to use seems to be: #configure-the-metrics-server-address


```sh
cloudflared tunnel diag --metrics 127.0.0.1:20241
Expand Down
Loading