The oldest_unacked_message_age vs raw backlog distinction is the right one to lead with, most teams alert on the wrong metric early on. On the ordering-key hot spot problem at 10x, did you consider splitting the hot key onto its own subscription instead of sharding the whole topic? That way a bursty user doesn't stall throughput for everyone else sharing the same ordering key space.