[dev.icinga.com #2539] add is_in_effect and trigger_time to scheduleddowntime and downtimehistory tables #947
Comments
Updated by mfriedrich on 2012-04-22 23:25:06 +00:00 implementing that feature requires that the neb callback happens after the detection of the downtime being entered (trigger_time) as well as setting it to is_in_effect as well. this could possibly interfere with existing event brokers, but none is allowed to override the downtime being set as this is an internal functionality. change must be noted though. |
Updated by mfriedrich on 2012-04-23 00:04:33 +00:00 tested with postgresql fow now. before
triggered
|
Updated by mfriedrich on 2012-04-23 00:05:13 +00:00
requires further rdbms tests, more tomorrow. |
Updated by mfriedrich on 2012-04-23 00:09:09 +00:00 well, first 2 rows did not work, 3 does on the downtimehistory.
|
Updated by mfriedrich on 2012-04-23 00:09:52 +00:00 diversification on "is_in_effect" is needed, depending on the callback sending data. |
Updated by mfriedrich on 2012-04-27 17:13:55 +00:00
for me it looks good. |
Updated by mfriedrich on 2014-12-08 14:37:41 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2539
Created by mfriedrich on 2012-04-22 22:58:37 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2012-04-27 17:13:55 +00:00)
Target Version: 1.7
Last Update: 2014-12-08 14:37:41 +00:00 (in Redmine)
requires #2537 to be implemented.
Changesets
2012-04-23 00:06:38 +00:00 by mfriedrich b7a29ac
Relations:
The text was updated successfully, but these errors were encountered: