ZABBIX FEATURE REQUESTS

Filesystem monitoring

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.9.1 (alpha)
  • Component/s: Agent (G)
  • Labels:
    None

Description

Is there a way to dynamically monitor filesystems on a server? How do you do that?

For the moment, when I had a new host, I run a script on it to check local FS and generate XML code ready to import into zabbix. However, if a new FS is created, it is not automaticaly added into zabbix (and I do not want to add a cronjob on each host to do that).

I tried to create un new parameter to send FS list to zabbix server, but I did not find a way to create a trigger who can treat these information. For example, it seems possible to change trigger state if a FS reach 95% but not to tell which one...

What is the best way to maintain node FS monitoring up to date without a manuel action? New FS are created everyday on serveral client, it is a real pain to add them manually into GUI...

Thank you in advance.

Activity

Hide
Alexei Vladishev added a comment -

Perhaps a couple of user parameters may do the trick:

1. The first item would scan all file systems and return percentage of used disk space of the most filled file system
2. The second item would return name of the most filled file system or several file systems

Then, a trigger may be defined to show name of the filesystem:

Trigger name: "Low free disk space on {ITEM.LASTVALUE}"
Trigger expression: {host:fs_name.last(0)}<0 | {host:fs_used.last(0)}<10

fs_name.last(0) will never be evaluated as true, so fs_used.last(0)<10 will actually be checked.
{ITEM.LASTVALUE} is a macro, which will be available starting from 1.4.3.

I hope this is close to what you want.

Alexei

Show
Alexei Vladishev added a comment - Perhaps a couple of user parameters may do the trick: 1. The first item would scan all file systems and return percentage of used disk space of the most filled file system 2. The second item would return name of the most filled file system or several file systems Then, a trigger may be defined to show name of the filesystem: Trigger name: "Low free disk space on {ITEM.LASTVALUE}" Trigger expression: {host:fs_name.last(0)}<0 | {host:fs_used.last(0)}<10 fs_name.last(0) will never be evaluated as true, so fs_used.last(0)<10 will actually be checked. {ITEM.LASTVALUE} is a macro, which will be available starting from 1.4.3. I hope this is close to what you want. Alexei
Hide
Andreas Faust added a comment - - edited

we do the same here using UserParameter, which we have an update-mechanism for.

UserParameter=drive.full, df -Ph|awk '{ print $6" is "$5" full"}'|sort -n -k4|egrep "8[5-9]%|9[0-9]%"||echo " "

the sort makes sure the most filled shows up on overview page.

works for linux/unix agents only (except there are similar tools for windows)

Show
Andreas Faust added a comment - - edited we do the same here using UserParameter, which we have an update-mechanism for. UserParameter=drive.full, df -Ph|awk '{ print $6" is "$5" full"}'|sort -n -k4|egrep "8[5-9]%|9[0-9]%"||echo " " the sort makes sure the most filled shows up on overview page. works for linux/unix agents only (except there are similar tools for windows)
Hide
Johan Segernas added a comment -

The solutions with user parameter isn't good enough. I would like to have a system that runs a discovery of the system on a regular basis and make Zabbix monitor/graph the volumes mounted.

Today we have added most of the 'known' mount points in our template but this isn't good enough either. We have a few hundred different systems which doesn't look alike at all.

Some dynamic discovery wanted!

Show
Johan Segernas added a comment - The solutions with user parameter isn't good enough. I would like to have a system that runs a discovery of the system on a regular basis and make Zabbix monitor/graph the volumes mounted. Today we have added most of the 'known' mount points in our template but this isn't good enough either. We have a few hundred different systems which doesn't look alike at all. Some dynamic discovery wanted!
Hide
richlv added a comment -
Show
richlv added a comment - implemented in trunk : http://www.zabbix.com/documentation/2.0/manual/discovery/low_level_discovery

People

  • Assignee:
    Unassigned
    Reporter:
    Steria
Vote (14)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: