Track client graphl documents for analytical purposes #21
Description
Describe the problem/challenge you have
As an organization, I'd like to run analyzes on the graphql operations in conjunction with the current schema. This is especially useful when all clients are controlled by the same organization.
- How does the schema coverage look like of my unified schema across all deployed clients?
- When can a field be removed from the schema? (Assumes that we know which clients are deployed)
- Which fragments, directives, mutations, variables are used?
- Is an operation name used?
- What's the average query complexity?
- How many clients/teams consume the api?
Goal: These metrics can be provided without adding runtime complexity to the gateway.
What it can't handle
- GraphQL documents that are built dynamically.
- Make statements about schema usage at runtime.
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.