[Yandex Cloud documentation](../../../index.md) > [Monium](../../index.md) > Alerts > Concepts > Annotation # Annotation Annotations enable you to save additional information during alert calculation. The annotation name and value are transmitted when sending alert notifications to the `Email` and `Telegram` [channels](notification-channel.md). Annotations support [mustache templates](http://mustache.github.io/): you can use them to add alert parameters to your annotations. Annotation examples: ```text Alert `not_var{{alert.name}}` is in not_var{{status.code}} state ``` ```text Used disk space is not_var{{pointValue}} Gbs, expected less than not_var{{alert.warnThreshold}} Gbs ``` Complete list of alert parameters available in annotations: Field | Description ---------|---------- **alert.projectId**
**alert.folderId**
**alert.id**
**alert.name**
**alert.state**
**alert.createdAt**
**alert.updatedAt**
**alert.createdBy**
**alert.updatedBy**
**alert.version**
| Shared alert parameters **alert.queries**
**alert.queryToCheck**
**alert.thresholdType**
**alert.comparison**
**alert.alarmThreshold**
**alert.warnThreshold** | Threshold alert queries and comparison parameters **fromTime** | Beginning of the time interval in which the alert is calculated. This is a string in ISO8601 format, such as `2017-09-07T11:30:00Z`. **toTime** | End of the time interval in which the alert is calculated. This is a string in ISO8601 format, such as `2017-09-07T12:00:00Z`. **pointValue** | Metric value as of alert calculation. **status.code** | Alert status: `OK`, `ALARM`, `WARN`, `NO_DATA`, or `ERROR`. **isOk**
**isWarn**
**isAlarm**
**isNoData**
**isError** | Boolean variables that can be used to find out the alert status. Here is an example:

`{{#isAlarm}}Disk usage is too high!{{/isAlarm}}`
`{{^isAlarm}}Disk usage is ok.{{/isAlarm}}`