Seq is a log server that runs on a Windows server or Docker container. Applications send structured events to Seq over HTTPS using a logging framework like Serilog. Seq displays the events and makes them searchable. Questions about using or configuring Seq itself, or configuring applications and logging frameworks to use it, should have this tag.
Seq is a self-hosted platform for application diagnostics and monitoring.
Seq is a web application with a browser-based UI. It is distributed as an MSI for Windows and as a Linux-based image for Docker.
Applications use Seq for:
- centralizing application logs so that they don't have to be retrieved from individual machines,
- managing JSON-formatted structured logs, so that logs can be searched and analyzed without pre-processing using regular expressions,
- analyzing and charting structured logs to find patterns and anomalies, and
- integrating structured log data into other systems, for example alerting through email, Slack or Microsoft Teams.
The Seq documentation is the primary source of usage information for Seq. Seq bugs and feature requests are tracked on GitHub.
Plug-ins for individual logging frameworks, such as the Serilog sink for Seq, the NLog target for Seq, and Pino stream for Seq generally have their own README, issue tracker, and other documentation.