Hello, is anyone facing the different log behavior...
# best-practices
q
Hello, is anyone facing the different log behavior when upgrading meltano from
3.6
to
3.7
? Back then, with
3.6
, when running sth like
meltano run tap-posgres target-redshift
, the console will show both internal logs from meltano and external logs from meltano plugins (`tap-postgres`/`target-redshift`). But when upgrading to
3.7
, it only shows the internal logs from meltano. So in our use case, the logs from plugins are really important because they're inputs for our monitoring systems. So is there any way to make it work similarly to the version
3.6
? Not sure if this is a dumb question or not. If so, then is there any doc that I can read more about this since I'm new to
meltano
😄 Thank you sirs a lot in advance
1
r
https://github.com/meltano/meltano/releases/tag/v3.7.0
A logging configuration is now automatically added for Singer extractors, loaders and mappers and passed to the plugin at runtime. This improves how the plugin logs are formatted in Meltano's own logs.
Specifically, https://github.com/meltano/meltano/pull/9077
This will make the plugins adjust to the logger's log level, which is set globally by
--log-level
or on the specific logger in
logging.yaml
.
ty 1
👍 1