Is there a way to disable the “keep alive” logs? My logs are bloated with these:
{"level":"debug","ts":"2023-03-29T16:50:10.556Z","caller":"server/pipeline.go:65","msg":"Received *rtapi.Envelope_Ping message","uid":"6f7e060f-654e-407e-bf04-671ff9aa93e7","sid":"b8b2ee3c-ce51-11ed-b57d-7106fdcb5b46","cid":"5","message":{"Ping":{}}}
{"level":"debug","ts":"2023-03-29T16:50:10.556Z","caller":"server/session_ws.go:395","msg":"Sending *rtapi.Envelope_Pong message","uid":"6f7e060f-654e-407e-bf04-671ff9aa93e7","sid":"b8b2ee3c-ce51-11ed-b57d-7106fdcb5b46","envelope":"cid:\"5\" pong:{}"}
Might be useful for you guys, but for me, the game dev, it’s completly not. I’m absolutly fine seeing connected presences in the console.
Since “keep alive” is an essential part of realtime matches, i dont feel like there is a need for logging these empty payloads anyway. I run a game server with couple hundreds users connected at the same time. This bloat makes it impossible to spot my own log lines.
I know i could use a log viewer with filter, but setting this up for live insights i’m not sure how to do (since everything runs in docker)
And i know i could set the loglevel to something higher, i.e. info. But that gets rid of all MY debug messages that i am actually interested in.
I do run a custom build of nakama (forked) because i needed a small tweak. If there is no such official way, i may need to go down the Go-rabbithole again 
- Versions: Nakama 3.14, Docker on Debian
- Server Framework Runtime language (If relevant) TS