QOE Admin Guide

Copyright 1995-2014 SolarWinds Worldwide, LLC.
All rights reserved

worldwide. No part of this document may be reproduced by any means nor
modified, decompiled, disassembled, published or distributed, in whole or in part,
or translated to any electronic medium or other means without the written consent
of SolarWinds. All right, title, and interest in and to the software and
documentation are and shall remain the exclusive property of SolarWinds and its
respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER
TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON
SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER
INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND
NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS,
NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING
IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF
SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
The SolarWinds, the SolarWinds & Design, ipMonitor, LANsurveyor, Orion, and
other SolarWinds marks, identified on the SolarWinds website, as updated from
SolarWinds from time to time and incorporated herein, are registered with the U.S.
Patent and Trademark Office and may be registered or pending registration in
other countries. All other SolarWinds trademarks may be common law marks or
registered or pending registration in the United States or in other countries. All
other trademarks or registered trademarks contained and/or mentioned herein are
used for identification purposes only and may be trademarks or registered
trademarks of their respective companies. Microsoft, Windows, and SQL
Server are registered trademarks of Microsoft Corporation in the United States
and/or other countries.
Version 1.0, draft revised 6.5.2014
Contents
About SolarWinds
SolarWinds, Inc develops and markets an array of network management,
monitoring, and discovery tools to meet the diverse requirements of todays
network management and consulting professionals. SolarWinds products
continue to set benchmarks for quality and performance and have positioned the
company as the leader in network management and discovery technology. The
SolarWinds customer base includes over 45 percent of the Fortune 500 and
customers from over 90 countries. Our global business partner distributor network
exceeds 100 distributors and resellers.
Contacting SolarWinds
You can contact SolarWinds in a number of ways, including the following:
Team
Sales
Contact Information
sales@solarwinds.com
www.solarwinds.com
1.866.530.8100
+353.21.5002900
Technical Support www.solarwinds.com/support/
User Forums
www.thwack.com
Conventions
The documentation uses consistent conventions to help you identify items
throughout the printed and online library.
Convention
Bold
Italics
Fixed font
Specifying
Window items, including buttons and fields.
Book and CD titles, variable names, new terms
File and directory names, commands and code
examples, text typed by you
Straight brackets, as in
Optional command parameters
[value]
Curly braces, as in
Required command parameters
{value}
Logical OR, as in
Exclusive command parameters where only one of the
value1|value2
options can be specified
Contents
Table of Contents
About SolarWinds
Contacting SolarWinds
Conventions
Table of Contents
Chapter 1: Introduction
User Scenario
11
Requirements, Installation, and Configuration
11
Chapter 2: Deploying Packet Analysis Sensors
12
Deploying a Network Sensor
13
To deploy a Network sensor:

Deploying a Server Sensor
13
14
To deploy a Server sensor:
15
Advanced Sensor Configuration
16
Configuring the monitored interface

To change the interface monitored by a sensor:
Configuring the CPU cores and memory allocated
To change the number of CPU cores and memory allocated to the
sensor:
Chapter 3: Configuring Nodes and Applications to Monitor
Defining nodes to monitor for a Network sensor
To add nodes for a Network sensor to monitor:
Defining nodes to monitor for a Server sensor
Monitor QoE Sensors
16
16
17
17
18
18
18
19
19
To add a sensor:
19
To disable a Sensor
21
To delete a Sensor
21
To delete nodes from Network sensors
21
To view the status of the Sensor
21
Monitor QoE Applications Page

Selecting pre-defined applications
To enable a pre-defined application:
Defining custom HTTP application
To create a custom HTTP application:
Licensing Details
To view license details:
Chapter 4: Agent and Plugin Configuration
Agent Deployment Requirements
21
22
22
23
24
25
25
27
28
Accounts and Security Requirements:
28
Requirements for Open Ports:
28
Supported OS Requirements:
29
Agent Diagnostics
29
Quality of Experience Plugin
29
Chapter 5: Quality of Experience Resources
30
All QoE Applications
30
To change how nodes are listed:
30
Application Response Time (Time to First Byte) By Application
31
Application Response Time (Time to First Byte) By Node
32
Business Related vs. Social Traffic
33
Data Volume By Application
34
Data Volume By Node
36
Network Response Time (TCP Handshake) by Application
36
Network Response Time (TCP Handshake) by Node
37
Nodes Exceeding Thresholds
38
Quality of Experience Application Details
39
Quality of Experience Application Stats
39
Top XX Application Response Time (Time to First Byte)
40
Contents
To export a chart:
42
Zooming
42
Top XX Data Volume
43
To export a chart:
44
Zooming
44
Top XX Network Response Time (TCP Handshake)
45
To export a chart:
47
Zooming
47
Top XX Transactions
48
To export a chart:
49
Zooming
49
Traffic By Category
50
Traffic By Risk Level
51
Transactions By Application
51
Transactions By Node
52
Quality of Experience (QoE) is a new dashboard within NPM that allows you to
monitor traffic on your network. QoE provides packet-level traffic information about
key devices and applications that you specify.
With QoE, you can:
l
Compare statistics like network response time (TCP Handshake) and application response time (Time to First Byte) to determine if the bottleneck is actually on your network, or if you need to call the server team.
l
Use data volume trends to pinpoint traffic anomalies and investigate the
cause.
Monitor risky types of traffic.
There are three steps you need to complete to get QoE monitoring traffic on your
network:
1. Deploy sensors (network and/or server) to Windows nodes where you want
traffic to be collected.
2. Specify the nodes and applications you want to collect traffic for.
Note that QoE does not automatically discover nodes and applications
you must define them before youll see traffic data in the QoE dashboard.
3. Allocate appropriate CPU cores and memory for the traffic load for each
sensor.
This traffic data is captured through a packet analysis sensor. The sensor collects
packets using either a dedicated Windows SPAN or Mirror port monitor or directly
on your Windows server. It captures packets from the local network interface
(NIC) and analyzes them to calculate metrics for application performance
monitoring. These metrics provide information about application health and allow
you to identify possible application performance issues before they get reported
by end-users. You define Quality of Experience nodes you want to monitor, and
select application traffic for which you want to monitor traffic. You can manage
these sensors through the easy to use web-based management interface.
With the ability to analyze packet traffic, QoE provides real observed network
response time (NRT) and application response time (ART). In addition, QoE has
10
User Scenario
the ability to classify and categorize traffic for over 1000 different applications by
associated purpose and risk-level.
User Scenario
Issue
A web server is providing an important web application. Your users are
encountering response times that are too long and also encountering outages.
Troubleshooting by QoE:
Follow the bullets below to troubleshoot the issue.
l
l
Remotely deploy a Server sensor directly on the web server.

Define which application(s) should be monitored, and let the data be collected for a period of time to establish some trends.
Determine if the issue is on the network side or if there is a problem with the
application.
Check related statistics and historical data.
Requirements, Installation, and Configuration

QoE is simply an additional sub-tab within NPM, and as such it is installed with
NPM. QoE does not require any additional hardware beyond what is required by
NPM.
11

Once NPM is installed, you must deploy Packet Analysis Sensors (agents) to
devices that you want to use as packet-level traffic collectors. Sensors are
deployed, configured, and managed from within NPM.
Note: Sensors can be deployed on Windows Server 2008 64-bit or later, or
Windows 7 64-bit or later. 32-bit operating systems are not supported.
Sensors include an agent that collects pcap data and then processes the data for
QoE statistics. In general, all non-Ethernet packets are ignored by QoE.
There are two types of sensors you can deploy:
l
Network sensors are deployed to a dedicated Windows device or VM that is

monitoring a SPAN or mirror port on your switch. Network sensors can be
used to monitor packet traffic from multiple specified nodes.
Server sensors are deployed directly on a Windows server, VM, or workstation where you want to collect local traffic data being sent to and from the
server.
12
Each type of sensor requires one license to deploy. NPM comes with one
network sensor license and one server sensor license. Additional licenses
can be purchased depending on your traffic monitoring needs.
By default, sensors use one CPU core and one GB of memory. Allocating
additional CPU cores and memory after deploying your sensors is highly
recommended for optimal performance.

You need one Network Sensor license for each network sensor you wish to
deploy. NPM includes one Network Sensor license; you can purchase additional
licenses through solarwinds.com.
To deploy a Network sensor:
1. In the Orion Website Administration page, navigate to Settings > QoE Settings.
2. Click Manage QoE PacketAnalysis Sensors.
3. To specify a node as a packet analysis sensor, click Add Packet Analysis
Sensor.
The Add Packet Analysis Sensor wizard opens.
4. Select the Network option.
5. Click Add Nodes.
6. Choose the Windows nodes that you want to deploy your Network sensors
on. Remember, these nodes should be monitoring a SPAN or mirror port on
a switch or router. Sensors can only be deployed on Windows Server 2008
64-bit or later, or Windows 7 64-bit or later. 32-bit operating systems are not
supported.
13

7. Test the credentials for each node that you want to deploy your sensors on.
In the Add Packet Analysis Sensor page, select the newly added node, and
click Assign Credentials. Select an existing admin WMI username and
password or create a new one (credentials must be administrative WMI credentials, since NPM will be installing an agent on each node), and click
Submit. Click Test to test the credential.
8. Click Add Node(s) and Deploy Agent(s) to deploy an agent on the node.
NPM will deploy agents to the selected nodes. Deployment may take some
time and will run as a background process.
NOTE: QoE automatically chooses settings such as interface to capture
traffic data, as well as memory and CPU limits, during agent deployment.
You can change these settings once deployment is complete by selecting
the sensor and clicking Edit.
When agent installation is complete, you will see a message in the
notification bar.
You can also check on the deployment status on the Manage QoE Packet
Analysis Sensors page.
9. Specify which nodes and applications to monitor. The steps for specifying
nodes and applications can be found in See "Configuring Nodes and Applications to Monitor" on page 18.
Note: Network Sensors do NOT automatically discover nodes and applications.
You must configure them manually before traffic can be collected and data will
appear in the QoE dashboard.

You need one Server Sensor license for each server sensor you wish to deploy.
NPM includes one Server Sensor license; you can purchase additional licenses
through solarwinds.com.
14

To deploy a Server sensor:
Sensor.
4. Select the Server option.
5. Choose the Windows nodes that you want to deploy your Server sensors
on. Remember, these nodes should be individual Windows servers whose
traffic you want to monitor. Sensors can only be deployed on Windows
Server 2008 64-bit or later, or Windows 7 64-bit or later. 32-bit operating systems are not supported.
NPM will deploy agents to the selected nodes. Deployment may take some time
and will run as a background process.
NOTE: QoE automatically chooses settings such as interface to capture traffic
data, as well as memory and CPU limits, during agent deployment. You can
change these settings once deployment is complete by selecting the sensor and
clicking Edit.
When agent installation is complete, you will see a message in the notification
bar.
Analysis Sensors page. When the status displays as Connected, deployment has
been completed successfully.
15
After your Server sensor has been deployed, you need to specify which nodes
and applications you want to collect traffic data for. The easiest way to do this is to
follow the link in the notification bar to the Manage QoE Packet sensors page,
select the sensor, and click Edit.
NOTE: Server Sensors automatically begin monitoring pre-selected applications
on the node they are installed on, including CIFS, FTP, HTTP, MS SQL, RDP,
and SNMP. You can change which applications are monitored after the Server
sensor has been deployed.

NOTE: Sensors cannot be edited until they have been fully deployed. You will be
notified when your sensor has been deployed, or you can check the Manage QoE
Nodes page to see if the sensor shows its status as Connected.
Configuring the monitored interface

When you deploy a sensor, NPM chooses the first available interface to monitor
for traffic. Once the sensor is installed, you can go back and change the
monitored interface.
To change the interface monitored by a sensor:
1. Select the sensor you want to edit.

2. Click the Edit Sensor button.
3. Change the Interface to capture QoE data to the desired interface. You
should see all available managed interfaces in the drop-down list.
16
Configuring the CPU cores and memory allocated

When you deploy a sensor, NPM allocates ONE CPU core and ONE GB of
memory to the sensor. Once the sensor is installed, you can go back and change
the allocated CPU cores and memory.
To change the number of CPU cores and memory allocated to the sensor:
1. Select the sensor you want to edit.

2. Click the Edit Sensor button.
3. In the Memory field, select the number of GB you want to allocate to the
sensor. If you allocate less than the recommended amount of memory, you
may see reduced performance since packets may not be processed.
For sensors, the memory usage scales with the traffic load. For every added
CPU, 15 MB is taken from a global packet sensor pool. The remainder of
the pool is used for keeping information about flows, so the more flows are
going on the line, the more memory you would need.
4. In the CPU Cores field, select the number of CPU cores you want to allocate to the sensor. If you allocate fewer than the recommended number of
cores, you may see reduced performance since packets may be dropped.
Some guidelines for allocating CPU cores:
l
l
l
l
l
1 core - Not recommended/very low loads

1-2 cores - Suitable for 100 Mbps links
3-4 cores - Gigabit links with low utilization
5-6 cores - Gigabit links with medium utilization
7+ cores - Gigabit links with heavy utilization
17
Chapter 3: Configuring Nodes and Applications to Monitor
Chapter 3: Configuring Nodes and

Applications to Monitor
After you have deployed Network and Server sensors, you must specify the
nodes and applications whose traffic you want to monitor. QoE does not
automatically discover nodes or applications.
l
Network sensors must manually have nodes and applications to monitor

specified before traffic for these nodes can be collected and data will appear
in the QoE dashboard.
Server sensors automatically begin monitoring pre-selected applications,
including CIFS, FTP, HTTP, MS SQL, RDP, and SNMP, on the node they
are installed on. You can change which applications are monitored after the
sensor has been deployed.
For each node you choose to add to QoE, youll also select specific applications
to watch for. QoE comes with over 1000 pre-defined applications that you can
choose from, such as FTP, RDP, CIFS, SQL, Exchange, and so forth. Selecting
one of these applications is as easy as choosing from the list of all available
applications. You can also define your own custom HTTP applications.
NOTE: Because of the hardware requirements needed to process large amounts
of traffic, SolarWinds recommends that you preferentially monitor business-critical
nodes and applications.
Defining nodes to monitor for a Network sensor

You must manually specify the nodes and applications you want your Network
sensors to collect traffic data for. After the Network sensor has been successfully
deployed, you can add nodes to monitor.
To add nodes for a Network sensor to monitor:
1. Navigate to the Manage QoE Sensors page.

2. Expand the Network sensor that you want to add a node to.
18
Monitor QoE Sensors

3. Click the Add Node to Monitor button.
4. On the Create QoE Node page, choose the managed nodes you want to
monitor with this network sensor, then click Next.
5. On the Select QoE Applications page, choose the applications you want to
monitor for these nodes, then click Next.
6. Review your selections on the Summary page, then click Finish.
You should see the nodes and applications selected if you expand the Network
sensor you just configured.
Defining nodes to monitor for a Server sensor

There is no node to define for a server sensor. Once deployed, a Server sensor
automatically begins collecting and analyzing traffic for the node it has been
deployed on. This is the only node that can be monitored by the Server sensor.
For additional information, see See "Deploying a Server Sensor" on page 14.
You can see the monitored node on the QoE Node Management page.
Monitor QoE Sensors

Nodes that are defined as QoE Sensors appear on this page, as well as the
nodes and applications that are being watched by each node.
Use the Add Packet Analysis Sensor wizard to add node(s) on which to deploy
packet analysis sensors, which allow you to collect packet data on those nodes.
Note: Each sensor can support up to 50 applications.
Note: PPPoE packets are not processed by QoE sensors.
To add a sensor:
Sensor.
19
To add a sensor:
4. Select either the Server or Network sensor type option.
l Server sensor - Installs an agent and QoE sensor on the selected Windows servers, then collects data locally on those servers.
l Network sensor - Installs an agent and QoE sensor on dedicated Windows servers monitoring SPAN or mirror ports. Collects packet data
for any specified nodes/applications sending traffic through the monitored port.
5. Click Add Nodes.
6. Choose the Windows nodes that you want to deploy your Network sensors
on. Remember, these nodes should be monitoring a SPAN or mirror port on
a switch or router. Sensors can only be deployed on Windows Server 2008
64-bit or later, or Windows 7 64-bit or later. 32-bit operating systems are not
supported.
NPM will deploy agents to the selected nodes. Deployment may take some
time and will run as a background process.
NOTE: QoE automatically chooses settings such as interface to capture
traffic data, as well as memory and CPU limits, during agent deployment.
You can change these settings once deployment is complete by selecting
the sensor and clicking Edit.
When agent installation is complete, you will see a message in the
notification bar.
Analysis Sensors page.
20

9. Specify which nodes and applications to monitor. The steps for specifying
nodes and applications can be found in See "Configuring Nodes and Applications to Monitor" on page 18.
Note: Network Sensors do NOT automatically discover nodes and applications.
You must configure them manually before traffic can be collected and data will
appear in the QoE dashboard.
To disable a Sensor
Sensors are enabled by default. You can disable a sensor as a troubleshooting

