`wrangler tail`

[threepointone]

This issue tracks the implementation of wrangler tail.

Usage

• as before, you can run wrangler tail inside a project and it'll start showing live logs for the worker defined in that project.
• additionally, you can pass a script name directly to it, like wrangler tail <name> and it'll tail the worker from your account with that name.
  • Consequently, you won't need to clone the worker's repo, install all dependencies, all just to tail the worker anymore. You should now be able to run npx wrangler tail <name> from anywhere.
• in v2, we only log in the json format, and don't support all the filters yet. We will fix this soon to add pretty mode, and all the filter flags: --status, --header, --method, --sampling-rate, --search.

[geelen]

Just to add one, I made fairly heavy use of the following query in the past:

wrangler1 tail | jq --compact-output '.event.request.url,.logs[].message[],.exceptions'

With wrangler1 being entirely config-driven (not interactive), this worked well:

I mean, it's not as good as actually presenting the log data in a really nice way. But something to think about. Maybe a --raw flag or even a --jq one?

[petebacondarwin]

Closing as the main task here have been completed!! 🚀