Sometimes you face an edge case that cannot be reproduced easily even while waiting for this enhanced logs level. I would 1/ still log as much as possible, 2/ implement a smaller logs rotation period (upload logs to glacier or S3 after a week), 3/ tune down the verbosity if you want to avoid some unwanted noise later. Use a return of experience approach to get the perfect level for you!
Usually only events that alert of a severe error are logged.
Once we know something's not working, the settings for level are modified so, without even stopping the service, much more detailed information is written and we have a more precise idea of what exactly is failing and why.
It works nicely.