PROMSTATSD(8)

πŸ’– PROMSTATSD(8) πŸ’–

okay bestie, welcome to the promstatsd(8) page from the Cyrus IMAP manual β€” she's the Cyrus Prometheus statistics collating daemon and she is thriving. 🫢


✨ NAME ✨

promstatsd β€” Cyrus IMAP documentation

Cyrus Prometheus statistics collating daemon πŸ’…


🌸 SYNOPSIS 🌸

promstatsd [ -C config-file ] [ -v ] [ -f service-frequency ] [ -d ]

promstatsd [ -C config-file ] [ -v ] -c

promstatsd [ -C config-file ] [ -v ] -1

πŸ¦‹ DESCRIPTION πŸ¦‹

promstatsd is the Cyrus Prometheus statistics collating daemon. that's her whole job and she eats every time. πŸ”₯

when the prometheus_enabled setting in imapd.conf(5) is true, all the various Cyrus service processes start counting statistics as they run. promstatsd swoops in and collates all those stats into a text-based report that Prometheus can ingest. it's giving matchmaker but for numbers. ✨

the report promstatsd produces gets served by httpd(8) at the "/metrics" URL β€” but ONLY if "prometheus" has been set in httpmodules in imapd.conf(5). no config, no metrics, iykyk. πŸ™ˆ

promstatsd reads her configuration options out of the imapd.conf(5) file, unless you say otherwise with -C.

first synopsis β€” promstatsd runs as a daemon, updating the service report and (optionally) the usage report at the frequencies set by the prometheus_service_update_freq and prometheus_usage_update_freq options in imapd.conf(5). those default to 10s and disabled, respectively. the optional -f service-frequency argument can override prometheus_service_update_freq. this invocation should be run from the DAEMON section of cyrus.conf(5) (see Examples below πŸ‘‡).

second synopsis β€” promstatsd cleans up ALL the statistics files and then exits. the statistics Cyrus maintains are only valid while Cyrus is running, so this invocation MUST be run from the START section of cyrus.conf(5) (see Examples below πŸ‘‡) so she can clean up after the previous run, before any new service processes get started. no cap, it's mandatory. πŸ’€

third synopsis β€” promstatsd immediately updates the report(s) once, then exits. this is safe to use while another promstatsd process is running in daemon form. it's the move when you need the report updated right now for some reason and you cannot wait for the daemon's next update. main character urgency. πŸ‘‘


πŸ’… OPTIONS πŸ’…

  • -C config-file β€” use the specified configuration file config-file instead of the default imapd.conf(5).
  • -D β€” run the external debugger specified in the debug_command option of imapd.conf(5).
  • -1 β€” update the report(s) once and exit.
  • -c β€” clean up the stats directory and exit.
  • -d β€” debug mode β€” promstatsd will not background herself, for aid in debugging.
  • -f service-frequency β€” update the service report every service-frequency seconds. if you don't specify it, the prometheus_service_update_freq from imapd.conf(5) gets used, and that defaults to 10 seconds.
  • -v β€” increase verbosity. can be specified multiple times. stack 'em. πŸ“š

πŸŽ€ EXAMPLES πŸŽ€

to regularly produce a report that Prometheus can consume, promstatsd must be run from the DAEMON section of cyrus.conf(5) as per the first synopsis, like so:

DAEMON {
    promstatsd    cmd="promstatsd"
}

to make sure the statistical state is clean at startup, promstatsd must be run from the START section of cyrus.conf(5) as per the second synopsis, like so:

START {
    statscleanup  cmd="promstatsd -c"
}

πŸ“œ HISTORY πŸ“œ

literally nothing here bestie, it's just vibes and empty space. 🌈

πŸ“ FILES πŸ“

also empty. the void said hi. πŸ¦‹

πŸ‘€ SEE ALSO πŸ‘€

imapd.conf(5), cyrus.conf(5), httpd(8),


πŸ’œ AUTHOR πŸ’œ

The Cyrus Team πŸ‘‘


1993–2026, The Cyrus Team


and that's the whole page, bestie β€” no crumbs left. 🌸✨

version 3.12.4, dated Sep 09, 2026 β€” mwah, slay, periodt. πŸ’…πŸŽ€πŸ«Ά

πŸ“¦ where this page comes from