[
https://issues.apache.org/jira/browse/FLINK-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20833:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Expose pluggable interface for exception analysis and metrics reporting in
> Execution Graph
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-20833
> URL: https://issues.apache.org/jira/browse/FLINK-20833
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Zhenqiu Huang
> Assignee: Zhenqiu Huang
> Priority: Major
> Labels: pull-request-available, stale-assigned
>
> For platform users of Apache flink, people usually want to classify the
> failure reason( for example user code, networking, dependencies and etc) for
> Flink jobs and emit metrics for those analyzed results. So that platform can
> provide an accurate value for system reliability by distinguishing the
> failure due to user logic from the system issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
