• 更好的網路管理關鍵就是了解網路的頻寬和資源消耗。
• 避免頻寬和伺服器效能的衝突。
• 找出什麼應用程式或伺服器在使用你的頻寬
• 可以替您的客戶主動提供更好服務品質
• 根據實際負載，減少購買頻寬和硬體的成本

使用簡單的 Windows 界面，你可以設置監測感應器和創建使用報告，可遠程存取 PRTG Network Monitor 在一個內置的網路伺服器提供使用的圖表。支援所有網路使用數據的常用方法:

• SNMP: Simple Network Management Protocol 是收集頻寬和網路使用情況數據的基本方法。它可以用來監測使用頻寬路由器和交換機以及裝置讀取像是記憶體，CPU負載等。
• Packet Sniffing: 藉著內置的Packet ，PRTG可以檢查所有網路數據封包，沿著LAN或WLAN去計算頻寬使用率。
• NetFlow: NetFlow的協議得到了大多數Cisco路由器測量頻寬使用，雖然是最複雜類型設置也是最強有力的方法，適合高流量的網路。

基於 Sniffer 和 NetFlow 的監控，PRTG 可以任意計算每個 IP 接口的頻寬，例如:在你的網路顯示當前的 Top Talkers, Top Connections 和 Top Protocols。 

這應用程式可以在所有 Windows 版本執行，和從 Cisco, HP, 3Com, Linksys, Nortel 等最多的網路產品相容，以及其他各種設備 (如Windows PCs或網路印表機)。

Licenses of PRTG differ by two parameters:

• The maximum number of sensors.
• The number of allowed core server installations.

sensors數計算:

The licensing options are based on the number of sensors. Each of the following items counts as one sensor:

• Monitoring traffic/bandwidth on one port of any device via SNMP (e.g. switch, firewall, server) using the MIB2 standard
• Monitoring errors/min, unicast packets/s, non-unicast packets/s on one port of a device via SNMP using the MIB2 standard
• Monitoring one other system parameter via SNMP (e.g. CPU, diskspace etc.) that is accessible via one OID value
• Monitoring traffic going through one local network card (NIC) via Packet Sniffing. If you use filtering then each set of filters counts as one sensor.
• Monitoring of one stream of data traffic via xFlow (NetFlow, sFlow) Monitoring. If you use filtering then each filterset counts as one sensor.

The number of actual hardware devices is not taken into account at all, only the number of sensors. For the "unlimited licenses" the number of sensors that can be monitored is not programmatically limited by the software itself, but may be limited by your software, hardware and network.

Recommended setup for most PRTG users

There are many parameters that influence the user experience of PRTG, but for the majority of PRTG users,
the following sizing recommendations for the hardware of the PRTG core server work fine.

We recommend that you run your PRTG core server installation

» directly on x64 server hardware or in a properly configured virtual environment (for more information, see section Running PRTG in virtual environments).
» on Windows Server 2019, Windows Server 2016, or Windows Server 2012 R2.

Note:  .NET Framework 4.7.2 or later must be installed on the core server system. For new PRTG core server installations, we recommend .NET Framework 4.8.

* For more information, see Running PRTG in virtual environments below.
** When you use more than 10 CPU cores, you might need to apply a CPU-splitting configuration in the Windows registry.

V = OK
▲= OK
♦ = not recommended
★=not officially supported: 請詢問友環業務

Note: Most PRTG users have 10 sensors per device on average. In most cases, a license for 1,000 sensors is therefore enough to monitor about 100 devices, for example.

Recommended setup for remote probes

We recommend that you run remote probes

» directly on compatible x86 hardware or in a properly configured virtual environment
(for more information, see section Running PRTG in virtual environments).
» on Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, or Windows 10.

Note: .NET Framework 4.7.2 or later must be installed on the probe system. For new installations, we recommend .NET Framework 4.8. 

* A remote probe system does not have any special disk requirements (< 1 GB). In general, we recommend at least 40 GB.

System Requirements for PRTG Remote Probes

• Hardware
  A PC or server with at least a dual core CPU and a minimum of 2048 MB RAM is sufficient for remote probes.
• Operating system
  We recommend that you use Microsoft Windows Server 2019, Microsoft Windows 10, or Microsoft Windows Server 2012 R2.
• Stable network connection
  Remote probes require a stable network connection between the PRTG server and the remote probe. Remote probes that connect to a PRTG hosted by Paessler server need a reliable internet connection. Unstable connections, for example via 3G, might work but it is possible that you lose monitoring data if the connection is non-reliable.

★ Why are remote probes helpful for monitoring with PRTG? Because they can extend your monitoring.

• Remote probes allow you to monitor different sub-networks that are separated from your PRTG on premises core server by a firewall and to keep an eye on remote locations. You can install one or more remote probes.
• Remote probes are useful if you want to distribute monitoring load by taking it from the system running the PRTG core server and putting it on one or more remote probe machines.
• You will need a remote probe if you want to monitor your local network using a PRTG hosted by Paessler instance.
• Remote probes may be suitable monitoring components in several individual scenarios that depend on your custom network setup.

Running PRTG in virtual environments

PRTG is an all-in-one monitoring solution with lots of different components that all rely on the performance and the stability of the system on which the PRTG core server runs. Here, virtual environments add even more layers of complexity. This needs to be considered when you want to set up your PRTG core server installation in a way that you can achieve the same level of performance as on a physical server.

Most PRTG core server installations from 500 to 5,000 sensors do not need any specific optimization regarding your virtual infrastructure.

If you run larger installations of PRTG with more than 5,000 sensors, please follow the instructions in our
Best Practice Guide: Running large installations of PRTG in a virtual environment.

 Particularly for virtual systems, make sure that you have a unique Windows security identifier per system