You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Johannes Wienke (Jira)" <ji...@apache.org> on 2019/10/04 12:49:00 UTC
[jira] [Updated] (AIRFLOW-5594) Remove excessive logging for
connections
[ https://issues.apache.org/jira/browse/AIRFLOW-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Wienke updated AIRFLOW-5594:
-------------------------------------
Priority: Minor (was: Major)
> Remove excessive logging for connections
> ----------------------------------------
>
> Key: AIRFLOW-5594
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5594
> Project: Apache Airflow
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.10.5
> Reporter: Johannes Wienke
> Priority: Minor
>
> Currently, acquiring a connection with the {{get_connection}} method in {{BaseHook}} always logs a message with info level of the format:
> {noformat}
> [2019-10-04 10:18:35,845] {{base_hook.py:84}} INFO - Using connection to: id: xxx. Host: xxx, Port: xxx, Schema: xxx, Login: xxx, Password: XXXXXXXX, extra: {}
> {noformat}
> I am using stored connections to construct the environment variables for docker tasks that are being run. That means, connections have to be accessed each time a DAG is being refreshed / parsed. Due to this message being logged with level INFO, this results in a huge amount of log volume on our airflow installation.
> To my mind, a debug message would be sufficient for this one single message that is printed each iteration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)