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 #7071] Re-design passive checks and freshness #1951

Closed
icinga-migration opened this issue Sep 3, 2014 · 20 comments
Closed

[dev.icinga.com #7071] Re-design passive checks and freshness #1951

icinga-migration opened this issue Sep 3, 2014 · 20 comments

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Sep 3, 2014

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

Created by mfriedrich on 2014-09-03 19:18:34 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2016-11-09 14:59:57 +00:00 (in Redmine)


=> Monitoring Basics

21:05:45 < CrossWire> question: i am trying to deploy a passive check wherewith the client uses nsca to submit results. It works fine ... stats get updated as 
                      expected. However when the hosts stop sending 'updates' icinga2 still happily thinks all is fine (with a last check 30 minutes ago) ... in 
                      the service i disabled active checks and enabled passive checks (like i did with nagios). Did i miss an option for him to notice its not 
                      getting any updates?
21:11:14 < shroud> CrossWire: icinga2 reschedules checks when it receives passive check results, so all you have to do is to enable active checks, set the check 
                   interval to a somewhat larger interval and decrease the retry interval
21:12:01 < shroud> for example, assuming nsca sends check results every 5 minutes and you want notifications after about 10 minutes if you don't get any 
                   results: check_interval = 10m, retry_interval = 10s
21:12:10 < CrossWire> so active checks should be enabled
21:12:13 < shroud> yes
21:14:46 < shroud> something like this should work:
21:14:50 < shroud> object Service "nsca-svc" {
21:14:50 < shroud>   import "generic-service"
21:14:50 < shroud>   check_command = "passive"
21:14:50 < shroud>   check_interval = 10m
21:14:50 < shroud>   max_check_attempts = 1
21:14:52 < shroud> }
21:15:22 < shroud> http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/configuring-icinga2#plugin-check-command-passive

Relations:

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Sep 5, 2014

Updated by gbeutner on 2014-09-05 13:13:25 +00:00

  • Subject changed from Better explaination of passive checks to Better explanation of passive checks
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Sep 5, 2014

Updated by gbeutner on 2014-09-05 13:14:17 +00:00

  • Target Version set to 2.1.1
  • Estimated Hours set to 2
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Sep 16, 2014

Updated by mfriedrich on 2014-09-16 09:22:22 +00:00

  • Project changed from 42 to Icinga 2
  • Category set to Documentation
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Sep 16, 2014

Updated by mfriedrich on 2014-09-16 10:19:19 +00:00

  • Target Version deleted 2.1.1
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Nov 24, 2014

Updated by mfriedrich on 2014-11-24 14:02:38 +00:00

  • Subject changed from Better explanation of passive checks to Re-design passive checks
  • Category changed from Documentation to libicinga
  • Target Version set to 2.3.0
  • Start Date deleted 2014
  • Estimated Hours deleted 2
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 26, 2015

Updated by mfriedrich on 2015-01-26 15:05:56 +00:00

  • Target Version changed from 2.3.0 to 2.4.0
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Apr 3, 2015

Updated by mfriedrich on 2015-04-03 16:30:10 +00:00

  • Relates set to 8141
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Apr 22, 2015

Updated by tobiasvdk on 2015-04-22 12:05:13 +00:00

How about adding a boolean attribute expect_continuously_check_results (defaults to false) to the Service object. If you set this to true then

  • check_interval is the value how frequent check results are expected
  • max_check_attempts check results can be missed, after this value the service goes into 'UNKNOWN'
  • check_command is optional; if it's defined it gets called when service becomes 'UNKNOWN'
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented May 18, 2015

Updated by mfriedrich on 2015-05-18 08:14:42 +00:00

  • Target Version deleted 2.4.0
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jun 22, 2015

Updated by mfriedrich on 2015-06-22 14:52:51 +00:00

  • Relates set to 8905
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jun 23, 2015

Updated by mfriedrich on 2015-06-23 13:36:38 +00:00

  • Target Version set to Backlog
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jul 7, 2015

Updated by mfriedrich on 2015-07-07 12:36:19 +00:00

  • Subject changed from Re-design passive checks to Re-design passive checks and freshness
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Nov 23, 2015

Updated by mathiasaerts on 2015-11-23 17:24:05 +00:00

Any chance this can be included in 2.5.0? The unknown check results are really frustrating every time Icinga is restarted..

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 4, 2016

Updated by mfriedrich on 2016-03-04 16:52:55 +00:00

  • Relates deleted 8905
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 4, 2016

Updated by mfriedrich on 2016-03-04 16:53:21 +00:00

  • Parent Id set to 11310
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 7, 2016

Updated by tclh123 on 2016-03-07 08:07:16 +00:00

Hi @dnsmichi,
I found icinga2 didn't reschedules checks when it receives passive check results.
I use icinga r2.4.2-1.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jun 14, 2016

Updated by elippmann on 2016-06-14 09:54:27 +00:00

Hi,

At the moment freshness checks are only executed if active checks are enabled. Our documentation may be a bit misleading here.

In my opinion it would be great to reintroduce the freshness_threshold from Icinga 1.x.

If active checks are disabled and the freshness_threshold has passed without any new passive check result, Icinga 2 will run the configured check command as a forced active check. This virtual expiration time is calculated from
last check result time + freshness threshold and is reset once Icinga 2 receives a passive check result or when Icinga 2 triggers the forced active check.

Just for the records, the check_interval in terms of active checks disabled represents the interval in which Icinga 2 expects passive check results. If the check_interval has passed w/o any new passive check result, nothing will happen in Icinga 2. But Icinga Web 2 displays that the check result is late. The check_interval (and retry_interval) for disabled active checks have visual impact only.

Best regards,
Eric

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Nov 9, 2016

Updated by mfriedrich on 2016-11-09 14:59:57 +00:00

  • Parent Id deleted 11310
@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@gunnarbeutner gunnarbeutner removed the libicinga label Feb 7, 2017
@dnsmichi dnsmichi added the wishlist label Feb 7, 2017
@dnsmichi dnsmichi modified the milestone: Backlog Sep 13, 2017
@dnsmichi dnsmichi added queue/wishlist and removed wishlist labels May 9, 2019
@dnsmichi dnsmichi added this to Design Drafts in icinga2 Nov 15, 2019
@htriem
Copy link
Contributor

@htriem htriem commented Jan 22, 2020

@lippserd Is this still relevant?

@lippserd
Copy link
Member

@lippserd lippserd commented Mar 22, 2020

@lippserd Is this still relevant?

@htriem I think we can close this one.

@lippserd lippserd removed their assignment Mar 22, 2020
@N-o-X N-o-X closed this Mar 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
icinga2
  
Design Drafts
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.