[
https://issues.apache.org/jira/browse/FLINK-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012814#comment-17012814
]
Dawid Wysakowicz commented on FLINK-15431:
------------------------------------------
If I understood the {{watermarkLaterncy}} metric correctly it applies to all
operators that deal with watermarks, which means all operators. However after a
second thought, I am not sure if it makes sense to add a special metric for
that. We already report {{currentInputWatermark}}. We can calculate the latency
on the receiver side as {{clock time - currentInputWatermark}}.
I'm inclined to add only the {{numLateRecordsDropped}} metric.
> 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)
