[KAFKA-304] Monitoring and troubleshooting Kafka Connector Created: 22/Mar/22  Updated: 28/Oct/23  Resolved: 16/Aug/22

Status: Closed
Project: Kafka Connector
Component/s: None
Affects Version/s: None
Fix Version/s: 1.8.0

Type: Epic Priority: Unknown
Reporter: Esha Bhargava Assignee: Maxim Katcharov
Resolution: Fixed Votes: 2
Labels: TSPR, size-large
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Quarter: FY23Q2
Case:
Start date:
End date:
Calendar Time: 4 weeks
Scope Cost Estimate: 3
Cost to Date: 3
Final Cost Estimate: 3
Cost Threshold %: 100
Detailed Project Statuses:

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


 Description   

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]



 Comments   
Comment by Githook User [ 21/Jul/22 ]

Author:

{'name': 'Maxim Katcharov', 'email': 'maxim.katcharov@mongodb.com', 'username': 'katcharov'}

Message: Add JMX statistics for timings and counts

KAFKA-304
Branch: stats
https://github.com/mongodb/mongo-kafka/commit/302112999a3abddb717d86325ef9d597380d4794

Comment by Githook User [ 20/Jul/22 ]

Author:

{'name': 'Maxim Katcharov', 'email': 'maxim.katcharov@mongodb.com', 'username': 'katcharov'}

Message: Add JMX statistics for timings and counts

KAFKA-304
Branch: stats
https://github.com/mongodb/mongo-kafka/commit/b97b75e7529ffd9032d4555e4cde36195bef8738

Generated at Thu Feb 08 09:06:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.