SecurityInsight settings · Settings > Schedules & what runs
Queue-driven scaling
| Key | SI_Bootstrap_UseKEDA |
|---|---|
| Where | Settings > Schedules & what runs |
| Type | On / off |
| Default | Off: one scheduled job per engine. |
| Edition | Community |
What it does
Runs the collection engines as queue-driven workers that scale from zero with the amount of work, instead of one scheduled job each.
When enabled
When on, each collection engine gets a scheduler and a worker job that scales up to the worker maximum, speeding up large tenants. Risk analysis and asset tagging are not affected.
When disabled
one scheduled job per engine.
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 for very large tenants where scheduled jobs run too long.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack