Tail Consumer Limitations in `wrangler dev`
I'm building a tail consumer worker for observability/tracing and hit some limitations in
Issues with
-
-
- No way to identify which worker generated the trace
I can see
Question:
Is there a timeline for
For now I'm accepting these limitations in local dev (hoping production will work), but it significantly impacts the local development experience for observability tooling.
Environment:
wrangler devIssues with
tail()-
item.scriptNamenull-
item.wallTimeitem.cpuTime0- No way to identify which worker generated the trace
tailStream()I can see
tailStream()src/workerd/api/tail-worker-test.wd-teststreaming_tail_workerIGNORED_KEYSQuestion:
Is there a timeline for
tailStream()event.timestampFor now I'm accepting these limitations in local dev (hoping production will work), but it significantly impacts the local development experience for observability tooling.
Environment:
wrangler 4.37.12025-09-13
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
