Vector v0.37.0 release notes

The datadog_agent source now contains a configuration setting parse_ddtags, which is disabled by default.

When enabled, the ddtags field (a comma separated list of key-value strings) is parsed and expanded into an object in the event.

The datadog_agent source now correctly calculates the value for the metric component_received_event_bytes_total before enriching the event with Vector metadata.

The source also now adheres to the Component Specification by incrementing component_errors_total when a request succeeded in decompression but JSON parsing failed.

The datadog_logs sink no longer requires a semantic meaning input definition for message and timestamp fields.

While the Datadog logs intake does handle these fields if they are present, they aren’t required.

The only impact is that configurations which enable the Log Namespace feature and use a Source input to this sink which does not itself define a semantic meaning for message and timestamp, no longer need to manually set the semantic meaning for these two fields through a remap transform.

Existing configurations that utilize the Legacy namespace are unaffected, as are configurations using the Vector namespace where the input source has defined the message and timestamp semantic meanings.

We now correctly calculate the estimated JSON size in bytes for the metric component_received_event_bytes_total for the splunk_hec source.

Previously this was being calculated after event enrichment. It is now calculated before enrichment, for both raw and event endpoints.