# Notification Triggers

This is a complete list of every alert that MaaS can trigger, organized by severity level. These are the notifications you will receive based on the severity levels you enable in your [Get Notifications](/maas-documentation/notifications/media-types.md) settings.

***

## Disaster

| Alert                   | Scope  | Description                                                             |
| ----------------------- | ------ | ----------------------------------------------------------------------- |
| No Status Data Received | Global | No data from TMedia API for 125+ seconds — complete monitoring blackout |

***

## High

| Alert                    | Scope             | Description                                |
| ------------------------ | ----------------- | ------------------------------------------ |
| Host Down                | Per Host          | TMedia host server is offline              |
| Hardware Unit Down       | Per Adapter       | Physical media gateway card is offline     |
| M2UA Peer Down           | Per M2UA Peer     | SS7 signaling peer connection lost         |
| NAP Registration Failed  | Per NAP (SIP)     | SIP trunk lost registration                |
| MaaS Call Limit Exceeded | Global            | Active call legs exceed MaaS service limit |
| License Limit in Danger  | Global            | Call legs critically close to license max  |
| File System 95%          | Per Host          | Disk space critical (>95%)                 |
| RAM Usage 95%            | Per Host          | Memory critical (>95%)                     |
| App CPU 95%              | Per Application   | Application CPU critical (5-min avg >94%)  |
| Ethernet Port Down       | Per Ethernet Port | Physical Ethernet port is offline          |

***

## Average

| Alert                       | Scope           | Description                                |
| --------------------------- | --------------- | ------------------------------------------ |
| File System 80%             | Per Host        | Disk space elevated (>80%)                 |
| App CPU 80%                 | Per Application | Application CPU elevated (15-min avg >79%) |
| TDM Line Bouncing           | Per E1/T1 Line  | More than 4 state changes in 1 hour        |
| Scheduling Problem          | Per Host        | Host has scheduling problems               |
| Firewall DDoS Alarm         | Per Host        | Firewall detected potential DDoS attack    |
| Firewall Scheduling Problem | Per Host        | Firewall has scheduling problems           |
| Dump File Detected          | Per Host        | Core or crash dump file present on disk    |

***

## Warning

| Alert                       | Scope   | Description                             |
| --------------------------- | ------- | --------------------------------------- |
| NAP Down                    | Per NAP | NAP availability dropped to 0%          |
| NAP Congestion              | Per NAP | NAP is experiencing congestion          |
| Nearing Call License Limit  | Global  | Call legs over 80% of licensed capacity |
| Backup Configuration Failed | Global  | Configuration backup process failed     |

***

## Information

| Alert                               | Scope           | Description                              |
| ----------------------------------- | --------------- | ---------------------------------------- |
| TDM State Change                    | Per E1/T1 Line  | TDM line state changed                   |
| RAM Usage 80%                       | Per Host        | Memory elevated (>80%)                   |
| Reboot Required                     | Per Host        | Host requires a reboot                   |
| Core Application Switchover         | Per Application | Core App HA state changed Active/Standby |
| MaaS Call Limit over 90%            | Global          | Call volume approaching MaaS limit       |
| Active Configuration Changed        | Global          | Active configuration change detected     |
| Configuration Successfully Received | Global          | Configuration backup completed (nightly) |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://prosbcdocs.telcobridges.com/maas-documentation/notifications/trigger-actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.