Thanks again kian. I submitted a request and will begin to look into Tail Workers!

K

kian•6/19/23, 5:59 PM

It's basically another Worker that receives an array of 'tail' items, which are the logs you see in

wrangler tail

wrangler tail

wrangler tail

wrangler tail and LogPush, that you'd then

fetch

fetch

subrequest onto a logging platform

K

kian•6/19/23, 5:59 PM

The 'durable' alternative would be using a Tail Worker to put those logs onto #queues-beta so that any intermittent issues with the request to the logging platform can be retried

K

kian•6/19/23, 6:00 PM

It's worth noting that Logpush is $0.05/million and Tail Workers would be $0.50/$0.15/million (depends if you use Bundled or Unbound), etc

M

Murder ChickenOP•6/19/23, 6:34 PM

Looking into that now via a Tail worker. Though, adding a

tail_consumer

tail_consumer

tail_consumer

tail_consumer entry to my worker's

wrangler.toml

wrangler.toml

seems to be crashing my Cloudflare dashboard when I go to the worker's

settings > variables

settings > variables

settings > variables

settings > variables configuration to verify if it's actually attached.

M

Murder ChickenOP•6/19/23, 6:35 PM

Been looking into the Event API: https://docs.newrelic.com/docs/data-apis/ingest-apis/event-api/introduction-event-api/#overview

Introduction to the Event API

Intro to New Relic's Event API, which lets you send custom event data to your New Relic account.

M

Murder ChickenOP•6/19/23, 6:52 PM

There's no way to debug a Tail worker, is there. Looks like you cannot tail the Tail worker to see what's going on inside it and I'm assuming there's no way to test locally?

GG @murder_chicken also in the same boat with this. Was hoping to use LogPush with ...

M

Murder ChickenOP•6/19/23, 7:01 PM

As far as I understand it

console.log

console.log

entries are added to an array that's pushed via LogPush. The limit on that per worker invocation is 20 elements in your array. For each array element, the character limit is 300 characters.

MMurder Chicken There's no way to debug a Tail worker, is there. Looks like you cannot tail the...

K

kian•6/19/23, 7:12 PM

Correct

M

Murder ChickenOP•6/19/23, 7:17 PM

Oof.

M

Murder ChickenOP•6/19/23, 7:17 PM

I'm trying to see if I can at least debug it locally by invoking it via the FetchEvent.

C

Cole-kun•6/19/23, 8:44 PM

Is there any problem storing

request

request

in AsyncLocalStorage? I'm looking for a quick and easy way to access

request

request

,

env

env

,

context

context

etc in various other functions/files. For example:

const asyncLocalStorage = new AsyncLocalStorage();
return asyncLocalStorage.run( { request, env, context, workerVersion }, async () => {
(...)

const asyncLocalStorage = new AsyncLocalStorage();
return asyncLocalStorage.run( { request, env, context, workerVersion }, async () => {
(...)

const asyncLocalStorage = new AsyncLocalStorage();
return asyncLocalStorage.run( { request, env, context, workerVersion }, async () => {
(...)

const asyncLocalStorage = new AsyncLocalStorage();
return asyncLocalStorage.run( { request, env, context, workerVersion }, async () => {
(...)

CCole-kun Is there any problem storing `request` in AsyncLocalStorage? I'm looking for a q...

H

Hello, I’m Allie!•6/19/23, 8:57 PM

Theoretically yes, I don’t see why it wouldn’t work, though I would be extra careful with it, since it makes it a lot easier to accidentally read the body twice

HHello, I’m Allie!Theoretically yes, I don’t see why it wouldn’t work, though I would be extra car...

C

Cole-kun•6/19/23, 9:08 PM

Yeah, I can see that. I learned that months ago with a retry logic I had. The first try consumed the body; if it failed, the retry also failed because the body was already consumed.

I don't think I'll hit this issue again, and this store will definitely help keep all the function parameters a bit cleaner. Thanks

J

James•6/19/23, 10:33 PM

await request.json()

await request.json()

await request.json()

await request.json(),

await request.text()

await request.text()

await request.text()

await request.text(), etc.

J

James•6/19/23, 10:33 PM

Check https://developer.mozilla.org/en-US/docs/Web/API/Request/json for example

J

James•6/19/23, 10:50 PM

The JSON you're sending in your POST must not be valid

J

James•6/19/23, 10:50 PM

You can try

await request.text()

await request.text()

await request.text()

await request.text() to get the raw text, but you'll see it's not valid JSON that can be passed to

JSON.parse

JSON.parse

JSON.parse

JSON.parse

C

Cyb3r-Jak3•6/19/23, 10:55 PM

You can do

const url = new URL(request.url)

const url = new URL(request.url)

const url = new URL(request.url)

const url = new URL(request.url) then be able to use a URL object https://developer.mozilla.org/en-US/docs/Web/API/URL so https://developer.mozilla.org/en-US/docs/Web/API/URL/hostname

Ssquadus What is this error?

H

Hello, I’m Allie!•6/19/23, 11:06 PM

Wrangler no longer uses Webpack for bundling

H

Hello, I’m Allie!•6/19/23, 11:07 PM

Also, looks like you are trying to import the wrangler.toml for some reason

J

James•6/19/23, 11:17 PM

The top error you're getting would imply that you're trying to import a

toml

toml

toml

toml file into your worker

J

James•6/19/23, 11:17 PM

The second one is due to changes from wrangler 1 -> 2: https://developers.cloudflare.com/workers/wrangler/migration/v1-to-v2/

Thanks again kian. I submitted a request and will begin to look into Tail Workers!

Similar Threads

Similar Threads

Similar Threads