[
https://issues.apache.org/jira/browse/FLINK-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9652:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor metrics sink
source (was: auto-deprioritized-major metrics sink source stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Metrics for upstream and downstream
> -----------------------------------
>
> Key: FLINK-9652
> URL: https://issues.apache.org/jira/browse/FLINK-9652
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Godfrey He
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> metrics, sink, source
>
> Flink can get metrics from source to the next operators，but can not get the
> total input/output metrics from web UI, which is inconvenient for user to get
> the records status for job.
> # Upstream and downstream metrics is import for troubleshooting.
> # No source input metrics, making many users considered that no kafka input
> at all, and Flink or Flink program might have some error. The same problem
> for the sink output metrics.
> # For some one operator job(just source and sink in the same operator
> chain), user cannot see any stream metrics, unless adds an keyBy operation,
> which will print the source output metrics.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
