What is happening here :eyes: I am using `meltanol...
# singer-targets
a
What is happening here 👀 I am using
meltanolabs-target-snowflake
h
looks info level messages from the
snowflake-connector-python
library are polluting your logs. There's probably a way to disable this logger or set the level to
WARNING
in order to mute
INFO
and below levels. I get confused every time I have to mess with logging configs, maybe someone more experienced can chime in.
e
Yeah, those are safe to ignore. I already have a logging config that is used to test the target in CI, so it would make sense to make some adjustments to it, package it with the target and use it as the default. https://github.com/MeltanoLabs/target-snowflake/blob/81f4466422bceb5e84473825b32fdfcaf704a80e/target_snowflake_logging.yaml
h
iiuc, this logging config file needs to be in the tap|target-snowflake project, and not a meltano project where the pipeline is defined and where we run meltano as
meltano run tap-source target-destination
. is that right?
e
There's both options. The default logging config has to live in the tap|target repo and be packaged, you can always override it with SINGER_SDK_LOG_CONFIG.
h
nice! just curious, would that apply the logging config to all the plugins involved in a meltano run, or only the plugins that are built with the singer-sdk? and is there a way to specify a logging config per plugin?
e
Depends on what environment you put it in. In the global
env
it would indeed apply to all sdk-based plugins: https://github.com/edgarrmondragon/meltano-dogfood/blob/6388e77e62595a3014a78baa318b597d9aa35451/meltano.yml#L5-L6