InfluxDB logs sink

Configuration

Example configurations

{
  "sinks": {
    "my_sink_id": {
      "type": "influxdb_logs",
      "inputs": [
        "my-source-or-transform-id"
      ],
      "bucket": "vector-bucket",
      "database": "vector-database",
      "endpoint": "http://localhost:8086",
      "org": "my-org",
      "token": "${INFLUXDB_TOKEN}"
    }
  }
}

[sinks.my_sink_id]
type = "influxdb_logs"
inputs = [ "my-source-or-transform-id" ]
bucket = "vector-bucket"
database = "vector-database"
endpoint = "http://localhost:8086"
org = "my-org"
token = "${INFLUXDB_TOKEN}"

sinks:
  my_sink_id:
    type: influxdb_logs
    inputs:
      - my-source-or-transform-id
    bucket: vector-bucket
    database: vector-database
    endpoint: http://localhost:8086
    org: my-org
    token: ${INFLUXDB_TOKEN}

{
  "sinks": {
    "my_sink_id": {
      "type": "influxdb_logs",
      "inputs": [
        "my-source-or-transform-id"
      ],
      "bucket": "vector-bucket",
      "consistency": "any",
      "database": "vector-database",
      "endpoint": "http://localhost:8086",
      "host_key": "hostname",
      "measurement": "vector-logs",
      "message_key": "text",
      "namespace": "service",
      "org": "my-org",
      "password": "${INFLUXDB_PASSWORD}",
      "retention_policy_name": "autogen",
      "source_type_key": "source",
      "tags": [
        "field1"
      ],
      "token": "${INFLUXDB_TOKEN}",
      "username": "todd"
    }
  }
}

[sinks.my_sink_id]
type = "influxdb_logs"
inputs = [ "my-source-or-transform-id" ]
bucket = "vector-bucket"
consistency = "any"
database = "vector-database"
endpoint = "http://localhost:8086"
host_key = "hostname"
measurement = "vector-logs"
message_key = "text"
namespace = "service"
org = "my-org"
password = "${INFLUXDB_PASSWORD}"
retention_policy_name = "autogen"
source_type_key = "source"
tags = [ "field1" ]
token = "${INFLUXDB_TOKEN}"
username = "todd"

sinks:
  my_sink_id:
    type: influxdb_logs
    inputs:
      - my-source-or-transform-id
    bucket: vector-bucket
    consistency: any
    database: vector-database
    endpoint: http://localhost:8086
    host_key: hostname
    measurement: vector-logs
    message_key: text
    namespace: service
    org: my-org
    password: ${INFLUXDB_PASSWORD}
    retention_policy_name: autogen
    source_type_key: source
    tags:
      - field1
    token: ${INFLUXDB_TOKEN}
    username: todd

acknowledgements

optional object

Controls how acknowledgements are handled for this sink.

See End-to-end Acknowledgements for more information on how event acknowledgement is handled.

acknowledgements.enabled

optional bool

Whether or not end-to-end acknowledgements are enabled.

When enabled for a sink, any source that supports end-to-end acknowledgements that is connected to that sink waits for events to be acknowledged by all connected sinks before acknowledging them at the source.

Enabling or disabling acknowledgements at the sink level takes precedence over any global acknowledgements configuration.

batch

optional object

Event batching behavior.

batch.max_bytes

optional uint

The maximum size of a batch that is processed by a sink.

This is based on the uncompressed size of the batched events, before they are serialized or compressed.

default: 1e+06(bytes)

batch.max_events

optional uint

The maximum size of a batch before it is flushed.

batch.timeout_secs

optional float

The maximum age of a batch before it is flushed.

default: 1(seconds)

bucket

required string literal

The name of the bucket to write into.

Only relevant when using InfluxDB v2.x and above.

Examples

"vector-bucket"

"4d2225e4d3d49f75"

buffer

optional object

Configures the buffering behavior for this sink.

More information about the individual buffer types, and buffer behavior, can be found in the Buffering Model section.

