Hi Shashidhar,

After discussion with our product specialists gathered some of the important features in AES 7.2 from its earlier versions are as follows:

1. Scorecard Pre-Calculation. Scorecard data is calculated via batch agent.
   1. Dramatically reduces response time during login and when switching tenants.
   2. All users see consistent state-of-the-system.
   3. Scorecards may be re-distributed at will.
2. PUSH Mode support. AES 72 significantly reduces load on monitored Pega71 systems.
   1. Pega71 systems can PUSH usage data to AES; eliminating need for AES to SOAP into node to gather data.
   2. Pega71 systems push database schema data daily; eliminating need for AES to SOAP to pull schema data for each new alert.
3. Secure communications.  AES now supports HTTP Authentication in addition to SSL encryption.
4. Granular alert thresholds. AES 72 provides THREE options to filter “the usual suspects”
   1. If an item is considered to be a non-issue and will not be worked, managers may take action “Ignore this issue”
   2. If a specific query / connector / stream / service is expected to be slower than standard threshold, managers may take action “Elevate KPI”.
      AES72 evaluates each alert against in-memory table of elevated KPI’s and ignores instances that are below the higher-bar when appropriate.
   3. AES72 has a delegated decision table to allow developers to simply construct complex filtering criteria for alerts and exceptions
5. Supports new alert format introduced with Pega718. As shipped AES 717 can not monitor Pega718+
6. Runs on Pega72+ platform.
7. Explicitly Postgres testing and support. Use of Postgres may significantly reduce cost of AES adoption and operations.

Hope this information might be helpful to you.

Regards

Mahesh

Hi Shashidhar,

After discussion with our product specialists gathered some of the important features in AES 7.2 from its earlier versions are as follows:

1. Scorecard Pre-Calculation. Scorecard data is calculated via batch agent.
   1. Dramatically reduces response time during login and when switching tenants.
   2. All users see consistent state-of-the-system.
   3. Scorecards may be re-distributed at will.
2. PUSH Mode support. AES 72 significantly reduces load on monitored Pega71 systems.
   1. Pega71 systems can PUSH usage data to AES; eliminating need for AES to SOAP into node to gather data.
   2. Pega71 systems push database schema data daily; eliminating need for AES to SOAP to pull schema data for each new alert.
3. Secure communications.  AES now supports HTTP Authentication in addition to SSL encryption.
4. Granular alert thresholds. AES 72 provides THREE options to filter “the usual suspects”
   1. If an item is considered to be a non-issue and will not be worked, managers may take action “Ignore this issue”
   2. If a specific query / connector / stream / service is expected to be slower than standard threshold, managers may take action “Elevate KPI”.
      AES72 evaluates each alert against in-memory table of elevated KPI’s and ignores instances that are below the higher-bar when appropriate.
   3. AES72 has a delegated decision table to allow developers to simply construct complex filtering criteria for alerts and exceptions
5. Supports new alert format introduced with Pega718. As shipped AES 717 can not monitor Pega718+
6. Runs on Pega72+ platform.
7. Explicitly Postgres testing and support. Use of Postgres may significantly reduce cost of AES adoption and operations.

Hope this information might be helpful to you.

Regards

Mahesh