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 #2715] Delegation: Freshness check #131

Closed
icinga-migration opened this issue Jun 26, 2012 · 6 comments
Closed

[dev.icinga.com #2715] Delegation: Freshness check #131

icinga-migration opened this issue Jun 26, 2012 · 6 comments
Labels
area/distributed Distributed monitoring (master, satellites, clients) blocker Blocks a release or needs immediate attention enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

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

Created by gbeutner on 2012-06-26 10:55:52 +00:00

Assignee: (none)
Status: Closed (closed on 2013-01-24 14:16:27 +00:00)
Target Version: Milestone 2
Last Update: 2013-09-23 14:29:47 +00:00 (in Redmine)


Check that we're getting check results for all of our services. Re-delegate services if necessary.

@icinga-migration
Copy link
Author

Updated by gbeutner on 2012-06-26 11:08:37 +00:00

  • Target Version set to Milestone 1

@icinga-migration
Copy link
Author

Updated by gbeutner on 2012-07-02 13:51:22 +00:00

  • Target Version changed from Milestone 1 to Milestone 2

We don't actually need this until we have passive checks (i.e. via the API).

@icinga-migration
Copy link
Author

Updated by gbeutner on 2012-11-26 07:41:56 +00:00

  • Priority changed from Normal to High

@icinga-migration
Copy link
Author

Updated by gbeutner on 2013-01-22 12:51:13 +00:00

(13:44:15) Gunnar Beutner: ich überlege mir gerade, wie ich freshness-checks machen will
(13:44:26) Gunnar Beutner: ich dachte da an folgendes:
(13:44:42) Gunnar Beutner: -du hast bei deinem service ganz normal ein check_interval
(13:45:16) Gunnar Beutner: -solange du immer brav passiv check-results reinkippst, wird jedesmal der next_check auf + <check_interval> aktualisiert
(13:45:25) Gunnar Beutner: wodurch dann keine aktiven checks ausgeführt werden
(13:45:40) Gunnar Beutner: wenn keine passiven checks mehr kommen, wird der service wie ein aktiver behandelt
(13:46:04) Gunnar Beutner: wenn du gar keine aktiven checks haben willst, machst du sie einfach komplett aus
(13:46:24) Gunnar Beutner: klingt das sinnvoll?
(13:47:37) Michael Friedrich: jo, klingt gut
(13:47:54) Michael Friedrich: allerdings sollte man freshness auch quasi global enablen koennen
(13:48:05) Gunnar Beutner: das verhalten da wäre global immer an
(13:48:15) Michael Friedrich: dh irgendwie muss ich den freshness trigger dann auch unterdruecken koennen, nicht nur via disable check
(13:48:44) Gunnar Beutner: du kannst bei einzelnen services aktive checks deaktivieren
(13:48:46) Gunnar Beutner: nicht nur global
(13:49:55) Michael Friedrich: ist die frage, wie man das dann nennt - die v1 user kennen freshness wie auch disable active checks... hmmm

@icinga-migration
Copy link
Author

Updated by gbeutner on 2013-01-24 14:16:27 +00:00

  • Status changed from New to Closed

Replaced by #3567.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-09-23 14:29:47 +00:00

  • Category set to Cluster

@icinga-migration icinga-migration added blocker Blocks a release or needs immediate attention enhancement New feature or request area/distributed Distributed monitoring (master, satellites, clients) labels Jan 17, 2017
@icinga-migration icinga-migration added this to the Milestone 2 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/distributed Distributed monitoring (master, satellites, clients) blocker Blocks a release or needs immediate attention enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant