ServiceNow events-driven discovery: Create a database index for the Cloud Events tableTarget Audience: Cloud Provisioning and Governance users using Event Driven Discovery Action to be Performed: Create a database index from the state, pid, resource_id columns (In written order) of the Cloud Events [sn_cmp_cloud_event] table. Requirement of Index: Cloud Events table is used to store and then process the events recieved from the cloud providers to enable event driven discovery. The database index helps to improve the cloud event processing performance of the ServiceNow instance. Cloud event processing post Utah follows a bucketing approach to allow parallel processing of cloud events for a better performance. This approach heavily depends on frequently querying the events table to assign the correct PID to each event. How to Create the Index: If you are an existing Cloud Provisioning and Governance user, you can create the index manually or by using a scheduled job. To manually create a database index, see Create a database index for the Cloud Events table.To create a database index using scheduled job, download and import this scheduled job. The resulting process runs as a background process. Use the logs to monitor the script execution. Symptoms/Results of not having the Index: If the index is not created and the volume of events is very high, the event processing may become very slow and the scheduled job named "Cloud Event Sorter" may take a lot of time to assign pid to each event. Conversly, if the event processing is getting really slow and the mentioned scheduled job is getting stuck, it's time to create the specified index. Note: If you've started using Cloud Provisioning and Governance with the Utah release, the database index is automatically created on application installation.