Blog
Notes on keeping data pipelines healthy, from the team that reads failure logs for a living.
Blog
-
Why one failure sends you forty alerts
Alerts follow the shape of your DAG, not the shape of the problem. Here is how we group them by cause.
-
What 10,000 automatic fix pull requests taught us
Which failures a machine should fix, which it shouldn’t, and why the test matters more than the patch.
-
Schema drift: the silent failure your tests miss
When a source changes shape, pipelines often keep running and quietly produce the wrong numbers.
-
A calmer on-call rotation for data teams
Data teams copied on-call from software engineering and kept the worst parts. Here is a lighter setup that works.
What we write about
Written by the engineers and customer engineers who build and run Tessel. No guest posts, no sponsored content.
-
Engineering
How root-cause detection, lineage and the fix engine work, including the parts that went wrong first.
-
Product
What we built, why, and what the data from thousands of incidents and fix pull requests tells us.
-
Practice
On-call, freshness promises, ownership and the habits that keep data teams out of firefighting mode.