Spammy network messages in the logs

[jancionear]

Network events like nodes connecting/disconnecting produce logs that are worrying to validators. We get questions about them from time to time.

Those are messages like:

WARN network: Message dropped because TTL reached 0. msg=RoutedMessageV2 { msg: RoutedMessage { target: PeerId(ed25519:CrviUGEGjUVWhQaHhdzCR18EBXijMRq3bqZk5UskKRTx), author: ed25519:FgMWfGCoLmzMxanwoZQckyqB66YweKWyseBJrCgvgdEK, signature: ed25519:2nrsY9WL2nW5agBfSGV22WE7tAfQ9k3mqUHfdvh6nAvMcsnwHCDxdYPmJu

ERROR network: Failed to save peer data err=Peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E is missing in the peer store

INFO near_network::peer_manager::connection: peer ed25519:6nckgUyKnY1epo6pqnjcTTCC7DvJWv5DrWpREJr5qL9a disconnected, while sending SyncSnapshotHosts

INFO near_network::peer_manager::connection: peer ed25519:8bFntvq1EnaSknHUM69YeGFHvs1YahwPSmgMrFmdkk6q disconnected

These logs often appear multiple times for the same event, spamming the output:

2024-08-16T13:05:34.475705Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475709Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475734Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475750Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475766Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475785Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475801Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475824Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475847Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475861Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475876Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475897Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475919Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475924Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475932Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475937Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
2024-08-16T13:05:34.475942Z  INFO near_network::peer_manager::connection: peer ed25519:86JbvXNHGiK3vfYwMq1f8vG1SZNei92KDTPsyUJMcY7E disconnected, while sending SyncSnapshotHosts
...

Could we make them DEBUG level logs? Is this something that the node operator needs to know? Sounds like harmless network events, nothing to worry about. It'd clear the output and wouldn't alarm community validators.

/cc @saketh-are

[saketh-are]

@jancionear I'm good with downgrading all of these to DEBUG level.