nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
- SolarWinds Academy
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

NPM packet loss alert

FormerMember

I recently turned on High Packet Loss monitoring, threshold set to >20%. However, after getting several alerts per day, I've realized that NPM must be basing it's measurement on some small number of pings, like 5 -- and thus is triggering 20% loss off just a single spurious packet drop.

Is there a way to make this alert more useful? For example, (a) increase the number of pings to make the results more granular, or (b) tell S.W. to follow up a single detected packet drop with a more proper test -- like 100+ pings?

Thanks for any thoughts...
Jim