Request edit access
JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.
Apollo Studio Single Field Insights Feedback
The Field Insights Page provides usage and health information about specific fields in your graph. We strive to make our tools as good as they can be, and we sincerely appreciate any feedback you have!
Sign in to Google
to save your progress.
Learn more
* Indicates required question
What is your primary role when working on GraphQL projects? (check all that apply)
*
Backend / GraphQL services (e.g. schema design, resolver implementation, microservice implementation)
Frontend / GraphQL clients (e.g. frontend websites, web apps, mobile apps, writing queries)
Graph Platform (e.g. enabling graph adoption, coordination, training)
Other:
Required
What are you usually trying to do when you visit the Single Field Insights Page in Apollo Studio? (check all that apply)
*
Plan for a Federation-related change (i.e. migration of types / fields between subgraphs ).
Plan for a schema change (i.e. deprecate / remove / change a field).
Plan for an infrastructure change (i.e. capacity planning).
Debug a performance issue.
See which clients are using a field.
Share insights with other team members.
See when a field was first used.
See when a field was last used.
Determine which subgraph a field belongs to.
See how much a field is being used.
See which operations are using a field.
Other:
Required
How useful is the Single Field Insights Page in Apollo Studio?
*
Not useful at all
1
2
3
4
5
Extremely useful
What else would make the Single Field Insights Page more useful to you? (choose up to 8)
*
I want it to load faster / more reliably.
Filter by client.
See latency over time (p50 / p90 etc).
Filter by subgraph.
See recent changes to the field's schema (arguments, deprecation, return type, etc.)
See usage and health for the Type (parent object).
See specific traces to further investigate field latency.
See specific errors for further investigation.
See usage insights for input objects / enum values.
See breakdowns by subgraph.
Other:
Required
Besides Apollo Studio, how else do you gain insights into your graph’s usage & health?
Your answer
Choose the way you'd most like Apollo Studio to fit into your workflow:
As a one-stop-shop for graph observability & telemetry.
As a complementary service to existing telemetry (i.e. integrations with other tools).
I'd prefer to have all of the data in another telemetry tool.
Other:
Clear selection
Next
Page 1 of 2
Clear form
Never submit passwords through Google Forms.
This form was created inside of Apollo.
Report Abuse
Forms
