# Alerts

## Overview

Working alongside [historical monitoring](https://docs.singlestore.com/cloud/user-and-workspace-administration/workspace-health-and-performance/historical-monitoring.md), the alerting feature actively notifies you about the changing state of a workspace. Alerts allow you to proactively remediate any issues that could adversely affect both the workspace and the applications that depend on it.

## Prerequisites

To use alerts with your workspace, SingleStore 7.3 or later is required.

## Pre-Configured Alert Types

Pre-configured alert types are included that can be configured by:

* Individual workspace(s), where alerts are triggered for the specified workspace(s)
* Workspace group, where alerts are triggered for all workspaces in the specified workspace group

These pre-configured alert types, most of which can be customized, have the following components:

* A *trigger condition* (alert type) refers to what’s being monitored.
* Each trigger condition has a single *condition* that can have up to three *severity levels* enabled: Critical, Warn, and Info.
* Each severity level has configurable parameters that, when taken together, constitute a *threshold*.
* When a severity level's threshold is reached, an email alert is sent to the list of subscribers.

  The one exception is the Availability alert type, which has a preset threshold that cannot be customized. As SingleStore continuously monitors the SingleStore Helios infrastructure, availability alerts are first routed to, and evaluated by, SingleStore. If the issue cannot be readily resolved, an Availability alert is sent to the customer. While this alert may arrive outside of the expected notification window, please know that SingleStore is already working to resolve the issue.

The following table summarizes the available pre-configured alert types, what they measure, what an alert could mean, and the preset thresholds.

| **Trigger Condition**(Alert Type)   | **Condition**                        | **Critical** | **Warn** | **Info** | **What it measures**                                                                        | **What it could mean**                                                                | **Alert Method** |
| ----------------------------------- | ------------------------------------ | ------------ | -------- | -------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ---------------- |
| CPU Utilization                     | Core CPU utilization is greater than | 95%          | 90%      | 80%      | A workload is beginning to slow due to lack of available CPU cycles                         | How long at least one CPU core has been running over the specified maximum threshold  | Email            |
| For this number of minutes          | 5                                    | 5            | 10       |          |                                                                                             |                                                                                       |                  |
| Memory Utilization                  | Memory utilization is greater than   | 95%          | 90%      | 80%      | How long that theworkspace’s memory has been allocated over the specified maximum threshold | Theworkspaceis using more memory than expected                                        | Email            |
| For this number of minutes          | 5                                    | 5            | 10       |          |                                                                                             |                                                                                       |                  |
| Persistent Cache (Disk) Utilization | Persistent cache is greater than     | 95%          | 90%      | 80%      | How long the disk has been allocated over the specified threshold                           | Theworkspaceis using more disk space than expected and warrants further investigation | Email            |
| For this number of minutes          | 5                                    | 5            | 10       |          |                                                                                             |                                                                                       |                  |
| Availability                        | Infrastructure is unavailable        | N/A          | N/A      | N/A      | Aworkspacemay be either offline, or online but unreachable                                  | Whether aworkspaceis available                                                        | Email            |

The following table specifies the alerting frequency for each severity level.

| **Severity Level** | **Alerting Frequency** |
| ------------------ | ---------------------- |
| Critical           | 1 hour                 |
| Warn               | 6 hours                |
| Info               | 24 hours               |

For example, if you receive a critical CPU Utilization alert for a given workspace, you will receive the next critical CPU Utilization alert an hour later. During this one-hour interval, all other critical CPU Utilization alerts will be suppressed for this workspace.

## Enable Alerts

Alerts for a workspace group can either be enabled or disabled. They are enabled by default when a new workspace group is created. When alerts are enabled, the Persistent Cache Utilization alert type is also enabled by default, as are the alert types that have been enabled by the user.

To enable or disable alerts for a workspace group:

1. Under **Monitoring**, select **Alerts** in the left navigation.

2. Select your workspace group from the list at the top of the page.

3. Select the **Enable Alerts** switch.

## Edit Thresholds and Alerting Level

Once alerts are enabled for a workspace group:

1. Select the checkbox next to the desired workspace(s) to enable additional alert types for it.

   You may also bulk-edit multiple workspaces by selecting additional or all workspaces.

2. Select the **Edit** icon next to this workspace.

3. Select the desired alert type’s severity level to enable it and set the desired thresholds.

***

Modified at: May 11, 2026

Source: [/cloud/user-and-workspace-administration/workspace-health-and-performance/alerts/](https://docs.singlestore.com/cloud/user-and-workspace-administration/workspace-health-and-performance/alerts/)

(An index of the documentation is available at /llms.txt)