SecurityInsight settings · Settings > Schedules & what runs
Azure job containers in parallel
| Key | SI_Bootstrap_ParallelismAzure |
|---|---|
| Where | Settings > Schedules & what runs |
| Type | int |
| Default | 1 container |
| Edition | Community |
What it does
How many containers the Azure profiling job runs side by side in each run.
When set
More containers split the Azure collection and finish sooner, at higher compute cost per run and more parallel load on Azure APIs.
When blank or default
Left blank, the default applies: 1 container
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 large Azure estates where the job runs too long.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack