Documentation
DocumentationDiscussions
These docs are for v2021.3. Click to read the latest docs for v2024.1.

Built-in Properties

Search expressions and queries can make use of system-provided data.

All Seq events expose a set of built-in properties that are distinguished by the @ symbol in their name:

PropertyDescriptionExample ContentsUsage
@ArrivedAn integer indicating the order in which the event arrived at the Seq server12344@Arrived <= Arrived('event-d8ce...0000')
@DataThe internal representation of the event as a single structured object.{ "@t": ... }Contains(ToJson(@Data), 'coffee')
@EventTypeA hash of the message template that was used to generate the event0x5432a8ff@EventType <> 0x5432a8ff
@ExceptionThe exception associated with the event if any, as a stringSystem.InvalidOp...@Exception like '%zero%'
@IdThe event's unique id in Seqevent-d8ce...0000@Id = 'event-d8ce...0000'
@LevelThe logging level of the event, as a stringWarning@Level <> 'Warning'
@MessageThe text message associated with the eventFailed to open file...@RenderedMessage like 'Failed%'
@MessageTemplateThe message template used to generate the eventLogged in {Username}@MessageTemplate = 'Logged in {Username}'
@PropertiesA dictionary with all properties associated with the event (Seq 3.1){"Name": "alice.example", "ThreadId": 10}@Properties['some irregular identifier']
@TimestampThe UTC timestamp associated with the event2015-02-28T13:56:20.293Z@Timestamp > DateTime('2015-01-13 06:00Z')

👍

Quick filter shortcuts

Many queries listed here are provided as one-click shortcuts via the row of blue links beneath the message text in an expanded log event - Id, Level, Type and so-on.