You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Daniel (JIRA)" <ji...@apache.org> on 2019/05/28 07:31:00 UTC

[jira] [Created] (AIRFLOW-4578) Set Container for Logs to Azure Blob Storage

Daniel created AIRFLOW-4578:
-------------------------------

             Summary: Set Container for Logs to Azure Blob Storage
                 Key: AIRFLOW-4578
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4578
             Project: Apache Airflow
          Issue Type: Improvement
          Components: configuration
    Affects Versions: 1.10.3
            Reporter: Daniel
            Assignee: Daniel


Currently it is possible to set the container that the logs to azure are written to when following the instructions.

However, there remain two issues:
 # The instructions do not mention the lines that need to be changed in the code to effect using a different container.
 # The instructions are completely unnecessary to use blob storage. 

I suggest an update that, when setting {color:#707070}remote_base_log_folder{color} in airflow.cfg, sets this as the Container in Azure. (The current setup forces the user to setup a container called airflow_logs and creates a folder in airflow_logs with the name set in {color:#707070}remote_base_log_folder{color}. This does not appear to be the likely behavior.


Secondly, I suggest updating the instructions such that they resemble the logging setup for both s3 and gcs. Setting three items in {color:#707070}airflow.cfg{color} allows logs to be sent to azure, but it currently requires a container labelled {color:#707070}airflow-logs{color} in the storage account. These three items are:


{color:#707070}remote_logging=True
{color}

{color:#707070}remote_base_log_folder=wasb-<choose a name here>{color}

{color:#a9b7c6}{color:#707070}remote_log_conn_id= <wasb-default>{color}
{color}

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)