Table of Contents

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 were implemented:

Pega Predictive Diagnostic Cloud 2.65 (October 22, 2020)

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

Previous versions

The following enhancements have been implemented:

Pega Predictive Diagnostic Cloud 2.64 (October 15, 2020)

  • If any dynamic system settings in your system are not optimally configured, PDC now displays a warning on the System Resources > DSS Setting landing page. To help you improve your configuration, PDC displays a list of incorrectly configured dynamic system settings and their Pega-recommended values.
  • The stability of the engine behind the Event Summary daily digest notification has been enhanced. As a result, PDC sends this type of daily digest notifications reliably, even under significant load.

Pega Predictive Diagnostic Cloud 2.63 (October 7, 2020)

  • You can now quickly correlate JVM memory statistics with garbage collection (GC) events. On the System Resources > JVM Monitoring landing page, you can now switch to Event Viewer and filter for GC events in a specific time frame by clicking a point on the timeline. This enhancement helps you troubleshoot JVM memory management issues. For more information, see Tools for monitoring system resources in Pega Predictive Diagnostic Cloud.
You can monitor JVM memory statistics with PDC only for Pega Platform™ 8.4.3 and 8.5.1 systems.

Pega Predictive Diagnostic Cloud 2.62 (October 1, 2020)

Pega Predictive Diagnostic Cloud 2.61 (September 24, 2020)

  • Enhanced PEGA0001 cases now emphasize the most important information: system name, assignment, first and last occurrences, as well as the performance impact for each requestor type.
  • The PegaAESRemote agents in Pega Platform now send all REST messages to PDC through Amazon Simple Queue Service (SQS). This process ensures continuous service because all REST messages reach PDC. For more information, see Data collected by Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.60 (September 17, 2020)

  • The System Resources > Database landing page and the notifications engine now include performance and usability improvements. As a result, you can access important diagnostic information about your systems more quickly and conveniently.
  • You can now subscribe to notifications for individual custom alerts. For more information, see Configuring custom alerts in your application in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.59 (September 3, 2020)

  • PDC now provides Insights, which are a new type of event. Insights are observations based on the activities and changes in your system. Insights are different from alerts and exceptions because they provide additional information that is the result of a synthetic analysis of your system. For more information, see Cases in Pega Predictive Diagnostic Cloud.
  • You can now subscribe to notifications for the following events:
    • PEGA0009
    • PEGA0016
    • PEGA0114
    • DBMS0006
    • OPS0005
    • OPS0010
    For more information, see List of events and notifications in PDC.
  • On the Manage notifications landing page, you can now view and edit the schedule for daily-digest notifications. This enhancement helps you save time by organizing notifications more conveniently. For more information, see Managing notifications in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.58 (August 27, 2020)

  • Multiple data collection services in PDC are now fully asynchronous, which further reduces network usage.

Pega Predictive Diagnostic Cloud 2.57 (August 20, 2020)

  • PDC now identifies a long-running query as an OPS0039 event and creates or updates a corresponding case to help you track the issue. You can receive a notification when this event occurs by subscribing to the Query running longer than expected notification.
  • Event-based notifications in ServiceNow now include the event ID. To learn how to subscribe to these notifications, see Integrating Pega Predictive Diagnostic Cloud with ServiceNow.
  • The OPS0018 event now recognizes one more Business Intelligence Exchange (BIX) extraction failure exception on your monitored systems.
  • The newly revised list of urgent (critical) events now includes only the most important issues. As a result, you can focus on resolving issues that have the greatest impact on the performance of your system. For more information, see List of events and notification in PDC.

Pega Predictive Diagnostic Cloud 2.56 (August 12, 2020)

  • You can now analyze the frequency and magnitude of an issue. In the new Event Distribution tab of the case view, two charts display changes in the average event metric, as well as changes in the number of all events associated with a case.
  • Filtering by event type in the Event Viewer has been improved to work better with large volumes of data.

Pega Predictive Diagnostic Cloud 2.55 (August 7, 2020)

  • PDC now features enhanced performance of the System Resources > Database landing page.
  • The case description for OPS0024 events (Java heap space out of memory) now provides more details about the node type to help you to more quickly diagnose the problem.

Pega Predictive Diagnostic Cloud 2.54 (July 31, 2020)

  • Save time by subscribing to multiple event-based notifications for multiple systems at once. This enhancement helps you organize your notifications with fewer clicks. For more information, see Managing notifications in Pega Predictive Diagnostic Cloud.
  • Analyze resource utilization data more quickly and more precisely on the enhanced System Resources > Resource Utilization page. The performance of the page is now improved, and you can view more granular data for each node. For more information, see Tools for monitoring system resources in Pega Predictive Diagnostic Cloud.
  • On the new System Resources > Nodes page, you can find statistics and detailed information about the status of your system nodes.
  • You can now analyze more recent query statistics by using the new "last six hours" time interval of on the Query Stats tab of the System Resources > Database page.
  • For improved usability, the System Resources > Queue Processor page now displays queue processors with broken items first, followed by queue processors in the disabled and running states.
  • For improved usability, the System Resources > Job Scheduler page now displays disabled job schedulers first, followed by job schedulers in the enabled state.
  • PDC now correctly indicates node shutdowns when your system sends a system health message after sending a PEGA0036 alert: PegaRULES engine intentionally shut down. Previously in these circumstances, the Topology changes section of the Changes Summary landing page also displayed a "node status lost" message. Now, the page displays only a "node shut down" message.
  • PDC now features improved performance of several REST services. As a result, your system processes service requests faster.

Pega Predictive Diagnostic Cloud 2.52 (July 15, 2020)

  • You can now track node status changes more reliably by using the redesigned Topology Changes section of the Changes Summary landing page. The section now correctly recognizes all edge cases, such as the reversed order of messages, and stores the entire history of node status changes. For more information, see Changes Summary landing page overview in Pega Predictive Diagnostic Cloud.
  • On the Changes Summary landing page, PDC now correlates rule changes that occur less than 60 seconds apart. As a result, you can quickly analyze all changes that occur together in the same batch.

Pega Predictive Diagnostic Cloud 2.51 (July 8, 2020)

  • Improved the case correlation logic for the PEGA0027 event (Number of rows exceeds database list limit). If a PEGA0027 alert returns empty SQL, the corresponding PDC case now provides the relevant report rule name in the correlation.
  • When a system is under maintenance, the Agents, Elasticsearch, and Queue Processor landing pages of the System Resources section display an information banner. For more information, see Maintenance mode in Pega Predictive Diagnostic Cloud.
  • Enhanced the case description for SMTP0003 events (Email sending failure) to provide more details about the problem and help you to more quickly and accurately diagnose email client issues.

Pega Predictive Diagnostic Cloud 2.50 (July 2, 2020)

Pega Predictive Diagnostic Cloud 2.49 (June 25, 2020)

  • Performance enhancements to the System Resources > Elasticsearch landing page.
  • To quickly view and diagnose database-related information, you can now expand and collapse charts on the System Resources > Database landing page.
  • When a system is under maintenance, a warning message is displayed with a link to an article on the Community site, to help you better understand maintenance mode in PDC. For more information, see Maintenance mode in Pega Predictive Diagnostic Cloud.
  • When the Usage Viewer landing page and the System Assessment landing page are not displaying data, a warning message is displayed with a link to a troubleshooting article on the Community site, to help you resolve the issue. For more information, see Missing Usage Viewer and System Assessment data.

Pega Predictive Diagnostic Cloud 2.48 (June 18, 2020)

Pega Predictive Diagnostic Cloud 2.47 (June 10, 2020)

Pega Predictive Diagnostic Cloud 2.46 (June 4, 2020)

  • This version provides performance and stability enhancements.

Pega Predictive Diagnostic Cloud 2.45 (May 28, 2020)

Pega Predictive Diagnostic Cloud 2.44 (May 21, 2020)

  • On the System Assessment landing page, you can now view multiple pages listing service interactions. Use this enhancement to learn how clients and external systems interact with services that are exposed in your system.

