Skip to content
Optimizing Discovery load for Event Framework › Configure Discovery to use Event Framework › Advanced Discovery configuration › Configuring Discovery › Discovery › ITOM Visibility › IT Operations Management
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Configure background worker job priority for Event Framework

Configure the job priority of background workers to help prevent noncritical tasks from preempting important work, which promotes system efficiency and stability.

Before you begin

Confirm the following:

  • Discovery Admin Workspace is using version 1.9.0 or later.
  • ServiceNow AI Platform® is using version XP9, YP4, or later than YP4.
  • The discovery.use.event.processing system property is turned on. For more information, see Configure Discovery to use Event Framework.
  • The com.glide.queue.discovery.sensors.processing_jobs.priority and com.glide.queue.discovery.cloud.sensors.processing_jobs.priority system properties are configured. For more information, see Add a system property.

Role required: discovery_admin

About this task

By default, Event Framework jobs have a priority of 100. If Discovery is preempting more important work, you can use the com.glide.queue.<queue_name>.processing_jobs.priority property to adjust the priority.

Procedure

  1. Navigate to All > System Properties > All Properties.

  2. Choose one or more job types for which you want to adjust the priority.

    Job typeAction
    IP-basedSelect com.glide.queue.discovery.sensors.processing_jobs.priority from the System Properties [sys_properties] table.
    Cloud-basedSelect com.glide.queue.discovery.cloud.sensors.processing_jobs.priority from the System Properties [sys_properties] table.

  3. In the Value field, enter 110.

    Note: Increasing the number in the Value field lowers the job's priority, while decreasing the number raises it.

  4. Select Update.

Parent Topic:Optimizing Discovery load for Event Framework