
Programmer, data collector, #Bitcoin supporter. Working on @Cloudflare Observability (tweets don't reflect my employer - you know the gist)
England
Joined October 2013
- Tweets1.3K
- Following453
- Followers2.3K
- Likes3.1K
One more thing, a personal one: I've joined our new Observability org!
The goal is simple. Build the best observability platform out there and set the standard for how all cloud platforms should do it. Very excited for this one.
Walshy retweeted
Cloudflare Tracing is now in open beta 🚀
Our teams rely on traces everyday to understand what happens to a request as it moves through our platform. Cloudflare Traces brings that same visibility to you.
✅Get automatic spans throughout the entire request
✅Control what gets traced with trace rules
✅Propagate traces across your stack a la W3C trace context
✅Query traces through our dashboard, SQL API or Cloudflare MCP
✅Export traces to any OTLP-compatible destination
Introducing Cloudflare Traces
Today we're launching Cloudflare Traces, a way for you to get an unprecedented view into requests going through Cloudflare!
Why was a request blocked?
Why did a request fail?
Why was a request slow?
Find out with Traces!
blog.cloudflare.com/cloudfla…
Walshy retweeted
Black box? Consider it observed 🤝
We’re building one observability platform to give you more visibility across Cloudflare services, the entire Workers platform, and even into your origin.
More coming 🤭 drop your wishlist below
Introducing Cloudflare Observability
We've been improving our Observability game in Cloudflare the last 2 years with Workers but now we're making OBS great platform wide!
blog.cloudflare.com/one-obse…
Tons of massive announcements today, I'll go through each of them one by one:
Introducing Cloudflare Traces
Today we're launching Cloudflare Traces, a way for you to get an unprecedented view into requests going through Cloudflare!
Why was a request blocked?
Why did a request fail?
Why was a request slow?
Find out with Traces!
blog.cloudflare.com/cloudfla…
I've been helping customers debug issues for years now and our internal tracing at Cloudflare has always been the best tool for the job. Logs & analytics give a partial story. Understanding _exactly_ what, how and when something happened in a request is vital information
Tracing gives you that. This will let you view exactly what happened in Cloudflare, what rules ran, what was matched, what was changed, what Worker we routed to, did we go to cache, did we go to an upper tier, did we move colos with Argo Smart Routing, etc.
I am sooo fricking excited for this!!
Please try it out, let me know any issues or feedback you have!
Also worth noting, this is just the beginning - we have a LOT more to do on Traces - more spans, more info, more services, etc.
Traces is free until December 1st so try it out!
Introducing Cloudflare Observability
We've been improving our Observability game in Cloudflare the last 2 years with Workers but now we're making OBS great platform wide!
blog.cloudflare.com/one-obse…
Tons of massive announcements today, I'll go through each of them one by one:
Walshy retweeted
production errors should not sit in a dashboard waiting for someone to copy a stack trace into a prompt 😿
today we’re introducing Workers Issues -- built-in error monitoring that can send production failures straight to your agent ✨
blog.cloudflare.com/real-tim…
It has been a while since I released stuff in Birthday Week (outside of helping teams with some bits and bobs)
I got some really big goodies coming next week 👀
Welcome to @Cloudflare's #BirthdayWeek. As is our tradition, @zatlyn and I penned our annual Founders' Letter to kick the week off: blog.cloudflare.com/cloudfla…




