Monitoring and Observability for all your GraphQL APIs

Gain insights into your API availability and performance

Why do you need an observable system?

Without an observable system, it would be difficult to understand what is going wrong with the system unless you are monitoring for known issues. At any point of time, you should be able to ask any arbitrary question about how your application works.
Metrics involved in queries:
  • TickTime of query and query execution time
  • TickActual query payload / query hash
  • TickResponse status codes of queries/mutations/subscriptions
  • TickGraphQL Server Version
  • TickIP Address from which the query originated


Monitor for Slow Queries

Monitor for Slow Queries

  • Find high latency queries from the dashboard
  • Optimise your database through Explain/Analyze
  • Compare query performance over time
Monitor for Slow Queries
Tracking Errors

Tracking Errors

  • Check and filter responses with “errors” object
  • Debug in dev mode to pinpoint issues
  • Perform regression testing to prevent errors from going into production
  • Enable higher logging level for debugging
Tracking Errors
Distributed Tracing

Distributed Tracing

  • Get a unified view of performance of all components in Hasura
  • Trace requests across database, remote schemas, events and action handlers
  • Track execution time per individual request
  • Support for integration of trace information with APM
Distributed Tracing
Websocket Monitoring

Manage your realtime apps with Websocket Monitoring

  • Track number of websocket connections open
  • Visualize average execution time of subscription workers
  • Monitor open and closed states of a websocket connection
Manage your realtime apps with Websocket Monitoring

Integrations with External Services

Export metrics and operations log to external services
New Relic
Azure Monitor