-
Notifications
You must be signed in to change notification settings - Fork 345
V3.29.0 proposal #3427
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
V3.29.0 proposal #3427
Conversation
…ler (#3371) * Initial code for code hotspots and endpoint aggregation in wall profiler Hide functionality behind DD_PROFILING_EXPERIMENTAL_CODEHOTSPOTS_ENABLED and DD_PROFILING_EXPERIMENTAL_ENDPOINT_COLLECTION_ENABLED flags. Profiler tracks changes of active span by subscribing to async hooks before channel and to AsyncResourceStorage enter channel that notifies when current store is changed with enterWith/run. Profiler remembers previous span and previous started spans, upon change of active span, it checks if a sample has been taken by native profiler addon, then if that's the case, it updates the context of the sample with span id and root span id computed from previous span / started spans. It also add the tags from the last web span to the context to allow computation of endpoint later on. Minor changes to other parts of the code to make it all work: === * Report error if start fails * Avoid clearing span context tags upon export Profiler may need the tags to determine span resource name for endpoint aggregation: profiler keeps a reference on web span that was active when each profiling sample is taken. Then during profile export, span tags are used to determine endpoint. Endpoint cannot be determined right away because sometimes tags necessary to determine endpoint are only set just before span is finished. * Add request tags just after span creation For web spans, add request tags just after span creation instead of when span finishes. This is needed for profiler code hotspots implementation to determine which span are web spans and should be used to find current endpoint.
* Taint request URI * Add check for safe tainted origins on unvalidated redirect analyzer * Change assertion construction for unvalidated redirect analyzer test * Add metric for uri sourcing * Fix PR comments
* Detect X-Content-Type-Options missing header * HSTS Header missing analyzer and refactor of xcontenttype-header-missing-aanalyzer * Move function to class method * use startswith instead of index===0 * Do not send evidence if value is undefined * Fix comment in PR and add test * Changes to support telemetry * Rename method name * Rename analyzer object key
Forgot to update yarn.lock when bumping pprof-nodejs version in a previous PR.
* Fix same dependency detection * Do not send same dependency:version twice * Clear map on stop * Update savedDependencies to savedDependenciesToSend to improve understanding
Co-authored-by: Attila Szegedi <[email protected]>
* address and fix edge cases * move to better tracer option name for service name flattening
* implement naming schema for graphql plugin * implement schema v1 and add tests --------- Co-authored-by: Thomas Hunter II <[email protected]> Co-authored-by: Jordi Bertran de Balanda <[email protected]>
Overall package sizeSelf size: 4.91 MB Dependency sizes
🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report
@@ Coverage Diff @@
## v3.x #3427 +/- ##
=======================================
Coverage ? 84.50%
=======================================
Files ? 218
Lines ? 8572
Branches ? 33
=======================================
Hits ? 7244
Misses ? 1328
Partials ? 0 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
BenchmarksBenchmark execution time: 2023-07-21 13:09:00 Comparing candidate commit d71337c in PR branch Found 1 performance improvements and 33 performance regressions! Performance is the same for 675 metrics, 29 unstable metrics. scenario:appsec-iast-no-vulnerability-control-14
scenario:appsec-iast-no-vulnerability-control-16
scenario:exporting-pipeline-0.4-14
scenario:exporting-pipeline-0.4-16
scenario:exporting-pipeline-0.4-18
scenario:exporting-pipeline-0.4_with_stats-14
scenario:exporting-pipeline-0.4_with_stats-16
scenario:exporting-pipeline-0.4_with_stats-18
scenario:exporting-pipeline-0.5-14
scenario:exporting-pipeline-0.5-16
scenario:exporting-pipeline-0.5-18
scenario:exporting-pipeline-0.5_with_stats-14
scenario:exporting-pipeline-0.5_with_stats-16
scenario:exporting-pipeline-0.5_with_stats-18
scenario:plugin-graphql-with-depth-and-collapse-on-18
scenario:plugin-graphql-with-depth-off-18
scenario:plugin-graphql-with-depth-on-max-18
scenario:spans-finish-later-14
|
* Couchbase: Update Docker Container repo This repo uses a slightly modified version of the Couchbase docker image for testing. This modified version is required to do some base configuration of the Couchbase container (such as password setup, memory settings, and more). Prior to this change, we used a container image/repo owned by Sam Brenner (sabrenner). This change forks the sabrenner repository and adds the container to DataDog's github container repository. * Couchbase: update tested versions This change updates several of the versions of Couchbase which we test against. In particular: * 2.6.12 replaces 2.6.5 due to an inability to compile 2.6.5 in the latest Node releases * 3.0.7 replaces 3.0.0 due to test timeout issues causing flakiness * 3.1.2 replaces 3.1.0 due to test timeout issues causing flakiness These changes put the couchbase dependency in a state where it can be re-introduced to the CI tests. * Couchbase: Re-enable testing Prior to this change, Couchbase tests were disabled due to constant failures and flaky tests. Recent changes have fixed the testing issues by: * Upgrading Couchbase server from 6.0.1 to 6.6.5 * Updating the versions of Couchbase client we use to test This change re-enables testing the Couchbase integration now that tests are working and stable.
* try to fix flaky test * Update test-gcloud-function.sh * Update test-gcloud-function.sh * Update test-gcloud-function.sh * Update test-gcloud-function.sh
ec246cb
to
66454e5
Compare
* Add BITBUCKET_GIT_HTTP_ORIGIN env variable * Update CI spec JSONs
66454e5
to
d71337c
Compare
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.
looks good from CI Visibility's perspective
Features
Enhancements
Bug fixes
Minor stuff (probably not notable for release notes)