Add a way to simplify cli logging

Simplifying log messages

Currently structured logging can be a bit difficult to read on a local terminal. It is possible to simplify the logging using the logging.yaml, but there is still a lot of extra information that makes it a bit cumbersome to understand what is going on.

As an example in the following log:

{'consumer': False, 'producer': True, 'string_id': 'tap-postmark', 'cmd_type': 'elb', 'stdio': 'stderr', 'name': 'tap-postmark', 'event': 'time=2022-06-11 19:55:20 name=tap-postmark level=INFO message=Tap has custom mapper. Using 1 provided map(s).', 'level': 'info', 'timestamp': '2022-06-11T19:55:20.971174Z'}

It would be great to be able to only print the message:

Tap has custom mapper. Using 1 provided map(s).

Errors

It is also the case when an error occurs. All the extra information makes it quite difficult to understand the error:

[pandemicsyn]

@tayloramurphy no sounds like @JulesHuisman found logging.yaml already and has a sense of what knobs he can turn.

A logger that would only print Tap has custom mapper. Using 1 provided map(s). without other fields probably isn’t very useful in many cases. Especially once we introduce parallel runs. If you run meltano run tap mapper target tap2 mapper target2 its handy knowing things like whether a line was produced by “tap1” or “target2”. Some of it definitely come down to personal preference. We probably just need to be able to support more formatting/structure options out of the box.

Now that run’s been around a while we could also suppress/remove some fields though (e.g. cmd_type).

[JulesHuisman]

@pandemicsyn Thanks for the jq tip, might come in handy.

Having the option to simplify logging further would be great! But the priority of this feature is not that high, we can manage for the time being 😃