Already on Seq: errors in Telegram without a new SDK

Updated 1 October 2026 · BugsRadar team

Serilog writes to Seq, the dashboard is good, and nobody is looking at it at 2 a.m. You don't need another SDK in the project; you need the errors that already flow to Seq to also reach a chat. BugsRadar takes CLEF, the format Seq clients speak, so the sink you have is the only client you need.

A second address in the same sink

Add a second WriteTo.Seq with the BugsRadar address, https://api.bugsradar.com/api/v3/clef, the project's key as the API key, and restrictedToMinimumLevel: LogEventLevel.Error. The sink that writes to your Seq server stays as it is. Everything below an error stays on your side, because BugsRadar sends only errors to channels anyway. See CLEF and Seq clients.

What arrives

Error and Fatal events, as one message per error with repeats counted in it. The message template in @mt groups the repeats, so Payment {PaymentId} declined for every payment is one error with a count; the exception in @x gives the type, the inner exceptions and the stack; SourceContext becomes the category, MachineName the host and EnvironmentName the environment. Verbose, Debug, Information and Warning are accepted and dropped.

Batches and limits

A Seq client sends one request per batch, and BugsRadar takes up to 50 requests per minute per project on the Free and Pro plans, up to 1 MB each. A sink restricted to errors stays far below that; when a batch is refused with 429, the client waits for Retry-After and sends it again, as it does with Seq.

Other Seq clients, other languages

Seq clients for other loggers and languages take the same address and add the path themselves. Anything else can post CLEF directly, one JSON object per line, with the key in the X-Seq-ApiKey header: see Other CLEF senders.

When the package is worth it

BugsRadar.Serilog does what the Seq route does and two things more: repeats of an error leave the process as one request with a count, and an error seen by both ILogger and Serilog is sent once. If you can add a package, it is the better sink; if you can't, the Seq route loses nothing that matters at 2 a.m. See Serilog sink.

What it doesn't do

BugsRadar is not a Seq replacement. It keeps no events and has no query page; keep Seq for the investigation and add BugsRadar for the alert.

Where to go next

The configuration is in CLEF and Seq clients; the overview is BugsRadar for Seq clients.