This repository was archived by the owner on Nov 17, 2022. It is now read-only.
Client logging is verbose and not configurable #33
Description
I've noticed that the client's logging is rather verbose. For example this is logged in the space of under a second:
info(message_bus): connected to replica 0
info(message_bus): peer performed an orderly shutdown: tigerbeetle.src.message_bus.union:375:19{ .replica = 0 }
info(message_bus): connected to replica 0
info(message_bus): peer performed an orderly shutdown: tigerbeetle.src.message_bus.union:375:19{ .replica = 0 }
info(message_bus): connected to replica 0
info(message_bus): peer performed an orderly shutdown: tigerbeetle.src.message_bus.union:375:19{ .replica = 0 }
info(message_bus): connected to replica 0
info(message_bus): connected to replica 0
info(message_bus): peer performed an orderly shutdown: tigerbeetle.src.message_bus.union:375:19{ .replica = 0 }
info(message_bus): connected to replica 0
info(message_bus): peer performed an orderly shutdown: tigerbeetle.src.message_bus.union:375:19{ .replica = 0 }
info(message_bus): connected to replica 0
Looking up these log messages, they appear to come from src/message_bus.zig in Tigerbeetle itself:
https://github.com/tigerbeetledb/tigerbeetle/blob/130692a16fc39bfeb5fd23739eeb449a2fb541c0/src/message_bus.zig
Is there any way to control the log verbosity from the node client? Or if not, any pointers on how I might go about implementing such a feature myself?