Queue latency triggers notify the user when the first block of a queue has remained at the beginning of the queue for more than the specified threshold. RMS monitors each inbound and outbound (DSI) queue, but does not track latency for RSI or materialization queues.
RMS, not the Replication Server or data servers, tracks
the queue latency. It is therefore important that you coordinate
the Replication Server monitoring interval and the latency threshold when you
are setting up a queue latency trigger. For example, if the monitoring
interval is set to 5 minutes and the queue latency threshold is
set to 1 minute, RMS checks latency only after 5 minutes. Since
RMS must compare the current time with the previous time, it may
take 2 cycles, or 10 minutes, to notice that the queue latency threshold has
been exceeded.
