Page Comparison

Every notification rule will have a Matching Rule to assign a notification rule to components. Matching rules use Iguana supports glob expression and tag matching to apply customized rules according to your requirements(*), boolean(and/or), or regular expressions (regex) with Tags to create matching rules. To use regex, simply enclose the expression in slash characters /<regex>/.

The table below provides a set of rules an overview of example pattern matching techniques you can combine to create a matching rule.

Conditions are the notification rule criteria. If a condition is met, a log is generated and sent to the notifier component.

There are four types of conditions used to trigger notifications:

1. Errors: triggered if an error message is generated in the component(s) logs.

2. Inactivity: triggered if a component(s) has not processed messages in the specified time (in minutes).

3. Queue: triggered if a component(s) queue count exceeds the threshold value set.

4. Log Contains: triggered if a component(s) logs contain a matching pattern.

The Log Contains rule is the most flexible type of notification rule as you can leverage default logs generated by Iguana or custom log messages invoked from the Translator (see Custom Logging). The pattern can use strings (ex. component stopped) or regex patterns. To use regex, simply enclose the expression in slash characters /<regex>/.