Skip to content

Capture native Lambda payloads with depth limits and redaction - #13249

Draft
joeyzhao2018 wants to merge 1 commit into
joey/lambda-06-message-fixturesfrom
joey/lambda-07-payload-capture
Draft

joeyzhao2018 wants to merge 1 commit into
joey/lambda-06-message-fixturesfrom
joey/lambda-07-payload-capture

Conversation

@joeyzhao2018

@joeyzhao2018 joeyzhao2018 commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

What Does This Do

Capture native Lambda request/response payload tags when enabled, with depth/truncation limits and sensitive-field redaction. Preserve usable application streams.

Motivation

Move opt-in payload capture into Java along with invocation ownership.

Additional Notes

Sensitive fields of all types are redacted before depth-limited serialization, including JSON-encoded bodies. This intentional strengthening of redaction needs review before rollout.

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: #13248

Next: #13251

@joeyzhao2018 joeyzhao2018 added type: feature Enhancements and improvements tag: serverless Serverless support inst: aws lambda AWS Lambda instrumentation tag: ai generated Largely based on code generated by an AI or LLM labels Nov 5, 2026
@dd-octo-sts

dd-octo-sts Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

🟢 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.08 s 14.01 s [-0.3%; +1.2%] (no difference)
startup:insecure-bank:tracing:Agent 12.91 s 12.96 s [-1.0%; +0.2%] (no difference)
startup:petclinic:appsec:Agent 17.09 s 16.41 s [+0.0%; +8.3%] (maybe worse)
startup:petclinic:iast:Agent 17.04 s 16.96 s [-0.4%; +1.3%] (no difference)
startup:petclinic:profiling:Agent 16.48 s 16.81 s [-3.0%; -1.0%] (maybe better)
startup:petclinic:sca:Agent 17.07 s 17.00 s [-0.3%; +1.2%] (no difference)
startup:petclinic:tracing:Agent 16.09 s 16.09 s [-0.8%; +0.9%] (no difference)

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

@datadog-datadog-prod-us1

This comment has been minimized.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

inst: aws lambda AWS Lambda instrumentation tag: ai generated Largely based on code generated by an AI or LLM tag: serverless Serverless support type: feature Enhancements and improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant