You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Updated by jmosshammer on 2011-05-02 16:21:47 +00:00
Status changed from New to Resolved
Fixed in current master, although this is not really a bug.
When you choose a non fixed downtime, duration defines how long this downtime goes and start/end just defines where it might start (afaik). Anyway, duration is now hidden when choosing the 'fixed' field
Updated by mfriedrich on 2011-05-02 16:24:08 +00:00
Done % changed from 0 to 100
true that. a flexible downtime starts within start and end time and lasts $duration, but only if soft or hard state change triggered - check bug #1228 for more infos.
Of course, that's how it works. And an expert Nagios user immediately understands what effect this forms fields will have once used for either a fixed or a flexible downtime. But there are also a very few poor mere mortals not grown up with Nagios to be found out there ;-) If the form itself isn't able to explain what is going to happen, a direct link to the related documentation would be great! Icinga-Classic offers such indications while hovering interrogation marks.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1280
Created by tgelf on 2011-03-09 10:14:25 +00:00
Assignee: (none)
Status: Resolved (closed on 2011-05-02 16:21:47 +00:00)
Target Version: 1.4
Last Update: 2011-05-02 20:45:56 +00:00 (in Redmine)
It's pretty unclear whether the downtime going to be configured in the attached screenshot will last either one or two hours...
Attachments
Changesets
2011-05-02 16:05:02 +00:00 by jmosshammer 76c2375
The text was updated successfully, but these errors were encountered: