Software /
code /
prosody-modules
File
mod_s2s_status/README.markdown @ 5218:1f4b768c831a
mod_http_oauth2: Correct field name for HTTP response status code
'code' is used in the incoming side of the Prosody HTTP stack while
'status_code' is used on the response side. Not confusing at all.
The default is 200 so this mistake had no real effect.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 07 Mar 2023 13:14:25 +0100 |
parent | 4791:b86282953663 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: 'Track the status and health of s2s connections' ... Introduction ============ Prosody already gives some insight into current s2s connections, e.g. via the `s2s:show()` command in the console. This will tell you about all current s2s connections. However sometimes this is not enough. For example if an s2s connection fails to establish, it won't show up - you have to go digging through the log file looking for the errors instead. This module maintains a record of recent connection attempts to a remote domain. You can use this module to answer questions such as: - Why did the last connection attempt to `example.com` fail? - When did I last have a successful connection with `example.com`? - Are my s2s connections generally stable? **Note:** At the time of writing, this module is not yet finished, and should be considered a proof-of-concept. # Configuration Just load the module as normal: ``` {.lua} modules_enabled = { ... "s2s_status"; ... } ``` # Compatibility trunk (0.12) and later, e.g. due to [60676b607b6d](https://hg.prosody.im/trunk/rev/60676b607b6d).