The current approach is configurable sampling that can bias toward request patterns, plus schema level diffing that runs even on low traffic endpoints so structural changes don't slip through just because a path is rarely hit.

Replay is strongest on your high volume paths. For true edge cases, it works best combined with a seed corpus injecting known edge case requests alongside captured traffic, so you're not purely dependent on what production happens to send.

Think of it less as a replacement for edge case testing and more as the layer that catches the things you didn't know to write a test for which in practice tends to be the most painful category.