NAME

ejabberd_ - Munin wildcard plugin to monitor ejabberd2

CONFIGURATION

As connected users, registered users and server-connections have somewhat different scales, this plugin uses munins suggest feature to create the following graphs:

ejabberd_connections

ejabberd_memory

ejabberd_registrations

ejabberd_statuses

ejabberd_threads

ejabberd_uptime

ejabberd_users

ejabberd_usersindays

If the autodetect-feature for vhosts breaks, you can set

  [ejabberd_*]
    env.vhosts foo.com bar.com

in a file in plugin-conf.d to override it. ("user root" may also be smart/not so smart depending on your setup).

For monitoring user statuses - define statuses environment variable: (you can monitor only some of them)

  [ejabberd_*]
    env.statuses available away chat xa

For usersindays statistics define days environment variable. Be careful on high loaded servers, because it will plot all days in one graph.

  [ejabberd_*]
    env.days 1 7 30

If your ejabberd.cfg cannot be found you can se it this way

  [ejabberd_*]
    env.configfile /etc/ejabberd/ejabberd.cfg

MAGIC MARKERS

  #%# family=contrib
  #%# capabilities=autoconf suggest

AUTHOR

Written by Lasse Karstensen <lkarsten@hyse.org>. Based on ejabberd-plugin by Christian Dröge <Christian@draugr.de>

Status, memory, threads, uptime, usersindays, ejabberd2 and other code optimisation by Peter Viskup <skupko.sk@gmail.com>

LICENSE

Unknown

BUGS

Previously the documentation for this plugin mentioned RRDs limit on data series names. Munin works around this limit and the restriction does not apply.

There is no way to configure the path to ejabberdctl.