-
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-3317 report probe status errored if probe fails to instrument #4301
base: master
Are you sure you want to change the base?
Conversation
spec/datadog/di/integration/everything_from_remote_config_spec.rb
Outdated
Show resolved
Hide resolved
spec/datadog/di/integration/everything_from_remote_config_spec.rb
Outdated
Show resolved
Hide resolved
Datadog ReportBranch report: ✅ 0 Failed, 22092 Passed, 1477 Skipped, 5m 8.94s Total Time |
BenchmarksBenchmark execution time: 2025-01-22 19:47:36 Comparing candidate commit b0f954d in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 31 metrics, 2 unstable metrics. |
…d but not in code tracker registry
91a1c3a
to
b0f954d
Compare
What does this PR do?
Reports probe status as errored if the probe fails to instrument.
Motivation:
Manual testing revealed that failure to instrument due to code not being in code tracker did not update UI with probe status.
Change log entry
Yes: fix UI notifications when dynamic instrumentation probes fail to instrument
Additional Notes:
How to test the change?
Tests are included