This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 2 and 3
Revision 2 as of 2017-12-15 14:21:43
Size: 2570
Editor: TimoSirainen
Revision 3 as of 2017-12-15 14:22:48
Size: 2655
Editor: TimoSirainen
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:

The gathered statistics are available by running:

doveadm stats dump


This page is about the statistics support for Dovecot v2.3. For v2.1 and v2.2 see Statistics/Old.

Dovecot v2.3 supports gathering statistics from "events". Eventually all of the log messages should be events, so it will be possible to configure Dovecot to get statistics for anything that is logged. For debug messages it's possible to get statistics even if the message itself isn't logged.

The gathered statistics are available by running:

doveadm stats dump

Currently there are no statistics logged by default (but this might change). You'll need to add some metrics:

metric name {
  # Individual events can be identified either by their name or source file:line location.
  # The source location of course can change between Dovecot versions, so it should be
  # avoided.
  event_name = example_event_name
  #source_location = example.c:123

  # Space-separated list of categories that must match the event (e.g. "mail" or "storage")
  #categories = 

  # List of fields in event parameters that are included in the metrics.
  # All events have a default "duration" field that doesn't need to be listed here.
  #fields = 

  # List of key=value pairs that must match the event. The value can contain '?' and '*' wildcards.
  #filter {
  #  field_key = wildcard


Current list of named events and their parameters:


  • tag: Command tag
  • name: Command name
  • args: Command's full parameters
  • human_args: Command's parameters as more human-readable output
  • tagged_reply_state: OK, NO, BAD
  • tagged_reply: Full tagged reply, e.g. "OK SELECT finished."
  • last_run_time: Timestamp when the command was running last time (it's followed by "mailbox sync" that can take some time)
  • running_usecs: How many usecs this command itself has spent running
  • lock_wait_usecs: How many usecs this command itself has spent waiting for locks.
  • bytes_in, bytes_out: How many bytes of client input/output command has used.


  • attmpts: Number of individual HTTP request attempts that were done (i.e. number of retries after failures + 1)


metric imap_select_no {
  event_name = imap_command_finished
  filter {
    name = SELECT
    tagged_reply_state = NO
metric imap_select_no_notfound {
  event_name = imap_command_finished
  filter {
    name = SELECT
    tagged_reply = NO*Mailbox doesn't exist:*

metric storage_http_gets {
  event_name = http_request_finished
  categories = storage
  filter {
    method = get

None: Statistics (last edited 2019-09-12 12:32:09 by MichaelSlusarz)