...
Input table /DVD/MON_SDTRI1 sets KPI’s rules for selecting the right transmissions. The table has the following fields:
KPI name | The same technical name as in the KPI definition |
Rule ID | Index of the rule of same KPI |
Status | Status of the sent object. Possible options are: WAITING - Waiting status INFUTURE - Send in future INCONSIST - Inconsistent, Still no entry in the queue DELIVERED - Transmitted SEND - Send ERROR - Cannot process the message |
Send method | Transmission method code (via Internet, Fax, etc.) [optional] |
Sender | Name of Sender [optional] |
Recipient | Email address of recipient [optional] |
Subject | Document title [optional] |
Add to detail | Add relevant transmissions found for KPIs also to detail table (Yes/No) |
Active | Rule is active (Yes/No) |
Changed user | Last change by user [automatically filled] |
Changed at | Last change date and time [automatically filled] |
Created user | Created by user [automatically filled] |
Created at | Created date and time [automatically filled] |
Defining KPIs via input tables offers higher scalability to create KPIs based on customer needs without any coding. The collector provides also detailed output in a detail table for relevant KPIs. The detail table is called /DVD/MON_SDTRD1 with the following fields:
Status |
Send method |
Sender |
Recipient |
Title |
Message number |
Send date |
Send time |
Message text |
Some KPIs are provided in standard delivery with the collector as examples:
...
- Create KPI definition
- Define KPI rules for collecting statistics
- Save customizing, add the KPI to the monitoring profile, and you are DONE
- Check the results of KPI after the first run of the collector job
