For the new worker logs, is there a way to explicity designate which console.log statements should b
For the new worker logs, is there a way to explicity designate which console.log statements should be captured. I feel like the pricing model and how this is integrated to
console.log statements make it a bit weird to use.
I think a way to have balance is to have the logger be in runtime.env instead of hijacking console.log or at least be able to set the logging level at which logs should be captured (e.g only for console.error). This way we can have logging for important things and if we need normal debugging then the live stream logs should include all console.logs.2 Replies
Hi all, can someone confirm to me if logging (both the observability, as well as logpush) is expected to work in preview urls? I got thrown for a loop today because it does not seem to generate any logs, so I couldn't figure out an exception until I promoted the version to a deploy. Is that currently expected? In Pages we didn't have log push, but you could view real time logs even for previews.
I see a lot of log missing too
and the filter on dashboard works incorrectly, sometimes