[
https://issues.apache.org/jira/browse/FLINK-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zlzhang0122 updated FLINK-20571:
--------------------------------
Description: 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 can 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. (was: 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 can 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 very helpful. )
> 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: Major
>
> 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 can 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
