demo · v139

Crash Report Inspector

Chrome 139 adds a crash-only filter for Reporting API endpoints. Route crash reports to a dedicated on-call endpoint without flooding it with CSP violations, deprecation notices, and intervention reports. This demo simulates the report stream under both modes.

Report-To header value

Why crash-only matters

Crash endpoints often route directly to on-call paging systems. A single CSP violation or deprecation warning can trigger false-positive alerts and wake engineers at 3 am. The crash-only filter lets you send crashes to PagerDuty or OpsGenie while everything else goes to a quieter analytics endpoint.

Press “Simulate incoming reports” to see the stream.

The header syntax

Reporting-Endpoints: crashes="https://crashes.example/v1",
                     default="https://reports.example/v1"

Report-To: {
  "group": "crashes",
  "max_age": 86400,
  "endpoints": [{"url": "https://crashes.example/v1"}],
  "include_types": ["crash"]
}

The include_types: ["crash"] key (Chrome 139+) restricts this endpoint group to crash reports only. The default group continues to receive everything else.

see also