Logs, metrics, traces, incidents and understanding production systems.
Showing 1–10 of 10 dossiers
Cloudflare's logs are no longer an Enterprise-only export capability. Small sites can send 25GB a month to internal destinations and another 25GB externally before overage charges, but destination costs and separate Workers/OTel meters still matter.
Developers can now profile a deployed Worker or a specific Durable Object without reproducing production traffic locally. Captures require an active isolate and measure allocations during the capture window, not retained memory.
The practical change is that debugging a Cloudflare-backed application no longer has to stop at the Worker boundary: one trace can follow security, cache, routing, Worker and origin handling, while logs and traces move toward one query and pricing model.
The new processor can vary sample rates by trace fingerprint and target either a traffic percentage or throughput budget. It is usable now in Honeycomb’s Collector distribution, while the upstream OpenTelemetry component is still working toward alpha.
The endpoint names are staying the same, but the trust chain is not. Teams that pin Sentry certificates or still ship very old Android/Java runtimes need to remove or update those assumptions before Sentry publishes its exact February cutover date.
Investigations has crossed from preview into production and incident.io now reports a large latency improvement in its own measured workflow. The agent continuously reassesses evidence and can hand remediation to coding agents, but the new speed and accuracy figures remain vendor-produced rather than independent.
Sentry has completed a breaking alerting migration. Legacy alert APIs are gone; metric detection now lives in Monitors while notification routing lives in Alerts, and old direct integrations must use the replacement endpoints.
The observe–test–release loop now has explicit economics: Free and Pro include 30,000 captured generations and 25 million system-initiated AI tokens per month; Pro overages start at $1.50 per 1,000 generations and $2 per million LLM Eval/Guard tokens, while ordinary telemetry is billed separately.
supabase-js 2.112.3 materially improves the tracing rollout BTN covered earlier: unsampled requests now still carry traceparent for backend log correlation, tracing misconfiguration produces warnings, and browser Edge Function calls need current CORS headers to admit W3C trace context.
Vercel Agent now works in Slack as well as the Vercel dashboard, combining logs, metrics, deployments and repository context with team conversation before proposing approved actions such as pull requests, rollbacks, configuration changes and cache purges.
Observability helps a team explain what its software is doing before an incident becomes a customer support mystery. Logs, metrics and traces are useful only when they can be collected, queried and retained at a cost that matches the service. Tooling changes often affect both operational clarity and a surprisingly large bill.
BTN follows important developments in telemetry standards, monitoring platforms, incident tooling and observability pricing. Coverage asks whether a change improves diagnosis, reduces lock-in or simply creates more data to manage. It is written for builders who want enough signal to run reliable products without copying an enterprise stack. The useful outcome is knowing what to instrument, what to retain and where a vendor decision changes the economics.
OpenTelemetry and other shared formats matter when they make telemetry easier to move and correlate. BTN also watches sampling, retention and high-cardinality pricing, where apparently small configuration choices can dominate cost. Good observability should shorten an investigation rather than create a second system that needs its own investigation.