Repository navigation
docs: document AGENT_WORKER_COUNT for private location agents - #592
Merged
Merged
Conversation
Since agent v7.0.0 API checks and uptime monitors run on the Go worker pool sized by AGENT_WORKER_COUNT (default 10, max 50). JOB_CONCURRENCY only applies to the Node process handling Browser, Multistep and Playwright checks, and has no effect on the uptime image. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This branch was successfully 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
`AGENT_WORKER_COUNT` was only documented in the internal go-runner README. Since agent v7.0.0, API checks and all uptime monitors (URL, TCP, DNS, ICMP) run on the Go agent's worker pool, which this variable sizes. `JOB_CONCURRENCY` is read only by the Node child process (Browser, Multistep, Playwright) and does nothing on the uptime image.
Source: `apps/go-runner/agent/config.go` (`WorkerCount`, default 10, capped at `maxWorkerCount = 50`), `apps/runners/checkly-agent/config/default.js` (`JOB_CONCURRENCY`), `apps/runners/Dockerfile_agent_uptime` (`AGENT_TYPE=uptime`, no Node agent).
Changes:
Reviewer note
The "150MB per API check" figure predates the Go runner and I did not re-measure it. The formula keeps the existing number; if the Go worker footprint is known to be different, that paragraph should be updated.
🤖 Generated with Claude Code