[KAFKA-921] Expose max lag mbean for consumers and replica fetchers - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 0.8.0
Fix Version/s: 0.8.0
Component/s: None
Labels:
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

- Sort By Name
- Sort By Date
- Ascending
- Descending

KAFKA-921-v3.patch
30/May/13 23:56
5 kB
Joel Jacob Koshy
KAFKA-921-v2.patch
29/May/13 18:37
3 kB
Joel Jacob Koshy
KAFKA-921-v1.patch
28/May/13 21:42
5 kB
Joel Jacob Koshy

Activity

People

Assignee:: Unassigned

Reporter:: Joel Jacob Koshy

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 28/May/13 21:38

Updated:: 31/May/13 17:45

Resolved:: 31/May/13 17:45