Skip to main content

Node status and resources data

Suggest edit Updated on January 19, 2022

Pega Predictive Diagnostic Cloud (PDC) monitors the usage statistics, hardware resources, and status of each node in your system and provide you information about the health of all nodes. With this information, you can quickly assess the general state of your system.

You can view this information on the following landing pages:

  • Nodes landing page - usage statistics for the nodes in your system
  • Resource utilization landing page – resources used by each node in your system
  • Enterprise landing page - a summary of all nodes in your system
Note: For cloud-based deployments, Pega Clouds monitors, scales, and maintains nodes in your system. The node information that PDC provides is most useful for on-premises deployments.

Nodes

The Nodes landing page displays both active and inactive nodes in your system. You can inspect each node to see the following information:

  • When the node was last active
  • Resources that the node uses
  • The following parameters of the node:
    • Software version that the node runs
    • Information about the node structure
    • Configuration parameters and their values

If you use PDC on premises, you can subscribe to the Health status change notification. This notification triggers when a node encounters an issue.

For more information, see Health status change notification.

The following figure shows different functionalities of the Nodes landing page in PDC:

Exploring the Nodes landing page of PDC
Exploring the Nodes landing page of PDC

Resource utilization

The Resource utilization landing page displays usage statistics and detailed information about the status of CPU utilization by JVM, heap utilization, and the number of requestors active in your system. With this information, you can correlate drops and peaks of resource usage with other issues in your system.

On the Resource Utilization landing page, you can find the following types of information:

  • CPU utilization by JVM – The average CPU time utilization for each JVM in the specified time frame.
    Every ten minutes, the management daemon in Pega Platform sends a HLTH0001 health status message that includes the average CPU utilization, which is calculated in the following way: (CPU seconds used since the JVM started according to the JVM right now — CPU seconds used since the JVM started according to the JVM ten minutes ago) / (600 seconds * number of virtual CPUs on the server according to Java). The chart shows only the maximum value for every hour.
  • Heap utilization – The percentage of heap in use in the specified time frame.
    Every ten minutes, the management daemon in Pega Platform sends a HLTH0001 health status message that includes the heap utilization. The chart shows only the maximum value for every hour.
  • Active requestors – The number of active requestors in the specified time frame. The chart shows only the maximum value for every hour.

Each chart shows separate data for each node.

The following figure shows different functionalities of the Resource Utilization landing page in PDC:

"The Resource Utilization landing page"
Exploring the Resource Utilization landing page in PDC

Enterprise

The Enterprise landing page now contains a summary of your monitored systems. In a glance, you can check the following information:

  • Healthy systems
  • Systems with any monitored parameters in the Critical, Urgent, or Warn state
  • Offline systems
  • Systems currently under maintenance
Note: The Enterprise landing page is a legacy view. You can access the same information in the Nodes landing page.


 

  • Previous topic Database statistics in Pega Predictive Diagnostic Cloud
  • Next topic Elasticsearch landing page in Pega Predictive Diagnostic Cloud
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us