The mirroring lag indicates how far behind the destination is from the source in terms of processing events.
This is measured as the maximum number of messages lagging on any of the partitions for a mirror topic.
For example, given a mirror topic with three partitions: one partition lags 4 messages behind the source topic,
another lags 24 messages behind, and the third lags 92 messages behind, the mirror topic’s lag is reported as 92.
Each mirror topic’s lag is measured once per minute. If your query’s
granularity is higher than a minute (
PT1M), then the API will
return the maximum lag from each of the minutes in that time range.
If your query does not group by
topic, then it will return the
maximum lag over all of the mirror topics that match the filter clause.
For example, if your query filters on a specific
then it will return the maximum lag among all of that link’s mirror topics.