[dev.icinga.com #9423] Heavy logging on external commands

[icinga-migration]

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

Created by mfrosch on 2015-06-16 08:12:20 +00:00

Assignee: (none) Status: Rejected (closed on 2016-02-25 00:00:45 +00:00) Target Version: (none) Last Update: 2016-02-25 00:00:45 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

---

During tests with my SCOM connector, I noticed that there is no real good way to limit logging, other than severity.

Could we find a way to:

• Filter logs based on module and sub-event
• or be able to configure what commands are logged? (inside ExternalCommandListener)

Icinga/Nagios have the option log_passive_checks

[icinga-migration]

Updated by mfriedrich on 2015-07-24 18:08:29 +00:00

Imho the issue only comes up when using the command pipe to send in checkresults. Other logging capabilities won't be visible that much inside the application log. Compared to Icinga 1.x there are no external parsers requiring a filtered application log. On the other hand, filtering away somehow relevant information will harden our support with users being asked to provide logs at a certain log level - instead of a simple severity being raised in a probblem situation.

Passing checkresults should become fairly easy with 2.4 btw.

[icinga-migration]

Updated by mfriedrich on 2016-02-25 00:00:45 +00:00

• Status changed from New to Rejected

I don't think additional log levels are necessary at this point. We've been re-iterating this idea for a while now, and it always seemed overkill. We may reduce the output and hide some specific queries from the main application log, and so on. But adding additional configuration layers shouldn't take place.

After all, the external command pipe is part of the more or less legacy compat mode where we should not touch that much sooner or later.