Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #12810] Scheduling a downtime for all services of a host does not work w/ the Icinga 2 API as command transport #2573

Closed
icinga-migration opened this issue Sep 27, 2016 · 7 comments
Labels
area/monitoring Affects the monitoring module bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

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

Created by tobiasvdk on 2016-09-27 14:36:45 +00:00

Assignee: elippmann
Status: Resolved (closed on 2016-12-08 09:45:17 +00:00)
Target Version: 2.4.0
Last Update: 2016-12-08 09:45:17 +00:00 (in Redmine)


I want to schedule a downtime of a host with all its services. Following the linkt "Schedule Downtime" on the host pane and checking "All Services" only schedules a downtime for the host itself.

I'm using git commit 7ed3acb of icingaweb2 with icinga 2 api as command transport for the monitoring module.

Attachments

Changesets

2016-12-08 09:40:22 +00:00 by elippmann 4f6c54e

Support scheduling a downtime for all services of a host w/ the Icinga 2 API as command transport

fixes #12810
@icinga-migration
Copy link
Author

Updated by tobiasvdk on 2016-09-30 14:35:07 +00:00

  • File added 0001-Fix-scheduling-a-downtime-for-all-services-of-a-host.patch

Looks like the function $hostDowntime->setForAllServices(); currently does not work.

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-10-04 09:13:48 +00:00

  • Subject changed from Scheduling a downtime for a host with all its services schedules only the host downtime to Scheduling a downtime for all services of a host does not work w/ the Icinga 2 API as command transport
  • Target Version set to 2.4.0

@icinga-migration
Copy link
Author

Updated by aklimov on 2016-10-12 12:07:36 +00:00

  • Status changed from New to Assigned
  • Assigned to set to aklimov

@icinga-migration
Copy link
Author

Updated by aklimov on 2016-10-12 16:01:29 +00:00

  • Status changed from Assigned to Feedback
  • Assigned to changed from aklimov to jmeyer

As you assumed there may be a better (than the patch) way to do it, but:

  • with the local cmd file we'd do SCHEDULE_HOST_SVC_DOWNTIME which "Schedules downtime for all services associated with a particular host." (see https://old.nagios.org/developerinfo/externalcommands/commandinfo.php?command\_id=122 and http://docs.icinga.org/latest/de/extcommands2.html)
  • this says nothing about the host itself, but when we do this, I2 schedules downtimes for all services + the host itself (understandable, but also not as the doc doesn't mention this)
  • my fix "Schedules downtime for all services associated with a particular host" as well (via API), but not for the host itself (is this acceptable? if not, is this an I2 bug?)
  • unfortunately scheduling downtimes for multiple types of objects at once seems not to work (via API) (see I2 doc and #12903)

@icinga-migration
Copy link
Author

Updated by aklimov on 2016-10-13 08:07:35 +00:00

  • Status changed from Feedback to Assigned
  • Assigned to changed from jmeyer to aklimov

@icinga-migration
Copy link
Author

Updated by aklimov on 2016-10-13 16:42:32 +00:00

  • Status changed from Assigned to Feedback
  • Assigned to changed from aklimov to elippmann

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-12-08 09:45:17 +00:00

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

Applied in changeset 4f6c54e.

@icinga-migration icinga-migration added bug Something isn't working area/monitoring Affects the monitoring module labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.4.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/monitoring Affects the monitoring module bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant