Rejected request data on DC Rate Limiting does not aggregate from all nodes

Issue Summary

While Rate Limiting is active on a DC product with multiple nodes, the request data does not get flushed consistently from all of them. This leads to delays and/or gaps in the aggregation of this data in the UI, particularly when the data on one node never gets flushed.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available