Expanded payload
Click any result row to open the full event, including every payload field.
Expanded payload
Clicking anywhere on a collapsed row opens its expanded view directly below. The expanded view shows every field the event carries: the canonical ones (severity, event, actor, source, message, dataset) plus every payload.* key your server included.
Anatomy
The expanded row has two parts.
Action bar (top). A row of small ↗ LABEL buttons across the right edge. Each one performs a single action on the focused event. See the dedicated guides for each:
| Button | Guide |
|---|---|
| VIEW PROFILE | Actor profile (only appears when actor starts with player:) |
| EVENTS NEAR | Events near this one |
| COPY JSON | Permalinks and Discord copy |
| PERMALINK | Permalinks and Discord copy |
| COPY DISCORD | Permalinks and Discord copy |
| ADD TO CASE | (Cases module pending. Disabled for now.) |
Payload list (below). A JSON-style key-value list of every field on the event. Top-level keys are the canonical fields (severity, event, actor, etc.) and your custom payload entries appear as payload.<key>.
Each line is clickable
Hover any key:value line and it tints orange. Click it and the value gets added to your search as a filter. The dropped row toggle stops there: clicking inside the expanded view does not collapse it.
The same clickable behaviour applies to all top-level fields (severity, event, actor, source, message, dataset) plus every payload.* key. See Click to filter.
Smart rendering for known shapes
If a payload value matches a known pattern (Steam ID, IP address, URL, etc.), it renders with extra affordances: external links, badges, or in-app buttons. See Smart fields for the full list.
Collapsing
Click the row's header (the timestamp / severity area) to collapse it. The ▾ glyph on the right flips back to ▸.
You can also click another row to expand it: only one row is expanded at a time, so the previous one collapses automatically.
Nested objects
The payload renderer walks into nested objects and arrays, indenting each level. Nested values are read only for the click-to-filter behaviour. You can only filter on top-level fields and on direct payload.<key> entries, because deeper paths are not addressable in SOQL.