Log spam in newer versions

[LilithSilver]

On automerge-rust-sync-server, I'm seeing info and debug tracing logs on each tick:

8854140500021203") local_peer_id=peer-8018854140500021203 now=1772848467386 event=Input(Tick)
2026-03-07T01:54:27.491270Z TRACE io_loop: samod::io_loop: received task local_peer_id=PeerId("peer-8018854140500021203")
2026-03-07T01:54:27.491512Z DEBUG io_loop:handle_event:handle_event: samod_core::actors::hub::state: hub event processed event_type="tick" connections=0 documents=0 ensure_connections_us=0 local_peer_id=PeerId("peer-8018854140500021203") local_peer_id=peer-8018854140500021203 now=1772848467491 event=Input(Tick)
2026-03-07T01:54:27.593026Z TRACE io_loop: samod::io_loop: received task local_peer_id=PeerId("peer-8018854140500021203")
2026-03-07T01:54:27.593240Z DEBUG io_loop:handle_event:handle_event: samod_core::actors::hub::state: hub event processed event_type="tick" connections=0 documents=0 ensure_connections_us=0 local_peer_id=PeerId("peer-8018854140500021203") local_peer_id=peer-8018854140500021203 now=1772848467593 event=Input(Tick)
2026-03-07T01:54:27.695074Z TRACE io_loop: samod::io_loop: received task local_peer_id=PeerId("peer-8018854140500021203")
2026-03-07T01:54:27.695294Z DEBUG io_loop:handle_event:handle_event: samod_core::actors::hub::state: hub event processed event_type="tick" connections=0 documents=0 ensure_connections_us=0 local_peer_id=PeerId("peer-8018854140500021203") local_peer_id=peer-8018854140500021203 now=1772848467695 event=Input(Tick)
2026-03-07T01:54:27.796613Z TRACE io_loop: samod::io_loop: received task local_peer_id=PeerId("peer-8018854140500021203")
2026-03-07T01:54:27.796789Z DEBUG io_loop:handle_event:handle_event: samod_core::actors::hub::state: hub event processed event_type="tick" connections=0 documents=0 ensure_connections_us=0 local_peer_id=PeerId("peer-8018854140500021203") local_peer_id=peer-8018854140500021203 now=1772848467796 event=Input(Tick)

It completely subsumes all other log output. Are these logs expected? If so, I'd suggest that these events either be removed or constrained only to TRACE mode. If not, please let me know!

[alexjg]

Yeah these are intentional (they're used for the telemetry). They definitely should be TRACE, but I also wonder whether they should be on a separate tracing span so that they aren't enabled unless you set something like RUST_LOG=samod::telemetry=TRACE or something.