InfluxDB Logs

InfluxDB Logs Sink

The InfluxDB Logs sink enables worker to deliver log event data into InfluxDB. It supports both InfluxDB v2.x (bucket + org + token) and legacy InfluxDB v0.x/v1.x (database + optional retention policy and username/password authentication).

This sink is useful when you want to store logs in InfluxDB for correlation with time-series telemetry and querying with InfluxDB’s native tooling.

Ensure the following prerequisites are satisfied before using this sink:

Defines the target InfluxDB HTTP endpoint where worker sends log data.

The endpoint must be a full HTTP URI including scheme, host, and port.

Use these parameters when writing to InfluxDB v2.x and above:

Bucket

Specifies the bucket where log data will be written.

Organization

Specifies the organization that owns the target bucket.

Token

The authentication token used to write data into the organization and bucket.

Use these parameters when writing to InfluxDB v0.x/v1.x:

Database

Specifies the database where log data will be written.

Retention Policy Name

Optionally targets a specific retention policy for writes. This is useful when different retention periods are configured at the database level.

Consistency

Optionally sets the write consistency level for the target cluster. This only applies to legacy InfluxDB versions where consistency levels are configurable.

Username and Password

Optional credentials for basic authentication when required by the InfluxDB deployment.

Controls the InfluxDB measurement name that receives the log entries.

This is important for organizing log streams and supporting predictable queries and retention strategies.

This field is deprecated and should not be used for new deployments. Use measurement instead.

Controls which event field is treated as the hostname. If not set explicitly, worker uses the configured log_schema.host_key value (commonly host).

Controls which event field is treated as the log message payload. If not set explicitly, worker uses the configured log_schema.message_key value (commonly message).

Controls which event field is treated as the source type. If not set explicitly, worker uses the configured log_schema.source_type_key value (commonly source_type).

These mappings allow you to align worker's events with your existing log conventions without restructuring upstream data producers.

Defines which log fields are promoted into InfluxDB tags.

Tags are indexed and are typically used for dimensions such as:

Because tags influence index cardinality, you should choose tag fields carefully to avoid excessive cardinality growth.

By default, worker adds:

The sink supports selective serialization controls via:

This is useful for:

The sink exposes outbound request tuning options to control behavior under load, including:

These settings are typically used to align the sink’s sending behavior with InfluxDB’s ingestion capacity and to protect the pipeline during transient failures.

TLS options control secure transport to the InfluxDB endpoint, including:

TLS should be used for production deployments, especially when sending data across networks you do not fully control.

Common scenarios for the InfluxDB Logs sink include:

The InfluxDB Logs sink provides a direct path for delivering worker log events into InfluxDB. It supports both modern (v2.x+) and legacy (v0.x/v1.x) deployments, allows flexible mapping of message/host/source fields, supports tagging for efficient querying, and includes fine-grained controls for request behavior and TLS security.