Who finds out when the data is late?
A partner file is due at 06:00. At 06:00 it is not there. Nothing failed, because nothing ran, so nothing alerted. How expected-rate checks turn silence into a…
Read →Blog
Field notes on OpenTelemetry, integration monitoring, and running it yourself. RSS
A partner file is due at 06:00. At 06:00 it is not there. Nothing failed, because nothing ran, so nothing alerted. How expected-rate checks turn silence into a…
Read →Most integrations lean on a database, and when SQL Server slows, everything on top of it slows too. Here's how to monitor a SQL Server instance with OpenTelemetry…
Read →Node-RED's OpenTelemetry package exports distributed traces per flow — but service-centric monitoring lumps every flow into one service, so one failing flow looks like a platform outage. Two…
Read →Here’s an org chart that exists in almost every large company, told as a small tragedy in three acts. There’s a centralized file-transfer team. They run the platform…
Read →Every OpenTelemetry tutorial starts the same way: a request arrives, spans fan out through your services, a response goes back. Lovely. Now explain that to an EDI flow.…
Read →Every integration landscape we’ve seen is a zoo. Kafka in one corner, RabbitMQ in another, a Debezium connector quietly copying a database, an API gateway in front of…
Read →Before we start: this is a personal opinion piece. No survey data, no analyst quadrant — just my own read on where this is heading, from building and…
Read →There’s a special irony in observability: the moment your systems get loud is the moment they produce the most telemetry — and the most telemetry is exactly what…
Read →There’s a quiet moment in every observability rollout where the incentives flip. In week one, more telemetry means more insight: the first traces answer questions you couldn’t answer…
Read →File-drop integrations fail silently. The sender writes an XML file to a share, the receiver picks it up — and when the receiver dies, nothing errors. Files just…
Read →