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

Support non GraphQL traces #10

Closed
danstarns opened this issue Sep 3, 2023 · 0 comments
Closed

Support non GraphQL traces #10

danstarns opened this issue Sep 3, 2023 · 0 comments

Comments

@danstarns
Copy link
Member

danstarns commented Sep 3, 2023

Problem

The collector is only designed to accept traces that have all the appropriate attribute values attached by graphql-otel, see also:

We do not counter for non-GraphQL OTEL traces, so people cannot get a fine-grained view of their GraphQL and then look further into OTEL-compliant tools they are using.

For example, if someone was using GraphQL Debugger and Prisma Tracing, they should be able to see the GraphQL traces as normal in the interface and then also see the Prisma traces displaying accordingly.

GraphQL Debugger should store non-recognized child spans in a trace group and then appropriately display them in the user interface.

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

No branches or pull requests

1 participant