ADM Predictor bin snapshot entry into external system before it gets deleted
Hi Team,
I want to write the predictor bin entry into a log before this is deleted by the ADM agent. After every update, ADM agent gets triggered and deletes the predictor snapshot data before adding the new record.(with default ADM configuration). Do we have any ADM extension points during model or predictor updates?
To do so, I would like to know the rules which gets triggered once the ADM snapshot is captured at the backend. Can we customize this to fit our requirement?
Regards,
Nizam
Pegasystems Inc.
NL
Hi @Nizam,
There is an ADMSnapshot Agent on the Pega-DecisionEngine rule set that is triggered once a day on a schedule. This one generates the new monitoring snapshots and deletes the old predictor snapshots according to the configuration.
There are no extension points here, but what you can do if you want to read this data before it is deleted, is to create another agent on an opposing schedule. Use this one to trigger to trigger an activity with your logic. Here you can read from the pyADMPredictorSnapshots data set to browse the predictor snapshots, for example by using a data flow and writing them to a different destination.
Let me know if there are more questions.
Best, Tom
Updated: 18 Jun 2021 13:51 EDT
Tech Mahindra
IN
@TomVanDuist Thanks. I will try this idea. But why these are not replaced with Job schedulers? Any technical reason behind it?