API reference

Remote write

Ingest time series data using the Prometheus Remote Write 1.0 protocol.

The request body must be a Snappy-compressed protobuf WriteRequest message (as defined by the Prometheus remote write specification). Each WriteRequest contains one or more TimeSeries messages, each with a set of labels and one or more timestamp/value sample pairs.

This endpoint is designed for integration with Prometheus remote-write compatible agents and collectors. It is not intended as a general-purpose high-throughput ingestion path — for bulk data loading, prefer dedicated import tooling.

This endpoint is only available when the server is built with the remote-write feature.

POST

api

write

Remote write

curl --request POST \
  --url http://localhost:9090/api/v1/write \
  --header 'Content-Encoding: <content-encoding>' \
  --header 'Content-Type: <content-type>' \
  --data '"<string>"'

{
  "status": "error",
  "errorType": "bad_data",
  "error": "<string>"
}

Headers

Content-Type

enum<string>

required

Must be application/x-protobuf.

Available options:

application/x-protobuf

Content-Encoding

enum<string>

required

Must be snappy.

Available options:

snappy

Body

application/x-protobuf

Snappy-compressed protobuf WriteRequest message. The protobuf schema is defined by the Prometheus remote write specification.

Response

Samples ingested successfully (empty body).

LogKey-oriented event streaming built on an LSM tree

Remote write

curl --request POST \
  --url http://localhost:9090/api/v1/write \
  --header 'Content-Encoding: <content-encoding>' \
  --header 'Content-Type: <content-type>' \
  --data '"<string>"'

{
  "status": "error",
  "errorType": "bad_data",
  "error": "<string>"
}

Concepts

Timeseries

Log

Vector

Key-Value

Remote write

Headers

Body

Response