Hi All,
We are getting pdc PEGA0011 alerts in our production.
While searching in logs we are able to see only service activity name in logs.
Please help me to get this issue resolved. Please find the logs in the attachment.
We are getting PEGA0020 alerts along with this.
PEGA0011.docx (14.5 KB)
@prasadn1 can you confirm that you carried out troubleshooting suggestions provided on the Predictive Diagnostic Cloud pages?
Event Viewer landing page in Pega Predictive Diagnostic Cloud
Identifying top performance issues in your system with Pega Predictive Diagnostic Cloud
PEGA0011 alert: Total request time exceeds limit
Using real-time container APIs
Triggering a real-time container with the Container REST service
The error indicates an issue with PegaMKTContainer|V3 - this is not a problem with PDC but with Marketing and configuration causing pderformance issues. Have you made changes to the application stack or to “simulation/enableSampling” DSS?
Can you check PDC alerts for any Strategy emitting empty payloads where fields contain blanks for customized outcome type .
I suggest that you go through the PDC landing pages and full logs to identify the Marketing processes that are causing problems. Please log a support incident if you require further help with this. Can you provide the INC reference here so that we can help track it?
Hi Marije. Thanks for the reply. From logs i can see PEGA0020 is coming along with PEGA0011. When i checked in logs i can see one of the connect rest api is taking more time to get response. Kindly please let me know how to handle this.
@prasadn1 there are lots of posts on the forum for ‘slow response connect rest’ issues:
Improve the performance of activity-based REST services by filtering the request and response .
Have you tested the Rest Service with post man/Rest client? please enable logger for Connect-REST .
The issue could be due to various reasons:
1# Your mapping many attributes to your Request as well as Response for this connector
2# You might have a slow responding Database at the backend. Pega005 and 42 will give an idea.
Please trace it and check where the time is actually spent. Our main documentation also gives you steps to troubleshoot:
→ please go through them and try out the suggestions.
If you need further help and if no other forum users provide any further input or suggestions then you can log a support ticket via on the MSP. Please provide the INC ticket number here if you decide to go down that route so that we can help track it. You wll be asked for the troubleshooting you have carried out.