TECHZEN Zenoss User Community ARCHIVE  

Raised filesystem threshold; still get Events at old threshold

Subject: Raised filesystem threshold; still get Events at old threshold
Author: [Not Specified]
Posted: 2015-08-20 07:40

Hi folks,

Have an occasional weird problem with our Filesystem template. Ages ago I raised the threshold from 90 to 95%:

here.getTotalBlocks() * .95

I also changed the description of the usedBlocks data source to read

"Filesystem template that uses HOST-RESOURCES mib. Has a 95% threshold."

But occasionally I get Events that are between 90 and 95%. Often this happens when I have to restart a collector for some reason. I also notice that if you check the Templates under a Filesystem component the description still reads "Has a 90% threshold".

It looks like there's something I'm missing here to propogate a Filesystem component template change.

Platform: Zenoss Core 4.2.5 + zenups

Any thoughts

Dave

p.s. more info:

Template info from API TemplateRouter getInfo

'uid' => '/zport/dmd/Devices/Server/rrdTemplates/FileSystem',
'name' => 'FileSystem',
'description' => 'Filesystem template that uses HOST-RESOURCES mib. Has a 90% threshold.',
'definition' => '/Devices/Server',

(If i go to Filesystem Devices Server in the Monitoring Templates GUI, I see it says "95% threshold")

Threshold info from TemplateRouter getThresholds

'maxval' => 'here.getTotalBlocks() * .95',
'dataPoints' => 'usedBlocks_usedBlocks',
'uid' => '/zport/dmd/Devices/Server/rrdTemplates/FileSystem/thresholds/high disk usage',



Subject: did you remodel?
Author: Andrew Kirch
Posted: 2015-08-24 14:03

did you remodel

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard



Subject: Yes, the servers have all
Author: [Not Specified]
Posted: 2015-08-24 14:07

Yes, the servers have all been remodeled by the daily process. The template in question was changed probably a year ago but occasionally we still get a flurry of these 90%s. It tends to happen when a collector gets rebooted as if there's a built in 90% threshold in the code used before everything is back up and running.



< Previous
severity to text transform issue
  Next
Same host by different (c)names
>