Ingest Data for Observability

Observability data reaches GreptimeDB through the protocol its source already speaks. Ingest Data lists every source in one table; this page groups the observability paths by signal.

Metrics

• Prometheus Remote Write — for an existing Prometheus server or Prometheus Agent.
• OpenTelemetry — OTLP/HTTP from an OpenTelemetry SDK.
• InfluxDB Line Protocol — the path for migrating off InfluxDB, and for Telegraf. This page also covers the Telegraf configuration.

Logs

• Loki — the Loki Push API, the path for migrating off Loki without changing the clients already writing to it. This page also covers the Alloy configuration.
• Elasticsearch — the _bulk API, compatible with Logstash, Filebeat, and Telegraf.
• Splunk — the HTTP Event Collector (HEC) protocol, compatible with Vector and the OpenTelemetry Collector.

Parsing and transforming text logs before they are stored is covered in Logs.

Traces

• OpenTelemetry — OTLP/HTTP from an SDK or the Collector.

Storing traces and querying them with SQL or the Jaeger-compatible API is covered in Traces.

Agents and pipelines

These sit between the source and GreptimeDB, writing through an exporter, sink, or output that you configure. The signals each one carries differ:

• OpenTelemetry Collector — routes metrics, logs, and traces through an OTLP/HTTP exporter.
• Vector — metrics through the greptimedb_metrics sink, logs through greptimedb_logs. No traces sink.
• Fluent Bit — logs through the HTTP output; metrics, logs, and traces through the OpenTelemetry output; metrics also through Prometheus Remote Write.
• Grafana Alloy — writes through Remote Write, OpenTelemetry, or Loki.
• Kafka — consumed into GreptimeDB with Vector as the transport.