Hi All,
I have low level discovery of file systems working very well in our environment. We have an in house developed storage appliance which basically allocates disk space to LV's on an as needed basis and automatically grows the file systems. This is causing issues for the triggers created as part of the discovery process because these file systems will typically sit at 99% used for their entire life.
I would like to achieve a test in the trigger prototype to discount these file systems based on the path of the mount point, I still need to monitor them, but just not be alerted about lack of free space. e.g. we have the usual /, /opt, /var, ... etc and our manged file systems are mounted (as an example) as /data/fs1, /data/fs2, ... etc.
My initial thoughts were to include a regexp test to the trigger so that it always resulted false should the path begin with /data/ as this is guaranteed to always be the case. While this could work I cannot see how I can do this in Zabbix.
I also thought about creating a file system discovery script which could be used to get those which are not the /data file systems and those that are but this would not be my first preference if it can be done natively.
I am sure the answer is simple, but I don't seem to be able to see it. Any pointers or suggestions would be greatly appreciated.
Cheers,
Brian.
I have low level discovery of file systems working very well in our environment. We have an in house developed storage appliance which basically allocates disk space to LV's on an as needed basis and automatically grows the file systems. This is causing issues for the triggers created as part of the discovery process because these file systems will typically sit at 99% used for their entire life.
I would like to achieve a test in the trigger prototype to discount these file systems based on the path of the mount point, I still need to monitor them, but just not be alerted about lack of free space. e.g. we have the usual /, /opt, /var, ... etc and our manged file systems are mounted (as an example) as /data/fs1, /data/fs2, ... etc.
My initial thoughts were to include a regexp test to the trigger so that it always resulted false should the path begin with /data/ as this is guaranteed to always be the case. While this could work I cannot see how I can do this in Zabbix.
I also thought about creating a file system discovery script which could be used to get those which are not the /data file systems and those that are but this would not be my first preference if it can be done natively.
I am sure the answer is simple, but I don't seem to be able to see it. Any pointers or suggestions would be greatly appreciated.
Cheers,
Brian.
Comment