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

Expose max lag mbean for consumers and replica fetchers

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.8.0
    • 0.8.0
    • None
    • None

    Description

      We have a ton of consumer mbeans with names that are derived from the consumer id, broker being fetched from, fetcher id, etc. This makes it difficult to do basic monitoring of consumer/replica fetcher lag - since the mbean to monitor can change. A more useful metric for monitoring purposes is the maximum lag across all fetchers.

      Attachments

        1. KAFKA-921-v1.patch
          5 kB
          Joel Jacob Koshy
        2. KAFKA-921-v2.patch
          3 kB
          Joel Jacob Koshy
        3. KAFKA-921-v3.patch
          5 kB
          Joel Jacob Koshy

        Activity

          People

            Unassigned Unassigned
            jjkoshy Joel Jacob Koshy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: