Alerts
On this page
Overview
Working alongside historical monitoring, the alerting feature actively notifies you about the changing state of a workspace.
Prerequisites
To use alerts with your workspace, SingleStore 7.
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 |
|
|
For this number of minutes |
5 |
5 |
10 |
||||
|
Memory Utilization |
Memory utilization is greater than |
95% |
90% |
80% |
How long that the workspace’s memory has been allocated over the specified maximum threshold |
The workspace is using more memory than expected |
|
|
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 |
The workspace is using more disk space than expected and warrants further investigation |
|
|
For this number of minutes |
5 |
5 |
10 |
||||
|
Availability |
Infrastructure is unavailable |
N/A |
N/A |
N/A |
A workspace may be either offline, or online but unreachable |
Whether a workspace is available |
|
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.
Enable Alerts
Alerts for a workspace group can either be enabled or disabled, and are enabled by default when a new workspace group is created.
To enable or disable alerts for a workspace group:
-
Click the Alerts link in the left nav.
-
Select the desired workspace group from the drop-down at the top of the page.
-
Click the Enable Alerts switch.
Edit Thresholds and Alerting Level
Once alerts are enabled for a workspace group:
-
Click 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.
-
Click the Edit icon next to this workspace.
-
Click the desired alert type’s severity level to enable it and set the desired thresholds.
Last modified: February 26, 2024