[claponcet]

What Does This Do

Run the system-tests workflow for both java and java_lambda against the agent built by the current CI run. Upload an agent-only artifact for Lambda, leaving the existing artifact (agent and OpenFeature JARs) unchanged for regular Java. Keep both matrix jobs running if either fails, and include both in the existing success gate.

Motivation

Add Lambda regression coverage to the Java tracer pipeline across API Gateway REST/HTTP, ALB single/multi-value headers, and Function URLs. The existing tracer-release group selects the Lambda scenarios.

Additional Notes

DataDog/system-tests#8128 is merged, activating the tests and updating the weblog. This workflow continues to use system-tests main.

All five Lambda profiles passed in CI: 297 tests passed, with no unexpected failures or XPASS. Expected xfails/skips remain; inferred-spans currently has no enabled tests.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: APPSEC-71301

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.89 s	13.93 s	[-1.0%; +0.4%] (no difference)
startup:insecure-bank:tracing:Agent	12.89 s	12.99 s	[-1.5%; -0.1%] (maybe better)
startup:petclinic:appsec:Agent	17.26 s	17.07 s	[+0.1%; +2.1%] (maybe worse)
startup:petclinic:iast:Agent	17.15 s	17.12 s	[-0.7%; +1.0%] (no difference)
startup:petclinic:profiling:Agent	16.56 s	16.93 s	[-3.1%; -1.2%] (significantly better)
startup:petclinic:sca:Agent	17.14 s	16.99 s	[-0.1%; +1.8%] (no difference)
startup:petclinic:tracing:Agent	16.28 s	16.26 s	[-0.7%; +0.9%] (no difference)

Commit: bfde47d3 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-27T13:32:19.508523Z	bfde47d	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-27T13:35:05.879486Z	bfde47d	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-datadog-prod-us1-2]

More details

The Lambda job receives the agent-only artifact, while regular Java retains its existing artifact. Matrix failure handling and the shared success gate are consistent with requiring both variants to succeed; no actionable defect was identified.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit bfde47d}

[amarziali]

looks ok

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-27 14:06:51 UTC ℹ️ Start processing command /merge

---

2026-10-27 14:06:55 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-10-27 15:38:44 UTC ℹ️ MergeQueue: This merge request was merged