[
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 metrics sink source stale-minor (was:
auto-deprioritized-major metrics sink source)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, metrics, sink, source,
> stale-minor
>
> 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)
