Seq — centralized structured logs Collect logs and traces, monitor applications, and hunt bugs — without data leaving your infrastructure
Getting Started - Seq Documentation Getting Started Seq is a telemetry server that runs on a central machine Your application uses a library like Serilog, Microsoft Extensions Logging or OpenTelemetry to send structured events to Seq's HTTP API, which stores them and makes them searchable through Seq's web interface
Search and Analyze Logs and Traces - Seq Documentation Search and Analyze Logs and Traces This page covers everything you need to know in order to understand your systems, find bugs, and spot trends using telemetry data in Seq! The Seq query language serves two closely related, yet distinct, purposes First, it's the foundation of quick and easy event searching: finding structured events that match some criteria Second, it's a language for log
An Overview of Seq An Overview of Seq Seq is a real-time search and analysis server for structured application logs and traces Its carefully designed user interface, JSON event store, and familiar query language make it an efficient platform for detecting and diagnosing issues in complex applications and microservices
Query Syntax - Seq Documentation Query Syntax Read the primer? If you're new to Seq's query language, start with Searching and Analyzing Logs and Spans - it's a complete syntax primer for the busy developer In addition to simple search expressions, Seq provides a SQL-like query syntax for more advanced queries Queries in Seq permit: Tabular queries - select event properties as columns Aggregate operators like count, mean
A Seq query language primer - Structured Blog A Seq query language primer Nicholas Blumhardt 9 July 2020 Seq 2020 1 includes some interesting query language improvements, including object literals, a universal ci case-insensitive text comparison modifier, conditional expressions, and a bunch of new built-ins Now seems like a good time to reintroduce our much-loved query language from the ground, up! Seq collects logs from applications
Search Expression Syntax - Seq Documentation Search Expression Syntax Read the primer? If you're new to Seq's query language, start with Searching and Analyzing Logs and Spans - it's a complete syntax primer for the busy developer The Seq filter bar can be used to find events containing certain text, or having properties with particular values
Getting Logs into Seq Getting Logs into Seq Most languages and frameworks have existing logging libraries or logging APIs The most popular method for logging to Seq is through an application logging library If you are new to Seq, that's a good place to start If your application uses a logging library that has direct support for Seq, such as Serilog, Pino, Microsoft Extensions Logging and many others, check the
Server Command Line - Seq Documentation The Seq server command line can be accessed by passing command arguments to the Docker run command Within the container (or using init scripts) the Seq server executable is called seqsvr Syntax: seqsvr <command> [<args>]
Is Seq an alternative to Application Insights? Is Seq an alternative to Application Insights? Seq and Application Insights both collect application logs in Azure Despite this overlap, Application Insights and Seq have different objectives: Application Insights is a data platform that addresses a wide range of operational monitoring scenarios Seq is focused on the needs of software development teams monitoring and debugging their own apps