-
Notifications
You must be signed in to change notification settings - Fork 424
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
chore(botocore): refactor kinesis module #8937
chore(botocore): refactor kinesis module #8937
Conversation
Datadog ReportBranch report: ✅ 0 Failed, 10400 Passed, 158712 Skipped, 3h 49m 13.82s Total duration (5h 40m 30.66s time saved) |
BenchmarksBenchmark execution time: 2024-04-10 21:43:01 Comparing candidate commit a4abdde in PR branch Found 6 performance improvements and 3 performance regressions! Performance is the same for 192 metrics, 9 unstable metrics. scenario:flasksimple-appsec-get
scenario:httppropagationextract-tracecontext_headers
scenario:httppropagationextract-wsgi_empty_headers
scenario:httppropagationextract-wsgi_invalid_span_id_header
scenario:httppropagationextract-wsgi_large_valid_headers_all
scenario:httppropagationextract-wsgi_medium_valid_headers_all
scenario:httppropagationextract-wsgi_valid_headers_basic
scenario:sethttpmeta-obfuscation-send-querystring-disabled
scenario:sethttpmeta-useragentvariant_not_exists_1
|
… input (#10262) In #7514 , I added a feature to patch start_execution calls to AWS stepfunctions and inject trace context into the input object. That feature suffered a regression in #8937 , and the whole stepfunctions integration was refactored to use the Core API in #9005 . This PR re-adds the injection of trace context into the start_execution input, and adds a few unit tests to detect the same regression in the future. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
This change refactors the kinesis module to use the core API instead of calling start_span directly in at least one instance.
Checklist
changelog/no-changelog
is set@DataDog/apm-tees
.Reviewer Checklist