-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support aws EventBridge instrumentation #4166
Comments
Hi @calindurnea, Some notes to get you started:
I haven't used EventBridge myself, so my help might be limited. |
Hello @trentm, |
<!-- Replace this comment with a description of what's being changed by this PR. If this PR should close an issue, please add one of the magic keywords (e.g. Fixes) followed by the issue number. For more info see: https://help.github.com/articles/closing-issues-using-keywords/ --> Resolves elastic#4166. Extends the aws lambda handled triggers with eventbridge specific events. The minimum event structure is based on https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-events-structure.html and it contains: ```json { "detail-type": "event name", "source": "event source", "detail": { JSON object } } ``` The full event that can be handled is the following: ```json { "version": "0", "id": "UUID", "detail-type": "event name", "source": "event source", "account": "ARN", "time": "timestamp", "region": "region", "resources": [ "ARN" ], "detail": { "traceparent": "00-traceId-spanId", ... } } ``` ### Checklist - [x] Implement code - [x] Add tests - [ ] Update TypeScript typings - [ ] Update documentation - [x] Add CHANGELOG.asciidoc entry - [x] Commit message follows [commit guidelines](https://github.com/elastic/apm-agent-nodejs/blob/main/CONTRIBUTING.md#commit-message-guidelines)
Is your feature request related to a problem? Please describe.
I would like to have a module that enables instrumentation of AWS lambdas that use EventBridge as a trigger.
Describe the solution you'd like
When a lambda gets triggered by an EventBridge event I would like instrumentation to be tracked similarly to how the AWS SQS functions.
Describe alternatives you've considered
I have attempted to use the lambda layers and then start custom transactions to continue the tracing. When doing this I have encountered issues with the custom traces not being sent to elasticsearch, I could only see the default trace that the layer generate on a new lambda invocation, but without any other context (for example the traceparent)
I would be open to giving it a shot at implementing this myself. I am open to any feedback or guidelines.
The text was updated successfully, but these errors were encountered: