diff --git a/frontend/index.html b/frontend/index.html index 667939c..62664d0 100644 --- a/frontend/index.html +++ b/frontend/index.html @@ -273,15 +273,30 @@ function renderIngest() {
Loading…
Estimate events and GB eliminated by dropping a source + event type combination.
+Before writing an SDL exclusion filter, use this to see how many events and GB it would remove.
+What it does: Runs a live PowerQuery against your data lake to count how many events match a source and/or event type, then projects that number into estimated GB and monthly cost savings.
+When to use it: You've spotted a noisy source in the Top Sources table above (e.g. a source sending millions of low-value events). Enter it here to quantify how much ingest you'd save by filtering it out before committing the change in the SentinelOne console.
+Source name: Paste the exact value from the dataSource.name column in the Top Sources table — e.g. ActivityFeed.
Event type: Optional. Narrow the filter to a specific event category (e.g. dns, heartbeat). Leave blank to simulate dropping the entire source.
GB estimate: Based on 0.5 GB per million events — adjust in code if your actual ratio differs.
+⚠ This is a read-only simulation — no filters are created or applied automatically. Use the results to inform an exclusion filter you create manually in the SentinelOne console.
+