> ## 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.

# View Alert History

> View the alarm overview in Siverse, filter historical alerts, and review alert delivery methods, delivery results, and raw details.

The alarm overview lets you review historical alert delivery records. Filter by alert name, severity, and time range to check whether an alert was triggered and delivered, and whether the delivery result meets expectations.

## Historical Data Scope

The alarm overview is a read-only query entry point and cannot be used to create or modify alert subscriptions. Whether an alert appears in the overview usually depends on the following process:

1. A platform event or metric meets the trigger conditions.
2. An alert matches a subscription.
3. The alert is delivered to the configured targets.
4. Historical alert and delivery records are generated.

If the notification target test is sent successfully but no corresponding actual alert appears in the alarm overview, first confirm whether the alert conditions were actually triggered and whether the subscription scope matches the target object.

## View Historical Alerts

1. Go to **Alarm > Alarm Overview**.
2. Filter records by alert name, alert severity, or time range.
3. Click **Search**.
4. In the list, verify the alert source, severity, trigger time, delivery method, and delivery result.

When reviewing the results, focus on the following information:

| Troubleshooting Goal | Key Information | Recommended Action |
| - | - | - |
| Confirm whether an alert occurred | Alert name, severity, and trigger time. | If no record is found, first check whether the alert subscription is enabled, whether the alert type is correct, and whether the narrowed scope covers the target object. |
| Confirm whether delivery was successful | Delivery method, delivery result, and failed notification targets. | If delivery fails, check whether the notification target is enabled, whether the **Endpoint** is correct, and test sending again. |
| Confirm whether the alert matches the expected object | Region, cluster, owning user, resource object, and details-page link. | If the object does not match expectations, return to the alert subscription and check the filter criteria. |
| Confirm whether the receiving end can view the message | Delivery result and receiving-end status. | If the platform shows successful delivery but the receiving end does not see the message, check the phone number, group bot, external system permissions, or message filtering rules. |

## View Original Details

In the **Actions** column of an alert record, view the details to verify the original alert information.

Resource-related alerts may include a resource name, order number, instance specification, utilization rate, or remaining days. The displayed information varies by alert type; refer to the actual details.

## Troubleshooting Missing Alerts

If the receiving end does not receive the alert, check the following in order:

1. In **Alarm Overview**, search by time range and alert name to confirm whether historical records were generated.
2. If no records are found, check whether the alert subscription is enabled, whether the correct alert type is selected, and whether the narrowed scope covers the target object.
3. If records exist but delivery fails, check whether the notification target is enabled, whether the **Endpoint** is correct, and test sending again.
4. If records exist and delivery succeeds but the recipient does not receive the message, check recipient permissions, phone numbers, group bots, external systems, or message filtering rules.
5. If alerts are merged or not sent immediately, check the group aggregation and quiet periods in the subscription or global noise control rules.

## Related Documentation

* [Create alarm subscriptions](/siverse/alerts/create-alert-subscriptions.md)
* [Manage alert notification targets](/siverse/alerts/manage-alert-notification-targets.md)


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