The PassiveMonitorActivityLog table stores Passive Monitor data collected by SNMP Trap, Syslog, and Windows Event Log monitoring.
In most cases, a very large table is the result of WhatsUp collecting unnecessary or unwanted passive monitor data.
1. Verify Passive Monitor Listener configuration
The first step is to ensure you are only collecting data for passive monitors you have explicitly configured for your devices. To do this, ensure that for the both the SNMP Trap Listener and the Syslog Listener, you are not accepting unsolicited messages. You can verify this configuration in Program Options.
To verify Passive Monitor Listener configuration:
2. Remove unnecessary data from the database
After WhatsUp Gold is configured to collect data from only passive monitors that are assigned to devices, the next step is to clear the unneeded data already collected from the database.
Do this by removing all passive monitor data collected by the application. This removes all passive monitor data that appears in the SNMP Trap Log, Syslog Entries, and Windows Event Log reports. Any actions triggered by an incoming passive monitor event will still appear in the Action Log.
Important: We recommend making a backup of your WhatsUp database should you need to reverse any of the following changes.
To remove all passive monitor data from the WhatsUp database:
>sqlcmd -E -S "%COMPUTERNAME%\WHATSUP" -Q "TRUNCATE TABLE [WhatsUp].[dbo].[PassiveMonitorActivityLog]"
Note: Replace %COMPUTERNAME%
with the name of the WhatsUp computer.
The command listed above assumes you are using the SQL Server 2005 Express Edition database that is installed with WhatsUp Gold. If you are using an alternate database configuration, contact your database administrator to determine what information should be included with the "-S" switch.
After you have removed all the Passive Monitor data from the WhatsUp database, you can optionally shrink the WhatsUp database files to reclaim disk space on the SQL server.
To shrink the WhatsUp database:
>sqlcmd -E -S "%COMPUTERNAME%\WHATSUP" -Q "DBCC SHRINKDATABASE ('WhatsUp', 20)"
Note: Replace %COMPUTERNAME%
with the name of the WhatsUp computer.
The database shrink could take quite some time depending on the size of the database and system resources, but reports a short database space analysis after completion.
Note: You can abort the shrink process at any time by using the [CTRL] + [C] keystroke sequence.
More information on the "DBCC SHRINKDATABASE" command can be found on Microsoft's web site at:
http://msdn.microsoft.com/en-us/library/ms190488.aspx
Important: After you reclaiming database space, you should examine your passive monitors' configuration. You can do this easily by viewing the the Total Passive Monitors by Type dashboard report (available on any Home dashboard), and the system-level SNMP Trap Log, Syslog Entries, and Windows Event Log reports. If you have passive monitors assigned to "talkative" devices, or you have monitors which are not exclusive enough in their search criteria assigned to your WhatsUp devices, you may re-encounter this problem as more passive monitor data is collected by the system.