The GreptimeDB Logs sink writes log and metric events to GreptimeDB using its HTTP ingestion interface. It is designed for time-series–oriented observability workloads, combining structured logs and metrics within a single analytical database.

This sink is commonly used when GreptimeDB serves as:

Specifies the HTTP endpoint of the GreptimeDB server.

The endpoint must:

Defines the GreptimeDB database used for ingestion.

Key characteristics:

Dynamic database selection is supported using per-event values when required.

Specifies the target table into which data is written.

Important considerations:

Authentication credentials are required only if authentication is enabled on the GreptimeDB instance.

When configured:

Controls how events are grouped before being sent to GreptimeDB.

Batching parameters influence:

Default behavior favors small batches to balance ingestion latency and request overhead.

Defines how events are temporarily stored when ingestion throughput is constrained.

Supported buffer types:

When buffers are full:

Controls HTTP payload compression.

Supported compression methods:

Compression reduces network usage and improves throughput, especially in high-volume log ingestion scenarios.

Field-level transformations can be applied before sending data to GreptimeDB:

These controls are essential for:

Defines the logical pipeline identity applied to ingested logs.

Use cases include:

Specifies a pipeline version identifier.

This is useful for:

Allows adding or overriding HTTP headers on ingestion requests.

Typical use cases:

Custom query parameters can be appended to ingestion requests.

Used primarily for:

Advanced request controls are available to manage delivery under load:

These settings are typically tuned in:

Supports secure communication using TLS.

Capabilities include:

TLS should be enabled whenever GreptimeDB is accessed over untrusted networks.