Skip to content

test(llmobs): use DD_LLMOBS_ENABLED in tagger sampling fixtures#9107

Merged
pabloerhard merged 1 commit into
masterfrom
BridgeAR/2026-06-26-fix-llmobs-tagger-sampling-enabled-key
Jun 26, 2026
Merged

test(llmobs): use DD_LLMOBS_ENABLED in tagger sampling fixtures#9107
pabloerhard merged 1 commit into
masterfrom
BridgeAR/2026-06-26-fix-llmobs-tagger-sampling-enabled-key

Conversation

@BridgeAR

Copy link
Copy Markdown
Member

Summary

Four tagger sampling test fixtures added by #9030 build their own Tagger instances with { llmobs: { enabled: true } }. PR #8943 renamed that key to DD_LLMOBS_ENABLED across the rest of tagger.spec.js, but both PRs were in flight at the same time — #8943 never saw the new fixtures.

On master the tagger reads this.#config.llmobs.DD_LLMOBS_ENABLED, finds it undefined in these four fixtures, and returns early before registering the span. Tagger.tagMap.get(span) yields undefined; the "DROPPED at sampleRate 0" test then throws synchronously, aborting the whole test:llmobs:sdk:ci run with exit 7.

Refs: #9030, #8943

The sampling tests in #9030 build their own taggers with `{ llmobs:
{ enabled: true } }`, and #8943 renamed that config key to
`DD_LLMOBS_ENABLED` everywhere it could see. The two landed in parallel,
so #8943 normalized the rest of the file but never saw these four
fixtures. On master the tagger now reads `DD_LLMOBS_ENABLED`, finds it
undefined, and returns before registering the span; `Tagger.tagMap.get`
then yields undefined and the "DROPPED at sampleRate 0" test throws
synchronously, aborting the whole `test:llmobs:sdk:ci` run with exit 7.

Fixes: https://github.com/DataDog/dd-trace-js/actions/runs/28265509637/job/83751636644
@BridgeAR BridgeAR requested a review from a team as a code owner June 26, 2026 21:49
@dd-octo-sts

dd-octo-sts Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Overall package size

Self size: 6.38 MB
Deduped: 7.44 MB
No deduping: 7.44 MB

Dependency sizes | name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.2.0 | 104.26 kB | 843.44 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |

🤖 This report was automatically generated by heaviest-objects-in-the-universe

@pabloerhard pabloerhard enabled auto-merge (squash) June 26, 2026 21:50
@datadog-datadog-prod-us1

datadog-datadog-prod-us1 Bot commented Jun 26, 2026

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 88.01% (+1.17%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 35e97a5 | Docs | Datadog PR Page | Give us feedback!

@pr-commenter

pr-commenter Bot commented Jun 26, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-06-26 21:59:09

Comparing candidate commit 35e97a5 in PR branch BridgeAR/2026-06-26-fix-llmobs-tagger-sampling-enabled-key with baseline commit d4a75c2 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2249 metrics, 37 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:appsec-appsec-enabled-20

  • unstable execution_time [-180.413ms; +194.878ms] or [-4.829%; +5.216%]

scenario:appsec-appsec-enabled-24

  • unstable execution_time [-181184.567µs; +181984.201µs] or [-6.887%; +6.917%]

scenario:appsec-appsec-enabled-26

  • unstable execution_time [-208.165ms; +213.435ms] or [-8.254%; +8.463%]

scenario:appsec-appsec-enabled-with-attacks-26

  • unstable execution_time [-159.577ms; +151.020ms] or [-5.539%; +5.242%]

scenario:appsec-control-20

  • unstable execution_time [-152.336ms; +167.077ms] or [-8.740%; +9.585%]

scenario:appsec-control-24

  • unstable execution_time [-103.650ms; +108.313ms] or [-8.549%; +8.934%]

scenario:appsec-control-26

  • unstable execution_time [-111.025ms; +113.741ms] or [-9.199%; +9.424%]

scenario:debugger-line-probe-with-snapshot-default-24

  • unstable cpu_user_time [-1837.538ms; +2893.151ms] or [-23.225%; +36.566%]
  • unstable execution_time [-1857.991ms; +2944.721ms] or [-21.611%; +34.251%]
  • unstable instructions [-15.9G instructions; +25.2G instructions] or [-24.716%; +39.164%]
  • unstable max_rss_usage [-6.446MB; +10.627MB] or [-4.079%; +6.726%]
  • unstable throughput [-875.455op/s; +553.377op/s] or [-22.832%; +14.432%]

scenario:debugger-line-probe-with-snapshot-minimal-24

  • unstable cpu_user_time [-1957.412ms; +3098.110ms] or [-24.686%; +39.072%]
  • unstable execution_time [-1982.798ms; +3149.532ms] or [-23.037%; +36.592%]
  • unstable instructions [-16.8G instructions; +26.7G instructions] or [-26.017%; +41.341%]
  • unstable max_rss_usage [-7.923MB; +11.632MB] or [-4.997%; +7.336%]
  • unstable throughput [-911.483op/s; +575.961op/s] or [-23.722%; +14.990%]

scenario:debugger-line-probe-without-snapshot-24

  • unstable cpu_user_time [-2673.484ms; +2585.380ms] or [-31.449%; +30.412%]
  • unstable execution_time [-2755.222ms; +2665.751ms] or [-30.004%; +29.030%]
  • unstable instructions [-22487.3M instructions; +21992.1M instructions] or [-32.455%; +31.740%]
  • unstable max_rss_usage [-9817.404KB; +9194.204KB] or [-6.126%; +5.737%]
  • unstable throughput [-781.491op/s; +811.391op/s] or [-21.277%; +22.091%]

scenario:debugger-line-probe-without-snapshot-26

  • unstable cpu_user_time [-3278.885ms; +2871.755ms] or [-32.767%; +28.698%]
  • unstable execution_time [-3292.121ms; +2908.477ms] or [-30.770%; +27.184%]
  • unstable instructions [-29.7G instructions; +25.9G instructions] or [-35.412%; +30.950%]
  • unstable max_rss_usage [-8433.991KB; +9543.591KB] or [-5.201%; +5.885%]
  • unstable throughput [-650.647op/s; +719.865op/s] or [-20.581%; +22.770%]

scenario:dogstatsd-with-tags-20

  • unstable cpu_user_time [-258.613ms; +415.321ms] or [-5.210%; +8.367%]
  • unstable execution_time [-255.464ms; +416.160ms] or [-5.071%; +8.261%]
  • unstable throughput [-144101.145op/s; +85284.290op/s] or [-8.642%; +5.114%]

scenario:plugin-graphql-long-with-depth-and-collapse-off-24

  • unstable cpu_user_time [-320.932ms; +289.477ms] or [-6.971%; +6.288%]
  • unstable execution_time [-347.124ms; +316.786ms] or [-7.083%; +6.464%]
  • unstable max_rss_usage [-47.035MB; +38.195MB] or [-8.431%; +6.846%]
  • unstable throughput [-2.903op/s; +3.563op/s] or [-6.673%; +8.189%]

scenario:plugin-graphql-long-with-depth-off-20

  • unstable max_rss_usage [-12764.182KB; +10943.611KB] or [-8.858%; +7.594%]

scenario:spans-finish-later-26

  • unstable max_rss_usage [-8418.390KB; +9014.390KB] or [-5.640%; +6.039%]

scenario:test-optimization-large-suite-20

  • unstable max_rss_usage [-6.089MB; +3.064MB] or [-7.513%; +3.780%]

@codecov

codecov Bot commented Jun 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.69%. Comparing base (d4a75c2) to head (35e97a5).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #9107      +/-   ##
==========================================
+ Coverage   92.77%   93.69%   +0.92%     
==========================================
  Files         889      889              
  Lines       50846    50846              
  Branches    11801    11801              
==========================================
+ Hits        47171    47641     +470     
+ Misses       3675     3205     -470     
Flag Coverage Δ
aiguard 34.87% <ø> (-0.08%) ⬇️
aiguard-integration 41.79% <ø> (ø)
apm-bucket-0 34.84% <ø> (-0.08%) ⬇️
apm-bucket-1 40.34% <ø> (-0.07%) ⬇️
apm-bucket-2 37.34% <ø> (-0.07%) ⬇️
apm-capabilities-tracing 48.57% <ø> (ø)
apm-integrations-aerospike 33.12% <ø> (-0.08%) ⬇️
apm-integrations-confluentinc-kafka-javascript 40.03% <ø> (-0.08%) ⬇️
apm-integrations-couchbase 33.24% <ø> (-0.24%) ⬇️
apm-integrations-http 42.04% <ø> (-0.07%) ⬇️
apm-integrations-kafkajs 40.27% <ø> (-0.08%) ⬇️
apm-integrations-next 29.46% <ø> (-0.11%) ⬇️
apm-integrations-prisma 35.03% <ø> (-0.07%) ⬇️
apm-integrations-tedious 33.90% <ø> (-0.08%) ⬇️
appsec 57.38% <ø> (+0.06%) ⬆️
appsec-express_fastify_graphql 53.73% <ø> (-0.06%) ⬇️
appsec-integration 36.17% <ø> (ø)
appsec-kafka_ldapjs_lodash 43.60% <ø> (-0.07%) ⬇️
appsec-mongodb-core_mongoose_mysql 48.81% <ø> (-0.06%) ⬇️
appsec-next 28.00% <ø> (-0.07%) ⬇️
appsec-node-serialize_passport_postgres 48.00% <ø> (-0.06%) ⬇️
appsec-sourcing_stripe_template 45.57% <ø> (-0.05%) ⬇️
debugger 44.41% <ø> (+0.04%) ⬆️
instrumentations-bucket-0 28.15% <ø> (-0.08%) ⬇️
instrumentations-bucket-1 37.41% <ø> (-0.07%) ⬇️
instrumentations-bucket-10 40.43% <ø> (-0.07%) ⬇️
instrumentations-bucket-11 27.95% <ø> (-0.08%) ⬇️
instrumentations-bucket-12 28.67% <ø> (-0.08%) ⬇️
instrumentations-bucket-13 27.78% <ø> (-0.08%) ⬇️
instrumentations-bucket-2 30.23% <ø> (-0.07%) ⬇️
instrumentations-bucket-3 35.91% <ø> (-0.07%) ⬇️
instrumentations-bucket-4 28.07% <ø> (-0.08%) ⬇️
instrumentations-bucket-5 36.28% <ø> (-0.07%) ⬇️
instrumentations-bucket-6 38.26% <ø> (-0.08%) ⬇️
instrumentations-bucket-7 36.00% <ø> (+0.01%) ⬆️
instrumentations-bucket-8 36.96% <ø> (-0.07%) ⬇️
instrumentations-bucket-9 39.53% <ø> (-0.07%) ⬇️
instrumentations-instrumentation-couchbase 46.50% <ø> (ø)
instrumentations-integration-esbuild 24.75% <ø> (ø)
llmobs-ai_anthropic_bedrock 39.54% <ø> (-0.07%) ⬇️
llmobs-google-genai_langchain_vertex-ai 36.98% <ø> (-0.06%) ⬇️
llmobs-openai 39.58% <ø> (-0.07%) ⬇️
llmobs-sdk 43.60% <ø> (?)
master-coverage 93.69% <ø> (?)
openfeature 37.75% <ø> (-0.01%) ⬇️
openfeature-unit 50.39% <ø> (ø)
platform-core_esbuild_instrumentations-misc 23.25% <ø> (ø)
platform-integration 47.43% <ø> (ø)
platform-shimmer_unit-guardrails_webpack 18.80% <ø> (ø)
plugins-bucket-0 36.33% <ø> (-0.07%) ⬇️
plugins-bucket-1 39.60% <ø> (ø)
plugins-bucket-11 38.46% <ø> (-0.57%) ⬇️
plugins-bucket-14 ?
plugins-bucket-17 39.16% <ø> (-0.38%) ⬇️
plugins-bucket-18 42.09% <ø> (+4.74%) ⬆️
plugins-bucket-19 39.56% <ø> (-0.17%) ⬇️
plugins-bucket-20 43.20% <ø> (+1.51%) ⬆️
plugins-bucket-4 37.72% <ø> (-0.07%) ⬇️
plugins-bullmq_cassandra_cookie 39.77% <ø> (-0.07%) ⬇️
plugins-cookie-parser_crypto_dd-trace-api 33.22% <ø> (-0.08%) ⬇️
plugins-fetch_fs_generic-pool 36.06% <ø> (-0.07%) ⬇️
plugins-google-cloud-pubsub_grpc_handlebars 43.11% <ø> (-0.07%) ⬇️
plugins-hapi_hono_ioredis 37.79% <ø> (-0.07%) ⬇️
plugins-jest_knex_langgraph 32.61% <ø> (?)
plugins-jest_langgraph_ldapjs ?
plugins-ldapjs_light-my-request_limitd-client 27.91% <ø> (?)
plugins-light-my-request_limitd-client_lodash ?
plugins-lodash_mariadb_memcached 35.18% <ø> (?)
plugins-mariadb_memcached_microgateway-core ?
plugins-mongodb-core_mongoose_multer ?
plugins-mongodb_mongodb-core_mongoose 36.31% <ø> (?)
plugins-multer_mysql_mysql2 35.15% <ø> (?)
plugins-mysql_mysql2_nats ?
plugins-nats_node-serialize_opensearch 37.09% <ø> (?)
plugins-passport-http_pino_postgres 35.53% <ø> (?)
plugins-pino_postgres_process ?
plugins-process_pug_redis 34.26% <ø> (?)
plugins-pug_redis_router ?
plugins-undici_url_valkey 35.76% <ø> (?)
plugins-url_valkey_vm ?
plugins-vm_winston_ws 37.56% <ø> (?)
plugins-winston_ws ?
profiling 43.62% <ø> (-0.07%) ⬇️
serverless-aws-sdk-aws-sdk 33.30% <ø> (-0.07%) ⬇️
serverless-aws-sdk-bedrockruntime 32.16% <ø> (-0.07%) ⬇️
serverless-aws-sdk-client 37.17% <ø> (ø)
serverless-aws-sdk-dynamodb 34.10% <ø> (-0.20%) ⬇️
serverless-aws-sdk-eventbridge 27.25% <ø> (-0.07%) ⬇️
serverless-aws-sdk-kinesis 37.41% <ø> (-0.07%) ⬇️
serverless-aws-sdk-lambda 34.60% <ø> (-0.07%) ⬇️
serverless-aws-sdk-s3 32.60% <ø> (-0.07%) ⬇️
serverless-aws-sdk-serverless-peer-service 39.47% <ø> (-0.17%) ⬇️
serverless-aws-sdk-sns 38.26% <ø> (-0.07%) ⬇️
serverless-aws-sdk-sqs 38.00% <ø> (-0.07%) ⬇️
serverless-aws-sdk-stepfunctions 33.18% <ø> (-0.07%) ⬇️
serverless-aws-sdk-util 47.95% <ø> (ø)
serverless-bucket-0 39.46% <ø> (ø)
serverless-lambda 34.33% <ø> (-0.09%) ⬇️
test-optimization-cucumber 52.67% <ø> (+0.11%) ⬆️
test-optimization-cypress 49.62% <ø> (-0.04%) ⬇️
test-optimization-jest 55.64% <ø> (+0.07%) ⬆️
test-optimization-mocha 53.65% <ø> (+0.08%) ⬆️
test-optimization-playwright-playwright-atr 43.58% <ø> (+0.08%) ⬆️
test-optimization-playwright-playwright-efd 43.87% <ø> (+0.08%) ⬆️
test-optimization-playwright-playwright-final-status 43.92% <ø> (+0.11%) ⬆️
test-optimization-playwright-playwright-impacted-tests 43.41% <ø> (ø)
test-optimization-playwright-playwright-reporting 43.49% <ø> (+0.08%) ⬆️
test-optimization-playwright-playwright-test-management 44.93% <ø> (+0.08%) ⬆️
test-optimization-playwright-playwright-test-span 44.78% <ø> (+0.07%) ⬆️
test-optimization-selenium 45.52% <ø> (+0.06%) ⬆️
test-optimization-testopt 48.28% <ø> (+0.08%) ⬆️
test-optimization-vitest 50.93% <ø> (+0.10%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pabloerhard pabloerhard merged commit 1ed6244 into master Jun 26, 2026
806 checks passed
@pabloerhard pabloerhard deleted the BridgeAR/2026-06-26-fix-llmobs-tagger-sampling-enabled-key branch June 26, 2026 21:59
dd-octo-sts Bot pushed a commit that referenced this pull request Jun 29, 2026
The sampling tests in #9030 build their own taggers with `{ llmobs:
{ enabled: true } }`, and #8943 renamed that config key to
`DD_LLMOBS_ENABLED` everywhere it could see. The two landed in parallel,
so #8943 normalized the rest of the file but never saw these four
fixtures. On master the tagger now reads `DD_LLMOBS_ENABLED`, finds it
undefined, and returns before registering the span; `Tagger.tagMap.get`
then yields undefined and the "DROPPED at sampleRate 0" test throws
synchronously, aborting the whole `test:llmobs:sdk:ci` run with exit 7.

Fixes: https://github.com/DataDog/dd-trace-js/actions/runs/28265509637/job/83751636644
This was referenced Jun 29, 2026
rochdev pushed a commit that referenced this pull request Jul 2, 2026
The sampling tests in #9030 build their own taggers with `{ llmobs:
{ enabled: true } }`, and #8943 renamed that config key to
`DD_LLMOBS_ENABLED` everywhere it could see. The two landed in parallel,
so #8943 normalized the rest of the file but never saw these four
fixtures. On master the tagger now reads `DD_LLMOBS_ENABLED`, finds it
undefined, and returns before registering the span; `Tagger.tagMap.get`
then yields undefined and the "DROPPED at sampleRate 0" test throws
synchronously, aborting the whole `test:llmobs:sdk:ci` run with exit 7.

Fixes: https://github.com/DataDog/dd-trace-js/actions/runs/28265509637/job/83751636644
rochdev pushed a commit that referenced this pull request Jul 2, 2026
The sampling tests in #9030 build their own taggers with `{ llmobs:
{ enabled: true } }`, and #8943 renamed that config key to
`DD_LLMOBS_ENABLED` everywhere it could see. The two landed in parallel,
so #8943 normalized the rest of the file but never saw these four
fixtures. On master the tagger now reads `DD_LLMOBS_ENABLED`, finds it
undefined, and returns before registering the span; `Tagger.tagMap.get`
then yields undefined and the "DROPPED at sampleRate 0" test throws
synchronously, aborting the whole `test:llmobs:sdk:ci` run with exit 7.

Fixes: https://github.com/DataDog/dd-trace-js/actions/runs/28265509637/job/83751636644
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants