-
Notifications
You must be signed in to change notification settings - Fork 379
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
[SDTEST-756] add +ci-X.Y.Z to the tracer_version reported to internal telemetry if datadog-ci is present and CI mode is enabled #3881
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3881 +/- ##
========================================
Coverage 97.87% 97.87%
========================================
Files 1277 1279 +2
Lines 76392 76521 +129
Branches 3744 3747 +3
========================================
+ Hits 74766 74893 +127
- Misses 1626 1628 +2 ☔ View full report in Codecov by Sentry. |
BenchmarksBenchmark execution time: 2024-09-06 14:44:01 Comparing candidate commit 72702ff in PR branch Found 2 performance improvements and 0 performance regressions! Performance is the same for 21 metrics, 2 unstable metrics. scenario:profiler - estimated profiler gc per minute (sample 60000 times + serialize result)
scenario:profiler - profiler gc
|
Does this PR not need any test coverage? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few notes!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM
eb1e504
to
f44f8b1
Compare
What does this PR do?
As discussed before, we will extend tracer_version reported for internal telemetry with datadog-ci gem version if tracing is running in CI mode.
The monkey patch should be removed in the next release: DataDog/datadog-ci-rb#228
Motivation:
We need a better solution to distinguish datadog-ci versions when examining telemetry metrics emitted from the datadog-ci gem.
Additional Notes:
![image](https://private-user-images.githubusercontent.com/426400/363964010-cb3f3a7b-259c-4e68-9452-40e38690cf11.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5NTU3OTYsIm5iZiI6MTczODk1NTQ5NiwicGF0aCI6Ii80MjY0MDAvMzYzOTY0MDEwLWNiM2YzYTdiLTI1OWMtNGU2OC05NDUyLTQwZTM4NjkwY2YxMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwN1QxOTExMzZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mNzFjZDI1YTY3OGYyYmViYzI5ZWQ4NzIxZTQ0MWYwNTUwOTQwZGQyMTRmZThiMDQ0MTFjZThiN2YxZWY5NGVjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.OG4JGk56t_og6x-VSMgeotoIRg6vKsruuN6DDAxLmco)
The original idea with
+ci-X.Y.Z
doesn't work perfect - it gets replaced by_
:-ci-X.Y.Z
works fine though:How to test the change?
Tested using staging (see reported tracer versions above). I didn't add unit tests because it would require bringing datadog-ci in appraisals which would be an overkill.