SECOPS

Cloudflare WAF burst to Honeycomb trace pivot

When Cloudflare WAF block events spike past a threshold in a short window, pull the offending request paths and open a scoped Honeycomb trace query.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCloudflare WAF firewall event receivedCloudflareCloudflare
  • LogicCount blocks in rolling window; gate on burst threshold
  • ActionRank top hostnames, paths, and ASNs via Cloudflare GraphQLCloudflareCloudflare
  • ActionBuild scoped Honeycomb trace query for the same windowHoneycomb
  • OutputPost burst summary and trace link to DiscordDiscordDiscord

What it does

Watches Cloudflare WAF firewall events and reacts when blocked requests cluster into a burst (for example, 50+ blocks in five minutes). It correlates the burst to your backend by extracting the targeted hostnames and paths, builds a matching Honeycomb trace query for that same window, and hands the on-call engineer a single Discord message with the attack shape and a clickable trace link.

When to use it

Use it when WAF noise is high and you need the signal that actually reached origin. It turns "WAF is blocking a lot right now" into "here are the three paths under attack and here is the trace view of what slipped through."

How it works

  1. 1Cloudflare emits WAF firewall events; the workflow buffers them per window.
  2. 2A logic step counts blocks in the rolling window and only continues past the burst threshold.
  3. 3An action step queries the Cloudflare GraphQL analytics API to rank the top hostnames, paths, and source ASNs in the burst.
  4. 4An action step builds a Honeycomb trace query filtered to those paths over the same timestamp range and returns a permalink.
  5. 5The output step posts the burst summary plus the Honeycomb link to the secops Discord channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect HoneycombDistributed traces and queries.
  3. 3
    Connect DiscordCommunity channels + voice + bots.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.