Lag can not update after alarm
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
When the burrow alerts, the lags do not update at all, so it can not recover and always alerts. After restarting, it recovers.
Here is my configuration:
[storage.mystorage]
class-name="inmemory"
intervals=20
expire-group=604800
workers=20
min-distance=1
[evaluator.mystorage]
class-name="caching"
expire-cache=86400
topic-refresh=120
offset-refresh=30
Something is wrong with my config?
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
Reproduce the alert and recovery behavior with the provided storage.mystorage and evaluator.mystorage configuration, focusing on the intervals, workers, topic-refresh, and offset-refresh settings. Compare lag updates before and after a restart and determine what should allow recovery without restarting. Done means lag values continue updating and the alert clears when the consumer recovers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- observability, stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100