Pega Predictive Diagnostic Cloud 2.43 (May 13, 2020)

  • You can now view MRU cache information on the Enterprise landing page System Info tab of a particular node. This information can help you perform advanced debugging of PEGA0016 and PEGA0017 alerts, and high CPU interactions.
  • Performance and usability enhancements:
    • The OPS0026 event (Connection pool timeout) is now correlated based on the node ID instead of the node type.
    • The OPS0014 event (Latency in search update) now has metric (KPI) values based on the count of pending items.
    • PDC now recognizes when a PEGA0010 alert (Agent processing disabled) indicates that an agent is manually disabled. PDC labels PEGA0010 alerts that are created for such circumstances as Manually agent disabled.

Pega Predictive Diagnostic Cloud 2.42 (May 6, 2020)

  • The enhanced event investigation mechanism now displays the date of the last event more accurately, and is always consistent with the date that is displayed for that case.
  • The new Remote column on the Enterprise landing page displays the version of the PegaAESRemote ruleset in each of your systems. You can use this feature to quickly check whether you have the latest version installed. For more information about the ruleset, see Enhanced PegaAESRemote ruleset to support the latest Pega Autonomic Event Services features.

Pega Predictive Diagnostic Cloud 2.41 (May 1, 2020)

You can now automatically create ServiceNow incidents and events by subscribing to event-based notifications. For more information, see Integrating Pega Predictive Diagnostic Cloud with ServiceNow and Managing notifications in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.40 (April 23, 2020)

Performance and usability enhancements.

Pega Predictive Diagnostic Cloud 2.39 (April 15, 2020)

  • You can now send PDC cases to ServiceNow to create ServiceNow events. These events help you track performance issues in your system or application. Previously, PDC supported only ServiceNow incidents. For more information, see Integrations in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.38 (April 7, 2020)

  • PDC now recognizes alerts that Robot Manager sends when various errors in its functioning occur. As a result, you can use PDC to send notifications when these errors occur. For more information, see Notification options in Pega Predictive Diagnostic Cloud.
  • On the Session Info tab of an event, you can now find the node, requestor, and interaction ID of the event. This information can help you to quickly locate the session in which an event occurred.

Pega Predictive Diagnostic Cloud 2.37 (April 2, 2020)

  • PDC now proactively monitors listeners by analyzing relevant Pega Platform exceptions. To track these issues, PDC creates OPS00xx events and can send you notifications when they occur. The following listener-related issues are now tracked by PDC:
    • OPS0029 critical event – the correspondence queue has entries that have been waiting for processing for more than 15 minutes exception
    • OPS0030 critical event – the correspondence queue failure exception
    • OPS0031 event – the email listener unsupported operation exception
    • OPS0032 event – the javax.mail.* messaging exception
    • OPS0033 event – the com.sun.mail* messaging exception
    • OPS0034 critical event – listeners are in the disabled state
    • OPS0035 critical event – listeners have 1000 errors in 30 minutes
  • As part of your enablement, to ensure that you receive the essential notifications, you can now quickly find the most important event-based notifications to subscribe to by filtering by the #Recommended tag. For more information, see Notification options in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.36 (March 26, 2020)

Pega Predictive Diagnostic Cloud 2.35 (March 18, 2020)

  • PDC now provides more granular tracking of agent status issues in Pega Platform. If an agent appears to have an exception, has run for an excessively long time, or has an outdated snapshot, PDC generates an OPS0015, OPS0027, or OPS0028 event respectively and creates a unique AgentStatus case for each application server on which the problem occurs. You can receive notifications for each of these events by subscribing to the Agent status issues notification type. For more information, see Notification options in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.34 (March 10, 2020)

  • Cases that PDC creates from PEGA0001 alerts now have more concise titles and descriptions that help you to identify the component that caused the issue.
  • On the Event Viewer landing page, you can now quickly filter events by event, application, and interaction ID, by clicking an icon in the column headers.
  • PDC now removes potentially sensitive literal values from exception messages. All literal text is replaced by the string 'literal'.

