storj/storagenode
Egon Elbre f41d440944 all: reduce number of log messages
Remove starting up messages from peers. We expect all of them to start,
if they don't, then they should return an error why they don't start.
The only informative message is when a service is disabled.

When doing initial database setup then each migration step isn't
informative, hence print only a single line with the final version.

Also use shorter log scopes.

Change-Id: Ic8b61411df2eeae2a36d600a0c2fbc97a84a5b93
2020-01-06 19:03:46 +00:00
..
bandwidth common: separate repository 2019-12-27 14:11:15 +02:00
collector private/testplanet: remove dependency to uplink 2020-01-02 09:40:46 +00:00
console common: separate repository 2019-12-27 14:11:15 +02:00
contact all: reduce number of log messages 2020-01-06 19:03:46 +00:00
gracefulexit private/testplanet: remove dependency to uplink 2020-01-02 09:40:46 +00:00
inspector private/testplanet: remove dependency to uplink 2020-01-02 09:40:46 +00:00
monitor common: separate repository 2019-12-27 14:11:15 +02:00
nodestats common: separate repository 2019-12-27 14:11:15 +02:00
notifications common: separate repository 2019-12-27 14:11:15 +02:00
orders storagenode/orders: adding jitter to sending (#3725) 2019-12-30 21:35:26 +01:00
pieces all: reduce number of log messages 2020-01-06 19:03:46 +00:00
piecestore common: separate repository 2019-12-27 14:11:15 +02:00
reputation common: separate repository 2019-12-27 14:11:15 +02:00
retain common: separate repository 2019-12-27 14:11:15 +02:00
satellites common: separate repository 2019-12-27 14:11:15 +02:00
storagenodedb common: separate repository 2019-12-27 14:11:15 +02:00
storageusage common: separate repository 2019-12-27 14:11:15 +02:00
trust common: separate repository 2019-12-27 14:11:15 +02:00
operator.go storagenode/main: map aliases for kademlia config values (#3118) 2019-09-30 19:33:00 -04:00
peer.go all: reduce number of log messages 2020-01-06 19:03:46 +00:00