If PA collection property com.snc.pa.dc.max_records is exceeded, is a subset of size max_records snapshotted?

[Pierre P_ Mouri]

In the context of data collection in Performance Analytics, specifically the com.snc.pa.dc.max_records PA property, I am unsure what the behavior is when the limit is reached:

- The warning message (when going over the limit) implies if the limit is breached a subset of sys_ids is stored.

"Not saving all records for indicator XYZ. Result has 9,234 records. Only allowed subset of 5,000 records are stored."

- The documentation (NY in my use-case, but still valid in QC) states if the limit is breached a subset is not stored.

"Maximum number of sys IDs that are stored on a single Snapshot [pa_snapshots] record. A Snapshot record is created for each collected score, and a field in this record contains all the sys IDs from the indicator that contribute to the score. If this limit is exceeded, a Snapshot record is not created for this score." 

- On an instance spot check, I see subsets of exactly 5,000 records for several consecutive days, leading me to believe a subset is indeed stored.

So, if there are 5,001 sys_ids for a given combination, is a subset of 5,000 stored? and, if so, how is this subset determined? 

[DJL2]

Hi Pierre,

I get this Warning on a number of my Collection Jobs - usually the ones which orchestrate collection of data against some of the chunkier tables, such as Metrics, Task SLA etc.  I set the limit on our instance to 25,000 records and some of our Indicators blow that out of the water and in this scenario, a set limit of 25,000 records will be cached.

I would imagine the subset is determined by the order (date, index etc) in which the query recursively executes, until such time as it hits the threshold parameter.  Admittedly anecdotal, our records appear to be trimmed based on date, therefore the query appears chronological.

If it's an option, I'd consider expanding that parameter 🙂

Thanks,

DJL