Architecture
One endpoint. ClickHouse underneath.
Send logs through OpenTelemetry or HTTP. LogHouse manages schema, ingest, scale, storage, retention, and query. You do not operate ClickHouse.
Ingestion API · routing · schema · storage · data skipping · retention · patterns
Pipeline
Sources
Applications, Kubernetes, cloud infrastructure, servers, security events.
Ingestion
OpenTelemetry Collector, HTTP API, existing collectors, supported integrations.
LogHouse
Ingestion API, routing, schema normalization, storage, data skipping, retention, patterns.
Consume
LogHouse explorer, Datadog (where supported), Grafana, API, alerts you already run.
No ClickHouse cluster to operate. No shards to size. No retention jobs to manage. LogHouse provides the managed product layer around scalable log infrastructure.
FAQ
Do I operate ClickHouse?
No. LogHouse uses ClickHouse-based analytical infrastructure. You use services, APIs, tokens, and retention—not shards, replicas, or merge settings.
What ingest paths exist today?
The documented HTTP ingest API is the primary path. OpenTelemetry Collector and other agents can export to that API. Grafana and Datadog connections are available as query or workflow integrations, with Datadog federation depending on account support.