Add Bucket and Object Key to Lambda transactions that are triggered by S3
Open
apm-agents
meta
- Dominant language
- Gherkin
- Stars
- 427
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
# Description
We started to report OTel attributes for S3 related transactions (see #759) and lambda functions triggered by S3 events should not be exception. See [this conversation](https://github.com/elastic/apm/pull/788#issuecomment-1518104399)
Having this information will be relevant to when analysing which Bucket/Key triggered the function that lead to an error or a slow execution.
## Spec Issue
- [x] https://github.com/elastic/apm/issues/791
## Agent Issues
- [ ] https://github.com/elastic/apm-agent-java/issues/3126 
- [ ] https://github.com/elastic/apm-agent-nodejs/issues/3292 
- [ ] https://github.com/elastic/apm-agent-python/issues/1815 
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.