Simulated incident story

This demo data is read-only and follows one deploy from failing tests to recovery.

Simulated

Bad deployStorefront release 2026.05-demo shipped with a checkout regression.
Failed CI/test runGitHub Actions posted a failed unit test run with two checkout failures.
Latency spikeAPI checks degraded while checkout health checks started returning errors.
Confirmed incidentErrorNotifier opened a critical incident after repeated external failures.
Alert routedEmail, Slack, and a signed automation webhook received delivery records.
ResolutionThe deploy was rolled back, recovery was confirmed, and the report budget was updated.

Public setup wizard

ErrorNotifier setup instructions for humans and AI agents

This page is intentionally public so an AI coding agent can open the URL, read the steps, and install monitoring on a site without needing your ErrorNotifier login. Logged-in users see their browser project key; visitors see the seeded demo/test key named enpk_your_public_project_key. Public examples use the obvious demo server-secret placeholder ensk_demo_placeholder_do_not_use until a real workspace creates its own secret.

1URLhttps://example.com/health

2Expected status200 OK

3Keyword checkcontains "ok"

4Alert channelops@example.com

5Workerwp errornotifier run-checks

Browser SDK keyFilled In

Use the project key shown below for browser error capture and domain proof.

Server secretNever Public

Server-side releases, deploys, artifacts, and automated tests need a secret key created inside App > Projects.

REST endpointReady

Use the WordPress REST namespace at https://errornotifier.com/wp-json/errornotifier/v1.

Privacy matchScript Enforced

The SDK only sends the page detail selected in the generated snippet. The app warns when a manually installed script and domain settings disagree.

Generated manual setup output

Affected setup output updates from the choices on the left.

Script Enforced

Browser SDK snippet

<script src="https://errornotifier.com/wp-content/plugins/errornotifier-core/assets/js/errornotifier-sdk.js"></script>
<script>
ErrorNotifier.init({
  projectKey: "enpk_your_public_project_key",
  endpoint: "https://errornotifier.com/wp-json/errornotifier/v1/store",
  feedbackEndpoint: "https://errornotifier.com/wp-json/errornotifier/v1/feedback",
  verificationEndpoint: "https://errornotifier.com/wp-json/errornotifier/v1/sdk-verify",
  environment: "production",
  reportBug: true,
  showReportBugButton: true,
  // accountCode: "acct_current_user_code",
  basicStats: true,
  pageStatsDetail: "path"
});
</script>

WordPress plugin setup link

Open this on the client WordPress site after the ErrorNotifier WordPress SDK plugin is installed. It carries the public project key and endpoint settings; the client site creates its own private diagnostics token.

https://example.com/wp-admin/options-general.php?page=errornotifier-wordpress-sdk&en_project_key=enpk_your_public_project_key&en_endpoint=https://errornotifier.com/wp-json/errornotifier/v1/store&en_script_src=https://errornotifier.com/wp-content/plugins/errornotifier-core/assets/js/errornotifier-sdk.js&en_environment=production&en_bug_button=default&en_page_stats=path&en_health_report=1&en_health_footer=1&en_health_slug=health-report

Visual Studio client settings

Use this in appsettings or another client-rendered configuration source for browser-side error capture. Server secrets stay in ErrorNotifier App > Projects and are not included here.

{
    "ErrorNotifier": {
        "PublicProjectKey": "enpk_your_public_project_key",
        "StoreEndpoint": "https://errornotifier.com/wp-json/errornotifier/v1/store",
        "FeedbackEndpoint": "https://errornotifier.com/wp-json/errornotifier/v1/feedback",
        "VerificationEndpoint": "https://errornotifier.com/wp-json/errornotifier/v1/sdk-verify",
        "Environment": "production",
        "ReportBug": true,
        "ShowReportBugButton": true,
        "BasicStats": true,
        "PageStatsDetail": "path"
    }
}

WordPress plugin

Agent task brief

.NET and CI example

Project key for browser pages: enpk_your_public_project_key
Authenticated account placeholder: acct_current_user_code
Server secret placeholder: ensk_demo_placeholder_do_not_use

curl -X POST "https://errornotifier.com/wp-json/errornotifier/v1/test-runs" \
  -H "Authorization: Bearer ensk_demo_placeholder_do_not_use" \
  -H "Content-Type: application/json" \
  -d "{\"run_uid\":\"dotnet-ci-1\",\"provider\":\"dotnet\",\"suite_name\":\"unit\",\"status\":\"passed\",\"total_tests\":42,\"passed_tests\":42,\"failed_tests\":0}"

Manual monitor checklist

Open App > Monitors and add the production HTTPS URL.
Choose the expected HTTP status and optional keyword check.
Open App > Domains to confirm SDK or DNS proof.
Open App > Alerts and add email, Slack, or webhook destinations.
Run a manual check from the Monitors table.