Hello Team,
We are trying to integrate Azure-managed Prometheus to our MongoDB cluster
for monitoring but we are running into some issues.
We got the below scrape config from the prometheus integration page in
Atlas MongoDB
- job_name: "sandbox-mongo-metrics"
scrape_interval: 10s
metrics_path: /metrics
scheme: https
basic_auth:
username: "prometheus"
password: "xxx"
http_sd_configs:
- url:
https://cloud.mongodb.com/prometheus/v1.0/groups/xxx/discovery?targetScheme=PRIVATE
refresh_interval: 60s
basic_auth:
username: "prometheus"
password: "xxx"
And we use the below ConfigMap to add the scrape config to prometheus.
kind: ConfigMap
apiVersion: v1
data:
prometheus-config: |-
scrape_configs:
- job_name: "sandbox-mongo-metrics"
scrape_interval: 10s
metrics_path: /metrics
scheme: https
basic_auth:
username: "prometheus"
password: "xxx"
http_sd_configs:
- url:
https://cloud.mongodb.com/prometheus/v1.0/groups/xxx/discovery?targetScheme=PRIVATE
refresh_interval: 60s
basic_auth:
username: "prometheus"
password: "xxx"
metadata:
name: ama-metrics-prometheus-config
namespace: kube-system
The target discovery works without issues when we check with a curl command
locally and in the kubernetes pod running prometheus.
But the target on the prometheus web ui fails with the below error
server returned HTTP status 401 Unauthorized
Any assistance is appreciated!
Thanks,
Arun
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/prometheus-users/36e14848-4108-4193-83c3-8facfe52a2a1n%40googlegroups.com.
