Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Pega Autonomic Event Services 7.3 Release Notes

Updated on October 17, 2017

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.

The information in the Pega Predictive Diagnostic Cloud scorecard article also applies to Pega Autonomic Event Services 7.3.

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.

IDDescription
BUG-330895Incorrect link for an exception item in the Dashboard.
BUG-329014In the Verify the report Throughput in past week by work type report, the chart is empty.
BUG-331163The PDN link is missing for PEGA0074 alerts.
BUG-331519In Custom Node Reports, clusters with more than one node have duplicate entries in the Select a Cluster list.
BUG-331259Subscribed Alert Email scorecard is never sent.
BUG-329001On server restart, Pega Autonomic Event Services throws exceptions while trying to pull data.
BUG-331001The Disable Enterprise health 'drill in' features check box in System Settings is cleared although the underlying feature is enabled.
BUG-332458The Action/Exception Items Urgency Update agent has an incorrect time zone setting.
BUG-331162Pega Autonomic Event Services does not save pulled LogUsage data into the PegaAES-Data-LogUsage class, causing blanks on the Weekly Scorecard.
BUG-332685Microsoft SQL Server: Cleanup agent fails while User-Defined Functions (UDFs) are disabled on the database.
BUG-329097The available items report does not display data.
BUG-330134Clicking the Summary tab in the Enterprise Health console causes exceptions.
BUG-328879Alerts with KPI value lower than 0 are not created.
BUG-329809NullPointerException occurs when aesuser tries to access the Reports page.
BUG-306164Details for PEGA0086 alert do not display stack and trace data.
BUG-330719Emailed scorecard for Requestor Lock Exception does not display a solution.
BUG-294367Reports: the Select a node list is empty for aesuser in the AESWorkUserV7 access group.
BUG-257464The Cause tab for the cacheForced- work object is not necessary; to save resources, it should not appear.
BUG-329489Incorrect PDN links in some work items.
BUG-329485Clicking on a requestors record in the Enterprise Health console causes an error.
BUG-328747An offline system removed from the Enterprise Health console reappears after a few seconds.
BUG-325876Pega Autonomic Event Services allows uppercase node IDs.
BUG-324947The Enterprise Health console displays production level 0 for some systems.
BUG-326001Pega Autonomic Event Services displays errors after trying to pull data.
BUG-326434Agent number threshold is too low for Pega Platform 7.3 WebUser nodes.
BUG-312869Compilation errors appear in catalina.out on system start.
BUG-290023Similar messages with unexpected properties are not correlated correctly.
BUG-317186Alert Distribution Analysis does not display STDDEV values.
BUG-324935The SaveSummaryFromSnapshot DSS (Dynamic System Settings) does not work as expected.
BUG-312405The Delete Node feature in the Enterprise Health console removes alerts, exceptions, and statistics.
BUG-322608Analyze Application Perf for Alerts reports do not work as expected.
BUG-307276webwb.workform_pyreportingskin.css is not compatible with Pega Platform 7.2.
BUG-273154Oracle error ORA-12899: value is too large for column "PEGAAM_ALERT".PEGATHREADNAME.
BUG-320997Cannot navigate between MU- cases and PEGA0028 alerts.
BUG-300248Connection string is blank for a monitored Pega Platform 7.1.5 node deployed on WebLogic.
BUG-320995Memory alerts have KPIThresholds higher than the KPIThreshold property can handle, causing errors on displaying details of a memory accumulator alert.
BUG-317141Urgency explanation on exceptions is not displayed.
BUG-321026Parsing an update query with an APPEND hint is causing the application to hang.
BUG-322263Emails use the old weekly scorecard layout.
BUG-313752Data is truncated in 32-character database columns storing node IDs.
BUG-310052com.pega.pegarules.pub.database.AuthorizationException occurs when refreshing the scorecard.
BUG-317184Thousands of action items are created because of incorrect PEGA0069 correlation.
BUG-278480The same exception can be logged twice.
BUG-314645Invalid argument to native writeImage.
BUG-229814Assigned To is updated with blank when user clicks Cancel.
BUG-312518Tables do not contain Pega Platform Required columns.
BUG-315356Exception-3754: String index out of range: -109 occurs on the production server.
BUG-315278The PEGA0028 alert is causing a Perform Critical Alert Analysis agent error.
BUG-314405All scorecards and dashboards are showing Alerts and Exceptions percentage as 0.
BUG-313333CallcleanupAESAgent runs too frequently and causes lockups to the pegaam_alert table.
BUG-306171Operations Management dashboard section counts are wrong.
BUG-313252Add the HealthStatusChange scorecard to Pega Autonomic Event Services 7.2.
BUG-289249Report charts and data do not line up.
BUG-310667When changing the password, does not always confirm that passwords must match.
BUG-253628Open_ElevatedKPI status is changed to Open_InProgress.
BUG-311246CallcleanupAESAgent crashes.
BUG-261259System reports default start/end dates include time.
BUG-312366Incorrect PDN link in the weekly scorecard.
BUG-242897Error when doing Regenerate advice action work.
BUG-302525New items are created in the Unassigned workbasket instead of in the Triage workbasket.
BUG-294196User cannot change password.
BUG-305654The Refresh button does not work for the PegaInternal user.
BUG-309942On Monday, mashup displays two columns with incorrect column labels.
BUG-309391Mashup data is inconsistent with scorecards.
BUG-306984Pega Autonomic Event Services 7.2 cannot create custom reports because it lacks webwb.workform_pyreportingskin.css.
BUG-308042Action items are not getting assigned to an operator correctly.
BUG-303334The Delete System process can time out.
BUG-301232Node records are re-created when restarting a monitored node.
BUG-293792Wrong users are shown in "Assigned To" in Pega Autonomic Event Services action items.
BUG-294397Discrepancy between user count and the Max Unique Users report.
BUG-292685Wrong parameter passed to the Embed-ListParams.getC activity.
BUG-294402Report MaxUniqueUsersByDayEnterprise from Reporting > Enterprise > Unique Users does not agree with the scorecard reports user count.
BUG-294194Cannot select fields in custom reports.
BUG-295244Items in state Resolved-Closed do not reopen when they reoccur.
BUG-294183Node list in Pega Autonomic Event Services 7.2 is missing columns that were present in version 7.1.7.
BUG-292159Alert cause is not displayed for some alerts.
BUG-293822Current system is lost when clicking back to reports.
BUG-290399Report definition AlertCountSummaryForScorecard is failing frequently because of timing out.
BUG-291716Scorecard urgency and work object urgency do not match.
BUG-289035Current system is lost when clicking back to reports.
BUG-286602Calculations are using wrong time ranges.
BUG-288123Remove pzpvstream from processing info table to limit BLOB usage.
BUG-287521A table is missing for agent monitoring.
BUG-285652Integration fails on the bad data-admin-db-table record.
BUG-258019Slow AvgKPIInTimeRangeByPCFAndCategory report execution.
BUG-282661The Reports tab is not displayed by default.
BUG-280608Database query in parseAlertLine is taking more than the set threshold.
BUG-274906Browser freezes on invalid input in the time series report.
BUG-274905Table labels are missing in the alerts by day report.
BUG-258013The AlertCountSummaryForScorecard report is running slowly.
BUG-247223The message "This is a PRPC query and has already been carefully optimized" is inaccurate.
BUG-269866Nodes do not appear for a cluster.
BUG-269743UDFs are required by default on MS SQL.
BUG-262724The AlertGroupProblemCorrelationCommon report runs slowly.
BUG-268292The java.lang.StringIndexOutOfBoundException occurs while running the Process Problem Correlation activity.
BUG-265976Enterprise Health console features do not work at cluster level because of authentication issues.
BUG-260176RDBIO average trips value.
BUG-260179Incorrect spelling in RDBIO and DBIO advice.
BUG-259474File name validation logic in ParseLogForExceptions.
BUG-257444Alerts by Category by Day report not displaying complete data.
BUG-258638Failed to find instance PegaAES-Data-IndicatorComp.ShowMessage of type Rule-Obj-HTML.
BUG-258641NoSuchMethodException loading CompareBenefits.
BUG-258231Remove unnecessary precision for WarningSeverity and WarningCount.
BUG-257826Change observations description.
BUG-257521Fix the formatting of the DBIO average percentage.
BUG-257833Fix observation message when an average number of trips to the database is one.
BUG-254640Benefits should be sorted.
BUG-256369Error parsing PEGA0008.
BUG-252074The nodes data page is refreshed too often.
BUG-255884Fix the formatting of average percent.
BUG-255885Fix the inconsistent formatting of numbers in the Performance tab.
BUG-254641Fix the formatting of the average query counts number in advice.
BUG-253235Large number of PegaAES-Work-Action-DeclareIndexesThreshold work objects.
BUG-253241Large number of PegaAES-Work-Action-HTTPRequestCorrupted work objects.
BUG-254958The reference pyWorkPage.CumulativePalStats() is not valid.
BUG-249005Incorrect package exception for the last30minutesfornodex activity.
BUG-250356Could not find an implementation of Rule-Connect-SQL.
BUG-249849Fix the From name field in emails based on the UserName.
BUG-249023Issue in Weekly Summary table in the scorecard.
BUG-221103LogHelper: SOAP service fails while parsing Exception-826.
BUG-242910Cannot filter the records based on the Unassigned workbasket in the My Work page.
BUG-241694purgeOldData delete limit with MS SQL Server.
BUG-247585Remove validation on file name to upload exception log.
BUG-249006Time Range Reports alignment is not correct.
BUG-247063JFreeLibrary is referencing getAESChart from an old rule set.
BUG-247760Duplicate alerts are not setting a flag on node page.
BUG-242912In My Group, View Queue for Pega Autonomic Event Services actions is listing exceptions.
BUG-237929Last week occurrences count is incorrect in urgency explanation.
BUG-247380If agent node is down, other node should pick up the agents.
BUG-243624Success message is not appearing after updating configuration.
BUG-243075Critical Events Table has null entries for pxCreateDateTime.
BUG-247046Handle duplicate key exception.
BUG-242180Scorecard showing metrics for incorrect dates.
BUG-238877DC Enterprise Chart does not display data on production.
BUG-241721Offline upload requires a log name with a specific prefix.
BUG-244434Correctly update alert count.
BUG-228010Data-Admin-System-PDCConfiguration instances do not appear.
BUG-244416Correctly handle all outbound email ports.
BUG-245403Attachment is not required for scorecard email.
BUG-242877Chart is missing when you access admin > weekly scorecard.
BUG-245272The StartStopAccess DSS does not disable Pega Autonomic Event Services listener context.
BUG-239887The top status message incorrectly displays "by 0%".
BUG-241440Observing UNAVBL in the Weekly Summary table.
BUG-242368The top 10 browser items do not match the top 10 by urgency.
BUG-243078ORA-01438: value larger than specified precision allowed for column.
BUG-242708Ruleset AESCriteria 01-01-01 is dependent on the wrong ruleset.
BUG-242709Decision table CustCheckIgnoreAlert references non-existent property isIgnoredElevatedKPI.
BUG-241947Chart shows only partial data.
BUG-241032Should not show removed scorecard names in the email subscription pages.
BUG-241015InvalidReferenceException if nodes have special characters.
BUG-241294Exceptions Event counts are incorrect in scorecard.
BUG-238826Issue with daylight saving time.
BUG-236624Should not show the top issues status message if logusage is not available.
BUG-238782Issue with JFreeChart in 7.2.
BUG-231360InvalidValueException: String was not a date.
BUG-236596PDN link is incorrect for CacheForced workobject.
BUG-237034System Connectivity Report timing out.
BUG-236079Formatting issues with the Time (%) column in the scorecard email.
BUG-233349New Items Daily Scorecard email has empty parenthesis.
BUG-234888Optimize properties for reporting.
BUG-234079Time (%) column is missing in the scorecard email.
BUG-234775Values are above 100% in Top Service Items section.
BUG-234685Incorrect PDN link for DPFreqLoad work object (PEGA0053 alert).
BUG-231472Scorecard is not printing properly.
BUG-229505Null Pointer Exception on sending scorecard email without a scorecard snapshot instance.
BUG-235231Alerts List report definition is timing out.
BUG-217308InvalidReferenceException because of dash in node name.
BUG-218127Enterprise Health console incorrectly displays quiesced nodes.
BUG-233796The Top Issues section of email scorecard should show notification when no data.
BUG-233725Incorrect alignments in the PDF scorecard.
BUG-235230Duplicate Totals row in performance metrics in PDF scorecard.
BUG-234098Daily Monitoring Email is causing the ArrayIndexOutOfBounds exception.
BUG-233932Details of the last day of Daily Performance metrics are incomplete.
BUG-235371Scorecard incorrectly displays extra data in daily metrics section.
BUG-234578Number of urgencies for Service Items is 0.
BUG-235286Description problem in DPFreqLoad action item.
BUG-233786Showing '1 minutes' instead of '1 minute' in scorecard.
BUG-232435Browser performance metrics show incorrect dates.
BUG-233787Show message if the Weekly Summary table has no data.
BUG-230098Downloading scorecard PDF does not work.
BUG-233159Scorecard: Unable to open exception items from scorecard email.
BUG-233259Exception-931: CurrentWeekOccurrences and LastWeekOccurrences.
BUG-232720Invalid characters in node name cause exceptions.
BUG-231319Unable to generate Alerts by Category by Day Report.
BUG-231318Unable to create a subscription for the Agent Disabled scorecard.
BUG-231181Event Frequency, Event Count, and Total KPI always setting up to 0 cause incorrect urgency status.
BUG-231003Duplicate entries in the Weekly Performance Metrics.
BUG-230155Custom Node Reports display an error message.
BUG-231167Clusters are created with cluster name as NULL.
BUG-228612The alertEmail activity is final, but it should be non-final.
BUG-228979Cluster Production Level always displays 0.
BUG-231150Same number of events displayed for total alert events and total exception events for this week and last week.
BUG-221706Database exception ORA-24345: A truncation or null fetch error.
BUG-230141Enterprise Health console does not have pagination in urgent events.
BUG-229782Action item and enterprise reports are shown as part of system reports.
BUG-230288Cluster name is not showing in the manage SOAP authentication pop-up window.
You can look up Pega Platform bug fixes in the Pega Platform Release Notes.

Related articles

Installing Pega Autonomic Event Services 7.3Upgrading to Pega Autonomic Event Services 7.3

Tags

Pega Autonomic Event Services 7.3 Pega Autonomic Event Services System Administration

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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