Skip to content
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

fix: introduce otellambda instrumentation #288

Merged
merged 1 commit into from
May 31, 2024
Merged

fix: introduce otellambda instrumentation #288

merged 1 commit into from
May 31, 2024

Conversation

jta
Copy link
Contributor

@jta jta commented May 31, 2024

Wrap our existing mux instrumentation with the otellambda package. The upstream package sets a reasonable span name, kind, and injects attributes that are consistent with the faas semantic convention.

In order to attach the payload to every invocation we still need to provide our own Invoke method. The payload is added as an attribute.

Wrap our existing mux instrumentation with the `otellambda` package. The
upstream package sets a reasonable span name, kind, and injects
attributes that are consistent with the `faas` semantic convention.

In order to attach the payload to every invocation we still need to
provide our own Invoke method. The payload is added as an attribute.
@jta jta marked this pull request as ready for review May 31, 2024 17:08
@jta jta merged commit f534b29 into main May 31, 2024
16 checks passed
@jta jta deleted the joao/otellambda branch May 31, 2024 19:34
Copy link

🎉 This PR is included in version 1.19.2-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Copy link

🎉 This PR is included in version 1.19.2-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Copy link

🎉 This PR is included in version 1.19.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants