Skip to main content

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.

Support Article

Log usage data - average response time not updated in AES

SA-8453

Summary



You see that there is no data present in response time reports in AES from monitored nodes. Data being received for ALERT messages and general Health information is being updated on the Health tab of the AES portal.

Error Messages



154 [ PegaRULES-Batch-1] [ STANDARD] [ PegaRULES:07.10] (sageData.PegaAESRemote_.Action) DEBUG - Running step 1_circum0
154 [ PegaRULES-Batch-1] [ STANDARD] [ PegaRULES:07.10] (sageData.PegaAESRemote_.Action) DEBUG - Running step 2_circum0
154 [ PegaRULES-Batch-1] [ STANDARD] [ PegaRULES:07.10] (sageData.PegaAESRemote_.Action) DEBUG - PegaAESRemote.PushLogUsageData: Error unable to find appender to use


Steps to Reproduce

  1. Open AES portal as aesuser.
  2. View response time reports from Reports tab.
  3. The Scorecard reports are also missing Response Time data.

Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment. 

Resolution



In order for Pega7 monitored nodes to send information to AES, uncomment the following entries in prlogging.xml (these are commented by default):
 

<!-- Example of sending real-time information to AES
                                <appender-ref ref="EXCEPTION-ASYNC"/> 
                                <appender-ref ref="HEALTH-ASYNC"/>
                                -->
 
               
<!-- Example of sending real-time information to AES     
                                <appender-ref ref="AES-ALERT-MSG"/>
                -->

 
Create the following two Dynamic System Settings in the monitored node and replace ‘3eaa1209ed9b00922e867aafe8599fc0’ with the monitored Node ID.

Owning Ruleset: PegaAESRemote
Purpose: 3eaa1209ed9b00922e867aafe8599fc0:altSOAPURL
Value: http://AESServer:port/prwe/PRSOAPServlet

Owning Ruleset: PegaAESRemote
Purpose: 3eaa1209ed9b00922e867aafe8599fc0:SOAPAppenderEnabled
Value: true


For PushLogUsageData 
to be sent successfully, add below DSS

Owning Ruleset: PegaAESRemote
Purpose: aessetting/perfstatmode
Value: PUSH

Published April 20, 2015 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community 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.

Close Deprecation Notice
Contact us