> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/event-management.md).

# Event Management

Any change observed and detected within your organization is an event.

The primary objective of the event management module within ITIL is to detect all changes or activities within the infrastructure, observe for anomalies and raise the alarm, if necessary. Events are Infraon's way of active and passive monitoring of

* CI items like laptops, desktops, etc.,
* Software licensing and performance
* Application performance
* Server performance

Monitoring the status and availability of items is part of active monitoring, while detection and correlation of operational alerts based on the configured thresholds and triggers are part of passive monitoring.

Infraon's Event Management module enables users/organizations to achieve their goals through the below steps:

* There are constant changes in the infrastructure. Ideally, a user's login, upgrade of software/hardware, or regular maintenance are all events. However, these are not events that need to be notified or taken action upon. When there is a change in the server's performance or availability, it needs to be reported immediately. Infraon extracts the necessary data from the happenings of the infrastructure and detects 'events that need attention on occurrence.
* These anomalies or changes are run through the default thresholds and categorized as basic, informational, major, or performance.  Thresholds can be sorted as minor, major, or critical. Refer to the Thresholds section for details.
* Anomalies and changes are categorized and reported as events.
* Technicians or NOC users can use these events to perform necessary actions.

{% hint style="info" %}
**Note:** If triggers are configured for events, a notification is triggered either at the event's occurrence or after correlating.
{% endhint %}

Refer to the [Events](/infinity/user-guide/event-management/events.md) section for more details.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infraon.io/infinity/user-guide/event-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.