[
https://issues.apache.org/jira/browse/FLINK-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20571:
-----------------------------------
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.
> Add dynamic open/close LatencyMarksEmitter to support online debug and
> monitoring
> ---------------------------------------------------------------------------------
>
> Key: FLINK-20571
> URL: https://issues.apache.org/jira/browse/FLINK-20571
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Reporter: zlzhang0122
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Now, flink has provided latency metrics to monitor the latency, but this
> function mainly used in debugging contexts rather than in production contexts
> because of throughput effect. If we provider an api that can dynamic
> open/close this function, then we can monitor the online data latency and
> find out the performance bottleneck in time without restart the job, which
> maybe helpful for online debug.Â
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
