What is the impact of removing log suppression?

[PhoneBoy]

Primarily disk space/usage, not to mention extra load on the logging infrastructure.
Why is this interesting to you?
What is your precise use case?

[Oscar_Bernat]

We work in a BAS technology to test security controls continuously, missing events because of the log suppression (default config) puts us in troubles because our test outcome is filled with false negatives (all suppressed logs).

So, I'd like to know if the suppressed logs are stored somewhere and if can be accessed via API if it was the case.

If that's not possible, my question is about the impact of removing log suppression and if the log suppression is related only to threat prevention events or other events as well

[PhoneBoy · Accepted solution]

No, the suppressed logs are not available anywhere as they are...suppressed from being written anywhere.
This feature dates back to at least FireWall-1 2.x (so quite old) and, to my knowledge, only relates to basic firewall logs, not Threat Prevention. 
However, App Control and possibly Threat Prevention logs can get consolidated.
There is a field in the log entry when this happens (i.e. number of logs).

Like I said, if you choose not to suppress logs, it can create extra load on the log server (disk mostly).

[Timothy_Hall]

I know for sure that IPS logs are suppressed, this screenshot is from my IPS Immersion course.  Not sure about the rest of Threat Prevention.

[Oscar_Bernat]

Thanks to everybody!!