Filtering events

The Events section of the KUMA web interface does not show any data by default. To view events, you need to define an SQL query in the search field and click the SearchField button. The SQL query can be entered manually or it can be generated using a query builder.

Please note that when switching to the query builder, the query parameters that were manually entered into the search string are not transferred to the builder so you will need to create your query again. Also, the query created in the builder does not overwrite the query that was entered into the search string until you click the Apply button in the builder window.

Data aggregation and grouping is supported in SQL queries.

An SQL query can be changed based on the search results:

In the SQL query input field, you can enable the display of control characters.

You can also filter events by time period. Search results can be automatically updated.

Filter configurations can be saved. Existing filter configurations can be deleted.

Filter functions are available for users regardless of their roles.

After updating KUMA to version 1.6, event filtering that uses an SQL query containing the inSubnet condition may result in error Code: 441. DB::Exception: Invalid IPv4 value. If this is the case, you must add the directive <cast_ipv4_ipv6_default_on_conversion_error>true</cast_ipv4_ipv6_default_on_conversion_error> in the profiles → default section of the file /opt/kaspersky/kuma/clickhouse/cfg/config.d/users.xml on the storage servers (on each machine of the ClickHouse cluster).

For more details on SQL, refer to the ClickHouse documentation. See also the SQL functions and operators supported by KUMA.

In this section

Filtering events by period

Generating an SQL query using a builder

Complicated SQL queries

Limited complexity of queries in drilldown analysis mode

Saving and selecting events filter configuration

Deleting event filter configurations

See also:

About events

Storage

Page top