Monitor messages and alerts

Monitor system messages and alerts across your clusters, and set who gets notified by email.

RisingWave Cloud provides a centralized Messages & Alerts interface to view and manage all system notifications for your clusters. It helps you quickly identify issues, understand their impact, and ensure the right people are notified in time. You can review notifications, configure email recipients, and control which supported alert rules can send notifications for each cluster.

Notification list

In RisingWave Cloud, click Messages in the main navigation, then select the Inbox tab. It lists notifications across your organization.

You can filter notifications by two main criteria:

• Severity levels: Alerts are classified by severity to help prioritize your response.

  Severity levels	Description	Example
  Critical	Issues requiring immediate attention to avoid service disruption or data loss.	Streaming job failure, node outage.
  Warning	Non-blocking issues that may escalate if unaddressed.	High memory usage, compaction delays.
  Info	Informational updates that do not indicate a problem.	Customer service contact changed.

• Function categories: Alerts are classified by the relevant system component or function.

  Category	Description
  Service Health	Status and availability of core services.
  Streaming	Data pipeline performance and processing errors.
  Compaction	Storage compaction schedules, delays, or failures.
  Cluster operations	Cluster-level changes, deployments, or failures.
  Billing	Usage thresholds, billing errors, and payment issues.
  Other	General informational messages.

Alert settings

To configure who receives alerts, click Messages in the main navigation, then select the Alert settings tab.

Email recipients

You can manage the list of email addresses to receive alert notifications.

• Default recipient: The email address associated with your login is added as a recipient by default but can be deselected.
• Add a recipient: Click Add new email, enter the address, and confirm.
• Configure alerts: For each recipient, specify the alert severity to receive: Critical only, Warning only, or Critical and Warning.
• Test notifications: Select one or more recipients and click Test notification to verify email delivery.
• Remove a recipient: To remove a recipient, hover over their entry and click the delete icon.

Below is an email example sent to recipients:

Manage alert rules

Alert rule enablement is configured separately for each cluster. Supported alert rules are enabled by default.

Manage alert rules for a cluster

To enable or disable an alert rule:

1. In the RisingWave Cloud console, open a cluster.
2. In the cluster navigation, select Alert Rules.
3. Optional: Search by rule name or key, or filter the list by severity and function category.
4. Use the switch next to a rule to enable or disable it. RisingWave Cloud saves the change immediately.

The page shows how many supported rules are currently enabled for the cluster.

Disabling an alert rule suppresses new RisingWave Cloud notifications and notification emails generated by that rule for the selected cluster. It does not remove existing notifications, and it does not stop the underlying cluster condition from being evaluated.

Recipient settings and alert rule enablement serve different purposes:

• Alert Rules controls which supported rules can generate new notifications for a cluster.
• Email recipients controls who receives email for enabled alerts.

You need a role with permission to update tenant-related resources for the selected cluster. The built-in OrganizationAdmin and ProjectAdmin roles include this access. For details, see Role-based access control.

Alert playbooks

Alert playbooks are provided to guide you through effective incident response. Each playbook details an alert’s description, common triggers, and provides step-by-step instructions for diagnosis and resolution.

For detailed guidance, see Alert playbooks.

Third party integration

These integrations allow you to automatically create incidents or send notifications to third-party systems when alerts are triggered. By routing email alert notifications to these platforms, you can streamline incident response and ensure your team is promptly notified through your preferred tools. Below are guides for some common integrations:

• PagerDuty
• Slack