DAST/Browserker: Improve logging statistics

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

A customer reported an issue when running passive scans with DAST where the jobs intermittently hang or get killed by the OOM killer with the message Killed.

See internal issue for more details.

It is difficult to diagnose the reason for this as we don't have enough logging in place. We need to add more statistics to the statistics log message that can help give engineers a clearer picture regarding:

• how much memory is being consumed during the scan
• outstanding navigation paths
• outstanding URLs

We should also consider adding an auth prefix to depict auth-related logs.