Linux File system monitoring using zabbix agent

[dharam]

Hi,
I am new to zabbix and looking to monitor Linux File System.
Anyone using File system monitoring for Linux host and can provide me high level steps to begin with. I have given task to explore this option.
Currently we have script based from tool called HP ovo and we need to replace it with zabbix

[tim.mooney]

Spend some time reading the documentation. Zabbix uses "items" to collect data about a system, and "triggers" to make decisions on whether that data means there is a problem.

Zabbix comes with many pre-defined templates, which are just collections of items, triggers, etc. You can create your own templates or you can use the pre-defined templates, or you can mix your templates with pre-defined.

The pre-defined templates are quite thorough and may require some configuration from you before you apply them to your systems. Understanding how you use macros to tailor how the pre-defined templates work will be very important to avoid an unpleasant experience with over-monitoring / spurious alerts. These forums get regular posts from people that just blindly applied the pre-defined templates to a whole bunch of systems and now they want to change things because they're monitoring things (and getting alerted by things) they don't care about.

Spend a bunch of time in Chapter 7 (Configuration) of the Zabbix web documentation, and it will benefit you throughout your deployment

[dharam]

GM,
I am able to discover filesystem but now how we can dynamically assign triggered/incident to support team as different filesystem own by different support team?

[dharam]

How other people are managing this? As this is very common practice that different filesystems are owned by different team?

[cyber]

GM,
I am able to discover filesystem but now how we can dynamically assign triggered/incident to support team as different filesystem own by different support team?

Tagging. For example, we add "support team" tag to each trigger. When event is forwarded out to 3rd party it has proper attributes set and integration to ticketing uses those to fill correct fields. Also helps to have inventory for hosts filled, so you can use data from inventory ie. "Support team" => "{INVENTORY.PRIMARY.POC.NAME}". Having CMDB and syncing data from there, helps...