Event logger¶

Introduction

The Event logger records the properties of one or more event types of interest generated by a specific node and/or by its child nodes, or by any node in the project, and stores them in a database.

Configuration of the database for the Event logger

Q Studio automatically configures the databases for the Event loggers (see Working with databases).

When the database in which to store the data is selected in an Event logger, Q Studio automatically creates a table in the database for each event type monitored, in which each column corresponds to a data/property of interest of the event.

Events source

In an Event logger, for each event type of interest it is possible to choose which source to consider:

a specific object
a project node with its child nodes/objects (in this case, typically a node that contains several objects that generate the events of interest is chosen)
all the project objects

The logger then records the data of all the events of interest generated by all the objects considered as sources.

Through the Non-interactive sessions excluded property setting, it is also possible to record only the events generated by user interactions with the application’s graphical interface, therefore excluding events generated by other logics, for example, a change event (see Change Events).

Audit through Event logger

UNIQO makes it possible to record the operations performed by users at runtime, for example, to perform quality checks or to certify applications in specific contexts. To do this, specific audit events are generated, in which to record data through an Event logger. Audit events concern the following operations:

write on variables
edit node attributes
create and destroy nodes
execute methods
login and logout

Note

for example, an audit event is generated when a user clicks an object which invokes a method. However, it is not generated when the same method is invoked by an application logic independent of the user’s actions.

Audit event types

Below, the audit event types most commonly recorded are described in summary:

Audit event type	Description
AuditEventType	All audit events
AuditNodeManagementEventType	Creation or destruction of nodes
AuditWriteUpdateEventType	Change of the variable value or a node attribute
AuditUpdateMethodEvent	Execution of a method
AuditConditionEventType	Execution of alarm methods
AuditConditionAcknowledgeEventType	Execution of the alarm Acknowledge method
AuditConditionCommentEventType	Execution of the alarm Add comment method
AuditConditionConfirmEventType	Execution of the alarm Confirm method
AuditConditionEnableEventType	Change of the alarm’s enabled/disabled status
RecipeApplicationEvent	Recipe applications
UserSessionEvent	User login and logout events