LockerImpl::lock() is called by code that appears to typically have a dbName or nss or UUID. However, down in LockerImpl::_lockComplete() where we log "Unable to acquire ... lock on <resId> within <time>", we only provide a hard/impossible to identify resId number. It would be helpful to connect the name for the lock down through to this log message, so we can know what lock failed to be acquired.

I'm less familiar with ResourceMutex identification, but it would be great to improve identification logging for those as well – an ambiguous resId number for a ResourceMutex acquisition attempt is what motivated this ticket.