Join us for GraphQL Summit, October 10-12 in San Diego. Use promo code ODYSSEY for $400 off your pass.
Launch GraphOS Studio

Operation metrics in GraphOS

Understand your supergraph's performance

Once you've configured your graph to send operation metrics to GraphOS, you can view them in Studio. In addition, you can configure your s to include resolver-level traces in their responses to your , which are then also reported to .

Viewing metrics

You can visualize metrics in GraphOS Studio, from any 's Operations page:

Apollo Studio metrics view

This page gives you a helpful overview of your 's recent performance, including:

  • The rate of requests sent to your
  • Your 's p95 service time
  • Your 's error rate

The page displays overall values for these metrics, along with values broken down by . You can click an operation name to view more detailed information for it.

Resolver-level traces

If you enable trace reporting in your s, Studio can also display -level trace information about each :

Traces tab for an operation in Apollo Studio

Shown above, the Traces tab for an provides a breakdown of timing and error information for each field that's resolved as part of that . This helps you identify opportunities to improve your 's overall performance by optimizing whichever s currently act as a bottleneck.

Enabling traces

To enable federated trace reporting in your s, consult the documentation for the GraphQL server library your subgraph uses.

Not all subgraph-compatible libraries support federated trace reporting.

To confirm the support status for your library, check its FEDERATED TRACING entry in Federation-compatible subgraph implementations.

If your s use Apollo Server with the @apollo/subgraph library, federated trace reporting is enabled by default. You can customize Apollo Server's trace reporting behavior with the inline trace plugin.

Field usage
Edit on GitHubEditForumsDiscord