From: Shane M. <sh...@mc...> - 2015-05-18 14:35:12
|
On 18/05/15 14:54, Ronald Schouw wrote: > Hi, > > This is not a big issue. > Can anyone tell how to create a dependency with autodiscovery ? > We get two messages in the monitoring screen > > > Disk - Free disk space 10% low on volume /backup > > and > > Disk - Free disk space 5% low on volume /backup > > It is the same filesystem, we do not want to get the messages on 10% > low, because the messages 5 % is allready there. > Anyone has a sollution ? You don't need dependency, you simply need to add more logic in your trigger prototypes. Something like this on the 10% trigger: {Template OS Linux:vfs.fs.size[{#FSNAME},pfree].last(0)}<10 and {Template OS Linux:vfs.fs.size[{#FSNAME},pfree].last(0)}>=5 And this on your 5% trigger: {Template OS Linux:vfs.fs.size[{#FSNAME},pfree].last(0)}<5 I used to have this but I found that when my filesystem was hovering around 5% I would end up with lots of alerts clearing the 10% and triggering the 5% then clearing the 5% and triggering the 10%. I tried adding hysteresis but couldn't get it to work satisfactorily. It got very annoying. Also, for users not experienced with the system it might be confusing seeing the 10% alert clear and then receive a 5% alert. So I ended up leaving the 10% triggered even if the 5% is also triggered. And don't even get me started on how useless percentage triggers are on 100TB filesystems . . . :-) Shane. |