Protocols
GreptimeDB speaks several wire protocols. They fall into two groups.
Connection protocols carry both writes and queries: the HTTP API, MySQL, and PostgreSQL. These pages document endpoints, authentication, and protocol-specific options. gRPC belongs here by transport but carries writes only β there is no gRPC query interface.
Ingestion protocols accept writes from a system that already speaks them β InfluxDB line protocol, OpenTelemetry, Loki, Elasticsearch, Splunk, and OpenTSDB. The pages here cover protocol-level details; the configuration for each source is in Ingest Data.
ποΈ Overview
The wire protocols GreptimeDB speaks, for both writing and querying, and where each protocol's ingestion guide lives.
ποΈ InfluxDB Line Protocol
Instructions on ingesting data to GreptimeDB using InfluxDB Line Protocol and using ping and health APIs.
ποΈ OpenTelemetry (OTLP)
Consume OpenTelemetry metrics, logs, and traces natively via OTLP/HTTP protocol
ποΈ MySQL
Guide on connecting to GreptimeDB using MySQL, managing tables, ingesting and querying data, and handling time zones.
ποΈ PostgreSQL
Guide on connecting to GreptimeDB using PostgreSQL, managing tables, ingesting and querying data, and handling time zones.
ποΈ HTTP API
Guide on using HTTP APIs to interact with GreptimeDB, including authentication, timeout settings, health checks, configuration, and SQL queries.
ποΈ gRPC
Overview of using gRPC SDKs for efficient and high-performance data ingestion in GreptimeDB.
ποΈ OpenTSDB
What GreptimeDB implements of the OpenTSDB protocol β the /api/put endpoint for writes only β and where the ingestion guide lives.
ποΈ Loki
What GreptimeDB implements of the Loki protocol β the Push API for writes only β and where the ingestion guide lives.
ποΈ Elasticsearch
What GreptimeDB implements of the Elasticsearch protocol β the _bulk API for writes only β and where the ingestion guide lives.
π οΈ Splunk
What GreptimeDB implements of the Splunk HEC protocol, which endpoints exist, and what is deliberately not implemented.