Software /
code /
prosody-modules
Comparison
mod_firewall/README.markdown @ 2093:7b9520479e99
mod_firewall: README: Document LOG's ability to take meta expressions
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Wed, 16 Mar 2016 11:46:47 +0000 |
parent | 2092:f5d78bc016a6 |
child | 2095:3b4a6d255d7a |
comparison
equal
deleted
inserted
replaced
2092:f5d78bc016a6 | 2093:7b9520479e99 |
---|---|
308 ### Informational | 308 ### Informational |
309 | 309 |
310 Action Description | 310 Action Description |
311 --------------- ------------------------------------------------------------------------------------------------------------------------ | 311 --------------- ------------------------------------------------------------------------------------------------------------------------ |
312 `LOG=message` Logs the given message to Prosody's log file. Optionally prefix it with a log level in square brackets, e.g. `[debug]` | 312 `LOG=message` Logs the given message to Prosody's log file. Optionally prefix it with a log level in square brackets, e.g. `[debug]` |
313 | |
314 You can include expressions in log messages, using `$(...)` syntax. For example, to log the stanza that matched the rule, you can use $(stanza), | |
315 or to log just the top tag of the stanza, use $(stanza:top_tag()). | |
316 | |
317 Example: | |
318 | |
319 # Log all stanzas to user@example.com: | |
320 TO: user@example.com | |
321 LOG=[debug] User received: $(stanza) | |
322 |