Jani Anttonen

10 seconds is the one I've seen used most. Might want to add that on a later date as the default.

Hi! Sorry for not answering earlier. I have a hunch that the issue is probably "caused" by the latest patch, but has been there for a while, just in another...

A fix that works as of now is to switch from protobuf to JSON / disable batching for protobuf.

The library should most definitely throw an error if any logs have a null value as a timestamp. Probably even move towards a configuration where there's `replaceTimestamp: true` by default...

@nort3x Yeah, seems to be a duplicate issue. Suggestion: Remove the `replaceTimestamp` configuration option and use user given timestamps if present, otherwise generate our own. How would that sound?

Yes, it can be used with any javascript project. :)

Oh, you're right. This happens because that API is not available in Javascript, only Nodejs. This could be an easy fix, though. Could be fixed by using the url constructor...

There's a patch I haven't tested out yet: https://github.com/JaniAnttonen/winston-loki/commit/f863f2a4b107675d285b51a4fa2c5fdb4ba4ffa9

Just an automatic publish action on GitHub could do as well. :)

To my knowledge, it's configurable in winston itself – there's a filter for what levels get sent to transports. So, all these should work (considering you enable silly logs to...