Skip to main content

Table of Contents

Changes Summary landing page in Pega Predictive Diagnostic Cloud

The Changes Summary landing page lists the changes that occur in a monitored system within the last 30 days. You can use the page to troubleshoot unusual behavior in your system, for example, to check whether periods of very slow response times coincide with system updates.

"Examining events listed on the Changes Summary landing page"
Examining events listed on the Changes Summary landing page

The Changes Summary shows the following lists of changes in your system:

  • Platform imports – Files that operators import into your application, such as JAR and ZIP packages with application upgrades, and the operators performing the imports.
  • Rule updates – Snapshots of recent rule updates. You can view a detailed list of up to the 50 most recently updated rules, and the operators that updated the rules, by clicking the number of updates.
  • Pega Platform updates – Changes to the Pega Platform version in your system.
  • Configuration changes – A list of configuration changes in your application that includes the type of configuration change, the ID of the node on which the change occurred, the value before the change, and the new value.
  • Topology changes – Changes that include node startups and shutdowns, and situations in which nodes suddenly stop sending health messages. You can click a link to quickly view each change in the Event Viewer.
    • Node started – When a PEGA0008 alert confirms a successful node startup. For more information, see PEGA0008 alert: PegaRULES engine started.
    • Node shut down – When a PEGA0036 alert confirms an intentional node shutdown. For more information, see PEGA0036 alert: PegaRULES engine intentionally shut down.
    • Node status lost – PDC failed to receive three consecutive health messages from the node.
    • Node alive – When a node starts sending health messages, but a PEGA0008 alert does not confirm the node's startup.
    • New type – When a new type of node is detected, for example, if all the nodes are Stream nodes and WebUser nodes, and then a BackgroundProcessing_BIX_Search node is detected.
Did you find this content helpful?

Related Content

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us