> 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.md).

# Event Analysis

The event table is used for tabular display of events from an acron and OLE DB database. For each event table, the events from all data sources released to the user are determined if no data source is selected.

## Creating an Event Analysis

In the *Views* area, click on the button with the *plus symbol*. Subsequently, select the entry *Event Analysis*.

The content of the event table can be customized according to individual requirements. The corresponding controls are located directly above the table:

* Column Selection: Via column selection, you can determine which columns are displayed in the table. A short description of the possible selectable columns can be found [here](/june5-3.7/en/datenquellenunterstuetzung-und-einbindung/microsoft-ole-db/sql-tabelle-ereignisse.md).
* Search Filter ([Advanced Filter](/june5-3.7/en/webanwendung/erweiterter-filter.md))

The table is sorted by clicking on the desired column header. In the footer of the table are the elements for navigation (paging).

### Pre-filter

A *Pre-filter* can be configured in the Properties window, which can be opened via the *Properties* button in the upper right corner of the screen. The filter criteria can be found in the chapter [Advanced Filter](/june5-3.7/en/webanwendung/erweiterter-filter.md). The *Pre-filter* is only executed after clicking the *Apply* button.

{% hint style="info" %}
The *Event Filter String* can be applied to all columns except those of type *Timestamp*.
{% endhint %}

## Properties

The following properties can be configured in the *Properties window*:

* Name
* Identification
* [Start Time](/june5-3.7/en/webanwendung/sichten/startzeit.md) *(automatically with current timestamp, absolute or relative)*
* Pre-filter
* Use Buffer
* Priority Background Color
* Event Font Color
* Selection of Event Data Source
* Allow Categories *(Enables the configuration of* [Categories](/june5-3.7/en/webanwendung/sichten/ereignisanalyse/kategorie.md))
* Widget Border Color (*only in Dashboard possible!*)
* Widget Border Width (*only in Dashboard possible!*)
* [Print](/june5-3.7/en/webanwendung/sichten/drucken.md)

## Toolbar

The toolbar provides buttons for the following settings.

* Refresh *(loads newly occurred values from the data source).*
* Set Time *(opens a modal window in which the time point/range can be adjusted).*
* Previous Time Interval
* Next Time Interval

### Use Buffer

This property determines whether the event buffer configuration set in [Data Sources](/june5-3.7/en/webanwendung/datenquellen/datenquellen-konfigurieren.md) should be applied or not. If the checkbox in the Properties window has a checkmark, the buffer is applied to the event query; otherwise, it is not.

### Reload Events

If not all events can be retrieved at once, they are reloaded dynamically. This is indicated to the right of the event analysis. There, the "Cancel" button can be used to cancel the reloading.

### Background Color for Priorities

The priority of an event is displayed in JUNE5 with numerical values between 0 and 1000. If the data source does not provide priority as a numerical value, the value of this priority must be assigned to a defined numerical value. The assignment can only be done for specific predefined strings specified in the following table.

| **Predefined Strings** | **Numerical Value** |
| ---------------------- | ------------------- |
| INFO                   | 001                 |
| LO                     | 200                 |
| LOLOLO                 | 250                 |
| LO                     | 300                 |
| MEDIUM                 | 500                 |
| HI                     | 700                 |
| HIHI                   | 750                 |
| HIHIHI                 | 800                 |
| CRITICAL               | 900                 |

{% hint style="info" %}
The priority of an event is set to 0 if the assignment is not possible.
{% endhint %}

For each event priority, a custom background color can be configured if desired. This is done in the Properties window, which can be opened via the *Properties* button in the upper right corner of the screen. To the right of the *Priority Background Color* entry is a *gear icon* which, when clicked, opens a modal window. Here, priorities can be divided into ranges. Each range can be assigned its own background color.

### Font Color for Events

A custom font color can be configured for each event type if desired. This is done in the Properties window, which can be opened via the Properties button in the upper right corner of the screen. To the right of the Event Font Color entry is a gear icon which, when clicked, opens a modal window. Here, each type can be assigned an individual font color.

### Selection of Event Data Source

The selection of the event data source can be configured in the Properties window, under the entry *Select Event Data Source*. If no data source is selected, events are determined from all data sources released to the user. Additionally, a SQL filter can be entered to restrict the result set to the corresponding data source.

A SQL filter consists of one or more partial expressions of a SQL WHERE clause. The partial expressions must not contain the keyword *WHERE* and must only represent boolean conditions. These boolean conditions must in turn only contain column names that are actually defined on the server for the events table. Below are some examples that illustrate how to create a boolean condition for a table with column names *PRIORITY* and *STATUS*.

* \[PRIORITY] >= 25
* \[PRIORITY] >= 25 AND \[STATUS] LIKE 'LOW'
* \[STATUS] LIKE 'HIHI'

Furthermore, these boolean conditions can contain keywords for columns that contain timestamps. The keywords are replaced at runtime with the configured start or end time of the query. Currently, two keywords ***<\<TS\_From>>*** and ***<\<TS\_To>>*** are defined. Below are some examples that illustrate how to create conditions with keywords for start or end time for a table with column names *ACKNOWLEDGED* and *STATUS*:

* \[ACKNOWLEDGED] BETWEEN ***<\<TS\_From>>*** AND ***<\<TS\_To>>***
* \[ACKNOWLEDGED] >= ***<\<TS\_From>>*** OR \[STATUS] LIKE 'INFO'
* \[ACKNOWLEDGED] >= ***<\<TS\_To>>*** OR \[STATUS] LIKE 'CRITICAL'

{% hint style="info" %}
A SQL filter can only be set for data sources of type OLE DB.
{% endhint %}

### Delete an Event Table

The delete button with the *trash icon* appears after clicking on the auxiliary button *(with three dots)*. This is located in the list view to the right of the event table. The event table is deleted after clicking the delete button.


---

# 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.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.