[APMAPI-1847] Config visibility on all configurations#5483
Conversation
…-visibility-existing-reported
-Cleaned app_started a bit -Keep nil configs with default and code precedence -Typing
…an/config-visibility-all-configs
6053738 to
94daca9
Compare
…an/config-visibility-all-configs
…ache_key.enabled)
Typing analysisNote: Ignored files are excluded from the next sections.
|
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: 0ae0062 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback! |
…to base-5540 * origin/di-c-ext-exception-backtrace: (12817 commits) Fix system-tests CI: bump ref to Phase 1 and drop deleted secrets Disable Test Optimization reporting for system-tests Document all backtrace override scenarios in code comments Remove exception backtrace doc (moved to claude-projects) Add doc explaining Exception backtrace internals and UnboundMethod behavior Explain why UnboundMethod doesn't bypass backtrace overrides [APMAPI-1847] Config visibility on all configurations (#5483) Fix EXCEPTION_BACKTRACE test: UnboundMethod does not bypass overrides Fall back to string backtrace when backtrace_locations is nil [🤖] Update System Tests (#5529) Update lib/datadog/core/configuration/config_helper.rb Update lib/datadog/core/environment/identity.rb [🤖] Update System Tests: https://github.com/DataDog/dd-trace-rb/actions/runs/23697412204 Fix Steep: update RBS for format_backtrace and remove BACKTRACE_FRAME_PATTERN Inline exception_backtrace: use constant directly at call site Fix RBS signature: exception_backtrace returns Location not String Replace C exception_backtrace with Ruby UnboundMethod + backtrace_locations Fix undefined symbol: use have_func to gate rb_backtrace_p Fix undefined symbol: use UnboundMethod instead of internal Ruby functions Add set_backtrace test and fix formatting in specs ...
What does this PR do?
Report all configs and all their sources through telemetry
Motivation:
This will help us debug customers apps, and this will be used in the configuration panel in Datadog UI to tell users which configs are active (once you're in a service page, Service Config > SDK & Agent Configuration tab)
Combined with Config registry to provide descriptions, and the automated update of telemetry normalization files in dd-go to map them to the correct environment variables, this will provide users with a nice interface to understand the configs that are used in their service, including the default ones.
Change log entry
Yes. Report and display all configurations used by a service in the 'SDK & Agent Configurations' tab of a Ruby service page in Datadog UI
Additional Notes:
How to test the change?
CI