Why we built TQL instead of just teaching everyone SQL
ClickHouse and Postgres have different aggregation models, different date functions, different everything. Here's why one query language beat two dialects.
Engineering write-ups, case studies, and product thinking from the team building Trasys — mostly about the failure modes nobody warns you about.
ClickHouse and Postgres have different aggregation models, different date functions, different everything. Here's why one query language beat two dialects.
Cost drift, latency creep, and quiet hallucination spikes rarely cross a threshold. This is the case for anomaly detection that doesn't need one configured.
A walkthrough of the incident workflow — alert rule, escalation, Debugger — that took response time from over an hour to under ten minutes.
Why every dashboard in Trasys ships with a plain-English view and a raw-data view, and how we decided what belongs in each.
The waterfall model behind Traces, and how span-level timing surfaces the one hop actually responsible for a slow request.
Groq, Anthropic, OpenAI, and Google each report cost differently. Here's how AI Monitoring normalizes it into one number your finance team can read.