Main: General
Attribute name |
Description |
Name |
The name of automated action item. It is recommended to use descriptive names for the items. |
Description |
The description field explains the meaning and usage of the automated action item. |
Responsible person |
The selected person is attached to the automated action item as a responsible person. By default, the person who has created the automated action item is filled here. |
Status |
If automated actions item is disabled it will not do anything. Only enabled automated actions items will process the identified events automatically. An automated action item can have following statuses:
Use the Tasks menu to change the status of automated action item. |
Event status after processed |
The automated action item can process events automatically from the Events queue by the event identification rules that are defined to the automated actions item. Once the automated action item has completed all the Taken actions that are defined to the automated actions item, it can set the processed event in to one of the following statuses:
Alternatively, an option 'Do not change event status' can be selected if the automated action item should not change the status of the event after automated processing. |
Main: Event identification rules
Attribute name |
Description |
Source |
The source determines which events are processed with this automated action item. The automated action item processes only the events that originate from the selected source (Miradore/External). Note! If you select External, you can input the source, event class and the event name manually. For example, if the source is external, you can enter the name of the external system to the source field. |
Source host |
The source host attribute can be used to specify the source host of the events that should be processed by this automated action item. It is possible to use ' * ' as a wildcard. A wildcard character can be used to substitute any other character or characters in the field. |
Time of occurrence |
Here you may select the time and days of week when the automated actions item is performed. When an automated actions item is performed, it identifies events from the Events queue by the event identification rules that have been defined to the automated action item. Then the item processes the items according to the Taken actions section of the automated actions item. Thus, the selected days and times also affect to the times when the SMS or email notifications are received from the event monitoring feature of Miradore. |
Identification rules |
Identification rules are used to define the events that should be processed by this automated actions item. Multiple identification rules can be defined for a single automated actions item. When adding an identification rule, there is a 'Test rule' button in the pop-up window. The 'Test rule' button shows the number of events to which the automated actions item would apply with the current settings. Use this button to adjust the event identification rules. |
Event class |
The event class specifies the class or category of events that should be processed by this automated action item. For example, selection 'Software management' would mean that only events that are related to software management will be processed by this automated action item. |
Event name |
Event name is a subcategory of Event class attribute. The event name specifies which events should be processed by this automated action item. For example, selection 'System settings changed' would mean that only events whose event name is System settings changed would be processed by this automated action item. |
Value |
The meaning of the value attribute depends on the selected Event class and Event name. However, the value can be used as a threshold value to filter the events that have the correct Event class and Event name. For example, if Event class = Asset management and Event name = Asset warranty expiring, then value 'Less than 14' would mean that the automated action item will automatically process all such asset warranty expiring -events that have less than 14 days left of the asset warranty period. With the other types of events, the value field can be used to filter the events. Depending on the selected event name, the value can be associated with the amount of days, percentage, or megabytes. |
Severity |
The severity level attribute specifies the minimum severity level of the events that should be automatically processed with this automated actions item. See the possible values and their descriptions below. Normal: All events that meet also the other event identification rules of this automated action should be processed by this automated action item since normal is the lowest level of severity that an event can have. Info: All events whose severity level is at least Info, and which meet also the other event identification rules of this automated action item should be processed by this automated action item. This means that events whose severity level is Normal should not be processed by this automated actions item. Warning: All events whose severity level is at least Warning, and which meet also the other event identification rules of this automated action item should be processed by this automated action item. This means that events whose severity level is Info or Normal should not be processed by this automated actions item. Critical: All events whose severity level is Critical, and which meet also the other event identification rules of this automated action item should be processed by this automated action item. This means that events whose severity level is Info, Normal, or Warning should not be processed by this automated actions item. |
Asset location |
Asset location attribute can be used to specify the location of the computers that are the source of the events which should be processed by this automated action item. Notice! Since this attribute is an asset management specific field, it is not shown for all event classes. |
Asset organization |
Asset organization attribute can be used to specify the organization of the computers that are the source of the events which should be processed by this automated action item. Example: Asset organization = Head Quarters, would mean that the actions defined by this automated action item will be only applied to asset configuration items of which organization is “Head quarters”. Notice! Since this attribute is an asset management specific field, it is not shown for all event classes. |
Asset configuration |
Asset configuration attribute can be used to specify an individual asset configuration item which events should be processed by this automated action item. Notice! This attribute is specific to events related to asset configuration items so it is not available for all events. |
Quality index report settings |
Quality index report settings attribute can be used to specify an individual quality index report item which events should be processed by this automated action item. Notice! This attribute is specific to events related to quality index report items so it is not available for all events. |
Contract |
Contract attribute can be used to specify an individual contract item which events should be processed by this automated action item. Notice! This attribute is specific to events related to contract items so it is not available for all events. |
License |
License attribute can be used to specify an individual license pool item which events should be processed by this automated action item. Notice! This attribute is specific to events related to license pool items so it is not available for all events. |
Incident |
Incident attribute can be used to specify an individual incident item which events should be processed by this automated action item. Notice! This attribute is specific to events related to incident items so it is not available for all events. |
System task |
System task attribute can be used to specify an individual system task which events should be processed by this automated action item. Notice! This attribute is specific to events related to system tasks so it is not available for all events. |
Connector |
Connector attribute can be used to specify an individual connector item which events should be processed by this automated action item. Notice! This attribute is specific to events related to connector items so it is not available for all events. |
Managed software |
Managed software attribute can be used to specify an individual managed software item which events should be processed by this automated action item. Notice! This attribute is specific to events related to managed software items so it is not available for all events. |
Main: Taken actions
Attribute name |
Description |
Create incident |
Miradore's event monitoring system can automatically create an incident into Miradore based on events. New incidents are generated into the Incidents view according to the incident parameters that are selected from the settings of the Create incident action. |
Distribute package |
Miradore's event monitoring system can distribute a selected package automatically to the source asset of the identified event. Use the Action interval drop down list to define an interval for the package distribution. |
Send HTTP notification |
Miradore's event monitoring system can send an HTTP notification about events to a specified URL address. Authentication and contents of the HTTP message can be configured for the notification. See also the table "Send HTTP notification parameters" for more details. |
Send SMS |
Miradore's event monitoring system can send an SMS notification about events automatically to a user or AD group. The alert message includes information about event´s severity, event count, event update date and the event subject. This feature can be enabled/disabled and configured from the system settings of Miradore (Administration > System settings > Main > SMS settings). |
Send email |
Miradore's event monitoring system can send an email notification about events automatically to a user or AD group. The alert message includes information about event´s severity, event count, event update date and the event subject. See also the table "Send email parameters" for more details. |
Main: Send email parameters
Parameter name |
Description |
Add link to CI |
This selection determines if the link to the configuration item is appended to the email alert. There are following selection available:
|
Add link to event |
This selection determines if the link to the event item is appended to the email alert. There are following selection available:
|
Recipient type |
Recipient types:
|
Recipients |
The email address(es), where to an email alert will be sent, can be added here. It is possible to write the address(es) here, or use the drop-down list to select the recipient(s). Use semicolon (;) as a delimiter to separate multiple recipient addresses from each other. Note! This field is mandatory. |
Sending interval |
From this drop-down list, it is possible to choose how often the notification message will be sent. There are following intervals defined:
|
Main: Send HTTP notification parameters
Parameter name |
Description |
URL |
URL address of the web service to which the HTTP notification is sent. Note! This field is mandatory. |
Authentication method |
Method for HTTP authentication. The options are:
|
User name |
User name for HTTP authentication. |
Password |
Password for HTTP authentication. |
Message section (prefix) |
Prefix that will be added in the beginning of each HTTP notification message. Following variable can be used in the prefix and postfix sections:
|
Message section (attributes) |
Message section(s) that will be added between the prefix and the postfix in the HTTP notification. Multiple 'attributes' message sections may be added into a single HTTP notification message. HTTP notifications are sent once in a minute by the System task 'Send HTTP notifications'. The system task groups events that have been created during the one minute time frame in a single HTTP notification. The events that are related to the same configuration item are grouped into the same HTTP notification. For example: Someone edits the location and status for an asset configuration item. The monitors "Asset status modified" and "Asset's location modified" are enabled. The two events will be included into a single HTTP notification message. Following variables can be used in the attributes section:
|
Message section (postfix) |
Postfix that will be added at the end of each HTTP notification message. Following variable can be used in the prefix and postfix sections:
|
Main: Additional information
Attribute name |
Description |
Attachments |
An attachment file can be added to this item. About attaching files. |
Comments |
A comment message can be added here. |