DEV Community

loading...
Cover image for TRACING YOUR GRAPHQL API (How GitHub Does It)
Bytesized Code

TRACING YOUR GRAPHQL API (How GitHub Does It)

Kristian Freeman
building mailing list hackers, bytesized code, and lots of side projects. developer advocate for cloudflare workers
・2 min read

This video is a talk from Byteconf GraphQL 2020, a free, live-streamed GraphQL conference that aired on January 31st, 2020. Visit our website to sign up for the Byteconf GraphQL "swag bag", a free downloadable resource with everything you need to get started with GraphQL, as well as info about future Byteconf events!

There are several tracing tools available publicly and privately for looking into execution time of GraphQL queries. These are super useful and key for integrators writing queries. But as API owners we also need to know how our API is being used. This is important for making deprecations, for choosing where we might want to optimise, understanding general usage patterns and even answering support queries. It's also key to not slow down execution gathering that data. To that end GitHub has several tools and relies heavily on data pipelines. We track parse and execution errors, which objects API queries touch, and more. All of this is beneficial when ensuring the smooth running of the API. This talk will focus on our experiences doing this, what data we've found useful, and how you might want to approach this in your APIs.

Thanks to Claire Knight who presented this talk at Byteconf GraphQL 2020!

If you enjoyed the video, give it a thumbs-up, and subscribe to our channel for more web dev content every week. We also have a newsletter where we send out what's new and cool in the web development world, every Tuesday – join here!

Discussion (0)