funnel
Count how many entities reach each step of an ordered process, and where the rest drop off.
Use funnel to count how many users, hosts, or IPs reach each step of an ordered process within a time window. You can inspect where entities stop progressing.
Syntax
Bracket form:
... | funnel by <field>[, <field> ...] [window=<duration>] [<condition 1>] [<condition 2>] ... [window=<duration>]Named-step form:
... | funnel by <field>[, <field> ...] window=<duration> step1=(<condition>) step2=(<condition>) ...| Argument | Default | Description |
|---|---|---|
by | required | Fields that identify the entity. |
window | 1h in bracket form; required in named-step form | Time allowed to go from the first step to the last. maxspan= is an alias. In bracket form it may come before or after the conditions. |
[condition] | at least one | A filter in square brackets, in where syntax. |
stepN=(condition) | — | Named-step form. A quoted string (step1="text") is a keyword search. |
Output fields
One row per step, in step order:
| Field | Description |
|---|---|
funnel_level | Step number, starting at 1 |
step_name | step1, step2, … |
count | Entities that reached this step |
dropper_count | Entities whose furthest step is this one. On the last step this is the number that completed the funnel. |
dropper_median_idle_s | For those entities, the median time in seconds between their first and last event in the search |
dropper_top_attrs | Most common values among those entities, taken from each entity's latest event (process.name, src_endpoint.hostname, dst_endpoint.hostname, dst_endpoint.ip, dst_endpoint.port, user.name, activity_name), each with field, value, count and pct |
How it works
- Steps must happen in order, within
windowof the entity's first step. - The base search limits which events are considered. Filter it to the classes your steps need.
- The result is a summary table. Later commands can use
funnel_level,step_name,count,dropper_count, anddropper_median_idle_s. funnelcan't be used in dashboard panels.
Examples
How many accounts that failed to log on later succeeded within 30 minutes:
class_uid=3002 | funnel by user.name window=30m [status_id=2] [status_id=1]The same in named-step form:
class_uid=3002 | funnel by user.name window=30m step1=(status_id=2) step2=(status_id=1)Execution chain on endpoints: PowerShell starts, writes a file, then connects out:
metadata.log_source=windows_sysmon | funnel by device.hostname window=1h [class_uid=1007 process.name="powershell.exe"] [class_uid=1001 actor.process.name="powershell.exe"] [class_uid=4001 actor.process.name="powershell.exe"]Web clients that requested a login page, then posted to it, then reached an admin path:
class_uid=4002 | funnel by src_endpoint.ip window=15m [http_request.url.path="/login"] [http_request.http_method="POST" http_request.url.path="/login"] [http_request.url.path=/^\/admin/]Cloud principals that listed, then read, then deleted (default 1h window):
metadata.log_source=aws_cloudtrail | funnel by actor.user.name [api.operation=/^List/] [api.operation=/^Get/] [api.operation=/^Delete/]What's next
- sequence: list each entity that completed every step
- transaction: group events by key
- stats: aggregate counts without ordering