Posted by @cwrx777:
Hi,
how can this log be disabled from schedule_visualizer_node ?
[schedule_visualizer_node-1] [2024-11-11 10:02:44] [frame_header] Dispatching write containing 13 message(s) containing 26 header bytes and 702 payload bytes
[schedule_visualizer_node-1] [2024-11-11 10:02:44] [frame_header] Header Bytes:
[schedule_visualizer_node-1] [0] (2) 82 36
[schedule_visualizer_node-1] [1] (2) 82 36
[schedule_visualizer_node-1] [2024-11-11 10:02:44] [frame_payload] Payload Bytes:
[schedule_visualizer_node-1] [0] (54) [2] 7B 22 63 6F 6E 66 6C 69 63 74 73 22 3A 5B 5D 2C 22 72 65 73 70 6F 6E 73 65 22 3A 22 74 72 61 6A 65 63 74 6F 72 79 22 2C 22 76 61 6C 75 65 73 22 3A 6E 75 6C 6C 7D
[schedule_visualizer_node-1] [1] (54) [2] 7B 22 63 6F 6E 66 6C 69 63 74 73 22 3A 5B 5D 2C 22 72 65 73 70 6F 6E 73 65 22 3A 22 74 72 61 6A 65 63 74 6F 72 79 22 2C 22 76 61 6C 75 65 73 22 3A 6E 75 6C 6C 7D
[schedule_visualizer_node-1] [2] (54) [2] 7B 22 63 6F 6E 66 6C 69 63 74 73 22 3A 5B 5D 2C 22 72 65 73 70 6F 6E 73 65 22 3A 22 74 72 61 6A 65 63 74 6F 72 79 22 2C 22 76 61 6C 75 65 73 22 3A 6E 75 6C 6C 7D
[schedule_visualizer_node-1] [3] (54) [2] 7B 22 63 6F 6E 66 6C 69 63 74 73 2
Chosen answer
Answer chosen by @luca-della-vedova at 2024-11-12T02:33:44Z.
Answered by @luca-della-vedova:
I’ll start by saying that this is not an area I’m familiar with, but with a quick search I found that the library printing it is websocketpp here,
The library docs claim that you can use a clear_access_channels function to disable specific channels. From the code snippet it seems to be the following channels:
log::alevel::frame_header
log::alevel::frame_payload
From the examples it seems it can be cleared as a function of the client / server, so I’d start by trying to use it on the clients / servers that we store internally
From your log it seems the log originates in the schedule visualizer so I would try to use the API above in its server.
That being said, I never encountered this before but if it’s reproducible and the solution works feel free to open a PR with detailed steps to reproduce! I fully agree that this level of logging is so verbose that it is not useful
, can you elaborate a bit more on whether it always appear, is a new issue, etc.? I do believe it would be worthy to submit the fix if it’s a common issue.