Is the Seq process crashing? Are unexpected errors reported in the UI? Seq is normally rock-solid stable, but if something's going wrong this page will help you gather information so that our Support Team can help you out.
Seq writes its own internal error log files in JSON format. On Windows, logs are written to C:\ProgramData\Seq\Logs. In Docker, logs are written to /data/Logs. This is the case even when varying storage paths are configured, unless explicitly overridden in Seq.json.
Log files are hard-limited to 1 GB each, rolled on a per day basis, and retained for 30 days.
The command-line client
seqcli provides a nice command-line pretty printer for these logs (
seqcli print), and can even forward them to another Seq instance for viewing (
seqcli ingest --json).
When an exception is reported either to applications logging to Seq, or to the Seq UI, an error token will be provided. This is a unique (GUID) string that will also be written along with error details into the Seq log file. Including the error from the log along with any support ticket will help us investigate any issues.
Please include the full diagnostic report if possible when contacting the Seq support team.
Updated almost 3 years ago