Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #1137] Show full command as executed by Icinga #285

Closed
icinga-migration opened this issue Jan 21, 2011 · 11 comments
Closed

Comments

@icinga-migration
Copy link

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

Created by tgelf on 2011-01-21 15:29:39 +00:00

Assignee: (none)
Status: Closed (closed on 2014-07-19 14:03:32 +00:00)
Target Version: (none)
Last Update: 2014-07-19 14:03:32 +00:00 (in Redmine)


Debugging failing checks (plugins) is a time-robbing and nasty task. You have to go through resources.cfg, host, service and command definitions to build the same statement that is run by Icinga.

It would be really, really helpful if this command could be "resolved" and "normalized" by Icinga and shown below the check information - always or on request.

Please note that there are sensible informations to be found in such a check command, therefore this feature should be accessible only for users equipped with a dedicated principal. A member of the default group "icinga_users" shall definitively NOT be granted such permissions.


Relations:

@icinga-migration
Copy link
Author

Updated by jmosshammer on 2011-09-26 15:48:41 +00:00

  • Target Version set to 1.7

@icinga-migration
Copy link
Author

Updated by jmosshammer on 2011-09-26 15:48:49 +00:00

  • Category set to Logging

@icinga-migration
Copy link
Author

Updated by tgelf on 2011-09-26 16:21:44 +00:00

NB: "Logging" is IMO not the right category for this feature request - this should find it's place in some check-related detail presentation dialog. Icinga Classic has in the meantime implemented such a feature.

@icinga-migration
Copy link
Author

Updated by jmosshammer on 2011-09-26 19:16:35 +00:00

  • Category changed from Logging to Interface Features

better :) ?

@icinga-migration
Copy link
Author

Updated by mhein on 2012-01-19 17:10:17 +00:00

  • Target Version deleted 1.7

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-04-30 18:37:27 +00:00

  • Status changed from New to Feedback
  • Priority changed from Normal to Low

i would go with classic ui - full command resolution, or likewise, as the wiki guides suggest, get yourself some debug logs as well.

probably icinga-web needs to implement macro grabbing somehow as well, in order to show a config cronk?

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-10-24 16:55:18 +00:00

  • Target Version set to 1.10

depends on #1882 and most likely, this should be put in place for icinga2 then imho.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-03-08 20:19:18 +00:00

  • Target Version changed from 1.10 to 1.9

might be resolvable with #3810

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-03-10 20:46:04 +00:00

  • Priority changed from Low to High

is resolvable with #3810 but requires some credentials to be added.

  • role icinga_admin sees it
  • role icinga_user only with special permission credential

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-03-11 18:05:25 +00:00

  • Priority changed from High to Normal
  • Target Version deleted 1.9

hm, #3810 requires more than that. dropping for security relevance, as discussed today.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-07-19 14:03:32 +00:00

  • Status changed from Feedback to Closed

I'd say we'll leave it to Icinga Web 2 doing it right here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant