It gets automatically added, but I’ve tried adding a custom processor to add it manually. It didn’t
It gets automatically added, but I’ve tried adding a custom processor to add it manually. It didn’t make a difference
�Ah, i see, then i dunno, sorry. Thought that it was similar to js where u needed to pass the trace id to logs yourself
ZObservability Logs get disabled every time we deploy a Worker via QuickEdit, which Where is the wrangler.toml file ?. Any chance we could get this fixed, please? 
PSomething I miss in the new Worker metrics is seeing the p50, p75, etc for request duration. I feel like that would be useful more than the p50 and such from wall time, as request duration is what's actually visible to the end-user.
Would love to get more insights in the metrics that actually affect my users
Would love to get more insights in the metrics that actually affect my users
PAlso not sure if it's a bug, but this docs page mentions
Worker metrics can be inspected for up to three months in the past in maximum increments of one week.which seems to outdated, as you can now view up to a month. Also it seems like you can't go past a month in the dash at least, because trying to look further than a month ago gives
Query time range is too long.
PAlso not sure if this is a bug, but clicking the calendar icon in the time range does nothing. I would assume that clicking it would've shown a date/time picker, but nothing happens
PAnother bug (sorry) - The zoom in/out button from the map is overlapping the time range dropdown
Rthanks for all the bug reports, we'll take care of them (quick edit, map component, docs pages should reference 1 month metrics retention)
BNot sure if this is the right channel but approximately how long do metrics take to update, the logs seem to be real time
KHey everyone, how can I implement baselime into my nextjs app hosted on cloudflare pages? I found this example for sveltekit, but nothing for nextjs: https://baselime.io/docs/sending-data/platforms/cloudflare/pages/#sveltekit. I also found this: https://baselime.io/docs/sending-data/languages/next.js/ but i'm not sure how I would change this to work on the edge. Lmk if anyone can help me with this.
Instrument your Next.js applications with OpenTelemetry using the the Baselime Node.js OpenTelemetry SDK
Cloudflare Pages is Cloudflare's app development platform.
AMaybe try the edge logger in a nextjs middlware
We launched Workers Logs to enable Observability for Cloudflare Workers directly in the Cloudflare Dashboard.
Kbut then i'd only be able to log info in the middleware right?
MHey, I was wondering if there is any project in the wild to orchestrate workers in the local environment.
As my app grows, I find myself working with 10-15 microservices each one corresponding to a worker connected to others by service bindings.
This is getting annoying to develop on dev since I need to start as many terminals at once on my localhost and (although they are connecting through each others) it's kinda hard to keep track of all off them,.
I was wondering if there is something like an orchestrator to start all of them in parallel and maybe share logs across a single or nicer interface, I understand this is no small task to develop but if there is already a poject of such I'd love to know and also to contribute to
As my app grows, I find myself working with 10-15 microservices each one corresponding to a worker connected to others by service bindings.
This is getting annoying to develop on dev since I need to start as many terminals at once on my localhost and (although they are connecting through each others) it's kinda hard to keep track of all off them,.
I was wondering if there is something like an orchestrator to start all of them in parallel and maybe share logs across a single or nicer interface, I understand this is no small task to develop but if there is already a poject of such I'd love to know and also to contribute to
Athat's true maybe just a logger util method that takes in router context and returns a logger instance, like
useLogger. That's what I'm using (Nuxt3):KSuper cool, thanks
PHi there,
Can we use Baselime as standalone service without using CF Worker? Also, I just invited my teammates to the platform but they didn't get any emails.
Can we use Baselime as standalone service without using CF Worker? Also, I just invited my teammates to the platform but they didn't get any emails.
IWhat are you logging that is over 128KB? At that point any text you log is likely to run into issues even rendering in the log viewer 
I128KB of text is a lot
RIs there a way for testing purposes to to make a request that goes to a worker in a specific geographic location?
RWe're working on some larger platform changes to support this, but don't have a timeline on it yet
HBarring using something like a VPN, no
SIs there any way to arbitrarily query logs, or is it limited only to viewing through dashboard UI? I'd like to be able find out things like number of requests that resulted in status codes (200, 4xx, 5xx) for a given time frame? Or even just number of log messages matching a filter, etc.
�I believe the quick-copy feature on the logs dashboard has a problem. Instead of the text value,
"undefined" is copied
"undefined" is copied
Ryou'll see some improvements releasing in the coming weeks. check out the new invocations view & send feedback our way!
Rstay tuned (for ~3 weeks)
for now, you'll have to rely on the workers logs filters, but we have a sizeable improvement coming your way.
for now, you'll have to rely on the workers logs filters, but we have a sizeable improvement coming your way.
Rcan you try again? this should be fixed
�tap F5 and now it works, thanks
WLogs should show up after about 2 mins not 30, have you tried the live logs?
Kthe new sidebar when you click on an invocation is very cool
Kis there a way to make invocations the default tab filter?
Ware your invocations lasting 30 mins?
Khi, can I please get assistance on my worker? i'm seeing a huge spike in errors in my monitoring dash, but i don't see any error logs so i can't figure out what's causing the errors
KFYI, i see a bug with the timestamps... the timestamps shown are different from the log. i checked the timestamp in the log and it aligned with the one in the hover view
Kwhat’s the difference between the errors in the monitoring dash and the errors in the logs? I’m not sure why I wasn’t seeing any errors on the logs page
D@kchro3 I also see this bug with the timestamps . The hover popup shows the correct timestamp, and the log line shows 4 days backwards.
I think this requires the attention of someone from cloudflare team
I think this requires the attention of someone from cloudflare team
Ohello, loving the new Invocations tab! thank you for adding it. Just an idea to add country (flag or code) as an additional tab, to quickly see if longer wall time is due to a request being distant from db
Wfix will rollout monday
Wwhat's your account id + script name?
DWorkflows very commonly have many steps, and therefore can have many log lines. Currently observability is limited to 128kb per request. After that, I get this message:
"Log size limit exceeded: More than 128KB of data (across console.log statements, exception, request metadata and headers) was logged during a single request. Subsequent data for this request will not be recorded in logs, appear when tailing this Worker's logs, or in Tail Workers."
I think that due to the nature of workflows, either the limit should be raised, or it shouldn't be counted as a single request for that purpose.
"Log size limit exceeded: More than 128KB of data (across console.log statements, exception, request metadata and headers) was logged during a single request. Subsequent data for this request will not be recorded in logs, appear when tailing this Worker's logs, or in Tail Workers."
I think that due to the nature of workflows, either the limit should be raised, or it shouldn't be counted as a single request for that purpose.
Kcan I DM you?
Ki hope i'm being helpful here, but it would be really nice to be able to group by like you could with Baselime
TI think you can get the location in the request object
only cpu and wall time are exported for now. Wall time is similar to request duration so that might help
only cpu and wall time are exported for now. Wall time is similar to request duration so that might help
WHi there, so all our #baselime queries and alerts have disappeared without any notice, what’s going on? The product pages are still up, but the functionality has disappeared.
Sneed help. Why is there no log when I request?
workers-and-pages-helpNo log display after using static assets
workers-and-pages-helpNo log display after using static assets
KHey, for worker observability, I have disabled the invocation logs, but the logs are still being sent.
Also, is there a way to filter by unhandled exceptions?
"observability": {
"enabled": true,
"logs": {
"invocation_logs": false
}
},
Also, is there a way to filter by unhandled exceptions?
"observability": {
"enabled": true,
"logs": {
"invocation_logs": false
}
},
IIf you handle an exception then it won't appear as "Worker threw exception", so any non-handled exceptions are visible by just filtering for "Worker threw exception"
IAs for invocation logs, are you running any console.log() statements? invocation_logs is only for logs sent by Cloudflare, and doesn't disable console.log() statement logging.