automatic logging backoff during erchef crash loops
Open
Nobody has claimed this yet.
Status: To be prioritized
Triage: Confirmed
Type: Enhancement
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
In the event that backend goes down on a busy Chef Server cluster we commonly see disk I/O on the FE's go through the roof due to bifrost/erchef/nginx logging. I don't know how feasible it is, but it'd be great if this could be detected and noise reduced.
Contributor guide
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
The issue names bifrost, erchef, and nginx but does not identify files, tests, or an entry point. Start by tracing their logging during backend crash loops and clarify how detection and reduced noise should work; done requires an agreed behavior and coverage for the busy-cluster failure scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100