-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Atlas Streams
-
Fully Compatible
-
Sprint 49, Sprint 50, Sprint 51, Sprint 52, Sprint 53
With the Kafka $source customers can track the position of the stream processor in the topic to understand how far behind it is. Today there is no way to monitor how far behind a change stream $source is in the oplog from being current. We should develop a way to track this lag for customers to monitor and alert on.
The Kafka Connector has the ability to do something like this today with a jmx metrics called
latest-mongodb-time-difference-secs |
https://www.mongodb.com/docs/kafka-connector/current/monitoring/#source-connector-jmx-metrics
- is related to
-
SERVER-90927 Ability to track input position in kafka source
- Closed