Mercurial > prosody-modules
view mod_host_status_check/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 | 2a16a6c67288 |
children | 694b62d8a82f |
line wrap: on
line source
--- labels: Stage-Beta summary: Host status check ... Introduction ============ This module allows you to monitor the state of hosts and components in your Prosody server. For example, it will track whether components are connected and (if the component supports it) listen for heartbeats sent by the component to indicate that it is functioning. This module does not expose any interface to access the status information itself. See [mod\_http\_host\_status\_check] for a module that allows you to access host status information over HTTP(S). Configuration ============= There are no configuration options for this module. You should enable it on every host that you want to monitor, by adding it to modules\_enabled. Note that to monitor components, adding to the global modules\_enabled list will not suffice - you will need to add it to the component's own modules\_enabled, like this: ``` {.lua} Component "mycomponent.example.com" modules_enabled = { "host_status_check" } ``` Compatibility ============= Works with Prosody 0.9.x and later.