Swallowing all stdout/stderr terminal output

[devinrhode2]

I've noticed that pino-applicationinsights swallows everything into it's writeStream.

If I try to simulate prod locally, and already have a server running on port 3000, server will start, and then immediately crash, next.js will normally print an error message that port 3000 is already in use, the application insights writeStream was not flushing that to stdout.

Maybe it's desirable from a performance perspective to simple capture all stdout/stderr and not let it print to the users terminal.

On the other hand, if server fails to start, or logs are not being sent correctly, then we should send all the logs we've collected to stdout/stderr.

It seems that pinoms is generally a legacy/compatibility package.

pino-applicationinsights Seems to be the weakest link. I think it was built with pino v6 in mind: And the docs there led me to use pino-multi-stream in the first place: https://github.com/ovhemert/pino-applicationinsights/blob/master/docs/API.md

But it turns out, pinoms DOES support pino v7..

If I comment out my whole next-logger.config.js file, then the default logger will print logs to the terminal. So there's something wrong with my Azure ApplicationInsights logger.

This was the fix:

I actually stole the idea from https://github.com/pinojs/pino-elasticsearch docs

We could probably steal the same snippet for docs for this project

[devinrhode2]

For extra context see: https://github.com/atkinchris/next-logger/issues/12

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.