buffer.max_events

optional uint

The maximum number of events allowed in the buffer.

Relevant when: type = "memory"

default: 500

buffer.max_size

required uint

The maximum size of the buffer on disk.

Must be at least ~256 megabytes (268435488 bytes).

Relevant when: type = "disk"

buffer.type

optional string literal enum

The type of buffer to use.

Enum options

Option Description

Option	Description
`disk`	Events are buffered on disk. This is less performant, but more durable. Data that has been synchronized to disk will not be lost if Vector is restarted forcefully or crashes. Data is synchronized to disk every 500ms.
`memory`	Events are buffered in memory. This is more performant, but less durable. Data will be lost if Vector is restarted forcefully or crashes.

disk

Events are buffered on disk.

This is less performant, but more durable. Data that has been synchronized to disk will not be lost if Vector is restarted forcefully or crashes.

Data is synchronized to disk every 500ms.

memory

Events are buffered in memory.

This is more performant, but less durable. Data will be lost if Vector is restarted forcefully or crashes.

default: memory

buffer.when_full

optional string literal enum

Event handling behavior when a buffer is full.

Enum options

Option Description

Option	Description
`block`	Wait for free space in the buffer. This applies backpressure up the topology, signalling that sources should slow down the acceptance/consumption of events. This means that while no data is lost, data will pile up at the edge.
`drop_newest`	Drops the event instead of waiting for free space in buffer. The event will be intentionally dropped. This mode is typically used when performance is the highest priority, and it is preferable to temporarily lose events rather than cause a slowdown in the acceptance/consumption of events.

block

Wait for free space in the buffer.

This applies backpressure up the topology, signalling that sources should slow down the acceptance/consumption of events. This means that while no data is lost, data will pile up at the edge.

drop_newest

Drops the event instead of waiting for free space in buffer.

The event will be intentionally dropped. This mode is typically used when performance is the highest priority, and it is preferable to temporarily lose events rather than cause a slowdown in the acceptance/consumption of events.

default: block

consistency

optional string literal

The consistency level to use for writes.

Only relevant when using InfluxDB v0.x/v1.x.

Examples

"any"

"one"

"quorum"

"all"

database

required string literal

The name of the database to write into.

Only relevant when using InfluxDB v0.x/v1.x.

Examples

"vector-database"

"iot-store"

encoding

optional object

Transformations to prepare an event for serialization.

encoding.except_fields

optional [string]

List of fields that are excluded from the encoded event.

encoding.only_fields

optional [string]

List of fields that are included in the encoded event.

encoding.timestamp_format

optional string literal enum

Format used for timestamp fields.

Enum options

Option	Description
`rfc3339`	Represent the timestamp as a RFC 3339 timestamp.
`unix`	Represent the timestamp as a Unix timestamp.
`unix_float`	Represent the timestamp as a Unix timestamp in floating point.
`unix_ms`	Represent the timestamp as a Unix timestamp in milliseconds.
`unix_ns`	Represent the timestamp as a Unix timestamp in nanoseconds.
`unix_us`	Represent the timestamp as a Unix timestamp in microseconds

endpoint

required string literal

The endpoint to send data to.

This should be a full HTTP URI, including the scheme, host, and port.

Examples

"http://localhost:8086"

healthcheck

optional object

Healthcheck configuration.

healthcheck.enabled

optional bool

Whether or not to check the health of the sink when Vector starts up.

default: true

host_key

optional string literal

Use this option to customize the key containing the hostname.

The setting of log_schema.host_key, usually host, is used here by default.

Examples

"hostname"

inputs

required [string]

A list of upstream source or transform IDs.

Wildcards (*) are supported.

See configuration for more info.

Array string literal

Examples

[
  "my-source-or-transform-id",
  "prefix-*"
]

measurement

optional string literal

The name of the InfluxDB measurement that is written to.

Examples

"vector-logs"

message_key

optional string literal

Use this option to customize the key containing the message.

The setting of log_schema.message_key, usually message, is used here by default.

Examples

"text"

namespace

optional string literal

Deprecated

This field is deprecated, and measurement should be used instead.

The namespace of the measurement name to use.

When specified, the measurement name is <namespace>.vector.

Examples

"service"

org

required string literal

The name of the organization to write into.

Only relevant when using InfluxDB v2.x and above.

Examples

"my-org"

"33f2cff0a28e5b63"

password

optional string literal

The password to authenticate with.

Only relevant when using InfluxDB v0.x/v1.x.

Examples

"${INFLUXDB_PASSWORD}"

"influxdb4ever"

request

optional object

Middleware settings for outbound requests.

Various settings can be configured, such as concurrency and rate limits, timeouts, and retry behavior.

Note that the retry backoff policy follows the Fibonacci sequence.

request.adaptive_concurrency

optional object

Configuration of adaptive concurrency parameters.

These parameters typically do not require changes from the default, and incorrect values can lead to meta-stable or unstable performance and sink behavior. Proceed with caution.

request.adaptive_concurrency.decrease_ratio

optional float

The fraction of the current value to set the new concurrency limit when decreasing the limit.

Valid values are greater than 0 and less than 1. Smaller values cause the algorithm to scale back rapidly when latency increases.

Note: The new limit is rounded down after applying this ratio.

default: 0.9

request.adaptive_concurrency.ewma_alpha

optional float

The weighting of new measurements compared to older measurements.

Valid values are greater than 0 and less than 1.

ARC uses an exponentially weighted moving average (EWMA) of past RTT measurements as a reference to compare with the current RTT. Smaller values cause this reference to adjust more slowly, which may be useful if a service has unusually high response variability.

default: 0.4

request.adaptive_concurrency.initial_concurrency

optional uint

The initial concurrency limit to use. If not specified, the initial limit is 1 (no concurrency).

Datadog recommends setting this value to your service’s average limit if you’re seeing that it takes a long time to ramp up adaptive concurrency after a restart. You can find this value by looking at the adaptive_concurrency_limit metric.

default: 1

request.adaptive_concurrency.max_concurrency_limit

optional uint

The maximum concurrency limit.

The adaptive request concurrency limit does not go above this bound. This is put in place as a safeguard.

default: 200

request.adaptive_concurrency.rtt_deviation_scale

optional float

Scale of RTT deviations which are not considered anomalous.

Valid values are greater than or equal to 0, and we expect reasonable values to range from 1.0 to 3.0.

When calculating the past RTT average, we also compute a secondary “deviation” value that indicates how variable those values are. We use that deviation when comparing the past RTT average to the current measurements, so we can ignore increases in RTT that are within an expected range. This factor is used to scale up the deviation to an appropriate range. Larger values cause the algorithm to ignore larger increases in the RTT.

default: 2.5

request.concurrency

optional string literal enum uint

Configuration for outbound request concurrency.

This can be set either to one of the below enum values or to a positive integer, which denotes a fixed concurrency limit.

Enum options

Option Description

adaptive Concurrency is managed by Vector’s Adaptive Request Concurrency feature.

Option	Description
`adaptive`	Concurrency is managed by Vector’s Adaptive Request Concurrency feature.
`none`	A fixed concurrency of 1. Only one request can be outstanding at any given time.

none

A fixed concurrency of 1.

Only one request can be outstanding at any given time.

default: adaptive

request.rate_limit_duration_secs

optional uint

The time window used for the rate_limit_num option.

default: 1(seconds)

request.rate_limit_num

optional uint

The maximum number of requests allowed within the rate_limit_duration_secs time window.

default: 9.223372036854776e+18(requests)

request.retry_attempts

optional uint

The maximum number of retries to make for failed requests.

default: 9.223372036854776e+18(retries)

request.retry_initial_backoff_secs

optional uint

The amount of time to wait before attempting the first retry for a failed request.

After the first retry has failed, the fibonacci sequence is used to select future backoffs.

default: 1(seconds)

request.retry_jitter_mode

optional string literal enum

The jitter mode to use for retry backoff behavior.

Enum options

Option Description

Option	Description
`Full`	Full jitter. The random delay is anywhere from 0 up to the maximum current delay calculated by the backoff strategy. Incorporating full jitter into your backoff strategy can greatly reduce the likelihood of creating accidental denial of service (DoS) conditions against your own systems when many clients are recovering from a failure state.
`None`	No jitter.

Full

Full jitter.

The random delay is anywhere from 0 up to the maximum current delay calculated by the backoff strategy.

Incorporating full jitter into your backoff strategy can greatly reduce the likelihood of creating accidental denial of service (DoS) conditions against your own systems when many clients are recovering from a failure state.

None No jitter.

default: Full

request.retry_max_duration_secs

optional uint

The maximum amount of time to wait between retries.

default: 30(seconds)

request.timeout_secs

optional uint

The time a request can take before being aborted.

Datadog highly recommends that you do not lower this value below the service’s internal timeout, as this could create orphaned requests, pile on retries, and result in duplicate data downstream.

default: 60(seconds)

retention_policy_name

optional string literal

The target retention policy for writes.

Only relevant when using InfluxDB v0.x/v1.x.

Examples

"autogen"

"one_day_only"

source_type_key

optional string literal

Use this option to customize the key containing the source_type.

The setting of log_schema.source_type_key, usually source_type, is used here by default.

Examples

"source"

tls

optional object

TLS configuration.

tls.alpn_protocols

optional [string]

Sets the list of supported ALPN protocols.

Declare the supported ALPN protocols, which are used during negotiation with a peer. They are prioritized in the order that they are defined.

tls.ca_file

optional string literal

Absolute path to an additional CA certificate file.

The certificate must be in the DER or PEM (X.509) format. Additionally, the certificate can be provided as an inline string in PEM format.

Examples

"/path/to/certificate_authority.crt"

tls.crt_file

optional string literal

Absolute path to a certificate file used to identify this server.

The certificate must be in DER, PEM (X.509), or PKCS#12 format. Additionally, the certificate can be provided as an inline string in PEM format.

If this is set and is not a PKCS#12 archive, key_file must also be set.

Examples

"/path/to/host_certificate.crt"

tls.key_file

optional string literal

Absolute path to a private key file used to identify this server.

The key must be in DER or PEM (PKCS#8) format. Additionally, the key can be provided as an inline string in PEM format.

Examples

"/path/to/host_certificate.key"

tls.key_pass

optional string literal

Passphrase used to unlock the encrypted key file.

This has no effect unless key_file is set.

Examples

"${KEY_PASS_ENV_VAR}"

"PassWord1"

tls.server_name

optional string literal

Server name to use when using Server Name Indication (SNI).

Only relevant for outgoing connections.

Examples

"www.example.com"

tls.verify_certificate

optional bool

Enables certificate verification. For components that create a server, this requires that the client connections have a valid client certificate. For components that initiate requests, this validates that the upstream has a valid certificate.

If enabled, certificates must not be expired and must be issued by a trusted issuer. This verification operates in a hierarchical manner, checking that the leaf certificate (the certificate presented by the client/server) is not only valid, but that the issuer of that certificate is also valid, and so on, until the verification process reaches a root certificate.

Do NOT set this to false unless you understand the risks of not verifying the validity of certificates.

tls.verify_hostname

optional bool

Enables hostname verification.

If enabled, the hostname used to connect to the remote host must be present in the TLS certificate presented by the remote host, either as the Common Name or as an entry in the Subject Alternative Name extension.

Only relevant for outgoing connections.

Do NOT set this to false unless you understand the risks of not verifying the remote hostname.

token

required string literal

The token to authenticate with.

Only relevant when using InfluxDB v2.x and above.

Examples

"${INFLUXDB_TOKEN}"

"ef8d5de700e7989468166c40fc8a0ccd"

username

optional string literal

The username to authenticate with.

Only relevant when using InfluxDB v0.x/v1.x.

Examples

"todd"

"vector-source"

Input Types

The following table lists all telemetry data types supported by the component across possible configurations. Be aware that the available data types may differ based on the specified codec configuration.

Logs

Log events are supported.

Telemetry

intentional

True if the events were discarded intentionally, like a filter transform, or false if due to an error.

pid optional

The process ID of the Vector instance.

component_errors_total

counter

The total number of errors encountered by this component.

component_id

The Vector component ID.

component_kind

The Vector component kind.

component_type

The Vector component type.

error_type

The type of the error

host optional

The hostname of the system Vector is running on.

pid optional

The process ID of the Vector instance.

stage

The stage within the component at which the error occurred.

component_received_event_bytes_total

counter

The number of event bytes accepted by this component either from tagged origins like file and uri, or cumulatively from other origins.

component_id

The Vector component ID.

component_kind

The Vector component kind.

component_type

The Vector component type.

container_name optional

The name of the container from which the data originated.

file optional

The file from which the data originated.

host optional

The hostname of the system Vector is running on.

mode optional

The connection mode used by the component.

peer_addr optional

The IP from which the data originated.

peer_path optional

The pathname from which the data originated.

pid optional

The process ID of the Vector instance.

pod_name optional

The name of the pod from which the data originated.

uri optional

The sanitized URI from which the data originated.

component_received_events_count

histogram

A histogram of the number of events passed in each internal batch in Vector’s internal topology.

Note that this is separate than sink-level batching. It is mostly useful for low level debugging performance issues in Vector due to small internal batches.

component_id

The Vector component ID.

component_kind

The Vector component kind.

component_type

The Vector component type.

container_name optional

The name of the container from which the data originated.

file optional

The file from which the data originated.

host optional

The hostname of the system Vector is running on.

mode optional

The connection mode used by the component.

peer_addr optional

The IP from which the data originated.

peer_path optional

The pathname from which the data originated.

pid optional

The process ID of the Vector instance.

pod_name optional

The name of the pod from which the data originated.

uri optional

The sanitized URI from which the data originated.

component_received_events_total

counter

The number of events accepted by this component either from tagged origins like file and uri, or cumulatively from other origins.

component_id

The Vector component ID.

component_kind

The Vector component kind.

component_type

The Vector component type.

container_name optional

The name of the container from which the data originated.

file optional

The file from which the data originated.

host optional

The hostname of the system Vector is running on.

mode optional

The connection mode used by the component.

peer_addr optional

The IP from which the data originated.

peer_path optional

The pathname from which the data originated.

pid optional

The process ID of the Vector instance.

pod_name optional

The name of the pod from which the data originated.

uri optional

The sanitized URI from which the data originated.

component_sent_bytes_total

counter

The number of raw bytes sent by this component to destination sinks.

component_id

The Vector component ID.

component_kind

The Vector component kind.

component_type

The Vector component type.

endpoint optional

The endpoint to which the bytes were sent. For HTTP, this will be the host and path only, excluding the query string.

file optional

The absolute path of the destination file.

host optional

The hostname of the system Vector is running on.

pid optional

The process ID of the Vector instance.

protocol

The protocol used to send the bytes.

region optional

The AWS region name to which the bytes were sent. In some configurations, this may be a literal hostname.

component_sent_event_bytes_total

counter

The total number of event bytes emitted by this component.

component_id

The Vector component ID.

component_kind

The Vector component kind.

component_type

The Vector component type.

host optional

The hostname of the system Vector is running on.

output optional

The specific output of the component.

pid optional

The process ID of the Vector instance.

component_sent_events_total

counter

The total number of events emitted by this component.

component_id

The Vector component ID.

component_kind

The Vector component kind.

component_type

The Vector component type.

host optional

The hostname of the system Vector is running on.

output optional

The specific output of the component.

pid optional

The process ID of the Vector instance.

utilization

gauge

A ratio from 0 to 1 of the load on a component. A value of 0 would indicate a completely idle component that is simply waiting for input. A value of 1 would indicate a that is never idle. This value is updated every 5 seconds.

component_id

The Vector component ID.

component_kind

The Vector component kind.

component_type

The Vector component type.

host optional

The hostname of the system Vector is running on.

pid optional

The process ID of the Vector instance.

How it works

Buffers and batches

This component buffers & batches data as shown in the diagram above. You’ll notice that Vector treats these concepts differently, instead of treating them as global concepts, Vector treats them as sink specific concepts. This isolates sinks, ensuring services disruptions are contained and delivery guarantees are honored.

Batches are flushed when 1 of 2 conditions are met:

The batch age meets or exceeds the configured timeout_secs.
The batch size meets or exceeds the configured max_bytes or max_events.

Buffers are controlled via the buffer.* options.

Health checks

Health checks ensure that the downstream service is accessible and ready to accept data. This check is performed upon sink initialization. If the health check fails an error will be logged and Vector will proceed to start.

Require health checks

If you’d like to exit immediately upon a health check failure, you can pass the --require-healthy flag:

vector --config /etc/vector/vector.yaml --require-healthy

Disable health checks

If you’d like to disable health checks for this sink you can set the healthcheck option to false.

Mapping Log Fields

InfluxDB uses line protocol to write data points. It is a text-based format that provides the measurement, tag set, field set, and timestamp of a data point.

A Log Event event contains an arbitrary set of fields (key/value pairs) that describe the event.

The following matrix outlines how Log Event fields are mapped into InfluxDB Line Protocol:

Field	Line Protocol
host	tag
message	field
source_type	tag
timestamp	timestamp
[custom-key]	field

The default behavior can be overridden by a tags configuration.

Mapping Example

The following event:

{
  "host": "my.host.com",
  "message": "<13>Feb 13 20:07:26 74794bfb6795 root[8539]: i am foobar",
  "timestamp": "2019-11-01T21:15:47+00:00",
  "custom_field": "custom_value"
}

Will be mapped to Influx’s line protocol:

vector-logs,host=my.host.com,metric_type=logs custom_field="custom_value",message="<13>Feb 13 20:07:26 74794bfb6795 root[8539]: i am foobar" 1572642947000000000

Rate limits & adaptive concurrency

Adaptive Request Concurrency (ARC)

Adaptive Request Concurrency is a feature of Vector that does away with static concurrency limits and automatically optimizes HTTP concurrency based on downstream service responses. The underlying mechanism is a feedback loop inspired by TCP congestion control algorithms. Checkout the announcement blog post,

We highly recommend enabling this feature as it improves performance and reliability of Vector and the systems it communicates with. As such, we have made it the default, and no further configuration is required.

Static concurrency

If Adaptive Request Concurrency is not for you, you can manually set static concurrency limits by specifying an integer for request.concurrency:

sinks:
	my-sink:
		request:
			concurrency: 10

Rate limits

In addition to limiting request concurrency, you can also limit the overall request throughput via the request.rate_limit_duration_secs and request.rate_limit_num options.

sinks:
	my-sink:
		request:
			rate_limit_duration_secs: 1
			rate_limit_num: 10

These will apply to both adaptive and fixed request.concurrency values.

Retry policy

Vector will retry failed requests (status in [408, 429], >= 500, and != 501). Other responses will not be retried. You can control the number of retry attempts and backoff rate with the request.retry_attempts and request.retry_backoff_secs options.

State

This component is stateless, meaning its behavior is consistent across each input.

Transport Layer Security (TLS)

Vector uses OpenSSL for TLS protocols due to OpenSSL’s maturity. You can enable and adjust TLS behavior via the

tls.*`` options and/or via an [OpenSSL configuration file](https://www.openssl.org/docs/man3.1/man5/config.html). The file location defaults to

/usr/local/ssl/openssl.cnfor can be specified with theOPENSSL_CONF` environment variable.