-
Notifications
You must be signed in to change notification settings - Fork 377
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
DEBUG-3328 report DI status in environment logger summary #4285
Conversation
BenchmarksBenchmark execution time: 2025-01-14 19:32:47 Comparing candidate commit 22b8070 in PR branch Found 0 performance improvements and 1 performance regressions! Performance is the same for 30 metrics, 2 unstable metrics. scenario:tracing - Propagation - Trace Context
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4285 +/- ##
==========================================
- Coverage 97.72% 97.72% -0.01%
==========================================
Files 1354 1354
Lines 82410 82455 +45
Branches 4213 4216 +3
==========================================
+ Hits 80538 80577 +39
- Misses 1872 1878 +6 ☔ View full report in Codecov by Sentry. |
* master: (161 commits) Bump to version 2.9.0 (#4293) Increase type checking coverage (#4290) DEBUG-3329 rename datadog/di/init to datadog/di/preload (#4288) update supported versions workflow (#4289) DEBUG-3182 DI railtie (#4272) DEBUG-3328 report DI status in environment logger summary (#4285) Move out ostruct gem from test group for Ruby 3.5 DEBUG-3316 verify code tracking works in forked processes (#4284) Fix rebase issue in Rack::RequestMiddleware Improve code style in AppSec rack middlewares Improve variable naming in Rack::RequestBodyMiddleware Improve variable naming in Rack::RequestMiddleware Simplify Rack::RequestMiddleware Switch AppSec rack blocking to throw Extract to .gitlab/scripts Implement polling vaccine Update RBS signatures Add new RSpec negate matcher not_change Replace direct AppSec::Processor::Context calls Change AppSec::Context exposed interface ...
What does this PR do?
Adds the state of dynamic instrumentation to environment logger summary reporting.
Motivation:
For troubleshooting it would be helpful to see whether DI is effectively turned on (i.e. it's requested to be on programmatically or via an environment variable, and environmental conditions are appropriate (environment, Ruby version, etc.))
Change log entry
Yes: library will report whether dynamic instrumentation is enabled in startup summary report
Additional Notes:
How to test the change?
Unit tests are included