You can use the msgBody rule to specify the message format for the body of the notification message. You can specify different formats for different types of alerts and for specific PATROL objects (applications, instances, or parameters).
Note
You can also use wildcards to create one rule that matches several alerts. You can use the following set of characters to identify a wildcard: {re:*}. For more information, see the following examples:
Wildcard Usage | Matches | No Match |
|---|---|---|
CPU_{re:*} | CPU_03 | CP_1 |
The regular expression rules can be applied only when the value of the WildcardsAppClass configuration variable is modified.
For information about prerequisites for using wildcards, see Using Wildcards to Represent PATROL Instance Names.
msgBody Configuration Variable
Rule | msgBody |
|---|---|
Configuration Variable | /AS/EVENTSPRING/ALERT/MSG/ object /msgBody |
Values | message_replacement_text |
Example | %HOSTNAME% has CPU Processor time of %PARAMETER_VALUE% for time zone %TIMEZONE% for %OS_TYPE% For more information about replacement variables, see NOTIFY_EVENT Fields. |
Menu Command Access | Event Management > Alert Settings > Alert Messages > Default Message Format |
Note
If you do not specify INFORMATION, WARNING or ALARM, the same message format is used for all events.
An example of a reworded message template is:
%HOSTNAME% has CPU Processor time of %PARAMETER_VALUE% for time zone %TIMEZONE% for %OS_TYPE%
At run time, the message could be displayed as:
Mercury has CPU Processor time of 99 for time zone Eastern Standard Time for NT 5.0 Service Pack 1
Note
A special instance name of _ANYINST_ can be used for all instances of a parameter. If object is not specified, then the configuration variable defines the default message format.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks