Skip to content

Commit 36826b1

Browse files
Remove the section for types of auth and add note for pod monitor
1 parent 935870d commit 36826b1

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

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

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -459,11 +459,6 @@ metric_relabel_configs:
459459
---
460460
461461
462-
Prometheus supports TLS and basic authentication over its HTTP endpoints. Scraping target using HTTPS instead of HTTP is supported. You could fetch metrics using HTTPS, client-certificate authentication, and basic authentication.
463-
464-
Below are the details on 2 mechanisms of authentication.
465-
1. Basic authentication
466-
2. TLS based authentication
467462
468463
### Basic Authentication
469464
@@ -504,8 +499,9 @@ basic_auth:
504499

505500
> [!NOTE]
506501
>
507-
> The **/etc/prometheus/certs/** path is mandatory, but *password1* can be any string and needs to match the key for the data in the secret created above.
508-
This is because the secret **ama-metrics-mtls-secret** is mounted in the path **/etc/prometheus/certs/** within the container.
502+
> Pod and Service monitors currently do not support basic authentication. Support for the same is coming up soon.
503+
>
504+
> The **/etc/prometheus/certs/** path is mandatory, but *password1* can be any string and needs to match the key for the data in the secret created above. This is because the secret **ama-metrics-mtls-secret** is mounted in the path **/etc/prometheus/certs/** within the container.
509505
>
510506
> The base64 encoded value is automatically decoded by the agent pods when the secret is mounted as file.
511507
>

0 commit comments

Comments
 (0)