LogDNA Sink

The Vector logdna sink batches log events to LogDna's HTTP Ingestion API.

Configuration

vector.toml
[sinks.my_sink_id]
type = "logdna" # required
inputs = ["my-source-id"] # required
api_key = "${LOGDNA_API_KEY}" # required
hostname = "${HOSTNAME}" # required
healthcheck = true # optional, default
12 items
stringcommonrequired

api_key

The Ingestion API key.

No default
View examples
tableoptional

batch

Configures the sink batching behavior.

int (bytes)commonoptional

max_size

The maximum size of a batch, in bytes, before it is flushed.

See Buffers & Batches for more info.

Default: 10490000 (bytes)
View examples
int (seconds)commonoptional

timeout_secs

The maximum age of a batch before it is flushed.

See Buffers & Batches for more info.

Default: 1 (seconds)
View examples
tableoptional

buffer

Configures the sink specific buffer behavior.

int (events)commonoptional

max_events

The maximum number of events allowed in the buffer.

Only relevant when: type = "memory"
Default: 500 (events)
View examples
int (bytes)required*

max_size

The maximum size of the buffer on the disk.

See Buffers & Batches for more info.

Only required when: type = "disk"
No default
View examples
stringenumcommonoptional

type

The buffer's type and storage mechanism.

Default: "memory"
Enum, must be one of: "memory" "disk"
View examples
stringenumoptional

when_full

The behavior when the buffer becomes full.

Default: "block"
Enum, must be one of: "block" "drop_newest"
View examples
stringoptional

default_app

The default app that will be set for events that do not contain a file or app field.

Default: "vector"
View examples
tableoptional

encoding

Configures the encoding specific sink behavior.

[string]optional

except_fields

Prevent the sink from encoding the specified labels.

No default
View examples
[string]optional

only_fields

Limit the sink to only encoding the specified labels.

No default
View examples
stringenumoptional

timestamp_format

How to format event timestamps.

Default: "rfc3339"
Enum, must be one of: "rfc3339" "unix"
View examples
boolcommonoptional

healthcheck

Enables/disables the sink healthcheck upon start.

See Health Checks for more info.

Default: true
View examples
stringoptional

host

An optional host that will override the default one.

No default
View examples
stringcommonrequired

hostname

The hostname that will be attached to each batch of events.

No default
View examples
stringoptional

ip

The IP address that will be attached to each batch of events.

No default
View examples
stringoptional

mac

The mac address that will be attached to each batch of events.

No default
View examples
tableoptional

request

Configures the sink request behavior.

int (requests)commonoptional

in_flight_limit

The maximum number of in-flight requests allowed at any given time.

See Rate Limits for more info.

Default: 5 (requests)
View examples
int (seconds)commonoptional

rate_limit_duration_secs

The time window, in seconds, used for the rate_limit_num option.

See Rate Limits for more info.

Default: 1 (seconds)
View examples
intcommonoptional

rate_limit_num

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

See Rate Limits for more info.

Default: 5
View examples
intoptional

retry_attempts

The maximum number of retries to make for failed requests.

See Retry Policy for more info.

Default: -1
View examples
int (seconds)optional

retry_initial_backoff_secs

The amount of time to wait before attempting the first retry for a failed request. Once, the first retry has failed the fibonacci sequence will be used to select future backoffs.

Default: 1 (seconds)
View examples
int (seconds)optional

retry_max_duration_secs

The maximum amount of time, in seconds, to wait between retries.

Default: 10 (seconds)
View examples
int (seconds)commonoptional

timeout_secs

The maximum time a request can take before being aborted. It is highly recommended that you do not lower value below the service's internal timeout, as this could create orphaned requests, pile on retries, and result in duplicate data downstream.

See Buffers & Batches for more info.

Default: 60 (seconds)
View examples
[string]optional

tags

The tags that will be attached to each batch of events.

No default
View examples

How It Works

Buffers & Batches

The logdna sink 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:

  1. The batch age meets or exceeds the configured timeout_secs.
  2. The batch size meets or exceeds the configured max_size.

Buffers are controlled via the buffer.* options.

Environment Variables

Environment variables are supported through all of Vector's configuration. Simply add ${MY_ENV_VAR} in your Vector configuration file and the variable will be replaced before being evaluated.

You can learn more in the Environment Variables section.

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.toml --require-healthy

Disable Health Checks

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

Rate Limits

Vector offers a few levers to control the rate and volume of requests to the downstream service. Start with the rate_limit_duration_secs and rate_limit_num options to ensure Vector does not exceed the specified number of requests in the specified window. You can further control the pace at which this window is saturated with the in_flight_limit option, which will guarantee no more than the specified number of requests are in-flight at any given time.

Please note, Vector's defaults are carefully chosen and it should be rare that you need to adjust these. If you found a good reason to do so please share it with the Vector team by opening an issie.

Retry Policy

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