Skip to content

docs: Report deletion policy — almost never delete reports#92

Open
NikitaVr wants to merge 2 commits into
mainfrom
knowledge-update/report-deletion-policy-almost-never-delete-reports-1780651947643
Open

docs: Report deletion policy — almost never delete reports#92
NikitaVr wants to merge 2 commits into
mainfrom
knowledge-update/report-deletion-policy-almost-never-delete-reports-1780651947643

Conversation

@NikitaVr

@NikitaVr NikitaVr commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Knowledge Update: Report deletion policy — almost never delete reports

This PR was automatically generated from a knowledge base update.

Changes

  • Reports (concepts/reports.mdx): Added report deletion policy explaining that reports should almost never be deleted, and only for removing accidentally uploaded sensitive information.
  • Metrics (concepts/metrics.mdx): Added context clarifying that the Reports Total metric represents the volume of work to check but is less meaningful than Confirmed Threats Count or Takedowns Count.

Knowledge Entry

Topic: Report deletion policy — almost never delete reports
Added by: nikita@chainpatrol.io
Date: 2026-06-05

Content:

Reports in ChainPatrol should almost never be deleted. The only valid reason to delete a report is to remove sensitive information that should not be stored in a report or was uploaded by accident.

Detection sources producing noise do affect report metrics, but this should be solved by configuring detection sources properly rather than deleting reports.

The reports total metric shows the volume of work we have to check through potential threats, but it is not as meaningful as the Confirmed Threats Count or the Takedowns Count.

Original Message

Add to Knowledge. Reports in ChainPatrol should almost never be deleted, unless it's needed for removing sensitive information that should not be stored in a report or was uploaded on accident.

Things like Detection sources producing noise do affect report metrics, but we should solve that by configuring detection sources properly instead of deleting reports

The reports total metric also just shows volume of work we have to do to check through potential threats, but it is not as meaningful as the Confirmed Threats Count or the Takedowns Count.


Auto-generated by the ChainPatrol Knowledge Agent

@mintlify

mintlify Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
chainpatrol 🔴 Failed Jun 5, 2026, 9:34 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant