Instances availability

Purpose

This monitor is dedicated for surveillance of ABAP application servers (AS). It will send an alarm if an AS cannot be reached, if it is not registered on the message server or if is has been restarted.

Configuration hints

You need to define the expected AS in the surveillance table (Use autodetect) and set the appropriate levels of severity. If an unexpected AS is found, the monitor will also generate an alarm.

Atomic fields

Severity unexpected instance	Severity of the alarm to send if an unexpected instance is found

Surveillance table

Parameter	Description
Mandatory	If checked, the instance must be registered and responding.
Instance name	The expected instance : [HOST]_[SID]_[NUMBER]
Availibility severity	The severity of the alarm sent if the AS is not responding.
Restart Severity	The severity of the alarm sent if the AS is restarted.
Auto clear	If checked, the alarm will be cleared as soon as the alarm condition is not met anymore.
Alarm tag	This field allows to add custom text within the alarm message. %MSG% variable will contain the actual generated message and can be used such as: “my_prefix %MSG% my_suffix”. By default, tag will be used as prefix.
Alarm	Enable of alarm sending
Metric	Enable for metric sending

Examples

Mandatory	Instance name	Availibility severity	Restart Severity	Auto clear	Alarm tag
true	mysap_PRD_00	CRITICAL	WARNING	true

Effect : Send a CRITICAL alarm if instance mysap_PRD_00 is not responding, and a WARNING if it is restarted.

Examples

Mandatory	Instance name	Availibility severity	Restart Severity	Auto clear	Alarm tag
false	mysap_PRD_01	CRITICAL	DISABLED	true

Effect : Ignore the fact that the instance is not responding or registered, ignore if restarted. The purpose of this line is to declare expected instances, so the probe can detect *unexpected* instances

Generated metrics

metricId	metricUnit	metricTarget	metricDescription
INSTANCE_AVAILABILITY	Status	INSTANCE	Sends TRUE if the instance is available, FALSE instead.