SecurityInsight settings · Settings > Schedules & what runs
Maximum queue-driven workers
| Key | SI_Bootstrap_KedaMaxReplicas |
|---|---|
| Where | Settings > Schedules & what runs |
| Type | int |
| Default | 30 workers |
| Edition | Community |
What it does
The most worker containers that may run at the same time per engine when queue-driven scaling is on.
When set
Higher finishes large collections faster but runs more containers at once, raising peak cost and load on the source APIs. Has no effect unless queue-driven scaling is on.
When blank or default
Left blank, the default applies: 30 workers
Risk and how to reverse it
Changes when or whether jobs run: a job that does not run leaves its data older until it runs again. Reversible at once; nothing already collected is changed.
Requires
Nothing else.
Recommended
Keep the default. Change it when: Only with queue-driven scaling, to speed up very large tenants or cap cost.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack