Ad Widget

Collapse

Disk Space Monitoring for multiple partitions

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • skibumatbu
    Junior Member
    • Oct 2014
    • 5

    #1

    Disk Space Monitoring for multiple partitions

    We're using Linux. We as a company have defined certain mount points system related sending alerts to the IT team. All other mount points go to the application owners.

    The system disks are: / /boot /var/log /tmp. Not every host has every disk. Every host has / and /boot, that's easy. But /var/log and /tmp may be on some hosts.
    The application disks are everything else.

    I want to create two templates. One for system disks and one for application disks (and the rest of the application monitoring). I can then have alerts based on the templates fire to the correct team.

    How do I define the application disks without having to specify each one? Can I say "all partitions except / /boot, etc"?

    Is there a way to define the system disks as one item in a template and one trigger? Or do I need to enumerate all of them? What if a host doesn't have those disks?

    If I can keep this to just the two templates, then I can add every host to both templates and it can do the right thing. If I need to have separate templates because I have to enumerate different lists of partitions, then it becomes very manual and I can't use Zabbix.
  • skibumatbu
    Junior Member
    • Oct 2014
    • 5

    #2
    Disk Space Monitoring for multiple partitions

    I'm still playing with this...

    I figured out how to group things. I can create a system template and a application template. Since the application partitions are unique to applications thats fine for them. I can create triggers per application.... again totally fine. Alerting based on the template... again... fine.

    But here is the issue... I have two types of hosts at a system level. Some have the / and the /boot partitions. The second type has those as well as /tmp and /var/log. If I add /tmp and /var/log items to all my hosts then the hosts that do not have those partitions will report back the disk space of the / partition (since that is the underlying partition. Then I build triggers around each partitions and an alert on the template. If the / partition fills up I'll get three alerts. This is leading me to create separate templates for the different types of hosts. I really don't want separate templates. The fewer moving bits the better.

    Any suggestions?

    Comment

    Working...