# Event Severity

{% hint style="info" %}
Please note that if you need assistance to go to Things Menu, [you may check out this guide on how to go to Thing Menu Events section.](https://docs.monogoto.io/guides/thing-menu-events)
{% endhint %}

Event Severity describes the attention level that the Events should receive.

![](/files/fbguL7ayduce6Rw2Bm90)

{% hint style="info" %}
Please note that Event Severity main purpose is usage with Alerts. In Alerts you can set the Severity level, thus seeing the most important Event types with higher Severity than common Events.
{% endhint %}

### Event Severities table

| Event Severity example | Description                                                                                                                                   |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Info                   | <p>Severity that is most common and is present in almost all Events<br>Also, can be seen in Alerts that are set to use this Severity type</p> |
| Warning                | <p>Rare Event Severity level, but can be seen in some Events</p><p>Also, can be seen in Alerts that are set to use this Severity type</p>     |
| Error                  | Only seen in Alerts, that are set to use this Severity type                                                                                   |
| Critical               | Only seen in Alerts, that are set to use this Severity type                                                                                   |


---

# 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://docs.monogoto.io/advanced-console/platform/thing-menu-events-explained/event-severity.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.