Introducing Alerts for Hasura Cloud

Although Hasura Cloud takes care of the performance, security and reliability requirements of your API layer, many issues are out of our control:

• Status of remote data sources and external webhooks that are hosted on your infrastructure
• Performance of database query and webhook invocations
• Logic errors

Today, we are announcing an Alerting system for Hasura Cloud that proactively notifies you about important events and incidents in your Hasura infrastructure. It ensures that you are informed about critical changes, potential performance, and reliability issues as soon as possible.

Faster incident resolution

By receiving timely alerts, users can quickly identify incidents and take immediate action to address them. This reduces the time it takes to detect and respond to issues, minimizing their impact on system performance and user experience.

Improved reliability

By promptly detecting and resolving incidents, Hasura Alerts help improve overall reliability. Users can proactively address potential issues before they impact end-users, resulting in enhanced system stability and user satisfaction.

Performance issue detection

Performance issues can arise within or downstream from Hasura infrastructure. With alerting, users can monitor important performance metrics and receive notifications when thresholds are breached. This allows for timely intervention and optimization, ensuring optimal system performance.

Root cause identification

Incidents often have downstream causes that originate from outside the Hasura infrastructure itself. Proactive alerting helps users quickly trace these issues to their root causes, enabling more efficient troubleshooting and resolution.

Abnormal error rate

Errors have a direct impact on end-user experience and can cause critical loss for your business. It requires the engineering team to quickly respond to solve the issue. Hasura Cloud supports error rate alerts for GraphQL operations, Event, and Cron triggers.

High latency

Even though the functionality of your API works as expected, slow response times also cause bad user experience and potential timeout errors. Hasura Cloud also supports these alerts for GraphQL operations, Event, and Cron triggers.

Data source status

The health of remote data sources is important. Hasura can’t work if remote data sources are unavailable. Postgres is natively supported by Hasura with health checks and concurrent connection metrics, as well as alerts for this data source.

Schema changes

This alert rule helps you quickly act with inconsistent metadata issues, or just get notifications about metadata changes by someone in your team.

The alert message contains general information that explains what’s going on in your project, including:

• The name of the alert.
• Description of the alert rule, and why it was triggered, e.g. The error rate exceeds 50 percent.
• Time when the alert was triggered.
• Alert status. The alert is sent when it happens or is resolved. The severity of the triggered status can be critical or warning.

The email below is an example of an alert message. Concurrent alerts are grouped in a single email to avoid spamming your inbox. However, some content can be different depending on special rules, for example, Schema registry alerts

At this moment, Hasura Alerts support email and Slack notifications. You will receive alert emails like below if enabling the feature.

To enable alerts, head to Project Details -> Alerting tab. On this page, you can:

• Enable or disable the feature to stop receiving alert messages.
• Specify alert rules that are fit for your project.
• Add email addresses and integrate a Slack application to receive alert messages.

Hasura Alerting is currently. Stay tuned to Hasura's blog for upcoming updates.Interested in Hasura Alert? You can give it a try on Hasura Cloud.

If you have feedback, request new alert rules, channels, or just ask questions about this feature, join Hasura engineers and community on our Discord or GitHub Discussions.