Re: Monitoring cyrusimapd
Michael Menge <[email protected]>
| Newsgroups | gmane.mail.imap.cyrus |
|---|---|
| Message-ID | <20180621105326.Horde.6fQnr-IzP6cV7HD4HMjk8VY@webmail.uni-tuebingen.de> |
Hi, Quoting Albert Shih <[email protected]>: > Hi everyone, > > I would like to know what kind of monitoring you perform on a cyrus-imapd. > Beside classic (check_imap, check_disk, check_cpu etc...) do you have any > special thing to monitor about cyrus-imapd. > In addition to the normal System monitoring (CPU-, Memory and Disk usage and the Checks if tie services are running, we monitor the Cyrus logs for Critical errors like IOERROR, or Mupdate commit errors. > For example do you launch any check on each database ? How can I > check if the replication work fine ? > No database checks. For Replication we check the size of the "sync" folder to see if the rolling replication log is growing over 1 MB or if average size of the logs was over 500 KB for more than 15 min -------------------------------------------------------------------------------- M.Menge Tel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: [email protected] Wächterstraße 76 72074 Tübingen ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus