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 #12216] icinga check reports "-1" for minimum latency and execution time and only uptime has a number but 0 #4394

Closed
icinga-migration opened this issue Jul 25, 2016 · 4 comments

Comments

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

commented Jul 25, 2016

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

Created by TheFlyingCorpse on 2016-07-25 07:38:45 +00:00

Assignee: TheFlyingCorpse
Status: Resolved (closed on 2016-07-26 07:55:04 +00:00)
Target Version: 2.5.0
Last Update: 2016-07-26 07:55:04 +00:00 (in Redmine)

Icinga Version: 2.4.3
Backport?: Not yet backported
Include in Changelog: 1

Icinga check for the perfdata output from the running instance reports a -1 on the following metrics:

min_execution_time
min_latency

In addition, it is not increasing any other values than uptime for the instance, even when remote checks are assigned to it via "command_endpoint" for instance, which might explain why its returning -1 to the two above, it doesnt "count" what is not locally defined.

The scenario is a setup as following:

Icinga - Master, only zone and endpoint defined,
Icinga - Slaves, only zone and endpoint defined, 

Observed in:
- Icinga2 version 2.4.3
- Icinga2 version 2.4.4
- Icinga2 version 2.4.10

Observed on:
- Debian (2.4.3, 2.4.4, 2.4.10)
- Oracle Linux (2.4.3, 2.4.10)
- Windows (2.4.4, 2.4.10)

Host, services, zones and endpoints are then defined via import and sync rules in Icinga Director.

Changesets

2016-07-25 13:43:33 +00:00 by TheFlyingCorpse 29c40f7

Fix min/max execution_time

refs #12216

2016-07-25 14:04:05 +00:00 by TheFlyingCorpse c1a8d52

Set min_latency and min_execution_time to 0 when there have been no checkresults processed.

refs #12216

2016-07-25 15:29:58 +00:00 by TheFlyingCorpse 9b62eba

Set min_latency and min_execution_time to 0 when there have been no checkresults processed.

refs #12216

2016-07-26 07:54:08 +00:00 by TheFlyingCorpse 730d959

Set min_latency and min_execution_time to 0 when there have been no checkresults processed

fixes #12216

Signed-off-by: Gunnar Beutner <gunnar.beutner@netways.de>
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 25, 2016

Updated by TheFlyingCorpse on 2016-07-25 13:37:16 +00:00

  • Assigned to set to TheFlyingCorpse

Found a few more errors:
https://git.icinga.org/?p=icinga2.git&a=search&h=HEAD&st=grep&s=scs.

min_latency and max_latency is copied to min_execution_time and max_execution_time

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 25, 2016

Updated by TheFlyingCorpse on 2016-07-25 15:34:13 +00:00

  • Done % changed from 0 to 90

Moved the fix for min/max execution_time to a separate ticket. Linked now is the revision required for this fix.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 26, 2016

Updated by gbeutner on 2016-07-26 07:54:42 +00:00

  • Category set to libicinga
  • Status changed from New to Assigned
  • Target Version set to 2.5.0
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 26, 2016

Updated by TheFlyingCorpse on 2016-07-26 07:55:04 +00:00

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

Applied in changeset 730d959.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.