5. What event text should cause notification?
Select or specify the event text that should cause a notification.
You can immediately edit the value that currently appears in the input field or you can select an item
that appears from the drop-down list.
A regular expression is required.
Comments are allowed and whitespace (blank character) is ignored.
This field
is initially supplied with a set of examples you can choose from and
the text filters from each of the currently defined monitors.
The event text may contain special characters which have specific meanings when the regular expression is evaluated.
Some of the special characters and examples of each include:
- .*
- A period followed by an asterisk indicates any number of characters.
For example, dog.* would be
evaluated as dog, doghouse, or dogwood.
- ^
- A caret as the first character implies that the text that follows must be at the beginning of the line
to match.
For example, ^house would not match The house on the hill since house is not at the
beginning of the phrase.
- -->
- Two dashes followed by the greater than sign are used to separate the before and after states when used with
State Changes events. The before state is defined on the left side of the dashes and the after state is defined
on the right side of the greater than sign.
For example, Operating-->Exceptions would match when the state
changed from Operating to Exceptions.
- [text]
- Text enclosed in brackets implies matching on any of those characters.
For example, [Ee]xception
matches on Exception or exception.
- #
- A pound sign indicates the start of a comment. If the event text contains a pound sign, then when the expression
is evaluated the pound sign and all the text that follows is ignored, any leading or trailing blanks around the rest
of the expression are removed, and any embedded blanks in the expression are changed to s so the event
text will match as desired.
For example, if the event text is Not Operating-->Operating # From Not Operating state to Operating State,
then the regular expression is evaluated as NotsOperating-->Operating. The comment is ignored and the embedded
blanks are respected.
If you need to specify your own entry for the event text and you do not want any of the above processing to occur,
then leave out the pound sign and your expression is evaluated as you specified it.
For more detailed information on regular expressions, refer to the documentation on java.util.regex.Pattern class.