====== RFC Destinations availability ======
  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 =====
  * Set the destinations to check in the table
  * **You cannot use regular expressions** you must explicitly set destination names
  * Use the **Load RFC destinations** button to get a list extracted from your system, and select the ones you want to test
  * 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 =====
^Parameter^Description^
^Active|Use this field to activate or deactivate a line of configuration.|
^RFC Destination|Defines the destination to check.|
^Instances to exclude|A coma separated list of application servers: Use that field if there are AS from which you don't want to check the destination|
^Check Mode|AUTO : 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.|
^Strict|If selected, the connection to the destination must work from all application servers. Otherwise, a connection working from at least one AS is sufficient.|
^Severity|The level of severity of the alarm generated by this line of surveillance.|
^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|If checked, this line of surveillance will be used for alarm generation.|
^Metric|If checked, this line of surveillance will be used for metric generation.|
^Report|If checked, this line of surveillance will used for showing threshold and severity in the daily report|
===== Examples =====
 
^Active^RFC Destination^Instances to exclude^Check Mode^Strict^Severity^Auto clear^Alarm tag^Alarm^Metric^Report^
|true|VERTEX_MS0018| |AUTO|true|CRITICAL|true| |true|false|false|

**Effect** : Checks VERTEX_MS0018 destination from all application servers. Sends a CRITICAL alarm if the destination can't be reached from one AS.
===== Examples =====
 
^Active^RFC Destination^Instances to exclude^Check Mode^Strict^Severity^Auto clear^Alarm tag^Alarm^Metric^Report^
|true|VERTEX_MS0018|mysap_PRD_00|AUTO|false|CRITICAL|true| |true|false|false|

**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 =====
 
^metricId^metricUnit^metricTarget^metricDescription^
|RFC_DESTINATION_AVAILABILITY_PER_AS|status|[INSTANCE][DESTINATION]|The status of the destination per AS|
|RFC_DESTINATION_AVAILABILITY_PER_SYSTEM|status|[DESTINATION]|The global status of the destination. True if works from all application servers, false instead.|