---
title: "Events"
description: "The platform-wide activity log: device, tag, model, component, and system events with acknowledgement, muting, and cascade grouping"
source_url: https://ai-ops.com/docs/events/introduction
---

# Events

The Events page is the platform-wide activity log and audit trail. Every meaningful action in Koios records an event: a device connecting or failing, a tag going into alarm, a model starting inference, a component throwing an error, a user changing a setting, or a service reporting its health. Open **Events** from the sidebar to see the full stream, newest first.

Each event captures what happened, which service reported it, which entity it relates to, and who triggered it (a user or an API client). Configuration changes also record the exact field values before and after.

## Event Types

Every event has a type that sets its severity and color. Filter the list by one or more types.

| Type | Meaning |
|------|---------|
| **Information** | Normal activity worth recording, no action needed |
| **Success** | An operation completed successfully (connected, started, restored) |
| **Warning** | A condition that may need attention but is not yet failing |
| **Alarm** | A monitored value crossed an alarm threshold |
| **Error** | An operation failed (connection lost, inference error, validation failure) |
| **Configuration** | A user or client changed a setting; carries the field-level before and after values |
| **Action** | A user or client triggered an operation (enable, disable, reconnect, acknowledge) |

## Event Sources

The source is the service that recorded the event. Filter the list by one or more sources.

| Source | Records events for |
|--------|--------------------|
| **WebApp** | Configuration changes, user and client actions, backup and restore |
| **Data Collector** | Device connections, tag reads, protocol errors |
| **Prediction Engine** | Model inference, binding validation, execution failures |
| **Mapping** | Data transformation and normalization |
| **Performance Monitor** | CPU, memory, and disk alarms |
| **Heartbeat** | Service health and availability checks |
| **Component Engine** | Component instance execution and errors |
| **Expression Evaluator** | Calculated tag and expression evaluation |
| **None** | Events with no specific originating service |

## The Event List

The list shows one row per event with these columns:

| Column | Contents |
|--------|----------|
| **Type** | Severity badge with icon |
| **Time** | Relative time; hover for the exact timestamp |
| **Message** | The one-line summary |
| **Entity Type** | The kind of related entity (device, tag, model, and so on) |
| **Entity** | The name of the related entity |
| **Source** | The service that recorded the event |
| **User** | The user or API client responsible, if any |
| **Acknowledged** | A check mark when the event has been acknowledged |

Use the column filters to narrow by type, source, entity type, or a time range, and type in the message filter to search event text. Sort by time, type, source, or message. The list loads more rows as you scroll.

By default the list shows only **unacknowledged** events and hides events from muted entities. Use **View all** to include acknowledged and muted events. When new events arrive while you are scrolled down, a **new events** pill appears at the top; click it to jump back and load them.

> [!NOTE] Seen is per-user, acknowledged is shared
> Whether an event has been *seen* is tracked per user and drives your popup notifications. Whether an event is *acknowledged* is shared across everyone, so acknowledging clears it from the default view for all users.

## Event Detail

Click any row to open the detail drawer. Depending on the event, it shows:

| Section | Contents |
|---------|----------|
| **Message** | The full summary line |
| **Detail** | Extended context, such as an error traceback |
| **Related Entity** | A link to the device, tag, model, or other entity the event is about |
| **Time** | Relative and absolute timestamps |
| **User / API Client** | Who triggered the event, linking to their profile or client |
| **Field Changes** | For configuration events, each changed field with its previous and current value |
| **Parent Event / Cascade** | Links to related events when the event is part of a group |

## Acknowledging Events

Acknowledging an event marks it as handled and removes it from the default unacknowledged view. Acknowledge a single event from its detail drawer, select several rows and acknowledge them together, or use **Acknowledge all** to clear every unacknowledged event at once.

Acknowledging requires the **Acknowledge events** permission. Without it, the acknowledge controls are visible but disabled with a tooltip explaining why. See [Roles & Permissions](https://ai-ops.com/docs/system/roles-permissions.md) to grant it.

## Muting

Muting suppresses your popup notifications without hiding events from the log. Muting is per-user, so it never affects what your teammates see.

- **Mute an entity**: from an event's detail drawer, mute the related device, tag, or model for a set duration or indefinitely. Muted entities are also hidden from the default event view.
- **Mute all notifications**: silence every popup notification for a duration or indefinitely from the notification bell in the header. Events still record; only the popups stop.

Manage these from the notification settings, reachable via the bell icon in the Events page header.

## Related Events

When one root cause produces many events, such as a bulk enable touching hundreds of tags or a device failure cascading to its tags, Koios groups them. The originating event becomes the **root**, and the rest become its children.

The list collapses each group to its root row and shows a **+N related** badge with the child count. Use the **Expand** toggle to reveal child events inline. Open a root event to see the full **Event Cascade** timeline, drill into any child, and step back to the parent. **Acknowledge All** on a root acknowledges the root and every child together.

## Real-Time Notifications

New events raise popup notifications in the corner of the screen for events you have not yet seen. During a sustained burst, Koios consolidates the individual popups into a single storm notification with a live counter, so a flood of events never buries the interface. The counter keeps climbing until activity quiets down. The event list itself is never collapsed; every event is always recorded and browsable.

## Retention

Events are kept for a configurable number of days (90 by default) and older events are deleted automatically. Adjust the **Event Retention** period in [Data Retention](https://ai-ops.com/docs/system/retention.md).

## What's Next

- [Data Retention](https://ai-ops.com/docs/system/retention.md): control how long events and other history are kept.
- [Roles & Permissions](https://ai-ops.com/docs/system/roles-permissions.md): grant the Acknowledge events permission and control access.