[
https://issues.apache.org/jira/browse/FLINK-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-4830:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
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.
> Show latency statistics in web interface
> ----------------------------------------
>
> Key: FLINK-4830
> URL: https://issues.apache.org/jira/browse/FLINK-4830
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Metrics, Runtime / Web Frontend
> Reporter: Robert Metzger
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> With FLINK-3660, we added a metric that measures the latency of records
> flowing through the system.
> With this JIRA, I would like to expose the latency also in the web frontend.
> Therefore, we'll probably need to change the format the latency is reported
> in the metric.
> I think we should show the latencies in two different views in the interface:
> - A global end-to-end latency in the overview of running jobs. This number is
> probably pretty inaccurate, but should give users a first impression of the
> latency characteristics currently present in the job
> - A detailed latency drill-down view, that allows to see how much latency is
> added on average at each operator, for the sources.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
