Hi, > On 15 Apr 2016, at 09:18, Florian Bachmann <[email protected]> wrote: > > Hi, > > does anyone know if it is possible (at all) to use "non-legacy" timeperiod > specifications in ScheduledDowntime objects?
No, there were plans before 2.0.0 to add a different time period specification but that never happened thus far. Right now only the “legacy” time period format from Icinga 1.x / Nagios works. Kind regards, Michael > The documentation > (http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/advanced-topics#recurring-downtimes) > states that various time specification formats are supported; but none of > these work for my ScheduledDowntime objects. > > E.g. I have something like > > object ScheduledDowntime dt1 { > ... > ranges = { > "January 1st" = "00:00-04:00" > } > } > > But I get this: > > Attribute 'ranges': Invalid time specification 'January 1st': Invalid time > specification: January 1st > > The same for other specification formats like fixed dates, "Day x", etc. > > I am running Icinga2 2.4.4. > > With kind regards > Florian > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.icinga.org/mailman/listinfo/icinga-users -- Michael Friedrich, DI (FH) Senior Developer 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 | [email protected] ** OSDC 2016 - April - netways.de/osdc ** ** OSBConf 2016 - September - osbconf.org ** _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