tool. You might also want to disable a sensor if it is overloaded with traffic, or if
you want to apply the sensor license to another device. A disabled sensor will not
collect traffic information about any of the nodes listed for that sensor.
1. In the Manage Quality of Experience (QoE) Packet Analysis Sensors
page, select the sensor and click Disable Sensor.
To delete a Sensor
Deleting a sensor also deletes all of the nodes and applications associated with
the sensor. It does NOT delete the nodes from Orion or the applications from the
Manage QoE Applications page).
page, select the sensor and click Delete Sensor.
To delete nodes from Network sensors
Nodes cannot be deleted from Server sensors since they only record traffic on the
node the sensor is installed on.
To view the status of the Sensor
A status can be whether sensor is connected or not, if it is in the process of being

deployed, and so forth. You can also access the Manage Agents page from here
by clicking Manage Agent next to the sensors status.
page, view the Agent Status column.

To access that Manage QoE Applications page:
21

1. Navigate to Settings >QoE Settings >Manage QoE Applications.
If there are no nodes being monitored, no applications will appear in this list. You
must first add a QoE Network or Server Sensor before you can enable any
applications.
If applications are listed and shown as Enabled, they are currently being
monitored on at least one node.
Applications can be Disabled, which means that no traffic for the application will
be collected on any node.
Note: You shouldn't assign more than 50 applications to a node due to
performance issues.

QoE includes over 1000 pre-defined applications. You can enable and apply a
single application to multiple nodes from The Manage QoE Applications page.
To enable a pre-defined application:
1. Navigate to Settings, then select Manage QoE Applications.

2. Click Add New.
22

3. On the Select Application page, choose Choose a pre-configured application. The list of available applications displays.
Note that applications (either pre-configured or custom HTTP applications)
that are already enabled will not appear in the list.
4. Use the Search or Group By options to find the application youre looking
for, then select it and click Next.
5. On the Configure Application page, change the Category, Risk Level, or
Productivity Rating if desired, then click Next.
6. On the Configure Data Collection page, choose the node(s) you want to
monitor for this type of traffic. Only nodes that have already been specified
as nodes to monitor (on the Manage QoE Nodes page) appear in this list.
Click Next.
7. Review your choices on the Summary page, then click Finish.
Your newly enabled application will appear on the Manage QoE
Applications page in alphabetical order.
Defining custom HTTP application

In addition to choosing from pre-defined applications, you can also define custom
HTTP apps, and then add them to nodes you are monitoring.
23

1. Navigate to Settings, then select Manage QoE Applications.

2. Click Add New.
3. On the Select Application page, select Create a new HTTP application,

then click Next.
4. On the Configure Application page, enter the name and description of the
application youre creating, then choose the Category, Risk Level, and Productivity Rating appropriate for the application.
5. Set the URL Filter. This specifies the HTTP application traffic to monitor.
When you choose which filter to use in the drop-down, notice that the
example changes to indicate how the accompanying text field will be used.
For example, selecting Hostname contains changes the help text to

http://*...*/path/page.html. Any text you enter will be included in the filter
where the appears.
24
Licensing Details
6. Enter the hostname or URL for your filter, then click Next.
7. On the Configure Data Collection page, choose the node(s) you want to
monitor for this type of traffic. Only nodes that have already been specified
as nodes to monitor (on the Manage QoE Nodes page) will appear in this
list.
8. Click Next. Review your choices on the Summary page, then click Finish.
9. Your new application will appear on the Manage QoE Applications page
in alphabetical order.
Licensing Details
NPM includes two QoE licenses by default: one Packet Analysis for Networks
license and one Packet Analysis for Servers license. An appropriate license is
required to deploy a sensor.
QoE has a 30-day evaluation license. It also has a commercial license. The
Evaluation license must be activated before you can activate the commercial
license. There is no need to restart any services after entering commercial license
keys.
1. In the web console, navigate to Settings >Details > License Details.

Under Packet Analysis Sensors, you can view module name, version, and
service pack information.
25
26

The agent is a piece of software providing a communication channel between the
Orion server and the client machine with a QoE sensor.
When you deploy a Network or Server sensor, an agent and special QoE plugin
are deployed on that node. Deployment can take some time, and until the Agent
has fully deployed, it cannot be edited.
Note: Port 17777 must be open for machines hosting the agent.
You can check deployment status on the Manage QoE Packet Analysis Sensors
page. Agent status can be as follows:
l
l
Agent Deployment in Progress

Connected
If you need to manage the agent for any reason, click Manage Agent in the Agent
Status column.
This will take you to the Edit Agent Settings page.
27
Agent Deployment Requirements

The following requirements must be met in order for agent deployment to be
successful:
Accounts and Security Requirements:
l
l
l
Accounts must have access to the remote administrator share.

Updated Root Certificates.
For Windows Vista & Windows 7 computers in a workgroup:
o UAC must either be disabled or the built in Administrator account
must be used for deployment.
Requirements for Open Ports:

135 Microsoft EPMAP (DCE/RPC Locator service).
445 Microsoft-DS SMB file sharing.
17777 (TCP) For agents to function properly.
28
l
l
Windows Server 2008 64-bit or later

Windows 7 64-bit or later
During the deployment process, all prerequisites will be installed automatically,

(e.g. VC Redistributables, .NET Framework, and so on).
Note: The remote machine may be restarted at the end of the deployment
process.
Agent Diagnostics
The Diagnostics section in the Troubleshooting section of the Edit Agent Settings
page lets you download diagnostic logs.
1. In the Edit Agent Settings page, expand the Troubleshooting heading.
2. (optional) (Select a Log level. The default is WARN.
3. Click Download to download the most recent troubleshooting files.
or click Collect new diagnostics to generate current diagnostics.
The following logs are downloaded:
l
l
l
l
l
l
SolarWinds.Agent.Service.exe.0001.log.txt
SolarWinds.Agent.Discovery.Plugin.exe.txt
SolarWinds.Agent.Service.exe.txt
DPIBusinessLayer.log
DPIProbe.log
DPIProbe.Packets.log
Quality of Experience Plugin

In addition to installing an agent, deploying a sensor enables a special QoE
plugin. This plugin has the following states:
l
l
l
l
Unknown Have not yet received QoE data from this node
Not present Plugin has not yet been deployed (agent may or may not have
finished deploying).
Up NPM is receiving QoE data from this node
Warning NPM has not received QoE data from this node for more than 15
minutes
Down NPM has not received QoE data from this node for more than 20
minutes
29
Chapter 5: Quality of Experience Resources
Chapter 5: Quality of Experience

Resources
This section describes available resources. All resources cover a 24-hour time
period by default (zoom). The default grouping for Resources is None, meaning
that items tracked by Resources will not be grouped at all.
All QoE Applications

This resource ranks all nodes with QoE traffic.
To change how nodes are listed:

1. Click Edit.
2. (optional) Enter a new title, or subtitle. Leave the subtitle field blank to have
Grouped By generated automatically.
3. Select the drop-down lists of Grouping Nodes, Category, Risk Level, and
30
Application Response Time (Time to First Byte) By Application

Productivity Rating and select the item you want to display.
4. Click Submit.
Application Response Time (Time to

First Byte) By Application
The Top 10 Application Response Time (Time to First Byte) resource let you view
the application response time for one or several applications.
1. In Quality of Experience, in the Top 10 Application Response Time (Time to
First Byte) resource, click an application.
All checked applications are displayed in the graph, each with a corresponding
color in the left column.
In the application view, the Top 10 Application Response Time (Time to First
Byte) resource is displayed. The applications are displayed below the graph, with
its data displayed in graph format and in the Average Application Response Time
and Peak Value columns under the graph.
31
Application Response Time (Time to First Byte) By Node
Application Response Time (Time to

First Byte) By Node
The Top 10 Application Response Time (Time to First Byte) resource let you view
the application response time for an individual node.
1. In Quality of Experience, in the Top 10 Application Response Time (Time to
First Byte) resource, click a node.
In the application view, the Top 10 Application Response Time (Time to First
Byte) resource is displayed. The node is displayed below the graph, with its data
displayed in graph format and in the Average Application Response Time and
Total Peak Value columns under the graph.
32

This resource compares business traffic against social traffic. The productivity
rating of the application can be changed in See "Monitor QoE Applications Page"
on page 21. You can click a color to get more details about the productivity rating.
33
1. Click Edit.
3. Select the drop-down list of Data to Summarize or Selected Time Period
and select the items you want to display.
4. Click Submit.

The Top 10 Data Volume resource let you view the data volume for one or
several applications.
1. In Quality of Experience, in the Top 10 Data Volume resource, click an
application.
34

In the application view, the Top 10 Data Volume resource is displayed. The
applications are displayed below the graph, with data displayed in graph format
and in the Average Data Volume and Total Data Volume columns under the
graph.
35
Data Volume By Node
Data Volume By Node

The Top 10 Data Volume resource let you view the data volume for an individual
node.
1. In Quality of Experience, in the Top 10 Data Volume resource, click an
application.
In the application view, the Top 10 Data Volume resource is displayed. The node
is displayed below the graph, with its data displayed in graph format and in the
Average Data Volume and Total Data Volume columns under the graph.
Network Response Time (TCP Handshake) by Application

The Top 10 Network Response Time (TCP Handshake) resource lets you view
the network response time for one or several applications.
1. In Quality of Experience, in the Top 10 Network Response Time (TCP Handshake) resource, click an application.
36

In the application view, the Top 10 Network Response Time (TCP Handshake)
resource is displayed. The applications are displayed below the graph, with its
data displayed in graph format and in the Average Network Response Time and
Peak Value columns under the graph.

The Top 10 Network Response Time (TCP Handshake) resource let you view the
network response time for an individual node.
1. In Quality of Experience, in the Top 10 Network Response Time (TCP Handshake) resource, click an application.
In the application view, the Top 10 Network Response Time (TCP Handshake)
resource is displayed. The node is displayed below the graph, with its data
37

displayed in graph format and in the Average Network Response Time and Peak
Value columns under the graph.

This resource ranks all nodes exceeding specified thresholds.
38
Quality of Experience Application Details

To change how nodes exceeding thresholds are displayed:
1. Click Edit.
3. Select the drop-down lists of Selected Time Period, Grouping Nodes, Category, Risk Level, and Productivity Rating and select the item you want to
display.
4. Click Submit.
Quality of Experience Application

Details
This resource provides details for the selected application.
1. Click an application in the Top 10 Application Response Time (Time to First

Byte), Quality of Experience Application Stats, or Top 10 Network
Response Time (TCP Handshake) resources.
2. In the Quality of Experience Application Details resource, Click Manage.
3. The Manage Quality of Experience Applications page opens, from which
you can modify the Category, Risk Level, or Productivity Rating settings.
Quality of Experience Application

Stats
This resource lists QoE application statistics.
39
1. Click Edit.
3. Select the drop-down list of Selected Time Period and select the time period
for which you want to display statistics.
4. Click Submit.
Top XX Application Response Time

(Time to First Byte)
This resource ranks application response times.
40
If the application is selected, its data (if any) is displayed in the graph in the
application's assigned color.
To change how response times are ranked:
1. Click Edit.
a. (optional) Enter a new title, or subtitle. Leave the subtitle field blank to
have Grouped By generated automatically.
b. (optional) Enter the number of items you want the resource to display
in the Number of Items text box.
41
To export a chart:
c. (optional) Select the drop-down list of the Group By, Category, Risk
Level, or Productivity Rating drop-down lists and select the items you
want to display.
d. (optional) Select the Default Zoom Range drop-down list and select a
range.
e. (optional) Select the Amount of Historical Data to Load drop-down list
and select an amount of data to load.
f. (optional) Select the Sample Interval drop-down list and select a
sample interval to use.
g. (optional) Click Advanced, and enter a chart title and subtitle.
2. Click Submit.
To export a chart:
1. Click Export.
2. (optional) Enter a title and subtitle for the chart, make selections in the
Default Zoom Range, Time Period, and the Sample Interval drop-down lists.
3. In the Chart Size box, enter a width and height in pixels for the chart in the
Width and Height text boxes.
4. Click Refresh to display the data on the current page or click Submit to exit
the current page and display the data on the Quality of Experience Summary page.
5. Click Export to XLS to export the data to Excel, or click Export to HTML to
export the data to HTML.
Zooming
You can have the chart show a predetermined, hourly time period of data by
clicking on any one of the three Zoom buttons; 30m, 1h, or 2h,. Alternatively, you
can have the chart show a specific time range by dragging the mouse over a
small area of the chart.
Once you have a time period selected, the lower chart will zoom to the starting
and ending values of the selected time period. With the lower chart you can zoom
in further by fine tuning the view with the sliders. The main view of the chart will
display the selected time period between the two sliders of the lower chart.
Moving the mouse over the main chart will reveal a tooltip with more detailed
information about the specific time period the mouse is hovering over.
42
Top XX Data Volume
Top XX Data Volume

This resource ranks Quality of Experience applications by data volume. Use the
slider below the graph to change the display. Click the Zoom interval you want to
view.
To change how data volume is ranked:
43
To export a chart:
1. Click Edit.
Level, or Productivity Rating and select the items you want to display.
range.
sample interval.
2. Click Submit.
To export a chart:
1. Click Export.
Zooming
44

Top XX Network Response Time

(TCP Handshake)
This resource ranks the top 10 network response times.
45
To change how network response times are listed
1. Click Edit.
46

range.
sample interval.
2. Click Submit.
To export a chart:
1. Click Export.
Zooming
47
Top XX Transactions
Top XX Transactions
This resource ranks the top 10 transactions. Use the slider below the graph to
change the display. Click the Zoom interval you want to view.
48
Top XX Transactions
1. Click Edit.
range.
sample interval.
2. Click Submit.
To export a chart:
1. Click Export.
Zooming
49
Traffic By Category
Traffic By Category
This resource displays traffic by category. The category of the application can be
changed in See "Monitor QoE Applications Page" on page 21.
1. Click Edit.
3. Select the drop-down list of Data to Summarize or Selected Time Period
and select the items you want to display.
4. Click Submit.
50

This resource displays traffic by Risk Level. The risk level of the application can
be changed in See "Monitor QoE Applications Page" on page 21.
1. Click Edit.
3. click the Data to Summarize or Selected Time Period drop-down list boxes
and select the item you want to display.
4. Click Submit.
Transactions By Application
The Top 10 Transactions resource let you view transaction data for one or several
applications.
1. In Quality of Experience, in the Top 10 Transactions resource, click an
application.
In the application view, the Top 10 Transactions resource is displayed. The
applications are displayed below the graph, with its data displayed in graph
51
format and in the Average # of Transactions and Total # of Transactions columns
under the graph.
The Top 10 Transactions resource let you view transaction data for an individual
node.
1. In Quality of Experience, in the Top 10 Transactions resource, click an
application
In the application view, the Top 10 Transactions resource is displayed. The node
is displayed below the graph, with its data displayed in graph format and in the
Average # of Transactions and Total # of Transactions columns under the graph.
52
53

QOE Admin Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

QOE Admin Guide

Transféré par

Droits d'auteur :

Formats disponibles

Copyright 1995-2014 SolarWinds Worldwide, LLC.

All rights reserved

options can be specified

Requirements, Installation, and Configuration

Chapter 2: Deploying Packet Analysis Sensors

Deploying a Network Sensor

To deploy a Network sensor:

To deploy a Server sensor:

Advanced Sensor Configuration

Configuring the monitored interface

To delete nodes from Network sensors

To view the status of the Sensor

Monitor QoE Applications Page

Accounts and Security Requirements:

Requirements for Open Ports:

Quality of Experience Plugin

Chapter 5: Quality of Experience Resources

All QoE Applications

To change how nodes are listed:

Application Response Time (Time to First Byte) By Application

Application Response Time (Time to First Byte) By Node

Business Related vs. Social Traffic

Data Volume By Application

Data Volume By Node

Network Response Time (TCP Handshake) by Application

Network Response Time (TCP Handshake) by Node

Nodes Exceeding Thresholds

Quality of Experience Application Details

Quality of Experience Application Stats

Top XX Application Response Time (Time to First Byte)

Top XX Data Volume

Top XX Network Response Time (TCP Handshake)

Traffic By Risk Level

Monitor risky types of traffic.

Remotely deploy a Server sensor directly on the web server.

Requirements, Installation, and Configuration

Chapter 2: Deploying Packet Analysis Sensors

Chapter 2: Deploying Packet Analysis Sensors

Network sensors are deployed to a dedicated Windows device or VM that is

Deploying a Network Sensor

Deploying a Network Sensor

Deploying a Server Sensor

Deploying a Server Sensor

Deploying a Server Sensor

Advanced Sensor Configuration

Advanced Sensor Configuration

Configuring the monitored interface

1. Select the sensor you want to edit.

Advanced Sensor Configuration

Configuring the CPU cores and memory allocated

1. Select the sensor you want to edit.

1 core - Not recommended/very low loads

Chapter 3: Configuring Nodes and Applications to Monitor

Chapter 3: Configuring Nodes and

Network sensors must manually have nodes and applications to monitor

Defining nodes to monitor for a Network sensor

1. Navigate to the Manage QoE Sensors page.

Monitor QoE Sensors

Defining nodes to monitor for a Server sensor

Monitor QoE Sensors

Monitor QoE Applications Page

Sensors are enabled by default. You can disable a sensor as a troubleshooting

A status can be whether sensor is connected or not, if it is in the process of being

Monitor QoE Applications Page