.NET logging provider
ErrorNotifier.Extensions.Logging adds a non-blocking ILogger provider for ASP.NET Core, console apps, and worker services.
- Log calls enqueue to a bounded System.Threading.Channels queue and return immediately
- BackgroundService batching sends JSON through IHttpClientFactory instead of making per-log network calls
- Full queues drop oldest entries to protect the host application under error spikes
- Transient HTTP failures retry with exponential backoff and jitter before local fallback files are written
- The default hosted endpoint is https://errornotifier.com/api/log, and Enterprise teams can override it to WordPress or direct MySQL ingestion
Install and configure
dotnet add package ErrorNotifier.Extensions.Logging
builder.Logging.AddErrorNotifier();
{
"ErrorNotifier": {
"ApiKey": "ensk_xxx",
"Endpoint": "https://errornotifier.com/api/log",
"BatchSize": 100,
"QueueSize": 10000,
"FlushInterval": "00:00:05",
"MinimumLogLevel": "Warning"
}
}Package download
Use the dedicated NuGet package page for the current ErrorNotifier.Extensions.Logging package file, checksum, and install commands.
Implementation guide
The .NET logging docs cover endpoint override, batching, retries, fallback files, and backend ingestion choices.
Read .NET logging guidePublic demo
Review the real product screens with read-only mock data
Open the demo workspace to inspect monitors, incidents, domains, alert channels, status pages, projects, issues, automated test runs, releases, artifacts, audit history, and umbrella reports without creating an account.