Anomalous notifications
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Not quite sure what is going on here? Is Burrow going through and analysing from the beginning or something?
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
Review the two screenshots and trace Burrow’s Kafka consumer-lag notification path to reproduce the reported anomaly. Confirm whether analysis starts from the beginning and establish the expected notification behavior; no file or test is named in the issue, so repository exploration is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- observability-sre, stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100