Repository navigation
Explain load-based Botstopper activation - #539
Open
hnyasingunaydin wants to merge 1 commit into
Open
hnyasingunaydin wants to merge 1 commit into
hnyasingunaydin wants to merge 1 commit into
Conversation
Add a section to the Botstopper how-to that explains how to keep Botstopper enabled but only challenge visitors when the system load exceeds roughly 75% of the CPU cores, using a WEIGH rule on load_1m. Co-authored-by: yasingunaydiin <81875281+yasingunaydiin@users.noreply.github.com>
hnyasingunaydin
force-pushed
the
botstopper-load-based-activation
branch
from
November 7, 2026 11:46
8c28987 to
bd74a7a
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a section Only Challenge Visitors Under High Load to How to Use Botstopper on Hypernode.
It explains how to keep Botstopper enabled at all times, but only challenge visitors when the Hypernode is under pressure (roughly CPU > 75%):
load_1m,load_5m,load_15m) is and why it depends on the number of CPU cores (nproc)WEIGHrule forpost.policy.ymlthat removes weight while the load is lowDENY/CHALLENGErules still apply,load_1mvsload_5m, and load not reflecting I/O or database latency