Mercurial > prosody-modules
view mod_storage_muc_log/README.markdown @ 4877:adc6241e5d16
mod_measure_process: Report the enforced limit
The soft limit is what the kernel actually enforces, while the hard
limit is is how far you can change the soft limit without privileges.
Unless the process dynamically adjusts the soft limit, knowing the hard
limit is not as useful as knowing the soft limit.
Reporting the soft limit and the number of in-use FDs allows placing
alerts on expressions like 'process_open_fds / process_max_fds >= 0.95'
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 18 Jan 2022 18:55:20 +0100 |
parents | 058844edcaaf |
children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' - ArchiveStorage summary: 'Storage module using mod\_muc\_log data with new stanza archive API' --- Introduction ============ [mod\_muc\_log] provided logging of chatrooms running on the server to Prosody's data store. This module gives access to this data using the 0.10+ stanza archive API, allowing legacy log data to be used with [mod\_mam\_muc] and [mod\_http\_muc\_log]. Details ======= Replace [mod\_muc\_log] and [mod\_muc\_log\_http] in your config with ``` {.lua} Component "conference.example.org" "muc" modules_enabled = { -- "muc_log"; -- functionality replaced by mod_mam_muc + mod_storage_muc_log "mam_muc"; -- Does logging to storage backend configured below -- "muc_log_http"; -- Replaced by the mod_http_muc_log "http_muc_log"; } storage = { muc_log = "muc_log"; } ``` Compatibility ============= version status --------- --------------- 0.9 unknown 0.10 works 0.11 does not work