Log Drain: warnings coming through as error level

[aschokking]

Question

Have setup a basic log drain to AWS via a simple Lambda that just relogs the json that it receives.

However I noticed that log lines generated from console.warn that on vercel.com's log viewer are correctly are listed as "Warning" are all coming through the log sync with "level": "error". Is there any way to get this to plumb through correctly or do we need to start annotating the log text itself in some way so it can be filtered correctly after the fact?

Other vercel logs are coming through successfully as warning (like status 404 warnings).

Example

Here's an example event that came through with the wrong level of error.

First in vercel.com's log viewer it's correctly identified as a warning:

But the JSON through the log sync has it as level error:

2024-07-08T15:49:20.050Z	157e50f5-8445-43e2-ae00-d99b13848076	INFO	{"id":"99740996690172045375387938300000","message":"REDACTED","timestamp":1720453753879,"type":"stderr","requestId":"69b8d-1720453753639-74dc56d77ea0","executionRegion":"iad1","level":"error","proxy":{"timestamp":1720453753639,"method":"GET","host":"REDACTED","path":"REDACTED","scheme":"https","userAgent":["Mozilla/5.0 (Windows NT 6.1; WOW64) SkypeUriPreview Preview/0.5 [email protected]"],"clientIp":"REDACTED","region":"cdg1","lambdaRegion":"iad1","vercelCache":"MISS"},"projectId":"REDACTED","projectName":"REDACTED","deploymentId":"REDACTED","source":"lambda","host":"REDACTED","path":"REDACTED","environment":"production","branch":"main"}

[github-actions[bot]]

This discussion was automatically locked because the community moved to a new site. Please join us at vercel.community