Kaspersky Next XDR Expert
[Topic 233383]

About events in Open Single Management Platform

Open Single Management Platform allows you to receive information about events that occur during the operation of Administration Server and Kaspersky applications installed on managed devices. Information about events is saved in the Administration Server database.

Events by type

In Open Single Management Platform, there are the following types of events:

  • General events. These events occur in all managed Kaspersky applications. An example of a general event is Virus outbreak. General events have strictly defined syntax and semantics. General events are used, for instance, in reports and dashboards.
  • Managed Kaspersky applications-specific events. Each managed Kaspersky application has its own set of events.

Events by source

You can view the full list of the events that can be generated by an application on the Event configuration tab in the application policy. For Administration Server, you can additionally view the event list in the Administration Server properties.

Events can be generated by the following applications:

  • Open Single Management Platform components:
  • Managed Kaspersky applications

    For details about the events generated by Kaspersky managed applications, please refer to the documentation of the corresponding application.

Events by importance level

Each event has its own importance level. Depending on the conditions of its occurrence, an event can be assigned various importance levels. There are four importance levels of events:

  • A critical event is an event that indicates the occurrence of a critical problem that may lead to data loss, an operational malfunction, or a critical error.
  • A functional failure is an event that indicates the occurrence of a serious problem, error, or malfunction that occurred during operation of the application or while performing a procedure.
  • A warning is an event that is not necessarily serious, but nevertheless indicates a potential problem in the future. Most events are designated as warnings if the application can be restored without loss of data or functional capabilities after such events occur.
  • An info event is an event that occurs for the purpose of informing about successful completion of an operation, proper functioning of the application, or completion of a procedure.

Each event has a defined storage term, during which you can view or modify it in Open Single Management Platform. Some events are not saved in the Administration Server database by default because their defined storage term is zero. Only events that will be stored in the Administration Server database for at least one day can be exported to external systems.

See also:

Events of Open Single Management Platform components

Scenario: Configuring event export to SIEM systems

Page top
[Topic 151331]

Events of Open Single Management Platform components

Each Open Single Management Platform component has its own set of event types. This section lists types of events that occur in Kaspersky Security Center Administration Server and Network Agent. Types of events that occur in Kaspersky applications are not listed in this section.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

In this section

Data structure of event type description

Administration Server events

Network Agent events

Page top
[Topic 151336]

Data structure of event type description

For each event type, its display name, identifier (ID), alphabetic code, description, and the default storage term are provided.

  • Event type display name. This text is displayed in Open Single Management Platform when you configure events and when they occur.
  • Event type ID. This numerical code is used when you process events by using third-party tools for event analysis.
  • Event type (alphabetic code). This code is used when you browse and process events by using public views that are provided in the Open Single Management Platform database and when events are exported to a SIEM system.
  • Description. This text contains the situations when an event occurs and what you can do in such a case.
  • Default storage term. This is the number of days during which the event is stored in the Administration Server database and is displayed in the list of events on Administration Server. After this period elapses, the event is deleted. If the event storage term value is 0, such events are detected but are not displayed in the list of events on Administration Server. If you configured to save such events to the operating system event log, you can find them there.

    You can change the storage term for events: Setting the storage term for an event

Page top
[Topic 181756]

Administration Server events

This section contains information about the events related to the Administration Server.

In this section

Administration Server critical events

Administration Server functional failure events

Administration Server warning events

Administration Server informational events

Page top
[Topic 184666_1]

Administration Server critical events

The table below shows the events of Kaspersky Security Center Administration Server that have the Critical importance level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Administration Server critical events

Event type display name

Event type ID

Event type

Description

Default storage term

License limit has been exceeded

4099

KLSRV_EV_LICENSE_CHECK_MORE_110

Once a day Open Single Management Platform checks whether a license limit is exceeded.

Events of this type occur when Administration Server detects that some licensing limits are exceeded by Kaspersky applications installed on client devices and if the number of currently used licensing units covered by a single license exceeds 110% of the total number of units covered by the license.

Even when this event occurs, client devices are protected.

You can respond to the event in the following ways:

  • Look through the managed devices list. Delete devices that are not in use.
  • Provide a license for more devices (add a valid activation code or a key file to Administration Server).

Open Single Management Platform determines the rules to generate events when a licensing limit is exceeded.

180 days

Device has become unmanaged

4111

KLSRV_HOST_OUT_CONTROL

Events of this type occur if a managed device is visible on the network but has not connected to Administration Server for a specific period.

Find out what prevents the proper functioning of Network Agent on the device. Possible causes include network issues and removal of Network Agent from the device.

180 days

Device status is Critical

4113

KLSRV_HOST_STATUS_CRITICAL

Events of this type occur when a managed device is assigned the Critical status. You can configure the conditions under which the device status is changed to Critical.

180 days

The key file has been added to the denylist

4124

KLSRV_LICENSE_BLACKLISTED

Events of this type occur when Kaspersky has added the activation code or key file that you use to the denylist.

Contact Technical Support for more details.

180 days

License expires soon

4129

KLSRV_EV_LICENSE_SRV_EXPIRE_SOON

Events of this type occur when the commercial license expiration date is approaching.

Once a day Open Single Management Platform checks whether a license expiration date is approaching. Events of this type are published 30 days, 15 days, 5 days, and 1 day before the license expiration date. This number of days cannot be changed. If the Administration Server is turned off on the specified day before the license expiration date, the event will not be published until the next day.

When the commercial license expires, Open Single Management Platform provides only basic functionality.

You can respond to the event in the following ways:

  • Make sure that a reserve license key is added to Administration Server.
  • If you use a subscription, make sure to renew it. An unlimited subscription is renewed automatically if it has been prepaid to the service provider by the due date.

180 days

Certificate has expired

4132

KLSRV_CERTIFICATE_EXPIRED

Events of this type occur when the Administration Server certificate for Mobile Device Management expires.

You need to update the expired certificate.

180 days

See also:

Administration Server functional failure events

Administration Server informational events

Administration Server warning events

About events in Open Single Management Platform

Page top
[Topic 177080_1]

Administration Server functional failure events

The table below shows the events of Kaspersky Security Center Administration Server that have the Functional failure importance level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Administration Server functional failure events

Event type display name

Event type ID

Event type

Description

Default storage term

Runtime error

 

 

4125

 

 

 

 

KLSRV_RUNTIME_ERROR

 

 

 

 

Events of this type occur because of unknown issues.

Most often these are DBMS issues, network issues, and other software and hardware issues.

Details of the event can be found in the event description.

 

 

 

 

 

180 days

 

 

 

 

Failed to copy the updates to the specified folder

4123

KLSRV_UPD_REPL_FAIL

Events of this type occur when software updates are copied to an additional shared folder(s).

You can respond to the event in the following ways:

  • Check whether the user account that is employed to gain access to the folder(s) has write permission.
  • Check whether a user name and/or a password to the folder(s) changed.
  • Check the internet connection, as it might be the cause of the event. Follow the instructions to update databases and software modules.

180 days

No free disk space

4107

KLSRV_DISK_FULL

Events of this type occur when the hard drive of the device on which Administration Server is installed runs out of free space.

Free up disk space on the device.

180 days

Shared folder is not available

4108

KLSRV_SHARED_FOLDER_UNAVAILABLE

Events of this type occur if the shared folder of Administration Server is not available.

You can respond to the event in the following ways:

  • Check whether the Administration Server (where the shared folder is located) is turned on and available.
  • Check whether a user name and/or a password to the folder is/are changed.
  • Check the network connection.

180 days

The Administration Server database is unavailable

4109

KLSRV_DATABASE_UNAVAILABLE

Events of this type occur if the Administration Server database becomes unavailable.

You can respond to the event in the following ways:

  • Check whether the remote server that has SQL Server installed is available.
  • View the DBMS logs to discover the reason for Administration Server database unavailability. For example, because of preventive maintenance a remote server with SQL Server installed might be unavailable.

180 days

No free space in the Administration Server database

4110

KLSRV_DATABASE_FULL

Events of this type occur when there is no free space in the Administration Server database.

Administration Server does not function when its database has reached its capacity and when further recording to the database is not possible.

Following are the causes of this event, depending on the DBMS that you use, and appropriate responses to the event:

Review the information on DBMS selection.

180 days

Failed to poll the cloud segment

4143

KLSRV_KLCLOUD_SCAN_ERROR

Events of this type occur when Administration Server fails to poll a network segment in a cloud environment. Read the details in the event description and respond accordingly.

Not stored

See also:

Administration Server critical events

Administration Server informational events

Administration Server warning events

About events in Open Single Management Platform

Page top
[Topic 177081_1]

Administration Server warning events

The table below shows the events of Kaspersky Security Center Administration Server that have the Warning importance level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Administration Server warning events

Event type display name

Event type ID

Event type

Description

Default storage term

A frequent event has been detected

 

KLSRV_EVENT_SPAM_EVENTS_DETECTED

Events of this type occur when Administration Server detects a frequent event on a managed device. Refer to the following section for details: Blocking frequent events.

90 days

License limit has been exceeded

4098

KLSRV_EV_LICENSE_CHECK_100_110

Once a day Open Single Management Platform checks whether a licensing limit is exceeded.

Events of this type occur when Administration Server detects that some licensing limits are exceeded by Kaspersky applications installed on client devices and if the number of currently used licensing units covered by a single license constitute 100% to 110% of the total number of units covered by the license.

Even when this event occurs, client devices are protected.

You can respond to the event in the following ways:

  • Look through the managed devices list. Delete devices that are not in use.
  • Provide a license for more devices (add a valid activation code or a key file to Administration Server).

Open Single Management Platform determines the rules to generate events when a licensing limit is exceeded.

90 days

Device has remained inactive on the network for a long time

4103

KLSRV_EVENT_HOSTS_NOT_VISIBLE

Events of this type occur when a managed device shows inactivity for some time.

Most often, this happens when a managed device is decommissioned.

You can respond to the event in the following ways:

  • Manually remove the device from the list of managed devices.

    Specify the time interval after which the Device has remained inactive on the network for a long time event is created by using OSMP Console.

  • Specify the time interval after which the device is automatically removed from the group by using OSMP Console.

90 days

Conflict of device names

4102

KLSRV_EVENT_HOSTS_CONFLICT

Events of this type occur when Administration Server considers two or more managed devices as a single device.

Most often this happens when a cloned hard drive was used for software deployment on managed devices and without switching the Network Agent to the dedicated disk cloning mode on a reference device.

To avoid this issue, switch Network Agent to the disk cloning mode on a reference device before cloning the hard drive of this device.

90 days

Device status is Warning

 

 

 

4114

 

 

 

KLSRV_HOST_STATUS_WARNING

 

 

 

Events of this type occur when a managed device is assigned the Warning status. You can configure the conditions under which the device status is changed to Warning.

 

 

 

 

 

90 days

 

 

 

Certificate has been requested

4133

KLSRV_CERTIFICATE_REQUESTED

Events of this type occur when a certificate for Mobile Device Management fails to be automatically reissued.

Following might be the causes and appropriate responses to the event:

  • Automatic reissue was initiated for a certificate for which the Reissue certificate automatically if possible option is disabled. This might be due to an error that occurred during creation of the certificate. Manual reissue of the certificate might be required.
  • If you use an integration with a public key infrastructure, the cause might be a missing SAM-Account-Name attribute of the account used for integration with PKI and for issuance of the certificate. Review the account properties.

90 days

Certificate has been removed

4134

KLSRV_CERTIFICATE_REMOVED

Events of this type occur when an administrator removes any type of certificate (General, Mail, VPN) for Mobile Device Management.

After removing a certificate, mobile devices connected via this certificate will fail to connect to Administration Server.

This event might be helpful when investigating malfunctions associated with the management of mobile devices.

90 days

APNs certificate has expired

4135

KLSRV_APN_CERTIFICATE_EXPIRED

Events of this type occur when an APNs certificate expires.

You need to manually renew the APNs certificate and install it on an iOS MDM Server.

Not stored

APNs certificate expires soon

4136

KLSRV_APN_CERTIFICATE_EXPIRES_SOON

Events of this type occur when there are fewer than 14 days left before the APNs certificate expires.

When the APNs certificate expires, you need to manually renew the APNs certificate and install it on an iOS MDM Server.

We recommend that you schedule the APNs certificate renewal in advance of the expiration date.

Not stored

Failed to send the FCM message to the mobile device

4138

KLSRV_GCM_DEVICE_ERROR

Events of this type occur when Mobile Device Management is configured to use Google Firebase Cloud Messaging (FCM) for connecting to managed mobile devices with an Android operating system and FCM Server fails to handle some of the requests received from Administration Server. It means that some of the managed mobile devices will not receive a push notification.

Read the HTTP code in the details of the event description and respond accordingly. For more information on the HTTP codes received from FCM Server and related errors, please refer to the Google Firebase service documentation (see chapter "Downstream message error response codes").

90 days

HTTP error sending the FCM message to the FCM server

4139

KLSRV_GCM_HTTP_ERROR

Events of this type occur when Mobile Device Management is configured to use Google Firebase Cloud Messaging (FCM) for connecting managed mobile devices with the Android operating system and FCM Server reverts to the Administration Server a request with a HTTP code other than 200 (OK).

