Seq runs on most modern Windows configurations. Your requirements will depend on the volume of log events you intend to process.
Log processing from busy applications can be an extremely resource-intensive process. Careful consideration of what data your application needs to log at each level can make a big impact on the hardware needed to collect and view events.
The Seq server runs on the .NET Framework 4.6 and better; it is supported on Windows 8+ and Windows Server 2012+.
When selecting an operating system, the most recent possible standard Windows Server SKU is recommended. Windows Server 2012 R2 and above provide significantly better performance than earlier versions.
Seq requires a 64-bit physical or virtual machine. If you're hosting on Microsoft Azure you'll need a full VM (not a Cloud Service or Web App).
For most light workloads - a few events per second, retained 30 days, - a basic machine with a minimum of the following specifications will provide very good performance:
- 2 CPU cores
- 3 GB RAM
- 50 GB storage
(On Microsoft Azure this indicates the A2 tier.)
For busier servers, additional CPU, RAM and storage may be required. As a rule of thumb, 1 GB RAM per 1.5 million retained events is a good starting point. CPU and IO requirements are highly dependent on the nature of the events being logged, so measuring and tuning based on usage will be necessary.
Seq performs best with SSD storage. On cloud VMs with poor I/O performance (e.g. HDDs) ticking Allow buffered writes under Settings > System is recommended.
Seq runs in a single-node configuration, so scaling up or down requires adjustment of these numbers, rather than the addition of machines.
Seq accepts events and serves its web interface via HTTP or HTTPS.
The default installation uses HTTP on port 5341. For production work, opening port 80 or 443 as appropriate is recommended.
Updated less than a minute ago