The Alerts module links to the PSP Alerts table (u_psp_alerts) to allow you to view alerts generated by the Perspectium application. Alerts are created when the Perspectium application logs errors and when errors are placed directly into this table (as done by Observer). Errors are automatically saved into this table as the application runs and does not require any additional configuration or setup. Using this table allows you to monitor the Perspectium application for errors that may occur.
Using the Error Notification feature, you can subscribe to alerts in this table to be notified by email when there are errors with the Perspectium application such as errors connecting to the Perspectium MBS server.
It is recommended you setup error notification for all alerts in this table that are of “critical” priority. However, if you prefer to be notified on specific errors such as being errors connecting to MBS, the following are different types of alerts generated by the Perspectium application:
|*||*||critical||All application running errors logged will have a priority of “critical”|
|Perspectium.processMultiOutput||Error processing <Perspectium_MBS_Server>: Error: HTTP POST failed: <Error_Message>||critical||Error when the application is unable to successfully share messages to the the Perspectium MBS server on the URL specified in <Perspectium_MBS_Server>. <Error_Message> will give further details on what the error is, including “503” and “504” when the server is unavailable|
|Perspectium.checkMessagePastLimit||Trying to send outbound message <sys_id> that was created more than 10 minutes ago||critical||Error when the Perspectium application is trying to send a message that has been sitting in the outbound messages table (psp_out_message) for more than 10 minutes where <sys_id> is the sys_id of the record in the outbound messages table. This error can be because of an error with the message itself (such as the message is too large or malformed) or an issue connecting to the Perspectium MBS server|
|PerspectiumReplicator.fetchFromQueue||Error fetching from queue <Queue_Name> on <Perspectium_MBS_Server>: <Error_Message>||critical||Error when the application is unable to subscribe to messages from a queue on the Perspectium MBS server. <Queue_Name> represents the queue this instance is subscribing to on the URL specified in <Perspectium_MBS_Server>. <Error_Message> will give further details to why it cannot subscribe to messages, including if there are errors connecting to the server such as “503” and “504” when the server is unavailable|
|PerspectiumReplicator.fetchFromOneQueue||error: <Error_Message>||critical||Error processing a subscribed message with <Error_Message> providing details why the subscribed message could not be processed. This error is after the message has been received from the Perspectium MBS server and as the application tries to process the message's record into the target table|
|Perspectium MultiOutput Processing||error = <Error_Message>||critical||Error when running the scheduled job to share out messages with further details in <Error_Message>. This error will generally also be superseded by errors with the previously mentioned “Perspectium.processMultiOutput” alert|
|Perspectium Replicator Subscriber||error = <Error_Message>||critical||Error when running the scheduled job to subscribe to messages with further details in <Error_Message>. This error will generally also be superseded by errors with the previously mentioned “Perspectium.fetchFromQueue” alert|
|Perspectium.postMulti||Unable to run as the target server or credentials are not configured properly. Please check your Perspectium properties||critical||Error when the application properties or queue properties are not configured properly so the application cannot connect to MBS|
|PerspectiumReplicator.fetchFromOneQueue||Unable to run as the target server or credentials are not configured properly. Please check your Perspectium properties||critical||Error when the application properties or queue properties are not configured properly so the application cannot connect to MBS|
|PerspectiumOutbound.processTargetQueue||unable to process <sys_id> <Error_Message>||critical||Error sharing out a message from a specific outbound messages table. This error may be due to issues with the message itself or connecting to MBS (see the <Error_Message> for further details)|
|*||*||high||High alerts in your instance as configured in Observer|
|*||*||medium||Medium alerts in your instance as configured in Observer|
|*||*||low||Low alerts in your instance as configured in Observer|
The PSP Alerts table contains the “Acknowledge” column and “Acknowledged by” columns for you to be able to specify if someone has reviewed the alert and select who through your own scripting. These columns are made available for your use as the Perspectium application does not automatically acknowledge these alerts.
Below is a zip containing two example alerts you can import into your instance to test if error notifications are working properly. These two errors are examples of the “503” and “504” errors that may occur when the Perspectium MBS server is unavailable