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
feat(asm): standalone asm #9211
base: main
Are you sure you want to change the base?
Conversation
Datadog ReportBranch report: ❌ 37 Failed (1 Known Flaky), 142439 Passed, 30676 Skipped, 10h 22m 31.04s Total duration (49m 12.21s time saved) ❌ Failed Tests (37)
|
BenchmarksBenchmark execution time: 2024-05-17 13:52:05 Comparing candidate commit 1ac9b8d in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 209 metrics, 9 unstable metrics. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9211 +/- ##
===========================================
- Coverage 78.55% 6.78% -71.77%
===========================================
Files 1277 1247 -30
Lines 120316 118546 -1770
===========================================
- Hits 94511 8044 -86467
- Misses 25805 110502 +84697 ☔ View full report in Codecov by Sentry. |
# for the backend to consider the service as alive. | ||
from ddtrace.internal.rate_limiter import RateLimiter | ||
|
||
self._sampler.limiter = RateLimiter(rate_limit=1, time_window=60e9) # 1 trace per minute |
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.
Technically we can't rely on the _sampler always having a rate limiter in the event that customers set their own custom sampler (deprecated and is going to be removed in next major release). So we may want to try except around this and log something.
|
||
self._sampler.limiter = RateLimiter(rate_limit=1, time_window=60e9) # 1 trace per minute | ||
# Disable compute stats | ||
config._trace_compute_stats = False |
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.
Why do we need to disable compute stats?
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.
Well, it's part of the RFC. I think because we're disabling "APM" features basically
Mainly, make sure previous headers are reused at writer recreate
Description
This PR allows ASM customers to disable APM, and use only ASM features.
Details
It involves changes when opting out from APM with
DD_TRACE_ENABLED=false
, whileDD_APPSEC_ENABLED=true
:Datadog-Client-Computed-Stats
header is sent to the agent so it doesn't compute stats on its end, but they aren't computed on the library side either.dd.apm.enabled:0
metric in top span.Checklist
changelog/no-changelog
is set@DataDog/apm-tees
.Reviewer Checklist