cloudfoundry / cloudfoundry/loggregator-agent-release
loggregator-agent emits many logs per second when doppler does not exist
Open
Nobody has claimed this yet.
unscheduled
- Dominant language
- Go
- Stars
- 14
- Forks
- 34
- Avg merge
- 7h 6m
- Merged PRs (30d)
- 2
Description
When there is no upstream doppler (such as when the firehose is disabled) loggregator-agent emits 5 logs a second.
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
No files or tests are named. Start by reproducing the case where no upstream Doppler exists, then trace the loggregator-agent path that emits the repeated messages; done means the agent no longer emits five logs per second when Doppler is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100