User Guide
Vertex-Triage User Guide
Vertex-Triage adds new Storm commands and Workflows to manage queues and tasks.
Getting Started
Check with your Admin to enable permissions.
Tasks Workflow
The Tasks Workflow displays at most 1000 tasks. When more tasks match, a warning is displayed; use the
queue, status, priority, assignee, updated since, and search filters to narrow the results.
With the queue set to <all>, the table fills from queues in name order, so refine the filters or choose a
queue to see other tasks.
The updated since filter limits the results to tasks updated since a date picked from the calendar, or
since a relative time typed into the field, such as -7days or -24hours. Press Enter to check a typed
value. Picked dates start at midnight UTC. Tasks without an updated time are matched by their created time.
Leave the field empty to show tasks regardless of when they were updated. Like the other filters, the value
is saved as the default; a relative time stays relative, so -7days always shows the last seven days.
Examples
Create a new queue
Queues can also be created via the dedicated workflow.
> vertex.triage.queue.add alerts --desc "A queue for work items relating to alerts"
proj:project=31b8ade6aeb685ff96c2b33f58aef950
.created = 2026/11/13 16:48:59.926
:created = 2026/11/13 16:48:59.927
:creator = root
:desc = A queue for work items relating to alerts
:name = alerts
:type = vertex.triage
Create a new task within the “alerts” queue that references a risk:alert node
Tasks can also be created from a Node Action in the Research Tool.
> risk:alert#newalerts | vertex.triage.task.add alerts "alert investigation" --assignee visi --yield
proj:ticket=6fb842e19d9e7e3ad5a643d7c86e22fb
.created = 2026/11/13 16:48:59.953
:assignee = visi
:created = 2026/11/13 16:48:59.953
:creator = root
:name = alert investigation
:priority = medium
:project = 31b8ade6aeb685ff96c2b33f58aef950
:status = new
:type = task
:updated = 2026/11/13 16:48:59.953
Create a trigger to add a task when media:news:title is set and contains a keyword
This example creates a new task when :title contains the keyword malware,
and adds it to the malware queue. The title is used to populate the task name.
> trigger.add prop:set --prop media:news:title
--query { +:title~=malware | vertex.triage.task.add malware `triage "{:title}"` }
Added trigger: 9b863072df1ca5bfb0a95e31dbce6e29
> [ media:news=* :title="an article about malware" ]
media:news=36d31c18a342180133dd256333ce3bd5
.created = 2026/11/13 16:48:59.985
:title = an article about malware
> proj:project:name=malware -> proj:ticket
proj:ticket=dbbbedd294126f1898e411628f9ef82c
.created = 2026/11/13 16:48:59.997
:created = 2026/11/13 16:48:59.996
:creator = root
:name = triage "an article about malware"
:priority = medium
:project = 541de7207ff96a6ef9f42d6bae992d58
:status = new
:type = task
:updated = 2026/11/13 16:48:59.996
The task will also have a reference to the inbound node.
> proj:project:name=malware -> proj:ticket -(refs)> *
media:news=36d31c18a342180133dd256333ce3bd5
.created = 2026/11/13 16:48:59.985
:title = an article about malware
Create a cron to check an external system and create a task based on the results
This example calls a placeholder module, and creates tasks in the extsys queue.
A similar ingest routine could be written for calling an HTTP API.
> cron.add --hour +8 {
$mod = $lib.import(somemodule)
$data = $mod.getData()
for $item in $data {
vertex.triage.task.add extsys $item.name --desc $item.details
}
}
WARNING: "--hour" is deprecated and will be removed in v3.0.0.
Created cron job: c965fcb14352eea9415470ad3e341561
Use of meta:source nodes
Vertex-Triage uses a meta:source node and -(seen)> light
weight edges to track created nodes.
> meta:source=62cbf38be08a5fc8933790a68c41d103
meta:source=62cbf38be08a5fc8933790a68c41d103
.created = 2026/11/13 16:48:59.924
:name = vertex-triage