What I'm looking for is a full stack trace of a request, and how it progressed through their platform, through pops, Argo, Caches, etc. Akamai and others have tools like this, and it makes it much easier to debug gremlins on the inside.
From the docs:
"If your Workers application is returning an 1101 error code, your code is throwing an exception. You can catch the exception in your code using a try/catch block:"
That's great, but you end up just returning those details in a header or sending them somewhere else. We have to catch errors and send them to our backend for logging so we can debug them at a later point.
This doesn't help you debug things like sub-requests from the Worker or how they interact with other Cloudflare features like Cache.
We're working on this tracing tool as we move things like Page Rules and Rate Limiting into the same engine that runs Firewall Rules. Lots of advantages of using the same Rust-based engine/syntax to let customers express their configuration rules, e.g., adding rule-based alerting and combining different types of filters and actions.
Focus so far in the design process has been how requests get evaluated against a list of Custom and Managed Rules but if you imagine a world in which everything is a rule (incl. routing to/firing a Worker) it becomes tractable to do what you're asking about.
We'll be in discussions with the Workers team about how to best illustrate the handoff to Workers and what happens downstream: cache, origin fetch, etc.
Kenton, not exactly topic-related, by I am deeply grateful for what you did in Sandstorm. Cloudflare or not, you a great guy! And I am sure you still have a bunch of magic tricks in your pocket.
Does `wrangler tail` help with this?
https://developers.cloudflare.com/workers/about/tips/debuggi...