Chris Leonti

started a topic
almost 3 years ago

Show Correct Elapsed Time When Over 24 Hours

Hello,

In the agent an on-going scan resets the elapsed time at 24 hours. While long Deep Scans are less common they do occur. Long scans often occur even with RapidScan, especially the first time a Deep Scan is run and RapidScan is hashing all of the files. We have seen scans that take over a week to complete, but the user only sees the number of minutes since the latest 24 hour cycle has begun. It is confusing to the end-user to see 180 minutes when the scan has been actually running for over 3 days!

Thanks,

Chris

David Corlette

said
over 1 year ago

Hi Chris,

We've put a lot of effort over the last several releases into improving scan times and things like that - can you confirm if you're still seeing this behavior?

C

Chris Leonti

said
over 1 year ago

Hello - Thanks for checking on this. I still see Deep Scans that run over 24 hours so this is still an issue. It is also very difficult to tell if a scan has gone 'rogue' and is in a constant state of scanning when we see only a few hours, but in reality it has been running for days and it is only 3 hours in the current day. We have folks with huge amounts of data that are scanned and if it the issue were only for the initial scan and RapidScan decreases the time to sub-24 hours we have no way to see how long the initial scan tool. Hope this clears things up.

David Corlette

said
over 1 year ago

Hi Chris,

We're tracking this as VPBAGENT-3286 and as a bug, not a feature request. We'll try to get this addressed in an upcoming hotfix soon.