I'm at the point to where I'm connecting servers to monitor. I'm using Zabbix 2.4.x.
Apparently, at one point, SuSE/Novell defaulted to Reiser as a file type. So 'nssvol' and 'reiserfs' show up from filesystem autodiscovery. I add them in to the regex key value, and there they are, autodiscovered.
The problem occurs in that the default template tracks inodes, but reiser doesn't really have them. It has 0. So there's a trigger.
I could go through and turn off monitoring for those triggers, but instead, I tried this:
I made a new regular expression- "File systems for discoveryNOVELL" and then put reiser et al in there.
Then, to my discovery rule for filesystem, on its filters, I added an 'or' rule and for 'B' added {#FSTYPENOVELL} matches '@File systems for discoveryNOVELL'
Then, added prototypes for items that are for Free Disk Space on that: sample key is 'vfs.fs.size[{#FSNAMENOVELL},free]'
That doesn't resolve, however.
Any suggestions?
Apparently, at one point, SuSE/Novell defaulted to Reiser as a file type. So 'nssvol' and 'reiserfs' show up from filesystem autodiscovery. I add them in to the regex key value, and there they are, autodiscovered.
The problem occurs in that the default template tracks inodes, but reiser doesn't really have them. It has 0. So there's a trigger.
I could go through and turn off monitoring for those triggers, but instead, I tried this:
I made a new regular expression- "File systems for discoveryNOVELL" and then put reiser et al in there.
Then, to my discovery rule for filesystem, on its filters, I added an 'or' rule and for 'B' added {#FSTYPENOVELL} matches '@File systems for discoveryNOVELL'
Then, added prototypes for items that are for Free Disk Space on that: sample key is 'vfs.fs.size[{#FSNAMENOVELL},free]'
That doesn't resolve, however.
Any suggestions?
Comment