From 44e281f13ed3ea28818de2f8da02178337ea94dd Mon Sep 17 00:00:00 2001 From: Derek Date: Fri, 20 Nov 2026 14:40:43 +1100 Subject: [PATCH] docs(architecture): fix the pressure trigger docs The architecture page implies that dfe-infra's pressure trigger scales the stage. The scaling_pressure gauge stays at 0 when Vector runs. Nothing feeds the gauge a component. CPU does all the scaling. Update the page to explain why the pressure trigger doesn't scale the stage and link to #117. --- docs/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture.md b/docs/architecture.md index 0f5d4f6..9d4346a 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -159,7 +159,7 @@ You write the `transforms:` and `enrichment_tables:` blocks. The supervisor gene | Docker `single` | On by default. One instance per source that binds a Vector transform | | Kubernetes, every profile | When a deployment asks for it. One deployment per source config, KEDA sets replicas | -One Vector runs per pod, and replicas scale out. The released chart scales on CPU. dfe-infra's values add a pressure trigger in `single`, `scale` and `mesh`. Lag isn't a trigger, because it rises when a downstream stage breaks and more pods can't fix that. +One Vector runs per pod, and replicas scale out. The released chart scales on CPU. dfe-infra's values add a pressure trigger in `single`, `scale` and `mesh`, but the gauge it reads stays 0 when Vector runs, so that trigger never scales a pod out and CPU does the scaling. Feeding it is tracked in . Lag isn't a trigger, because it rises when a downstream stage breaks and more pods can't fix that. The chart mounts the config and transform files, and an edit to either rolls the pods. Outside a chart, a transform change hot-reloads. [reference/configuration.md](reference/configuration.md) has the config layers and what the chart fixes.