Ingestion

Choose the ingestion path that matches the system sending data to Parseable.

OpenTelemetry

Send logs, metrics, and traces through OTLP and OpenTelemetry-compatible pipelines.

Prometheus Remote Write

Ingest Prometheus metrics with the remote write protocol.

AI Infrastructure

Observe agents, LLMs, gateways, runtimes, sandboxes, and coding assistants.

Telemetry Agents

Forward telemetry with collectors and agents such as Fluent Bit, Vector, Logstash, and OTel Collector.

Containers & Orchestration

Collect logs and telemetry from Docker, Kubernetes, ECS, EKS, GKE, and AKS.

Streaming

Route events through Kafka, Redpanda, RabbitMQ, NATS, Cribl, and managed streaming platforms.

Databases

Send or migrate telemetry from PostgreSQL, MySQL, MongoDB, Redis, SQL Server, and Elasticsearch.

Parseable Auto Instrumentation

Collect Kubernetes logs, metrics, traces, and events with Parseable-managed instrumentation.

Security

Bring security events from Auth0, Falco, Trivy, and related sources into Parseable.

eBPF

Capture kernel-level observability signals with eBPF-based tooling.

GPU

Collect GPU metrics and accelerator telemetry.

CI/CD

Capture telemetry from GitHub Actions, Jenkins, GitLab CI, CircleCI, ArgoCD, and Terraform.

Infrastructure

Collect telemetry from infrastructure services such as Traefik and Windows Server.

Cloud

Ingest logs and events from AWS, Azure, Google Cloud, and Fly.io.

Programming Languages

Send telemetry directly from application code in Python, JavaScript, Go, Java, Rust, .NET, PHP, and Ruby.

You can ingest data to Parseable in JSON format over HTTP(s). This means that any log agent, metric collector, or tracing library that can send data over HTTP in JSON format can be used to ingest data into Parseable. For log data you can use the HTTP output plugins of all the logging agents/shippers. You can also directly integrate Parseable with your application via the ingestion API.

Parseable also supports OTel native data ingestion via Protobuf over HTTP. OpenTelemetry-compatible agents and libraries can send logs, metrics, and traces to the signal-specific OTLP endpoints: /v1/logs, /v1/metrics, and /v1/traces. Parseable derives the telemetry signal type from the endpoint path and uses X-P-Stream to choose the destination dataset.

Detailed reference

For HTTP headers, schema behavior, log processing, batching, timestamps, staging, and production planning, see the Ingestion Reference.