The current version 7.3.2 introduces log spamming rendering the entire log useless if Rebus logging is enabled.
2021-10-13 12:09:15.0513 DEBUG Thread id: 16 RabbitMqTransport.Receive 0 Waiting for queue read
2021-10-13 12:09:15.3005 DEBUG Thread id: 36 RabbitMqTransport.Receive 0 Reading from queue was cancelled
2021-10-13 12:09:15.3041 DEBUG Thread id: 96 RabbitMqTransport.Receive 0 Reading from queue was cancelled
2021-10-13 12:09:15.5580 DEBUG Thread id: 15 RabbitMqTransport.Receive 0 Waiting for queue read
2021-10-13 12:09:15.5580 DEBUG Thread id: 15 RabbitMqTransport.Receive 0 Waiting for queue read
2021-10-13 12:09:15.8040 DEBUG Thread id: 68 RabbitMqTransport.Receive 0 Reading from queue was cancelled
These log messages are written more than once per second even when there is no traffic.
Usually Rebus logging produces useful information about incoming and outgoing messages. However, due to these log messages, the useful messages are drowned.
The current version 7.3.2 introduces log spamming rendering the entire log useless if Rebus logging is enabled.
These log messages are written more than once per second even when there is no traffic. Usually Rebus logging produces useful information about incoming and outgoing messages. However, due to these log messages, the useful messages are drowned.
Can these log messages be excluded?