Cisco IP SLA polling should be aware of and adjust behavior based upon the implementation of the Cisco IP SLA History options that are available.
If I configure my Cisco device to retain IP SLA test results for some history that extends beyond the default SNMP polling interval of NPM, then NPM should collect those IP SLA test results on it's regular SNMP polling run.
This could greatly reduce the stress on the VNQM polling in circumstances where a network operator may desire the insights that might be gained from higher frequency polling(at say 60 second frequencies) but doesn't want to generate 6 new polling events occurring every 30 seconds just to get 4 ICMP, 1 DHCP, and 1 HTTP get test results.
The suggestion to place this in feature requests came from support staffer bob55 in response to this thread;
