Event Management bulk processing changes in Jakarta
In Jakarta, the bulk API was changed to https://<instancename>.service-now.com/api/global/em/jsonv2.
This API is more efficient, and therefore business rules on the Event table (em_event) are not being run. Event Management assumes that there are NO business rules on the Event table. This is a known bad practice and has been known to cause performance issues.
To run business rules on the Event table for various reasons, choose to work with the previous bulk insert. This is not recommended, but it works because the performance of the new API is superior.
For backward compatibility, you can configure the MID Server to work with each API. The following example describes how to work with the bulk API from Istanbul (http://<instancename>.service-now.com/em_event.do?JSONv2&sysparm_action=insertMultiple).
Navigate to MID Server > Servers.
Pick a server and go to the Configuration Parameters tab, which displays the configuration properties of the MID Server.
Click New and set the following properties on the MID Server by choosing from the drop-down list:
- mid.probe.event.queue.compress: false
- mid.probe.event.bulk_size: 100
- mid.probe.event.endpoint.url: em_event.do?JSONv2%26sysparm_action=insertMultiple
For additional information on the APIs, see the product documentation topic Event collection to the instance via web service API.