Common settings

Configuration tips & tricks common to most monitors

Multi thresholds syntax

This syntax allows to set multiple thresholds/severity associations within a single threshold field for the monitors that supports it

Example:

value > 80% -> WARNING

value > 90% -> CRITICAL

Syntax

You can associate a severity transition to a value

[SEVERITY]2[SEVERITY]:[VALUE]

SEVERITY can be selected amongst these possible letters:

G: Green (No alert)

W: Warning

m: minor

M: Major

C: Critical

VALUE is the threshold, without units

Example

G2W:50 -> 50 is the threshold to set a WARNING

W2M:80 -> 80 is the threshold to move from WARNING to MAJOR

M2W:70 -> 70 is the threshold to move from MAJOR to WARNING

You can combine multiple associations on the same line: G2W:50 W2M:80 M2W:70

With this example: G2W:80 W2M:90, the below severity will be used:

value < 80 -> No alarm

value = 80 -> WARNING

value = 89 -> WARNING

value >= 90 -> MAJOR

Filter syntax

Most monitors provide filtering capabilities for settings specific rules.

Those filters help to match a particular instance, user or client by example.

This is the behavior and syntax to use:

syntax	effect	example
* or .*	Matches any string
abc	Matches any string containing abc	admin matches superadmin
abc,xyz,...	A coma separated list, matches any string containing at least one member	admin,extended matches extended_user
!abc	Matches any string not containing abc	!admin does not match superadmin
!abc,!xyz,...	A coma separated list of exclusions	!admin,!extended does not match admin_user
abc+xyz+...	Match string only containing all members	admin+user does not match admin_password
Regexp	Match strings matching a valid regular expression	admin.* matches admin_password

Note:

abc* does not match any string starting with abc

abcd -> no match

abccc -> match

In such case you must use abc.* (as per regex syntax)

Exclusion rules

It is possible to set rules to exclude a particular set of data from the monitoring.

Those rules must be defined before the actual monitoring rules.

To set an exclusion rule, set the appropriate filter and select DISABLED as severity

Each result item matching the rule will be removed from the pool of results and won't be processed by next rules

Example

Shortdumps

Active	Instance	Client	Error Id	Report	Time period (min)	Max dumps	Aggregates	Severity	Auto clear	Alarm tag	Alarm	Metric	Report
true	*	800	*	*	15	10	true	DISABLED	true	true	false	true
true	*	*	*	Z_FI_REPORT	15	10	true	DISABLED	true	true	false	true
true	*	*	*	*	15	10	true	WARNING	true	true	false	true

In this example, all shortdumps will be monitored, except for the ones from client 800 or on report Z_FI_REPORT