Exchange DB trigger

[Magician]

Hi , i have exchange 2010 dag (cloud environment) i want the zabbix to report when one of the DBS are down i have 25 dbs i need to monitor that i get alert when DB is dismounted .

i have exchange template - but it doesnt seem like it autodiscovers the DB

any recommendation how to processed ?

[steveboyson]

1) define the "normal" state
2) define the "alert" state
3) what has changed?
4) create a script which checks that difference
5) Hook in that script into a "UserParameter" key in your zabbix_agentd config file
6) restart zabbix_agentd
7) create an item on the host to be monitored which calls that script
8) create a trigger for that item
9) DONE.

[Magician]

ok did it , here is what i did (maybe will help others)

i've created a script(a ps1 script) that updaing a log file everytime it runs .
if there is a problem , its writing the databases that are down in that file , and by that it makes the log file more than 0 bytes .
if no problem it erase everything on the log file and the log becomes 0

now , ive created additional script vbscript that query the log folder for size .

than created an item and trigger than if anything is bigger than 0 it will active the trigger .

the db script will run now with task schedualer and in the future ill transform it into zabbix agent probably .

this is the phase 1 of masterplan

next phases of the plan i intend to create folders to each db and create triggers for each db if error or not (dont know how to create a discovery so ill do it manual)

afterwards ill do something similar with querying the mpoints of each db for free % on that volume .

anyway thanks for the help .

[steveboyson]

You could write a script which autodiscovers your databases (giving you for example the name).
Then create item prototypes for each discovered databases which check for status or health, size etc.

[Magician]

yes but it take time now i need to get an sms when db is down (doesnt matter which db is down) to fix it in no time

nevermind fixed it , had problem in the script as currentlocation was in system32 and not in the directory the other script was