Search CiviCRM's debug log, stack traces included, however large the file.
Reads the CiviCRM debug log from Administer › Administration Console › Debug Log.
Search the full text of every entry, stack traces included, so you can find the class or file named in a backtrace and not only in the message line. Filter by date range and by severity, and open rotated log files as well as the one currently being written to.
Log files are read as a stream and are never loaded into memory whole, so the page opens immediately whatever the file size. Showing the newest entries reads only the end of the file: on a 269MB log holding 2.4 million entries, the first page costs a couple of block reads.
Log entries are also an APIv4 entity, DebugLogEntry, with the fields id, file, timestamp, severity, message, body and size. It is searchable, so you can build your own SearchKit searches, displays and dashboards over your logs — the bundled viewer is itself just a saved search and a table display.
Requires SearchKit and Afform. Because the records are files rather than database tables, the entity cannot be joined to other entities and does not support groupBy or having.
