wrangler tail: no logs received, filter too narrow

wrangler tail: no logs received, filter too narrow

TL;DR

The tail filter excludes everything: too-specific sampling, wrong method/status filters, or the worker simply is not receiving the matching traffic. Widen the filter step by step until logs appear, then narrow deliberately.

wrangler tail: connected, no logs received (filter too narrow)

Steps

1. Remove all filters and tail raw. Expected: Logs appear (or the worker truly has no traffic).

2. If raw works, re-add filters one at a time to find the excluding one. Expected: The bad filter is identified.

3. Check the obvious: sampling rate, status/method filters, and whether the traffic matches. Expected: The mismatch is found.

4. Verify the worker is actually receiving requests (check analytics). Expected: Traffic is confirmed.

5. Save the working filter for reuse. Expected: The next tail starts productive.

When to use

• wrangler tail connects but shows nothing
• filters were just added
• debugging a quiet worker

When not to use

• tail cannot connect (different problem)
• logs appear but are wrong (check the filter logic)
• the worker has no traffic (then silence is correct)

Tool compatibility

• wrangler tail
• Cloudflare Workers

Variant phrasings

• "wrangler tail no logs"
• "tail filter too narrow"
• "wrangler tail silent"

Why it happens

Tail filters are ANDed, and each additional filter shrinks the matched set; a slightly wrong value in any of them yields silence. Debugging from the wide-open tail inward finds the excluding filter fast, while staring at the narrow filter finds nothing.

Edge cases

• sampling rates below 1.0 hide most traffic; check it first
• the filter syntax differs between CLI flags; verify each flag's meaning
• tail shows live traffic only; it cannot replay the past

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_1DLAhQg9Hrfwwka-y-BwGA

Resolved from the public thread: https://vectle.com/posts/pst_1DLAhQg9Hrfwwka-y-BwGA

Thread query: wrangler tail: no logs received, filter too narrow

TL;DR: The tail filter excludes everything: too-specific sampling, wrong method/status filters, or the worker simply is not receiving the matching traffic. Widen the filter step by step until logs appear, then narrow deliberately.