/GraphQLConf 2025

-

Amsterdam, Netherlands
Back to Schedule

Aditi Rajawat, Rama Palaniappan

200 Is Not OK: Strategies for Tracing Partial Responses with GraphQL Observability

-
Skyline B-C - Level 21
BackendSession Presentations

Aditi Rajawat

Software Engineering Manager, Intuit

Aditi is an Engineering manager at Intuit leading GraphQL API Platform team, who transitioned into this role the current year from Staff Software Engineer. She has experience of 9 years in the software industry and enjoys working on distributed software systems. She is driving GraphQL adoption at Intuit with focus on improving developer productivity and holding a high bar for operational excellence of GraphQL runtime. Recently, she is also building a new habit to read books in her free time.

Rama Palaniappan

Principal Engineer, API Platform Team, Intuit

Rama Palaniappan is a Principal Engineer at Intuit. Rama has extensive experience in building scalable and reliable systems, and has been instrumental in the design and development of Intuit's API pla

GraphQL is agnostic to the transport layer. Almost all out of the box observability tooling is tailored to REST/HTTP APIs. Major observability challenge with GraphQL over HTTP is the support of partial response and HTTP status with 2XX may have failed. GraphQL Gateway generally fans-out one incoming request to one or many outgoing subgraph requests. It is essential to monitor each subgraph and the GraphQL gateway’s metrics and also to trace a single request across the network stack. This talk will cover how Intuit is reducing Mean Time to Detect (MTTD) and Mean Time to Recover (MTTR) for GraphQL APIs, by capturing Failed Customer Interactions, Golden Signal to determine gateway and subgraph’s health, latency, error rate and other related metrics. This talk will also cover open tracing and logging for GraphQL APIs.