Is anyone able to explain to me, or direct me to some useful documentation on, the communication between the IBRSD process on a BPPM 9.6 server and the arplugin process and INT:Staging form on a Remedy application server ?

If Incident load is more than 18-20 in a minute, prefer having multiple instances of IBRSD [more details in the document] and create Propagation Rule/Policy with ECF in such a way load is distributed across IBRSD instances

IBRSD process is single threaded and when there is a delay or failure in incident creation for an event, it will keep retrying based on the configuration and other events will be queued up and not processed by IBRSD, hence causing exponential delays

I believe the delay is on the BPPM\IBRSD side because, when an incident has not been created, the vast majority of the time there is no record in INT:Staging for it. Note that we do keep the records in INT:Staging for 1-2 days before removing them to help diagnose these ticketing delays.

I am interested to know when IBRSD writes to INT:Staging.

Does it attempt to write to INT:Staging immediately when an event is propagated to IBRSD ?

Does Remedy prevent it from writing to INT:Staging until it is ready to accept the incoming data ?

Does IBRSD wait for a signal from Remedy that it is ready to accept the incoming data ?