Operations | Monitoring | ITSM | DevOps | Cloud

Honeybadger Insights is pretty great. It's even greater when you connect it to Cloudflare and start shipping logs directly from Cloudflare Workers to Insights. If you're already using Cloudflare to distribute your applications, it's easy to set up. Cloudflare Workers logs capture what your application is doing at the edge: console.log() output, uncaught exceptions, and system-generated logs for each request.

AI-powered apps are hard to debug without observability. From one run to another, AI produces different results, goes down different paths, and you’re none the wiser as to why it’s happening. Agent Tracing bridges the gap between prompt, tool calls and final output, all within the context of your app. If things break (it always does at some point, we know from experience), you get everything in one complete trace.

Why does a checkout or login take several seconds when CPU and memory look normal on every server? In microservices, one click can travel through a long chain of components before the user sees a response. Any one of them can hold the request up, and server graphs won't tell you which. Logs show what each service recorded. Metrics give you averages. What's missing is the path one request took and the place it lost time, and Jaeger tracing records exactly that.

A checkout request leaves the browser and touches seven services before anything comes back. Seven dashboards light up. Every one of them reports a healthy number for its own service, and every one of them is telling the truth about a different slice of the work. Nobody measured the request. That gap is what pushed tracing in beside metrics and logs as a core signal of observability. In this blog, you will: By the end you will open a trace and say where the time went.

MCP server monitoring guide: spans, metrics and logs to record for tool calls, why failed tools look healthy, and how to trace requests from client to server. Sejal Pandey works on content and growth at Last9, writing about observability, reliability, and SRE practices.

If a checkout slows down or an API call fails, why can the cause stay hidden for so long while every service dashboard looks fine? One customer click in a microservices setup may hit a gateway and a few backend services first, then a queue or a database. Every hop logs its own events, yet none of those logs points back to the original request. Distributed tracing was created to solve exactly this. Zipkin arrived early, as one of the first open-source tracers.