You might be missing the Availability Filter in your collector manager config. This is particularly true if you are using SolutionPacks in a distributed environment, we have seen that in some versions this filter doesn't get deployed properly.
Below is an example for the Smarts collector, where the Availability filter has been put immediately next in line after the collector in collecting.xml (read from bottom up).
Note that if you are using the Smarts collector, you need to change the availability filter config file to match your polling cycle (default 240secs, not the usual 300secs for other collectors).
BenimusIQ
12 Posts
0
October 8th, 2013 18:00
Hi Denis,
You might be missing the Availability Filter in your collector manager config. This is particularly true if you are using SolutionPacks in a distributed environment, we have seen that in some versions this filter doesn't get deployed properly.
Below is an example for the Smarts collector, where the Availability filter has been put immediately next in line after the collector in collecting.xml (read from bottom up).
Note that if you are using the Smarts collector, you need to change the availability filter config file to match your polling cycle (default 240secs, not the usual 300secs for other collectors).
Benjamin Johns
iQ Consult Pty Ltd
Australia
T0mahawk_af3a63
2 Posts
0
October 8th, 2013 22:00
Hi Ben,
Thanks for the tip. I'll try to check this out later today and let you know if you were close.
Thanks,
Denis