Introducing Pitlane Pulse: know before your users do

Today we're launching Pitlane Pulse — our intelligent alerting and anomaly detection layer, built directly into the platform. It's the answer to a question we kept hearing from data teams: how do we know something went wrong before our users tell us?

The problem with reactive monitoring

Most alerting systems work on static thresholds. Error rate above 5%? Send an alert. Latency above 2 seconds? Page the on-call engineer. These rules are better than nothing, but they're blunt instruments. They generate noise when traffic spikes are expected. They miss subtle degradations that never cross a fixed threshold. And they require constant manual tuning as your system evolves.

How Pulse works

Pulse monitors your data streams continuously and learns what "normal" looks like for each metric, each pipeline, and each time window. Rather than comparing against static thresholds, it compares against dynamic baselines — accounting for daily patterns, weekly cycles, and seasonal trends.

When a metric deviates meaningfully from its expected range, Pulse fires an alert with full context: what changed, by how much, when it started, and which upstream events correlate with the anomaly.

What you can monitor

Pulse works across any metric flowing through Pitlane. Pipeline throughput, ingestion lag, query latency, error rates, custom business metrics — if it's a number that changes over time, Pulse can monitor it. You define what matters. Pulse handles the watching.

Alert routing

Alerts route to wherever your team already works. Slack channels, PagerDuty schedules, email, or any webhook endpoint. You can configure different routing rules for different severity levels — a latency spike at 2am goes to PagerDuty, a slower degradation during business hours goes to Slack.

Available today

Pitlane Pulse is available on all Pro and Enterprise plans. Free tier users get access to up to 3 monitors with daily digest delivery. Head to your dashboard to configure your first monitor — most teams are live within 10 minutes.

We built Pulse because we believe data teams shouldn't have to discover problems from their users. Your infrastructure should tell you first.