Skip to content

docs: cite the Deduplication Workflow Wednesday post in the dedup reference - #46

Merged
mraible merged 1 commit into
mainfrom
docs/dedup-workflow-wednesday-source
Aug 27, 2026
Merged

docs: cite the Deduplication Workflow Wednesday post in the dedup reference#46
mraible merged 1 commit into
mainfrom
docs/dedup-workflow-wednesday-source

Conversation

@mraible

@mraible mraible commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

The Deduplicate worked example (intro-deduplicate-third-party-detections.yaml) implements the same pattern taught in the CrowdStrike Workflow Wednesday post "Taming Noisy Alerts with Deduplication": a cs.hash.sha1 key over detection name + sender + subject, Workflow scope, an 86400-second (24h) period, branch on duplicate, Set Deduplicate Entry Metadata to store the Case ID, and Wait for Deduplicate Entry Metadata on the duplicate path to handle the create-vs-read race.

This adds that post as a corroborating public source in deduplicate-ratelimit.md, alongside the live-tenant console export the example is already built from. Docs-only; markdownlint clean.

…erence

The Deduplicate worked example mirrors the pattern in the CrowdStrike Workflow
Wednesday post 'Taming Noisy Alerts with Deduplication' (sha1 key over detection
name + sender + subject, Workflow scope, 24h period, metadata handoff with a Wait
on the duplicate path). Add it as a corroborating source alongside the live-tenant
console export the example is built from.
@mraible
mraible requested a review from a team August 27, 2026 15:36
@mraible
mraible enabled auto-merge (squash) August 27, 2026 16:26
@mraible
mraible merged commit 9592e5e into main Aug 27, 2026
6 checks passed
@mraible
mraible deleted the docs/dedup-workflow-wednesday-source branch August 30, 2026 19:58
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.

2 participants