Information | Actions and Notification
Macros are commonly used in Thresholds, Notifications and Templates and will be replaced with the relevant information at run time. For example, if you were to add 'Processor Utilization at time of event was {Attribute.CurrentValue}' to an event notification, this would be translated whenever the event occurs so that you would receive a message stating 'Processor Utilization at time of event was 99.995%'. For practical examples of using Macros, see the section on Notification Tips.
Available Macros
| Macro | Description |
|
{CI} |
Name of the Configuration Item the Event was fired on. |
|
{TIME} |
Time the Event occurred. |
|
{DATE} |
Date the Event occurred. |
|
{IPADDRESS} |
IP Address of the CI where the Event occurred. |
|
Event Definition Specific Macros |
|
|
{EVENT.NAME} |
Name of the Event Definition. |
| {EVENT_DEFINITION.ID} | Name of the Event, Aggregate Event Definition, or Policy. |
|
{EVENT.SEVERITY} |
Severity of the Event. |
|
{EVENT.ID} |
Unique ID of an Event. |
|
{EVENT.STATUS} |
Status of the Event. Ok or Failed. |
|
{EVENT.STATUS_VALUE} |
Status of the Event in numeric format. 0 = Ok, 1 = Failed. |
|
{EVENT.REMEDIATION_URL} |
URL entered in Event Definition’s Remediation URL field. |
|
{EVENT.COMMENT} |
Comment entered for the associated Event Definition. Useful for providing instructions or recommended fixes in the case an Event occurs. |
|
{EVENT.CUSTOM_1} |
Values entered for the custom field of an Event Definition (five custom fields are available). |
|
Macros for Attributes Related to the Event Definition |
|
|
{ATTRIBUTE.CURRENTVALUE} |
Current value of the Attribute associated with the Event Definition. |
|
{ATTRIBUTE.NAME} |
Name of the Attribute associated with the Event Definition. |
|
Macros for the Configuration Item associated with the Event Definition |
|
|
{CI_INFO.CONTACT} {CI_INFO.DEVICETYPE} {CI_INFO.LOCATION} {CI_INFO.MACADDRESS} {CI_INFO.NOTES} {CI_INFO.OS} {CI_INFO.SERIALNO} {CI_INFO.SOFTWARE} {CI_INFO.TAG} |
Values for the specified profile fields of the Configuration Item associated with this Event. |
This best practice guide describes a few commonly used scenarios for Actions within FireScope. Useful for giving you ideas on how to get the most value from FireScope.
Tips for Notifications of EventsUse these helpful tips to decide when and how you wish FireScope to send notifications or start remediation when critical events occur.
This document describes how to create or edit Actions in FireScope BSM.
Configuring Notification EscalationEscalation notification is often a requirement when monitoring key services and devices in an IT infrastructure. Organizations want to ensure that automated escalation is made when a critical alert has not been acknowledged within a certain time period.
Escalation NotificationThe Escalation Period is a global setting in the Administration features to determine how many minutes to wait for an acknowledgment of an event to occur before sending a secondary notification to an additional user.
For step by step instructions on setting up Service Groups, managed Configuration Items and your service-levels, browse the FireScope Administration Guide.