Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Orion Platform > Orion Documentation > Orion Platform Administrator Guide > Monitor Quality of Experience metrics > Limitations to Packet Analysis Sensors

Limitations to Packet Analysis Sensors

Table of contents
No headers
Created by Caroline Juszczak, last modified by Magdalena.Markova on Nov 03, 2016

Views: 536 Votes: 0 Revisions: 4

This Orion Platform topic applies to the highlighted products:

DPAIMEOCETSIPAMLMNCMNPMNTASAMSRMUDTVMANVNQMWPM

The number of nodes you can monitor is limited by the data throughput per node, the number of cores, and the amount of RAM available on the monitoring server.

The system requirements increase for every 100 Mbps of traffic.

sensor limitations value
Maximum throughput (NPAS and SPAS) 1 Gbps
Maximum number of nodes per sensor (NPAS) 50 nodes
Maximum number of node/application pairs
(NPAS and SPAS)
50,000 pairs
Maximum number of sensors deployed on your network 1,000 sensors
Maximum number of applications per node/sensor
(NPAS and SPAS)
1,000 applications per node
 
Last modified

Tags

Classifications

Public