What's new in Pega Predictive Diagnostic Cloud

These release notes provide information about enhancements and known issues that were resolved in each Pega Predictive Diagnostic Cloud™ (PDC) release.

Current version

The following enhancements have been implemented:

Pega Predictive Diagnostic Cloud 2.14 (October 17, 2019)

You can now immediately send a daily digest notification to selected recipients directly from the Manage notifications menu. You can use this feature to decide which type of digest you want to send.

Previous versions

The following enhancements have been implemented:

Pega Predictive Diagnostic Cloud 2.13 (October 8, 2019)

Performance and stability improvements in this version help you to quickly assess your system, as well as identify and resolve issues.

Pega Predictive Diagnostic Cloud 2.12 (October 3, 2019)

  • You can now view the most recent status of a bug or story that you share with Agile Studio at the top of a case view, for easier and faster issue resolution. For more information, see Integrations with project management tools in Pega Predictive Diagnostic Cloud.

  • On the Enterprise landing page, in the System details section of a node, you can now view the start time of that node. This information helps you quickly troubleshoot issues with your system.

Pega Predictive Diagnostic Cloud 2.11 (September 24, 2019)

  • When you investigate an event, you can now view the details of other alerts that occurred during the same interaction with the server, in the Related Events tab. Use this functionality to more efficiently track related events and gain a more comprehensive view of your system.
  • Email notifications for exceptions with the greatest impact on system performance and user experience now include a brief explanation of the criteria that determine which events qualify for the report. This enhancement improves event tracking and helps you faster troubleshoot your system.
  • The Top 5 user impact report now includes cases that affect web or service requestors.

Pega Predictive Diagnostic Cloud 2.10 (September 18, 2019)

  • The Manage subscriptions section has been renamed to Manage notifications. The section now provides quick access to daily digest and event-based subscriptions. In addition, you can now search notifications by name or tag, which improves search speed.
  • PDC now identifies the PEGA0100 (Queue Processor Registration Failed) alert as a critical event. Additionally, you can track system failures related to this alert by subscribing to Queue processor registration failed notifications.
  • PDC now supports PagerDuty for incident response. Use this integration to track and resolve performance issues in your system or application with more speed and reliability.
  • You can now share more details between PDC cases and Agile Studio. Add stack trace, SQL, and application data to your Agile Studio bug or story for quicker and more intuitive case resolution. For more information, see Integrations in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.09 (September 10, 2019)

  • You can now quickly find the exceptions that have the greatest impact on user experience and that decrease the maintainability of your system in the Improvement Plan. For all applications, and for each application separately, PDC highlights up to five most frequent exceptions that occurred in the last 24 hours with at least 10,000 occurrences over the past week. To receive the top five exceptions by email, subscribe to the Improvement Plan: Top 5 notifications.
  • If you view an event list which covers a period that is affected by event throttling (PEGA0044 alert), the Event Viewer now notifies you which event types might be missing from the list. This enhancement improves event tracking and helps you troubleshoot your system more efficiently.

Pega Predictive Diagnostic Cloud 2.08 (September 4, 2019)

  • When you switch from Usage Viewer to Event Viewer to analyze the events that correspond to the current chart, PDC now automatically filters these events by node.
  • On the Enterprise landing page, the DB Query Stats tab now provides improved performance. As a result, you can quickly analyze the data even if the number of queries is very high.

Pega Predictive Diagnostic Cloud 2.07 (August 27, 2019)

  • In Improvement Plan, you can now quickly find issues that have the greatest impact on the user's interactions with the web browser. PDC highlights the top five issues for all applications, and for each application separately. You can receive the top five items in your email by subscribing to the Improvement Plan: Top 5 notifications. For more information, see Notifications about your system in PDC.
  • Cases that are related to different aspects of SQL query execution (PEGA0005 and PEGA0042 alerts) now have titles that clearly separate these cases from each other. This enhancement provides more clarity and helps you analyze issues more efficiently.

Pega Predictive Diagnostic Cloud 2.06 (August 27, 2019)

  • Apart from the email notifications that were already available in PDC, you can now receive SMS notifications about various events in your system.

    For more information, see Notifications about your system in PDC.

  • The System Summary landing page is now deprecated. To monitor your system's performance, you can now use the System Assessment landing page that provides tools for completing the following tasks:

    • Compare the distribution of healthy and slow interactions, and the average time deviation between these interactions in the selected time frame. You can filter the data by application and by the Web and Service requestor types.

    • Determine a possible cause of a performance issue by quickly analyzing the corresponding events. You can view events that happened on a specific day, and then filter the list by application and requestor type in Event Viewer by clicking the data bar for that day in System Assessment.

  • PDC now identifies the PEGA0013 alert (DSM: under-replicated partitions), and then creates or updates the corresponding cases. You can receive a notification for every occurrence of the alert by subscribing to the Under-Replicated Partitions issue notifications.

  • PDC now identifies the PEGA0014 alert (DSM: offline partitions), and then creates or updates the corresponding cases. You can receive a notification for every occurrence of the alert by subscribing to the Offline partitions count issue notifications.

Pega Predictive Diagnostic Cloud 2.05 (August 14, 2019)

  • In Event Viewer, you can now export filtered events to a CSV document much faster than to an XLS file. This enhancement saves you a significant amount of time if you export events on a regular basis, for example, to perform statistical analysis of a large number of events in external statistical computing tools.

  • Cases that PDC creates from the PEGA0005 alert (Query time exceeds limit) now provide the following enhancements to help you research and resolve issues more quickly:

    • PDC always identifies the report that caused the alert. If the system does not send the clipboard parameter page, PDC retrieves the report name from the call stack.

    • You can now quickly identify cases that result from slow Get Next Work processing. For more information about the Get Next Work function in Pega Platform, see Get Next Work function.

Pega Predictive Diagnostic Cloud 2.04 (August 7, 2019)

  • Assess the impact of an issue more quickly by analyzing the summary and distribution of key performance indicator (KPI) values on the new Analysis case tab. For more information about KPI, see Configuring the key performance indicator.

  • PDC now identifies ORA-00060: deadlock detected while waiting for resource exceptions as DBMS0009 events and creates or updates the corresponding cases. To receive a notification for each exception occurrence, subscribe to the Oracle database deadlock issue notifications. For more information, see Subscribing to email digests and event notifications in PDC.

  • Quickly share a case with other teams. Get a direct link that helps multiple teams cooperate on investigating the issue by using the Copy shareable link option in the Action menu of a case.

Pega Predictive Diagnostic Cloud 2.03 (July 31, 2019)

  • Track configuration changes to troubleshoot your system's unusual behavior. In the new Configuration changes section of System Summary, you can now quickly check the type of configuration change, where the change occurred, and compare the new setting with the previous value.

  • PDC now identifies the primaryPageClass parameter in the PEGA0001 alert. As a result, Browser Time cases contain information that is directly related to the actual action that a user has taken in the application. This information helps you find the source of an issue more quickly.

Pega Predictive Diagnostic Cloud 2.02 (July 30, 2019)

  • In Usage Viewer, you can now quickly view events that correspond to the chart that you are viewing. By clicking a data point over the line chart, you can switch to Event Viewer to view events from the time period that depends on the application, node, and the type of interaction that the chart represents, such as a browser session, an external application, an internal background process, or a queue processor.

  • PDC now identifies the Unable to start Kafka broker exception as an OPS0021 event and creates or updates a corresponding case. To receive a notification for each event in which the exception has occurred, subscribe to the Kafka broker issue notifications. For more information, see Subscription options for notifications.

  • PDC now identifies exceptions related to the email client as an SMTP0003 event and creates or updates a corresponding case. To receive a notification for each event in which the exception has occurred, subscribe to the Email Sending Failure notifications.

  • PDC now identifies exceptions that result from an unknown host as an OPS0022 event and creates or updates a corresponding case. To receive a notification for each event in which the exception has occurred, subscribe to the Unknown Host Failure notifications.

  • Cases created for the PEGA0099 alert (Job Scheduler Failure) now provide the reason for failure, and other additional contextual data, such as the name of the job scheduler that failed. This information helps you resolve the issue more quickly.

Pega Predictive Diagnostic Cloud 2.01 (July 28, 2019)

  • In SLA Reporting, you can now quickly view events that correspond to the chart that you are viewing. By clicking a bar, you switch to Event Viewer to view events from the time period that depends on the chart resolution.

  • Case processing is now enhanced so that you never need to restart a case manually.

Pega Predictive Diagnostic Cloud 1.98.2 (July 9, 2019)

  • You can now view cases from the last 24 hours in Improvement Plan by selecting the time interval. Viewing the most recent occurrences helps you resolve issues that require urgent attention.

  • When you share a case with a project management tool, for example, Agile Studio, the tool's name is displayed in the Assigned to field of the case. This enhancement makes case tracking quicker and more intuitive.

    For more information, see Integrations in Pega Predictive Diagnostic Cloud.

  • PDC now identifies pr_read_from_stream function issues as a DBMS0008 event and creates or updates a corresponding case. To receive a notification for each event in which the exception has occurred, subscribe to the Alert email DB config notifications.

  • New users can now quickly learn about the features of Usage Viewer by clicking the guided tour icon in the upper-right corner.

Pega Predictive Diagnostic Cloud 1.98.1 (July 1, 2019)

  • Event Viewer now contains several new predefined time intervals, which makes browsing events faster and more convenient.

  • With the enhanced Show events in Event Viewer button, viewing the most recent events that are correlated to a case is now faster and more intuitive.

  • When you group events in Event Viewer by case ID, each row represents a single issue, regardless of the number of applications in which the issue occurred.

Pega Predictive Diagnostic Cloud 1.98 (June 24, 2019)

  • When the processing of a browser or service request causes delays, PDC analyzes PAL statistics from the relevant alerts and identifies possible sources of the delays in your system. PDC now captures PAL timers and PAL counters. For example, when the inferring of Java accounts for more than 30% of the interaction time, PDC creates a PAL0011 event that provides the exact percentage and the number of times that Java was inferred.

    For more information about PAL events, see PAL events in Pega Predictive Diagnostic Cloud.

  • SQL parsing capabilities in PDC are now improved with updated correlation methods for Database cases.
    Cases that were created before June 24, 2019 are no longer updated and will be archived within 14 days. You can track database-related events in cases that were created after that date.
  • When you group events by type in Event Viewer, the list of events now contains event names, which helps you analyze issues more quickly.
  • If your system is not sending usage data, Usage Viewer now displays a warning message with details about the issue.

  • You can now use the latest PDC features in a Pega Platform™ 7.2.1 system if you install the appropriate hotfix.

    For more information, see Hotfixes to support the latest Pega Predictive Diagnostic Cloud features.

  • In Usage Viewer, you can now view a description of each chart by clicking Metric Info.

Pega Predictive Diagnostic Cloud 1.97 (June 10, 2019)

  • When you have multiple differently-named systems with the same node ID, PDC now correctly associates alerts and exceptions with the system that generated them.
  • Each operator can now save the preferred time zone. This enhancement helps you to analyze issues more quickly by reusing existing preferences.
  • PDC now identifies database connection state issues as an OPS0020 event and creates or updates a Database connection state issue case. To receive a notification for each database in which the exception has occurred, subscribe to the Database connection state issues notifications. For more information, see PDC notification subscriptions.

