Good.
There are legitimate reasons to log requests. But far too often, developers that are used to 'printf debugging' will abuse the system. In many cases, what they were actually looking for was either some form of APM, distributed tracing, or much more commonly, would be better done by collecting metrics - which tend to be much more lightweight.
At work I've been fighting a battle to turn multiple dozens of terabytes of logs a day into something manageable, for years now. Sometimes I wonder if I could use the logging system itself in lieu of the application, as practically all data is dumped there! It's difficult battle to convince multiple groups to just use a counter instead of spitting out the same line of text every time the same kind of event happens.
Anyway, back to the point: no matter how busy the system is, you can surely engineer a mechanism to collect error logs, even if you have to sample them. But while things are running smoothly, track metrics. And, if you have a reason to suspect things are wrong, selectively turn on some logging.
I wish more people were aware of the costs of logging. Even more so nowadays, with the microservices craze.