I wanted to know what kind of alerts are being generated by adaptive decision manager services?i.e. does the data analysis which is done by the ADM services generate any alert ? What are those and when are they generated.
Thanks in advance,
***Edited by Moderator Marissa to update platform capability tags****
Thanks for responding. One question that I have is where does the data analysis take place? I mean does this data analysis and refreshing of models have any adverse effect on the database and on Pega interaction ? Can this lead to any PEGA0005 alerts (i.e. while querying Interaction History for fetching customer interactions) ?
I am of the idea that the ADM services are running on dedicated ADM server and should not have any adverse effect otherwise. Is that understanding correct?
Yes or no. Yes, ADM should be run on its own nodes (especially in production env) but the IH is all stored in the same table. A properly sized/tuned env should not have PEGA0005 alerts but it can happen for an environment, especially IH table is getting big. You should perform archiving on those IH tables to avoid potential performance issue.
Yeah Exactly. That's what I wanted to confirm that ADM data analysis efforts alone should not cause any PEGA0005 on IH tables or overhead on IH tables as it should happen asynchronously/remotely and not during decisioning. Right?
The updating (learning/training) of adaptive models is decoupled from the scoring of the models and therefore doesn't have an adverse effect (as mentioned above, in a production environment there would be dedicated ADM worker nodes for updating the models).
When updating a model, the Interaction History database doesn't play any role.
Of course there may be valuable predictive information in the Interaction History. Usage of IH data as predictors is optional. When any strategy is executed that retrieves IH info (for ADM or other purposes) this can result in a database query on IH and as such be part of the strategy execution performance.
In 7.4, an alternative way to retrieve IH data in strategies was introduced that doesn't make use of a query, for better performance. IH summaries eagerly aggregate data from IH (when they are 'materialized').