Monitoring for Buildkite agents
  • Python 80.7%
  • Nix 19.3%
Find a file
Pierre Bourdon c0a34fd002
buildkite-prober: add always-monitored-tags config
This allows forcing certain combinations of tags to always end up in the
pipeline steps, even if no agents are dynamically found to match them.
This way the absence of agents on e.g. certain queues can be detected,
which would cause CI jobs to be unschedulable.

Fixes #2.
2026-02-26 17:07:09 +01:00
src/buildkite_prober buildkite-prober: add always-monitored-tags config 2026-02-26 17:07:09 +01:00
.gitignore Initial prototype version 2026-02-05 23:40:14 +01:00
config.yml buildkite-prober: add always-monitored-tags config 2026-02-26 17:07:09 +01:00
flake.lock Add uv2nix boilerplate 2026-02-04 15:25:56 +01:00
flake.nix Add uv2nix boilerplate 2026-02-04 15:25:56 +01:00
LICENSE Initial commit 2026-02-04 15:00:49 +01:00
pyproject.toml Initial prototype version 2026-02-05 23:40:14 +01:00
README.md Initial prototype version 2026-02-05 23:40:14 +01:00
uv.lock Initial prototype version 2026-02-05 23:40:14 +01:00

Buildkite Prober - Monitoring for Buildkite agents

The AFNix Buildkite Prober checks the health of Buildkite agents - not just using whitebox metrics, but instead through a blackbox "probing" approach. On a regular interval, synthetic test workloads are injected as a test Buildkite pipeline which runs on an agent pool. The result of these test workloads is then used to determine the health of individual agents. This means that an agent technically up but unable to perform any work due to software or hardware issues will properly be reported as down.

See config.yml in the root directory for an example configuration file.