Software /
code /
prosody-modules
File
mod_log_messages_sql/README.markdown @ 5810: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 |
parent | 3438:b74c86d137c9 |
line wrap: on
line source
# Introduction ::: {.alert .alert-danger} Consider using [mod_mam][doc:modules:mod_mam] together with [mod_readonly] instead. ::: This module logs messages to a SQL database. SQL connection options are configured in a `message_log_sql` option, which has the same syntax as the `sql` option for [mod_storage_sql][doc:modules:mod_storage_sql]. # Usage You will need to create the following table in the configured database: ``` sql CREATE TABLE `prosodyarchive` ( `host` TEXT, `user` TEXT, `store` TEXT, `id` INTEGER PRIMARY KEY AUTOINCREMENT, `when` INTEGER, `with` TEXT, `resource` TEXT, `stanza` TEXT); ``` # Compatibility Does *NOT* work with 0.10 due to a conflict with the new archiving support in `mod_storage_sql`·