Understanding Collection Fault Monitors

Before removing or disabling any Collection Fault Monitors be absolutely certain that you understand the implications. Removing or disabling Collection Fault Monitors that are in active use could result in blank end-of-month reports deliverables.

What are Collection Fault Monitors?

Collection Fault Monitors in the SilverBack system are groupings of technology data collection types that you can use to monitor whether your system is correctly collecting required data.

Since Collection Fault Monitors are Policy Components, they can reside in Monitoring Policies and Monitoring Policy Templates, or they can be used as stand-alone Policy Components within a Management Domain

You can use Collection Fault Monitors to troubleshoot:

The absence of data in performance reports
The absence of an alert (i.e., a matching event message)

If you wish to use a Monitoring Policy to monitor data collection you must manually place Collection Fault Monitors into that policy.

The following topics contain detailed information about how and for what SilverBack collects failure information:

Reporting

There is a direct correlation between data that is collected and SilverBack’s various performance reports. The following table correlates the data that is collected using Collection Fault Monitors, and the associated performance reports.

Monitor Type	Correlating Performance/Security Report
Active Directory Address Book	Active Directory Address Book
Active Directory Authentication	Active Directory Authentication
Active Directory DNS	Active Directory DNS
Active Directory DRA (Replication)	Active Directory Replication
CPU	System CPU Utilization
Discovery	System Interface Utilization
Disk	System Disk Utilization
DNS	Port Monitor Availability & Port Monitor Latency
Exchange 2000 IS Storage Groups	Exchange 2000/2003 IS Storage Groups
Exchange 2000/2003 IS	Exchange 2000/2003 Information Store
Exchange 2000/2003 Mail Server	Exchange 2000/2003 POP/IMAP
Exchange 2000/2003 MTA	Exchange 2000/2003 Message Transfer Agent
Exchange 2000/2003 SMTP	Exchange 2000/2003 SMTP
Exchange 2003 IS Storage Groups	Exchange 2000/2003 IS Storage Groups
FTP	Port Monitor Availability & Port Monitor Latency
HTTP	Port Monitor Availability & Port Monitor Latency
HTTPS	Port Monitor Availability & Port Monitor Latency
Interface	System Interface Utilization
Interface Up/Down	Network Interface Utilization & System Interface Utilization
Memory	System Memory Utilization
MS SQL	Port Monitor Availability & Port Monitor Latency
Netware	Port Monitor Availability & Port Monitor Latency
Operating System	System Availability
Oracle	Port Monitor Availability & Port Monitor Latency
Patch Scan	Missing Patches by Device
POP3	Port Monitor Availability & Port Monitor Latency
SMTP	Port Monitor Availability & Port Monitor Latency
SQL Server Activity	SQL Server Activity
SQL Server Locks and Latches	SQL Server Locks and Latches
SQL Server Log	SQL Server Logs
SQL Server Memory	SQL Server Memory Statistics
SQL Server Scans and Searches	SQL Server Scans and Searches
Sybase	Port Monitor Availability & Port Monitor Latency
Syslog	None - not polled
Vulnerability Scan	Vulnerability Summary by Device
Windows Event Log Discovery	Windows Event Logs
Windows Event Log Polling	Windows Event Logs
Windows Process	Windows Processes
Windows Service	Windows Services
Windows Service Status	Windows Services

* Most of the alerts generated by Collection Fault Monitors will automatically clear. However, alerts generated by syslog monitoring will not.