Mercurial > prosody-modules
view mod_host_status_check/README.markdown @ 4719:5a06c711649c
mod_bookmarks2: Use max_items='max' on trunk, with fallback
check_node_config() throws an error attempting to compare the
pep_max_items number with the 'max' string, which allows detecting and
support using 'max' where available.
Unsure what happens when you upgrade, that seems a problem for a future
commit! :)
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Wed, 20 Oct 2021 22:16:14 +0200 |
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.