Merge pull request #266865 from gracewehner/main

[Managed Prometheus] Add warning for debug mode and fix port number

Author: prmerger-automator[bot]

articles/azure-monitor/containers/prometheus-metrics-scrape-configuration.md

@@ -114,6 +114,10 @@ The new label also shows up in the cluster parameter dropdown in the Grafana das
 > Only alphanumeric characters are allowed. Any other characters are replaced with `_`. This change is to ensure that different components that consume this label adhere to the basic alphanumeric convention.
 
 ### Debug mode
+
+> [!WARNING]
+> This mode can affect performance and should only be enabled for a short time for debugging purposes.
+
 To view every metric that's being scraped for debugging purposes, the metrics add-on agent can be configured to run in debug mode by updating the setting `enabled` to `true` under the `debug-mode` setting in the [configmap](https://aka.ms/azureprometheus-addon-settings-configmap) `ama-metrics-settings-configmap`. You can either create this configmap or edit an existing one. For more information, see the [Debug mode section in Troubleshoot collection of Prometheus metrics](prometheus-metrics-troubleshoot.md#debug-mode).
 
 ### Scrape interval settings

articles/azure-monitor/containers/prometheus-metrics-troubleshoot.md

@@ -116,15 +116,18 @@ If there are no issues and the intended targets are being scraped, you can view
 
 ## Debug mode
 
-The metrics addon can be configured to run in debug mode by changing the configmap setting `enabled` under `debug-mode` to `true` by following the instructions [here](prometheus-metrics-scrape-configuration.md#debug-mode). This mode can affect performance and should only be enabled for a short time for debugging purposes.
+> [!WARNING]
+> This mode can affect performance and should only be enabled for a short time for debugging purposes.
 
-When enabled, all Prometheus metrics that are scraped are hosted at port 9090. Run the following command:
+The metrics addon can be configured to run in debug mode by changing the configmap setting `enabled` under `debug-mode` to `true` by following the instructions [here](prometheus-metrics-scrape-configuration.md#debug-mode).
+
+When enabled, all Prometheus metrics that are scraped are hosted at port 9091. Run the following command:
 
 ```
-kubectl port-forward <ama-metrics pod name> -n kube-system 9090
+kubectl port-forward <ama-metrics pod name> -n kube-system 9091
 ``` 
 
-Go to `127.0.0.1:9090/metrics` in a browser to see if the metrics were scraped by the OpenTelemetry Collector. This user interface can be accessed for every `ama-metrics-*` pod. If metrics aren't there, there could be an issue with the metric or label name lengths or the number of labels. Also check for exceeding the ingestion quota for Prometheus metrics as specified in this article.
+Go to `127.0.0.1:9091/metrics` in a browser to see if the metrics were scraped by the OpenTelemetry Collector. This user interface can be accessed for every `ama-metrics-*` pod. If metrics aren't there, there could be an issue with the metric or label name lengths or the number of labels. Also check for exceeding the ingestion quota for Prometheus metrics as specified in this article.
 
 ## Metric names, label names & label values