Resolve a Collection Failure

Since the failure to monitor can result in users missing critical alerts or performance data, SilverBack provides collection faults to ensure that users can get real-time notification of these conditions. Collection faults are generated when SilverBack monitoring fails due to an issue on the remote device, and are currently supported in four areas:

• Windows monitoring

• Syslog monitoring

• Patch Scans monitoring

• Vulnerability Scans monitoring

This topic takes you through the following procedures:

• Viewing Collection Failures

• Diagnosing Collection Failures

• Remediating Collection Failures

Viewing Collection Failures

1. From the Alerts category page click on the Browse Collection Failures link to display the Collection Failures report.

Diagnosing Collection Failures

1. Click on a collection failure, then hover the mouse over a failure's Description column to display the entire message in a tooltip.

2. Click on the same collection failure, then select the More Action drop-down's Test Polling Configuration option.

3. Once the tests have completed, scroll down the report to find the matching collection type, and confirm that a similar failure reason exists.

Remediating Collection Failures

1. Navigate to SilverBack's Collection Failures troubleshooting website at http://www.silverbacktech.com/site/collectionfaults/index.html.

2. Scroll down to find a matching collection failure error message.

3. Click on the matching link to display the corresponding troubleshooting information

4. After reading through the category, possible cause, diagnosis and remediation steps and product version information, perform the steps required.

In this case, you would access the affected device's Windows Control Panel to ensure that Client for Microsoft Networks and File and Print Sharing for Microsoft Networks are installed and enabled on the network connection.

5. Finally, run the Polling Configuration test again to ensure that the issue has been corrected.