We are exploring option of using PDC instead of AES. As part of this migration, have few questions related to configuration and data privacy. If you are using PDC could you please help with these questions:
In which AWS region PDC cloud instances are hosted?
As part of monitoring integration/API calls, does payload is also sent to PDC?
How does PDC identifies PII in Clipboard data? Is it based on property name (Frist name, Customer name, Email ID etc.) or actual value (patterns like email IDs, 16 digit CC number etc.)?
Is retention period of data in PDC is configurable?
As PDC receives only alerts, exceptions and monitoring data, does client have to provide dump of all Pega log files to GCS to help with SR/INC resolution?
Who should use Pega Predictive Diagnostic Cloud | Pega mentions that “Application owners and product owners can measure the business value that your application delivers and prioritize investments into key areas. PDC can help them understand how end-users use the application by providing information on the levels of traffic in the application and identify which functionalities customers use the most.”. Does PDC really helps client to decide in which aspects of the application to invest to bring the most possible business value?
How to configure allow list so that PDC does not receive PII/Confidential data?
Where is your application hosted? Is it over the pega cloud or is it over your private on-premise servers or any private cloud.
If it is pega cloud your application is hosted on then by default system will be onboarded on to PDC. raise a request to my support portal to gain the required access.
If it is your private cloud and then you are trying to onboard to PDC and then data will be sent over API using SOAP. No Amazon SQS comes into picture. Amazon SQS is when your application is over Pega cloud.
PDC is multi tenant application hosted in multiple different regions. low level details work with pega my support team
When monitoring is enabled data from pega application is sent to PDC. one way communication
Pega Alerts and it’s respective causes are frequently logged into a database too apart from log file. Agent from respective table frequently reads the table and send’s it across to PDC. alerts does not hold any PII data. it only holds the details of what is the root cause for it.
Retention should be configurable at PDC if it’s dedicated to your application only. it’s a multi-tenant application not specific to one single application.
Yes when required pega log files needs to be shared. at times alerts alone may not be sufficient to identify the root cause.
@SriharshaAnika Really appreciate your quick response on this.
My application is hosted in Private Cloud (AWS) in APAC (Sydney) region.
Good to know SQS is not required for private cloud installations. Thanks for the clarification.
Sure, will check with Pega Support team. Customer Success Manager has mentioned as of now PDC is hosted in America and Europe regions and client would be able to select the region for client’s tenant. Will check this with support team if any plans on hosting PDC in APAC regions.
Need bit more clarity on this please. As as example, CreateCase API (Pega OOTB) is heavily used in my application. As part of API payload, being a bank, sensitive data like account number, customer name, customer email ID etc ate sent. When these API calls result in performance alerts or exceptions, does pay load data is also sent to PDC? What about API query parameters? In some cases we do have customer account number as a query parameter.
Thanks for the clarification.
Thanks for the clarification.
We have been told by Pega GCS that there will be no need of sharing log files if we move to PDC. After going through PDC documentation, it was evident that some times we might have to provide complete log files when alerts data is not sufficient to debug the issue. Thanks for the clarification.
For point 3. For all low level details about how the information from application is shared with PDC/AES. take a look at the agents present in PegeAESRemote ruleset. Agent’s present in this ruleset is responsible for frequently gathering the application health with respect to various dimensions and send it over to PDC over REST Interface.