Pega Autonomic Event Services 7.3 Release Notes
Pega® Autonomic Event Services 7.3 includes several enhancements, such as support for several new performance and security alerts, basic support for custom and nonstandard alerts, manual refresh of scorecards, additional advice for top-level browser and service alerts, declarative partitioning, an improved scorecard, and a new system health grading system with customizable grade thresholds.
For more information and a list of additional documentation available for this release, see the Pega Autonomic Event Services product page.
For more information about Pega Platform 7.3, see Pega Platform Release Notes.
Support for new performance alerts
Pega Autonomic Event Services 7.3 introduces full support for several new types of alert messages. It has unique action item types, correlation logic, and advice for each of the following newly added alerts:
- PEGA0055 - Clock drift exceeded the configured time threshold; this issue is now treated as an urgent event
- PEGA0058 - Interaction History read time above threshold
- PEGA0059 - Interaction History write time above threshold
- PEGA0060 - Number of Interaction History rows read above threshold
- PEGA0061 - Number of Interaction History rows written above threshold
- PEGA0062 - Data Flow execution time above threshold
- PEGA0063 - Decision Strategy execution time above threshold
- PEGA0064 - Maximum number of rows processed by the strategy above threshold
- PEGA0065 - Adaptive Decision Manager set response time above threshold (include payload size)
- PEGA0066 - Mobile App Data-Sync Failure
- PEGA0067 - DSM social media dataset error
- PEGA0068 - DSM social media dataset warning
- PEGA0069 - Client page load time
- PEGA0070 - Adaptive Decision Manager has used 90% of the allocated memory
- PEGA0074 - Decision Data Store write time above threshold
- PEGA0075 - Decision Data Store read time above threshold
- PEGA0076 - Decision Strategy Manager service node is unreachable
- PEGA0077 - Data Flow assignment time above threshold
- PEGA0078 - Number of records returned by the Compose shape is above threshold
- PEGA0079 - Record size written by Decision Data Store above threshold
- PEGA0080 - Record size read by Decision Data Store above threshold
- PEGA0081 - Visual Business Director query time above threshold
- PEGA0084 - Search node count
- PEGA0085 - Decision Data Store disk space below threshold
- PEGA0086 - Requestor locked by a busy thread
- PEGA0087 - Service SLA violation
For more information about Pega Platform alert messages, see Performance alerts, security alerts, and Autonomic Event Services.
Support for security alerts
Pega Autonomic Event Services 7.3 now supports security alerts. The application can analyze these alerts, create action items for them, and send critical alert emails when appropriate. Security alerts ensure that system administrators are informed whenever the security of a Pega Platform web node server is at risk.
For more information about Pega Platform alert messages, see Performance alerts, security alerts, and Autonomic Event Services.
Basic support for custom and nonstandard alert messages
Pega Autonomic Event Services 7.3 adds basic support for custom and nonstandard alert messages. It creates a single action item case for each such alert per system.
Query counts and times for top-level browser and service alerts
Additional advice provided with PEGA0001 and PEGA0011 action items now indicates when many database queries in an interaction are collectively taking a significant amount of time. This information helps application developers and system administrators to quickly understand the root cause of slow browser and service response times and improve the user experience of an application.
Declarative partitioning
Pega Autonomic Event Services 7.3 includes an extension point that simplifies database partitioning and optimizes database storage management. Sample implementation for Postgres DBMS is available on request.
New notification scorecards
Pega Autonomic Event Services 7.3 adds several new types of notification scorecards for which managers can add subscriptions. Specified recipients can now stay informed about the following new events:
- Adaptive Decision Manager Memory - Notifies of PEGA0070 alerts, when the Adaptive Decision Manager service has used at least 90% of the allocated memory. The allocated memory is a user-specified threshold that is a part of the service definition.
- Requestor Lock Exception - Notifies of PEGA0086 alerts, when the maximum number of attempts to acquire a lock on a requestor has been exceeded and a thread fails to obtain a lock on the requestor and displays the RequestorLockException message.
- Clock drift time exceeded - Notifies of PEGA0055 alerts, when the clock drift in any of the participating nodes in a multinode cluster exceeds the configured time threshold.
- Decision Data Store disk space below threshold - Notifies of PEGA0085 alerts, when the amount of free disk space on a Decision Data Store node is lower than the amount of disk space that is used by Cassandra on this node.
- Decision Strategy Manager service node is unreachable - Notifies of PEGA0076 alerts, when, for any Decision Strategy Manager (DSM) service, the status of a designated node changes from normal to unreachable. This issue can occur for all the DSM services (Decision Data Store, Adaptive Decision Manager, Visual Business Director, Data Flow).
- Service SLA violation - Notifies of PEGA0087 alerts, when a service-level agreement (SLA) violation for a service is detected and a fallback activity is in use.
- Social media error - Notifies of PEGA0067 alerts, when the social media data set (Facebook or Twitter) that is the source of a data flow encounters a fatal error that stops the data flow.
For more information, see Managing Pega Predictive Diagnostic Cloud scorecard and alert subscriptions.
Manual refresh of scorecards
It is now possible to manually update a selected scorecard. Managers who use Pega Autonomic Event Services to actively assign action items to users and workbaskets, close items that have been fixed, and tag items with tracking system IDs can regenerate a scorecard to reflect the changes by clicking an icon on the dashboard.
Improved scorecard with simpler and transparent system grades
Pega Autonomic Event Services 7.3 introduces a new grading system for system health. The overall system health takes into account three subgrades: browser response time, service response time, and alert and exceptions rate. Three icons for each grade on the scorecard categorize the status as healthy, warning, or critical.
A new section displays the top operation issues, which might directly result from browser or service interactions. For example, the PEGA0017: Cache exceeds limit alert is a typical alert in this category.
For more information about the scorecard, see Pega Predictive Diagnostic Cloud scorecard overview.
Grade thresholds customized per system
Managers can now define custom thresholds for each subgrade for each monitored system. The ability to adjust the default values increases confidence in the grades, and is especially useful, for example, when a system with unique requirements is expected to send an unusually large number of alerts of one kind.
Issues addressed in this release
The following issues have been resolved in this release. These issues are likely to have the most effect on the Pega user and developer community.
|