Comment by chickensong
4 days ago
You could have the log shipper filter events and create a separate audit stream with different behavior and destination.
4 days ago
You could have the log shipper filter events and create a separate audit stream with different behavior and destination.
Really, have sane log message types and include ”audit” as one of them.
Log levels could be considered an anti-pattern.
I like this. But doesn't it make sense to categorize en Exception thrown as an erro somehow? And a new user registration as an email info?
Perhaps use tags then?
Some kind of ”Error” is of course one of the sane message types. ”Warning” and ”info” might be as well.
”Verbose”, ”debug”, ”trace” and ”silly” are definitely not, as those describe a different thing altogether, and would probably be better instrumented through something like the npm ”debug” package.