Closed ashishstationcasinos closed 4 months ago
Pinging code owners:
receiver/prometheus: @Aneurysm9 @dashpole
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Can you enable debug logging in the collector? I think adding this should work. It will make the log include the reason why the scrape failed.
service:
telemetry:
logs:
level: DEBUG
Enabled the log leve to Debug.
It displayed the Actual Reason of Firewall issue.
Component(s)
receiver/prometheus
What happened?
Description
Installed OpenTelemetry Collector on AKS Kubernetes Cluster using Helm Chart . And Provided the Prometheus Config for MongoDB Atlas to pull Metrics by OpenTelemetry collector. Helm Chart Values.yaml
Steps to Reproduce
Deploy OpenTelemetry collector with Above Values.yaml using helm chart image: otel/opentelemetry-collector-contrib:0.99.0
Expected Result
Actual Result
Collector version
0.99.0
Environment information
Environment
AKS cluster with Kubernetes version 1.26.10 OpenTelemetry collector 0.99.0
OpenTelemetry Collector configuration
Log output
Additional context
No response