Result rows
What each column means on a collapsed event row in the Logs result list.
Result rows
Every matching event renders as one row in the result list. Read left to right:
| Column | Example | What it is |
|---|---|---|
| Timestamp | 05-19 07:42:08 | Month-day and clock time in UTC. Hover for the full ISO timestamp including year and milliseconds. |
| Severity badge | WARN | Coloured chip: trace / debug (grey), info (slate), warn (amber), error (red), fatal (magenta). |
| Event | chat_rate_limit_hit | The short event name your server sent. |
| Message | CharlesSmith hit chat rate limit (5 msg / 10s) | The human-readable summary. |
| Actor | player:CharlesSmith | Who or what produced the event. |
| Expand glyph | ▸ | Click anywhere on the row to open the full payload. |
What is clickable
Event name and actor are buttons. Click them to add event:"name" or actor:"value" to your current search, without expanding the row.
The rest of the row is one large clickable area that toggles the expanded view. See Expanded payload.
Required fields
These three fields are guaranteed to be present on every event:
- Severity (defaults to
infoif your server did not send one) - Event (the short identifier)
- Message (the human-readable summary)
If your server sends an event without message, the ingest API rejects it. See Sending events for the full contract.
Sort order
Results are always sorted newest first (descending by timestamp). The Load more button at the bottom of the list fetches the next 100 older events.
Hovering for full precision
The timestamp column is intentionally compact (no year, no millisecond). For investigations where the year matters or you need precision below the second, hover the timestamp cell. A tooltip pops up with the full ISO string.
What is not on the row
The dataset, source, and the full payload are hidden by default to keep rows scannable. Click a row to open them in the expanded view, or use the facets sidebar to see top values across the visible page.