EDR Telemetry Statistics
Historical trends in EDR Telemetry visibility across the vendor matrix: which vendors gained coverage, which categories moved, and how contributions landed. Rankings use weighted score deltas from accepted changes — not PR counts.
How these statistics are calculated
Numbers below come from accepted changes in the EDR-Telemetry data/generated dataset on GitHub. The site does not recompute history; it visualizes the published summaries.
Methodology
We measure telemetry changes in the vendor matrix: each accepted update to a vendor’s telemetry status is compared against the previous repository state, scored using the project’s published status model, weighted by the relevant telemetry feature weight, and linked back to the commit or pull request that introduced it.
- Leaderboards rank by net weighted score delta, not activity volume.
- Baselines and zero-delta references are excluded from “improvement” charts.
- Corrections and downgrades appear as negative deltas where applicable.
What this does not measure
These statistics describe changes in user-visible telemetry coverage. They do not measure product quality, prevention capability, detection quality, alert quality, or managed service performance. A higher score or positive delta means broader exposed telemetry, not a “better” product.
New vendor baselines, new categories, renames, documentation-only changes, and corrections are labeled separately so they do not inflate improvement metrics. For the evidence standard behind status values, see the methodology page.
Loading charts and summary data…