You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally created by @vischous on 2021-07-16 22:27:20
Could we get logging documentation and best practices?
I spent a few hours diving into this today. It took me that long because I refused to read the advanced logging section in python for some silly reason. But to the point
Maybe we could tell everyone they could specify a LOGGING_CONF_FILE in their environment variables if they need debug logging. With an example or two?
Context:
I want debug logging, and I need to turn on debug logging sometimes in production but there's PII data in the logs so I can't output them all the time.
I have a custom target with some custom classes that are using logger.debug("yadayada") and I was manually adding the logging configuration to see this data. In production I need a better way than this (LOGGING_CONF_FILE is one way)
Subtopics (curated by AJ)
logging.conf: We can document how works, how to set and give examples for users/devs to utilize this.
Changing log level for particularly noisy operations in the SDK.
For high-cardinality parent-child relationships, the "starting" and "stopping" section of each partition context can be 10+ times per second.
For high-cardinality parent-child relationships, Singer INFO metrics also can be noisy if emitted after each stream.
Within a Meltano logging.conf, we might want separate control of the SDK vs Meltano itself.
Pretty-printed exceptions, ideally togglable.
The text was updated successfully, but these errors were encountered:
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.
Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/170
Originally created by @vischous on 2021-07-16 22:27:20
Could we get logging documentation and best practices?
I spent a few hours diving into this today. It took me that long because I refused to read the advanced logging section in python for some silly reason. But to the point
I believe https://github.com/transferwise/pipelinewise-singer-python/blob/master/singer/logging.conf is where the majority of the logging configuration is coming from.
Maybe we could tell everyone they could specify a LOGGING_CONF_FILE in their environment variables if they need debug logging. With an example or two?
Context:
Subtopics (curated by AJ)
logging.conf
: We can document how works, how to set and give examples for users/devs to utilize this.INFO metrics
also can be noisy if emitted after each stream.logging.conf
, we might want separate control of the SDK vs Meltano itself.The text was updated successfully, but these errors were encountered: