view mod_storage_muc_log/README.markdown @ 5787:e79f9dec35c0

mod_c2s_conn_throttle: Reduce log level from error->info Our general policy is that "error" should never be triggerable by remote entities, and that it is always about something that requires admin intervention. This satisfies neither condition. The "warn" level can be used for unexpected events/behaviour triggered by remote entities, and this could qualify. However I don't think failed auth attempts are unexpected enough. I selected "info" because it is what is also used for other notable session lifecycle events.
author Matthew Wild <mwild1@gmail.com>
date Thu, 07 Dec 2023 15:46:50 +0000
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