-
Notifications
You must be signed in to change notification settings - Fork 57
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
Allow the source of the parent context to be configurable. #607
Comments
This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled |
This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled |
This issue is stale because it has been open 90 days with no activity. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled |
This issue was closed because it has been marked as stale for 30 days with no activity. |
This is to track the upstream work as result of:
open-telemetry/opentelemetry-lambda#714
We need propose a change in the spec to add support to the EventToCarrier abstraction and make it configurable in the lambda instrumentation. The configuration should be used to inform what is the source for generating the carrier that will be used in the instrumentation so that the parent/child relationship is properly created.
References:
The text was updated successfully, but these errors were encountered: