Broker connection error should be ERROR not WARNING
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
These broker connection errors should probably be logged at ERROR level rather than WARNING level currently.
Not high priority.
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
Start by locating the broker connection error logging path and compare the current WARNING-level records with the behavior shown in the attached screenshot. Confirm that the affected connection errors are emitted at ERROR level and verify the change with the relevant existing tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100