Template syntax

Vector supports a template syntax for some configuration options. This allows for dynamic values derived from event data. Options that support this syntax will be clearly documented as such in the option description.

linkExample

For example, let's partition data on AWS S3 by application_id and date. We can accomplish this with the key_prefix option in the aws_s3 sink:

1[sinks.backup]
2  type = "aws_s3"
3  bucket = "all_application_logs"
4  key_prefix = "application_id={{ application_id }}/date=%F/"

Notice that Vector allows direct field references as well as strftime specifiers. If we were to run the following log event though Vector:

1{
2  "timestamp": "2020-02-14T01:22:23.223Z",
3  "application_id": 1,
4  "message": "Hello world"
5}

The value of the key_prefix option would equal:

1application_id=1/date=2020-02-14

Because the aws_s3 sink batches data, each event would be grouped by its produced value. This effectively enables dynamic partitioning, something fundamental to storing log data in filesystems.

linkSyntax

linkEvent fields

Individual log event fields can be accessed using {{ <field-path-notation> }} syntax:

1option = "{{ field_path_notation }}"

Vector's field notation uses . to target nested fields and [<index>] to target array values.

linkstrftime specifiers

In addition to directly accessing fields, Vector offers a shortcut for injecting strftime specifiers:

1options = "year=%Y/month=%m/day=%d/"

The value is derived from the timestamp field and the name of this field can be changed via the global timestamp_key option.

linkEscaping

You can escape this syntax by prefixing the character with a \. For example, you can escape the event field syntax like this:

1option = "\{{ field_name }}"

And strftime specified like so:

1options = "year=\%Y/month=\%m/day=\%d/"

Each of the values above would be treated literally.

linkHow it works

linkArray Values

Array values can be accessed using Vector's field notation syntax:

1option = "{{ parent.child[0] }}"

linkFallback values

Vector doesn't currently support fallback values. Issue 1692 is open to add this functionality. In the interim, you can use the remap transform to set a default value:

1[transforms.set_defaults]
2  # REQUIRED
3  type = "remap"
4  inputs = ["my-source-id"]
5  source = '''
6    if !exists(.my_field) {
7      .my_field = "default"
8    }
9  '''

linkMissing fields

If a field is missing, a blank string is inserted in its place. In that case, Vector neither errors nor drops the event nor logs anything.

linkNested fields

Nested values can be accessed using Vector's field notation syntax:

1option = "{{ parent.child[0] }}"