Burrow /status/totallag endpoint for all active consumers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Hello, we have a use case to monitor all consumers for lag. Using the /status endpoint, we now have to first retrieve the list of consumers via the /consumer endpoint, and then iterate through the list to configure, say logstash. It would be great to have a unique endpoint for /status.totallag of all consumers, for ease of ingestion into elastic, etc...
We are currently thinking of branching the project to implement this endpoint; anybody interested in the same?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the handlers for the existing /status and /consumer endpoints in Burrow and compare their responses. Define the new endpoint's response for all active consumers and verify that it can be consumed by monitoring tools such as Logstash and Elasticsearch; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- observability, stream-processing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100