Failed Probe Scanning Alerts | Voters

Failed Probe Scanning Alerts

Nathan

Currently a scan job (local probes and external scanner) can be hung up and fail for literal months, and there's no automated action or alerting. You're forced to manually dig through job logs in multiple places to manually validate scanning consistency.

3 days ago

Ryan Seymour

Adding a Scheduled 'Scan' Failed event set could be a path forward on this

Nathan

Ryan Seymour Those are only for reports and patching. Not for probe actions.

Ryan Seymour

Nathan yes sorry, I was saying we could add the missing 'Scan Jobs' to this section where we have the Patching and Reporting

Nathan

Ryan Seymour The problem is there are too many variables. Sometimes the jobs don't log as "failed" they simply stop and are missing from the job log. Other times there are more obscure errors then just "failed". It would need to be the other way around where there would be a conditional alert of ≠ Completed for x Hours etc.

Ryan Seymour

Nathan great points! Thanks for your feedback. I'm with the ConnectSecure team and will be sharing.