> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/4.2/usage/events.md).

# Events

This page describes the events available in the WEKA system and how to work with them.

WEKA events provide essential information about the WEKA cluster and customer environment. Cluster and customer operations and changes in the background can trigger these timestamped events. They may convey information, signal a system issue, or report a previously resolved problem.

The WEKA cluster sends all events to a predefined central monitoring system, WEKA Home or Local WEKA Home. The GUI displays the events retrieved from the central monitoring system.

![System events](https://1970823310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNqDzxyFrTFrLD641p0iH%2Fuploads%2FawyzFJ8vd5UYoVxZPIOS%2Fwmng_events_overview.png?alt=media\&token=c661cba4-c50d-438c-89c7-507d1cecdfe2)

### Events triggered by alerts

In the monitoring and alerting system, alerts are closely tied to specific events, providing valuable insights into problematic states' occurrence and underlying causes. The events associated with alerts encompass a comprehensive log, including triggered, cleared, and continuous alerts.

The following processes ensure systematic and efficient handling of events triggered by alerts:

* Alerts that are active for at least 1 minute generate an `AlertTriggered` event. Once they are inactive for at least 1 minute, an `AlertCleared` event is generated with details, including the alert type, title, and description.
* Every 30 minutes, all active alerts are logged as part of an `AlertContinuousEvent` with details, including the alert type and the entry count.
* These events are internal with severity level DEBUG and category ALERTS.

**Related topics**

[Manage events using the GUI](/4.2/usage/events/events.md)

[Manage events using the CLI](/4.2/usage/events/events-1.md)

[List of events](/4.2/usage/events/list-of-events.md)

[WEKA Home - The WEKA support cloud](/4.2/monitor-the-weka-cluster/the-wekaio-support-cloud.md)


---

# 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.weka.io/4.2/usage/events.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.