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 #4139] Notify monitoring backend availability problems #162

Closed
icinga-migration opened this issue May 7, 2013 · 23 comments
Labels
area/monitoring Affects the monitoring module enhancement New feature or improvement
Milestone

Comments

@icinga-migration
Copy link

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

Created by gbeutner on 2013-05-07 09:44:38 +00:00

Assignee: afuhr
Status: Closed (closed on 2015-05-04 09:32:16 +00:00)
Target Version: 2.0.0-rc1
Last Update: 2015-05-04 09:32:16 +00:00 (in Redmine)


As a user, I want to be informed about backend problems because it is important to know that information is outdated or a backend does not work properly.

Acceptance criteria:

  • Check timestamp for status.dat / IDO
  • Check Livestatus socket availability
  • Check update timestamps
  • Notify via a top-tray balloon system (event system)
  • Provide a permanent message about backend errors
  • Provide information on every page
  • Provide useful information i.e. with a link to documentation

Changesets

2015-04-30 14:10:44 +00:00 by afuhr 5075ccd

Add ProblemMenuItemRenderer to system menu as renderer

refs #4139

2015-04-30 14:12:36 +00:00 by afuhr 880b1eb

Add better styling for backend-not-running class

refs #4139

2015-04-30 14:13:10 +00:00 by afuhr 8484a27

Add a backend problem menu item renderer to system menu

refs #4139

2015-04-30 14:15:33 +00:00 by afuhr 15b86e5

Merge branch 'feature/menu-item-renderer-backend-4139'

resolves #4139

Relations:

@icinga-migration
Copy link
Author

Updated by gbeutner on 2013-05-07 09:45:52 +00:00

  • Description updated

@icinga-migration
Copy link
Author

Updated by mhein on 2013-07-29 12:01:34 +00:00

  • Target Version set to 140

@icinga-migration
Copy link
Author

Updated by mhein on 2013-07-29 13:22:46 +00:00

  • Subject changed from Report backend availability problems to Notify backend availability problems
  • Estimated Hours set to 16

@icinga-migration
Copy link
Author

Updated by mhein on 2013-12-23 15:33:35 +00:00

  • Subject changed from Notify backend availability problems to Notify Backend Availability Problems
  • Description updated
  • Target Version changed from 140 to Backlog

@icinga-migration
Copy link
Author

Updated by mhein on 2014-01-16 07:17:12 +00:00

  • Category changed from 138 to Monitoring

@icinga-migration
Copy link
Author

Updated by mhein on 2014-01-16 07:38:58 +00:00

  • Description updated

@icinga-migration
Copy link
Author

Updated by elippmann on 2014-02-04 13:05:46 +00:00

  • Target Version changed from Backlog to 2.0-2

@icinga-migration
Copy link
Author

Updated by elippmann on 2014-03-14 16:08:16 +00:00

  • Target Version changed from 2.0-2 to 2.0-3

@icinga-migration
Copy link
Author

Updated by elippmann on 2014-06-01 12:36:08 +00:00

  • Target Version changed from 2.0-3 to Backlog

@icinga-migration
Copy link
Author

Updated by elippmann on 2014-10-28 08:43:42 +00:00

  • Target Version changed from Backlog to 2.0-16

@icinga-migration
Copy link
Author

Updated by elippmann on 2014-11-21 15:38:54 +00:00

  • Target Version changed from 2.0-16 to Backlog

@icinga-migration
Copy link
Author

Updated by elippmann on 2014-11-25 15:49:28 +00:00

  • Relates set to 7821

@icinga-migration
Copy link
Author

Updated by elippmann on 2015-03-27 15:09:02 +00:00

  • Subject changed from Notify Backend Availability Problems to Notify monitoring backend availability problems
  • Target Version changed from Backlog to 2.0.0-rc1

@icinga-migration
Copy link
Author

Updated by elippmann on 2015-03-31 13:44:26 +00:00

  • Relates deleted 7821

@icinga-migration
Copy link
Author

Updated by elippmann on 2015-03-31 13:44:45 +00:00

  • Duplicated set to 7821

@icinga-migration
Copy link
Author

Updated by elippmann on 2015-04-20 08:46:17 +00:00

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

@icinga-migration
Copy link
Author

Updated by afuhr on 2015-04-30 14:25:03 +00:00

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

Applied in changeset 15b86e5.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-30 14:34:48 +00:00

  • Relates set to 9207

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-30 14:37:40 +00:00

Monitoring Health does not auto-refresh nor does the menu - therefore it won't fetch a new state when running Icinga 2 again. I also don't see an alert popup similar to when the http webserver connection dies.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-30 15:15:45 +00:00

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

Ok, I had accidently disabled the auto-refresh.

One thing which is missing is the popup tray similar to http connection loss.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-30 16:48:39 +00:00

PS: I did review this with Alex and changed the state with him.

@icinga-migration
Copy link
Author

Updated by afuhr on 2015-05-04 09:29:22 +00:00

  • Relates set to 9219

@icinga-migration
Copy link
Author

Updated by afuhr on 2015-05-04 09:32:16 +00:00

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

@michael I have talked to Tom, so I opened a new Issue https://dev.icinga.org/issues/9219

@icinga-migration icinga-migration added enhancement New feature or improvement area/monitoring Affects the monitoring module labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.0.0-rc1 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 enhancement New feature or improvement
Projects
None yet
Development

No branches or pull requests

1 participant