Overhead of mongodb slow query logging

What is the impact of logging slow query on incoming request.
based on this code i can see that we are trying to acquire lock for 500ms.

in my logs i am seeing lots of

2022-09-15T01:56:12.046+0530 W  COMMAND  [conn3609044] Unable to gather storage statistics for a slow operation due to lock aquire timeout

Is this logging done in request path or async path? what is the impact of lots of lock aquire timeout (even if logging is done in async path, what is the pool size for this async logger? if some user request is not able to acquire a thread from this pool will it be stuck till it acquires a thread)? why would lock acquire timeout?

this questions has come up as part of deep diving on this issue. Please help.