4 Replies Latest reply on Feb 25, 2016 5:46 PM by tgill80

    Traps and TrapVarbinds Tables

    tgill80

      Hello,

       

      I am seeing the following messages for the Traps and TrapVarbinds tables in the web console for Solarwinds NPM:

       

      TrapVarbinds reached 35603018 rows, which is above warning threshold of 5000000.

      Traps reached 6348226 rows, which is above warning threshold of 1000000.

       

      I found a Solarwinds KB article that suggests using the following query against the TrapVarbinds table:

       

      Delete from TrapVarBinds where TrapID not in (select TrapID from Traps)

       

      If i go ahead and delete some old trap entries from the Traps table, does this mean that i should note down the Trap IDs for the entries i am removing?

      I presume that i would have to enter these Trap IDs into the query above to remove them from the TrapVarbinds table.

       

      Wondering if someone could confirm this for me.

       

      Thanks,

       

      Taran

       

        • Re: Traps and TrapVarbinds Tables
          njoylif

          I wouldn't bother noting the trap IDs.  If you were going to do that for records or such you would archive them out somehow.  This basically removes [orphaned] data from TrapVarBinds table where there is no related trap id in the Traps table.

          you don't have to do anything but run the query.  the subquery in () gets the list and feeds to main query.

          • Re: Traps and TrapVarbinds Tables
            shuth

            Also note that the query will only remove any trap details from the TrapsVarBinds if the trap ID does not exist in the Traps table.

             

            If you are receiving a large number of traps, you will continue to see these messages. If you have trap retention still set to the default 7 days, you are receiving almost 900,000 traps a day. On a Summary page, you can add the Traps Summary resource and it will tell you how many traps you have received by trap type, IP address, hostname, or machine type. This will allow you to narrow down what devices are sending the majority of traps and what traps they are. From there, you can determine if you still need these traps or disable them.