Log STUN responses at 'debug' level only

On busy servers, the amount of STUN queries can be overwhelming, so don't log those at 'info' level.
processone · Aug 30, 2020 · d01c712 · d01c712
1 parent be1d2fb
commit d01c712
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,6 +2,7 @@
 
 * Log relay allocation refreshes at notice level.
 * Log duration of TURN sessions.
+* Log STUN queries at debug (rather than info) level.
 * Hand over more metadata to STUN callback.
 
 # Version 1.0.37

diff --git a/src/stun.erl b/src/stun.erl
@@ -299,10 +299,10 @@ process(State, #stun{class = request,
     AddrPort = unmap_v4_addr(State#state.peer),
     R = case stun_codec:version(Msg) of
 	    old ->
-		?LOG_INFO("Responding to 'classic' STUN request"),
+		?LOG_DEBUG("Responding to 'classic' STUN request"),
 		Resp#stun{class = response, 'MAPPED-ADDRESS' = AddrPort};
 	    new ->
-		?LOG_INFO("Responding to STUN request"),
+		?LOG_DEBUG("Responding to STUN request"),
 		Resp#stun{class = response, 'XOR-MAPPED-ADDRESS' = AddrPort}
 	end,
     run_hook(stun_query, State, Msg),