synapse/contrib/systemd/log_config.yaml

version: 1

# In systemd's journal, loglevel is implicitly stored, so let's omit it
# from the message text.
formatters:
    journal_fmt:
        format: '%(name)s: [%(request)s] %(message)s'

filters:
    context:
        (): synapse.util.logcontext.LoggingContextFilter
        request: ""

handlers:
    journal:
        class: systemd.journal.JournalHandler
        formatter: journal_fmt
        filters: [context]
        SYSLOG_IDENTIFIER: synapse

root:
    level: INFO
    handlers: [journal]

disable_existing_loggers: False
contrib/systemd: add a sample systemd unit file and a logger configuration The added logger configuration (--log-config or log_config:) uses systemd's python bindings to pass messages directly to the journal. Signed-off-by: Ivan Shapovalov <intelfx100@gmail.com> 2015-04-28 22:20:08 +00:00			`version: 1`

			`# In systemd's journal, loglevel is implicitly stored, so let's omit it`
			`# from the message text.`
			`formatters:`
			`journal_fmt:`
			`format: '%(name)s: [%(request)s] %(message)s'`

			`filters:`
			`context:`
			`(): synapse.util.logcontext.LoggingContextFilter`
			`request: ""`

			`handlers:`
			`journal:`
			`class: systemd.journal.JournalHandler`
			`formatter: journal_fmt`
			`filters: [context]`
			`SYSLOG_IDENTIFIER: synapse`

			`root:`
			`level: INFO`
			`handlers: [journal]`
contrib/systemd: log_config.yaml: do not disable existing loggers It turned out that merely configuring the root logger is not enough for "catch-all" semantics. The logging subsystem also needs to be told not to disable existing loggers (so that their messages will get propagated to handlers up the logging hierarchy, not just silently discarded). Signed-off-by: Ivan Shapovalov <intelfx100@gmail.com> 2015-05-31 16:21:55 +00:00
			`disable_existing_loggers: False`