This counter counts brand-new lock requests both created by and resolved on this same cluster member, without involving other nodes. This measures purely local locking activity, useful as a baseline the admin can compare against incoming and outgoing counts to see how much lock traffic actually crosses the cluster interconnect. For example, a single-node application that locks its own private database files would drive this local counter up without generating any cross-node lock traffic at all.