Closed trentm closed 1 year ago
https://github.com/elastic/apm-agent-nodejs/pull/3131 implemented these changes for Node.js, https://github.com/elastic/apm-agent-python/pull/1727 implemented these changes for Python, and no other APM agents have yet added ELB-triggered Lambda function support. So, no implementation issues need to be opened.
This tweaks a few
transaction
fields for ELB-triggered Lambda functions.In my draft impl for the Node.js APM agent I also added testing that:
capture_body
is enabledtransaction.context.response.status_code
defaults to 502 if there is an error or a bogus "statusCode" set in the response. E.g.: for a Lambda function that returns{ body: 'hi from myPlayHandler' }
the response is a 502:I'm not sure if we want the spec to go into those details as well.
Checklist
CODEOWNERS
)/
schedule YYYY-MM-DD
to the PR description./schedule 2023-02-02