Following might be the causes and appropriate responses to the event:

  • Problems on the FCM server side. Read the HTTP code in the details of the event description and respond accordingly. For more information on the HTTP codes received from FCM Server and related errors, please refer to the Google Firebase service documentation (see chapter "Downstream message error response codes").
  • Problems on the proxy server side (if you use proxy server). Read the HTTP code in the details of the event and respond accordingly.

90 days

Failed to send the FCM message to the FCM server

4140

KLSRV_GCM_GENERAL_ERROR

Events of this type occur due to unexpected errors on the Administration Server side when working with the Google Firebase Cloud Messaging HTTP protocol.

Read the details in the event description and respond accordingly.

If you cannot find the solution to an issue on your own, we recommend that you contact Kaspersky Technical Support.

90 days

Little free space on the hard drive

4105

KLSRV_NO_SPACE_ON_VOLUMES

Events of this type occur when the hard drive of the device on which Administration Server is installed almost runs out of free space.

Free up disk space on the device.

90 days

Little free space in the Administration Server database

4106

KLSRV_NO_SPACE_IN_DATABASE

Events of this type occur if space in the Administration Server database is too limited. If you do not remedy the situation, soon the Administration Server database will reach its capacity and Administration Server will not function.

Following are the causes of this event, depending on the DBMS that you use, and the appropriate responses to the event.

You use the SQL Server Express Edition DBMS:

  • In SQL Server Express documentation, review the database size limit for the version you use. Probably your Administration Server database is about to reach the database size limit.
  • Limit the number of events to store in the Administration Server database.
  • In the Administration Server database there are too many events sent by the Application Control component. You can change the settings of the Kaspersky Endpoint Security policy relating to Application Control event storage in the Administration Server database.

You use a DBMS other than SQL Server Express Edition:

Review the information on DBMS selection.

90 days

Connection to the secondary Administration Server has been interrupted

4116

KLSRV_EV_SLAVE_SRV_DISCONNECTED

Events of this type occur when a connection to the secondary Administration Server is interrupted.

Read the operating system log on the device where the secondary Administration Server is installed and respond accordingly.

90 days

Connection to the primary Administration Server has been interrupted

4118

KLSRV_EV_MASTER_SRV_DISCONNECTED

Events of this type occur when a connection to the primary Administration Server is interrupted.

Read the operating system log on the device where the primary Administration Server is installed and respond accordingly.

90 days

New updates for Kaspersky application modules have been registered

4141

KLSRV_SEAMLESS_UPDATE_REGISTERED

Events of this type occur when Administration Server registers new updates for the Kaspersky software installed on managed devices that require approval to be installed.

Approve or decline the updates by using Kaspersky Security Center Web Console.

90 days

The limit on the number of events in the database is exceeded, deletion of events has started

4145

KLSRV_EVP_DB_TRUNCATING

Events of this type occur when deletion of old events from the Administration Server database has started after the Administration Server database capacity is reached.

You can respond to the event in the following ways:

Not stored

The limit on the number of events in the database is exceeded, the events have been deleted

4146

KLSRV_EVP_DB_TRUNCATED

Events of this type occur when old events have been deleted from the Administration Server database after the Administration Server database capacity is reached.

You can respond to the event in the following ways:

Not stored

See also:

Administration Server critical events

Administration Server functional failure events

Administration Server informational events

About events in Open Single Management Platform

Page top
[Topic 177082_1]

Administration Server informational events

The table below shows the events of Kaspersky Security Center Administration Server that have the Info importance level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Administration Server informational events

Event type display name

Event type ID

Event type

Default storage term

Remarks

Over 90% of the license key is used up

4097

KLSRV_EV_LICENSE_CHECK_90

30 days

Events of this type occur when Administration Server detects that some licensing limits are close to being exceeded by Kaspersky applications installed on client devices and if the number of currently used licensing units covered by a single license constitute over 90% of the total number of units covered by the license.

Even when a licensing limit is exceeded, client devices are protected.

You can respond to the event in the following ways:

  • Look through the managed devices list. Delete devices that are not in use.
  • Provide a license for more devices (add a valid activation code or a key file to Administration Server).

Open Single Management Platform determines the rules to generate events when a licensing limit is exceeded.

New device has been detected

4100

KLSRV_EVENT_HOSTS_NEW_DETECTED

30 days

Events of this type occur when new networked devices have been discovered.

Device has been automatically added to the group

4101

KLSRV_EVENT_HOSTS_NEW_REDIRECTED

30 days

Events of this type occur when devices have been assigned to a group according to device moving rules.

