ASM : Working with blocking mode only

Thank you Jacob for confirming that. I was told long time ago by an F5 integrator, that blocking and learning at the same time was not possible, but this is wrong if i got it well.

The underlying idea of my post is that a team is working on blocking mode directly in qualification, saying that they have no time for learning and limited storage for logs on their bigip. The result of a specific application policy deployment is that blocking mode provides too many blocking, they switch to transparent and this made things better to stabilize the policy according to what they said.

In preproduction we should have trusted sources, so working in transparent mode should make more sense. In blocking mode, maybe some blocked requests is delaying the possibilty to run subjacent ones, where as in transparent a full browsing of the application is possible in a shorter amount of time.