Your support data is in ClickHouse. Let Altor query it.
ClickHouse holds your customer's API logs, event streams, and operational metrics. Today your support engineers write ad-hoc queries to investigate tickets. Altor runs those same queries automatically — every ticket, every time, in 2 minutes.
How ClickHouse data powers ticket investigation
These are the tickets that sit in queue until an engineer has time to investigate:
- •"Error rate spiked for our production workload" — Altor queries ClickHouse for error_count by endpoint, time window, and customer_id to isolate the pattern
- •"Latency doubled on our batch processing endpoint" — Altor queries p50/p95/p99 latency over the last 48 hours, segments by payload size and region
- •"We are seeing intermittent timeouts on reads" — Altor checks query_log for slow queries, MergeTree part counts, and concurrent merge activity
- •"Our event pipeline dropped events between 2-4am UTC" — Altor queries ingestion_log for gaps, checks insert_errors, and correlates with merge operations
ClickHouse tables Altor can query
Altor connects to the systems where your investigation data actually lives:
- •Request/event logs — error rates, latency percentiles, status codes by customer, endpoint, and time window
- •system.query_log — slow queries affecting specific customers, resource-intensive operations
- •system.merges / system.parts — merge activity, part counts, storage health indicators
- •Custom analytics tables — whatever customer-facing metrics your product tracks
- •Billing/usage tables — metered consumption reconciled against Stripe invoices
tickets diagnosed using ClickHouse data at Portkey
from ticket to ClickHouse-backed diagnosis
ClickHouse queries typically needed per investigation
queries your support team needs to write 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."
Why ClickHouse teams get the most from Altor
ClickHouse is the ideal investigation backend: it stores massive volumes of customer operational data with sub-second query performance. The problem isn't that the data doesn't exist — it's that writing the right queries for each ticket takes 15-20 minutes.
Altor knows your schema. It generates and executes the right ClickHouse queries for each ticket automatically — the same queries your best engineer would write, but in seconds instead of minutes.
See Altor investigate a real ticket from your queue
We'll connect to your systems and run a live investigation. Your data, your ticket, diagnosed in 2 minutes during EST or PST hours.
Get weekly support engineering insights
Opens your email app with your address prefilled.