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

[dev.icinga.com #992] maintenance-mode for servers #451

Closed
icinga-migration opened this issue Nov 11, 2010 · 32 comments

Comments

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

commented Nov 11, 2010

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

Created by dklueh on 2010-11-11 06:38:30 +00:00

Assignee: mjbrooks
Status: Resolved (closed on 2011-07-16 23:01:01 +00:00)
Target Version: 1.5
Last Update: 2014-12-08 09:39:49 +00:00 (in Redmine)


maintenance-mode for servers and/or services which is conscious and well planned down.
It would be nice if these servers, and services are not critical any more, but shown as maintenance.

See pictures below- anything like this would be reasonable.

Attachments

Changesets

2011-06-03 06:08:04 +00:00 by (unknown) 56cf27e

Added option to suppress coloring of hosts/services in maintenance #992

The current Classic UI view shows the state of hosts including
attention grabbing colors even if the host/service is scheduled for
downtime. This tends to distract from discerning which problems
really exist between those which were planned or expected.

This commit adds the following option to cgi.cfg:

suppress_maintenance_downtime=0

It is disabled by default to maintain the old behavior, however
those wishing to enable it will note that rather than displaying
issues in their regular color, they will be grey (similar to
the pending state). The status, however will still display the
actual state and this is intended behavior. This is so the user
can use icinga to see what the state is in before the downtime
ends. A useful example for this is so it can be seen that a
host/service that was being worked on actually came back online.

In addition, hosts in scheduled downtime will be grey in the
statusmap.cgi

refs #992

Relations:

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 11, 2010

Updated by ricardo on 2010-11-11 18:27:49 +00:00

  • Priority changed from High to Normal

I somehow like this, what are the others think about that?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 12, 2010

Updated by Joerg_M on 2010-11-12 08:00:33 +00:00

I like it, too.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 16, 2010

Updated by mfriedrich on 2010-11-16 09:50:12 +00:00

  • Status changed from New to Feedback

so considering another presentation only change for hosts/services being in a scheduled downtime, right?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 16, 2010

Updated by dklueh on 2010-11-16 09:53:42 +00:00

Yes, this would be nice- if a scheduled downtime would be shown as maintenance.

dnsmichi wrote:

so considering another presentation only change for hosts/services being in a scheduled downtime, right?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 16, 2010

Updated by mfriedrich on 2010-11-16 11:24:36 +00:00

ok, then i'll vote for an opt-in feature, enabled through a config option then, deciding which printf is being shown based on the state/downtime being set.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 16, 2010

Updated by dklueh on 2010-11-16 12:05:44 +00:00

Yes- this would be a nice integration!

dnsmichi wrote:

ok, then i'll vote for an opt-in feature, enabled through a config option then, deciding which printf is being shown based on the state/downtime being set.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Mar 14, 2011

Updated by mfriedrich on 2011-03-14 21:44:06 +00:00

  • Priority changed from Normal to Low
  • Target Version set to 1.5
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Mar 24, 2011

Updated by mfriedrich on 2011-03-24 21:33:58 +00:00

  • Status changed from Feedback to Assigned
  • Assigned to set to ricardo

one for you, but 1.5 @ricardo

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Apr 4, 2011

Updated by mjbrooks on 2011-04-04 06:51:48 +00:00

I think this is essentially a dupe of #421

I'll leave it to someone who knows best to decide ;)

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 10, 2011

Updated by mjbrooks on 2011-05-10 08:38:11 +00:00

  • File added 993-examples6.png
  • File added 992-examples.png
  • File added 993-examples2.png
  • File added 993-examples3.png
  • File added 993-examples4.png
  • File added 993-examples5.png

dklueh thanks for being patient. I can see this has been aging a bit.

On reading through it again, #421 includes change request regarding calculating service availability for SLAs. Which makes that more of a two part issue and since anything affecting availability data or reporting should be considered carefully, it would be something that needs to be discussed a lot more.

This one (and the first part of #421) is just straight up display.

I hope I'm not stepping on your feet here by jumping in ricardo, but I didn't catch you around today and I was able to quickly put something together for you to look at. As soon as I finalize a few things, do a few checks and clean up my commits, I'll push it onto a topic branch.

Couple of points:

It'll be opt-in (off by default in cgi.cfg)

I'm going with gray by default (changeable via CSS). Gray for pending and for maintenance could then be seen by people to mean "Icinga won't say it's up or down either because it doesn't have the info or it was told not to"

Other than the extinfo where it says MAINTENANCE, I'm leaving the display of the reported state. I think it's useful to see the state rather than hide it so you know where things will be at when it comes out of maintenance and so you can use it as a tool while working on the host/service in question.

Although it says MAINTENANCE, I haven't created a new state... perhaps that is taboo or it might be preferred to only do that for the SLA part mentioned in the other ticket?

Any thoughts on my approach or the pretty pictures are appreciated.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 10, 2011

Updated by ricardo on 2011-05-10 15:00:09 +00:00

hey, no problem.

feel free to fix whatever you like. :D
We just have to take care not to work at the same stuff at the same time.

But it already looks good from the pics.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 11, 2011

Updated by dklueh on 2011-05-11 05:33:02 +00:00

@mjbrooks:
No problem- this would be a very useful functionality for us- so we wait patiently for release 1.5! :-)

Your pictures look really great- that is exactly what i thought about.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 12, 2011

Updated by mjbrooks on 2011-05-12 05:12:35 +00:00

  • Assigned to changed from ricardo to mjbrooks
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 3, 2011

Updated by mjbrooks on 2011-06-03 06:24:42 +00:00

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

Just pushed to mbrooks/cgis in git. Redmine should pick it up whenever it wakes up.

@dnsmichi FYI, I checked this against rbartels/cgi-current just to be safe and it merges with his branch cleanly.

@dklueh Let me know if this works for you.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 4, 2011

Updated by mfriedrich on 2011-06-04 14:58:17 +00:00

good all recent cgi changes are merged into mfriedrich/cgis while i am touching the core in my normal branch. i've only checked ricardo's changes, the other ones are opt-in so i'd have to check manually then when it comes to 1.5 target (right on is 1.4.1).

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 6, 2011

Updated by dklueh on 2011-06-06 09:28:37 +00:00

Hi all!
In which snapshot will this feature testable? The todays git doesn't include this, right?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 6, 2011

Updated by mjbrooks on 2011-06-06 09:55:15 +00:00

It won't be in master until after 1.4.1 is released soon.

Until then, you can check it out directly or checkout my whole branch which only has one other feature after it having to do with showing partial hostgroups:

$ git checkout 56cf27e

or

$ git checkout origin/mbrooks/cgis

respectively.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 6, 2011

Updated by mfriedrich on 2011-06-06 10:41:23 +00:00

it's been merged into test/cgis

https://git.icinga.org/?p=icinga-core.git;a=shortlog;h=refs/heads/test/cgis

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 6, 2011

Updated by dklueh on 2011-06-06 11:20:37 +00:00

Ok, I tested the new feature- its great! Working well in Host- and Service Detail- except in StatusMap- there it is already makred as "up"

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 6, 2011

Updated by mjbrooks on 2011-06-06 11:22:27 +00:00

Is it in a gray color and when you hover over it it says "Up (Maintenance)"?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 6, 2011

Updated by dklueh on 2011-06-06 11:46:34 +00:00

No, only the views Host and Service Detail show the grey color- in StatusMap it's green and up- not showing maintenance... is there another parameter but suppress_maintenance_downtime=1 i have to set?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 6, 2011

Updated by mjbrooks on 2011-06-06 22:18:38 +00:00

I believe the status displayed in statusmap is based on the host state, is the host also in maintenance or just some of the services that are on the host?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 15, 2011

Updated by dklueh on 2011-06-15 06:38:11 +00:00

Sorry for my delayed answer-

Yes, host and each service is in maintenance, it's grey colored when i take a look at hsot or service detail- but not in the status-map view- there it is marked as 'up'

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 15, 2011

Updated by mjbrooks on 2011-06-15 07:25:38 +00:00

Well, it should say "Up" as I didn't want to hide the state because it's useful information.

I don't remember which part it is off the top of my head, but there is some additional CSS entries that do some of the grey coloring. Did you "make install-html" as well?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 25, 2011

Updated by mjbrooks on 2011-06-25 23:56:51 +00:00

Can you post a screenshot?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 27, 2011

Updated by dklueh on 2011-06-27 08:50:25 +00:00

Sorry, but during a crash in our SAN, my testserver is temporary unavailable... so i couldn't send a screenshot. But i think, I forgot to install hmtl... I'll test this as soon as possible...

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 16, 2011

Updated by mfriedrich on 2011-07-16 16:02:53 +00:00

what's the status on this?

if it runs into 1.5 pls create a docs issue for the cgi.cfg config option.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 16, 2011

Updated by mjbrooks on 2011-07-16 23:01:01 +00:00

  • Status changed from Feedback to Closed

Done.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2011

Updated by mfriedrich on 2011-07-17 09:51:49 +00:00

  • Status changed from Closed to Resolved

if done means resolved, pls mark it as that - it allows easier searching/sorting in the overall issues table :)

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2011

Updated by mjbrooks on 2011-07-17 09:58:35 +00:00

Yes, that was an error on my part that I realized right away, but for some reason I don't have permission to change it once it's closed so I couldn't correct it.

Thanks for correcting it.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2011

Updated by mfriedrich on 2011-07-17 10:04:27 +00:00

i think it's somehow a redmine permission problem. take it on for mumble to organize the manager parts of each subproject better. i've now granted you manager priviliegues on the classic ui project.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Dec 8, 2014

Updated by mfriedrich on 2014-12-08 09:39:49 +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.