You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project that is a simple web service developed with Vercel api directory—note, it's not the Next.js project, just a couple of individual functions.
Now, some background: one of my functions is doing a lot of web requests. It runs reasonably fast locally (14s), but times out in Vercel (there's a hard limit of 60s). So, the function logs a lot of intermediary messages, and I want to monitor them as it runs.
Now, with Vercel itself, I can only see the short tail, and only after the HTTP request completes.
So, I have set up Vercel integration, created the Logflare source, set up logs drain, converted all console logs in my app to pino, and set up pino with this lib like this:
Hi there!
I have a project that is a simple web service developed with Vercel
api directory
—note, it's not the Next.js project, just a couple of individual functions.Now, some background: one of my functions is doing a lot of web requests. It runs reasonably fast locally (14s), but times out in Vercel (there's a hard limit of 60s). So, the function logs a lot of intermediary messages, and I want to monitor them as it runs.
Now, with Vercel itself, I can only see the short tail, and only after the HTTP request completes.
So, I have set up Vercel integration, created the Logflare source, set up logs drain, converted all console logs in my app to pino, and set up pino with this lib like this:
Unfortunately, I don't get the individual logs in my logflare stream. Is this the reasonable thing to expect?
I get the build logs and the lambda calls logs. Inside that are unparsed pino messages. Trimmed the same way Vercel does it:
The text was updated successfully, but these errors were encountered: