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
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

Add Solarwinds internal communication to QoE?

wrgeorge1983

So we haven't dug much into QoE. I used to have to deal with a horrible and unresponsive we application, but then we decommissioned WUG and bought Solarwinds, so I haven't had a lot of use for it lately

Except now our Netflow storage volume is getting rather large and I'm starting to gather evidence to push our storage and server guys to give it some more juice.

It'd be nice to be able to use QoE to observe where and how the delays are manifesting themselves, but I believe nearly all of the relevant FrontEnd to BackEnd communication is on port 17777 and I can't find any way to get that added into QoE.