Returns all in-memory performance data staging tables with an unusually high number of rows. Default=500,000, but this may need to be adjusted per environment.
When the number of rows is over the threshold, it means that the MovePABufferData procedure is not keeping up with the volume of incoming performance data, and thus is not moving data from the in-memory tables into the CCI tables quickly enough. This can be caused by:
1) High latency network links between the S1 Monitoring Service(s) and the S1 database which is causing the performance data for some targets to be written too slowly. The Move process will wait up to 60 seconds by default for committing each new timestamp, and continual lag may lead to an accumulation of staging data. Contact S1 Support for assistance troubleshooting slow links.
2) The Move process is not running -- the associated thread may have experienced and error and not restarted successfully. Restart the primary S1 Monitoring Service to reset it -- this is the one with with the oldest "Last Initialized" time under All Targets->Show Monitoring Services List.
3) Transient maintenance activities like index rebuilds, backups, etc., which can cause resource contention and/or blocking leading to temporary queueing of the staging data. The max value can be adjusted to account for these spikes, or a Response Ruleset can be used to wait for n minutes before alerting.