Redmine

Shows what is failing for the people who use your Redmine instance. The plugin reads the log files that Redmine already writes, keeps the entries that affect users, groups repeats, and explains each problem in plain English. It also reports the mail configuration, because the most common cause of "email does not work" is a setting, not an error.

What it reports¶

• Outgoing email - delivery failures, with a probable cause for each SMTP error (rejected credentials, firewall timeouts, TLS port mismatch, relay refusal, DNS).
• Incoming email - messages that the mail handler dropped without a reply (unknown sender, locked account, missing required field, no permission), and failed fetch tasks.
• Login and directory - LDAP/AD unreachable, failed logins, missing database_cipher_key.
• Attachments and files - files missing from disk, unwritable files/ directory, full disk, failed thumbnails.
• Repositories, database and application errors - failed SCM commands, deadlocks, 500 errors, aborted rake tasks.
• Mail configuration - delivery method (passwords masked), raise_delivery_errors, mailer logger, emission address, host name in links, and whether any notified events are selected.

It also finds the log files of cron and systemd jobs (for example the IMAP fetch log) automatically, and masks credentials on those command lines.

Access¶

Administrators open it from Administration. Two role permissions give access to other users: View log & mail insight and View log & mail insight configuration. Permitted users get a link in the top menu.

Read-only. No database migration. No core patches. Reads only the tail of each log, so large logs do not slow it down.

The plugin directory must be named redmine_log_insight. Redmine does not start if the name is different.

cd /path/to/redmine/plugins
git clone https://github.com/anthonyhorne/redmine_log_and_mail_insight.git redmine_log_insight
chown -R <redmine-user>:<redmine-group> redmine_log_insight

No migration is necessary. Restart Redmine (for example touch tmp/restart.txt under Passenger).

To give access to non-admin users, set the two permissions in Administration > Roles and permissions.