Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Getting message for Traps and Trapvarbinds exceeded its limit

HI all,

I have a report which tells me if there is anything wrong during the DB maintenance which happens every night.

Is this something to worry about? I saw the KB articles mentioned which says that the traps can be deleted or truncated. But not sure so need input on this.

Find more posts tagged with

Accepted answers

All comments

janene16

Yes, it will cause performance issues if left as is specially if multiple nodes are sending Traps per second.

Just imagine how many connection it will create on the database.

Also, if your just using SQL Express, it will consume the database space

pratikmehta003

So can i just follow the KB article? Also i checked the settings for traps retention in trap viewer, i see it is only for 2 days.

Am i missing something?

janene16

Yup you can definitely use this KB article:

SolarWinds Knowledge Base :: SQL is reporting that my Orion NPM database is currently out of space. How can I clear up s…

if your retention settings is already set that low, then most probably there's a device that keeps on sending the Traps. Better check the list of traps being received from your Traps Viewer, and create a Discard rule for it (if its not worth keeping)

To proceed, check this one out:

Tips and Tricks for Managing Traps and Syslog in Orion NPM

pratikmehta003

Thanks for the info. Let me see if that can be ran. I recently tried running query for de fragmentation on DB but it ended up in mess. Orion stopped working due to high utilization. Had to disable the query again to have it running fine as before