guardRejectionsByGuard

guardRejections broken down by the dev.kmemo.guard.MatchGuard.name that fired.

The values sum to guardRejections — each guard-rejected miss is attributed to the single guard that vetoed it first, matching the order guards run in. Every configured guard is a key, so one that has never fired shows up as 0 rather than being absent: a guard stuck at 0 is either redundant for your traffic or ordered behind one that always rejects first, and only the breakdown tells you which. Empty when the cache runs with dev.kmemo.guard.MatchGuards.none.