Dear list,
I am struggling with Icinga2 downtimes. Maybe it is just me, but I
stumbled over some very strange things and thought I'd like to share
them with you. Maybe you could point me to the right direction..
(a) Downtimes over midnight
When I schedule a downtime over midnight (e.g. 22:00-05:00), it doesn't
work (known thing).
A known workaround I found online is to provide two time ranges, e.g:
monday = "22:00-24:00,00:00-05:00"
However, Icingaweb2 shows only (I translate the German UI):
Schuled start: 22:00
Scheduled end: 00:00
So, no 05:00 on Tuesday :( The icinga2 database also shows the wrong end
time:
scheduled_start_time: 2017-02-13 22:00:00
scheduled_end_time: 2017-02-14 00:00:00
I also know that one could provide a valid range for a day-change
downtime by adding hours to midnight, e.g.:
"22:00-29:00"
This finally works, Icingaweb2 shows the correct ending on Tuesday 05:00
in the morning.
Is this known, do you guys have other workarounds? Do you know if this
will be changed someday?
IMHO providing two time ranges (22:00-24:00,00:00-05:00) would be more
intuitive.
(b)
I provided a downtime with the following configuration:
apply ScheduledDowntime "2818_test_downtime" to Host {
author = "admin"
comment = "test downtime"
ranges = {
tuesday = "22:00-29:00"
}
assign where host.vars.os == "Linux"
}
When I update the downtime and append _2 to the downtime name and
comment and also change the time range, some strange stuff begins to happen:
1. Icingaweb2 shows the updated time range, but still the same name and
comment.
2. For a minute or so, Icingaweb2 showed the old and new version of the
downtime (new version still with old name and comment).
I played around a bit, and the old downtime versions still appear in the
history of an affected host, although the downtime didn't even start yet.
Looking at the database of Icinga2, I can see that my downtime entries
are there, still with wrong comments and names.
This looks like a huge inconsistency. Could it be that this is mainly a
viewing issue within Icingaweb2?
Why doesn't Icingaweb2 take over the new name and comment values? How
comes that the history of an affected host shows old downtime version
entries?
Best regards
Valentin
--
Valentin Höbel
Senior Consultant IT Infrastructure
mobil 0711-30585357
Linux Information Systems
LIS Stuttgart GmbH
Talstraße 41 70188 Stuttgart Germany
Geschäftsführer Tilo Mey
Amtsgericht Stuttgart, HRB 729287, Ust-IdNr DE264295269
Volksbank Stuttgart EG, BIC VOBADESS, IBAN DE75600901000340001003
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
