Documentation

Noise rules

We block common noise before it reaches you. You decide about the rest. A noise rule recognizes reports that are not yours to fix, such as scripts a browser extension injects, and keeps them out of your issue list and your notifications. Nothing is dropped: every filtered report is stored like any other and stays one click away.

We maintain the rules and test each one against sample reports: some it must match and some it must leave alone. The rules apply to every organization, and this page lists every rule and whether it is on. You can't turn a rule off for your apps yet. If a rule hides something you need, tell us: have your coding agent send it with submit_feedback over MCP. Until then, Show filtered in the web app and include_filtered over MCP bring the filtered reports back.

The rules

Rule Filters State
Browser extension CSP, integrity, COEP and deprecation reports caused by a script, style or request a browser extension injected On
Cloudflare Speed Brain prefetch Network errors: a 503 a Cloudflare edge answered in under 50 ms to a link prefetch On
Injected script calling AWS API Gateway CSP violations for requests to an AWS API Gateway default host (*.execute-api.<region>.amazonaws.com) Off
Bot or crawler Reports of every type from a bot, crawler or automated tool such as Lighthouse Off

A rule that is off filters nothing. A rule we turn on or change applies to new reports. When we change a rule, we may also reclassify the reports of the last 30 days, so reports it filtered can return to your lists and older reports can become filtered.

What happens to filtered reports

  • They are stored and grouped like any other report. A filtered report joins its issue, keeps its release and stays as long as your other reports, so the issue's history and per-day counts stay complete.
  • They never notify. AppSignal, webhooks and Google Chat receive no filtered report.
  • An issue made only of filtered reports is hidden. It leaves the default Issues list and carries a Filtered badge when you show it.
  • An issue with some filtered reports stays in the list. Its page names the rules that filtered reports, with how many each one filtered, and says how many of its reports were filtered.
  • They leave triage and releases alone. A filtered report never reopens a resolved issue, never opens a regression issue and never moves an issue's release. An issue made only of filtered reports doesn't count as new in a release. Once a report no rule filters arrives, the issue shows, notifies and takes that report's release as usual.
  • They count toward your plan. Like every report you receive, they count toward your monthly report volume.

See what was filtered

In the web app:

  • On the Issues list, the filter reads Hiding 3 filtered, naming how many filtered issues match your other filters. Pick Show filtered to list them; the filter then reads Showing 3 filtered.
  • On the Reports list, pick Show filtered.
  • An issue's own reports list always includes its filtered reports.

Over the MCP server, your coding agent sees the same and can tell why a report was filtered:

  • list_issues, list_reports and count_reports leave filtered issues and reports out unless include_filtered is true. list_reports with an issue_id includes them.
  • Every issue carries filtered_reports_count. get_issue adds filtered_by, one entry per rule with the fields rule, name, docs_url and count.
  • Every report carries noise_rule, with the key, name and docs_url of the rule that filtered it, or null. Pass the docs_url to get_documentation to read the rule's page.
Something filtered that you need?: Every rule page says what the rule can hide besides noise. If a rule filters reports you need, have your agent tell us with submit_feedback, naming the report.

Next steps

  • Triage Issues — Decide about the rest: states, assignees and notes
  • MCP Server — Let your coding agent triage what is left