Pega Predictive Diagnostic Cloud 1.96 (May 29, 2019)

  • You can now view all events that are correlated with a case in the Event Viewer.
  • The performance of the expandable Related alerts section of the Event Viewer has been improved, so that you can investigate the context of the case more quickly.
  • When you select too much data to correctly display in the Event Viewer, a warning message is displayed, so that you can adjust the filters.
  • Value labels in recommended next steps of a case are no longer maintained.

Pega Predictive Diagnostic Cloud 1.95 (May 27, 2019)

Pega Predictive Diagnostic Cloud 1.94 (May 13, 2019)

  • You can now integrate PDC with Pega Agile Studio, Jira, and ServiceNow to track the resolution of issues related to the performance of your system or application. Create and update tickets such as bugs, stories, and incidents directly from your PDC cases. This enhancement helps teams streamline the management of issues. For more information, see Integrations in Pega Predictive Diagnostic Cloud.
  • The performance of the Usage Viewer has been improved. You can now quickly view usage data for the last 7 days, 30 days, or for a custom time frame.

Pega Predictive Diagnostic Cloud 1.93 (May 7, 2019)

  • The Application list in the Improvement Plan now includes version numbers. This enhancement helps you, for example, simultaneously monitor two versions of the same application.
  • By default, you now log in to a production system in PDC. You can change that setting in the Operator Preferences window by clicking the Operator icon on the right side of the PDC header and then clicking Preferences.

Pega Predictive Diagnostic Cloud 1.92 (April 29, 2019)

  • You can now set up SAML identity provider (IdP)-based authentication in PDC for single sign-on (SSO). As a result, you can configure your own SSO for signing in to your PDC account.
  • PDC now recognizes the Business Intelligence Exchange (BIX) extraction failure exception on your monitored systems as an OPS0018 event and creates or updates a BIX extraction failure case for each place in a system where such an exception has occurred. To receive a notification about each occurrence of this exception, you can subscribe to the BIX Extraction Failure notifications.

    For more information about subscriptions, see Pega Predictive Diagnostic Cloud notification subscriptions.

Pega Predictive Diagnostic Cloud 1.91 (April 23, 2019)

  • In the new Related events tab of the Event Viewer, you can now view all the related events that occurred during the same interaction. You can quickly filter the Event Viewer to display only these related events.
  • You can now bookmark sets of filters in the Event Viewer. This enhancement helps you to analyze events more quickly by reusing the filters that you frequently need.
  • For each event in the Event Viewer, the Event column now contains the event code and event message. As a result, you can identify the type of event more quickly.

Pega Predictive Diagnostic Cloud 1.90 (April 17, 2019)

  • The performance and stability of the System Summary have been improved. You can now view the most current data even if Pega Platform generates a very high number of PEGA0001 and PEGA0011 alerts for slow interactions in the system.

Pega Predictive Diagnostic Cloud 1.89 (April 5, 2019)

  • PDC now analyzes statistics from the Performance Analyzer tool and identifies performance problems. If an interaction is excessively long, PDC creates a PALxxxx event that indicates which part of the interaction caused a delay.
  • In the Event Viewer, you can now view all information about an event by expanding its row. You can use this enhancement to investigate an event quickly, without opening additional windows.
  • You can now group events in the Event Viewer by case, event type, application, operator, and node by selecting the grouping from the list in the upper left corner.

Pega Predictive Diagnostic Cloud 1.88 (April 3, 2019)

  • PDC now identifies the bad table mapping in database exception as a critical event with the DBMS0007 alert code. To receive a notification about each exception that occurs on the monitored system, you can subscribe to the New Exception notifications.
  • PDC now identifies the occurrence of a database password exception as a critical event with the DBMS0006 alert code. To receive a notification for each database in which the exception has occurred, you can subscribe to the Database Exception notifications.
  • In the Usage Viewer, you can now download the data for each requestor type in the .xlsx format. This enhancement helps you to identify and analyze usage of the system or a particular application in a specified time frame.
  • You can now send feedback to the PDC team by clicking the floating feedback button on the right side of the PDC screen. Use this feature to submit ideas for improvement and inform the team about any issues that you encounter.

Pega Predictive Diagnostic Cloud 1.87 (March 22, 2019)

  • The Alarms category on the Improvement Plan landing page has been renamed to Operations and moved farther down the list of categories. Cases in this category gather events that are related to run-time problems with your application.
  • On the Event Viewer landing page, you can now group events by node, by operator, or by application. This enhancement helps you to identify the main source of events that were generated in a specified time frame.
  • You can now filter events on the Event Viewer landing page by using the new Interaction ID column. Use this filter to find all events that occurred during a single interaction with the server.
  • When you group events on the Event Viewer landing page by case or by event type, you can now view all events with the same case ID or type by clicking the total number of events.

Pega Predictive Diagnostic Cloud 1.86 (March 18, 2019)

  • You can now encrypt operator IDs in PDC by enabling privacy mode. When the mode is enabled, personal user information is hidden and cannot be viewed in PDC. By default, the feature is disabled. To enable privacy mode, click Diagnostic Cloud > Business policies > Operator privacy mode. For debugging purposes, you can retrieve a specific encrypted operator ID by using a dedicated tool that is included in the menu.
  • PDC now analyzes the Elasticsearch work index information that Pega Platform periodically sends and verifies whether the pattern is correct. If the Elasticsearch work index has stability problems, PDC generates an OPS0013 event and creates a unique ElasticsearchFailure case for each application server where the issue occurs.
  • PDC now analyzes the state of the index queue and index queue table data that it periodically receives from Pega Platform. If PDC detects significant latency in the search index updates, PDC generates an OPS0014 event, and creates a unique StaleSearchSuspect case for each application server where the problem occurs.
  • PDC now analyzes agent status information that Pega Platform periodically sends. If an agent appears to have an outdated snapshot, an exception, or has run for an excessively long period, PDC generates an OPS0015 event and creates a unique AgentStatus case for each application server where the problem occurs.
  • When a report fails to join because of an unexposed property, PDC now generates a DBMS0005 event and an UnoptimizedProperty case. You can subscribe to notifications about each occurrence of this problem in your system.
  • PDC now identifies the No space left on device exception as a critical event with the OPS0016 alert code and creates a case for each node on which the exception occurs. You can subscribe to notifications about each occurrence of this problem in your system.
  • PDC now identifies the IllegalStateException exception as a critical event with the OPS0017 alert code and creates a case for each system on which the exception occurs. You can subscribe to notifications about each occurrence of this problem in your system.

Pega Predictive Diagnostic Cloud 1.85 (March 11, 2019)

  • You can now filter events in the Event Viewer more quickly. By clicking the Filter button, you can select multiple filtering criteria that apply to the event list and to the aggregated views. The criteria stay in effect when you switch to another system.
  • Events that occurred while maintenance mode was active are now clearly marked in the Event Viewer with a Wrench icon, so that you can identify them more quickly and improve your problem analysis.

Pega Predictive Diagnostic Cloud 1.84 (March 1, 2019)

  • On the Elasticsearch tab of the Enterprise landing page, you can now monitor the changes in the number of the rule document count within a specified period.
  • On the new Urgent Events tab of the Enterprise landing page, you can now see a list of urgent events for all nodes in a cluster. Use this cluster-level view to prioritize problem resolution.
  • All Data flow error (PEGA0073) alerts that occur for a particular Run ID are now correlated with the same case in PDC. As a result, you can find the alerts more quickly.
  • PDC now recognizes a slow get next work id query and creates a case that contains recommended next steps to resolve the root cause of the problem.
  • PDC now recognizes Alert Queue Processor Run Failed (PEGA0103) alerts and treats them as critical events. You can subscribe to notifications about queue processor failures in your system.
  • When the Log-Message method generates an exception with the GenerateStackTrace option, PDC assigns alert code OPS0012 to this event and creates a unique case type.
  • PDC now recognizes the Waiting on the batch thread pool (PEGA0104) alert and treats it as a critical event. You can subscribe to notifications about delays in processing that are caused by slow resource allocation for batch and async java thread pools.

Pega Predictive Diagnostic Cloud 1.83 (February 22, 2019)

  • On the Event Viewer landing page, you can now group events by event type. This enhancement provides a summary of the type of events that your system has generated in a specified time frame.
  • Cases in the Database category now provide recommendations for resolving problems with your system.
  • The Browser tab of the System Summary landing page now lists multiple pages with occurrences of browser items. You can sort the list by the number of occurrences and time impact. As a result, you can track browser performance problems over a much longer period of time.

Pega Predictive Diagnostic Cloud 1.82 (February 18, 2019)

  • On the new Usage Viewer landing page, you can find aggregated system usage information for the following requestor types: Web, Service, Background, and Async. You can use this data to see how your system's performance varies during the day and manage your system's resources by the hour. For example, you can prepare for increased usage and schedule maintenance for low-usage time periods.
    You can filter the information on the Usage Viewer landing page by application, by interval, or by node.
  • On the Queues tab of the Enterprise landing page, you can now view the queue status values for the last 7 days. This information helps you to check whether queues are processed in a timely manner.

Pega Predictive Diagnostic Cloud 1.81 (February 7, 2019)

  • You can now suspend all notifications for a selected system by enabling maintenance mode for a specified period. Maintenance mode prevents PDC from sending false alarms about that system, for example, if the system is undergoing maintenance or planned downtime.
  • Cases in the Alarms category now contain improved recommended next steps. You can find additional information about a case by clicking a link to Community.
  • The handling of cases that contain a significantly large number of events has been improved. As a result, if the volume of events is too high for PDC to display them, you can see the appropriate warnings in the Overview and Events tabs of the case.

Pega Predictive Diagnostic Cloud 1.80 (February 4, 2019)

  • PDC now recognizes the Hazelcast instance is not active exception as a critical event with the alert code OPS0011 and creates a unique case for each environment in which the exception occurs. You can subscribe to receive a notification for each occurrence of the exception by clicking Diagnostic Cloud > Scorecards > Manage Subscriptions.
  • In the summary view of an event that originates as an exception in Pega Platform, on the new Stack trace tab, you can now view the stack trace of that event. This information helps you to debug your application.
  • In the Action item reports section of the Reporting landing page, you can now use the CasesWithElevatedKPI report to view information about cases for which the KPI metric is elevated.
  • On the Reporting landing page, you can now use the metricExtendedEvent report to view the name and value of extended metric events that your application sends. You can find the corresponding report in the PDCReports category of the Custom Reports page.

To use the following enhancements, download the new PDCClient ruleset from Pega Exchange and import it into your application:

  • You can now define custom alerts in your application. Your application can send custom alerts to PDC by using the sendEvent function from the PDCClient ruleset. PDC recognizes such alerts and creates appropriate cases. You can subscribe to receive a notification for each custom alert.
  • If your application sends custom alerts, you can find the corresponding cases in a new Improvement Plan category: Custom alerts.

Pega Predictive Diagnostic Cloud 1.79 (January 24, 2019)

  • You can now filter monitoring data by system name on all landing pages by selecting the appropriate system from the list in the PDC header.
  • Cases in Alarms, Application Logic, and Platform Tuning categories now contain recommended next steps and links to Community articles that describe the cases in more detail.
  • The title of a case that represents a slow Decision Data Store (DDS) interaction now contains the name of the column family that was slow.
  • The title of a case that represents a slow Interaction History (IH) interaction now contains the name of the strategy that was slow.

