[dev.icinga.com #3593] Implement volatile services

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/3593

Created by gbeutner on 2013-01-30 19:32:58 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2013-06-13 10:24:45 +00:00)
Target Version: Milestone 1.x Compat
Last Update: 2013-09-23 15:11:26 +00:00 (in Redmine)

---

Changesets

2013-06-13 10:24:20 +00:00 by gbeutner 4ab9d26

Implement volatile services

Fixes #3593

---

Relations:

• relates #3593
• blocks #3593
• blocks #3593

[icinga-migration]

Updated by mfriedrich on 2013-03-20 11:22:45 +00:00

tbh i don't consider this important for m2. it is an 1.x feature which is partly used (same goes for stalking), and should be discussed if and how this implementation makes sense. furthermore, it is bound to the state change logic inside the core.

and reading here - http://www.nagios-wiki.de/nagios/doku3/volatileservices - the event handlers called are not yet implemented, side by side to the finalisation of notifications.

so my proposal - reschedule for m3 and depend on notification and event handler issues.

[icinga-migration]

Updated by gbeutner on 2013-03-20 11:24:00 +00:00

JFDI.

[icinga-migration]

Updated by mfriedrich on 2013-03-20 11:26:11 +00:00

• Target Version changed from 107 to 87

[icinga-migration]

Updated by mfriedrich on 2013-03-20 11:32:41 +00:00

• Status changed from New to Assigned

[icinga-migration]

Updated by gbeutner on 2013-05-14 07:58:31 +00:00

• Target Version changed from 87 to Milestone 1.x Compat

[icinga-migration]

Updated by gbeutner on 2013-06-13 10:24:45 +00:00

• Status changed from Assigned to Resolved
• Done % changed from 0 to 100

Applied in changeset 4ab9d26.

[icinga-migration]

Updated by mfriedrich on 2013-09-23 15:11:26 +00:00

• Category set to libicinga