QApply Replication Monitor Help

The average latency is a running average over the last 1000 time intervals. If the refresh interval is 10 seconds, then this is the average over the last ~3 hours. Next to the average is the latency trend. This is an indicator on how the average over the last 30 values relates to the larger average. If the trend shows as a red arrow pointing up, the latency is increasing. If the trend is a green arrow pointing down, the latency is decreasing.
This shows a running graph of latency. The total height of the bars is the total end-to-end latency for that interval. The different colors show the components of that latency: QCapture, MQ, and QApply.
This shows the latest latency values. The values are color coded to act a legend for the graph.
The latency values are calculated as follows from the IBMQREP_APPLYMON table:
- Apply latency is from the APPLY_LATENCY column
- MQ latency is from the QLATENCY column
- Capture latency is the END2END_LATENCY column minus the APPLY_LATENCY and QLATENCY columns
This shows a running graph of row throughput, measured in rows/sec.
This value is calculated by fetching ROWS_APPLIED from the IBMQREP_APPLYMON table and dividing the value by the number of seconds that has passed since the last row was fetched. If the ROWS_PUBLISHED value is 0, then the no activity message is shown.
The average throughput is a running average over the last 1000 time intervals. If the refresh interval is 10 seconds, then this is the average over the last ~3 hours. Next to the average is the throughput trend. This is an indicator on how the average over the last 30 intervals relates to the larger average. If the trend shows as an arrow pointing up, the throughput is increasing. If the trend is an arrow pointing down, the throughput is decreasing.

At the bottom of the latency graph there is a message area that might show one of two messages:

"No Activity". This means that no data is travelling accross this queue to QApply. If you get this message, but think that activity should be happening, check the following things:
- Insure that the QSubs using that queue are active.
- Insure that data updates are occuring at the source.
"Queue Stopped". This means that QApply has "stopped" the queue (which means QApply is no longer reading the queue). No QSubs that use this queue are replicating. There are several reasons that a queue might be stopped:
- A queue might be stopped by the Replication operator. From Replication Center, see the "Operations-> ->Manage->Queues" dialog.
- A QSub can be defined to stop the queue if the QSub encounters an error.
- If the underlying MQ Queue does not exist, QApply automatically stops the queue.