Plain-text log files make it difficult to follow an event across services or search reliably for a particular customer request. Seq collects structured logs, where events contain named fields as well as messages, and provides search and analysis over them. It helps developers investigate application behavior using those details. Its event data lives on persistent storage, so capacity, retention and backups matter; sharing one data directory among extra pods is not a supported shortcut to availability.
Current guidance
Datalust’s Kubernetes guide provides a vendor Helm repository and describes the chart as a simplified deployment strategy with assumptions that may need adjustment. It creates a cluster-internal service and persistent storage; external UI or ingestion access is a separate configuration decision.
Seq stores configuration and event data under its data directory and performs substantial disk I/O. The storage guide requires a volume used by one Seq container at a time, and the chart uses a Recreate strategy during upgrades to avoid simultaneous access. Do not increase replicas against one data volume as an improvised high-availability design.
Before adopting or migrating the chart, choose appropriate block storage, capacity, retention and a tested backup procedure. Check whether the PVC is chart-created or supplied through an existing claim: the documented uninstall behavior can delete a chart-owned claim. Rehearse restart and restore with representative events, and validate ingestion credentials and UI access separately. Retain the previous backup across an application upgrade; a successful Helm rollback is not proof that an upgraded data directory can be read by an older Seq version.
Historical upstream link check · 2026-10-09
The recorded upstream address redirects to https://datalust.co/ and returned HTTP 200 on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Seq is the easiest way for development teams to capture, search and visualize structured log events! Seq creates the visibility you need to quickly identify and diagnose problems in complex applications and microservices. Empower your team to build better software by centralizing, searching, and alerting on structured application logs.
Seq has great support for .NET libraries including Serilog, ASP.NET Core, and NLog, as well as Node.js, Python, and others. Developers in thousands of companies rely on Seq every day.
Important note: The 2.x versions of the Seq App packages require Seq 3.3 or later. For earlier Seq versions, install packages from the Seq Apps 1.x series.
Currently, in this repository you’ll find:
- ✔ Email+ – send log events as HTML email messages when they arrive
- ✔ File Archive – copy incoming log events into a set of rolling text files
- ✔ First, of Type – raise an event the first time a new event type is seen
- ✔ Replication – forward incoming events to another Seq server
- ✔ Thresholds – raise an event if the frequency of matched events exceeds a threshold
Works with your stack
Seq collects data over HTTP, while your applications use the best available structured logging APIs for your platform. The simple Windows installer and plug-ins from NuGet or NPM make getting started quick and friction-free.
Seq is a web application hosted on your infrastructure, so you retain complete control over your own data.
✓ Rich Event Data: Structured logging adds context to errors and application events. Quickly zoom-in to find related events by filtering on properties, or use the same technique to exclude noise and see only what is relevant to a line of exploration.
Support for message templates seamlessly fuses text and structured data when used with compatible logging libraries.
✓ Intuitive Filtering: Use SQL expression syntax or familiar C#/JavaScript-style operators including ==, !=, <, <= and so-on. Built-in functions include fundamentals like StartsWith(), EndsWith(), IndexOf() and Contains().
Full-text search and /regular expressions/ are supported, too: just type free text into the filter bar and Seq will find it in log messages and stack traces.
✓ Save and Share Filters: Signals are saved filters that can be applied with one click. Easily view the intersection of two or more filters, like Errors and Production to view only the logs you’re interested in.
Signals and queries are shared across your team so everyone can tune in.
✓ Beautiful Dashboards: Build rich dashboards to keep an eye on your application. Watch error rates, track latencies or visualize business performance using structured data from your application log events.
Don’t wait for users to report problems: set alerts on dashboard data to notify you when values are outside their expected ranges.
✓ Integrate and Notify: Tail events matching a filter in real-time, or use a pre-built integration to send events to an issue tracker, Slack or HipChat.
Extend Seq to react to events using C#, or modify one of the many examples available on GitHub.
A comprehensive HTTP API client makes it easy to query data from your own applications.
✓ Analyze and Chart with SQL: SQL queries with grouping, aggregation, and time-slicing let you dig deeper into system behavior and performance.
Property-aware CSV export makes it easy to take the analysis further with Excel and industry-standard business intelligence tools.
Sources & further reading
Spotted something that needs another look?
Help improve this page →