We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
One of the pain points we have monitoring a (Mercurius+Fastify) GraphQL server is the tracing.
By default, all is collapsed to a generic POST /graphql endpoint and there is no detail about which mutation or query is being executed.
POST /graphql
I think it would be extremely useful to support and write about this use case that is not simple (one request contains multiple queries/mutations).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
One of the pain points we have monitoring a (Mercurius+Fastify) GraphQL server is the tracing.
By default, all is collapsed to a generic
POST /graphqlendpoint and there is no detail about which mutation or query is being executed.I think it would be extremely useful to support and write about this use case that is not simple (one request contains multiple queries/mutations).
The text was updated successfully, but these errors were encountered: