Page 1 of 1

Availability reports in diferent timezones

Posted: Thu Apr 19, 2012 8:42 am
by henqix
Hi,

We monitor a large number of targets all over the world in different timezones and I would like to know if someone has an idea of reporting availability per timezone without creating multiple Nagios instances.

Many thanks in advance.

Cheers,

Henk

Re: Availability reports in diferent timezones

Posted: Thu Apr 19, 2012 6:57 pm
by jsmurphy
What you could do is create a logical hostgroup with no function other than to contain all the devices in a timezone and then run an availability report for that hostgroup.

Re: Availability reports in diferent timezones

Posted: Mon Apr 23, 2012 5:44 am
by henqix
Thanks for your answer and I have thought about this for a start. But how can I choose the correct timezone for that hostgroup because I can select "workhours" in the Availability Report but not what work hours and for which timezone.

Re: Availability reports in diferent timezones

Posted: Mon Apr 23, 2012 5:47 am
by henqix
jsmurphy wrote:What you could do is create a logical hostgroup with no function other than to contain all the devices in a timezone and then run an availability report for that hostgroup.
Thank for you answer and I thought of this for a start. I can choose "workhours" from the Availability Report but what work hours are that and for which timezone?

Re: Availability reports in diferent timezones

Posted: Mon Apr 23, 2012 10:00 am
by agriffin
"workhours" is a timeperiod defined somewhere else in your configuration. It's probably 9-5 M-F for whatever timezone your server is in.

Re: Availability reports in diferent timezones

Posted: Mon Apr 23, 2012 6:53 pm
by jsmurphy
agriffin wrote:"workhours" is a timeperiod defined somewhere else in your configuration. It's probably 9-5 M-F for whatever timezone your server is in.
What Alex said, you still define the time periods on the host.

The easiest way to do all of this would probably be to create a template that assigned the host the timeperiod and the logical hostgroup for that particular timeperiod. Each host would then have base template -> time template -> host. Really you just have to find a way to structure it that's not going to blow out your administrative overhead.