geomagilles commented on a change in pull request #10099: URL: https://github.com/apache/pulsar/pull/10099#discussion_r605022410
########## File path: site2/website/versioned_docs/version-2.7.1/deploy-monitoring.md ########## @@ -74,7 +74,7 @@ Those metrics are added in the Prometheus interface, you can monitor and check t You can use Prometheus to collect all the metrics exposed for Pulsar components and set up [Grafana](https://grafana.com/) dashboards to display the metrics and monitor your Pulsar cluster. For details, refer to [Prometheus guide](https://prometheus.io/docs/introduction/getting_started/). -When you run Pulsar on bare metal, you can provide the list of nodes to be probed. When you deploy Pulsar in a Kubernetes cluster, the monitoring is setup automatically. For details, refer to [Kubernetes instructions](kubernetes-helm.md). +When you run Pulsar on bare metal, you can provide the list of nodes to be probed. When you deploy Pulsar in a Kubernetes cluster, the monitoring is setup automatically. For details, refer to [Kubernetes instructions](helm-install.md). Review comment: done. > @geomagilles Thank you for your contribution. If we have similar issues in other versions, we need to apply the updates in related versions as well. Strangely, the link was correct in 2.7.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
