Schedule Downtime and SLA Timeframes

[navtek007]

Hi All,

I know that this question has been asked quite a few times but i am yet to see a answer.

I would like to know if scheduled downtime will be introduced and also if SLA calcualtions will be done on specified timeframes

eg: Web Services 6:30am to 6:30pm.

I can get around the scheduled downtime with scripts to change the monitored state, however I can't seem to find a way to incorporate timeframes with the SLA side of things. If anyone has any ideas then that would be great. Overall the software is great, looking forward to the next release.

Thanks in advanced.

[rdg]

Check out http://sourceforge.net/docman/displa...&group_id=4141 to see how OpenNMS handles this.

/Robert

[navtek007]

Ok so any suggestions on how it can be encorporated with Zabbix?

[navtek007]

any other suggestions? Alex will this be a feature available in 1.1 or in the future?

thanks.

[Alexei]

I'd like to see it in 1.1.

[crs9]

Alexei,

Is this feature still in the works for 1.1? I'd like to use it to track SLA numbers JUST during business hours, and I think this would work.

Thanks

[mary nancy]

Hi all,

I would like to know how to schedule a maintenance windows. For eg: If I have a maintenance activity scheduled between 5.00am to 5.30pm on a particular host. there should be no alerts generated by that host in that time interval....

Can somebody guide me on this?

Thanks
Nancy

[devros]

this would also be a big one for me. I am currently looking at SLA reporting solutions, and it seems that Zabbix is almost there. Scheduled Downtime and more configuration of reporting would make it perfect for what I need.

-ed

[Alexei]

The feature (scheduled downtimes) is already implemented and will be part of ZABBIX 1.4. It won't be introduced in stable 1.1.x.

[lreadshaw]

navtek007,
As a newbie to zabbix, I could use some help with implementing a scheduled downtime workaround for now. Could you give me some insight into how you used scripts to put a scheduled maintenance window in place?

Thanks,
Lawrence

[navtek007]

basically i have done the following

1. Create maintenance start sql script which basically disables all triggers for all hosts that are enabled

update triggers ,functions, items, hosts set triggers.status = 1
where triggers.triggerid = functions.triggerid
and items.itemid = functions.itemid
and hosts.hostid = items.hostid
and hosts.host like '%'
and hosts.status=0;

2. Create a maintenance stop sql script which turns all triggers back on for all hosts that are enabled.

update triggers, functions, items, hosts set triggers.status = 0
where triggers.triggerid = functions.triggerid
and items.itemid = functions.itemid
and hosts.hostid = items.hostid
and hosts.host like '%'
and hosts.status=0;

3. Create a cronjob to run these scripts at your scheduled outage/maintenance window or operation hours.

eg:

00 05 * * 1-6 /home/zabbix/maint_complete.sh # Turn all triggers on at 5:00am Mon-Sat
30 18 * * 1-5 /home/zabbix/maint_start.sh # Turn all triggers off at 6:30pm Mon-Fri

There are a couple of holes in my solution as you are unaware of what triggers are executed during the night as they are not turned on. to get around this i basically turn triggers on 1.5 hours before the start of our operation hours just to give me a heads up before i get bombed with calls.

For me it is handy to get a acurate availability time for our business and it saves me from doing a whole bunch of calculation on the availability report. It also makes Zabbix SLA calculation correct for our infrastructure sla's.

hope this helps.

[Alexei]

Note that SLA downtimes are already implemented in beta code of 1.4 (1.3.x).