A Vector log event is a structured representation of a point-in-time event. It contains an arbitrary set of fields that describe the event.
A key tenet of Vector is to remain schema neutral. This ensures that Vector can work with any schema, supporting legacy and future schemas as your needs evolve. Vector does not require any specific fields, and each compoennt will document the fields it provides.
An arbitrary set of key/value pairs that can be infinitely nested.
How It Works
Vector is schema-neutral and does not require any specific schema. This ensures that Vector can work with a variety of schemas, supporting legacy schemas as well as future schemas.
Vector does plan to implement a common information model that would recognize popular schemas, allowing you to seamlessly transform between schemas. You can track progress on this work in issue 3910.
Strings are UTF-8 compatible and are only bounded by the available system memory.
Integers are signed integers up to 64 bits.
Floats are 64-bit IEEE 754 floats.
Booleans represent binary true/false values.
Timestamps are represented as
DateTime Rust structs
stored as UTC.
There are cases where Vector interacts with formats that do not have a formal
timestamp definition, such as JSON. In these cases, Vector will ingest the
timestamp in its primitive form (string or integer). You can then coerce the
field into a
timestamp using the
coercer transform. If you are parsing this data
out of a string, all Vector parser transforms include a
allowing you to extract and coerce in one step.
If Vector receives a timestamp that does not contain timezone information Vector assumes the timestamp is in local time, and will convert the timestamp to UTC from the local time.
For compatibility with JSON log events, Vector also supports
Maps are associative arrays mapping string fields to values of any type.
Array fields are sequences of values of any type.