Example of smarts-collector messages that indicate high latency

The following messages in the smarts-collector indicate that the collector is not keeping up with domain polling. If a polling action exceeds 235 seconds, it is considered late.

collecting-0-0.log:INFO  -- [2014-03-27 07:20:36 MDT] -- SmPollingData::updateNextPollingDelay(): emc-smarts : INCHARGE-PM2 (conf/smarts-pm.xml): polling completed in 235.674s, next polling will be late...
collecting-0-0.log:INFO  -- [2014-03-27 07:24:24 MDT] -- SmPollingData::updateNextPollingDelay(): emc-smarts : INCHARGE-PM1 (conf/smarts-pm.xml): polling completed in 234.032s, next polling in 5.966s...
collecting-0-0.log:INFO  -- [2014-03-27 07:24:38 MDT] -- SmPollingData::updateNextPollingDelay(): emc-smarts : INCHARGE-PM2 (conf/smarts-pm.xml): polling completed in 241.856s, next polling will be late...
collecting-0-0.log:INFO  -- [2014-03-27 07:28:25 MDT] -- SmPollingData::updateNextPollingDelay(): emc-smarts : INCHARGE-PM1 (conf/smarts-pm.xml): polling completed in 234.88s, next polling in 5.118s...
collecting-0-0.log:INFO  -- [2014-03-27 07:28:47 MDT] -- SmPollingData::updateNextPollingDelay(): emc-smarts : INCHARGE-PM2 (conf/smarts-pm.xml): polling completed in 248.549s, next polling will be late...
collecting-0-0.log:INFO  -- [2014-03-27 07:32:35 MDT] -- SmPollingData::updateNextPollingDelay(): emc-smarts : INCHARGE-PM1 (conf/smarts-pm.xml): polling completed in 244.762s, next polling will be late...