Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
Sets the maximum number of probes a node can pick up during one run, with a default limit of 20. |
| What area does it affect? |
ECC probe processing |
| What does the default mean? |
No default value is stated in the ServiceNow documentation. |
| When should you review it? |
Review when adjusting the number of probes nodes process in each run. |
Property record
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name |
glide.eccprobe.max_queued_probes_per_run |
| Type |
Not stated |
| Application |
Not stated |
| Default value |
Not stated |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... of time (seconds) the AWS request attempts to retry. Maximum value: 2046 seconds. Setting negative values is equivalent to setting the maximum value. • Type: integer • Default value: 30 glide.eccprobe.max_queued_probes_per_run Set the maximum number of probes a node can pick up during a run. • Type: integer • Default value: 20 glide.eccprobe.node_agent_id ECC queue entries with "mid.server. ${VALUE}" will be ...
More in glide.eccprobe
Other properties in the same namespace.
All 11 properties in glide.eccprobe →