Hi @Lyndon-prequel, @tonymeehan

I just wanted to clarify that the failure I submitted in my PR was not my original plan. Initially, I was trying to simulate a high-severity failure described in this GitHub issue: redpanda-data/redpanda#3643. If I had succeeded, it would have been the perfect candidate for a serious production-level failure.

This failure involves a Redpanda broker running on an ARM64 AWS instance where, after several hours of normal operation, both the producer and broker experience a sudden surge of errors and memory usage increases (~1GB every 5 hours). The producer uses rust-rdkafka to send around 200 messages/second to 14 topics with idempotency and SASL authentication enabled.

Despite trying to reproduce this in multiple languages (Rust, Python), I was not able to successfully simulate the issue, even after many attempts and long-running tests.

Because of this, I had to switch to a simpler but still valid failure scenario, which delayed my PR submission.

Thanks for understanding!

@tonymeehan Can I have your eye on this 😄?

This rule looks good to merge! Please rename the CRE id (folder and rule ID) to CRE-2025-0091 and we'll be good to merge.

Done!, @tonymeehan

thanks @Lyndon-prequel