instrumentation: stop sending telemetry logs for each log a contrib would send to stdout#3684
Conversation
BenchmarksBenchmark execution time: 2025-06-24 13:19:49 Comparing candidate commit 99736f9 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics. |
RomainMuller
left a comment
There was a problem hiding this comment.
Assuming we're quite convinced this is "all the places"
|
I would say I am 99% sure this is the only dangerous place right now. The last one 1% can be covered by @rarguelloF once he is out of PTo Original PR: https://github.com/DataDog/dd-trace-go/pull/3294/files from @ygree |
…hat is sent to stdout Signed-off-by: Eliott Bouhana <[email protected]>
b3256e4 to
d59ed8a
Compare
Datadog ReportBranch report: ✅ 0 Failed, 70 Passed, 0 Skipped, 4m 29.93s Total Time |
What does this PR do?
This PR stops reporting all contriberrors that would be on stdout to telemetry.
Partial revert of: https://github.com/DataDog/dd-trace-go/pull/3294/files
Motivation
Some logs can incluse sensitive data.
Reviewer's Checklist
golangci-lint runlocally.Unsure? Have a question? Request a review!