ILogger provider

Updated 1 October 2026 · BugsRadar team

Everything your application already logs at Error and above through Microsoft.Extensions.Logging goes to BugsRadar with its message template, properties, scopes and category.

The provider comes with the BugsRadar package: install it and register the client first. Using Serilog, NLog or log4net as the host's logger? Their own packages fit better: Serilog sink, NLog target, log4net appender.

Add the provider

using BugsRadar.Extensions.DependencyInjection;
using BugsRadar.Extensions.Logging;

builder.Services.AddBugsRadar(c => c.ApiKey = "<your project API key>");
builder.Logging.AddBugsRadar();

What arrives

logger.LogError(ex, "Order {OrderId} failed", 42) arrives with the template Order {OrderId} failed and the property OrderId = 42. The minimum level is BugsRadarConfiguration.MinimumLevel, Error by default.

What the message looks like in the chat, how repeats are counted and when errors are bundled: see What you receive. Exceptions you catch yourself go through direct calls.