Smart fields
Recognised payload value shapes get badges and links automatically.
Smart fields
When you open an event, certain payload values get extra rendering instead of plain text. The list is intentionally small to keep noise down: only shapes that are unambiguous and useful at a glance.
What is recognised
Steam IDs. Both forms work:
steam:11000010abc1234(prefixed)- Bare 17-digit numbers, but ONLY when the key hints at a Steam ID. Keys ending in
.steam_id,.steamid, or namedsteam_id/steamidtrigger the detection. A random 17-digit number elsewhere stays plain.
A detected Steam ID renders as a small dotted-underline link with a ↗ glyph. Click to open the Steam community profile in a new tab.
Discord IDs. The form discord:<17-19 digit ID> gets a small DISCORD badge next to the value. There is no public profile page for arbitrary Discord IDs, so this is for visual recognition only. When staff tools land, this will turn into a deep link to the internal profile page.
IPv4 addresses. Strings matching N.N.N.N get a small IP badge prefix. This makes IP addresses jump out from a wall of unrelated numbers without sending you to an external service.
URLs. Any string starting with http:// or https:// renders as an external link with the same dotted-underline + ↗ treatment as Steam IDs.
What is NOT recognised
These deliberately do not get smart treatment to avoid false positives:
- Bare 17-digit numbers without a Steam-hinting key. Could be a transaction ID, a Steam ID, or a random hash. Without context we cannot tell.
player:<name>actors. These no longer auto-navigate to the player profile. Use the explicit↗ VIEW PROFILEbutton in the expanded row's action bar instead. See Actor profile.- Email addresses. No external link makes sense by default.
- UUIDs. Used for everything from event IDs to internal references. Linking them anywhere would be guessing.
If you want a value to be recognised that currently is not, ping support with the exact shape and what you would expect to happen on click.
Click behaviour
Clicks on smart values do NOT trigger the surrounding "click to filter" behaviour of the row. The link wins. This is intentional: navigating to a Steam profile is a different intent from filtering your search.
If you want to filter on the value as well, click any OTHER part of the line (the key, or the colon, or whitespace). Or just type the filter manually.
A note on safety
Smart fields render external URLs without normalisation. The standard rel="noopener noreferrer" is applied to every external link so the destination page cannot manipulate the dashboard window. Treat unknown URLs in logs the same way you would treat any unknown URL: hover before clicking.