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

Instrumented versions of OTP behaviours #149

Open
tsloughter opened this issue Nov 20, 2020 · 0 comments
Open

Instrumented versions of OTP behaviours #149

tsloughter opened this issue Nov 20, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@tsloughter
Copy link
Member

In the SIG meeting yesterday @yurishkuro asked about auto-instrumentation, like in Java and others. I realized this is similar to what @ferd and I had discussed at one point making otel_gen_* behaviours to be used in place of the standard gen_* modules but that propagate context.

Preferably they would just call the gen_* modules so no logic/features have to be duplicated, but I the receiving of the messages and unwrapping the context before calling handle_* will have to be implemented.

I'm also now wondering if adding "context" to OTP so the gen_* behaviours propagate it could be an acceptable patch to OTP.

This would still leave raw send to not be automatically propagating context, but this could be a happy middle ground between always propagating some value across processes and having to always do it manually.

Opening this issue to track/discuss ideas, other issues should probably be opened to track implementation of individual behaviours.

@tsloughter tsloughter added the enhancement New feature or request label Nov 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant