fix(profiling): reduce lock profiler log spam (#11377)

The lock profiler would log a warning if it couldn't determine a
name for a lock, and it would try determining a name multiple times for
the same lock. This lead to excessive log spam. Downgrade this to a
debug log and only try to determine the name once.

Author: nsrip-dd

ddtrace/profiling/collector/_lock.py

@@ -269,7 +269,7 @@ def _find_self_name(self, var_dict: typing.Dict):
 
     # Get lock acquire/release call location and variable name the lock is assigned to
     def _maybe_update_self_name(self):
-        if self._self_name:
+        if self._self_name is not None:
             return
         try:
             # We expect the call stack to be like this:
@@ -298,7 +298,7 @@ def _maybe_update_self_name(self):
 
             if not self._self_name:
                 self._self_name = ""
-                LOG.warning(
+                LOG.debug(
                     "Failed to get lock variable name, we only support local/global variables and their attributes."
                 )
 

releasenotes/notes/profiling-reduce-lock-profiler-log-spam-5931d957ff1becd4.yaml

@@ -0,0 +1,7 @@
+---
+fixes:
+  - |
+    profiling: The lock profiler would log a warning if it couldn't determine a
+      name for a lock, and it would try determining a name multiple times for
+      the same lock.  This lead to excessive log spam. Downgrade this to a
+      debug log and only try to determine the name once.