Log structured things

I am choosing between loguru or structlog for a new project. I’ve settled now on loguru, but there is one thing that really bothers me is how to log structured objects like dicts.

I found https://github.com/Delgan/loguru/issues/2, which ended up being labeled as wont-fix.

Just throwing it out, but before I start making a PR for an idea, what is the thoughts about something like this for a solution:

• Using pipe for structured logs, example a_dict | logger.info('message here')
  • We can use the pythons __ror__ function to implement something that looks like a unix-pipe
  • logger.info can work as normal, no api changes
  • The structured log can be handled by a function, a serializer to make it into a log-line
• Maybe also a_var = some_func() | logger.info('a_var assigned')
  • If the logger/pipe construct returns the output back, this idea can be used in normal assignments as well.

I didn’t start to write much code yet, but I think this might be possible to implement.

Thoughts?

[Delgan]

@xeor @benhowes Good news: loguru now supports “structured logging” out of the box!

The **kwargs arguments are automatically added to the extra dict. This can be disabled using .opt(capture=False). 👍

[Delgan]

@benhowes I intentionally chose not to have any “magical” arguments. The logging functions must matches the behavior of str.format(*args, **kwargs), nothing more, nothing less. There is one special case that happens if opt(record=True) but this is the only one. Special cases should be kept to a minimum in order to avoid possible edge cases like logger.info("Value: {bind}", bind=123).

If you’re worried about the overhead introduced by bind(), don’t be. 🙂 There are things internally that are quite heavier when a message is logged. Hopefully, it will be drastically improved once I find time to re-implement it in C.