linkedin / linkedin/Burrow

add owner and partition_Leader

Open
#656 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

burrow_kafka_consumer_partition_lag{cluster="cluster01",consumer_group="group01",owner="1.1.1.1",partition="2",partition_Leader="2.2.2.2:9092",topic="topic01"} 412445
burrow_kafka_consumer_current_offset{cluster="cluster01",consumer_group="group01",owner="1.1.1.1",partition="2",partition_Leader="2.2.2.2:9092",topic="topic01"} 22513

https://github.com/DavidLeeUX/Burrow_kafka

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides sample Burrow Kafka consumer metrics with owner and partition_Leader labels, but names no source file or test. Start by locating the code that emits burrow_kafka_consumer_partition_lag and burrow_kafka_consumer_current_offset metrics, then verify the two labels appear consistently in the output for the relevant partitions.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
observability
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.