Device has been removed from the group: inactive on the network for a long time

 

 

4104

 

 

KLSRV_INVISIBLE_HOSTS_REMOVED

 

 

30 days

 

 

 

Files have been found to send to Kaspersky for analysis

4131

KLSRV_APS_FILE_APPEARED

30 days

 

FCM Instance ID has changed on this mobile device

4137

KLSRV_GCM_DEVICE_REGID_CHANGED

30 days

 

Updates have been successfully copied to the specified folder

4122

KLSRV_UPD_REPL_OK

30 days

 

Connection to the secondary Administration Server has been established

4115

KLSRV_EV_SLAVE_SRV_CONNECTED

30 days

 

Connection to the primary Administration Server has been established

4117

KLSRV_EV_MASTER_SRV_CONNECTED

30 days

 

Databases have been updated

4144

KLSRV_UPD_BASES_UPDATED

30 days

 

Audit: Connection to the Administration Server has been established

4147

KLAUD_EV_SERVERCONNECT

30 days

 

Audit: Object has been modified

4148

KLAUD_EV_OBJECTMODIFY

30 days

This event tracks changes in the following objects:

  • Administration group
  • Security group
  • User
  • Package
  • Task
  • Policy
  • Server
  • Virtual Server

Audit: Object status has changed

4150

KLAUD_EV_TASK_STATE_CHANGED

30 days

For example, this event occurs when a task has failed with an error.

Audit: Group settings have been modified

4149

KLAUD_EV_ADMGROUP_CHANGED

30 days

 

Audit: Connection to Administration Server has been terminated

4151

KLAUD_EV_SERVERDISCONNECT

30 days

 

Audit: Object properties have been modified

4152

KLAUD_EV_OBJECTPROPMODIFIED

30 days

This event tracks changes in the following properties:

  • User
  • License
  • Server
  • Virtual server

Audit: User permissions have been modified

4153

KLAUD_EV_OBJECTACLMODIFIED

30 days

 

Audit: Encryption keys have been imported or exported from Administration Server

5100

KLAUD_EV_DPEKEYSEXPORT

30 days

 

Page top
[Topic 177083_1]

Network Agent events

This section contains information about the events related to Network Agent.

In this section

Network Agent warning events

Network Agent informational events

Page top
[Topic 184667]

Network Agent warning events

The table below shows the events of Network Agent that have the Warning severity level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Network Agent warning events

Event type display name

Event type ID

Event type

Description

Default storage term

Security issue has occurred

549

GNRL_EV_APP_INCIDENT_OCCURED

Events of this type occur when an incident has been found on a device. For example, this event occurs when the device has low disk space.

30 days

KSN Proxy has started. Failed to check KSN for availability

7718

KSNPROXY_STARTED_CON_CHK_FAILED

Events of this type occur when test connection fails for the configured KSN proxy connection.

30 days

Third-party software update installation has been postponed

7698

KLNAG_EV_3P_PATCH_INSTALL_SLIPPED

For example, events of this type occur when EULA for a third-party update installation is declined.

30 days

Third-party software update installation has completed with a warning

7696

KLNAG_EV_3P_PATCH_INSTALL_WARNING

Download the trace files and check the KLRI_PATCH_RES_DESC field value for details.

30 days

Warning has been returned during installation of the software module update

7701

KLNAG_EV_PATCH_INSTALL_WARNING

Download the trace files and check the KLRI_PATCH_RES_DESC field value for details.

30 days

See also:

Network Agent informational events

Page top
[Topic 173538]

Network Agent informational events

The table below shows the events of Network Agent that have the Info severity level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Network Agent informational events

Event type display name

Event type ID

Event type

Default storage term

Application has been installed

7703

KLNAG_EV_INV_APP_INSTALLED

30 days

Application has been uninstalled

7704

KLNAG_EV_INV_APP_UNINSTALLED

30 days

Monitored application has been installed

7705

KLNAG_EV_INV_OBS_APP_INSTALLED

30 days

Monitored application has been uninstalled

7706

KLNAG_EV_INV_OBS_APP_UNINSTALLED

30 days

New device has been added

7708

KLNAG_EV_DEVICE_ARRIVAL

30 days

Device has been removed

7709

KLNAG_EV_DEVICE_REMOVE

30 days

New device has been detected

7710

KLNAG_EV_NAC_DEVICE_DISCOVERED

30 days

Device has been authorized

7711

KLNAG_EV_NAC_HOST_AUTHORIZED

30 days

KSN Proxy has started. KSN availability check has completed successfully

7719

