[
https://issues.apache.org/jira/browse/FLINK-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012839#comment-17012839
]
Benchao Li commented on FLINK-15431:
------------------------------------
Yes, we can calculate `watermarkLaterncy` from `time - currentInputWatermark`.
However, IMHO it's more convenient for users if we have watermarkLaterncy
metric directly.
> Add numLateRecordsDropped/lateRecordsDroppedRate/watermarkLatency in
> CepOperator
> --------------------------------------------------------------------------------
>
> Key: FLINK-15431
> URL: https://issues.apache.org/jira/browse/FLINK-15431
> Project: Flink
> Issue Type: Improvement
> Components: Library / CEP
> Reporter: Benchao Li
> Assignee: Benchao Li
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I find that current CepOperator has no metric indicates
> numLateRecordsDropped/lateRecordsDroppedRate/watermarkLatency which is
> available in WindowOperator.
> It is inconvenient for users to debugging and monitoring. So I propose to
> add these metrics in CepOperator too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
