Skip to content
Public demo modeRead-only mock data for demo.errornotifier.com, shop.demo.errornotifier.com, api.demo.errornotifier.com, docs.demo.errornotifier.com, and hooks.demo.errornotifier.com. Placeholder secrets such as ensk_demo_placeholder_do_not_use are fake and cannot write data.
Create a real workspace

Simulated incident story

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

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

Artifacts and source maps

Foundation is implemented with database tables, REST routes, and docs. This page now shows the feed contract, current records, and the next setup action.

API docs

Copyable per-project artifact endpoints

Upload protected build artifacts only from CI or trusted backend automation.

Project: Browser storefront
Secret placeholder: ensk_demo_placeholder_do_not_use

Source-map endpoint: POST https://errornotifier.com/wp-json/errornotifier/v1/artifacts/source-maps
Symbol-file endpoint: POST https://errornotifier.com/wp-json/errornotifier/v1/artifacts/symbol-files
Authorization: Bearer ensk_demo_placeholder_do_not_use
Project scope comes from the server secret; artifact rows should carry release, dist, bundle_url or bundle_path, and SHA-256 response metadata.
1. Build assetsRelease Tied
Keep release and dist values stable across events and source-map uploads.
2. Upload metadataProtected
Send source-map or symbol files with server secrets only.
3. Verify integritySHA 256
Uploaded artifacts return a checksum and status for review.
4. Process laterFoundation
Parser jobs can use the stored artifact record without changing the API contract.

Artifact upload example

curl -X POST https://errornotifier.com/wp-json/errornotifier/v1/artifacts/source-maps \
  -H "Authorization: Bearer ensk_demo_placeholder_do_not_use" \
  -F "release=web-2026.06.07.1" \
  -F "dist=build-417" \
  -F "bundle_url=https://example.com/assets/app.js" \
  -F "file=@dist/app.js.map"
StoredReady
Upload and checksum were accepted into the protected artifact registry.
ProcessingQueued
A parser or symbol-processing job can work from this stored artifact.
ProcessedComplete
The artifact has been processed and is ready for error-context lookup.
DeletedAudit Only
The artifact file is removed or disabled; the row remains useful for audit history.
ProjectReleaseTypeBundleSizeStatusChecksum
Browser storefront2026.05.18.4dist demosource_maphttps://demo.errornotifier.com/assets/app.9e2ad41.js822 KBStoredUpload and checksum were accepted into the protected artifact registry.b522c0b88c5c6ff8...
Public APIapi-2026.05.18.2dist demosymbol_file306 KBArtifact metadata is recorded; review the row details before relying on processing output.4a0382d905a106af...