---
title: Events Log
description: The events log records all key system events, providing transparency and control over user actions.
weight: 3
---

import Image from '@/components/docs/Image.astro';
import Alert from '@/components/docs/Alert.astro';

The **"Events Log"** section (located in the **"Administration"** section) records all key events in the system, providing transparency and control over user actions.

<Alert type="warning">Only the **Platform Administrator** has access to the log.</Alert>

Logging allows you to:

- Track data changes (creation, editing, deletion of objects).
- Analyze unauthorized access attempts.
- Restore the history of operations when errors occur.

## Log structure

The log window contains the following fields:

1. **Logged type** — object category (e.g. "Metering unit", "User").
2. **User** — account that performed the action.
3. **Logged action** — operation type (authorization, creation, modification).
4. **Metering unit ID** — identifier of the metering unit.
5. **ID of the logged object** — identifier of the object to which the action was applied.
6. **Changes** — details of the changes made (old and new value).
7. **Address** — IP address or network name of the device from which the action was performed.
8. **Creation date** — the exact time and date of the event.

<Image
  src="/images/interface/events/events-log-list-en.webp"
  alt="Events Log Interface"
  caption="Events Log Interface"
/>

## Example of record analysis

The figure below shows the change history for the Metering unit with ID 861. Analysis of the records (bottom up) reveals:

- **Change of unit ownership** — transfer between consumers.
- **Rename unit** — name update (e.g., "Warehouse No. 5" → "Fuel and lubricants warehouse").
- **Change of service organization** — assignment of a new company for servicing.
- **Update of telemetry unit data** — replacement of the factory number.
- **Change of SIM card number** — activation of a new identifier for data transfer.

<Alert type="tip">
  Use **filters** to search for quick events by type, action, metering unit, etc.
</Alert>

<Image
  src="/images/interface/events/events-log-en.webp"
  alt="Change log for the Metering Unit."
  caption="Change log for the Metering Unit."
/>

## Benefits of logging

1. **Security audit** — identify suspicious activity (e.g. logins from unauthorized IP addresses).
2. **Data recovery** — roll back erroneous changes via edit history.
3. **Reporting** — generate statistics on user activity.
4. **Transparency** — each administrator can check who made changes and when.