👁 Image
Serilog.Sinks.SentrySDK 1.0.7.2

Serilog.Sinks.SentrySDK

A Serilog sink for Sentry that simplifies error and log management in your applications. It builds on the Sentry .NET SDK and official Serilog integration.

Based on serilog-contrib/serilog-sinks-sentry

Project status

👁 .NET Core Test
👁 .NET Core CI
👁 codecov
👁 GitHub Release

👁 NuGet Serilog.Sinks.SentrySDK
👁 NuGet Serilog.Sinks.SentrySDK downloads
👁 NuGet Serilog.Sinks.SentrySDK.AspNetCore
👁 NuGet Serilog.Sinks.SentrySDK.AspNetCore downloads

Available packages

Release 1.0.7.2 on NuGet aligns with GitHub tags such as v1.0.7.2. GitHub Releases carry the changelog and attached .nupkg assets.

Prefer the main ids unless you want a single target framework per NuGet package id.

Installation

Core sink:

dotnet add package Serilog.Sinks.SentrySDK

Install-Package Serilog.Sinks.SentrySDK

ASP.NET Core companion (user/request context in logs):

dotnet add package Serilog.Sinks.SentrySDK.AspNetCore

Install-Package Serilog.Sinks.SentrySDK.AspNetCore

Alternate ids (single TFM per package): Serilog.Sinks.SentrySDK.6, Serilog.Sinks.SentrySDK.10, and matching AspNetCore ids — see Available packages.

This stack references the Sentry NuGet package (6.3.2), the same major line as Sentry for .NET. For DSN, SendDefaultPii, and debug options, see the Quick Start. Initialize as early as possible so startup failures are reported. This sink calls SentrySdk.Init when you configure WriteTo.Sentry with a DSN; avoid a second SentrySdk.Init in the same process unless you deliberately use one initialization path.

Set a valid Sentry DSN in appsettings.json or in code. Without a DSN, the sink throws when the DSN argument is empty. Demos show JSON and programmatic configuration.

Getting started

Add the sink so logs are sent to Sentry. You can use Serilog.Settings.Configuration with JSON:

{
 "Serilog": {
 "Using": [ "Serilog.Sinks.SentrySDK" ],
 "MinimumLevel": "Debug",
 "WriteTo": [
 {
 "Name": "Sentry",
 "Args": {
 "dsn": "YOUR_SENTRY_DSN",
 "sendDefaultPii": true,
 "environment": "Development",
 "release": "1.0.7.2",
 "attachStacktrace": true,
 "tracesSampleRate": 1.0
 }
 }
 ],
 "Enrich": [ "FromLogContext", "WithMachineName", "WithThreadId" ],
 "Properties": {
 "Application": "Sample"
 }
 }
}

var configuration = new ConfigurationBuilder()
 .SetBasePath(Directory.GetCurrentDirectory())
 .AddJsonFile("appsettings.json")
 .Build();

var log = new LoggerConfiguration()
 .ReadFrom.Configuration(configuration)
 .Enrich.FromLogContext()
 .CreateLogger();

log.Error("This error goes to Sentry.");

Optional configureSentryOptions and beforeSend on WriteTo.Sentry map to init-time SentryOptions and a chained SetBeforeSend. A fuller argument list and examples are in the repository README — Getting Started.

Data scrubbing

Use SetBeforeSend / SetBeforeSendTransaction on SentryOptions for client-side scrubbing; see Scrubbing sensitive data. Prefer the sink’s optional beforeSend callback for event filtering; use configureSentryOptions for other flags (for example EnableLogs, EnableMetrics) and do not call SetBeforeSend inside that callback, because the sink registers its own SetBeforeSend chain. You can still use Serilog filters and enrichers to limit what reaches the sink.

Capturing HttpContext (ASP.NET Core)

Install Serilog.Sinks.SentrySDK.AspNetCore, then extend the logger:

var log = new LoggerConfiguration()
 .WriteTo.Sentry("YOUR_SENTRY_DSN")
 .Enrich.FromLogContext()
 .Destructure.With<HttpContextDestructingPolicy>()
 .Filter.ByExcluding(e => e.Exception?.CheckIfCaptured() == true)
 .CreateLogger();

Register middleware (for example in Startup / pipeline setup):

app.AddSentryContext();

Full snippets, including older Startup.cs examples, are in the repository README — Capturing HttpContext.

Sentry SDK options vs this sink

This package aligns with Sentry .NET 6.3.2. The repository README maps SentryOptions properties and methods to WriteTo.Sentry parameters (large tables): Sentry SDK and Mapping to WriteTo.Sentry.

Further reading: Data Management, Structured logs, Migration guide.

Demos, build, contributing

• Demos: demos/README.md on GitHub
• Solution and local build/test commands: README — Build, run tests, and coverage
• CONTRIBUTING.md

Full documentation (CI, publishing, formatting): README.md on GitHub.