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 #9060] Alert config reload failures with the icinga check #2896

Closed
icinga-migration opened this issue Apr 14, 2015 · 11 comments
Labels
area/distributed Distributed monitoring (master, satellites, clients) enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

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

Created by mfrosch on 2015-04-14 13:33:47 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2016-05-11 14:10:03 +00:00)
Target Version: 2.4.8
Last Update: 2016-05-11 15:24:35 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 0

If an satellite or config receiver fails reloading the new configuration this is only logged inside the logfile of the host.

We should add the information as an critical error when running the Icinga check, either locally or via command_endpoint.

So the system recognizes the failure and displays it to the user.

Attachments

Changesets

2016-05-11 14:07:28 +00:00 by gbeutner 1ad4d9c

Report failed reload attempts for the icinga check

fixes #9060
fixes #9997
fixes #11129

2016-05-12 09:11:03 +00:00 by gbeutner ff24863

Report failed reload attempts for the icinga check

fixes #9060
fixes #9997
fixes #11129

Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-29 16:08:02 +00:00

By flagging it as dirty only, or by adding a timestamp with the last failure allowing the caller to determine the delta himself?

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-10-30 23:43:02 +00:00

  • Target Version set to Backlog

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-10-30 23:43:25 +00:00

  • Category changed from Plugins to Cluster

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-11-02 09:17:04 +00:00

The parent process waits for the child on reload, if that action fails the local icinga check should return the warning state. This sends back a check result to the master.

@icinga-migration
Copy link
Author

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

  • Relates set to 11129

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-02-24 23:32:20 +00:00

  • Relates set to 9997

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-04-07 10:38:32 +00:00

  • Target Version changed from Backlog to 2.5.0

@icinga-migration
Copy link
Author

Updated by gbeutner on 2016-05-11 14:09:25 +00:00

  • Status changed from New to Assigned
  • Assigned to set to gbeutner
  • Target Version changed from 2.5.0 to 2.4.8

@icinga-migration
Copy link
Author

Updated by gbeutner on 2016-05-11 14:09:33 +00:00

  • Include in Changelog changed from 1 to 0

@icinga-migration
Copy link
Author

Updated by gbeutner on 2016-05-11 14:10:03 +00:00

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

Applied in changeset 1ad4d9c.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-05-11 15:24:35 +00:00

  • File added icinga2_icinga_check_last_failed_reload.png

Awesome :)

icinga2_icinga_check_last_failed_reload.png

@icinga-migration icinga-migration added enhancement New feature or request area/distributed Distributed monitoring (master, satellites, clients) labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.4.8 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) enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant