Kalashikam VijayKanth (Kalashikam)
Verizon Data Services India Pvt Ltd
Kalashikam VijayKanth
Verizon Data Services India Pvt Ltd
Kalashikam Member since 2017 2 posts
Verizon Data Services India Pvt Ltd
Posted: June 12, 2020
Last activity: December 2, 2020
Posted: 12 Jun 2020 9:20 EDT
Last activity: 2 Dec 2020 7:26 EST

Adding Customized Properties to Alert Log

Hi Team,


As of now, we have some default properties which we use to log the alerts.


But in advanced world there is a chance of working multiple users on a single rule. Due to this, there is a chance of getting multiple exceptions/alerts during the run time. These may come because a developer not following proper guidelines.


When as a Developer and as a User tried to analyze these log I wish I could have these additional customized properties in the logs which make my life easy.


As a Developer,

- If the logs have the version and developer name who recently worked, then it will be easy to assign this to the concerned person.


As an End User,

- Example, an application has some 150 requests that will be processed using PEGA (there are common rules which are used).

- Each request have some unique identifiers like request ID, session ID, etc. (pal log properties)

- During the processing of the request, I have got some 20 Alerts on the common rules used.

- Now, the only way to identify the occurrence of the Alert is 'Time Stamp'. This may take around 5 to 10 mins to identify the request which causing the alert.

- If we have an option to add my custom (pal log) properties to logs then I can identify the request in seconds.



- Easy identification of the alert

- It saves times

- Analyzing and fixing the alert will be easier



- Adding customized properties may decrease the performance as the log size increases. But, it can be fixed faster so that the alert will not repeat.


***Edited by Moderator Marissa to change type from Pega Academy to Product***

Pega Platform 8.2.5 Case Management Communications and Media Senior System Architect