Event properties

When you select an event, its properties are displayed at the bottom of the panel, where you can edit them. A tooltip over the event box shows all the event properties available as variables that you can use to define the action properties.

When you choose the event properties, you define a filter for all the events that you want to monitor and manage. The most meaningful properties you choose are logically correlated and represent the event scope, which is displayed in the event box.

You can add further properties by selecting them from the drop-down list. When you add new properties, they become mandatory, therefore you cannot leave them blank but you can delete them by clicking the close icon.

Mandatory property values are displayed by default, marked by asterisks and with a yellow background. If you try to add an event without specifying one or more mandatory values, the event turns red, the invalid fields are highlighted, and the rule cannot be saved.

You can also add the same property multiple times assigning different values to it. In this case all these properties are logically correlated by the conjunction and, creating a cumulative filter.

For example, when you define your event filter, if you want to exclude some files from it, you can define as event properties all the filenames that match/tmp/tool/oldfiles, and all the filenames that do not match /tmp/tools/newfiles. You can also remove the non-required properties, by clicking the close icon next to them. You cannot remove mandatory properties.

When completing this section, consider that wildcard characters are supported, depending on the event type. When wildcard characters are supported, the wildcard icon is enabled.

Event properties that do not support wildcard characters are identified by the wildcards not supported icon .

Some event properties allow you to specify multiple values separated by semicolon (;). These properties are identified by the multiple filter icon . When you specify multiple values, these values are logically correlated by the conjunction or.

For example, if you create a Job Status Changed event specifying the Job name property as "A;B;C", an action is triggered each time either of the specified jobs changes its status.

Event properties that do not support multiple values are identified by this icon .