Could there be a way to collect Crash/Intervention reports without collecting Deprecation reports?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 84
- Forks
- 39
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 1
Description
Or any other combination of the above?
I ask because a proxy downstream of my site appears to be adding the Expect-CT header, which is causing my reporting server to be spammed with "Expect-CT is depreciated" depreciation reports. To stop the flood of reports, I have no choice but to stop collecting Depreciation, Intervention and Crash reports - when I only actually want to stop collecting Depreciation reports (or at least stop receiving that one report).
I can't contact the proxy (I don't even know for sure it exists or which of my clients might be using it), and I can't add a filter to the reporting server (it's a third-party service).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is identified in the issue. Start by reviewing the Reporting API behavior for selecting report types, then determine the specification change needed to allow Deprecation reports to be suppressed independently; done means the requested combinations are defined unambiguously.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100