Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > QoE is not able to reliably classify custom HTTP applications based on specific URL path

QoE is not able to reliably classify custom HTTP applications based on specific URL path

Table of contents
No headers

QoE is not able to reliably classify custom HTTP applications based on a specific URL path. (for example, you can have two applications, one with filter on http://cp.mywebsite.com/display/DPIRD/ and another on http://cp.mywebsite.com/display/NPMRD/).
 

The issue is caused by the KeepAlive feature of HTTP protocol. Because of this, only one connection is opened during the whole time when the user browses on a single server, even when he or she visits different URLs on this server. QoE classifies the application after the initial contact between the user and the server and any subsequent changes in the URL are not reflected.

Last modified

Tags

Classifications

Public