Property reference

`sn_itom_pattern.k8s_schedule_batch_delay`

Sets the delay, in seconds, between batches of Kubernetes discovery schedules. At the default of 300 seconds, later batches run five minutes after the preceding batch.

Default: 300
Type: integer
Application: Not stated
Category: CMDB & Discovery

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 time in seconds between batches of Kubernetes discovery schedules; the default delay is 300 seconds.
What area does it affect?	Kubernetes discovery scheduling
What does the default mean?	The default value is "300", which sets the baseline numeric behavior for this property.
When should you review it?	When adjusting the timing between batches of Kubernetes discovery schedules

Property record

No out of the box record exists. ServiceNow scripts read this property and use the default value shown until you create it.

Property name	`sn_itom_pattern.k8s_schedule_batch_delay`
Type	integer
Application	Not stated
Default value	`300`
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... respective companies with which they are associated. 976 Other Supported System configuration (continued) Property name Property description Type Default value Example- 5 (Number of schedules to run in on batch) sn_itom_pattern.k8s_schedule_batch_delay [keeps tracks of the time difference between two batches value contains in sec] Example- 300 (in seconds) Integer sn_itom_pattern.k8s_run_time [keeps tracks of the current time for a batch] If this ...

Used in

Out of the box artefacts that read this property. Append the path to your instance URL to open the record and see how the value is used.

Pattern Pre/Post Script: Create Kubernetes Cluster Schedule This setting controls the delay between batches of Kubernetes discovery schedules, affecting when later batches run; admins can change it to adjust that timing. If unset, the code uses 300 seconds (5 minutes). /sa_pattern_prepost_script.do?sys_id=17c8c2bb876c4910fd5752c73cbb35bd

More in `sn_itom_pattern`

Other properties in the same namespace.

sn_itom_pattern.k8s_prometheusUrl Provides the default Prometheus URL read by the Create Kubernetes Cluster Schedule pattern; an unset setting… sn_itom_pattern.k8s_run Sets how often the Kubernetes discovery schedule runs, with a default frequency of Daily. sn_itom_pattern.k8s_run_k8s_cloud_discovery This boolean property determines whether Kubernetes cluster records are discovered without creating an… sn_itom_pattern.k8s_run_time Provides the Kubernetes discovery schedule batch time in HH:MM:SS format, or uses timing five minutes after… sn_itom_pattern.linux_server_preferred_serial_number_type This property allows administrators to define which serial number type to use for populating the Serial… sn_itom_pattern.log_gcp_event_job This property controls whether account information is logged for the GCP-Events-job scheduled job, impacting… sn_itom_pattern.logger_level This property configures the logging level, with a default of 'info', affecting the amount of detail… sn_itom_pattern.logger_names When debug logging is enabled and a prefix is provided, sn_itom_pattern.logger_names allows output only for…

All 58 properties in sn_itom_pattern →