Telemetry Agents

Telemetry agents sit close to the systems that produce data. They read container logs, application logs, host metrics, Prometheus metrics, or OTLP signals, then forward that data to Parseable with the labels and metadata you need for search and dashboards.

Parseable supports ingesting logs, metrics, and traces from agents that teams already use in production. Plain JSON logs are sent to /api/v1/ingest with an X-P-Stream header. OTLP logs, metrics, and traces are sent to /v1/logs, /v1/metrics, and /v1/traces; Parseable derives the signal type from the endpoint and uses X-P-Stream for the destination dataset. For OTLP examples, send the Parseable API key as a Bearer token in the Authorization header.

Use this section when you already have an agent running, or when you want to pick one for a new deployment.

Apache Log4j 2

Send Java application logs directly from the app over HTTP.

Filebeat

Use existing Beats pipelines where Filebeat ships logs to Logstash before forwarding to Parseable.

Fluent Bit

Collect lightweight container, Kubernetes, host, and edge logs.

Fluentd

Keep existing Fluentd pipelines and add Parseable as an HTTP destination.

Logstash

Run filter-heavy log pipelines and Beats ingestion before sending data to Parseable.

OpenTelemetry Collector

Build logs, metrics, and traces pipelines around OpenTelemetry receivers, processors, and exporters.

Prometheus

Ingest metrics through Prometheus Remote Write.

Promtail

Route existing Loki-style log pipelines through the OpenTelemetry Collector.

Syslog-ng

Collect network, host, appliance, and security logs through syslog.

Vector

Run high-throughput log pipelines with transforms before HTTP delivery.

If you are starting fresh on Kubernetes, Fluent Bit or the OpenTelemetry Collector is usually the simplest place to begin. If your team already runs Filebeat, Fluentd, Logstash, Promtail, Syslog-ng, or Vector, keep that pipeline and update only the output stage that sends data to Parseable.