The TTLMonitor has reports metrics for each ttl passess and subpasses. However, the TTLMonitor utilizes replicated deletes, and should only be run when the node is primary.

However, the TTLMonitor checks late on whether it is primary. At that point, scope guards will auto-increment 'passess' and 'subpassess'.

This is misleading from an observability perspective - the TTLMonitor appears to be running on secondaries, but doesn't perform any real work.