Skip to main content

Tag: Datadog

Problems related to Datadog integration, such as missing metrics, reporting failures, or misconfigurations

IDTitleDescriptionCategoryTechnologyTags
prequel-2025-0028
Low
Impact: 2/10
Mitigation: 2/10
Datadog Postgres Check ExceptionThe Datadog Agent’s *Postgres* integration throws an uncaught Python traceback while trying to run an `EXPLAIN (FORMAT JSON)` against a sampled query. After the first failure the underlying **psycopg2** cursor is closed, and every subsequent collection cycle logs ``` Traceback … File ".../datadog_checks/postgres/explain_parameterized_queries.py", … psycopg2.InterfaceError: cursor already closed ``` The check status flips to **ERROR**, and query metrics / samples stop flowing.Postgres ProblemsdatadogPostgreSQLDatadog
prequel-2025-0081
Medium
Impact: 6/10
Mitigation: 4/10
ArgoCD RawExtension API Field Error with Datadog OperatorArgoCD application controller fails to process certain custom resources due to being unable to find API fields in struct RawExtension. This commonly affects users deploying Datadog Operator CRDs, resulting in application sync errors for these resources.Continuous Delivery ProblemsargocdArgoCDKubernetesCustom ResourceDatadog
prequel-2025-0099
Medium
Impact: 6/10
Mitigation: 3/10
DataDog Agent Remote Configuration ErrorDataDog Agent encounters "empty targets meta in director local store" errors when attempting to retrieve remote configuration. This issue affects APM (Application Performance Monitoring) remote configuration functionality in DataDog Agent versions between 7.61.0 and 7.68.0. The error prevents proper retrieval and parsing of remote configuration from DataDog's backend, causing APM tracer libraries to fail when attempting to fetch dynamic configuration updates.Observability ProblemsdatadogDatadogObservabilityConfiguration