In this context GraphQL should be seen as a higher level protocol than HTTP. Standard HTTP mechanisms for evaluating availability still work, but may not provide the full picture, while still being valid. Still a non-2xx response code for HTTP is a valid indicator or error.

What you are asking is similar to trying to evaluate availability of HTTP just by relying on TCP metrics (lower level transport protocol).

There isn't a well established mechanism that is de-facto standardized. What makes it even tricky is that GraphQL can also work over other transports (WebSocket or MQTT).

If you are using a popular off the shelf GraphQL server likely it already has some metrics that it provides.

If you are using a custom implemented the following custom metrics could indicate issues:

• Percentage of responses including errors

• Average number of errors in responses (there may be more than one)