products:promonitor:6.8:monitorsguide:netweaver:rfcdestinationsavailability

RFC Destinations availability

Purpose

This monitor will check that a destination can be reached from all application servers, using either a RFC ping or an authentication, based on RFC destination configuration.

Configuration hints

Only one destination per line must be declared, you cannot use regular expression in the filter. You can use the load destination button to discover available destinations registered in a system.

Use the strict button to indicate if it is mandatory for a destination to be reachable from every application server. You can exclude an application server from the check if necessary.

Surveillance table

ParameterDescription
ActiveUse this field to activate or deactivate a line of configuration.
RFC DestinationDefines the destination to check.
Instances to excludeA coma separated list of application servers: Use that field if there are AS from which you don't want to check the destination
Check ModeAUTO : the probe will detect if the destination needs authentication or if a simple PING is enough. NO_AUTHENTICATION : The check is done via a simple PING.
StrictIf selected, the connection to the destination must work from all application servers. Otherwise, a connection working from at least one AS is sufficient.
SeverityThe level of severity of the alarm generated by this line of surveillance.
Auto clearIf checked, the alarm will be cleared as soon as the alarm condition is not met anymore.
Alarm tagThis 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.
AlarmIf checked, this line of surveillance will be used for alarm generation.
MetricIf checked, this line of surveillance will be used for metric generation.
ReportIf checked, this line of surveillance will used for showing threshold and severity in the daily report

Examples

ActiveRFC DestinationInstances to excludeCheck ModeStrictSeverityAuto clearAlarm tagAlarmMetricReport
trueVERTEX_MS0018 AUTOtrueCRITICALtrue truefalsefalse

Effect : Checks VERTEX_MS0018 destination from all application servers. Sends a CRITICAL alarm if the destination can't be reached from one AS.

Examples

ActiveRFC DestinationInstances to excludeCheck ModeStrictSeverityAuto clearAlarm tagAlarmMetricReport
trueVERTEX_MS0018mysap_PRD_00AUTOfalseCRITICALtrue truefalsefalse

Effect : Checks VERTEX_MS0018 destination from all application servers, except mysap_PRD_00. Sends a CRITICAL alarm if the destination can't be reached from any application server.

Generated metrics

metricIdmetricUnitmetricTargetmetricDescription
RFC_DESTINATION_AVAILABILITY_PER_ASstatus[INSTANCE][DESTINATION]The status of the destination per AS
RFC_DESTINATION_AVAILABILITY_PER_SYSTEMstatus[DESTINATION]The global status of the destination. True if works from all application servers, false instead.
/home/clients/8c48b436badcd3a0bdaaba8c59a54bf1/wiki-web/data/pages/products/promonitor/6.8/monitorsguide/netweaver/rfcdestinationsavailability.txt · Last modified: 2024/05/01 18:35 (external edit)