Your support data is in ClickHouse. Altor queries it automatically.
When a ticket arrives, Altor runs the ClickHouse queries your engineers would write - error rates by customer, latency percentiles, failed request patterns - and delivers the diagnosis before your agent finishes reading the ticket.
What Altor queries in ClickHouse
Altor generates and executes targeted ClickHouse queries for each ticket, pulling exactly the data needed to diagnose the reported issue:
- •Request logs - error rates, status codes, response times by customer_id and endpoint over the relevant time window
- •system.query_log - slow queries, resource-intensive operations affecting the reporting customer
- •Custom event tables - whatever usage or behavioral data your product tracks per customer
- •Ingestion and pipeline tables - for data infrastructure products reporting missing or delayed data
- •Billing and usage tables - metered consumption reconciled against invoice line items
tickets diagnosed via ClickHouse queries at Portkey
from ticket to ClickHouse-backed diagnosis
ClickHouse queries typically needed per investigation
queries your support team writes manually
"Our tickets are investigations, not FAQs. Nobody else could even attempt to answer them automatically. Altor can because it queries our actual production data."
How the ClickHouse integration works
Setup takes under 30 minutes. Altor connects to your ClickHouse instance with read-only credentials, learns your schema, and begins querying on the first ticket.
You control which tables Altor can access. Most teams grant access to request logs, error tables, and usage data - keeping payment and PII tables off-limits.
See Altor query your ClickHouse during a live ticket
We connect to your ClickHouse instance and diagnose a real ticket in 2 minutes. US hours.
Get weekly support engineering insights
Opens your email app with your address prefilled.