Skip to content
This repository has been archived by the owner. It is now read-only.

[dev.icinga.com #421] Add extra status for Services/Hosts/... during planned downtime. #205

Closed
icinga-migration opened this issue May 11, 2010 · 16 comments

Comments

Projects
None yet
1 participant
@icinga-migration
Copy link
Member

commented May 11, 2010

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

Created by bd on 2010-05-11 11:31:08 +00:00

Assignee: (none)
Status: Resolved (closed on 2011-08-02 18:32:39 +00:00)
Target Version: 1.5
Last Update: 2014-12-08 09:34:04 +00:00 (in Redmine)


During a planned downtime services/hosts/... should be shown in a different color independent of their status.

This will declutter the overview pages, as important red/yellow states are no longer hidden between the downtime red states.

It will also document that this service was down in an organized manner and not due to a real outage.

Also planned downtimes should not count against the services/etc availability, or there should be two availablities, one counting downtimes as down, the other as up. This can be used to caluclate SLA compliance, as planned downtimes normaly do not count as down.


Relations:

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 14, 2010

Updated by mfriedrich on 2010-06-14 07:39:49 +00:00

sth like that probably

http://wleibzon.bol.ucla.edu/nagios/nagios28-support\_disabledstatus.patch

http://william.leibzon.org/nagios/

This is nagios patch that adds "Disabled" status for detail/overview/summary CGI view which is for all services/hosts that have active checks disabled, such services no longer count under "all problems" with this patch. There are no nagios configuration options added by this patch.
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 9, 2010

Updated by mfriedrich on 2010-07-09 14:51:28 +00:00

  • Category changed from Other to Status Data
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 9, 2010

Updated by mfriedrich on 2010-11-09 16:20:48 +00:00

  • Status changed from New to Feedback
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 9, 2010

Updated by bd on 2010-11-09 16:26:54 +00:00

I am not sure what type of Feedback you need. Could you please elaborate?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 10, 2010

Updated by mfriedrich on 2010-11-10 11:06:37 +00:00

i want feedback from other developers, if this is good/bad/etc idea, if it's possible to implement, etc etc since this has been floating around for 4 months without comments (imho too long).

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Mar 18, 2011

Updated by mfriedrich on 2011-03-18 17:38:50 +00:00

  • Target Version set to 1.5
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 23, 2011

Updated by mfriedrich on 2011-05-23 16:20:59 +00:00

i would consider this a gui change, rather than injecting the core itsself. so moving to classic ui section.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 23, 2011

Updated by mfriedrich on 2011-05-23 16:21:07 +00:00

  • Project changed from Core, Classic UI, IDOUtils to 19
  • Category deleted Status Data
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 26, 2011

Updated by mjbrooks on 2011-06-26 00:06:18 +00:00

  • Done % changed from 0 to 50

See #992 for the visual portion.

I think there is some separate work or plans going on for SLAs which might cover the other part of this.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 16, 2011

Updated by mfriedrich on 2011-07-16 16:04:06 +00:00

is this ready for production yet?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2011

Updated by mjbrooks on 2011-07-17 00:49:52 +00:00

Are you asking about the SLA part?

I only addressed the coloring as part of #992

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2011

Updated by mfriedrich on 2011-07-17 09:53:03 +00:00

i'm only interested in the gui changes, not the core parts. for the reporting stuff, pls ask ricardo/rune/michaelL about it.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2011

Updated by mjbrooks on 2011-07-17 10:05:09 +00:00

The coloring is done per #992

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 28, 2011

Updated by mjbrooks on 2011-07-28 23:14:40 +00:00

dnsmichi: As I understand it, SLA is being address elsewhere. #992 is done, which covers the coloring portion of this request... so what to do with this ticket now?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 2, 2011

Updated by mfriedrich on 2011-08-02 18:32:39 +00:00

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

resolve it and for the sla reporting stuff, create a ticket in the reporting section. i don't think this should be covered in the gui sections nor the core sections.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2014

Updated by mfriedrich on 2014-12-08 09:34:05 +00:00

  • Project changed from 19 to Core, Classic UI, IDOUtils
  • Category set to Classic UI
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.