[joeyzhao2018]

What Does This Do

Continue native Lambda traces through Java propagation and baggage extraction, honoring configured styles and extraction behavior.

Motivation

Make event-derived context participate in the tracer’s existing parent and sampling decisions.

Additional Notes

Includes unsigned/128-bit IDs, carrier fallbacks, ignore/restart behavior and invocation-scoped baggage. No extension identity reporting is involved.

Validation: Revised complete stack: 513 focused core tests, 12 forked Lambda tests and 40 handler tests passed; the handler total includes two zero-lifecycle-HTTP cases. Independent P3 lifecycle, P8b DSM and P10 legacy/native boundary checks also passed. Spotless applied. Core validation uses a local init script to omit an unused private container dependency; repository build settings are unchanged. Deployed certification remains pending.

Contributor Checklist

• Focused local validation and formatting.
• Required labels and Lambda ownership patterns retained.
• Deployment, platform compatibility and performance gates before rollout.

Jira ticket: APMSVLS-689.

Previous: #13244

Next: #13246

[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	14.03 s	14.00 s	[-0.5%; +1.0%] (no difference)
startup:insecure-bank:tracing:Agent	13.00 s	13.01 s	[-1.0%; +0.8%] (no difference)
startup:petclinic:appsec:Agent	17.28 s	17.13 s	[+0.1%; +1.7%] (maybe worse)
startup:petclinic:iast:Agent	17.13 s	17.02 s	[-0.2%; +1.4%] (no difference)
startup:petclinic:profiling:Agent	16.72 s	16.32 s	[-2.0%; +6.9%] (no difference)
startup:petclinic:sca:Agent	17.17 s	17.10 s	[-0.4%; +1.2%] (no difference)
startup:petclinic:tracing:Agent	16.16 s	16.13 s	[-0.8%; +1.2%] (no difference)

Commit: 1d955abc · 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.