Create a Dedicated Event ProcessorDescription Dedicated Event Processor Use Case and How-To Setup Most events go into the sysevent table with no queue specified, these events are picked up and processed by the events processors jobs, referred to as general events. Events such as the Text Index events (text_index) are added to the sysevent table with a queue of text_index and these events are processed by the Text Event Processor, these events have a dedicated job process. Benefits This allows for the separation of workA dedicated (worker) job to processes only the events configuredCan be used to help control backlogs caused by slower events.Can be used to better control priority events Use Case Use Case: A customer executes a large clean up script or sync job that updates all change requests. As a results there is a large spike in 'ci.affected' events created. This in turn delays all other general event processing, the customer sees the impact to a down stream process as the those events are not being processed timely. Solution: Create a Dedicated Event Process job for just impacted events. This solution greatly reduces the chances that the impacted events could be delay due to other issues that may be occurring with the instance or the general event queue. ResolutionHow-To Setup Note: The standard Event Processor uses a delegate model where events are pushed, process and limited to 500 events per node. This method will not do that, when the job starts, 100% of the pending events for that queue will be claimed. This method was not designed to be multiple threaded (multiple jobs). Login as an Admin account into the instanceNavigate to the System Policy > Registry module.Filter on the event name, IE. x_snc_employee_spe.employeeOccasionOpen the record, input the desired queue name under Queue. IE, my_queue for the use case. Then save the record. You can repeat steps 2-4 for any other named events that you want to route to this new dedicated events processor. For example, you might want to route similar events to a single event processor.All newly created events from step 4 now have a queue specified. This is confirmed by going to the System Logs > Events module and filter down matching event name. The specified queue is only added on newly created events Create the dedicated Event Processor job for the newly created queue by navigating to the System Scheduler > Scheduled Jobs module.Click the New button.Enter the following values for the fields and then Click Submit. (Swap out QUEUENAME for the queue name set in step 4) Name: QUEUENAME events process System ID: ACTIVE NODES Job Context: fcScriptName=javascript\:GlideEventManager('QUEUENAME').process(); Trigger type: Interval Repeat: 30 seconds (Leave all other field as default, in our example we used 'my_queue'. Ensure that the Job ID field defaults to RunScriptJob) To verify the new processor is working as expected, navigate to System Logs > Events module and filter down matching event name and confirm that new created events are being marked processed. Validation Make sure that you validate that everything is working as expected! Check that the newly created events are going into the correct queueCheck that the newly created events are being processed