Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-90436

Ability to track resumetoken postion of a stream processor

    • 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

            Assignee:
            mayuresh.kulkarni@mongodb.com Mayuresh Kulkarni
            Reporter:
            mayuresh.kulkarni@mongodb.com Mayuresh Kulkarni
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: