Read the error digest
This task is for administrators doing the daily log check. At the end you know whether anything new is wrong. The digest groups and counts the distinct errors and warnings of the last 24 hours of each kernel log (Error digest and log health).
Contents
Before you start
setup/logs(see Give log access without admin rights).
Steps
- Setup > Log files, then Error digest (
/setup/logsdigest). - Read each log's table, most frequent first: the normalized message, count, most severe level, last seen.
- Groups you accepted earlier are hidden; Show known messages lists them.
- For a group you do not recognize, open its link: the log filtered to it. Open a line to see the whole request and the audit records of the same minute.
- For another window:
/setup/logsdigest/(hours)/72(1 to 168 hours); for one log:/setup/logsdigest/error.
Deciding what a group means
| Group | Action |
|---|---|
| New since yesterday, from a deploy | check with the developer of the change; Broken deploy rollback if it hurts visitors |
| A known harmless message (an old extension's notice) | Mark as known and record why |
| Growing quickly | find the cause before the log fills the disk |
| "Not found requests (404)" grouped by reason | broken links: fix links or add URL aliases |
| "Security (request classifier)" | Review the security log weekly; now, if injections got a 200 |
For a developer ticket, use Copy permalink on the filtered view: the link reproduces the filter.
Related pages
- Check log health
- Find an error by its reference
- The log viewer
- Log viewer feature
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.