Collector for RFC Ping Tests
The technical name of the Collector for RFC Ping Tests is /DVD/MON_CL_COL_RFC.
This collector collects KPIs about RFC ping tests. The KPIs are specified via the KPI definition and the input table /DVD/MON_RFC_I1. It contains the following fields:
|
System ID |
System ID |
|---|---|
|
RFC destination |
Logical destination |
|
Connection test |
Whether a connection test is performed |
|
Authorization test |
Whether an authorization test is performed |
|
Ping test |
Whether a ping test is performed |
|
Changed by user |
Last changed by user [automatically filled] |
|
Change date |
Last change date [automatically filled] |
|
Created by |
Created by user [automatically filled] |
|
Created at |
Creation time [automatically filled] |
The three test groups for the connection, authorization and ping tests only make sense when they are set for the connection types ABAP (3) and Internal (I).
For the connection types TCP/IP (T) and HTTP (G/H), the collector only performs the connection test. The authorization and ping tests are automatically excluded if they are set in the input table. Other RFC connection types are not supported.
Some KPIs are provided in the standard delivery with the collector as examples:
|
KPI name |
Description |
Unit |
|---|---|---|
|
RFC_IN_AUTHERR |
Number of failed RFC tests – RFC check with authorization |
Count |
|
RFC_IN_CON_ERR |
Number of failed RFC tests – RFC check without authorization |
Count |
|
RFC_IN_PINGERR |
Number of failed RFC tests – ping server IP |
Count |
|
Note: All standard RFC ping test KPIs have the prefix RFC_IN_*. |
||
