R
DX ImprovementWe introduced invocation logs to enrich the context we give you for your Workers invocation with zero instrumentation. However, we have heard from many of you that you want the ability to opt-out of invocation logs because a) added noise for high-volume log producers and b) billing implications. Starting today, you can disable invocation logs by adding the following to your wrangler.toml
You can also disable Invocation Logs via the Dashboard.
Kthat's awesome! if there are any beta testing openings etc, please let me know!
EHi all, we're on CF Enterprise using Workers to manipulate the streaming HTML. We're looking through the logs and noticed that there are multipe entries for the same request. We're trying to find out what the events are in relation to the workers, because the CF documentation is quite thin. We are assuming that the "ParentRayID":"00" is the ingress request which is assigned the RayID of "1234", which then gets ran through a CF worker which creates a new ID "5678" and then returns that response to the client? We are uncertain because the
EdgeResponseBytes is high for both entries. Any ideas? I've chopped some attributes out of the JSON object for brevity
WYeah, so in this case - that one on top is a subrequest made from the Worker and the second one is the parent request
So, request from Googlebot came in, it fired a Worker (log 2) and that Worker made a subrequest to xyz (log 1)
You can match up parent to child by the
So, request from Googlebot came in, it fired a Worker (log 2) and that Worker made a subrequest to xyz (log 1)
You can match up parent to child by the
ParentRayID like you already mentioned
EThanks Walshy, that makes sense. We want to get the RayID which is returned to the client because we're matching the log entries here against a web crawler. For example
Googlebot makes request -> Goes into CF ("RayID: 1234") -> Goes into Worker ("RayID: 5678") -> Response returned to Googlebot ("RayID: ?????")
Googlebot makes request -> Goes into CF ("RayID: 1234") -> Goes into Worker ("RayID: 5678") -> Response returned to Googlebot ("RayID: ?????")
Wthe response would be the highest parent, that's the request from the eyeball and the response to the eyeball
WSo, 1234 in this case
EOk great. In my example above, it is just simple HTML manipulation. Another case is that we are using Workers as a way to check a redirection database too. In those instances, if the origin server is expected to return a 200 status code and we intercept it via the Worker and the Worker changes it to a 301 redirect, would it then use the parent request or the worker request? The end goal is that we are trying to figure out which entry log we need to keep for some analysis of Googlebot. At the moment, having both entries is causing havoc because it's showing a url path can be both a 200 and a 301 at the exact same timestamp
WWorkers are still part of the initial request so the parent - the top level one
ENice, so we can assume if there is no ParentRayID or the ParentRayID = "00" then keep it. All others entries can be disgarded.
LI'm trying to start using worker logs on my project but need a little better control over the sampling. Is there any way that I can programmatically determine whether a requests logs should be sampled or not?
For example - I'm invoking 500MM worker requests a month and each request can log anywhere from 10-1000 messages which adds up very quickly. I don't want to persist
I was thinking I could just log everything and then use a
For example - I'm invoking 500MM worker requests a month and each request can log anywhere from 10-1000 messages which adds up very quickly. I don't want to persist
debugerrorI was thinking I could just log everything and then use a
tailerrorI see, thank you! If I were to use a tail worker and just conditionally
console.logok thanks I'll give it a shot. With tail workers do you know if there is any way to pass it additional events/data or is it just given the results of console.log/fetch/exceptions?
TFor this scenario its always much easier to fix it in your code. We do plan on supporting tail sampling but you should use a logger with log level support 
Xmorning all, I'm trying to disable the
invocation_logswrangler.toml
Xhere's the blocks in wrangler.toml:
X(it would be nice to have even more control over which invocation logs are disabled, ideally I would keep the external requests, but disable the ones for queues and DOs)
TAre you on wrangler 3.88?
Xyeah, 3.88.0
Shi folks, I am new to Cloudflare. Loving it so far. But observability seems to be an issue. I am trying to integrate Baselime using the Edge Logger, but i dont see the logs in my baselime namespace
TOoh it looks like you need to set env.prod.observability.logs to invocation_logs = false
XI had tried it like this too, but had the same problem:
TIs this just in the dash drawer? That looks like a visual bug. It seems to be disabled correctly. Can you DM me your account id and worker name please so I can check for you
Xhmm, I still see the logs, it's not until I manually disable it in the UI that comes into effect, account id sent
Mhey guys - i'm not sure if this is the right channel, but i was wondering how to get the tail worker working in local dev?
TTail doesn't work right now in local dev, best to test it in prod!
Mtoo sad 
But thanks for the reply!
But thanks for the reply!Rwe recommend using Workers Log as its better supported now
-Can I access the content of Workers Log via API the same way as they are displayed in the dashboard?
Kwhat's the retention period for the worker obs logs?
ZAssuming you're talking about workers logs, 7 days as per https://developers.cloudflare.com/workers/observability/logs/workers-logs/#limits
Rnot yet, we're working to make that available!
-Will be waiting for that to happen!
Mare there any alternatives to the js implementations for opentelemetry? i find the existing lib a little heavy for what it provides
TIs there a known issue for workers obs logs not working for Next.js apps running on workers using OpenNext? I've got 2 workers, both with observability enabled, and the one running Next.js does not show any logs.
SAny example on to setup new relic with cloud flare workers to have traces of all outbound comunication?
D+1 that this update ^ is weird, cc @rohin
Not seeing subrequests, wfp requests, tail logs etc in the same place is a step backwards with the new UI
Not seeing subrequests, wfp requests, tail logs etc in the same place is a step backwards with the new UI
Rhey @ebar0n, thanks for surfacing this! We're on it. Hoping to get a quick fix in asap soyou can continue to use real-time logs with WFP. We are also looking into longer-term solutions like using Workers Logs with Workers for Platforms.
Rfor now, the requestId matches the rayID. You can fetch the ray ID from the request header:
const rayId = request.headers.get('cf-ray');
Yhi, wondering if the new workers logs is supporting console.log only or it will also pickup console.error?
IIt should pick up console.error as well.
TI got screwed
TWhy cant I add my newest joiner to the team to Baselime?? @boristane 
TSince the new "cloudflare logs" banner got added
TNo email is being sent when we invite, or when he requests to be added to team
