Software /
code /
prosody-modules
File
mod_discodot/README.markdown @ 4877:adc6241e5d16
mod_measure_process: Report the enforced limit
The soft limit is what the kernel actually enforces, while the hard
limit is is how far you can change the soft limit without privileges.
Unless the process dynamically adjusts the soft limit, knowing the hard
limit is not as useful as knowing the soft limit.
Reporting the soft limit and the number of in-use FDs allows placing
alerts on expressions like 'process_open_fds / process_max_fds >= 0.95'
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 18 Jan 2022 18:55:20 +0100 |
parent | 4577:253df0798996 |
line wrap: on
line source
# Flowcharts! Put this module somewhere Prosody will find it and then run `prosodyctl mod_discodot | dot -Tsvg -o disco-graph.svg` to receive a graph like this[^1]: +------------------------+ +------------------------------------------+ | proxy.external.example | <-- | VirtualHost "example.com" | -+ +------------------------+ +------------------------------------------+ | | | | | v | +------------------------------------------+ | | Component "conference.example.com" "muc" | <+ +------------------------------------------+ Example config for the above: ``` {.lua} VirtualHost "xmpp.example.com" disco_items = { { "conference.example.com"; }; { "proxy.external.example"; }; } Component "conference.example.com" "muc" ``` Note the `disco_items` entry causing duplication since subdomains are implicitly added. [^1]: this was actuall made with `graph-easy`