Just to clarify the scope and objectives @adriatic this effort is to help with serverless api logging – not browser-side user tracking or exception reporting. Those are very important features to once apps go to production and need monitoring, but for this I was looking for a solid logging library that solved some main problems when in serverless, namely your logs “don’t go anywhere”/ephemeral and are not formatted nicely. Vercel does support log drains but you still need a library to log your messages (warnings, errors, etc).
When logging via console in Netlify or Vercel in your api, these logs are ephemeral. There isn’t a good way to just log certain level events (like warns or errors but not trace or infos).
- log levels (log just warn and above in prod)
- redaction (hide pwds or tokens)
- easy to read output (both in dev and up in cloud)
- support logging to external services (logFlare or Datadog or Papertrail etc) but service-agnostic (ie, you can chose your logging service if you want it persisted and searchable)
- Here’s a list of pino supported transports but note that not all can work in serverless
- etc
Bugsnag, LogRocket are also useful on the api side, but really helpful on the web/browser side to monitor user interaction and errors.
Even with the api side logging, you can still setup LogRocket on a per project basis. But I can see Redwood offering cookbooks or setups with some opinionated choices in the future.
Definitely is helpful to know which of these is most wanted.
BTW - LogRocket recently wrote about Pino: