Getting a good understanding of how your GraphQL server performs and tracking down issues that you might not yet see is difficult with GraphQL. This is because the requests to your GraphQL server are defined by your consumers. With the emergence of OpenTelemetry, we now have tooling to build a great GraphQL cockpit that turns the lights on in GraphQL and shows you exactly which GraphQL requests use what in your infrastructure. The best thing is that OpenTelemetry is an open standard, allowing you to pick and choose tooling and vendors. Let’s explore how we can integrate OpenTelemetry into GraphQL from backend to frontend.