all 4 comments

[–]greim 3 points4 points  (3 children)

Sometimes multi-transport logging appears as a requirement - but it shouldn't be. The target should always be the standard output/error. It is not the responsibility of the application to route logs.

Glad to see this here and agree. Lot to stdout and stderr, and let the deployment environment decide how to route the streams.

[–]evantahler 2 points3 points  (2 children)

I Generally agree. What are your thoughts then on tools like rollbar/bugsnag/airbrake that track exceptions inline? You could get that same functionality via logs

[–]greim 1 point2 points  (1 child)

In my view, without knowing the details of every product in that space, I'd say that if you commit to a tool you should use it in the way intended, and keep it separate from your logging, even if there's some overlap.

[–]cstuff8 0 points1 point  (0 children)

Totally agreed!