Hi Peter,
sure, I could imagine something like this:
object TimePeriod "24x7" {
import "legacy-timeperiod"
timezone = "PDT"
ranges = { .. }
}
Could you please open a related feature request?
Thomas.
Am 15.06.2018 um 10:29 schrieb Peter Eckel:
Hi Thomas,
Time periods in Icinga 2 have initially been designed to allow for
alternative implementations. There have been related experiments, but as
far as I know no other implementation has ever been published.
funny, just this week I asked myself the same question ... thanks for
clarifying.
A related question, or maybe an idea for an upcoming alternative
implementation: Is there any way to define time periods in a different time
zone than the one used for the server?
While it may sound a bit weird at first, the reason for this is quite simple: All servers
in my customers' data centers are running on UTC for various reasons. Unfortunately their
support organisations don't, and so it would make sense to define time periods in local
time to avoid, for instance, a time period called "business-hours" to shift by
an hour two times per year when summer time gets switched on or off.
--
Thomas Gelf
Principal Consultant
NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | thomas.g...@netways.de
** OSDC 2018 - June - osdc.de **
** Icinga as a Service - nws.netways.de **
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
