-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[FA] Always instrument methods #19956
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
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
77d942d to
49f035f
Compare
iliakur
left a comment
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.
Just some questions about the exception-catching logic in the new code we're introducing, otherwise seems fine!
iliakur
left a comment
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, but something's up with the CI...
Review from iliakur is dismissed. Related teams and files:
- agent-integrations
- datadog_checks_base/datadog_checks/base/utils/tracing.py
What does this PR do?
This PR update the instrumentation logic of all the check methods.
Here are the following changes:
AGENT_CHECK_DEFAULT_TRACED_METHODSare always instrumented (meaning wrapped with atracer.trace)configure_tracermethod before running the method.configure_tracersamples all traces ifintegration_tracingorintegration_tracing_exhaustiveis truedd_trace_idanddd_parent_span_idif they exist in the instance.Next step is to read the sampling from the agent config, and let the agent pass the trade ID and the parent ID through the instance
Motivation
The goal is to be able to enable or disable tracing at runtime. (PR in progress)
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged