> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Alarm Overview

> Learn about GPU Cloud alerting capabilities, rule types, notification methods, and alert handling procedures.

GPU Cloud provides alerting capabilities to help you identify resource or service anomalies and send anomaly messages to specified channels through the Notifier. You can use Preset Rules to monitor common anomalies or use PromQL to create Custom Rules.

After accessing the **Alerts** page, you can view custom rules, preset rules, notification channels, and the number of alert events in the past 15 days. You can also configure rules, query events, and manage notifications on the **Custom Rules**, **Preset Rules**, **History**, and **Notifier** tabs. You can also access the **OBSERVABILITY > Alerts** page from the CKS cluster console to view or configure alerts related to cluster O\&M.

## Usage workflow

When using alerts for the first time, we recommend following the steps below for configuration and troubleshooting:

1. Create a notifier to receive alert messages.

2. Select an alert rule based on the monitoring scenario.

   | Scenario | Recommendation |
   | - | - |
   | Monitor common exceptions already covered by the platform | Subscribe to Preset Rules. |
   | Need to use custom PromQL expressions or a custom Active Period | Create Custom Rules. |

3. After enabling the rule, confirm that it is working as expected and is associated with the correct Notifier.

4. After an alert is triggered, view the event status, trigger value, and tag information on the **History** tab, then return to the relevant resource or monitoring metric to troubleshoot the issue.

   ![Alerts homepage](https://mintcdn.com/scitix-adfc65c2/zAestxkyOFggIEE8/gpu-cloud/alarm/media/alarm-custom-rules.png?fit=max\&auto=format\&n=zAestxkyOFggIEE8\&q=85\&s=726e06cc1eb6bceacd5d11dd7ed0d997)

## Alert Rule Types

GPU Cloud supports the following two types of alert rules:

| Rule Type | Description |
| - | - |
| Custom Rules | Configure the Rule Name, Severity, PromQL, execution frequency, Duration, Notifier, and Active Period. Suitable for scenarios requiring custom conditions. |
| Preset Rules | Common alarm rules provided by the platform. You can view and subscribe to them by product. |

## Alert Event Status

On the **History** tab, you can view the current status of alerts. Alert statuses include:

| Status | Description |
| - | - |
| Firing | The alert is still active. |
| Resolved | The alert has been resolved. |

## Alarm Severity

Custom Rules and historical events can use alert severity to distinguish event severity. Alert severity levels include `CRITICAL`, `WARNING`, and `INFO`.

## Alarm Handling Recommendations

After receiving an alert, it is recommended that you first view the rule name, trigger time, duration, trigger value, and label information on the **History** tab. Labels may include information related to the product, region, cluster, resource, or rule, which can help you return to the relevant resource or monitoring metric for further troubleshooting.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.