Applications Systems

SolarWinds Platform database growing in size due to APM_WindowsEvent_Detail table

This article addresses an issue with the SolarWinds Platform database growing uncontrollably in size due to the APM_WindowsEvent_Detail table

First published date

8/7/2019 3:40 PM

Last published date

3/12/2025 9:31 PM

Overview

When monitoring servers in SAM, the APM_WindowsEvent_Detail table can grow the database size exponentially bringing the whole environment down.
 

Product section

Server Application Monitor

Cause

Monitored servers generate too many Event Logs that SAM picks up and saves them in the APM_WindowsEvent_Detail table

Resolution

Resolution 1

1. Identify the servers generating too many Windows Events
2. Temporarily disable the Windows Event Log monitors assigned to these servers
  • NOTE: If the Windows Event logs are coming from AppInsight templates, unmanage the entire application monitor
3. Wait 7 days(default) for the database maintenance to discard these Windows Events


Resolution 2

Truncate the APM_WindowsEvent_Detail table then manually run Database Maintenance. 
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

TRUNCATE TABLE APM_WindowsEvent_Detail