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 #11772] Add lag threshold for cluster-zone check #4206

Closed
icinga-migration opened this issue May 11, 2016 · 4 comments

Comments

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

commented May 11, 2016

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

Created by webx on 2016-05-11 16:38:43 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-06-24 08:20:07 +00:00)
Target Version: 2.5.0
Last Update: 2016-06-24 08:32:49 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

Hi,

In a cluster environment, running over very poor network links (e.g.: LTE links in a moving vehicle), there could be a lot of connections/disconnections between the different nodes.

It would be very useful to have some thresholds available with the cluster-zone check to tolerate a long lag between two nodes before having a warning or critical state.

Thanks !

Cyril.

Attachments

Changesets

2016-06-24 08:18:38 +00:00 by mfriedrich 9c57294

Add lag thresholds to cluster-zone check

fixes #11772

2016-06-24 08:33:04 +00:00 by mfriedrich 1451a0e

Add lag thresholds to cluster-zone check

fixes #11772

2016-06-24 09:27:49 +00:00 by mfriedrich 3a1023a

Docs: Add a note about cluster-zone log lag thresholds.

refs #11772
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 21, 2016

Updated by mfriedrich on 2016-05-21 12:36:29 +00:00

  • Target Version set to Backlog
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 24, 2016

Updated by mfriedrich on 2016-06-24 08:15:43 +00:00

  • File added icinga2_cluster_zone_lag_thresholds_11772_ok.png
  • File added icinga2_cluster_zone_lag_thresholds_11772_config.png
  • File added icinga2_cluster_zone_lag_thresholds_11772_critical.png
  • File added icinga2_cluster_zone_lag_thresholds_11772_warning.png
  • Status changed from New to Assigned
  • Assigned to set to mfriedrich
  • Target Version changed from Backlog to 2.5.0
  • lag_warning, lag_critical in seconds
  • both purely optional - ResolveMacros needs missingMacro reference to determine whether the value was set or not
  • Extended PerfdataValue with Warn/Crit values
  • Output/State Formatting depending on thresholds set

Config

icinga2_cluster_zone_lag_thresholds_11772_config.png

OK

icinga2_cluster_zone_lag_thresholds_11772_ok.png

Warning

icinga2_cluster_zone_lag_thresholds_11772_warning.png

Critical

icinga2_cluster_zone_lag_thresholds_11772_critical.png

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 24, 2016

Updated by mfriedrich on 2016-06-24 08:20:07 +00:00

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

Applied in changeset 9c57294.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jun 24, 2016

Updated by mfriedrich on 2016-06-24 08:32:49 +00:00

Ah hm. I need to rename the custom attributes to provide the check prefix. Mea culpa :-)

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.