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

Investigate bi-directional context propagation between NR and OTel #2098

Open
jasonjkeller opened this issue Oct 19, 2024 · 1 comment
Open
Assignees
Labels
oct-dec qtr Represents proposed work item for the Oct-Dec quarter

Comments

@jasonjkeller
Copy link
Contributor

jasonjkeller commented Oct 19, 2024

The prototype in the Java agent appears to be uni-directional, where it receives a notification that a span started or ended, and then it starts/stops a transaction/segment using the internal New Relic data model.

It doesn't appear that this internal state is reflected back into the OTel API.

Maybe this uni-directional approach is good enough to start out with?

Maybe we can have a better offering if we can support reflecting some of our internal context back via the OTel APIs?

See the results described here for an example of some of the issues that need to be addressed: #2060 (comment)

@workato-integration
Copy link

@jasonjkeller jasonjkeller self-assigned this Oct 19, 2024
@jasonjkeller jasonjkeller moved this from Triage to In Quarter in Java Engineering Board Oct 19, 2024
@jasonjkeller jasonjkeller added the oct-dec qtr Represents proposed work item for the Oct-Dec quarter label Oct 19, 2024
@jasonjkeller jasonjkeller moved this from In Quarter to In Sprint in Java Engineering Board Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
oct-dec qtr Represents proposed work item for the Oct-Dec quarter
Projects
Status: In Sprint
Development

No branches or pull requests

1 participant