CDH usage statistics in Pega Predictive Diagnostic Cloud
The landing page provides statistics and detailed data about Pega Customer Decision Hub™ and lets you check the business usage and load patterns in your Customer Decision Hub applications. With this information, you can better plan and optimize the use of resources in your system, which is especially useful for a system administrator or an account executive. For example, if strategy execution times become longer and event processing rates decrease, you might need to increase the processing capacity of your system.
You can access this information for all your systems with the following Pega Platform™ versions:
• For Pega Platform 8.6, version 8.6.1 and later
• For Pega Platform 8.5, version 8.5.5 and later
• For Pega Platform 8.4, version 8.4.6 and later
metrics data in PDC is aligned with Customer Decision Hub taxonomy components from the Customer Decision Hub framework. With the landing page, you can correlate metrics data with business related components, for example, a real-time container that is associated with the Next-Best-Action Designer. For more information, see Next-Best-Action Designer taxonomy.
Every hour, the PDC monitoring agent in your application sends Customer Decision Hub usage data to PDC. Customer Decision Hub metrics measure the count of decisions, events, and actions that your customers perform, and captures the response times for each interaction of the customer in your application. By automatically processing and aggregating this data at 15-minute intervals, PDC helps you to identify the application features that cause the particular usage patterns that PDC observes. This monitoring capability helps you with capacity planning, determining the throughput of your system, and configuring the performance parameters. To help you better manage the Customer Decision Hub data, you can export the results of each metric as CSV files.
The following table lists the metrics that you can monitor:
| Metric | Information |
|---|---|
| Batch decision | The number of batch decisions that nodes in your system performed in the selected time period. |
| Real-time decisions | The number of real-time decisions per second that nodes in your system performed in the selected time period. |
| Stream events | The number of stream events that nodes in your system processed in the selected time period. |
| Batch data loads | The number of data processing batch data-flows that nodes in your system performed in the selected time period. |
| Real Time Data Loads | The number of data processing real-time data-flows that nodes in your system performed in the selected time period. |
| Stream data loads | The number of streaming data-flows that nodes in your system performed in the selected time period. |
| Customer | The count of unique customers loaded into the customer table that is mapped to the primary context. This metric is updated every day. |
| Prospect | The count of unique prospects loaded into the prospect table. This metric is updated every day. |
| Email queue depth | The number of email messages that nodes in your system staged in the selected time period. |
| Email processed | The number of emails that nodes in your system processed successfully in the selected time period. |
| SMS queue depth | The number of SMS messages that nodes in your system staged in the selected time period. |
| SMS processed | The number of SMS messages that nodes in your system processed successfully in the selected time period. |
| Paid Media | The number of paid media audience counts that nodes in your system processed successfully in the selected time period. |
| Push Notifications | The number of notifications that nodes in your system processed successfully in the selected time period. |
| Cassandra storage consumed | The amount of disk space that Cassandra used across all Decision Data Store (DDS) nodes. |
| S3 storage consumed | The amount of disk space used by files in the S3 repository. |
| IH_Fact storage consumed | The amount of disk space used by interaction history records. |
| Strategy Responses | The average time that decision strategies across all nodes in your system took to process data in the selected time period. |
| Context Data Loads | The number of context data processing like loading customer associated data that nodes in your system performed in the selected time period. |
| Capture Response | The number of capture responses for the selected time period. |
For more information about the Customer Decision Hub usage metrics that are monitored by PDC, see Pega Customer Decision Hub metrics in Pega Predictive Diagnostic Cloud.
Configuring Customer Decision Hub metrics for non-production environments
PDC can also capture Customer Decision Hub metrics data for non-production environments for up to 10 days. After the configured date, PDC automatically stops collecting metrics for non-production environments. For example, if today is July 29 and you configure the end date as August 7, PDC stops collecting data on August 8.
To enable this function:
- Configure the PEGAAESREMOTE!AESSETTING/CAPTURERUNMETRICSTILL Dynamic System Settings (DSS) by providing an end date in the GMT format.
Reclassification of data-flows
If you have a manager role, you can reclassify data-flows. You can reassign data-flows from Data Processing to other categories based on a specific use-case to adjust your Customer Decision Hub metrics data in a way best suited for your business to help you bring maximum business value.
You can further configure the landing page view to present data that you currently need.
Previous topic System Assessment landing page in Pega Predictive Diagnostic Cloud Next topic Pega Customer Decision Hub metrics data in Pega Predictive Diagnostic Cloud