[dev.icinga.com #8957] Fall back on syslog if the logger's type directive is misconfigured

[icinga-migration]

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

Created by elippmann on 2015-04-02 08:25:18 +00:00

Assignee: jmeyer
Status: Resolved (closed on 2015-04-13 15:13:06 +00:00)
Target Version: 2.0.0-rc1
Last Update: 2015-04-13 15:13:06 +00:00 (in Redmine)

---

Instead of logging

Cannot find log writer of type ""

to syslog on every request we should log the real log message and that the logger's type directive is misconfigured on actual log entries.

Changesets

2015-04-13 15:09:49 +00:00 by jmeyer 67ad575

Set the configured logging level even if the configured logging type is invalid

refs #8957

2015-04-13 15:11:42 +00:00 by jmeyer 36fed03

Do not log that the logging configuration is invalid on every request

Instead, log those messages *everytime* a subsequent message is being
logged.

refs #8957

[icinga-migration]

Updated by jmeyer on 2015-04-07 13:18:55 +00:00

• Status changed from New to Rejected

This is a joke. ;-)

[icinga-migration]

Updated by elippmann on 2015-04-07 13:37:07 +00:00

• Description updated
• Status changed from Rejected to New

Johannes wrote:

This is a joke. ;-)

The description is indeed not perfect. I'll update it.

[icinga-migration]

Updated by elippmann on 2015-04-07 14:22:09 +00:00

If the logger's type directive is misconfigured, Icinga Web 2 ignores the configured level and uses error by default. Error exceptions are routed to syslog correctly.

[icinga-migration]

Updated by jmeyer on 2015-04-13 14:03:36 +00:00

• Status changed from New to Assigned
• Assigned to set to jmeyer

[icinga-migration]

Updated by jmeyer on 2015-04-13 15:13:06 +00:00

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