KSNPROXY_STARTED_CON_CHK_OK

30 days

KSN Proxy has stopped

7720

KSNPROXY_STOPPED

30 days

Third-party application has been installed

7707

KLNAG_EV_INV_CMPTR_APP_INSTALLED

30 days

Third-party software update has been installed successfully

7694

KLNAG_EV_3P_PATCH_INSTALLED_SUCCESSFULLY

30 days

Third-party software update installation has started

7695

KLNAG_EV_3P_PATCH_INSTALL_STARTING

30 days

Installation of the software module update has started

7700

KLNAG_EV_PATCH_INSTALL_STARTING

30 days

Windows Desktop Sharing: Application has been started

7714

KLUSRLOG_EV_PROCESS_LAUNCHED

30 days

Windows Desktop Sharing: File has been modified

7713

KLUSRLOG_EV_FILE_MODIFIED

30 days

Windows Desktop Sharing: File has been read

7712

KLUSRLOG_EV_FILE_READ

30 days

Windows Desktop Sharing: Started

7715

KLUSRLOG_EV_WDS_BEGIN

30 days

Windows Desktop Sharing: Stopped

7716

KLUSRLOG_EV_WDS_END

30 days

See also:

Network Agent warning events

Page top
[Topic 173727]

Using event selections

Event selections provide an onscreen view of named sets of events that are selected from the Administration Server database. These sets of events are grouped according to the following categories:

  • By importance level—Critical events, Functional failures, Warnings, and Info events
  • By time—Recent events
  • By type—User requests and Audit events

You can create and view user-defined event selections based on the settings available, in the OSMP Console interface, for configuration.

Event selections are available in the OSMP Console, in the Monitoring & reporting section, by clicking Event selections.

By default, event selections include information for the last seven days.

Open Single Management Platform has a default set of event (predefined) selections:

  • Events with different importance levels:
    • Critical events
    • Functional failures
    • Warnings
    • Informational messages
  • User requests (events of managed applications)
  • Recent events (over the last week)
  • Audit events.

In Kaspersky Next XDR Expert, audit events related to service operations in your OSMP Console are displayed. These events are conditioned by actions of Kaspersky specialists. These events, for example include the following: logging in to Administration Server; Administration Server ports changing; Administration Server database backup; creation, modification, and deletion of user accounts.

You can also create and configure additional user-defined selections. In user-defined selections, you can filter events by the properties of the devices they originated from (device names, IP ranges, and administration groups), by event types and severity levels, by application and component name, and by time interval. It is also possible to include task results in the search scope. You can also use a simple search field where a word or several words can be typed. All events that contain any of the typed words anywhere in their attributes (such as event name, description, component name) are displayed.

Both for predefined and user-defined selections, you can limit the number of displayed events or the number of records to search. Both options affect the time it takes Open Single Management Platform to display the events. The larger the database is, the more time-consuming the process can be.

You can do the following:

See also:

Device selections

Page top
[Topic 166234]

Creating an event selection

To create an event selection:

  1. In the main menu, go to Monitoring & reporting Event selections.
  2. Click Add.
  3. In the New event selection window that opens, specify the settings of the new event selection. Do this in one or more of the sections in the window.
  4. Click Save to save the changes.

    The confirmation window opens.

  5. To view the event selection result, keep the Go to selection result check box selected.
  6. Click Save to confirm the event selection creation.

If you kept the Go to selection result check box selected, the event selection result is displayed. Otherwise, the new event selection appears in the list of event selections.

See also:

Scenario: Monitoring and reporting

Page top
[Topic 176385]

Editing an event selection

To edit an event selection:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Select the check box next to the event selection that you want to edit.
  3. Click the Properties button.

    An event selection settings window opens.

  4. Edit the properties of the event selection.

    For predefined event selections, you can edit only the properties on the following tabs: General (except for the selection name), Time, and Access rights.

    For user-defined selections, you can edit all properties.

  5. Click Save to save the changes.

The edited event selection is shown in the list.

See also:

Scenario: Monitoring and reporting

Page top
[Topic 177708]

Viewing a list of an event selection

To view an event selection:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Select the check box next to the event selection that you want to start.
  3. Do one of the following:
    • If you want to configure sorting in the event selection result, do the following:
      1. Click the Reconfigure sorting and start button.
      2. In the displayed Reconfigure sorting for event selection window, specify the sorting settings.
      3. Click the name of the selection.
    • Otherwise, if you want to view the list of events as they are sorted on the Administration Server, click the name of the selection.

The event selection result is displayed.

See also:

Scenario: Monitoring and reporting

Page top
[Topic 176415]

Exporting an event selection

Open Single Management Platform allows you to save an event selection and its settings to a KLO file. You can use this KLO file to import the saved event selection both to Kaspersky Security Center Windows and Kaspersky Security Center Linux.

Note that you can export only user-defined event selections. Event selections from the default set of Open Single Management Platform (predefined selections) cannot be saved to a file.

To export an event selection:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Select the check box next to the event selection that you want to export.

    You cannot export multiple event selections at the same time. If you select more than one selection, the Export button will be disabled.

  3. Click the Export button.
  4. In the opened Save as window, specify the event selection file name and path, and then click the Save button.

    The Save as window is displayed only if you use Google Chrome, Microsoft Edge, or Opera. If you use another browser, the event selection file is automatically saved in the Downloads folder.

Page top
[Topic 236067]

Importing an event selection

Open Single Management Platform allows you to import an event selection from a KLO file. The KLO file contains the exported event selection and its settings.

To import an event selection:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Click the Import button, and then choose an event selection file that you want to import.
  3. In the opened window, specify the path to the KLO file, and then click the Open button. Note that you can select only one event selection file.

    The event selection processing starts.

The notification with the import results appears. If the event selection is imported successfully, you can click the View import details link to view the event selection properties.

After a successful import, the event selection is displayed in the selection list. The settings of the event selection are also imported.

If the newly imported event selection has a name identical to that of an existing event selection, the name of the imported selection is expanded with the (<next sequence number>) index, for example: (1), (2).

Page top
[Topic 236654]

Viewing details of an event


To view details of an event:

  1. Start an event selection.
  2. Click the time of the required event.

    The Event properties window opens.

  3. In the displayed window, you can do the following:
    • View the information about the selected event
    • Go to the next event and the previous event in the event selection result
    • Go to the device on which the event occurred
    • Go to the administration group that includes the device on which the event occurred
    • For an event related to a task, go to the task properties

See also:

Scenario: Monitoring and reporting

Page top
[Topic 171287]

Exporting events to a file

To export events to a file:

  1. Start an event selection.
  2. Select the check box next to the required event.
  3. Click the Export to file button.

The selected event is exported to a file.

See also:

Scenario: Monitoring and reporting

Page top
[Topic 178646]

Viewing an object history from an event

From an event of creation or modification of an object that supports revision management, you can switch to the revision history of the object.

To view an object history from an event:

  1. Start an event selection.
  2. Select the check box next to the required event.
  3. Click the Revision history button.

The revision history of the object is opened.

See also:

Scenario: Monitoring and reporting

Page top
[Topic 177727]

Deleting events

To delete one or several events:

  1. Start an event selection.
  2. Select the check boxes next to the required events.
  3. Click the Delete button.

The selected events are deleted and cannot be restored.

See also:

Scenario: Monitoring and reporting

Page top
[Topic 178626]

Deleting event selections

You can delete only user-defined event selections. Predefined event selections cannot be deleted.

To delete one or several event selections:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Select the check boxes next to the event selections that you want to delete.
  3. Click Delete.
  4. In the window that opens, click OK.

The event selection is deleted.

See also:

Scenario: Monitoring and reporting

Page top
[Topic 176418]

Setting the storage term for an event

Open Single Management Platform allows you to receive information about events that occur during the operation of Administration Server and Kaspersky applications installed on managed devices. Information about events is saved in the Administration Server database. You might need to store some events for a longer or shorter period than specified by default values. You can change the default settings of the storage term for an event.

If you are not interested in storing some events in the database of Administration Server, you can disable the appropriate setting in the Administration Server policy and Kaspersky application policy, or in the Administration Server properties (only for Administration Server events). This will reduce the number of event types in the database.

The longer the storage term for an event, the faster the database reaches its maximum capacity. However, a longer storage term for an event lets you perform monitoring and reporting tasks for a longer period.

To set the storage term for an event in the database of Administration Server:

  1. In the main menu, go to Assets (Devices)Policies & profiles.
  2. Do one of the following:
    • To configure the storage term of the events of Network Agent or of a managed Kaspersky application, click the name of the corresponding policy.

      The policy properties page opens.

    • To configure Administration Server events, in the main menu, click the settings icon () next to the name of the required Administration Server.

      If you have a policy for the Administration Server, you can click the name of this policy instead.

      The Administration Server properties page (or the Administration Server policy properties page) opens.

  3. Select the Event configuration tab.

    A list of event types related to the Critical section is displayed.

  4. Select the Functional failure, Warning, or Info section.
  5. In the list of event types in the right pane, click the link for the event whose storage term you want to change.

    In the Event registration section of the window that opens, the Store in the Administration Server database for (days) option is enabled.

  6. In the edit box below this toggle button, enter the number of days to store the event.
  7. If you do not want to store an event in the Administration Server database, disable the Store in the Administration Server database for (days) option.

    If you configure Administration Server events in Administration Server properties window and if event settings are locked in the Kaspersky Security Center Administration Server policy, you cannot redefine the storage term value for an event.

  8. Click OK.

    The properties window of the policy is closed.

From now on, when Administration Server receives and stores the events of the selected type, they will have the changed storage term. Administration Server does not change the storage term of previously received events.

Page top
[Topic 178622]

Blocking frequent events

This section provides information about managing frequent events blocking and about removing blocking of frequent events.

In this section

About blocking frequent events

Managing frequent events blocking

Removing blocking of frequent events

Page top
[Topic 212870]

About blocking frequent events

A managed application, for example, Kaspersky Endpoint Security for Linux, installed on a single or several managed devices can send a lot of events of the same type to the Administration Server. Receiving frequent events may overload the Administration Server database and overwrite other events. Administration Server starts blocking the most frequent events when the number of all the received events exceeds the specified limit for the database.

Administration Server blocks the frequent events from receiving automatically. You cannot block the frequent events yourself, or choose which events to block.

If you want to find out if an event is blocked, you can view the notification list or you can check if this event is present in the Blocking frequent events section of the Administration Server properties. If the event is blocked, you can do the following:

  • If you want to prevent overwriting the database, you can continue blocking such type of events from receiving.
  • If you want, for example, to find the reason of sending the frequent events to the Administration Server, you can unblock frequent events and continue receiving the events of this type anyway.
  • If you want to continue receiving the frequent events until they become blocked again, you can remove from blocking the frequent events.

Page top
[Topic 212440]

Managing frequent events blocking

Administration Server blocks the automatic receiving of frequent events, but you can unblock and continue to receive frequent events. You can also block receiving frequent events that you unblocked before.

To manage frequent events blocking:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Blocking frequent events section.
  3. In the Blocking frequent events section:
    • If you want to unblock the receiving of frequent events:
      1. Select the frequent events you want to unblock, and then click the Exclude button.
      2. Click the Save button.
    • If you want to block receiving frequent events:
      1. Select the frequent events you want to block, and then click the Block button.
      2. Click the Save button.

Administration Server receives the unblocked frequent events and does not receive the blocked frequent events.

Page top
[Topic 212657]

Removing blocking of frequent events

You can remove blocking for frequent events and start receiving them until Administration Server blocks these frequent events again.

To remove blocking for frequent events:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Blocking frequent events section.
  3. In the Blocking frequent events section, select the frequent event types for which you want to remove blocking.
  4. Click the Remove from blocking button.

The frequent event is removed from the list of frequent events. Administration Server will receive events of this type.

Page top
[Topic 212658]

Event processing and storage on the Administration Server

Information about events during the operation of the application and managed devices is saved in the Administration Server database. Each event is attributed to a certain type and level of severity (Critical event, Functional failure, Warning, or Info). Depending on the conditions under which an event occurred, the application can assign different levels of severity to events of the same type.

You can view types and levels of severity assigned to events in the Event configuration section of the Administration Server properties window. In the Event configuration section, you can also configure processing of every event by the Administration Server:

  • Registration of events on the Administration Server and in event logs of the operating system on a device and on the Administration Server.
  • Method used for notifying the administrator of an event (for example, an SMS or email message).

In the Events repository section of the Administration Server properties window, you can edit the settings of events storage in the Administration Server database by limiting the number of event records and record storage term. When you specify the maximum number of events, the application calculates an approximate amount of storage space required for the specified number. You can use this approximate calculation to evaluate whether you have enough free space on the disk to avoid database overflow. The default capacity of the Administration Server database is 400,000 events. The maximum recommended capacity of the database is 45 million events.

The application checks the database every 10 minutes. If the number of events reaches the specified maximum value plus 10,000, the application deletes the oldest events so that only the specified maximum number of events remains.

When the Administration Server deletes old events, it cannot save new events to the database. During this period, information about events that were rejected is written to the operating system log. The new events are queued and then saved to the database after the deletion operation is complete. By default, the event queue is limited to 20,000 events. You can customize the queue limit by editing the KLEVP_MAX_POSTPONED_CNT flag value.

Page top
[Topic 30023]