Add new tail command options#2095
Conversation
| - `--search $SEARCH` | ||
| - Filter by a text match in console.log messages | ||
| - `--status $STATUS` | ||
| - Filter by invocation status [possible values: ok, error, canceled] |
There was a problem hiding this comment.
Is this exactly how the values show up in the terminal or are they capitalized? (like 'OK, ERROR, CANCELED')
There was a problem hiding this comment.
They are lowercased.
| ### Dependencies | ||
|
|
||
| Wrangler tail uses cloudflared under the hood. If you are already using cloudflared, be sure you have installed the latest version. Otherwise, follow the [getting started guide](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup) for Cloudflare Tunnel. | ||
| `wrangler tail` will register a tailing session for your Worker, and start a server on `localhost` with a [tunnel](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup) that listens for incoming log requests from your Worker. | ||
|
|
||
| <Aside type="warning" header="Legacy issues with existing cloudflared configuration"> | ||
|
|
||
| For versions before Wrangler 1.19.0, `wrangler tail` will not work with existing `cloudflared` configuration on a local machine. This is a well-known issue, [tracked in this Github issue](https://github.com/cloudflare/wrangler/issues/1844). To update your Wrangler version, refer to the [update documentation](/cli-wrangler/install-update#update). | ||
|
|
||
| To apply a temporary fix, rename your `cloudflared` config to allow `wrangler tail` to work correctly. | ||
|
|
||
| ```sh | ||
| # Move config file when using `wrangler tail`. | ||
| # This will temporarily disable `cloudflared`. | ||
| $ mv ~/.cloudflared/config.yml ~/.cloudflared/config.yml.disabled | ||
|
|
||
| # Move file back when you need to use `cloudflared`. | ||
| $ mv ~/.cloudflared/config.yml.disabled ~/.cloudflared/config.yml | ||
| ``` | ||
|
|
||
| </Aside> | ||
|
|
There was a problem hiding this comment.
@nataliescottdavidson
Kristian and I decided to leave this in temporarily in case people had not updated their wrangler version yet. I'm not sure how user experience goes, but is updating wrangler a pretty common-sense action for people to take or do they hold off on it? Or is the new update of not needing cloudflared make this whole section pointless? If it's pointless, I'm okay w deleting the whole thing.
There was a problem hiding this comment.
Also I know it went to Changes approved state on PR but need Kristian or Luke to look this PR over before merge.
There was a problem hiding this comment.
it's been about two weeks since we updated this page to mention the new version of wrangler. maybe instead of removing this entirely, we can update it to link to the upcoming blog post, and say "We've recently shipped an overhauled version of wrangler tail that removes a dependency on cloudflared. Make sure to update (link) and check out the blog post (link) to learn more." rough stab at copy, but the idea will be instead of giving them a list of instructions, we can start to point them towards the new features as incentive to upgrade
There was a problem hiding this comment.
We need to deprecate the old version. I think that letting folks know that the <1.19.0 depends on cloudflared is good enough if they want to debug an earlier version
| - `--search $SEARCH` | ||
| - Filter by a text match in console.log messages | ||
| - `--status $STATUS` | ||
| - Filter by invocation status [possible values: ok, error, canceled] |
There was a problem hiding this comment.
invocation status is different than http status, right? how would a user run into error/canceled states?
There was a problem hiding this comment.
This one is referring to invocation status.
e190c2a to
bab1474
Compare
4 participants
No description provided.