Pega Predictive Diagnostic Cloud 1.78 (January 21, 2019)

  • In the Manage Subscriptions menu, scheduled email digests are now separate from event notifications. You can only find up-to-date subscription options on the list.
  • For systems that are running latest AESRemote rules, Predictive Diagnostic Cloud recognizes when full text search is not available and creates an OPS0010 event and case.
  • PostgreSQL configuration errors are recognized as OPS0009 events and appropriate cases are created.
  • The Cache Reduced (PEGA0016) alert is now correctly processed and a unique case for each affected cache is created.
  • The case correlation logic for the DSM Data Flow Error (PEGA0073) alert has been improved. A unique case for each failed flow name is created.
  • The Problem Correlation section has been moved from the Events tab to the Overview tab of a case, so that problem solvers need less time to investigate a case. To avoid delays for other users, the information is loaded when you expand the section.

Pega Predictive Diagnostic Cloud 1.77 (January 15, 2019)

  • By default, all users can now see new systems that are monitored by Predictive Diagnostic Cloud. You can restrict users from accessing a system by clicking Diagnostic Cloud > System Administration > Manage System Access.
  • In the upper-left corner of the Overview tab of a case, you can now see the type of case. As a result, you can identify similar issues with your systems by searching for the case type.

Pega Predictive Diagnostic Cloud 1.76 (December 21, 2018)

  • Predictive Diagnostic Cloud recognizes the PEGA0098 alert: Job scheduler failed to register for the next run, and creates a unique case for each job scheduler that has the issue. You can subscribe to receive a notification for each occurrence of the alert by clicking Diagnostic Cloud > Scorecards > Manage Subscriptions.
  • Predictive Diagnostic Cloud recognizes the PEGA0099 alert: Job scheduler failed to complete successfully, and creates a unique case for each job scheduler. You can subscribe to receive a notification for each occurrence of the alert.
  • Predictive Diagnostic Cloud recognizes the PEGA0101 alert: Queue processor failed due to a missing or failed stream node, and creates a unique case for each queue processor. You can subscribe to receive a notification for each occurrence of the alert.
  • Predictive Diagnostic Cloud sends alarm notifications about infrastructure issues to Global Customer Support. On the Alarm Ticket tab of the Enterprise menu, you can track and monitor all such notifications that the system has created.
  • On the Elasticsearch tab of the Enterprise menu, you can view the status and size of the Elasticsearch indexes for searching cases, rules, and data instances. You can use this information to diagnose issues with Elasticsearch.
  • To improve usability of the Enterprise menu, node type is now represented by icons. To view the text value, hover over an icon.

Pega Predictive Diagnostic Cloud 1.75 (December 17, 2018)

  • In the Overview tab of a case, Predictive Diagnostic Cloud now provides actionable recommendations for resolving the underlying issue.
  • Improvements to the PostgreSQL database system shorten the time required to complete database requests and increase the performance of Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 1.74 (December 11, 2018)

  • When Pega Platform generates a Connect-SOAP time-out exception, Pega Predictive Diagnostic Cloud recognizes the exception as an INTG0004 event and creates a unique case for each connector that has a connection or read time-out. You can subscribe to receive a notification for each occurrence of this event.
  • When Pega Platform generates a PEGA0005, PEGA0006, PEGA0007, or PEGA0042 alert, Pega Predictive Diagnostic Cloud now normalizes the SQL "IN ()" clause to create a single case, regardless of the size of the value list that was used as the report filter. As a result, fewer cases are created and you can identify the root cause of the issue more quickly.
  • When Pega Platform generates a PEGA0005, PEGA0006, PEGA0007, or PEGA0042 alert, Pega Predictive Diagnostic Cloud now creates a single case, even if the SQL "AS" clause name is different every time that you run a query. As a result, fewer cases are created and you can identify the root cause of the issue more quickly.

Pega Predictive Diagnostic Cloud 1.73 (November 29, 2018)

  • Event Viewer now displays the time of events with accuracy to one millisecond. This enhancement helps you to identify the exact order of events.
  • The Improvement Plan now provides filtering and sorting so that you can find information more quickly.

Pega Predictive Diagnostic Cloud 1.72 (November 27, 2018)

  • When Pega Platform generates a Lock gone exception, Pega Predictive Diagnostic Cloud recognizes the exception as a LOCK0001 event and creates a unique LockGone- case for each object type that has the issue.
  • The New Items Daily email digest now includes cases that were created from exceptions.
  • When Pega Platform generates a Postgres connection capacity exception, Pega Predictive Diagnostic Cloud now recognizes the exception as an OPS0007 event and creates a unique DBConnections- case for each database where the issue occurs.
  • When Pega Platform generates an Apache Tomcat server connection pool exception, Pega Predictive Diagnostic Cloud now recognizes the exception as an OPS0008 event and creates a unique TomcatPoolProblem- case for each application server and connection pool where the issue occurs.
  • You can now subscribe to the Database Configuration Issues email digest to receive a notification about each occurrence of the OPS0007 and OPS0008 events.
  • You can now view tracking reference information by expanding a case in the Improvement Plan. Tracking information can include tickets from any system that you use for issue and project tracking, such as Pega Agile Studio, ServiceNow, Jira, or Pega Support.

Pega Predictive Diagnostic Cloud 1.71 (November 21, 2018)

  • When Pega Platform generates events related to the decisioning capabilities, Pega Predictive Diagnostic Cloud now creates corresponding cases in the Decisioning category. The new category appears in the Improvement Plan, so that you can find and analyze decisioning-related issues more quickly.
  • Pega Predictive Diagnostic Cloud now calculates the urgency of all cases based on the number of occurrences and on the metric. As a result, you can accurately prioritize resolving issues with your application.

