GraphQL distributed tracing

Helios' instrumentation of GraphQL enables developers to visualize, troubleshoot and test their applicative flows that include GraphQL operations.

GraphQL APIs are supported out of the box, as the underlying queries are simple HTTP requests.

Below are a few examples of how to leverage E2E observability in Helios when using GraphQL across your microservices.

Tracing & visualization

A GraphQL endpoint will show as a list of all the observed GraphQL queries and mutations. For example, the following operations represent a single GraphQL HTTP route:

HTTP attributes and data are available for GraphQL, just like other HTTP based operations:


Operation details for GraphQL

Notice that the request will be either a query or a mutation, depending on whether you're getting or changing data. The response will include the retrieved data, structured according to the corresponding query.

Flow replay

It's easy to replay flows triggered by GraphQL requests directly from the traces in Helios.


1-click to generate flow replay code

Test generation

GraphQL operations can be included in end-to-end tests generated in Helios. GraphQL spans in any trace can be configured and set as validation checkpoints when generating test code.


E2E tests including GraphQL operations configured as validation checkpoints


Helios is a a dev-first observability platform that helps dev and ops teams shorten the time to find and fix issues in distributed applications. Built on OpenTelemetry, Helios provides traces and correlates them with logs and metrics, enabling end-to-end app visibility and faster troubleshooting.

Get started for free with Helios to simplify and enrich OpenTelemetry distributed tracing.