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 to C:\ProgramData\Seq\Logs. This is the case even when varying storage paths are configured, unless explicitly overridden in Seq.json.
Log files are rolled on a per day basis and retained for 30 days.
The clef-tool provides a nice command-line pretty printer for these logs, and can even forward them to another Seq instance for viewing.
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.
To help us respond with the most useful advice, please consider including the following basic information in your support request, along with a description/screenshot of the problem if applicable:
- Operating system version information
- .NET Framework version information from the server
- Server hardware information - particularly RAM/CPU cores
- Copy of the Settings > Diagnostics page from Seq
- Recent log file (see above)
- Browser/version information, if it is a UI issue
- History/frequency of the problem
If you'd rather not post this information in public, an email contact is listed on our support page.
Updated less than a minute ago