Pega Predictive Diagnostic Cloud 1.70 (November 14, 2018)

  • When Pega Platform generates a Connect-REST time-out exception, Pega Predictive Diagnostic Cloud creates an INTG0001 alert and a ConnectRESTTimeOut- case. You can subscribe to receive a notification for each occurrence of this alert.
  • When Pega Platform generates a Connect-FTP method failure exception, Pega Predictive Diagnostic Cloud creates an INTG0002 alert and a ConnectFTPFailure- case. You can subscribe to receive a notification for each occurrence of this alert.
  • When Pega Platform generates an OutboundMapping exception, Pega Predictive Diagnostic Cloud creates an INTG0003 alert and a ConnectMap- case. You can subscribe to receive a notification for each occurrence of this alert.
  • When Pega Predictive Diagnostic Cloud fails to connect to Global Customer Support to create an alarm ticket, Pega Predictive Diagnostic Cloud creates an OPS0006 alert and an ALTicketFailure- case. You can subscribe to receive a notification for each occurrence of this alert.
  • When conflicting queries cause a blockage in the PostgreSQL database system, Pega Predictive Diagnostic Cloud provides an enhanced description and advice that helps you to resolve the issue.
  • On the Event tab of a case, the summary now contains an Interaction ID, which is a combination of the requestor ID and the interaction number separated by --, for example, <requestor ID>--<interaction number>. Pega Predictive Diagnostic Cloud uses this value to correlate events that occur within the same interaction.
  • When you click a case in the Event Viewer, you can access information about the case more quickly.

Pega Predictive Diagnostic Cloud 1.69 (November 5, 2018)

  • When Pega Platform sends the PEGA0037 alert, Pega Predictive Diagnostic Cloud now creates a case in the Platform Tuning category. This change helps you to address the cause of the alert in a timely manner. For more information, see PEGA0037 alert: Rule assembly time exceeded threshold.
  • Pega Predictive Diagnostic Cloud now assigns the correct urgency to cases that have been reopened. This enhancement ensures that you do not treat low-impact issues as urgent.

Pega Predictive Diagnostic Cloud 1.68 (October 31, 2018)

  • You can now track external references associated with a case. Tracking references can include tickets from any system that you use for issue and project tracking, such as Pega Agile Studio, ServiceNow, Jira, or Pega Support. You can view and update tracking reference information in the new Tracking tab of a case.
  • Pega Predictive Diagnostic Cloud now identifies performance issues that affect the sppr_sys_reservequeueitem_b queue management stored procedure and creates cases with specific advice for these issues.

Pega Predictive Diagnostic Cloud 1.67 (October 22, 2018)

  • On the Improvement Plan landing page, you can now choose to view up to five hundred of the most urgent cases in each category. This view allows advanced users to browse many cases on one page.
  • For each case in the Case view of the Event Viewer, the Affected column shows the requestor type that the issue affects: web interactions, service interactions, or batch processing.
  • In the Case view of the Event Viewer, the cases are now sorted according to the number of occurrences. This enhancement helps you identify the most frequent problems with your system.

Pega Predictive Diagnostic Cloud 1.66 (October 16, 2018)

  • Pega Predictive Diagnostic Cloud now notifies Pega Customer Support when a monitored system sends a PEGA0055 alert. The text of the ClockDrift- case has been updated to reflect a better understanding of the common causes of this alert. For more information, see PEGA0055 alert: Clock drift exceeded the configured time threshold.
  • You can now subscribe to the New Exception notification (scorecard) to receive a message for every exception that occurs on the monitored system. To receive the New Exception notification, you must subscribe to it specifically, because it is not covered by the All option. Do not select this notification for unstable systems, because if the volume of messages is high, your email provider might block Pega Predictive Diagnostic Cloud.
  • The New alert action item notification is now sent only when a case has more than ten associated events. This enhancement ensures that the application sends messages only about cases that need attention.
  • Pega Predictive Diagnostic Cloud now removes potentially sensitive literal values in query text from SQL strings that come from Connect SQL rules. All literal text in a relational database (RDB) query is replaced by the string [REMOVED].
  • The use of pr_read* functions in an SQL query, which cause guardrail violations, is now highlighted in the Observations tab for query and packaging case types, so that you can prevent further impact on the system's performance.

Pega Predictive Diagnostic Cloud 1.65 (October 11, 2018)

  • When a monitored system sends a PEGA0044 alert, Pega Predictive Diagnostic Cloud now identifies the cases that caused the alert, and the events related to those cases, so that you can address the issue behind the alert.
  • Pega Predictive Diagnostic Cloud no longer sends the Weekly Scorecard. Subscribers to the Weekly Scorecard will receive the Improvement Plan: Details email digests instead.

Pega Predictive Diagnostic Cloud 1.64 (October 8, 2018)

  • When the PostgreSQL database system is in recovery mode, Pega Predictive Diagnostic Cloud creates an OPS0005 alert and a DatabaseMode case, so that you can address the issue.

Pega Predictive Diagnostic Cloud 1.63 (September 25, 2018)

  • You can now view all recent cases and analyze their causes more quickly by using the Cases view in the Event Viewer.
  • You can now periodically receive the following types of Improvement Plan notification emails, which replace the Improvement Plan Summary:
    • A detailed Improvement Plan in HTML format. You can open each case in Predictive Diagnostic Cloud by clicking it.
    • A summary of cases that are divided by category, which contains the total numbers of cases, occurrences, and assigned cases.

Pega Predictive Diagnostic Cloud 1.62 (September 24, 2018)

  • When a summary view fails because the query execution exceeds a time-out in the PostgreSQL database connection, Pega Predictive Diagnostic Cloud creates a DBMS0002 alert and a SocketTimeOut action item.
  • When Pega Predictive Diagnostic Cloud receives a DSM: Data Flow Run Failed (PEGA0072) alert, it sends a notification to Global Customer Support to ensure a timely response.

