Issues Tab is not loading any alerts data

Pega Alerts are not loading in the Issues tab like it usually does. Appreciate if any help regarding the issue

Hi @Kishore Sanagapalli,

Got it! If Pega Alerts are not loading in the Issues tab, here are some possible reasons and solutions:

1. Check if Pega Alerts Logging is Enabled

  • Go to Dev StudioConfigureSystemOperationsLogs.
  • Check if PEGA0001 - PEGA9999 Alerts are being generated.
  • If no alerts are appearing, they might be disabled in prconfig.xml.

:white_check_mark: Fix:

  • check Records → sysadmin → Dynamic System Settings (DSS):

    Owning Ruleset: Pega-Engine
    Setting Purpose: alerts/active
    Value: true
    
    
  • Restart the server after enabling alerts.

2. Verify Logging Level Configuration

  • Go to Admin studio → Resources → log categories page
  • Check if Alerts are set to an appropriate level (INFO or DEBUG). otherwise click 3dots(More), change log level

:white_check_mark: Fix:

  • If alerts are set to OFF, change them to INFO or DEBUG and restart the system.

3. Check if PegaRules Logs Contain Alerts

  • Download the logs from ConfigureSystemOperationsLogs.
  • Open the PegaRULES.log file and check if any alerts (PEGA0001, PEGA0005, etc.) are being generated.

.:white_check_mark: Fix:

  • Restart the node or use “Clear Cache” in Admin Studio to force a refresh.

Next Steps

  • Let me know what you found!
  • If alerts still aren’t showing, we can try enabling PDC/AES logging for deeper debugging. :rocket:

I hope it works,

Thanks

Regards

Raja

@Koti Raja

Hello Raja,

Thanks for pitching in and your response. All the above suggested changes are as is basis and we did not observe any deviation in that.

Suspecting the issue could be due to the prlog4j2.xml custom change i have made to later the pega app-logs time zone. Working on the same. I will keep it posted here.

Hi @Kishore Sanagapalli,

Ok, Please post here

Thanks

Regards

Raja

@Koti Raja

It’s confirmed. As part of Pega Logs Retention in OpenShift | Support Center, I was implementing the Logs retention and logs to be printed in Asia Riyadh Timezone.

Changes made to the prlog4j2.xml file with xml tag of Asia/Riyadh is conflicting in the PegaRULES-Alert layer. GMT8 is the default hardcoded one for PegaRULES-ALERT and it’s not accepting any other timezone.

Issues Tab alignment is getting changed with added tag in the PegaRULES-ALERT layer in prlog4j2.xml but it’s working fine for all other logging levels.

Issue has been resolved upon removing the Asia/Riyadh xml tag in the PegaRULES-ALERT layer in prlog4j2.xml.