[dev.icinga.com #7931] Can't acknowledge multiple selected services which are in downtime

[icinga-migration]

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

Created by shakalandy on 2014-12-03 09:47:32 +00:00

Assignee: mjentsch
Status: Resolved (closed on 2015-06-01 11:40:03 +00:00)
Target Version: 2.0.0-rc1
Last Update: 2015-06-01 11:40:03 +00:00 (in Redmine)

---

We have currently two services in downtimed state.
In the new icinga web it is possible to Acknowledge them if you select a single service.
Selecting both services with "Shift + click" makes the "acknowledge" buttons disappear.
If we remove the downtime both services can be acknowledged together again.

See attached screenshots ™

Attachments

• Multuiple Downtimes.png shakalandy - 2014-12-03 09:46:43 +00:00 - multiple acknowledgements not possible if downtime is set
• multiple_ack_possible.png shakalandy - 2014-12-03 09:46:43 +00:00 - multiple acknowledgements possible when no downtime is set
• Single Downtime.png shakalandy - 2014-12-03 09:46:44 +00:00 - Single acknowledgement possible if downtime is set

Changesets

2015-06-01 10:24:29 +00:00 by mjentsch 29cc92a

Display acknowledgement action for all unacknowledged objects

Instead of displaying the ack for all unhandled problem host, make acknowledgement possible for all monitored objects in multi views.

fixes #7931

[icinga-migration]

Updated by jmeyer on 2014-12-22 14:11:38 +00:00

• Status changed from New to Rejected

Hi,

I guess the hosts of the two services shown on the "Multuiple Downtimes.png" picture were not UP at this time. Icinga Web 2 will consider a service only as unhandled in case all of the following conditions are met:

• state is not OK
• not acknowledged
• not in downtime
• the service's host's state is UP

To schedule a downtime for the shown services you should have used the "Schedule service downtimes" link further up.

Note that whether a service (or host) is being handled or not is also indicated by the first column in every list view:

• Filled out: Unhandled
• Just a narrow left border: Handled

You can see this clearly on the "multiple_ack_possible.png " picture where you've selected two rows with a filled out first column and the link to schedule a downtime for them as well. :)

Best regards,
Johannes

[icinga-migration]

Updated by tgelf on 2015-03-02 09:18:02 +00:00

• Status changed from Rejected to Feedback
• Assigned to set to elippmann

I do not fully agree here. While Johannes is technically right with his explanation, there are still use cases for the requested feature:

• Create sticky/expiring acknowledgements on OK objects - that's perfectly valid, and necessary to avoid notifications
• "Transform" a downtime in an acknowledgement without bothering people with notifications
  In case you wonder why someone might prefer to have an acknowledgement over a downtime in those use cases: downtimes have an influence on SLA, acknowledgements don't.

Cheers,
Thomas

[icinga-migration]

Updated by shakalandy on 2015-03-02 15:55:19 +00:00

Thanks @tgelf.

In addition it is still unclear to me why the handling of a single service should be handled different to multiple ones.

[icinga-migration]

Updated by elippmann on 2015-03-31 14:05:28 +00:00

• Subject changed from acknowledgement of multiple downtimed services not possible to Can't acknowledge multiple selected services which are in downtime
• Category set to Monitoring
• Status changed from Feedback to New
• Assigned to deleted elippmann
• Target Version set to 2.0.0-rc1

We'll fix this.

[icinga-migration]

Updated by mjentsch on 2015-06-01 07:34:21 +00:00

• Assigned to set to mjentsch

[icinga-migration]

Updated by mjentsch on 2015-06-01 11:40:03 +00:00

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

Applied in changeset 29cc92a.