How Pega Predictive Diagnostic Cloud manages monitoring data
Note: The following content, referenced from Pega Documentation, is included here to help you better achieve the module learning objectives.
Each Pega Platform client has a dedicated Pega Predictive Diagnostic Cloud (PDC) virtual user account, called a tenant. Each tenant can monitor
any number of applications that belong to the same client.
You can configure PDC to monitor different environments, as shown in the following
figure:
One-way data push model in PDC
Each Pega Platform instance contains PDC monitoring agents that
collect diagnostic data. Your system sends alerts and diagnostic data through Amazon
Simple Queue Service (SQS) asynchronously, which prevents the slowing of your systems.
After receiving the data, PDC identifies issues in your system, and can send you
notifications about events critical to your business.
What data Pega Predictive Diagnostic Cloud collects
Note: The following content, referenced from Pega Documentation, is included here to help you better achieve the module learning objectives.
Pega Predictive Diagnostic Cloud (PDC) collects, parses, and aggregates the monitoring
data without the need of user involvement. The data that PDC presents provides an in-depth
view of issues and events in your system, which increases your control over how your
applications operate, and helps you eliminate errors.
PDC collects the following data:
Rule usage and rule changes
Processes that occur inside your application
System resources
Data flow between interface elements and data pages
Performance statistics
Note: When monitoring a development environment, PDC collects data from all
developers that use the environment.
Data that PDC collects belongs to two general categories:
Each Pega Platform™ instance includes PegaAESRemote, a PDC
monitoring agent. This agent collects information from Pega Platform™ components and sends the information to PDC in five-
or ten-minute intervals by using REST services. PDC receives the information
regardless of the activity in the system, which means PDC monitors your application
even when it has no traffic.
The PDC monitoring agent collects the following data:
Resource information, for example, memory or CPU usage
Components health, for example, queue processors or listeners
Backing service information, for example, search service
After receiving data, PDC creates a visual dashboard of system health, using visual
charts, graphs, and diagrams to present the information on the System Resources
landing page.
When specific conditions occur, or when your application encounters an exception,
Pega Platform generates alerts and registers them in the Pega
Alert log. Based on these records, PDC creates system events. The Pega Alert log
includes the following alert types:
Predefined PEGA alerts, which occur in specific conditions.
Alerts raised by Pega Platform components, for example, HTML
generation, SQL execution, internal database, backing services.
Unhandled exceptions inside your application that were not identified by Pega
Platform.
Note: The alerts do not contain any console output. Each alert has
a predefined structure which collects only the information necessary to identify the
issue, such as type and time of the operation. PDC does not collect any Personal
identifiable information (PII).
Events created by PDC contain additional details useful in diagnosing and remediating
issues and offer real-time notifications for urgent events. PDC also further
aggregates correlated events into cases.
PDC presents all created events in the Event Viewer.
Pega Academy 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.