Pega Predictive Diagnostic Cloud 2.33 (March 4, 2020)

  • PDC now identifies the java.lang.OutOfMemoryError exception as an OPS0025 event and creates or updates a corresponding Metaspace is out of memory case. To receive a notification when this exception occurs, subscribe to the Metaspace out of memory issue notification.
  • PDC now identifies the org.apache.http.conn.ConnectionPoolTimeoutException exception as an OPS0026 event and creates or updates a corresponding ConnectionPoolTimeout case. To receive a notification when this exception occurs, subscribe to the Connection pool timeout notification.
    To learn more about notifications, see Managing notifications in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.32 (February 27, 2020)

  • The enhanced Events tab for a case now uses the same user interface as the Event Viewer landing page, so that you can expand each event to see the details. The more consistent user interface improves usability and helps you analyze events related to a case more intuitively. To use additional filtering options, you can click to open the events in the Event Viewer.
    For more information, see Pega Predictive Diagnostic Cloud Event Viewer overview.

Pega Predictive Diagnostic Cloud 2.31 (February 27, 2020)

  • You can now receive a periodic summary of cases in your system by subscribing to the Cases summary daily-digest email notification. For more information, see Notification options in Pega Predictive Diagnostic Cloud.
  • On the Agent queues landing page in the System Resources section, you can now visually analyze agent queues to quickly diagnose and check the status of the queues.
  • On the Overview tab of a case, you can now analyze similar cases that reference other systems. The new Similar cases for other systems section provides a summary of each similar case so that you can quickly find out whether the same problem has occurred in multiple systems.

Pega Predictive Diagnostic Cloud 2.29 (February 7, 2020)

  • You can now set the frequency of event-based notifications. As a result, PDC sends a notification only after the number of events meets a specified threshold within a set time period, for example, 500 events in 10 minutes. You can set a condition for new notifications, and for notifications to which you already subscribe. This enhancement helps you ensure that all notifications provide the right context for taking further action. For more information, see Managing notifications in Pega Predictive Diagnostic Cloud.
  • On the Manage notifications landing page, you can now mute, unmute, and delete notifications in bulk by selecting multiple notifications. This enhancement helps you save time and organize notifications more conveniently.
  • You can now receive a periodic email summary of events that have occurred in your system by subscribing to the Event summary daily-digest notification. For more information, see Notification options in Pega Predictive Diagnostic Cloud.
  • PDC now identifies the FATAL: sorry, too many clients already exception as an OPS0007 event and creates or updates a corresponding case. To receive a notification when this exception occurs, subscribe to the Database configuration issues notification.

Pega Predictive Diagnostic Cloud 2.28 (February 1, 2020)

  • On the Event Viewer landing page, you can now investigate issues more efficiently by reusing your recent searches. This enhancement helps you save time and analyze the data more conveniently.
  • The performance of the Improvement Plan landing page is now significantly enhanced. As a result, you can spend less time waiting for pages to load and more time identifying and resolving issues.

Pega Predictive Diagnostic Cloud 2.27 (January 24, 2020)

In the new System Resources section, you can find statistics and detailed information about the usage and status of your database, Elasticsearch, job schedulers, queue processors, agents, listeners, and your system resources. You can use this data to check the health of various resources and backing services.

Pega Predictive Diagnostic Cloud 2.26 (January 24, 2020)

PDC now tracks topology changes that include node startups and shutdowns, and situations in which nodes suddenly stop sending health messages. The Topology changes section of the Changes summary landing page contains a list of these node changes, and links that you can click to quickly view each change in the Event Viewer.

Pega Predictive Diagnostic Cloud 2.25 (January 10, 2020)

  • The Enterprise landing page now contains a summary of all your monitored systems. At a glance, you can check the number of healthy systems; systems with any of the monitored parameters in the Critical, Urgent, or Warn state; systems that are offline, and systems that are currently under maintenance.
  • The enhanced Manage notifications menu helps you configure your subscriptions with fewer clicks. You can now subscribe to multiple notifications about multiple systems at the same time.
    For more information, see Managing notifications in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.24 (December 27, 2019)

  • You can now provide case-specific feedback to the PDC team by using the Did you find this case helpful? widget on the right side of the case view. Use this feature to submit ideas for improvement and to inform the team about any issues that you encounter.
  • PDC now recognizes the following alerts and exceptions:
    • The Dataflow started or Dataflow resumed (PEGA0082) alert.
    • The Dataflow completed, Dataflow paused, or Dataflow stopped (PEGA0083) alert.
    • The Cluster segmentation causes subclusters to form (PEGA0090) alert.
    • The Queue processor delayed/scheduled message processing failed (PEGA0102) alert.
    • The Split-Brain Syndrome (PEGA0108) alert is treated as a critical event.
    • The MLaaS external service authentication failed (PEGA0111) alert is treated as a critical event.
    • The MLaaS external service connection time-out (PEGA0112) alert is treated as a critical event.
    • The Service package timeout exception is recognized as an OPS0023 alert.
    • The Java heap space out of memory exception is recognized as an OPS0024 alert and treated as a critical event.

Pega Predictive Diagnostic Cloud 2.23 (December 21, 2019)

  • On the Event Viewer landing page, you can now view events that reference a specific value, such as requestor, operator, or node, by clicking the Filter icon next to the value. This enhancement helps you filter the results more quickly and conveniently.

Pega Predictive Diagnostic Cloud 2.22 (December 12, 2019)

  • Event-based email notifications now contain a link to the relevant case, so that you can analyze the number of occurrences and other details of an issue directly in PDC.
  • The Enterprise landing page now displays the details of the system that you select in the PDC header. This usability enhancement helps you quickly analyze and assess the contextual data of a system.

Pega Predictive Diagnostic Cloud 2.21 (December 5, 2019)

  • You can now view the type of metric that PDC uses for each event. The Metric column on the Event Viewer landing page now displays the value and the appropriate unit of measurement: milliseconds for time-based events, bytes for size-based events, and no unit for events that are count-based or triggered by a single occurrence.
  • On the Overview tab of a case, you can now analyze other cases that reference the same Pega Platform component. The new Other cases affecting this case section provides a summary of each related case.

Pega Predictive Diagnostic Cloud 2.20 (November 28, 2019)

If you are unable to receive the standard PDC notifications, for example, because of strict security settings of your network, you can now use a REST API that PDC provides to receive event-based notifications with OAuth 2.0 authentication.
For more information, see Subscribing to Pega Diagnostic Cloud notifications by using a REST API and Managing notifications in Pega Predictive Diagnostic Cloud.

Pega Predictive Diagnostic Cloud 2.19 (November 28, 2019)

  • In Event Viewer, you can now group events by requestor. Use this enhancement to determine the number of occurrences of an issue for each requestor.
  • You can now assign cases from directly within a case by using the Actions > Reassign option.

Pega Predictive Diagnostic Cloud 2.18 (November 14, 2019)

You can now find the options for managing notifications and other system settings on the right side of the header in PDC.

Pega Predictive Diagnostic Cloud 2.17 (November 6, 2019)

  • You can now schedule maintenance mode separately for each of your systems. This enhancement helps you avoid false alarms about a specific system, for example, if the system is undergoing maintenance or planned downtime.
  • The TOP 5 reliability daily digest now includes issues from the Operations category of Improvement Plan. As a result, you can learn about important issues that affect your system's reliability.
    To subscribe to this digest, see Subscribing to notifications in Pega Predictive Diagnostic Cloud.

    Pega Predictive Diagnostic Cloud 2.16 (October 29, 2019)

    • You can now quickly mute and unmute notifications directly from the Manage notifications menu. Save time by temporarily disabling notifications that you do not want to receive, instead of deleting and adding it again later. Additionally, you can quickly check which notifications you have muted.
    • Learn about the available notifications in PDC, their area of impact, and notification options, by clicking the Help button in the Manage notifications menu.
      For more information, see Notification options in Pega Predictive Diagnostic Cloud.

    Pega Predictive Diagnostic Cloud 2.15 (October 25, 2019)

    In Event Viewer, tabs that contain no data now appear dimmed and are disabled. This enhancement helps you save time by avoiding unnecessary clicks while you analyze an issue.

    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 to send.
    For more information, see Subscribing to notifications in Pega Predictive Diagnostic Cloud.

    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 to troubleshoot your system more quickly.
    • The Top 5 user impact daily digest notification 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.

    For a list of enhancements to earlier versions of PDC, see Pega Predictive Diagnostic Cloud release notes archive.

    System Administrator System Architect System Administration
    Suggest Edit

    100% found this useful


    Related Content

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.