nano SIEM
Search Commands

table

Supported in:Self-hosted

Choose which fields appear in the result, in what order, and under what column names.

Use table to choose the fields and column order in your results. You can add aliases for the output columns.

Syntax

... | table <field> [as <alias>] [, <field> [as <alias>] ...]
... | table *
ArgumentDescription
fieldAn OCSF path (src_endpoint.ip), a field computed earlier in the pipeline (eval, rex, stats output), or a quoted name ("Source IP"). Separate fields with commas.
as <alias>Output the field under a new column name. Quote aliases that contain spaces.
*Keep every field.

How it works

  • Fields not in the list are dropped. Columns come back in the order you list them.
  • as <alias> replaces the column: the result has a <alias> column and no column under the original name.
  • Later commands can refer to the alias. The original name is no longer an output column. Use rename when you want to retain other fields as well.
  • A path that no event in the result populates comes back as an empty column, not an error. A name that isn't an OCSF 1.9 path is rejected; see OCSF schema.

Examples

A readable list of failed logons:

class_uid=3002 status_id=2 | table time, user.name, src_endpoint.ip, device.hostname, status_detail

Process launches with their parent command line:

class_uid=1007 | table time, device.hostname, actor.user.name, actor.process.cmd_line, process.cmd_line

Friendly column names for a report (keep table last):

class_uid=4002 http_response.code>=500 | table time as "Time", src_endpoint.ip as "Client", http_request.url.url_string as "URL", http_response.code as "Status"

Aggregated output in a fixed column order:

class_uid=3002 status_id=2 | stats count as failures, dc(src_endpoint.ip) as sources by user.name | table user.name, failures, sources

Rename first when a later command needs the new name:

class_uid=3002 | rename user.name as account | stats count by account | table account, count

Notes

  • table is one of the commands that also run after a nano-side stage (lookup, prevalence, inputlookup, resolve_identity, ai, lateral).
  • fields keeps or removes fields without fixing their order or renaming them.

What's next

  • fields: keep or remove fields
  • rename: rename a field for later commands
  • eval: compute a new field to show
  • sort: order the rows

On this page