You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: