klen / klen/graphite-beacon

max_clients limit reached, alerts reset

Open
#120 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
450
Forks
117
PR merge metrics
No merged PRs in 30d

Description

I occasionally see this in the log for one of my metrics. What I noticed as a side affect that it never clears the alert if it was previously in a Warning state, and then goes into normal area, the normal alert doesn't fire, maybe it's the reset alerts?

Is reset alerts related to the max_clients limit reached? Is there a way to increase the size?

`
graphite_beacon stderr | [D 160524 16:32:00 simple_httpclient:125] max_clients limit reached, request queued. 10 active, 1 queued requests.
[I 160524 16:32:00 core:117] Reset alerts
`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the `simple_httpclient:125` and `core:117` log points shown in the report, focusing on the relationship between queued requests, the max_clients limit, and alert resets. Reproduce or inspect the warning-to-normal transition and determine whether alerts clear and fire correctly after the reset; document the relevant configuration or behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.