graphql
graphql copied to clipboard
RFC-026: GraphQL Toolbox tracking
RFC to add tracking to the GraphQL Toolbox.
⚠️ No Changeset found
Latest commit: 7b3b3f1f5a1a3d1e7ec4d47c28e41db1c8e1451b
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Tracking requirements for Toolbox Can we track high level details of type definitions?
- number of types
- quantity of directive usage
- number of interfaces and unions
- use third party library to calculate complexity of queries so that we can start informing the scale we need to support for the service offering and pricing
- queries count and mutation count To understand how people use these features
Additional tracking Possibly add link to track interest in GraphQL aaS. Want us to host your API for you? Click here to register your interest Publish your API feature coming soon! Click here to register your interest
@tbwiss Can you advise on what's possible of the above? Thank you!
Tracking requirements for Toolbox Can we track high level details of type definitions?
- number of types
- quantity of directive usage
- number of interfaces and unions
- use third party library to calculate complexity of queries so that we can start informing the scale we need to support for the service offering and pricing
- queries count and mutation count To understand how people use these features
Additional tracking Possibly add link to track interest in GraphQL aaS. Want us to host your API for you? Click here to register your interest Publish your API feature coming soon! Click here to register your interest
@tbwiss Can you advise on what's possible of the above? Thank you!
These four are relatively easy to achieve:
- number of types
- quantity of directive usage
- number of interfaces and unions
- Per executed query/mutation: complexity calculation with third-party lib
The "queries and mutation count" will have to be aggregated on the data analysis side. For instance, anonymous entity/user X has executed y queries and z mutations in a given time span. This means in the Toolbox we will track every time an anonymous entity/user executes a query or a mutation (or several of them in one). We actually already get that information with the "complexity calculation with third-party lib" above if the third-party lib can handle mutations.
The additional tracking: Should not be a problem at all! If you think of it as a button to click at least.
Merging this as work on this task has already started