This report is a monitoring tool which can detect queues or of idocs with alarming statuses and inform the responsible monitoring consultants about it via email.
| Table of Contents | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Queue status
An Email Alert can be sent to responsible persons when FSM queues stop working/are not active. The program retrieves existing queues and checks if their names/statuses match the selection criteria. The program should be executed by a background job every minute for near-real-time monitoring, in order to alert the responsible consultants as soon as issues occur.
Field name | Description | Recommended value | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SYSFAIL, CPICERR, STOPPING, STOP, WAITSTOP, NOSENDS, WAITING
READY
RUNNING | Select which queue statuses should be considered for queue alerts. The most common statutes are displayed as checkboxes. | Select all | ||||||||||||
Min. queue age (in minutes) | Certain queue statuses are not alarming right away, but only after a longer period of time. Optionally enter the minimum queue lifespan for queues with status WAITSTOP, WAITING and READY. Queues with shorter lifespan will not be considered alarming (won’t be added to emails). If the field is left empty, all queues with a given status will be displayed. | 5 | ||||||||||||
Number of entries in queue | Enter the critical number of entries in queues with status RUNNING. | 1000 | ||||||||||||
Additional monitored statuses | Enter other statuses relevant for queue alerts.
| |||||||||||||
Queue name | Filter queues relevant for queue alerts by the queue name. | /PACG/* | ||||||||||||
Email (Queue Alerts) | Enter the emails to which queue alerts should be sent. |
Example SMQ1 Alert displayed in transaction SOST:
Old AL11 files deletion
Message log files can be generated if the ‘Directory’ field is filled. Delete old log files from the directory specified in that field.
Delete older than (Days) | Specify the number of days which should be taken away from the system’s date (minus 1) to determine the date relevant for log file deletion. The date is searched for in log files names.
| ||
|---|---|---|---|
Deletion Period (Days) | Determine how many days should be deleted, starting from the date calculated based on the field above. If '1' is entered, only files from the day calculated based on the field above will be deleted. If '2' is entered, also the day before will be deleted. Example: System date: 29.12.2021 Delete older than (Days): 7 Deletion Period (Days): 5 Files with date 21.12.2021 and 20.12, 19.12, 18.12, 17.12 will be deleted. |
Please note that both of the fields above must be filled in order for file deletion to be performed.
Message Broker status
Generate a Message Broker alert if for a given logical port a WebService System Fault or WebService Application fault is detected.
Logical port | Logical ports can be found in transaction https:/ |
|---|
/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953259 | |
Email to which a Message Broker alert should be sent |
An example alert:
IDOCs in error status
| Status | ||
|---|---|---|
|
If IDoc alert should be sent, enter at least one email address. The program is designed for incoming IDocs in status 51 but you can select different status values as well.
For the first run, the program selects IDocs from the past week. If error IDocs are found for the company, then in table /PACG/ECM_ALERRI an entry with the last IDoc number is created. The next time the program selects IDocs greater than the stored IDoc’s number. The result of the program is an email:
