You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/09/09 17:38:20 UTC
[jira] [Commented] (AIRFLOW-494) Add per-operator success/failure
metrics.
[ https://issues.apache.org/jira/browse/AIRFLOW-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477690#comment-15477690 ]
ASF subversion and git services commented on AIRFLOW-494:
---------------------------------------------------------
Commit daa326cb4dc5e367182f344a957b979952731c73 in incubator-airflow's branch refs/heads/master from [~aoen]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=daa326c ]
[AIRFLOW-494] Add per-operator success/failure metrics
Adds metrics for success/failure rates of each operator, that way
when we e.g. do a new release we will have some
signal if there is a regression in an operator. It
will also be useful if e.g. a user wants to
upgrade their infrastructure and make sure that
all of the operators still work as expected.
Testing Done:
- Local staging and make sure that several
operators successes/failures were accurately
reflected
Closes #1785 from aoen/ddavydov/add_per_operator_s
uccess_fail_metrics
> Add per-operator success/failure metrics.
> -----------------------------------------
>
> Key: AIRFLOW-494
> URL: https://issues.apache.org/jira/browse/AIRFLOW-494
> Project: Apache Airflow
> Issue Type: Improvement
> Components: rics
> Reporter: Dan Davydov
> Assignee: Dan Davydov
> Priority: Minor
>
> It would be good to have metrics for success/failure rates of each operator, that way when we e.g. do a new release we will have some signal if there is a regression in an operator. It will also be useful if e.g. a user wants to upgrade their infrastructure and make sure that all of the operators still work as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)