Posted: 7 Aug 2018 6:04 EDT Last activity: 27 Dec 2018 9:07 EST
SLA for ExecuteProgramRun flow in marketing not triggering the expecting log message
I have a requirement to log message if the executeProgramRun flow does not complete with in a specified time . I am not sure if SLA given in the flow is picked up and I am unable to trace the requestor thread. Also the log message is not seen anywhere in the log files. Need your expert assistance.
***Edited by Moderator Marissa to update SR Details***
In order to provide assistance some more information is needed. Can you please explain further what you mean by 'I am not sure if SLA given in the flow is picked up'? Have you customized the 'executeProgramRun' flow? Also, please indicate what version of Pega Marketing and Pega you have installed.
Some more information about the use case requiring logging the message would be helpful too. Logging a message doesn't seem like the most effective mechanism for communicating this information.
The problem statement is to trigger an alert when a campaign is not completing with in a stipulated time . So the design which I could think of was to customise the ExecuteProgramRun flow and include an SLA in the design which I am not able trace or confirm if its being executed. that is what I am trying to convey in 'I am not sure if SLA given in the flow is picked up'? . Please let me know if you have a better approach to achieve this requirement.
Could you explain in a bit more detail how you will use this log data. Is the intention to monitor campaign performance by reviewing the logs for these messages? Or is there a plan for some action to be taken when the log entry is recorded? Having an understanding of the goal could help us provide more assistance.
Starting in Pega Marketing 7.31 there are some extension points available in the ExecuteProgramRun flow. If possible it would be advisable to use these instead of overtaking the flow itself.
We have a requirement to trigger an incident /notification if the campaign does not completed with in the prescribed time. There is a Tivoli system which will listen to PegaRules.log file for configured alerts and raise an incident depending on the alert.
For now the design that I have thought of is to write a log-Message in the SLA activity, which would in turn be read by the external system.
Version of Pega marketing -7.31
Please let me know if any of the available extension points would help complete this requirement.
Yes Marissa, i am in the process of verifying the solution provided. will keep this thread posted . We have a dev rebuild scheduled in the first week of Jan , will confirm the SLA issue after the rebuild