Product
Search logs at the volume you actually produce.
Filter service, severity, and attributes across retained datasets. Surrounding context stays in the same query path—no archive restore as the default investigation step.
service:payment-apiseverity:errorlast 15m
2026-09-14 14:32:09ERRORpayment-api Request to payment provider timed out after 5002ms
2026-09-14 14:32:08INFOcheckout-api POST /api/checkout 200 187ms
2026-09-14 14:32:07WARNauth-service Authentication retry for user_id=8f24c
2026-09-14 14:32:06INFOedge GET /health 200 4ms
2026-09-14 14:32:05ERRORpayment-api Request to payment provider timed out after 4988ms
Built for investigations
Column-oriented storage, compression, and data skipping keep scans on billions of events practical. You ask questions in LogHouse or from tools you already run—without operating the database underneath.
FAQ
Is this full-text search like Elasticsearch?
LogHouse is built for analytical log queries: filters on attributes, time, and message patterns at high volume. It is not positioned as a general document search engine.
Can I query from Grafana?
Yes. Grafana can be connected as a query frontend. You can also search in LogHouse and via the HTTP API.