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 #8646] Introduce a proper output format for the executed check_commands #2710

Closed
icinga-migration opened this issue Mar 9, 2015 · 4 comments
Labels
enhancement New feature or request

Comments

@icinga-migration
Copy link

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

Created by mfrosch on 2015-03-09 08:48:12 +00:00

Assignee: (none)
Status: Closed (closed on 2015-09-05 14:49:46 +00:00)
Target Version: (none)
Last Update: 2015-09-05 14:49:46 +00:00 (in Redmine)

Backport?: No
Include in Changelog: 1

We need to find a way to dump the executed command line, with enough meta data to filter the arguments.

Ideas:

  • JSON
  • IDO text field / Livestatus field
  • updated on check execution
  • GUI must be able filter the output

TBD:

  • format
  • proper description of the feature

Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-29 16:20:57 +00:00

  • Category changed from Checker to libicinga
  • Assigned to deleted mfrosch

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-29 16:21:15 +00:00

  • Relates set to 9079

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-07-02 18:48:49 +00:00

  • Target Version set to Backlog

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-09-05 14:49:46 +00:00

  • Status changed from New to Closed
  • Target Version deleted Backlog

We won't add that to the existing backends, only expose that value using the API in 2.4. Everything else will introduce problems with filtering sensitive information (database or livestatus columns).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant