Teleport Log Sink regex filtering and high-volume event latency

Teleport utilizes Log Sinks to stream audit events to external providers like Webhooks, Slack, or PagerDuty. To manage notification noise, administrators apply regex filters within the sink configuration to exclude high-frequency events, such as routine health heartbeats or repetitive session metadata. p>There is uncertainty regarding the performance impact of these filters when the Audit Service processes high-volume log streams. While filtering reduces the volume of downstream notifications, it is unclear if complex regex processing at the sink level introduces measurable latency for critical security events during an incident spike.

How does the Teleport Audit Service prioritize event delivery when multiple regex filters are applied to high-throughput streams? Is there a documented mechanism to implement rate-limiting at the sink level to prevent webhook API exhaustion during event storms?