Documentation
ErrorNotifier docs for setup, operations, and API integration
Start with a monitor, prove domain ownership, connect alerts, then add browser errors, visitor reports, release metadata, and CI test-run history when the team is ready.
Python connection parity
The Python connection guide covers ERRORNOTIFIER_PROJECT_KEY, ERRORNOTIFIER_BASE_URL, a Flask application sample, a logging-handler sample, and raw requests.post fallback code.
.NET package path
The .NET logging guide links the hosted ErrorNotifier.Extensions.Logging package, explains X-ErrorNotifier-Key, and keeps Python connection parity through the same ERRORNOTIFIER_* environment-variable contract.
NuGet download
Download ErrorNotifier.Extensions.Logging.1.0.2.nupkg and compare the published SHA-256 checksum before mirroring it into an organization feed.
Install path
Most sites start with one public HTTPS monitor, email alerts, and a scheduled worker. Browser SDK setup can prove the domain and add JavaScript issue capture later.
Operational path
Use incidents, status pages, alert delivery logs, and uptime budgets to decide who owns response and when customers get updates.
Developer path
Use public project keys in browsers and server secrets in CI or backend systems. Keep server secrets out of client code and templates.