> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.7/en/webanwendung/sichten/ereignisanalyse/arbeitsweise.md).

# How It Works

The event interface is complex. Some background information is important when working with the event interface.

Event data is difficult to calculate for JUNE5. For a measurement variable (measurement value time series) with second-by-second recording, the data volume is relatively static (86400 values per day per measurement variable).

Event data can, for example, occur very frequently in a short time at alarm thresholds. If queries are then made over longer time periods, it inevitably leads to large amounts of data that must be processed. Since it is not known during the query in which time periods the data lies, a logic must be applied so that the system is not overloaded and the user always has a "reactive" system.

{% hint style="info" %}
The connectors for the event query have their own logic to process and reduce the difficult-to-calculate data volume.
{% endhint %}

## acron

The acron API interface is limited to 100,000 events. If this data volume is exceeded, only the first 100,000 events are returned. For this reason, the acron connector creates multiple queries to the acron data source.

Each query contains a time range of 6 hours. This value is hardcoded and cannot be adjusted. If the user creates an event object with a 24-hour time range, a total of 4 queries are executed to the acron data source. The amount returned is then sent by the connector to the web server. This then provides pagination (e.g., 100-block chunks) for the frontend.

However, if a filter for the item ID has been defined, only the filtered data is delivered to the web server. The acron connector thus pre-filters the item ID so that the data volume does not become too large. This pre-filter applies only to the item ID, not to all other properties such as item name, user, etc.

If the connector receives a request over 10 days, it creates 40 requests to the ACRON data source. If more than 10,000 events are already returned from the acron data source after the 3rd query, the connector aborts the query and reports the result with a warning to the web server. This ensures that the system is not blocked and can continue to work.

The limit can be set globally in the ServerConfiguration.xml.

***\<EventResultLimit>10000\</EventResultLimit>***

## OLE DB

With the OLE DB interface, data restriction is usually achieved through the SQL command. For example:\
\&#xNAN;***SELECT TOP (1000) FROM Alarmtable***\
Only the first 1000 events of the table are returned here, regardless of how large the time range is.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.videc.de/june5-3.7/en/webanwendung/sichten/ereignisanalyse/arbeitsweise.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.