this post was submitted on 18 Apr 2024
3 points (100.0% liked)

JavaScript

19 readers
1 users here now

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] dan@upvote.au 1 points 7 months ago (2 children)

The issue I usually have with these logging libraries is that they often don't handle structured data well, which is something that's commonly needed in a logging library.

For example, it's fine for log entries to be a string when logging to console or a text file, but if you add a sink that logs to a database, service (Sentry, Loki, NewRelic, whatever), or JSON file, you'll generally want some sort of structured data. At the minimum, you'd want the format string (e.g. "Unable to find {id}") and the variables (e.g. {"id":123}) to be stored separately, so that you can get aggregated counts for how often each error is being thrown regardless of the variables.

[–] hongminhee@lemmy.ml 1 points 7 months ago* (last edited 7 months ago) (1 children)

LogTape author here.

LogTape also supports structured logging. Structured values are kept in LogRecord.properties. Please see how to use the JSON formatter.

[–] dan@upvote.au 2 points 7 months ago

Thanks for the details!! Sorry I didn't notice that.