Page tree
Skip to end of metadata
Go to start of metadata

You can use the msgText rule to specify the message format for the subject line 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 
CPU_13 
HoustonCPU_03

CP_1 
CPU14

Wildcard usage in msgText: Examples

Without wildcard/AS/EVENTSPRING/ALERT/MSG/NT_CPU/CPU_0/LOGErrorLvl/msgText
With wildcard/AS/EVENTSPRING/ALERT/MSG/NT_CPU/CPU_{re:*}/LOGErrorLvl/msgText

For information about prerequisites for using wildcards, see Using Wildcards to Represent PATROL Instance Names

The regular expression rules can be applied only when the value of the WildcardsAppClass configuration variable is modified.

msgText Configuration Variable 

Rule

msgText

Configuration Variable

/AS/EVENTSPRING/ALERT/MSG/ object /msgText
/AS/EVENTSPRING/ALERT/MSG/ object /msgTextINFORMATION
/AS/EVENTSPRING/ALERT/MSG/ object /msgTextWARNING
/AS/EVENTSPRING/ALERT/MSG/ object /msgTextALARM

Values

message_replacement_text
message_replacement_variables
message_replacement_text_and_variables

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

Notes

  • If you do not specify INFORMATION, WARNING or ALARM, the same message format is used for all events.
  • 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.
  • No labels