-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing datadog metrics for the prodpublick8s
AKS cluster
#3123
Comments
The logs of the cluster-agent pods for
which looks like DataDog/datadog-agent#10413 and DataDog/datadog-agent#10764 |
Closing as it is now working. |
prodpublick8s
AKS cluster
While working on the datadog integration with the artifact caching proxy (#2752 ) we discovered that the datadog agents of this cluster are failing with the following errors:
Also a LOT of warnings like below, related to our custom python checks (embedded in the Docker image from jenkins-infra/docker-datadog):
|
Two (closed) issues about the error message that could (or not) help: |
Which dates from https://github.com/DataDog/helm-charts/blob/main/charts/datadog/CHANGELOG.md#2320 => https://github.com/jenkins-infra/kubernetes-management/pull/2225/files |
By the way: https://docs.datadoghq.com/agent/troubleshooting/debug_mode/?tab=agentv6v7#containerized-agent is really useful to enable debug log on a given agent while it is running |
Service(s)
Azure, Other
Summary
Datadog dashboards are only reporting a partial set of the metrics from the prodpublick8s cluster
![Capture d’écran 2022-09-09 à 09 54 40](https://user-images.githubusercontent.com/1522731/189301247-8f0f70f8-80ba-42bb-bd16-3fcc6c96a658.png)
![Capture d’écran 2022-09-09 à 09 54 29](https://user-images.githubusercontent.com/1522731/189301243-f615b967-ee33-4277-b226-bf4ecb37f6f4.png)
2 Az
ure Kubernetes clusters compared to thes AWS and Digital Ocean clusters as you can see on the screenshots below:
On short term, we have our own Grafana installation to gather metrics for prodpublick8s, but it's running... in this cluster
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: