SecurityInsight settings · Settings > Guards
First collection: restarts of a failed step
| Key | SI_Pro_Pipeline_FirstRunRestarts |
|---|---|
| Where | Settings > Guards (safety checks) > Data-quality warnings |
| Type | int |
| Default | 2 restarts |
| Edition | pro |
What it does
On a new install's first collection, a step that fails or is stopped is started again at once and carries on from what it finished, this many times. After that the run ends with a warning that names the step and who must act.
When set
Higher tries more often before the first collection ends with a warning; 0 means a failed step is not started again. Only the steps that collect, correlate and load the web app are started again -- never a step that writes to a CMDB, to ServiceNow or to a ticket. It has no effect after the first complete collection.
When blank or default
Left blank, the default applies: 2 restarts
Risk and how to reverse it
0: a step that fails on a new install's first collection is not started again, so the first data arrives a run later. Higher: a step that cannot succeed is tried that many times more before the warning. Nothing is written to a CMDB, to ServiceNow or to a ticket by a restart, and nothing is closed. Reversible at once; it applies from the next run and only until the first complete collection.
Requires
A SecurityInsight Pro licence.
Recommended
Keep the default. Change it when: Leave it at 2. Set 0 only when a failed step of the first collection must be looked at before anything is started again.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack