Open
Conversation
Codecov Report❌ Patch coverage is ❌ Your patch status has failed because the patch coverage (36.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #2725 +/- ##
=======================================
Coverage 38.81% 38.82%
=======================================
Files 308 308
Lines 26705 26700 -5
=======================================
Hits 10365 10365
+ Misses 15561 15556 -5
Partials 779 779
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Use the same logging fields as DDAI controller (see #2519). Also increase the logging verbosity of some logs and remove extraneous logs as it's a lot of logging at the debug level.
Motivation
https://datadoghq.atlassian.net/browse/CONTP-1334
Additional Notes
There is still excessive logging for
DatadogMetricForwarders. That needs to be changed in a future PRMinimum Agent Versions
Are there minimum versions of the Datadog Agent and/or Cluster Agent required?
Describe your test plan
Check the operator logs for
New CRD detected. Previously, you'd see:{"level":"DEBUG","ts":"2026-03-09T14:06:26.946Z","logger":"metadata.crd","msg":"New CRD detected","key":"DatadogAgent/default/datadog-agent"}Now you should see:
{"level":"DEBUG","ts":"2026-03-09T20:29:26.401Z","logger":"metadata.crd","msg":"New CRD detected","kind":"DatadogAgent","namespace":"default","name":"datadog-agent"}Overall, there should also be fewer logs from the
metadata.*logger compared to previous releases.Checklist
bug,enhancement,refactoring,documentation,tooling, and/ordependenciesqa/skip-qalabel