@kaganoskay

there’s no knob in Pega to rate-limit PDC traffic. Pega sends health data to PDC via the PegaAESRemote agents over REST in batches every 5–10 minutes, and that cadence isn’t exposed for tuning. Your best options are outside the app tier: rate-limit and buffer at the proxy/API gateway (for example, spike-arrest or token-bucket style policies) so bursts get smoothed without dropping data. If your proxy is in the path, make sure the PDC endpoint is whitelisted and not deep-inspected, since Pega’s docs recommend allowing direct, trusted egress to PDC. To reduce volume at the source, suppress noisy events instead of throttling transport: raise/suppress alert thresholds in PDC so known chatter doesn’t generate cases, and avoid enabling optional high-volume metrics (like temporary Data Flow shape metrics) unless needed. If you must insert a queue, point Pega’s PDC alt REST URL to an internal collector that buffers and forwards to PDC (Dynamic System Setting prconfig/pdcconfig/altresturl/default). What this really means is: implement rate limiting in the proxy, not in Pega; in Pega, focus on reducing what you emit rather than how fast it’s shipped.