DAST engine stats output of nav_action_count is misleading
Problem to solve
The scan statistics output includes a nav_action_count field which is just the total number of seen or collected actions, not the number of actions taken.
2021-09-28T02:37:01.000 INF STAT State monitor ping alloc_mb=282 avg_nav_time_ms=6374 browser_ids=[8724357680335746214] leased_browsers=1 nav_action_count=2 num_gc=3 sys_mem_mb=336 total_alloc_mb=284Proposal
This should be updated to nav_actions_collected, and also add output of nav_actions_taken. This would allow customers to quickly see how many actions the scan has taken and how many are left if a MAX_ACTIONS value has been set.
More information
https://gitlab.slack.com/archives/CKWJP0ZS7/p1633977128235300
Intended users
What does success look like, and how can we measure that?
Output contains nav_actions_collected, and nav_actions_taken