airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Campbell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-2253) Adding Airflow CLI instrumentation
Date Tue, 08 May 2018 16:31:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467655#comment-16467655
] 

Kevin Campbell commented on AIRFLOW-2253:
-----------------------------------------

The initidb operation also displayed the error, and it caused the transaction to fail. It
appears that the tables were created successfully, but no data is loaded.

> Adding Airflow CLI instrumentation
> ----------------------------------
>
>                 Key: AIRFLOW-2253
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2253
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Jin Hyuk Chang
>            Assignee: Jin Hyuk Chang
>            Priority: Major
>
> We are trying to improve user experience on Airflow particularly on Airflow CLI where
our user does most of testing in CLI. As a first step, we'd like to instrument user's activity
on CLI.
> Currently, Airflow instruments user activity from web UI via www.utils.action_logger,
but not on CLI and we are trying to instrument user activity from Airflow CLI as well. By
default, we'd like to instrument same as what current behavior from Web UI.
> Should it need different instrumentation, we will provide a registry method to register
callback so that customized instrument can be easily plugged in. (e.g: We have our customized
event topic that already wired with ingestion pipeline. Having pluggable callback, making
integration with customized instrumentation a breeze.)
> Thanks!
> Jin



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

Mime
View raw message