Uploaded image for project: 'Kafka Connector'
  1. Kafka Connector
  2. KAFKA-304

Monitoring and troubleshooting Kafka Connector

    • Type: Icon: Epic Epic
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 1.8.0
    • Affects Version/s: None
    • Component/s: None
    • Done
    • Monitoring and troubleshooting Kafka Connector
    • 3
    • 3
    • 3
    • 100
    • Hide

      Engineer(s): Maxim

      Summary: The biggest request from technical support is improvements to monitoring and metrics to be used for better troubleshooting. This epic consists of multiple tickets that describe work that could be done to greatly improve the monitoring experience with the Kafka Connector.

       

      2022-08-09: Updated target end date to 2022-09-12

      Status update:

      • All stats implemented and in second round of review

      Rationale for delays:

      • No delays

      Risks:

      • No risks

       


       

      2022-07-26: Setting initial target end date to 2022-08-05
      Status update:

      • Timing and count for Kafka connector metrics in review
      • Exposing monitoring metrics over JMX in progress

      Rationale for delays:

      • No delays

      Risks:

      • No risks

      Show
      Engineer(s): Maxim Summary: The biggest request from technical support is improvements to monitoring and metrics to be used for better troubleshooting. This epic consists of multiple tickets that describe work that could be done to greatly improve the monitoring experience with the Kafka Connector.   2022-08-09: Updated target end date to 2022-09-12 Status update: All stats implemented and in second round of review Rationale for delays: No delays Risks: No risks     2022-07-26: Setting initial target end date to 2022-08-05 Status update: Timing and count for Kafka connector metrics in review Exposing monitoring metrics over JMX in progress Rationale for delays: No delays Risks: No risks

      Summary

      The biggest request from technical support is improvements to monitoring and metrics to be used for better troubleshooting.  This epic consists of multiple tickets that describe work that could be done to greatly improve the monitoring experience with the Kafka Connector.

      Motivation

      Who is the affected end user?

      MongoDB Technical Support, and end-users of the Kafka Connector

      How does this affect the end user?

      Makes it easier to monitor and troubleshoot a MongoDB Connector for Apache Kafka deployment

      How likely is it that this problem or use case will occur?

      its not a problem its an enhancement to make problems less problematic

      If the problem does occur, what are the consequences and how severe are they?

      They cost time which is money

      Is this issue urgent?

      The lack of monitoring has become more of an issue now that the adoption of Kafka Connector is increasing

      Is this ticket required by a downstream team?

      no

      Is this ticket only for tests?

      no

      Cast of Characters

      Engineering Lead: Jeff Yemin
      Document Author:  Robert Walters / Ross Lawley
      POCers:
      Product Owner:  Robert Walters
      Program Manager:
      Stakeholders:

      Channels & Docs

      Slack Channel

      [Scope Document|some.url]

      [Technical Design Document|some.url]

            Assignee:
            maxim.katcharov@mongodb.com Maxim Katcharov
            Reporter:
            esha.bhargava@mongodb.com Esha Bhargava
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              4 weeks