I agree to the comments right below your question: Just reconfigure logging.
Technically speaking, with Spring AOP you are limited to intercepting calls to or executions of Spring bean methods. So unless your logging calls are not encapsulated in Spring beans, Spring AOP will not be useful.
With AspectJ though, you could apply LTW (load-time weaving) to your logging library and block execution of logging methods called by a specific control flow. You could also do the same by weaving your application code and then block calls to logging methods from within a specific control flow.
Disclaimer: While this is easily implemented aspect-wise, I have no idea if your production admins will permit you to use AspectJ on the target system. Even if you compile the aspects into your own production code, at least you will need the AspectJ runtime (aspectjrt.jar) on the application's classpath.