> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-ims-en/estadisticas-monitorizacion-y-alarmas/alarmas-descripcion-general.md).

# Alarms: overview

Currently, monitoring sessions requires constantly consulting the statistics files or the Log file and distinguishing between the messages that indicate the correct progression of the sessions and those that report a malfunction in any of them.

The Alarm Management subsystem will facilitate the detection of possible errors in each of the phases of data presentation and transmission, notifying, if desired, any type of incident.

It will also be possible to report the incidents detected in application processes related to a presentation session, such as the prior and subsequent user programs. (See Annex).

The system will implement the complete path from the moment the incident occurs until the notification is received by the user, but it will also be integrated with existing process control systems such as “TIVOLI” or others.

For alarm notification, the messages handled in Editran/E will be used as a basis and the following methods will be used:

* External manager.
* e-mail:
  * through the zOS SMTP server.
  * through the program *sendmail* from the zOS UNIX partition.
  * through an external server.
* Mobile alarms through an external server.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-ims-en/estadisticas-monitorizacion-y-alarmas/alarmas-descripcion-general.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.