Mercurial > prosody-modules

comparison mod_log_ringbuffer/README.markdown @ 4220:0b1b7d671448

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_log_ringbuffer: Document how to integrate with mod_debug_traceback
author Matthew Wild <mwild1@gmail.com>
date Fri, 16 Oct 2020 18:48:08 +0100
parents b3dd77f2d0d7
children df2ccb42a241
comparison
equal deleted inserted replaced
4219:b3dd77f2d0d7 4220:0b1b7d671448
90 for the path to Prosody's data directory. 90 for the path to Prosody's data directory.
91 91
92 The filename does not have to be unique for every dump - if a file with the same 92 The filename does not have to be unique for every dump - if a file with the same
93 name already exists, it will be appended to. 93 name already exists, it will be appended to.
94 94
95 ## Integration with mod_debug_traceback
96
97 This module can be used in combination with [mod_debug_traceback] so that debug
98 logs are dumped at the same time as the traceback. Use the following configuration:
99
100 ``` {.lua}
101 log = {
102 ---
103 -- other optional logging config here --
104 ---
105
106 {
107 to = "ringbuffer";
108 level = "debug";
109 filename_template = "{paths.data}/traceback-{pid}-{count}.log";
110 event = "debug_traceback/triggered";
111 };
112 }
113 ```
114
115 If the filename template matches the traceback path, both logs and traceback will
116 be combined into the same file. Of course separate files can be specified if preferred.
117
95 # Compatibility 118 # Compatibility
96 119
97 0.11 and later. 120 0.11 and later.