Sematext Metrics

CAUTION

Sematext monitoring only accepts metrics which contain a single value. Therefore, only counter and gauge metrics are supported. If you'd like to ingest other metric types please consider using the metric_to_log transform with the sematext_logs sink.

Configuration Options

Required Options

region(required)

The region to send data to.

Type	Syntax	Default	Example
string	literal		["us","eu"]

default_namespace(required)

Used as a namespace for metrics that don't have it.

Type	Syntax	Default	Example
string	literal		["service"]

inputs(required)

A list of upstream source or transform IDs. Wildcards (*) are supported.

See configuration for more info.

Type	Syntax	Default	Example
array	literal		["my-source-or-transform-id","prefix-*"]

encoding(required)

Configures the encoding specific sink behavior.

Type	Syntax	Default	Example
hash	literal		[]

token(required)

The token that will be used to write to Sematext.

Type	Syntax	Default	Example
string	literal		["${SEMATEXT_TOKEN}","some-sematext-token"]

type(required)

The component type. This is a required field for all components and tells Vector which component to use.

Type	Syntax	Default	Example
string	literal		["sematext_metrics"]

Advanced Options

endpoint(optional)

The endpoint to send data to.

Type	Syntax	Default	Example
string	literal		["http://127.0.0.1","http://example.com"]

buffer(optional)

Configures the sink specific buffer behavior.

Type	Syntax	Default	Example
hash	literal		[]

batch(optional)

Configures the sink batching behavior.

Type	Syntax	Default	Example
hash			[]

healthcheck(optional)

Health check options for the sink.

Type	Syntax	Default	Example
hash			[]

proxy(optional)

Configures an HTTP(S) proxy for Vector to use. By default, the globally configured proxy is used.

Type	Syntax	Default	Example
hash	literal		[]

How it Works

State

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

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.

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_size or max_events.

Buffers are controlled via the buffer.* options.