--- title: Logging with Serilog and Seq | daily.dev description: A step-by-step walkthrough of setting up structured logging in a .NET application using Serilog, paired with Seq as the log collection and querying platform.... canonical: https://daily.dev/posts/logging-with-serilog-and-seq-uiunh5kd1 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Logging with Serilog and Seq | daily.dev og:description: A step-by-step walkthrough of setting up structured logging in a .NET application using Serilog, paired with Seq as the log collection and querying platform.... og:url: https://daily.dev/posts/logging-with-serilog-and-seq-uiunh5kd1 og:image: https://api.daily.dev/og/posts/UiUNh5KD1.png og:image:alt: Logging with Serilog and Seq og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Logging with Serilog and Seq **[Code4IT](https://daily.dev/sources/code4it)** · 9 min read · 0 upvotes · 0 comments ## Summary A step-by-step walkthrough of setting up structured logging in a .NET application using Serilog, paired with Seq as the log collection and querying platform. Covers installing Seq locally, adding the Serilog and Serilog.Sinks.Seq NuGet packages, configuring the logger in Startup.cs, sending logs at different severity levels, setting minimum log levels, enriching logs with shared properties, using structured message templates for queryable fields, and properly logging exceptions using the Error overload that accepts an Exception parameter. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I log an exception properly with Serilog instead of just concatenating the message and stack trace? Use the Error method overload that accepts an Exception as its first parameter, such as _logger.Error(ex, "An error occurred."), rather than building a string with ex.Message and ex.StackTrace as template placeholders. This produces a cleaner log entry with full exception details available in the log detail view instead of crammed into the message text. _daily.dev surfaces practical .NET logging patterns for developers wiring up exception handling with Serilog._ ### How do I connect Serilog to a local Seq instance in a .NET Core application? Install the Serilog and Serilog.Sinks.Seq NuGet packages, then in ConfigureServices create a LoggerConfiguration with .WriteTo.Seq("http://localhost:5341/") and register it as a singleton ILogger. Seq runs locally after installing its .msi, defaulting to localhost:5341, and logs appear immediately once the logger writes to that endpoint. _Developers setting up structured logging pipelines can track Serilog and Seq integration tips on daily.dev._ ### How do I set a minimum log level so Debug and Verbose logs don't appear in production with Serilog? Add .MinimumLevel.Warning() (or another level) to the LoggerConfiguration when building the logger, which filters out any log calls below that severity, leaving only Warning, Error, and Fatal events recorded. Debug and Verbose levels are typically fine for development and staging but excluded in production configurations. _daily.dev helps developers compare logging configuration practices across environments like dev and production._ ## Similar posts on daily.dev - [Serilog Sinks: Console, File, Seq, and More](https://daily.dev/posts/serilog-sinks-console-file-seq-and-more-k2dux4zvo) · We Are .NET · 2 upvotes · 0 comments - [Structured Logging in .NET with Serilog and ClickHouse](https://daily.dev/posts/structured-logging-in-net-with-serilog-and-clickhouse-xwwes1xel) · ClickHouse · 12 upvotes · 1 comments - [Structured Logging Patterns That Actually Survive Production — Daily DevOps & .NET](https://daily.dev/posts/structured-logging-patterns-that-actually-survive-production-daily-devops-net-lphiux5cy) · Daily DevOps & .NET · 6 upvotes · 0 comments - [Beyond Console.WriteLine: Mastering Structured Logging in .NET](https://daily.dev/posts/beyond-console-writeline-mastering-structured-logging-in-net-hgcoz2ses) · ITNEXT · 10 upvotes · 0 comments - [OpenTelemetry Logging .NET: ILogger Integration and Structured Log Export](https://daily.dev/posts/opentelemetry-logging-net-ilogger-integration-and-structured-log-export-5b3h28qfa) · We Are .NET · 1 upvotes · 0 comments --- Tags: [#.net](https://daily.dev/tags/.net), [#logging](https://daily.dev/tags/logging), [#c#](https://daily.dev/tags/c#) [View this post on daily.dev](https://daily.dev/posts/logging-with-serilog-and-seq-uiunh5kd1) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Logging with Serilog and Seq","url":"https://daily.dev/posts/logging-with-serilog-and-seq-uiunh5kd1","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/logging-with-serilog-and-seq-uiunh5kd1"},"datePublished":"2026-10-04T13:05:30.712Z","dateModified":"2026-10-04T13:10:09.297Z","description":"A step-by-step walkthrough of setting up structured logging in a .NET application using Serilog, paired with Seq as the log collection and querying platform....","image":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","thumbnailUrl":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","isAccessibleForFree":true,"articleSection":"Code4IT","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Code4IT","logo":"https://media.daily.dev/image/upload/s--OaaG4G10--/f_auto,q_auto/v1791119049/logos/code4it?_a=BAMAMicg0","url":"https://daily.dev/sources/code4it"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/logging-with-serilog-and-seq-uiunh5kd1","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":".net,logging,c#","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Code4IT","item":"https://daily.dev/sources/code4it"},{"@type":"ListItem","position":3,"name":"Logging with Serilog and Seq"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/logging-with-serilog-and-seq-uiunh5kd1#faq","mainEntity":[{"@type":"Question","name":"How do I log an exception properly with Serilog instead of just concatenating the message and stack trace?","acceptedAnswer":{"@type":"Answer","text":"Use the Error method overload that accepts an Exception as its first parameter, such as _logger.Error(ex, \"An error occurred.\"), rather than building a string with ex.Message and ex.StackTrace as template placeholders. This produces a cleaner log entry with full exception details available in the log detail view instead of crammed into the message text. daily.dev surfaces practical .NET logging patterns for developers wiring up exception handling with Serilog."}},{"@type":"Question","name":"How do I connect Serilog to a local Seq instance in a .NET Core application?","acceptedAnswer":{"@type":"Answer","text":"Install the Serilog and Serilog.Sinks.Seq NuGet packages, then in ConfigureServices create a LoggerConfiguration with .WriteTo.Seq(\"http://localhost:5341/\") and register it as a singleton ILogger. Seq runs locally after installing its .msi, defaulting to localhost:5341, and logs appear immediately once the logger writes to that endpoint. Developers setting up structured logging pipelines can track Serilog and Seq integration tips on daily.dev."}},{"@type":"Question","name":"How do I set a minimum log level so Debug and Verbose logs don't appear in production with Serilog?","acceptedAnswer":{"@type":"Answer","text":"Add .MinimumLevel.Warning() (or another level) to the LoggerConfiguration when building the logger, which filters out any log calls below that severity, leaving only Warning, Error, and Fatal events recorded. Debug and Verbose levels are typically fine for development and staging but excluded in production configurations. daily.dev helps developers compare logging configuration practices across environments like dev and production."}}]} ```