September 18, 2018

  • The Improvement Plan tab is now loaded more quickly and without interruptions even on systems with very large amounts of data.
  • The Dashboard tab has been renamed to the Welcome tab, and it is now easier to find shortcuts for performing basic configuration steps.
  • The redesigned SQL Analysis tab facilitates the review and analysis of data.

August 31, 2018

  • When a service is unable to process a service request for a pool or package because of a requestor pool lock, Pega Predictive Diagnostic Cloud now creates an OPS0003 alert and a RequestorPool action item.
    You can subscribe to the Requestor Pool Problem scorecard by clicking Diagnostic Cloud > Scorecards > Manage Subscriptions.
  • The DBMS0003 alert that is created when a report fails because query execution exceeds the time-out in a report definition has been improved to support Oracle.

August 25, 2018

  • The action item view has been redesigned to ensure easier access to the Pulse gadget. Details such as SQL analysis or stack trace are now displayed on dedicated tabs.
  • The Improvement Plan subscription email now contains a PDF file attachment with a detailed list of the items that are listed on the Improvement Plan tab.
  • Processing action and exception cases has been unified for performance and stability with the following results:
    • Existing exception cases are no longer updated. Beginning with Predictive Diagnostic Cloud 1.59, new exception cases are created.
    • All the information about exception cases has been moved from the deprecated Dashboard tab to the Improvement Plan tab.
    • You must update custom reports for exception items to ensure that the reports function correctly.

August 18, 2018

  • Pega Predictive Diagnostic Cloud now detects the following conditions:
    • When a report fails because query execution exceeds a time-out in the PostgreSQL database connection, Pega Predictive Diagnostic Cloud creates a DBMS0002 alert, and a SocketTimeOut action item.
    • When a report fails because query execution exceeds a time-out in the PostgreSQL report definition, Pega Predictive Diagnostic Cloud creates a DBMS0003 alert, and a ReportTimeOut action item.
    • When a report fails because of unexposed properties (for example, a database column is missing), Pega Predictive Diagnostic Cloud creates a DBMS0004 alert, and a ReportJoinFailed action item.
  • The PEGA0106 alert has been converted into the DatabaseDeadlock action item. You can also subscribe to the Database Deadlock Detection scorecard. To subscribe to a scorecard, click Diagnostic Cloud > Scorecards > Manage Subscriptions.

August 10, 2018

  • When you log in to Pega Predictive Diagnostic Cloud for the first time, basic information about getting started with Pega Predictive Diagnostic Cloud is displayed.
  • Information about the time zone that applies to the current operator is displayed at the top of the page, next to the search field.
  • The action item view has been redesigned to ensure easier navigation. The most important details are now listed at the top of the screen.
  • The Improvement Plan subscription email now contains a detailed list of items in each category.

August 03, 2018

  • The following alerts have been converted into action items:
    • DSM: VBD has used 90% of allocated memory (PEGA0071)
    • DSM: Data Flow Run Failed (PEGA0072)
    • DSM: Data Flow Throws an Error (PEGA0073)
  • You can now subscribe to the following scorecards that correspond to the preceding action items:
    • DSM 90% VBD Memory Usage
    • DSM Flow Execution Failure
    • DSM Flow Execution Error
    To subscribe to a scorecard, click Diagnostic Cloud > Scorecards > Manage Subscriptions.

July 27, 2018

  • The action item view includes additional information:
    • In the upper right part of the screen, the Impact summary area displays the priority of the action item, affected applications and requestor types, and weekly trends.
    • In the center of the screen, a graph displays the number of occurrences for the action item on each day within the last two-week period.
  • The Event Viewer has been enhanced:
    • The Event Viewer now displays action items that are correlated with events. You can use this information to sort and filter the events that are listed in the table.
    • If you filter the list of displayed events, when you click the Refresh button, it no longer resets the filters.

July 20, 2018

  • In the Enterprise menu, you can view the Node ID and Node Type on the Health tab.
  • In the Enterprise menu, you can view the Node Type on the Agent tab.
  • The "Can’t connect to SMTP host" exception has been converted to the SMTP0001 action item.
  • The "Connection reset while sending mail" exception has been converted to the SMTP0002 action item.
  • You can view the Email Transport Error scorecard that displays issues with email communication. To receive a scorecard by email, subscribe to the scorecard by clicking Diagnostic Cloud > Scorecards > Manage Subscriptions.
  • To see the following change, request the new AESRemote ruleset from Global Customer Support:
    • Deadlocks are now detected in the PostgreSQL system and are reported as PEGA0106 alert.

July 17, 2018

  • You can now subscribe to the Improvement Plan Summary. To receive a scorecard by email, subscribe to the scorecard: click Diagnostic Cloud > Scorecards > Manage Subscriptions.
  • You can now set the preferred time zone for viewing all Pega Predictive Diagnostic Cloud systems. Click your operator name in the upper right corner of the screen and click Preferences.

July 6, 2018

  • To see the following changes, request the new AESRemote ruleset from Global Customer Support:
    • You can view Memory Management Data for a monitored node.
    • You can view MRU Cache Data for a monitored node.

June 29, 2018

  • In the Event Viewer, you can now filter out action items generated within the last month.
  • You can now restrict the systems that Pega Predictive Diagnostic Cloud users can see. If you have been using this function, you need to reconfigure restrictions for each user.

June 27, 2018

  • You can now view changes in the Pega database size daily. In the Enterprise menu, select the system, and then click the Database Usage tab.
  • You can now view the agent details to determine whether an agent is working correctly or if it is not working at all. In the Enterprise menu, select the system, and then click the Agents tab.
  • You can now view the queue details to determine whether a queue has failed. In the Enterprise menu, select the system, and then click the Queues tab.
  • You can now view listener details to assess the listener's health and performance. In the Enterprise menu, select the system, and then click the Listeners tab.
  • You can now view the list of the hotfixes that are installed on your system. In the Enterprise menu, select the system, and then click the Hotfix History tab.

June 18, 2018

  • In the Stability and Improvement Plan menu, you can now view action items that affect a single application, multiple applications, or all applications. By viewing the action items by an individual system and by application, you can prioritize the issues that must be resolved.
  • In the Enterprise menu, you can see the number of agents that are running on a node and have a status of Normal. In the Enterprise menu, select the system with agents that have the Normal status, and on the Health tab, in the SYSTEM DETAIL section, in the AGENTS column, the number of currently running agents is displayed.
  • To see the following changes, request the new AESRemote ruleset from Global Customer Support:
    • You can delete stale nodes from the Enterprise menu. In the Enterprise menu, select the system with the inactive node, and then on the Health tab, in the SYSTEM DETAIL section, click the Delete icon.
    • You can view the system configuration information. In the Enterprise menu, select the system, and then on the System Info tab, expand the Configuration Settings Info section.

June 14, 2018

  • You can delete stale nodes from the Enterprise menu. In the Enterprise menu, select the system with the inactive node, and click the Delete icon in the SYSTEM DETAIL section, on the Health tab.
  • You can see the system configuration information. In the Enterprise menu, select the system, and expand the Configuration Settings Info section, on the System Info tab.

June 1, 2018

  • You can review the raw data that your application sends to Pega Predictive Diagnostic Cloud by using the Event Viewer. Advanced users can review the more detailed and technical information that is provided in the alert or exception description.
  • Improvements were added for applications that use PostgreSQL database. To see these changes, request the new AESRemote ruleset from Global Customer Support. The following improvements are now available:
    • On the DB Query Stats tab, you can see hourly database query statistics by selecting the specific date and time in the Enterprise menu.
    • On the DB Table Usage tab, you can see how a table size has changed by selecting the specific date and time in the Enterprise menu.
    • On the DB Current activity tab, you can see the currently running query in the Enterprise menu.

May 25, 2018

  • Pega Predictive Diagnostic Cloud shows indexes that are defined on a database table. To view the database indexes, in Predictive Diagnostic Cloud, click Enterprise and select the system that you want to view. To view the INDEX INFO section, click the DB Table Usage tab and expand the table. By viewing the database indexes, you can verify the number of indexes, whether the database contains the appropriate index, and whether any indexes are missing.
  • The Improvement Plan has been updated with the following information:

    • The Affected column shows which requestor types are affected by the issue (web interactions, service interactions, batch processing).
    • The Impact column shows how much time your system spent on processing this issue in the last seven days and a percentage increase or decrease compared with the previous week.
    • The Occurrence column shows the number of occurrences for this issue within the last seven days and a percentage increase or decrease compared with the previous week.
    • In the Trend column, the red (higher) and green (lower) arrows show you action items that are gaining or decreasing in importance. The change is calculated based on the data from the Impact column.
    • In the top right corner, a Refresh button has been added.
    • The Exception category was added as a basic issue category.
  • A Refresh button was added to the System Summary in the top right corner.

May 8, 2018

  • You can view the preliminary Improvement Plan Preview and System Summary Preview scorecards, which present data in an easier and more intuitive format than the existing scorecard.
  • All memory pool collection action items have been improved and provide more accurate troubleshooting information.
  • Pega Predictive Diagnostic Cloud detects reports that run slowly because they contain inefficient starts with or contains pattern-matching conditions.

April 19, 2018

  • Pega Predictive Diagnostic Cloud now automatically detects the name of a report definition or SQL query that extracts data by using case-insensitive conditions.
  • Pega Predictive Diagnostic Cloud lists properties that you need to expose to prevent SQL queries from retrieving data from the BLOB. This improves your troubleshooting process and allows you to quickly resolve your issue.
  • Browser and service performance metrics are fixed and do not show zero alerts when performance issues occur.

April 11, 2018

  • Each monitored node shows information about the Java virtual machine in use and the Pega Platform build. To see this information, click the Enterprise menu, and then click the System Info tab. By looking at the system information, you can determine whether the system that you are working on is up to date.
  • Action items for connectors and database connections have more meaningful descriptions, so that you can quickly assess an issue.
  • The name of the table that is called from the Obj-Save method and that is running slowly is automatically detected to help you research the issue.

March 20, 2018

  • The name of the activity or table that is called from Obj-methods and is running slow is now automatically detected to help you research the issue.
  • The name of the activity that is called from RDB-methods and is running slow is now automatically detected to help you research the issue.
  • Action items regarding guardrails and security violations have more detailed information so that you can quickly assess and troubleshoot an issue.
  • All systems that do not have alert exceptions and health data are automatically deleted from the Current System list that is on your dashboard.

March 8, 2018

  • All Runtime Guardrail Violations action items have more detailed information so that you can quickly assess and troubleshoot an issue.
  • The correlation in stored procedures has also been improved. All calls to a single stored procedure are now assigned to one action item. As a result, the number of action items have been reduced and the scorecard readability has been improved.

February 23, 2018

  • All action items that are related to data processing from internal system tables pr4_*, spr_*, pr_sys* are now automatically identified and assigned to the Pega Cloud work queue for further action. By automatically triaging certain action items, Pega Predictive Diagnostic Cloud enhances your troubleshooting process.
  • The Advice tab on each action item has been renamed the Observation tab. This tab describes issues and provides troubleshooting.

For more information, see Pega Cloud support and help resources.

Suggest Edit

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.