Managing Pega Predictive Diagnostic Cloud notification subscriptions
As a Pega Predictive Diagnostic Cloud™ operator with a manager role, you can request that email digests and event notifications be sent to specific mailboxes, so that the recipients stay informed about system health information.
The following types of notification are available:
- Schedule-based email digests are for business sponsors and program managers
- Event-based notifications are for operations managers or operations staff
You can create subscriptions for a combination of monitored servers. You can choose a complete Improvement Plan, a summary of recent issues, a periodic new issues digest, or a one-time notification.
You can select the following types of notification to subscribe to or to modify.
Scheduled email digests
Subscribers receive these digests on a regular basis as part of system governance to stay up to date with the status of a monitored system.
- Improvement Plan: Details – A complete Improvement Plan for the selected system, with cases divided into categories: Alarms, Application Logic, Connectors, Database, Decisioning, Pega Platform™ Tuning, and Exceptions. Click a case to view it in Pega Predictive Diagnostic Cloud.
For more information, see Pega Predictive Diagnostic Cloud Improvement Plan overview.
- Improvement Plan: Summary – A summary of cases divided by category. It contains the total numbers of cases, occurrences, and assigned cases. Icons identify affected areas. The effect on the system is shown as the amount of time spent on resolving requests along with a comparison of the time spent the previous week, expressed as a percentage.
- New Items Daily Scorecard – Notifies of all new issues that have occurred within the 24-hour period before the digest is sent.
Subscribers receive the following notifications whenever the relevant events occur:
- Agent disabled – An agent has become disabled. The monitored system has sent a PEGA0010 alert.
- AlarmTicketFailure – Pega Predictive Diagnostic Cloud has failed to connect to Global Customer Support to create an alarm ticket, and it has created an OPS0006 event.
- Alerts throttled – The monitored system has generated an excessive number of alerts in the past few minutes. The monitored system has sent a PEGA0044 alert.
- Cache force reduced – When records in the rule assembly cache, a personal cache, or a property conclusion cache reach or exceed a specified limit, the system invalidates older entries, which affects performance. The monitored system has sent a PEGA0017 alert.
- Clock drift time exceeded – The system clock on a node is out of sync with other nodes in the cluster. The monitored system has sent a PEGA0055 alert.
- Conflicting Queries Detected – Conflicting queries have caused a blockage in the PostgreSQL database system. The monitored system has sent a PEGA0106 alert.
- Connect FTP Failure – A Connect-FTP method call has failed while trying to copy a file from one file system to another file system by using the File Transfer Protocol (FTP). Pega Predictive Diagnostic Cloud has created an INTG0002 event.
- Connect-Rest Timeout – A Connect-REST method call has timed out before it received a response. Pega Predictive Diagnostic Cloud has created an INTG0001 event.
- Connectors Outbound Exceptions – The outbound mapping of a connector has failed before Pega Platform™ created a request. Pega Predictive Diagnostic Cloud has created an INTG0003 event.
- Database Configuration Issues – Pega Platform has generated a PostgreSQL connection capacity exception or an Apache Tomcat server connection pool exception. Pega Predictive Diagnostic Cloud has created an OPS0007 event or an OPS0008 event, respectively.
- Email Transport Errors – Email communication issues have caused the monitored system to send an exception, for example, Can’t connect to SMTP host. Pega Predictive Diagnostic Cloud has created an SMTP<number> event.
- Health status change – The health status of a system in the Enterprise Health console has changed. One or more critical events have been recently received to change server health normal to
Critical, or the server has failed to send a health status message.
- Long requestor time – The system master agent has detected that a session has been busy for an excessive amount of time. The monitored system has sent a PEGA0019 alert.
- Memory pool collection – A system reports issues with managing Java memory pools, and not enough virtual memory is available. The monitored system has sent a PEGA0028 alert.
- New alert action item – The system has created a new case for a performance or operations issue. To ensure that you receive messages only about significant issues, this notification is sent only when a case has more than 10 associated events.
- New Exception – An exception has occurred on a monitored system. Exceptions are unplanned events that interrupt the flow of a program while it is running. A system that operates correctly should not show any exceptions.
- Pulse down – A monitored node reports that the system pulse has not run recently, and the node has not received recent rule and reference data changes.
- Requestor Lock Exception – The monitored system is not processing a browser request because the session (requestor) has been locked for an excessive amount of time while processing prior requests. The monitored system has sent a PEGA0086 alert.
- Requestor Pool Problem – A service was unable to process a service request for a pool or package because of a requestor pool lock. Pega Predictive Diagnostic Cloud has created an OPS0003 event.
- Rule cache disabled – The rule cache is disabled on a monitored node. The monitored system has sent a PEGA0022 alert.
- Service SLA violation – The performance of a service does not comply with the service-level agreement (SLA), and a fallback activity is in use. The monitored system has sent a PEGA0087 alert.
- SLA Reporting: Failed Requests – The number of requests that have failed within the set time window has exceeded the threshold. To configure the threshold, go to Diagnostic Cloud > Scorecards > SLA Notifications.
- SLA Reporting: Requests past SLA – The number of requests that have exceeded the SLA within the set time window has exceeded the threshold.
Feature-specific event notifications
In addition to the standard Pega Platform events, several alerts are generated only for specific features. Subscribers receive the following notifications only if monitored systems use the relevant features:
- Adaptive Decision Manager Memory – The Adaptive Decision Manager service is using excessive memory. The monitored system has sent a PEGA0070 alert.
- Decision Data Store disk space below threshold – Insufficient free disk space for the Decision Data Store. The monitored system has sent a PEGA0085 alert.
- Decision Strategy Manager service node is unreachable – At least one node that hosts the Decision Strategy Manager (DSM) service cannot be reached. The monitored system has sent a PEGA0076 alert.
- DSM 90% VBD Memory Usage – The Visual Business Director (VBD) service has used at least 90% of the allocated memory. The monitored system has sent a PEGA0071 alert.
- DSM Flow Execution Error – The DSM data flow has encountered an error. The monitored system has sent a PEGA0073 alert.
- DSM Flow Execution Failure – The DSM data flow run has failed and stopped. The monitored system has sent a PEGA0072 alert.
- Social media error – Data flow processing has failed because of an error in the social media data set (for example, Facebook or Twitter). The monitored system has sent a PEGA0067 alert.
Reviewing and modifying existing subscriptions
You can review the existing notifications to see who has subscribed to which reports. You can also change the delivery frequency of notifications, change personal details of email recipients, or remove the subscription if recipients no longer want to receive a notification.
- Click and do any of the following actions: d > Scorecards > Manage Subscriptions
2. To return to the main screen, click Unsaved changes dialog box.
on the form, and click in the
Subscribing to Pega Predictive Diagnostic Cloud email digests or event notifications
You can subscribe to periodic email digests or to event notifications about a monitored system.
- Click . iagnostic Cloud > Scorecards > Manage Subscriptions
- Click .
- In the Add Subscription window, in the System field, select a monitored system for which you want to send a digest or an event notification. Select All to send notifications for all the systems that are monitored by the server.
- In the Scorecard field, select one of the options listed in Subscription options above.
- If you selected the Improvement Plan: Details, Improvement Plan: Summary, or New Items Daily Scorecard digest, select the days of the week on which you want an email to be sent.
- If you want a digest or an event notification to be sent to more than one recipient, click Add Item.
- Enter an email address, a first name, and a last name for each of the recipients of an email.
- Click to save the subscription.
- To return to the main screen, click - , and click in the Unsaved changes dialog box. on the
Requesting a one-time email with a current digest
Even if you have not subscribed to any notification emails, you can request that an email digest be sent immediately to your mailbox.
- Click Diagnostic Cloud > Scorecards > Email Scorecards.
- In the System field, select a monitored system for which you want to receive a digest.
- In the Scorecard field, select Improvement Plan: Details, Improvement Plan: Summary, or New Items Daily Scorecard.
- Do one of the following actions:
- In the Email To section, click Add Item to add email addresses to which you want to send a digest.
- Select the All Current Subscribers option to send a digest to all the operators who have subscribed to any of the reports on this server.
- Click to send a digest.
- To return to the main screen, click Unsaved changes dialog box. on the form, and click in the
Published February 23, 2017 — Updated December 19, 2018