prosody-modules
f64d13d9b76b
misc/lnav/prosody.json

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody-modules

Comparison

misc/lnav/prosody.json @ 4880:f64d13d9b76b

misc/lnav: Attempt at log format description for lnav The default lnav behavior often misidentifies messages with the word 'error' as errors, even in debug messages. This solves that.
author Kim Alvefur <zash@zash.se>
date Mon, 31 Jan 2022 11:51:50 +0100
child 5496:3e6d1e248dc1
comparison
equal deleted inserted replaced
4879:883d45d2082a 4880:f64d13d9b76b
1 {
2 "$schema" : "https://lnav.org/schemas/format-v1.schema.json",
3 "prosody_log" : {
4 "body-field" : "message",
5 "description" : "The Prosody IM server log format",
6 "level" : {
7 "debug" : "^debug$",
8 "error" : "^error$",
9 "info" : "^info$",
10 "warning" : "^warn$"
11 },
12 "level-field" : "loglevel",
13 "multiline" : false,
14 "ordered-by-time" : true,
15 "regex" : {
16 "standard" : {
17 "pattern" : "^(?<timestamp>\\w{3} \\d{2} \\d{2}:\\d{2}:\\d{2})\\s+(?<loggername>\\S+)\\s+(?<loglevel>debug|info|warn|error)\\s+(?<message>.+)$"
18 }
19 },
20 "sample" : [
21 {
22 "line" : "Jan 31 11:07:34 c2s565063fff480\tinfo\tClient connected"
23 }
24 ],
25 "timestamp-field" : "timestamp",
26 "timestamp-format" : "%b %d %H:%M:%S ",
27 "title" : "Prosody log",
28 "url" : "https://prosody.im/doc/logging",
29 "value" : {
30 "loggername" : {
31 "identifier" : true,
32 "kind" : "string"
33 },
34 "payload" : {
35 "kind" : "xml"
36 }
37 }
38 }
39 }