Log Schema Reference

LogSchema fields

  • version (0,required): The version of the log schema. This field should be set to zero (0). Its purpose is to allow backwards compatibility with future versions of the log schema.

  • fields ([]FieldSchema, required): The fields in each Log Event.

  • parser (ParserSpec): Define a parser that will convert non-JSON logs to JSON.


version: 0
delimiter: ','
- name: action
type: string
required: true
- name: time
type: timestamp
timeFormat: unix


A ParserSpec specifies a parser to use to convert non-JSON input to JSON. Only one of the following fields can be specified:

  • fastmatch (FastmatchParser{}): Use fastmatch parser

  • regex (RegexParser{}): Use regex parser

  • csv (CSVParser{}): Use csv parser

Parser fastmatch fields

  • match ([]string, required, non-empty): One or more patterns to match log lines against.

  • emptyValues ([]string): Values to consider as null.

  • expandFields (map[string]string): Additional fields to be injected by expanding text templates.

  • trimSpace (bool): Trim space surrounding each value

Parser regex fields

  • match ([]string, required, non-empty): A pattern to match log lines against (can be split it into parts for documentation purposes).

  • patternDefinitions (map[string]string): Additional named patterns to use in match pattern.

  • emptyValues ([]string): Values to consider as null.

  • expandFields (map[string]string): Additional fields to be injected by expanding text templates.

  • trimSpace (bool): Trim space surrounding each value

Parser csv

  • delimiter (string, required, non-empty): A character to use as field delimiter.

  • hasHeader (bool): Use first row to derive column names (unless columns is set also in which case the header is just skipped).

  • columns ([]string, required(without hasHeader), non-empty): Names for each column in the CSV file. If not set, the first row is used as a header.

  • emptyValues ([]string): Values to consider as null.

  • trimSpace (bool): Trim space surrounding each value

  • expandFields (map[string]string): Additional fields to be injected by expanding text templates.


A FieldSchema defines a field and its value. The field is defined by:

  • name (String,required): The name of the field.

  • required (Boolean): If the field is required or not.

  • description (String): Some text documenting the field.

And its value is defined using the fields of a ValueSchema.


A ValueSchema defines a value and how it should be processed. Each ValueSchema has a type field that can be of the following values:

Value Type



A string value


A 32-bit integer number in the range -2147483648, 2147483647


A 16-bit integer number in the range -32768, 32767


A 64-bit integer number in the range -9223372036854775808, 9223372036854775807


A 64-bit floating point number


A boolean value true / false


A timestamp value


A JSON array where each element is of the same type


A JSON object of known keys


Any valid JSON value (JSON object, array, number, string, boolean)

The fields of a ValueSchema depend on the value of the type field.






fields (required)


An array of FieldSpec objects describing the fields of the object.


element (required)


A ValueSchema describing the elements of an array.


timeFormat (required)


The format to use for parsing the timestamp. (see Timestamps)




A flag to tell Panther to use this timestamp as the Log Event Timestamp.




Tells Panther to extract indicators from this value (see Indicators)


Timestamps are defined by setting the type field to timestamp and specifying the timestamp format using the timeFormat field. Timestamp formats can be either one of the built-in timestamp formats:

  • rfc3339 The most common timestamp format.

  • unix Timestamp expressed in seconds since UNIX epoch time. It can handle fractions of seconds as a decimal part.

  • unix_ms Timestamp expressed in milliseconds since UNIX epoch time.

  • unix_us Timestamp expressed in microseconds since UNIX epoch time.

  • unix_ns Timestamp expressed in nanoseconds since UNIX epoch time.

or you can define a custom format by using strftime notation. For example:

# The field is a timestmap using a custom timestamp format like "2020-09-14 14:29:21"
- name: ts
type: timestamp
timeFormat: "%Y-%m-%d %H:%M:%S" # note the quotes required for proper YAML syntax

Timestamp values can also be marked with isEventTime: true to tell Panther that it should use this timestamp as the p_event_time field. It is possible to set isEventTime on multiple fields. This covers the cases where some logs have optional or mutually exclusive fields holding event time information. Since there can only be a single p_event_time for every Log Event, the priority is defined using the order of fields in the schema.


Values of string type can be used as indicators. To mark a field as an indicator you must set the indicators field to an array of indicator scanner names. This will instruct Panther to parse the string and store any indicator values it finds to the relevant field. For example:

# Will scan the value as IP address and store it to `p_any_ip_addresses`
- name: remote_ip
type: string
indicators: [ ip ]
# Will scan the value as URL and store domain name or ip address to `p_any_domain_names` or `p_any_ip_addresses`
- name: target_url
type: string
indicators: [ url ]

Using JSON Schema in an IDE

If your editor/IDE supports JSON Schema, you can use this JSON Schema file for validation and autocompletion.


You can find instruction on how to configure JetBrains IDEs to use custom JSON Schemas here


You can find instructions on how to configure VSCode to use JSON Schema here.