Critical errors is the second card in Settings. It lists only the things that stop Loghound working: what is failing on the machine right now, plus the last 50 failures that happened and are over. When the card is empty, the installation is healthy.
Before this card, an empty panel had no visible reason. A reader that stopped, a rejected configset or an unreachable Opensolr account each left a trace in a different file. This card gathers them in one place, and it reads nothing from your indexes to do it.
Listed
- The reader stopped, or cannot read one of your log files.
- A whole log file failing to parse: lines read and nothing indexed. One bad line is not an error; a whole file is Loghound silently collecting nothing.
- A configset rejected, or a schema update that failed.
- Your Opensolr account unreachable, or Solr refusing writes.
- A job that died, the beacon collector unable to write, or nowhere left to write on the machine.
- Sign-in unable to work because its files cannot be written.
Never listed
- A single unparsed line, one slow query, a request that was retried and then worked, a warning.
- Happening now entries are measured each time you open the card, and they disappear by themselves the moment the problem clears.
- Recorded entries are failures that are over, such as a job that died. The same failure repeated within an hour updates one entry and shows seen N times, so a failing loop cannot push everything else out.
- Each entry shows when it happened (UTC), what Loghound was doing, and the error the platform or the system returned.
- Everything about this failure is a block you can copy into an issue at github.com/phpcip/loghound/issues. It names the release, PHP, operating system and web server. Every secret the installation holds is removed from it before it is shown.
Clear the recorded failures empties the record of past failures. Anything still broken comes back straight away, because it is measured, not remembered.
For the reader’s own status and the commands that inspect it, see Running it and Troubleshooting.