PRTG Ver 13 Manual Usuario

PRTG Net work Monit or User Manual
2015 Paessler AG
All rights reserved. No parts of this work may be reproduced in any form or by any meansgraphic,
electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval
systemswithout the written permission of the publisher.
Products that are referred to in this document may be either trademarks and/or registered trademarks
of the respective owners. The publisher and the author make no claim to these trademarks.
While every precaution has been taken in the preparation of this document, the publisher and the author
assume no responsibility for errors or omissions, or for damages resulting from the use of information
contained in this document or from the use of programs and source code that may accompany it. In no
event shall the publisher and the author be liable for any loss of profit or any other commercial damage
caused or alleged to have been caused directly or indirectly by this document.
Printed: Februar 2015 in Nuremberg

Contents
Table of Contents
Part 1 Welcome to PRTG Network M onitor 14

1 About this Document 15
2 Key Features 16
3 New in This Version 18
4 Available Licenses 19
5 System Requirements 21
Detailed System Requirements 23
Part 2 Quick Start Guide 32

1 ONEDownload, Installation, and First Login 33
2 TWOUsing the Configuration Guru 36
Part 3 Installing the Software 44

1 Download PRTG 45
2 Update From Previous Versions 47
3 Install a PRTG Core Server 51
4 Install a PRTG Cluster 56
5 Enter a License Key 57
6 Activate the Product 60
7 Install a PRTG Remote Probe 62
8 Install the Enterprise Console 67
9 Uninstall PRTG Products 71
Part 4 Understanding Basic Concepts 76

1 Architecture and User Interfaces 77
2 Clustering 81
3 Object Hierarchy 83
4 Inheritance of Settings 88
5 Tags 90
6 Dependencies 92
7 Scheduling 93
8 Notifying 94
9 Data Reporting 95
10 User Access Rights 96
11 IPv6 99
Part 5 Ajax Web InterfaceBasic Procedures 102

1 Login 104
2 SSL Certificate Warning 107
3 General Layout 110
3
Contents
4 Sensor States 123

5 Review Monitoring Data 126
6 Compare Sensors 132
7 Historic Data Reports 135
8 Similar Sensors 139
9 Object Settings 143
10 Alarms 145
11 Logs 148
12 Tickets 150
13 Working with Table Lists 157
14 Object Selector 160
15 Priority and Favorites 161
16 Pause 164
17 Context Menus 165
18 Hover Popup 178
19 Main Menu Structure 179
Part 6 Ajax Web InterfaceDevice and Sensor Setup 196

1 Auto-Discovery 198
2 Create Objects Manually 212
Add a Group 213
Add a Device 219
Add a Sensor 228
3 Manage Device Tree 230
4 Root Group Settings 232
5 Probe Settings 248
6 Group Settings 266
7 Device Settings 288
8 Sensor Settings 310
List of Available Sensor Types 311
Active Directory Replication Errors Sensor 330
ADO SQL Sensor 340
Amazon CloudWatch Sensor 350
AVM FRITZ!Box WAN Interface v2 Sensor 361
Cisco IP SLA Sensor 370
Citrix XenServer Host Sensor 379
Citrix XenServer Virtual Machine Sensor 390
Cloud HTTP Sensor 399
Cloud Ping Sensor 408
ClusterState Sensor 415
Core Health Sensor 420
Dell PowerVault MDi Logical Disk Sensor 427
Dell PowerVault MDi Physical Disk Sensor 436
DHCP Sensor 446
DNS Sensor 455
Enterprise Virtual Array Sensor 463
Event Log (Windows API) Sensor 473
Exchange Backup (Powershell) Sensor 483
4
Contents
Exchange Database (Powershell) Sensor 493

Exchange Mail Queue (Powershell) Sensor 503
Exchange Mailbox (Powershell) Sensor 513
Exchange Public Folder (Powershell) Sensor 523
EXE/Script Sensor 533
EXE/Script Advanced Sensor 545
File Sensor 555
File Content Sensor 564
Folder Sensor 573
FTP Sensor 582
FTP Server File Count Sensor 590
Google Analytics Sensor 600
HTTP Sensor 610
HTTP Advanced Sensor 619
HTTP Apache ModStatus PerfStats Sensor 634
HTTP Apache ModStatus Totals Sensor 644
HTTP Content Sensor 653
HTTP Full Web Page Sensor 664
HTTP Push Count Sensor 675
HTTP Push Data Sensor 683
HTTP Push Data Advanced Sensor 693
HTTP SSL Certificate Expiry Sensor 703
HTTP Transaction Sensor 713
HTTP XML/REST Value Sensor 726
Hyper-V Cluster Shared Volume Disk Free Sensor 740
Hyper-V Host Server Sensor 750
Hyper-V Virtual Machine Sensor 758
Hyper-V Virtual Network Adapter Sensor 769
Hyper-V Virtual Storage Device Sensor 780
IMAP Sensor 789
INI File Content Check Sensor 803
IP on DNS Blacklist Sensor 811
IPFIX Sensor 820
IPFIX (Custom) Sensor 831
IPMI System Health Sensor 841
jFlow V5 Sensor 851
jFlow V5 (Custom) Sensor 863
LDAP Sensor 873
Microsoft SQL Sensor 880
Microsoft SQL v2 Sensor 889
MongoDB System Health Sensor 902
MySQL Sensor 910
MySQL v2 Sensor 919
NetFlow V5 Sensor 931
NetFlow V5 (Custom) Sensor 943
Oracle SQL Sensor 976
Oracle SQL v2 Sensor 986
Packet Sniffer Sensor 999
Packet Sniffer (Custom) Sensor 1010
5
Contents
Passive Application Performance Sensor 1020

PerfCounter Custom Sensor 1028
PerfCounter IIS Application Pool Sensor 1037
Ping Sensor 1047
Ping Jitter Sensor 1056
Pingdom Sensor 1064
POP3 Sensor 1072
POP3 Email Count Sensor 1081
Port Sensor 1090
Port Range Sensor 1099
PostgreSQL Sensor 1107
Probe Health Sensor 1120
QoS (Quality of Service) One Way Sensor 1127
QoS (Quality of Service) Round Trip Sensor 1135
RADIUS Sensor 1145
RADIUS v2 Sensor 1152
RDP (Remote Desktop) Sensor 1161
SCVMM Host Sensor 1169
SCVMM Virtual Machine Sensor 1180
Sensor Factory Sensor 1190
sFlow Sensor 1208
sFlow (Custom) Sensor 1220
SFTP Secure File Transfer Protocol Sensor 1231
Share Disk Free Sensor 1240
SIP Options Ping Sensor 1248
SMTP Sensor 1257
SMTP&IMAP Round Trip Sensor 1266
SMTP&POP3 Round Trip Sensor 1278
SNMP APC Hardware Sensor 1290
SNMP Cisco ADSL Sensor 1299
SNMP Cisco ASA VPN Connections Sensor 1307
SNMP Cisco ASA VPN Traffic Sensor 1317
SNMP Cisco ASA VPN Users Sensor 1327
SNMP Cisco CBQoS Sensor 1337
SNMP Cisco System Health Sensor 1346
SNMP Cisco UCS Blade Sensor 1355
SNMP Cisco UCS Chassis Sensor 1356
SNMP Cisco UCS Physical Disk Sensor 1365
SNMP Cisco UCS System Health Sensor 1373
SNMP CPU Load Sensor 1382
SNMP Custom Lookup Sensor 1390
SNMP Custom Sensor 1391
SNMP Custom String Sensor 1400
SNMP Dell Hardware Sensor 1411
SNMP Dell PowerEdge Physical Disk Sensor 1420
SNMP Dell PowerEdge System Health Sensor 1429
SNMP Disk Free Sensor 1439
SNMP GSA System Health Sensor 1447
SNMP Hardware Status Sensor 1456
SNMP HP LaserJet Hardware Sensor 1464
SNMP HP ProLiant Logical Disk Sensor 1473
6
Contents
SNMP HP ProLiant Memory Controller Sensor 1482

SNMP HP ProLiant Network Interface Sensor 1491
SNMP HP ProLiant Physical Disk Sensor 1500
SNMP HP ProLiant System Health Sensor 1509
SNMP IBM System X Logical Disk Sensor 1519
SNMP IBM System X Physical Disk Sensor 1528
SNMP IBM System X Physical Memory Sensor 1537
SNMP IBM System X System Health Sensor 1546
SNMP interSeptor Pro Environment Sensor 1555
SNMP LenovoEMC Physical Disk Sensor 1563
SNMP LenovoEMC System Health Sensor 1571
SNMP Library Sensor 1579
SNMP Linux Disk Free Sensor 1590
SNMP Linux Load Average Sensor 1602
SNMP Linux Meminfo Sensor 1610
SNMP Linux Physical Disk Sensor 1618
SNMP Memory Sensor 1626
SNMP NetApp Disk Free Sensor 1634
SNMP NetApp Enclosure Sensor 1643
SNMP NetApp I/O Sensor 1653
SNMP NetApp License Sensor 1662
SNMP NetApp Logical Unit Sensor 1670
SNMP NetApp Network Interface Sensor 1679
SNMP NetApp System Health Sensor 1687
SNMP Poseidon Environment Sensor 1696
SNMP Printer Sensor 1704
SNMP QNAP Logical Disk Sensor 1712
SNMP QNAP Physical Disk Sensor 1720
SNMP QNAP System Health Sensor 1729
SNMP RMON Sensor 1737
SNMP SonicWALL System Health Sensor 1747
SNMP SonicWALL VPN Traffic Sensor 1755
SNMP Synology Logical Disk Sensor 1764
SNMP Synology Physical Disk Sensor 1772
SNMP Synology System Health Sensor 1780
SNMP System Uptime Sensor 1789
SNMP Traffic Sensor 1797
SNMP Trap Receiver Sensor 1808
SNMP Windows Service Sensor 1820
SNTP Sensor 1828
SSH Disk Free Sensor 1835
SSH INodes Free Sensor 1847
SSH Load Average Sensor 1856
SSH Meminfo Sensor 1865
SSH Remote Ping Sensor 1874
SSH SAN Enclosure Sensor 1883
SSH SAN Logical Disk Sensor 1893
SSH SAN Physical Disk Sensor 1902
SSH SAN System Health Sensor 1912
SSH Script Sensor 1922
SSH Script Advanced Sensor 1933
7
Contents
SSH VMWare ESX(i) Disk Sensor 1943

SSL Security Check Sensor 1955
Syslog Receiver Sensor 1963
System Health Sensor 1975
TFTP Sensor 1981
Traceroute Hop Count Sensor 1989
Virtuozzo Container Disk Sensor 1997
Virtuozzo Container Network Sensor 2005
VMware Host Hardware (WBEM) Sensor 2012
VMware Host Hardware Status (SOAP) Sensor 2020
VMware Host Performance (SOAP) Sensor 2029
VMware Virtual Machine (SOAP) Sensor 2039
WBEM Custom Sensor 2049
Windows CPU Load Sensor 2058
Windows IIS 6.0 SMTP Received Sensor 2067
Windows IIS 6.0 SMTP Sent Sensor 2076
Windows IIS Application Sensor 2085
Windows Last Update (Remote Registry) Sensor 2095
Windows Logged In Users Sensor 2104
Windows MSMQ Queue Length Sensor 2112
Windows Network Card Sensor 2122
Windows Pagefile Sensor 2132
Windows Physical Disk Sensor 2141
Windows Print Queue Sensor 2151
Windows Process Sensor 2161
Windows Registry Sensor 2171
Windows Scheduled Task Sensor 2181
Windows System Uptime Sensor 2191
Windows Updates Status (Powershell) Sensor 2200
WMI Custom Sensor 2209
WMI Custom String Sensor 2219
WMI Event Log Sensor 2230
WMI Exchange Server Sensor 2241
WMI Exchange Transport Queue Sensor 2251
WMI File Sensor 2261
WMI Free Disk Space (Multi Disk) Sensor 2269
WMI HDD Health Sensor 2280
WMI Logical Disk Sensor 2291
WMI Memory Sensor 2300
WMI Microsoft SQL Server 2005 Sensor (Deprecated) 2308
WMI Microsoft SQL Server 2008 Sensor 2320
WMI Remote Ping Sensor 2356
WMI Security Center Sensor 2364
WMI Service Sensor 2373
WMI Share Sensor 2383
WMI SharePoint Process Sensor 2393
WMI Terminal Services (Windows 2008) Sensor 2402
WMI Terminal Services (Windows XP/Vista/2003) Sensor 2410
WMI UTC Time Sensor 2418
8
Contents
WMI Vital System Data (V2) Sensor 2426

WMI Volume Sensor 2436
WMI Volume Fragmentation Sensor 2445
WMI Windows Version Sensor 2455
WSUS Statistics Sensor 2464
9 Additional Sensor Types (Custom Sensors) 2474
10 Sensor Channels Settings 2477
11 Sensor Notifications Settings 2484
Part 7 Ajax Web InterfaceAdvanced Procedures 2496

1 Toplists 2498
2 Arrange Objects 2503
3 Clone Object 2504
4 Multi-Edit 2506
5 Create Device Template 2511
6 Show Dependencies 2514
7 Geo Maps 2516
8 Notifications 2521
Setting Up Notifications Based on Sensor Limits: Example 2524
9 Libraries 2533
Libraries Step By Step 2536
Management 2540
Libraries and Node Settings 2542
Context Menus 2548
10 Reports 2549
Reports Step By Step 2553
View and Run Reports 2556
Reports Settings 2559
11 Maps 2569
Maps Step By Step 2572
Maps Designer 2575
Maps Settings 2581
12 Setup 2585
Account SettingsMy Account 2587
Account SettingsNotifications 2593
Account SettingsNotification Contacts 2608
Account SettingsSchedules 2612
System AdministrationUser Interface 2616
System AdministrationMonitoring 2626
System AdministrationNotification Delivery 2631
System AdministrationCore & Probes 2638
System AdministrationUser Accounts 2644
System AdministrationUser Groups 2649
System AdministrationAdministrative Tools 2653
System AdministrationCluster 2658
PRTG StatusSystem Status 2660
PRTG StatusAuto-Update 2670
PRTG StatusCluster Status 2675
PRTG StatusLicensing Status and Settings 2677
9
Contents
Optional Downloads and Add-Ons 2680

Desktop Notifications 2682
SupportContact Support 2684
Part 8 Enterprise Console 2688

1 First Start 2691
2 General Layout 2692
3 Menu Tabs and Page Content 2695
Devices 2696
Libraries 2703
Sensors 2705
Alarms 2707
Maps 2709
Reports 2711
Logs 2713
Tickets 2715
Setup 2717
Search Results 2719
4 PRTG Servers 2720
5 Options 2723
6 Windows Menu Structure 2729
7 Context Menus 2736
8 Shortcuts Overview 2737
Part 9 Other User Interfaces 2740

1 Mobile Web GUI 2741
2 Smartphone Apps 2744
Part 10 Sensor Technologies 2748

1 Monitoring via SNMP 2749
2 Monitoring via WMI 2753
3 Monitoring via SSH 2756
4 Monitoring Bandwidth via Packet Sniffing 2758
5 Monitoring Bandwidth via Flows 2760
6 Bandwidth Monitoring Comparison 2763
7 Monitoring Quality of Service and VoIP 2765
8 Monitoring Email Round Trip 2770
9 Monitoring Backups 2772
10 Monitoring Virtual Environments 2773
11 Monitoring Databases 2782
12 Monitoring Syslogs and SNMP Traps 2784
Part 11 PRTG Administration Tool 2794

1 PRTG Administration Tool on Core Server System 2795
2 PRTG Administration Tool on Remote Probe Systems 2818
Part 12 Advanced Topics 2826
10
Contents
1 Active Directory Integration 2827

2 Application Programming Interface (API) Definition 2830
3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors 2831
4 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors 2835
5 Define IP Ranges 2837
6 Define Lookups 2838
7 Regular Expressions 2846
8 Add Remote Probe 2847
Remote Probes and Multiple Probes 2848
Remote Probe Quick Setup 2851
Remote Probe Setup Using Installer 2856
9 Failover Cluster Configuration 2861
Failover Cluster Step by Step 2864
10 Data Storage 2871
11 Using Your Own SSL Certificate with PRTG's Web Server 2873
12 Calculating Percentiles 2875
Part 13 Appendix 2878

1 Glossary 2879
2 List of Abbreviations 2883
3 Support and Troubleshooting 2886
4 Legal Notices 2887
Index 0
11
Part 1
Welcome to PRTG Network Monitor
02.02.2015 13
Part 1: Welcome to PRTG Network Monitor |
1 Welcome to PRTG Network Monitor

Welcome to PRTG Network Monitor! You have chosen an easy-to-use software product that
comes with a powerful set of features to monitor your entire network.
Why Network Monitoring is Important

Today, most businesses rely on a computer and network infrastructure for internet, internal
management, telephone, and email. A complex set of servers and network equipment is
required to ensure that business data flows seamlessly between employees, offices, and
customers. The economical success of an organization is tightly connected with the flow of
data.
The computer network's reliability, speed, and efficiency are crucial for businesses to be
successful. But, like all other technical objects, network devices may fail from time to time
potentially causing trouble and loss of sales, no matter what migration efforts have been made
up-front.
Network administrators need to take three key steps to maintain network uptime, reliability,
and speed:
1. Set up a well-planned network with reliable components.

2. Create recovery plans for the event of device failure.
3. Monitor their network to know about failures as they build up or actually happen.
PRTG Network Monitor, the software described in this document, is a complete solution for
monitoring small, medium, and large networks.
Monitoring Networks with PRTG Network Monitor

PRTG Network Monitor is a powerful network monitoring application for Windows-based
systems. It is suitable for small, medium, and large networks and capable of LAN, WAN, WLAN,
and VPN monitoring. You can also monitor physical or virtual web, mail, and file servers, Linux
systems, Windows clients, routers, and many more. PRTG monitors network availability and
bandwidth usage, as well as various other network parameters such as quality of service,
memory load, and CPU usages. It provides system administrators with live readings and
periodical usage trends to optimize the efficiency, layout, and setup of leased lines, routers,
firewalls, servers, and other network components.
The software is easy to set up and use and monitors a network using Simple Network
Management Protocol (SNMP), Windows Management Instrumentation (WMI), packet sniffer,
Cisco NetFlow (as well as IPFIX, sFlow, and jFlow), and many other industry standard protocols.
It runs on a Windows-based machine in your network for 24-hours every day. PRTG Network
Monitor constantly records the network usage parameters and the availability of network
systems. The recorded data is stored in an internal database for later analysis.
14 02.02.2015
Part 1: Welcome to PRTG Network Monitor | 1 About this Document
1.1 About this Document

This document introduces you to the system concepts of PRTG Net work Monit or and
explains how to set up the software to achieve the best monitoring results. You will learn how
to plan your monitoring setup, how to set up your devices and sensors, dependencies,
reports, notifications, maps, user accounts, and clustering for fail-safe monitoring.
This document is also meant as a reference for all available settings. Short contextual help is
already provided within the Ajax web interface; in this manual you often get some more help
regarding the different options available.
This document does not explain monitoring protocols and file formats in-depth. Also, the use
of the Application Programming Interface (API) built into PRTG is only briefly addressed.
Whenever possible, hyperlinks to more detailed resources are provided, such as articles in the
Paessler Knowledge Base.
To start using PRTG right away, please see the Quick St art Guide 32 section. For more
detailed instructions, see the other sections.
02.02.2015 15
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
1.2 Key Features

PRTG Network Monitor monitors your network and requires no third party software.
Conducting a quick ad-hoc download, you do not need to fill web forms and will not have any
registration hassles. The installation process requires only a few minutes, as well as the first
configuration which is mainly done automatically. The initial setup is achieved by an interactive
guidance by the software.
What PRTG Can Be Used For

Monitor and alert due to uptimes/downtimes or slow servers.
Monitor system health of various hardware devices.
Monitor and account bandwidth and network device usage.
Monitor applications.
Monitor virtual servers.
Monitor Service Level Agreement (SLA).
Monitor system usage (CPU loads, free memory, free disk space, etc.).
Monitor performance of databases as well as monitor databases directly.
Monitor email servers and use this feature to monitor various backup solutions.
Monitor the environment.
Classify network traffic by source/destination and content.
Discover unusual, suspicious, or malicious activity with devices or users.
Measure Quality of Service (QoS) and Voice over IP (VoIP) parameters and control service
level agreements (SLA).
Discover and assess network devices.
Find unexpected relationships between your network components to detect potential
security issues and to explore the real usage of your network and hardware.
Monitor fail-safe using a failover cluster setup.
What PRTG Includes

The PRTG installer contains all modules and software necessary to run the monitoring system
without the need for third party modules, including:
High performance: PRTG's own fast and efficient database system stores the raw monitoring
results, as well as logs, toplists, and tickets (outperforms SQL servers for monitoring data),
accessible through the Application Programming Interface (API). You can distribute high loads
over multiple probes.
Low system requirements: An average PC from the year 2007 is sufficient and even a
netbook can monitor over thousand sensors.
High security standards: SSL encryption for connections and web server, and multiple user
accounts with shared and private sensors, as well as rights management, and many more.
16 02.02.2015
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
Built-in SSL secured web server with HTTP and HTTPS support for the user interface.
Fast web interface, works as Single Page Application (SPA) to avoid time-extensive reloading
of the page.
Mail server for automatic email delivery.
Flexible alerting
including nine notification technologies, for example, email, SMS, syslog and SNMP trap,
HTTP request, event log, Amazon SNS, executing scripts, etc.
including various triggers, for example, status alerts, limit alerts, threshold alerts, multiple
condition alerts, escalation alerts.
including dependencies to avoid alarms floods, acknowledging alarms to avoid further
notifications for this alarm, and alert scheduling.
In-depth report generator to create reports on-the-fly as well as scheduled reports in HTML
or Portable Document Format (PDF). Many report templates are available by default.
Graphics engine for user-friendly live and historic data charts.
Network analysis module to automatically discover network devices and sensors.
Distributed monitoring to monitor several networks in different locations.
Special features for Managed Service Provider (MSP) to monitor customer networks and
increase the quality of service.
Data publishing with real time dashboardsprivate and publicincluding live performance
and status information. You can design these maps as you like with many different objects,
as well as you can integrate external custom objects.
Different languages like English, German, Spanish, French, Portuguese, Dutch, Czech,
Japanese, and Simplified Chinese.
Customizations: The PRTG Application Programming Interface (API) allows you to program
your own features and to customize and re-brand PRTG's web interface to your needs. In
addition, you can create custom sensors, notifications, and device templates.
PRTG Network Monitor supports monitoring up to 20,000 thousand sensors per installation. It
can optionally work with multiple remote probes to monitor multiple sites or network
segments from one central core installation, and to distribute high loads. You can also
configure fail-safe monitoring using a cluster installation to perform automatic failovers. Single
failover installations are allowed with every PRTG license.
The software is based on Paessler's reliable monitoring technology, which has been constantly
improved since 1997 and is already used by more than 150,000 users around the world every
day. An outstanding support ensures that your inquiries are answered within one business day
to ensure best possible network monitoring. Attractive licensing packages from freeware (up
to 30 sensors) to enterprise level (with thousands of sensors) make sure that every user finds
the proper solution.
02.02.2015 17
Part 1: Welcome to PRTG Network Monitor | 3 New in This Version
1.3 New in This Version

With ongoing continuous development and rollout, we constantly extend and improve on the
functionalities provided by PRTG. Instead of delivering just a few versions distributed over the
year with massive changes in every version, PRTG is automatically and seamlessly enhanced
with new features and fixesfast and with high quality. There are three release channels for
PRTG:
St able: best tested version of PRTG for live systems; updated about once or twice a month;
for usage on live systems
Preview: offering the latest features and fixes; updated about once a week; consider this
version as "beta", thus, do not use this version on live systems you have to depend on!
Canary : providing "nightly builds"; updated very often; not tested extensively; never use on
live systems you have to depend on!
Because of these three channels, you can choose either maximum stability, earlier access to
new features, or a mixture of both.
For an overview of all most recent changes in the current version, please visit the version
history on our website. Please see the More 18 section below for more information.
More
Paessler Website: PRTG Network Monitor Version History
http://www.paessler.com/prtg/history
Paessler Blog: Version 12 of PRTG introduces "Continuous Rollout"

http://www.paessler.com/blog/2012/04/25/
18 02.02.2015
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
1.4 Available Licenses

There are four different PRTG flavors available.
Freeware Edition
The Freeware Edition is a good solution to get started with PRTG or for private use:
Is for free for personal and commercial use.

Can monitor up to 30 sensors.
Supports all available sensor types.
Shortest available monitoring interval is one minute.
Note: If you want to use the Freeware Edition, please first install the Trial Edit ion 19 and get a
free trial key. After the trial period has ended, your Trial Edition will automatically revert into a
Freeware Edition.
Special Edition
The Special Edition has all the features of the Freeware Edition, plus it supports up to 50
sensors. You can extend your Freeware Edition by entering the key for a Special Edition. This
key is not for download and is only used for special marketing campaigns.
Trial Edition
The Trial Edition is intended for evaluation purposes for customers who are interested in
purchasing commercial licenses:
Can monitor an unlimited number of sensors.

Shortest available monitoring interval is one second (not officially supported; a minimum
interval of 10 seconds is recommended).
Temporary license key must be requested from Paessler's website.
Trial period limited to 30 days (automatically reverts to Freeware Edition 19 afterwards).
With each license one single failover cluster setup 81 , consisting of two nodes, is included.
Cluster installations with two and three failover nodes will require one additional trial license
key; a cluster installation with four failover nodes will require two additional trial license
keys.
After the trial period has ended, a Trial Edition will revert into a Freeware Edition, allowing you
to monitor up to 30 sensors for free.
Commercial Editions
There are several licenses of PRTG Network Monitor available to suit the demands of smaller as
well as larger customers and organizations:
02.02.2015 19
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
Can monitor maximum number of sensors (from 100 to unlimited).

Shortest available monitoring interval is one second (not officially supported; a minimum
interval of 10 seconds is recommended).
With each license one single failover cluster setup 81 , consisting of two nodes, is included.
Cluster installations with two and three failover nodes will require one additional license of
the same size; a cluster installation with four failover nodes will require two additional
licenses of the same size.
For more information about available commercial licenses, please see More 20 section below.
More
Knowledge Base: What is the PRTG Special Edition license?
http://kb.paessler.com/en/topic/8063
Paessler Website: Request a Free PRTG Trial Key for Evaluation

http://www.paessler.com/prtg/trial
Paessler FAQs: What is the difference between the PRTG Network Monitor licenses?
http://www.paessler.com/support/faqs#e1912
20 02.02.2015
Part 1: Welcome to PRTG Network Monitor | 5 System Requirements
1.5 System Requirements

To install and work with PRTG Network Monitor, you need to meet the following requirements:
A current PC or server with average desktop performance and minimum 2048 MB RAM
memory.
Operating systems Microsoft Windows Server 2012 R2 (recommended), Windows Server
2012, Windows 8.1, Windows 8, Windows 7, and Windows 2008 R2 (all 32-bit or 64-bit) are
officially supported. You can also use Windows Vista or Windows 2008, but we recommend
not using these systems, because there are known performance issues related to them.
Web browser to access the web interface. The following browsers are supported:
Google Chrome 40 or later (recommended)
Mozilla Firefox 35 or later
Microsoft Internet Explorer 10 or 11
Planning an Installation With Hundreds of Sensors or More?

The maximum number of sensors you can monitor with one installation of PRTG mainly
depends on the monitoring technology and the monitoring intervals you use. Please see
section Det ailed Sy st em Requirement s 23 .
In general, consider the following rules:
SNMP V1 and V2, Ping, Port , and HTTP

These sensor types are recommended for scenarios with thousands of sensors.
SNMP V3
You will be able to monitor about 5,000 SNMP V3 sensors with an interval of 60 seconds on
a common two core computer, and about 10,000 sensors on a four core system (the main
limiting factor is your CPU power).
WMI
Try to keep the number of WMI sensors per probe below 120 sensors (with 60s interval), or
600 sensors (with 300s interval).
xFlow (IPFIX , Net Flow, sFlow, jFlow)
Monitoring the maximum number of sensors depends on the traffic pattern, the number of
xFlow packets per second received by the PRTG probe, as well as the performance of the
probe system.
Packet Sniffer
These sensors create the highest CPU load on the probe system. This technology is only
recommended for monitoring of low traffic connections (<50 Mbit/s steady stream). When
traffic is often over 10 Mbit/s a dedicated remote probe 2847 should be used.
VMware Monit oring
Monitoring of VMware is limited to about 20 sensors at a 60 seconds monitoring interval, or
100 sensors at a 5 minutes interval. These limitations issue from the VMware platform. A
registry hack is available to boost this to 150 sensors at a 5 minutes interval (this will require
a change in the ESX/vCenter configuration). For details please see More 22 section below.
11.02.2015 21
Ot her sensor t y pes

The impact of a specific sensor type on performance is indicated by a color range when
adding a sensor to a device. It ranges from dark green (very low impact) to bold red (very
high impact).
To overcome any limitations mentioned above you should distribute the sensors over two
remote probes 2847 or more.
We recommend using a dedicated physical machine to run both the PRTG core server and PRTG
remote probes. For more information please see the Det ailed Sy st em Requirement s 23
section.
More
Updat e From Previous Versions 47
Knowledge Base: Planning Large Installations of PRTG Network Monitor

Knowledge Base: How can I speed up PRTGespecially for large installations?

Knowledge Base: Increasing Maximum Connections for VMware Sensors

Knowledge Base: Checklist for Running PRTG on VMware

Knowledge Base: Which ports does PRTG use on my system?

Knowledge Base: Which .NET version does PRTG require?

22 11.02.2015
1 Detailed System Requirements
1.5.1 Detailed Sy stem Requirements
This section shows different aspects of system requirements for PRTG. Please consider these
requirements to avoid issues while network monitoring.
Support ed Operat ing Sy st ems 23
Hardware Requirement s 24
Net work Size: Recommendat ions 25
Running PRTG on Virt ual Machines 26
Running PRTG in a Failover Clust er 26
Web Browser Requirement s 27
Screen Resolut ion 27
Requirement s for Monit ored Devices 27
Requirement s for t he Ent erprise Console 27
Requirement s for Mobile Web GUI 28
Requirement s for Smart phones 28
More 28
Supported Operating Systems

The 32-bit and 64-bit versions of the following operating systems are officially supported for
PRTG Core Service and Probe Service:
Microsoft Windows Server 2012 R2** (recommended)

Microsoft Windows Server 2012**
Microsoft Windows 8.1
Microsoft Windows 8
Microsoft Windows 7
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008 (not recommended)
Microsoft Windows Vista (not recommended)
* Windows Server 2012 in Core mode and the Minimal Server Interface are not officially
supported.
The version (32-bit or 64-bit) of the PRTG Core Server depends on the version of your
operating system. The 64-bit version of the PRTG Core Server will be installed if
the operating system is a 64-bit Windows system, and

the system provides 6 GB RAM or more.
Otherwise the 32-bit version of the PRTG Core Server will be installed.
11.02.2015 23
We recommend you to provide Microsoft .NET Framework versions 3.5 and 4.0 (with latest
updates) on all systems running a PRTG probe. Note: Version 4.0 is imperatively needed for
monitoring VMware and XenServer virtual environments.
More details: Some sensor types need the Microsoft .NET Framework to be installed on the
computer running the PRTG probe. This is either on the local system (on every node, if on a
cluster probe), or on the system running a remote probe 2848 . Depending on the sensor type,
the required versions are 2.0, 3.0, 4.0, or 4.5. See section More 28 for details. Note: According
to the Microsoft website, .NET version 3.5 contains versions 2.0 SP1 and 3.0 SP1. Version 4.0
is not downward compatible, but must be installed side-by-side to older version(s), if required.
For best performance of VMware sensors, EXE/Script sensors, and some other sensor types,
we recommend Windows 2012 R2 on the computer running the PRTG probe: This is either on
the local system (on every node, if on a cluster probe), or on the system running a remote
probe 2848 .
For best performance of hybrid sensors using Windows Performance Counters and Windows
Management Instrumentation (WMI), we recommend Windows 2008 R2 or higher on the
computer running the PRTG probe: This is either on the local system (on every node, if on a
cluster probe), or on the system running a remote probe 2848 .
Hardware Requirements
Hardware requirements for PRTG Core Service and Probe Service mainly depend on the
sensor types and intervals used. The following values are provided as reference for common
usage scenarios of PRTG (based on a default sensor interval of 60 seconds).
CPU
A current PC or server can easily monitor up to 2,000 sensors (see sensor type specific
notes below). PRTG supports native x86/x64 architectures.
RAM memory
Minimum requirement: 2048 MB RAM. You need about 150 KB of RAM per sensor.
In general, we recommend at least 1 CPU core and 1 GB RAM per 1,000 sensors.
Hard Disk Drive
You need about 200 KB of disk space per sensor per day (for sensors with 60 second
interval).
Int ernet connect ion
An internet connection is required for license activation (via HTTP or email).
St able net work connect ion for remot e probes
Remote probes require a stable network connection between the PRTG core server and the
remote probe. Unstable connections, for example via 3G, might work but it could be possible
that you lose monitoring data if the connection is non-reliable.
There are also non-hardware dependent limitations for some sensor types, for example, WMI
and SNMP V3 sensors. These limitations can be overcome by distributing the sensors across
multiple remote probes 2847 . If you plan installations with more than 500 to 1,000 sensors, or
more than 10 Packet Sniffer or xFlow (NetFlow, sFlow) sensors, please consult the site planner
tool linked in the More 28 section below. For clusters we recommend staying below 5,000
sensors per cluster.
24 11.02.2015
Network Size: Recommendations

Rule of thumb: Typical PRTG installations almost never run into performance issues when
they stay under 2,000 sensors, under 30 remote probes, and under 30 user accounts.
PRTG can scale much higher when the installation is planned well. Please read on if you plan
to go beyond these numbers and/or if you plan elevated use of resource intensive features
like reporting, xFlow sensors, or clustering.
If you plan an installation that monitors more than 5,000 sensors from one instance of PRTG
on a physical device or more than 2,500 sensors with PRTG running on a virtual machine we
ask you to contact our pre-sales team for consultation.
Note: PRTG users usually monitor each device in their network with about 10-20 sensors, so
for 50 servers you need about 500-1,000 sensors.
For your information: To monitor 5,000 sensors in a 1-minute interval, PRTG takes 7.2 million
measurements and evaluates, notifies, and stores themthis adds 700 MB of additional data
to the database every single day.
Apart from the processing power required for the monitoring itself, several aspects can affect
the number of sensors that you can use with PRTG. The following recommendations are for a
PRTG single core setup (without clustering) on a physical machine. You can overcome some of
these limitations if you distribute the sensors across multiple remote probes.
SIZING R ECOMMENDATIONS
Operating System We recommend Windows Server 2012 R2 to run the PRTG core
server and probes. This offers superior performance for
monitoring, especially if you have more than 2,000 sensors.
Sensor Types Ping 1047 and SNMP sensors 313 create much less load than complex
sensors like xFlow sensors 2760 , VMware sensors 317 , Sensor
Factory sensors 1190 , WMI sensors 315 , or Syslog 1963 /Trap receiver 1808
sensors, for example.
Scanning Interval We recommend to mainly use 1-minute scanning intervals 242 for up
to 2,000 sensors and 5-minute intervals if you have more sensors.
Number of Users We recommend staying below 30 active user accounts 2644 for each
PRTG core server. You can work well with more users if these do
not all use the UI at the same time (including public dashboards).
Number of Remote Our general recommendation is to stay below 30 remote probes

Probes 2848 on one PRTG core server. PRTG still scales well up to 60 probes
as long as you have less than 100 sensors per probe.
11.02.2015 25
SIZING R ECOMMENDATIONS
CPU Intensive Features Try keeping the usage of the following features down: Many
quickly refreshed dashboards 2569 , frequent generation of huge
sensor reports 2549 , heavy usage of packet sniffing 2758 , factory
sensors 1190 , and toplists 2498 , frequent automatically scheduled auto-
discoveries 198 for large network segments, constant queries of
monitoring data via the API 2830 , among others.
Network Connection The quality of your network also plays an important role. When
Quality monitoring via UDP, for example, a high packet loss rate can lead to
frequent timeouts. Remote probes that connect via unstable (WAN)
connections can lead to delays as well.
Running PRTG on Virtual Machines

You can run the PRTG core server as well as PRTG remote probes on virtualized platforms.
However, we strongly recommend using a dedicated physical machine to run the PRTG core
server respectively PRTG remote probes 2848 . There are several reasons why we recommend
running PRTG (core server and remote probes) on real hardware, especially for thousands of
sensors. Each sensor request will have to go through many virtualization layers, which costs
performance and makes measurements less exact. In our experience, a physical machine
simply works best for a thousand sensors and more.
Our recommendation to use real hardware is valid for the PRTG core server and for remote
probes. If you must run PRTG on a virtual machine, please stay below 2,500 sensors per virtual
machine and consider running several PRTG core server instances instead.
Important note: We cannot offer technical support regarding performance and stability
problems for PRTG installations on virtual machines that run with more than 5,000 sensors. In
this case, please migrate PRTG to one or more, preferably physical, machines.
Note: When running PRTG on a virtual machine, do not use dynamic resource allocation, but
please make sure that full resources are available to the virtual machine at any time. In our
experience, dynamic resource allocation is not working efficiently for a monitoring software
and can therefore lead to massive performance issues.
Please see also section More 28 regarding running PRTG on VMware.
Running PRTG in a Failover Cluster

We recommend a single failover setup 81 if you need fail-safe monitoring. This consists of two
PRTG core servers, each working as a cluster node.
In a PRTG failover cluster, the monitoring load doubles with each cluster node, so you will
encounter half performance for each additional cluster node. In a single failover cluster, please
divide our recommended numbers from above in half.
26 11.02.2015
Web Browser Requirements

The following browsers are officially supported by the PRTG web interface (in order of
performance and reliability):
Google Chrome 40 or later (recommended)

Mozilla Firefox 35 or later
Microsoft Internet Explorer 10 or 11
Note: Deprecated Internet Explorer versions as well as mobile browsers might not be able to
display the full featured Ajax web int erface 102 . Using these browsers, you can access the
feature-limited Mobile Web GUI 2741 , which does not require CSS or Javascript capability.
Screen Resolution
A screen resolution of at least 1024x768 pixels is sufficient for most functions of PRTG.
However, we recommend a screen resolution of 1200x800 or higher.
Requirements for Monitored Devices

SNMP monit oring
The monitored device(s) must be equipped with SNMP Version 1, 2c, or 3 (i.e., an SNMP-
compatible software must be installed on the device). SNMP must be enabled on the device
and the machine running PRTG must be granted access to the SNMP interface.
Windows/WMI monit oring
To use Windows Management Instrumentation (WMI) monitoring, you need a Windows
network. For client PCs monitored with WMI, only the operating systems as given above 23
are officially supported. Please do not use Windows Vista or Windows 2008 R1 for WMI
monitoring (they both have WMI performance issues).
xFlow (IPFIX , Net Flow, sFlow) monit oring
The device must be configured to send NetFlow data packets (NetFlow version 5 or 9; IPFIX
is the successor protocol of NetFlow 9) or sFlow packets (version 5) to the machine running
the PRTG probe.
Packet Sniffer monit oring
Only data packets passing the local machine's network card can be analyzed. Switches with
so-called 'monitoring ports' are necessary for network-wide monitoring in switched
networks.
Ot her sensor t y pes
Depending on the specific sensor type, you can find requirements (for example, modules,
components, device configurations) which may have to be fulfilled in the corresponding
manual section, as well as partly when adding the sensor to a device.
Requirements for the Enterprise Console

The optional PRTG Ent erprise Console 2688 runs under all supported Windows versions 23 . It
has a built-in webkit browser engine and requires no specific browser installed on the system.
See also section Ent erprise ConsoleRequirement s for Connect ions t o PRTG Web Server
(s) 2688 .
11.02.2015 27
Requirements for Mobile Web GUI

The feature-limited mobile web interface is optimized for low bandwidth and mobile access. It
has been designed for and tested with iOS (iPhone, iPad), Android, Blackberry, Windows Mobile,
and also deprecated Internet Explorer versions.
Requirements for Smartphones

The optional smartphone apps for iOS devices require iOS version 6 or later and PRTG v12 or
later. For Android devices, the app "PRTG for Android" requires Android OS 4.0 or later (version
4.1 or later recommended), as well as PRTG Network Monitor 13.1 or later. For more
information, please see Smart phone Apps 2744 . The 'Mobile Web GUI 2741 ' interface can be used
on most phones with a browser. We successfully tested it on Symbian, BlackBerry, Windows,
Android, and iOS devices.
More
Knowledge Base: How can I speed up PRTGespecially for large installations?

Knowledge Base: My WMI sensors don't work. What can I do?

Knowledge Base: Frequent Questions about xFlow, Packet Sniffing, Traffic Monitoring and
Cisco
Knowledge Base: My SNMP sensors don't work. What can I do?

Knowledge Base: Checklist for Running PRTG on VMware

Knowledge Base: Which ports does PRTG use on my system?


Knowledge Base: Why can't I save my PRTG password in Google Chrome?
28 11.02.2015
11.02.2015 29
Part 2
Quick Start Guide
02.02.2015 31
Part 2: Quick Start Guide |
2 Quick Start Guide

Welcome to PRTG Network Monitor! This section will support you with a quick start into PRTG,
so you can start monitoring your network right away!
Welc ome Sc reen
Setting up monitoring for your network is easy! You only need to download the installer from
Paessler's website, run through the installation wizard, and provide some information in the
configuration guru. PRTG will start monitoring your network immediately without any further
complicated stumbling blocks! Of course, later on, you still can adjust everything to your
needs.
Please see the following quick steps.
Quick Start GuideTopics

ONEDownload, Inst allat ion, and First Login 33
TWOUsing t he Configurat ion Guru 36
32 02.02.2015
Part 2: Quick Start Guide | 1 ONEDownload, Installation, and First Login
2.1 ONEDownload, Installation, and First Login

Simply download and install the version of PRTG Network Monitor which meets your needs.
For video tutorials with PRTG basics, please see section More 35 below.
Download
On the Paessler website, you find two different installers for PRTG, a public download for the
Freeware, Special, and Trial editions, and a login link to download the commercial editions
(which is only available for paying customers).
PRTG Download on Paessler Website with Marked Full Version Download Link
02.02.2015 33
Downloading the Freeware or Trial Edition

Please download the latest publicly available file from the Paessler website. You can also
request a trial key there, which must be entered during installation:
ht t p://www.paessler.com/prt g/download
Note: Every Freeware installation will start as a Trial version, giving you an unlimited number of
sensors for 30 days. After the trial period has expired, your installation will automatically revert
to a Freeware edition with 30 sensors.
Downloading the Commercial Edition

Downloads and updates are free to customers with an active maintenance contract. Please log
into the Paessler website to get the latest download. You can also find your license key there,
which must be entered during installation:
ht t p://www.paessler.com/login
If you do not have an active maintenance contract, please contact sales@paessler.com.
Note: Once installed, you will usually use the Soft ware Aut o-Updat e 2670 function of PRTG to
download and install new versions. This will further ease the process of installing updates.
Installation
Please double click the setup file on the computer that will be your PRTG server. Follow the
installation wizard and install the software.
At the end of the installation, a browser window will be opened automatically, and it will
connect to the PRTG web interface, showing the Configurat ion Guru. Please make sure you
load the web interface with one of the supported browsers:
Google Chrome 40 or later (recommended),

Mozilla Firefox 35 or later, or
Microsoft Internet Explorer 10 or 11.
Note: Due to scripting incompatibilities, you might not be able to use all functionalities of the
PRTG Ajax web interface with Internet Explorer 9 or earlier and other older browsers. If you
cannot access the Configurat ion Guru, please open the URL of the PRTG web interface in
another browser.
Login
If everything works fine, you will not see the login screen on first startup. Only when switching
browsers you will have to log in.
34 02.02.2015
PRTG Login Sc reen
Leave the Login Name and Password fields empty.

Choose the AJAX Web GUI (All feat ures, opt imized for deskt op access) option.
Click on the Default Login button to login.
Please make sure you use a supported web browser when logging in to PRTG. Please use
Google Chrome 40 or later (recommended), Mozilla Firefox 35 or later, or Microsoft Internet
Explorer 10 or 11. Only with a supported browser you can use the AJAX Web GUI (All
feat ures, opt imized for deskt op access) option. If you see this option grayed out, please
change your browser and open the URL again.
Please see the next step for more information about Using t he Configurat ion Guru 36 .
More
Video Tutorials for PRTG Network Monitor:
http://www.paessler.com/support/video_tutorials
02.02.2015 35
Part 2: Quick Start Guide | 2 TWOUsing the Configuration Guru
2.2 TWOUsing the Configuration Guru

For a new inst allat ion, PRTG will open t he Configurat ion Guru aut omat ically aft er each
login. It will reappear unt il y ou eit her ran t hrough it complet ely or skipped it . In order
t o open it at any t ime, please click t he Run Configurat ion Guru but t on on PRTG's Home
screen.
Note: When using the Ent erprise Console 2688 , please start the Guru by selecting Help | Run
Configurat ion Guru from the main menu.
Ajax Web Interfac e Home Sc reen
By answering about ten simple questions, this assistant will guide you through an initial setup
and pre-configure an essential monitoring of your network including important devices,
servers, and websites. You can later adjust these automatically generated monitoring settings
later by hand.
36 02.02.2015
Configuration Guru Start Sc reen
The steps to go are:
Enable SSL Encry pt ion 38
Configure Administ rat or Account 38
Ent er Windows/WMI Credent ials 38
Ent er SNMP Credent ials 39
Ent er VMware/X enServer Credent ials 39
Ent er Linux/Solaris/Mac OS Credent ials 40
Monit or Your Int ernet Connect ion 40
Monit or LAN Servers 40
Monit or Websit es/Online Shops 41
Monit or Cloud Services 41
Discover a Net work Segment 41
You Are Done! 42
Click on the St art Guru button to start. You can skip a step at any time by clicking on the Skip
button.
02.02.2015 37
Enable SSL Encryption

This step is shown only if your web server runs on http. We recommend running the PRTG web
interface using SSL encryption (https), especially if you make your web interface available from
the internet. Without encryption your passwords are sent over your network unencrypted.
Choose between:
Yes: Switch the PRTG web server to use SSL. A popup will appear, showing you the screen
shot of a certificate security warning that will be shown the next time you load the PRTG
web interface. Confirm by clicking the button Yes, swit ch t o SSL now. After you confirm,
the PRTG core server Windows service will be restarted and the web interface will be
reloaded, most likely showing a certificate warning. Confirm it to proceed to the login
screen. For more information, please see SSL Cert ificat e Warning 107 .
No: Skip this step and keep using an unencrypted http connection. Once you skipped this
step, it will not be shown again. You can switch to SSL later by using the PRTG Administration
Tool from the Windows start menu. For more information, please see PRTG Administ rat ion
Tool on Core Server Sy st em 2796 .
Click the Save & Next button to apply your settings, or click the Skip button to skip this step.
Both buttons will take you to the next step.
Configure Administrator Account

By default, PRTG uses the administrator account with login name prt gadmin and password
prt gadmin. For security reasons you should at least change the password.
Please enter credentials and email address for the administrator account.
The password must meet the following requirements:
at least eight characters long

at least one number
at least one capital letter
Enter Windows/WMI Credentials

In order to monitor your Windows clients and servers via Windows Management
Instrumentation (WMI), please enter Windows administrator credentials for your network. We
recommend using Domain Administrator credentials (if you're using an Active Directory).
PRTG will store these credentials in the Root 232 group of your device tree. All Windows-based
devices will automatically inherit and use them for monitoring. You can discontinue
Inherit ance of Set t ings 88 at any level, entering other credentials instead.
38 02.02.2015
For a general introduction to the technology behind WMI, please see Monit oring via WMI 2753
section.
Enter SNMP Credentials

In order to monitor your hardware (router, switches, etc.), Simple Network Management
Protocol (SNMP) is the most common protocol used. Usually, all SNMP-enabled devices use the
same settings by default: SNMP version 1, community string public, SNMP port 161).
You only need to change values here if the SNMP-enabled devices in your network use other
settings. Choose between:
No: You SNMP-enabled devices use the default configuration. If you're not sure, choose this
option.
Yes: Choose this option to enter your own SNMP credentials and settings. More settings will
appear. Choose the SNMP version, enter the community string and SNMP port number, and
define a time out for SNMP connections.
PRTG will store these credentials in the Root 232 group of your device tree. All SNMP-based
devices will automatically inherit and use them for monitoring. You can discontinue
For a general introduction to the technology behind SNMP, please see manual section
Monit oring via SNMP 2749 .
Enter VMware/XenServer Credentials

If you use the virtual environments VMware or Citrix XenServer, PRTG can monitor them as
well. To do so, please enter root access credentials for those systems. Choose between:
No: PRTG will not monitor virtual environments. You can later add those credentials.
Yes: Please enter user name and password for VMware or XenServer systems. For VMware,
please also specify the protocol that will be used to connect.
PRTG will store these credentials in the Root 232 group of your device tree. All VMware/
XenServer-based devices will automatically inherit and use them for monitoring. You can
discontinue Inherit ance of Set t ings 88 at any level, entering other credentials instead.
For an overview of all available VMware and XenServer sensors, please see List of Available
Sensor Ty pes 317 , section "Virtual Servers Sensors".
02.02.2015 39
Enter Linux/Solaris/Mac OS Credentials

If you have systems running on Linux, Solaris, or Mac OS X, PRTG can monitor them as well. To
do so, please enter root access credentials for those systems. Choose between:
No: PRTG will not monitor devices via SSH/WBEM. You can later add those credentials.
Yes: Please enter SSH/WBEM credentials. You can either provide username and password, or
paste a private key. For WBEM access, please also define protocol and port. Additionally,
specify the rights an SSH command will be executed with.
PRTG will store these credentials in the Root 232 group of your device tree. All SSH/WBEM-
based devices will automatically inherit and use them for monitoring. You can discontinue
For a general introduction to SSH monitoring, please see Monit oring via SSH 2756 section.
Monitor Your Internet Connection

PRTG can monitor the availability of your default gateway and DNS servers. It will try to
automatically detect and pre-populate the respective fields with the correct IP addresses.
Please review and/or enter the IP addresses of your default (internet) gateway and your DNS
server(s). Enter each IP address/DNS name in one line.
Note: For most networks, the gateway is the IP address or DNS name of your firewall or
router. If you do not have a second DNS server, simply leave the respective field blank.
PRTG will create a new device for each entry and run an auto-discovery to set up sensors. In
the background, auto-discovery will start immediately after you confirm this step.
Monitor LAN Servers

PRTG can monitor your AD domain controllers, Exchange or other mail servers, as well as
additional servers in your network. PRTG will try to automatically detect and pre-populate the
respective fields with the correct IP addresses. Please review and/or enter the entries for your
Active Directory domain controllers and mail servers. Enter each IP address/DNS name in one
line.
PRTG will create a new device for each entry and run an auto-discovery to set up sensors. In
the background, auto-discovery will start immediately after you confirm this step.
40 02.02.2015
Note: Your entries will not be shown in the Configuration Guru after confirming this step but
will be added as devices to your device tree nevertheless. The Configuration Guru option
Monit or LAN Servers will be marked with a green check mark as well if one or more servers
were defined in this section.
Monitor Websites/Online Shops

PRTG can monitor your website and online shop using http. Simply enter the URLs you want to
monitor, each in one line.
PRTG will create a new device for all of your websites, with one sensor for each URL.
Monitor Cloud Services

To see if the cloud services that you usually use are up and running, PRTG can set up http
sensors for those as well. In the list of services, simply switch the radio button to Yes for each
service you want to monitor. Choose from:
Google Search, Google Mail, Google Drive

Microsoft Office 365
Salesforce
Dropbox
iCloud
Facebook
Twit t er
Sky pe
PRTG will create a new device for all of cloud services, with one sensor for each URL.
Discover a Network Segment

PRTG can scan an entire network segment, automatically detect devices, and create sensors
using its auto-discovery.
02.02.2015 41
PRTG will try to automatically detect and pre-populate the respective fields with the correct IP
range. Please review and/or enter the entries. In the IPv4 Base field, enter the first three
octets of your network's IP range, for example 192.168.0 or 10.0.0, or whatever IP address
range you use. If you don't change the default values for IPv4 Range St art and End, PRTG will
automatically complete the IP base and scan all IP addresses ending in .1 to .254.
If you need more options regarding the definition of IP ranges, you can run additional auto-
discoveries later. Please see Aut o-Discovery 198 for more details.
You Are Done!

While you were busy using the guru, PRTG has already created devices and sensors for you.
There are first monitoring values available, too. In the meantime, you can follow PRTG on your
favorite social network by clicking on of the buttons for Facebook, Twitter, or Google +.
Click on the OK! Let me view my new sensors! button to view the device tree.
In order to get familiar with the PRTG web interface, we recommend you proceed with section
General Lay out 110 of the web interface, or with General Lay out 2692 of the Enterprise
Console.
42 02.02.2015
Part 3
Installing the Software
02.02.2015 43
Part 3: Installing the Software |
3 Installing the Software

This section describes how to download and install your PRTG product.
PRTG Setup
Please see the following sections for more information.
Installing the SoftwareTopics

Download PRTG 45
Inst all a PRTG Core Server 51
Inst all a PRTG Clust er 56
Ent er a License Key 57
Act ivat e t he Product 60
Inst all a PRTG Remot e Probe 62
Inst all t he Ent erprise Console 67
Uninst all PRTG Product s 71
44 02.02.2015
Part 3: Installing the Software | 1 Download PRTG
3.1 Download PRTG

On the Paessler website, you find two different installers for PRTG, a public download for the
Freeware, Special, and Trial editions, and a login link to download the commercial editions
(which is only available for paying customers).
PRTG Download on Paessler Website with Marked Full Version Download Link
Downloading the Freeware or Trial Edition

Please download the latest publicly available file from the Paessler website. You can also
request a trial key there, which must be entered during installation:
ht t p://www.paessler.com/prt g/download
02.02.2015 45
Part 3: Installing the Software | 1 Download PRTG
Note: Every Freeware installation will start as a Trial version, giving you an unlimited number of
sensors for 30 days. After the trial period has expired, your installation will automatically revert
to a Freeware edition with 30 sensors.
Downloading the Commercial Edition

Downloads and updates are free to customers with an active maintenance contract. Please log
into the Paessler website to get the latest download. You can also find your license key there,
which must be entered during installation:
ht t p://www.paessler.com/login
If you do not have an active maintenance contract, please contact sales@paessler.com.
Note: Once installed, you will usually use the Soft ware Aut o-Updat e 2670 function of PRTG to
download and install new versions. This will further ease the process of installing updates.
46 02.02.2015
Part 3: Installing the Software | 2 Update From Previous Versions
3.2 Update From Previous Versions

If you already have installed a previous software version, there are several things you should
consider before updating to the current PRTG version. Please see section Det ailed Sy st em
Requirement s 23 to see all requirements for the current PRTG version.
Note: We recommend you always have a proper backup of your monitoring data and
configuration. In most cases both will be maintained when upgrading. Anyway, we recommend
a backup before upgrading. Please see More 49 section below.
Update From PRTG Network Monitor 12 or later

If you have been running PRTG Network Monitor with version 12, 13 or 14, simply install 51 the
latest version on top of the previous version. Your configuration will be kept. If you have
configured PRTG as a cluster, you only have to install an update on any node server (master or
failover). The new version will then be deployed to the cluster automatically. Note: We
recommend you always have a proper backup of your monitoring data.
Note: As of PRTG 14, Int ernet Explorer 9 is no longer officially support ed for access to the
PRTG web interface. Also, PRTG core and probes do not support Windows X P and Windows
Server 2003 (including SP1 and SP2) officially anymore.
Web Interface Customizations as of PRTG Network Monitor 13.2.3

As of PRTG version 13.2.3, the website folder of the PRTG program directory is not used any
more. This means that if you update from an older PRTG version than 13.2.3 to the current
version, all existing customizations of the web interface will be disabled and have to be
revised. You may find a way for a similar customization that can be applied to the files in the
current webroot folder which contains the web interface files now. For details, please see
section More 49 .
Update From PRTG Network Monitor 9

If you are using PRTG 9 now, your configuration will be kept when installing the current PRTG
version in St andalone Mode or when installing a Mast er Node. There are only a few things
you should consider.
Discont inued Sensors: Existing instances of the following sensor types will stop working as
of PRTG V12 and must be replaced with their successor sensor types!
- VMware Host Server (SOAP)

- VMware Virt ual Machine (SOAP)
- X en Virt ual Machine
If your configuration contains these sensor types, they will stop monitoring after upgrading
to the current version. We recommend you to pause them to keep their data. In order to
continue monitoring, please add the sensors anew (for example, using the auto-discovery).
Please inst all .NET 4.0: We strongly recommend installing .NET 4.0 on systems that run the
core server (and the remote probes, if you use those). Otherwise the following features will
not work: VMware 317 auto-discovery and monitoring, Citrix XenServer 379 auto-discovery
and monitoring, SIP Options Ping Sensor 1248 , Windows Last Update Sensor 2095 .
02.02.2015 47
Changed Geo Maps Provider: When you update to the current PRTG version, the provider
for geographical maps will automatically be switched from Google Maps to MapQuest (using
Open Street Map data).
Windows 2000 Not Support ed: Since PRTG 7 we do not officially support Windows 2000
systems any more. This means, PRTG cannot be installed on systems running Windows 2000,
and you cannot officially monitor Windows 2000 systems (for example, via WMI). However, if
you could successfully monitor your Windows 2000 systems with PRTG 9, this might actually
not be possible any more with the current PRTG version. Especially the WMI Service Sensor
2373 will show an error message when monitoring Windows 2000 systems under the current
PRTG version. For a work around, please see More 49 section below.
Note: We recommend you to have a look at the Det ailed Sy st em Requirement s 23 before
updating to the current version! Officially supported operating systems, browsers, and other
requirements may have changed since version 9.
Update From PRTG Network Monitor 7 or 8

If you are using PRTG 7 or 8 now, your configuration will be kept when installing the current
PRTG version in St andalone Mode or when installing a Mast er Node. There are only a few
things you should consider.
Note: If you're running PRTG 7 or 8 we recommend you first update to the latest PRTG 8
version as an intermediate step, in order to make sure all data is carried over correctly. Please
contact technical support 2886 to obtain a download link for PRTG 8. In any case we recommend
you always keep a proper backup of your configuration and monitoring data.
Updat ing from PRTG 7 or 8 t o Current PRTG Version
Packet Sniffer (Content) sensors are not supported any more. Existing sensors of this type
will automatically be switched to Packet Sniffer (Header) sensors after the update. As a
benefit, you can now also sniff IPv6 traffic.
Internet Explorer 8 is no longer supported for access to the PRTG Ajax web interface or to
the mobile web GUI.
You may experience a slow Enterprise Console 2688 (former 'Windows GUI') due to different
reasons. For detailed information, please see the knowledge base article linked in the More
49 section below.
When installing a failover node on top of an existing stand-alone PRTG 7, 8, 9, 12, or 13+
installation, the configuration cannot be kept and is written to a backup folder. Then, the
new cluster configuration is received from the master node of the cluster. As all nodes work
with the same configuration, a failover node's old configuration and monitoring data can no
longer be used. If you want to keep a configuration of PRTG 7, please install the master node
on top of the old installation and use other servers for the failover node installations.
Since PRTG 9 the SNMP sensors use the IPv4 Out going IP set for the probe service (this
setting was formerly ignored by those sensors, using the aut o setting instead). If you
experience failing sensors, please check the setting in the probe settings 263 . For detailed
information please see More 49 section below.
48 02.02.2015
If you have (manually) configured the PRTG probe or PRTG core service to run under a
different Windows user account (for example, for successful internet access through an ISA
server firewall), please apply the respective Windows user account for the
"PRTGProbeService" and/or "PRTGCoreService" anew after installing the current PRTG version.
For detailed information please see More 49 section below.
Probe core and probe now require: SP1 (or later) on Windows 2003; Windows XP is no
longer officially supported.
If you use the default data path in your PRTG setup, it will be changed automatically. Up to
version 8 all data was stored in a sub folder reflecting a PRTG version number (v7 or v8). As
of version 9 this sub folder is omitted, and data is stored directly at %ALLUSERSPROFILE%
\Application data\Paessler\PRTG Network Monitor. During setup, all data will be moved to
the new directory. If you use a custom data path it will not be changed.
Up to version 8 all data in the registry was stored in a sub key reflecting a PRTG version
number (v7 or v8). As of version 9 this sub key is omitted, and registry data is stored directly
under the key HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor (on 32-bit
systems) respectively HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG
Network Monitor (on 64-bit systems). During setup, all existing registry values will be moved
to the new key.
Note: We recommend you to have a look at the Det ailed Sy st em Requirement s 23 before
updating to the current version! Officially supported operating systems, browsers, and other
requirements may have changed since version 8.
Updat ing from PRTG 7 t o Current PRTG Version
Regarding custom sensors, the interpretation of returned values is handled more strict as of
PRTG 8. If you're using custom sensors with PRTG 7, these may not work with the current
PRTG version if they do not fully apply to the API definition 2830 .
Update From Older PRTG Products

For all other predecessor products, a direct data import into the current version is not
possible.
If you have been using IPCheck 5 or PRTG Traffic Grapher 6, please perform a clean installation
of PRTG Network Monitor and set up your configuration anew. Using PRTG's Aut o-Discovery
198 is the easiest way to quickly configure a monitoring of your entire network. Please see
Quick St art Guide 32 section for more information.
More
Knowledge Base: How do I backup all data and configuration of my PRTG installation?
Knowledge Base: What about my web interface customizations as of PRTG 13.2.3?

02.02.2015 49
Knowledge Base: How can I monitor a Windows service on Windows 2000?

Knowledge Base: Why is the Enterprise Console so slow?

Knowledge Base: Some of my SNMP sensors do not work after updating from PRTG 8 to PRTG
9 or later
Knowledge Base: Probe Service or Core Service stop working after updating from PRTG 8 to
PRTG 9 or later
Knowledge Base: How and where does PRTG store its data?
Knowledge Base: Can I update from PRTG Traffic Grapher or IP Check 5 to the current PRTG
version?
Knowledge Base: How do I Import Data from PRTG Traffic Grapher 6 or IPCheck Server Monitor
5 in PRTG Network Monitor?
50 02.02.2015
Part 3: Installing the Software | 3 Install a PRTG Core Server
3.3 Install a PRTG Core Server

Installing PRTG is easy. It is similar to other Windows-based applications. To install the
application please run the installation setup program from the ZIP file that you have
downloaded.
Windows User Ac c ount Control Confirmation Request
Confirm the question of the Windows User Account Control with Yes to allow the program to
install. The usual software installation wizard will guide you through the installation process.
Setup Language Selec tion
Please select a language for your product and click the OK button. The available language
options depend on both your Windows version and the setup file.
02.02.2015 51
Setup Wizard Start Sc reen
Please click Next to walk through the wizard.
Setup Wizard Lic ense Agreement
Please accept the license agreement and click Next .
52 02.02.2015
Administrator Email Address
Please enter a valid email address. Your PRTG server will send important and urgent system
alerts to this address. Click the Next button to continue.
Lic ense Key Information
Please choose the folder you wish to install the software in. We recommend using the default
value.
02.02.2015 53
Setup Wizard Destination Loc ation
As soon as you click Next , the necessary files will be copied to your disk.
Setup Wizard Installing
After installation, the Ajax Web Int erface 102 is opened in your system's default browser.
Please make sure there is Google Chrome 40 or later (recommended), Mozilla Firefox 35 or
later, or Microsoft Internet Explorer 10 or 11 available on the system, and set as default
browser (see Sy st em Requirement s 21 ).
54 02.02.2015
Enter License Information

Only if you entered incorrect license information before you will be asked to enter a correct
license name and key.
Welc ome Wizard Enter Lic ense Information
Please enter both Name and Key exactly as stated in the email received from Paessler. We
recommend using copy&paste to avoid typing mistakes. For details, please see Ent er a
License Key 57 .
More
Knowledge Base: What is the PRTG Special Edition license?
Knowledge Base: How can I establish a secure web interface connection to PRTG?
Knowledge Base: PRTG blocks port 80 although I'm using SSL on port 443. How to free port
80?
02.02.2015 55
Part 3: Installing the Software | 4 Install a PRTG Cluster
3.4 Install a PRTG Cluster

PRTG offers single failover clustering in all licenseseven using the freeware edition. A single
failover cluster consists of two servers ("Current Master" Node and "Failover Node"), each of
them running one installation of PRTG. They are connected to each other and exchange
configuration and monitoring data. You can run a cluster with up to 5 nodes.
Illustration of a Single Failov er Cluster
For detailed information, please see Failover Clust er Configurat ion 2861 .
More
Knowledge Base: What's the Clustering Feature in PRTG?
56 02.02.2015
Part 3: Installing the Software | 5 Enter a License Key
3.5 Enter a License Key

A license key for PRTG Network Monitor consists of the license name and a license key. The
key is a string consisting of approx. 70 characters.
Your Personal License Information

You have received the license name and key form Paessler via email. This is either the
information for a Trial or a Commercial Edition.
EXAMPLE OF LICENSE INFOR MATION
License Name: John Q. Public

License Key: 0223515-FFSEJC-ZHGRDFM-UR1CS8-U73FGK-G645F2-YVF1DD-H8323N-
D11HG9-M2DRG
During the setup process, PRTG will ask you to enter your license information. Please use copy
and paste to fill out the form in the dialog shown by the installer.
Trial/Freeware license key : When entering a Trial license key, you can experience unlimited
functionality of PRTG during the trial period. Your installation automatically switches to a
Freeware Edition afterwards. For details about how to get your free Trial installer, please see
Download PRTG 45 section.
Commercial license key : This key can only be entered if you install the Commercial Edition
of PRTG, available for download in the customer service center. See Download PRTG 46
section for details. Your installation allows the number of sensors according to your license.
Change License Key

Usually you do not need to enter a key manually, as it is prompted during installation.
However, there are still scenarios where you want to change your key, for example, when
switching from a Trial Edition to a Special Edition 19 .
If you need to enter new license information, please follow these steps.
Step 1: Make Sure You Have Installed the Correct Edition

Please check first if you have installed the proper edition and then enter the license key.
There are two different installers available for PRTG (see Download 45 section):
The publicly available installer only contains the Freeware, Special, and Trial Editions. It does
not accept any commercial license keys.
The Commercial installer is only available for download to paying customers.
02.02.2015 57
The Commercial Installer must be installed to run the commercial editions of PRTG Network
Monitor. If y ou have purchased a license key for PRTG, please download and inst all t he
lat est Commercial Inst aller from t he Paessler websit e in order t o apply y our license
key . Note: You can install a commercial version "on top" of an existing Trial Edition in order to
maintain your configuration and monitoring data.
Step 2: Enter the License Key

You have two options to enter a license key. If you can login to the PRTG web interface 102 ,
choose Set up | Ent er License Key from the main menu bar 179 and provide your license
information 2678 . Alternatively, start the PRTG Administ rat ion Tool 2807 from the Windows Start
Menu. In this program, select the License tab.
To use a PRTG license with this installation of PRTG, please enter the license information you
have received from Paessler via email. To avoid typing errors, please copy and paste both the
License Name and the License Key from the email. Both must be transferred exactly as shown
in the email.
PRTG Administration Tool: Lic ense
To make sure your key has been entered correctly please click on the Check Key button. A
popup box will either show success or denial of your license information. License information
is also checked if you change tabs.
58 02.02.2015
In the Licensed Edit ion field you will see an accepted license key.
Click on the Ok button to save and confirm to restart the core server service by clicking on
the Yes button.
PRTG Administrator: Restart Core Serv er Serv ic e
02.02.2015 59
Part 3: Installing the Software | 6 Activate the Product
3.6 Activate the Product

PRTG tries to activate your license automatically via the internet on first start up. Only if PRTG
cannot connect to the internet directly, the web interface will display a Soft ware Act ivat ion
Required notice.
You have to run through the product activation process once to use PRTG continuously (only
Freeware and Trial Edition are always activated automatically and do not require a special
procedure). The activation has to be done within ten days after installation and only takes a
few minutes. If you do not activate PRTG for ten days, it temporarily reverts to the Freeware
Edition (with a maximum of 30 sensors) until you activate. Login to the PRTG web interface 104
to activate.
Activate via Internet

In the PRTG web interface, choose Set up | License from the main menu.
Click on the button St art Act ivat ion Now to start product activation. PRTG now connects
with the Paessler license server to check your license (via SSL on port 443). A few seconds
later you see Act ivat ion OK in the License Activation Status.
Note: The PRTG core server needs an internet connection on port 443 to activate. If a proxy
connection is needed, please configure it in the Sy st em Administ rat ionCore & Probes 2638
settings. Please see More 61 section for details about activation servers. In case activation
fails, you can activate via email.
Activate via Email

In the PRTG Web Interface, choose Set up | License from the main menu.
If there is no internet connection available, you can activate PRTG via email. To do so, first click
on the St art Act ivat ion Now button. You will then see Last message about act ivat ion:
Act ivat ion failed in the License Activation Status.
Once the activation via internet fails, the activation via email is available.
Click on the St art Act ivat ion per Email tab. You will see an Act ivat ion Request Code.
Copy it and send it to the email address shown.
Within two business days you will receive an email reply from Paessler, containing an
activation code.
Once you've received this email, go the Finalize Act ivat ion per Email tab and copy the
activation code into the according field.
Note: Ensure you only copy the code itself and nothing else from the email. Also, please
omit the "Activation Code Start/End" markers.
Click on Confirm Act ivat ion.
A few seconds later you should see Act ivat ion OK in the License Activation Status.
60 02.02.2015
Part 3: Installing the Software | 6 Activate the Product
More
Knowledge Base: Which servers does PRTG connect to for Software Auto-Update and for
Activation?
02.02.2015 61
Part 3: Installing the Software | 7 Install a PRTG Remote Probe
3.7 Install a PRTG Remote Probe

The local probe is already included in a PRTG core server installation 51 . You can install
additional remote probes on other computers in order to take load from the system running
the core installation or to extend monitoring to distributed networks. Note: You cannot install
a remote probe on a system already running a PRTG core installation.
Download Remote Probe Installer from the Web Interface

The remote probe version has to fit the PRTG core server version you will connect to. In order
download your setup program to the computer you want to install it on, please connect to the
Ajax web interface 104 . On the login screen 104 , enter login name and password and from the
main menu, select Set up | Downloads / Add-Ons | Remot e Probe Inst aller. Click on the
Download: Remot e Probe Inst aller button. Your browser will show a download dialog. Save
the setup program to your local hard disk drive.
Install Remote Probe

Please execute the setup program you've just downloaded.
62 02.02.2015
Remote Probe Setup Wizard Welc ome Sc reen
After accepting the license agreement, you can choose the folder you wish to install the
software in. We recommend using the default value.
02.02.2015 63
Windows GUI Setup Wizard Install
The PRTG Administ rat ion Tool 2794 is shown. Please enter the correct settings in order to
connect with your PRTG core installation. See Remot e Probe Set up 2856 section for more
information. Click Ok to continue.
64 02.02.2015
Probe Settings in PRTG Probe Administrator
When asked if you want to start the probe service, confirm with Yes. The installation is
completed.
PRTG Probe Administrator Start Serv ic e Request
After installation, click Finish.
02.02.2015 65
Remote Probe Setup Wizard Finish
Your remote probe is now installed on this computer as Windows service.
More
After you click the Finish button, the PRTG Administ rat ion Tool 2794 is shown, allowing you to
configure connections. Please see section Remot e Probe Set up 2856 for more information on
how to connect the remote probe with your PRTG core server installation.
Note: You can also install a Remote Probe directly from PRTG's web interface. For details, refer
to Remot e Probe Quick Inst all 2851 .
66 02.02.2015
Part 3: Installing the Software | 8 Install the Enterprise Console
3.8 Install the Enterprise Console

The Enterprise Console is already included in a PRTG core server installation 51 . You can install
additional Enterprise Consoles on other computers.
Download Enterprise Console from the Web Interface

The version of the Enterprise Console has to fit exactly the PRTG core server version you will
connect to. From the computer you want to install the Enterprise Console on, please connect
to the Ajax 102 web interface. On the login screen 104 of the web interface, enter login name
and password and select the Ent erprise Console (Download for Windows) option. You
browser will show a download dialog. Save the setup program to the local hard disk drive.
Install Enterprise Console

Please execute the setup program you just have downloaded.
02.02.2015 67
Windows GUI Setup Wizard Welc ome Sc reen
After accepting the license agreement, you can choose the folder you wish to install the
software in. We recommend using the default value.
68 02.02.2015
Select which icons will be created. We recommend using the default value.
Windows GUI Setup Wizard Additional Tasks
02.02.2015 69
Windows GUI Setup Wizard Install
After installation, click Finish to start the Enterprise Console.
Windows GUI Setup Wizard Finish
More
Please see section Ent erprise Console 2688 for more information on how to use this Graphical
User Interface (GUI).
70 02.02.2015
Part 3: Installing the Software | 9 Uninstall PRTG Products
3.9 Uninstall PRTG Products

The uninstall process has six stepsregardless of if you are uninstalling an entire PRTG
Network Monitor installation, a single Enterprise Console installation, or a PRTG Remote Probe
installation. Use the Windows uninstall routines to remove the PRTG software from your
system.
Step 1
From the Windows Start Menu, select the Uninst all PRTG Net work Monit or icon, the
Uninst all PRTG Ent erprise Console icon, or the Uninst all PRTG Remot e Probe icon, or open
your Windows Control Panel and choose the respective entry in the Programs section.
Depending on the installed products, not all uninstall programs are available.
Start Menu Ic ons
Step 2
If asked, confirm the question of the Windows User Account Control with Yes to allow the
program to uninstall. The usual software uninstall wizard will guide you through the uninstall
process.
Windows User Ac c ount Control Request
Step 3
Confirm the removal of the software by clicking the Yes button.
02.02.2015 71
Uninstall PRTG Network Monitor Step 1
Step 4
Wait while the software is being removed.
Step 5
Confirm a system restart by clicking the Yes button.
72 02.02.2015
Step 6
After system restart, the software is removed. However, there are still custom data in the PRTG
program folder left. If you have uninstalled an entire PRTG Network Monitor installation or a
remote probe installation, your monitoring data is still stored on the system. To completely
remove all PRTG data, please delete the PRTG Net work Monit or program folder as well as the
Paessler\PRTG Net work Monit or folder in your data path. For more information where data is
stored see Dat a St orage 2871 section.
More
Knowledge Base: Can we remotely and silently uninstall a Remote Probe?
02.02.2015 73
Part 4
Understanding Basic Concepts
02.02.2015 75
Part 4: Understanding Basic Concepts |
4 Understanding Basic Concepts

There are a number of basic concepts that are essential for understanding the functionality and
ease of use of PRTG Network Monitor. We have made using our software as easy as possible;
setting it up for the first start and getting first monitoring results happens almost automatically.
Nevertheless, there are some basic principles we would like to explain to you. Please read this
section carefully to understand the underlying workflow like architecture of the monitoring
system, hierarchy of objects, settings inheritance, notifying, etc. Afterwards, you will be able to
enhance your monitoring experience permanently.
Understanding Basic ConceptsTopics

Archit ect ure and User Int erfaces 77
Clust ering 81
Object Hierarchy 83
Inherit ance of Set t ings 88
Tags 90
Dependencies 92
Scheduling 93
Not ify ing 94
Dat a Report ing 95
User Access Right s 96
IPv6 99
76 02.02.2015
Part 4: Understanding Basic Concepts | 1 Architecture and User Interfaces
4.1 Architecture and User Interfaces

PRTG Network Monitor consists of different parts which can be divided into three main
categories: System parts, control interfaces, and a basic administration interface.
Ty pe Part of PRTG
System Parts Core Server 78

This is the central part of a PRTG installation and includes data
storage, web server, report engine, a notification system, and
more. The core server is configured is Windows service which run
permanently.
Probe(s) 78
The part of PRTG on which the actual monitoring is performed.
There are local probes, remote probes, and cluster probes
available. All monitoring data is forwarded to the central core
server. Probes are configured as Windows services which run
permanently.
A special kind of probes are the mini probes. Please see the
Applicat ion Programming Int erface (API) Definit ion 2830 for
details.
User Interfaces Ajax Web Int erface 102

The Ajax-based web interface is used for configuration of devices
and sensors, as well as the review of monitoring results. Also
system administration and user management are configured here.
Ent erprise Console 2688

A native Windows application (former Windows GUI) as alternative
to the web interface to manage your monitoring. With the
Enterprise Console, you can connect to different independent
PRTG core server installations and review their data at a glance!
Mobile Web GUI 2741

A read-only interface optimized for mobile access to your PRTG
installation. View latest states, tables, and graphs. Using jQuery
Mobile, this interface is compatible with almost all mobile devices
available on the market, as well as with older and unsupported
browser versions.
Smart Phone Apps 2744

Monitor your network on the go with PRTG and apps for iOS,
Android, Windows Phone, and BlackBerry devices.
PRTG Administ rat ion Tool on Core Server Sy st em 2795

System Administration Used to configure basic core server settings, such as administrator
Program login, web server IPs and port, probe connection settings, cluster
mode, system language, and more.
02.02.2015 77
Ty pe Part of PRTG
PRTG Administ rat ion Tool on Remot e Probe Sy st em 2818

Used to configure basic probe settings such as name of the probe,
IP and server connection settings, and more.
Core Server
The core server is the heart of your PRTG system and performs the following processes:
Configuration management for object monitoring

Management and configuration of the connected probes
Cluster management
Database for monitoring results
Notification management including a mail server for email delivery
Report generator and scheduler
User account management
Data purging (culling data that is older than 365 days, for example)
Web server and API server
In a cluster 81 , the current master node is responsible for all of these tasks.
The built-in, fast, and secure web server (no additional IIS or Apache is required) supports HTTP
as well as secure HTTPS (via SSL). It serves the web interface when accessed with a browser
and also answers PRTG Application Programming Interface (API) calls (for example, for user
scripts or the Enterprise Console).
Note: Core server and probe(s) are configured as Windows services which are permanently run
by the Windows system without the requirement for a logged-in user.
Probe(s)
On a probe, PRTG performs the actual monitoring with the sensors created on a device (for
example, computer, router, server, firewall, etc.). The probe receives its configuration from the
core server, runs the monitoring processes, and delivers monitoring results back to the core
server. On every system running a PRTG core server, there is always a local probe running with
it on the same machine.
78 02.02.2015
PRTG Core Serv er and Loc al Probe Monitoring a Loc al Area Network
The actual monitoring is performed by PRTG probe processes which run on one or more
computers. During installation, the system automatically creates the so-called Local Probe. In a
single-probe installationwhich is the default setupthe local probe performs all monitoring.
The PRTG core server inside the corporate LAN (bottom right in the figure above) is able to
monitor services and servers in the entire Local Area Network (LAN). Note: Core server and
probe(s) are configured as Windows services which are permanently run by the Windows
system without the requirement for a logged-in user.
In a cluster setup 81 , a cluster probe runs on all nodes. There is an additional so-called Clust er
Probe. All devices created on it are monitored by all nodes in the cluster, so data from
different perspectives is available and monitoring for these devices always continues, also if
one of the nodes fails.
PRTG automatically monitors system health of its own core server and of each probe to
discover overloading situations that may distort monitoring results. To monitor the system
status of the probe computer, PRTG automatically creates a few sensors. These include Core
and Probe Healt h, Sy st em Healt h, Clust er Probe Healt h, Disk Free, and a bandwidth sensor
for all installed network cards. We recommend keeping these sensors, but you can optionally
remove all except the Healt h sensors. They measure various internal system parameters of
the probe system hardware and the probe's internal processes and then computes a resulting
value. Frequent or repeated values below 100% should be investigated. Please check the
channels 126 of a particular sensor for details.
Additional so-called Remot e Probes can be created by the user in order to achieve monitoring
of multiple locations, or for several other scenarios. They are using SSL-secured connections
to the core and allow to securely monitor services and systems inside remote networks which
are not openly accessible or secured by firewalls. For more information, please see Remot e
Probes and Mult iple Probes 2847 section. For a video on this please see More 211 section
below.
PRTG Mini Probes allow you to create small probes on any device (not just on Windows
systems). You can implement mini probes to gather monitoring data exactly like you need it
and create them on any platform. For more information, see the Mini Probe API definition in
the PRTG web interface.
02.02.2015 79
More
Video Tutorial: There is a video available on the Paessler video tutorials page.
80 02.02.2015
Part 4: Understanding Basic Concepts | 2 Clustering
4.2 Clustering
A PRTG Cluster consists of two or more installations of PRTG 51 that work together to form a
high availability monitoring system. The objective is to reach true 100% uptime for the
monitoring tool. Using clustering 2861 , the uptime will no longer be degraded by failing
connections because of an internet outage at a PRTG server's location, failing hardware, or
because of downtime due to a software update for the operating system or PRTG itself.
How a PRTG Cluster Works

A PRTG cluster consists of one Primary Mast er Node and one or more Failover Nodes. Each
node is simply a full installation of PRTG which could perform the whole monitoring and alerting
on its own. Nodes are connected to each other using two TCP/IP connections. They
communicate in both directions and a single node only needs to connect to one other node
to integrate into the cluster.
During normal operation the Primary Mast er is used to configure devices and sensors (using
the web interface 102 or Enterprise Console 2688 ). The master automatically distributes the
configuration to all other nodes in real time. All nodes are permanently monitoring the
network according to this common configuration and each node stores its results into its own
database. This way, the storage of monitoring results also is distributed among the cluster (the
downside of this concept is that monitoring traffic and load on the network is multiplied by the
number of cluster nodes, but this will not be a problem for most usage scenarios). The user
can review the monitoring results by logging into the web interface of any of the cluster nodes
in read only mode. Because the monitoring configuration is centrally managed, it can only be
changed on the master node, though.
By default, all devices created on the Clust er Probe are monitored by all nodes in the cluster,
so data from different perspective is available and monitoring for these devices always
continues, even if one of the nodes fails. In case the Primary Mast er fails, one of the Failover
Nodes takes over the master role and controls the cluster until the master node is back. This
ensures a fail-safe monitoring with gapless data.
Note: During the outage of a node, it will not be able to collect monitoring data. The data of
this single node will show gaps. However, monitoring data for this time span is still available on
the other node(s). There is no functionality to actually fill in other nodes' data into those gaps.
If downtimes or threshold breaches are discovered by one or more nodes, only one
installation, either the Primary Master or the Failover Master, will send out notifications (via
email, SMS text message, etc.). Thus, the administrator will not be flooded with notifications
from all cluster nodes in case of failures.
Note: For clusters we recommend you to stay below 10,000 sensors per cluster.
Set Up a PRTG Cluster

For detailed information, please see Failover Clust er Configurat ion 2861 .
More
Knowledge Base: What's the Clustering Feature in PRTG?
02.02.2015 81
Part 4: Understanding Basic Concepts | 2 Clustering
82 02.02.2015
Part 4: Understanding Basic Concepts | 3 Object Hierarchy
4.3 Object Hierarchy

All objects in a PRTG monitoring configuration are arranged in a tree-like hierarchy to create an
easy to navigate list and to give the user the possibility to arrange them in groups that monitor
similar devices, services, or same locations. The hierarchical order described is also used to
define common settings for larger groups of objects, for example, settings of the Root group
apply by default to all other objects underneath (see section Inherit ance of Set t ings 88 ).
Objec t Hierarc hy in PRTG
The figure shows the object hierarchy in PRTG:
Root group contains all objects in your setup; all probes are directly under the root node.
A Probe contains one or more groups.
A Group contains one or more devices.
02.02.2015 83
A Device represents one component in your network which is reachable via an IP address.
On a device are several sensors.
A Sensor monitors one single aspect of a device and has at least one channel.
A Channel receives the monitoring results and is part of a sensor.
Root Group
The Root group is the topmost instance in PRTG. It contains all other objects in your setup.
Using the inheritance 88 mechanism, we recommend adjusting the default settings for the
Root group 232 . This makes configuration easier later on, because all other objects inherit
these standard settings by default and, thus, you will not have to set up the same
configuration for each object anew.
Probe
Each group (except the Root group) is part of a Probe. This is the platform on which the
monitoring takes place. All objects configured below a probe will be monitored via that probe.
Every PRTG core installation automatically installs a Local Probe service. You can add additional
probes and remote probes to your configuration to include remote devices from outside your
network into the monitoring (see section Mult iple Probes and Remot e Probes 2847 ). In a
cluster, there is an additional Clust er Probe running on all nodes. Devices on the cluster
probe are monitored by all nodes of the cluster, so data from a different perspective is
available and monitoring for these devices will always continue, even if one of the nodes fails.
Group
On each probe, there are one or more Groups, which serve merely structural purposes. Use
groups to arrange similar objects in order to inherit same settings to them. To a group, you
add the devices. You can arrange your devices in different nested groups to reflect the
structure of your network.
Find below a sample configuration: A device tree with local probe, several groups, devices and
their sensors.
84 02.02.2015
PRTG Dev ic e Tree View
Device
To each probe or group, you can add Devices that you want to monitor. Each device in your
PRTG configuration represents a real hardware or virtual device in your network. These can be,
for example:
Web or file server

Client computer (Windows, Linux, or Mac OS)
Router or network switch
Almost every device in your network that has its own IP address
Note: Sometimes you may want to add the same device in PRTG several times to get a better
overview when using many sensors for a very detailed monitoring, or to use different device
settings for different groups of sensors. In PRTG you can simply add multiple devices with the
same IP address or DNS name. The sensors on all of these PRTG devices will then query the
same real hardware device in your network.
PRTG additionally adds a so called Probe Device to the local probe. This is an internal system
device. It has access to the computer on which the probe is running on and monitors its
health parameters with several sensors running on it.
02.02.2015 85
To get a better and more detailed picture about your devices, PRTG automatically analyzes the
devices which you add and recommends appropriate sensor types 311 on the device overview
tab 126 . In the Recommended Sensors table, click on the Add Sensors button in the
corresponding table row to create recommended sensor types with one click.
Note: You can turn off the sensor recommendation in Sy st em Administ rat ionMonit oring
2628 .
Sensor
On each device you can create a number of Sensors. Every sensor monitors one single aspect
of a device. This can be, for example:
One network service like SMTP, FTP, HTTP, etc.

One network switch port's traffic
CPU load of a device
Memory load of a device
Traffic on one network card
One NetFlow device
System health of a device
Other content (for example, of databases, mails, HTTP, XML, files, etc.)
etc.
Channel
Every sensor has a number of Channels through which it receives the different data streams.
The available channels depend on the type of sensor. One sensor channel can contain, for
example:
Downt ime and upt ime of a device

Traffic in of a bandwidth device (for example, a router)
Traffic out of a bandwidth device (for example, a router)
Traffic sum of a bandwidth device (for example, a router)
WWW t raffic of a NetFlow device
Mail t raffic of a NetFlow device
Ot her t raffic of a NetFlow device
CPU load of a device
Loading t ime of a web page
Download bandwidt h of a web page
Time t o first by t e of a web page
86 02.02.2015
Response t ime of a Ping request to a device

Response t ime of a Remote Desktop service
etc.
02.02.2015 87
Part 4: Understanding Basic Concepts | 4 Inheritance of Settings
4.4 Inheritance of Settings

The hierarchical tree 83 is not only used to group sensors for organizational reasons, there is
also an important aspect involved that we call inheritance. To ensure administration is quick
and easyespecially for large monitoring setupscertain settings are inherited from the
overlying level. For example, you can change the monitoring interval for all sensors by editing
the interval setting of the topmost Root group (unless no other setting is defined below).
Settings are Inherited to Child Objects

You can override this inheritance on any level of the hierarchy by setting a different value for a
specific probe, group, device, or sensor. All objects below will inherit these new settings;
object settings from levels above will stay unchanged.
Settings that are inherited among all objects include:
Monitoring interval
Notification triggers
Authentication settings for several systems
Compatibility settings (for certain types of sensors)
Channel and unit configuration
User access rights 96
Tags 90
Paused status: If an object is paused by the user, or a schedule, all sensors on it are paused
as well
etc.
There is one exception for devices and sensors: The IP address or DNS name of a device and
compatibility settings are always inherited by sensors and can not be changed on sensor level.
The actual overriding of the parent's settings takes place in an object's settings: Remove the
check mark symbol at the beginning of the respective line inherit from [parent object ]. For
example, the screenshot below shows Windows systems credentials settings after removing
the check mark symbol.
Credentials for Windows Sy stems
88 02.02.2015
Part 4: Understanding Basic Concepts | 4 Inheritance of Settings
Default Values Set in Root Group

For all settings (except passwords), PRTG already includes a set of default values so you can
get started with the software immediately. For example, the following settings will be inherited
by all sensors from the Root group:
Default monitoring interval of one minute

SNMP version 1 with community string set to public (default values for most devices)
Dependency type Use parent
etc.
You may need to change some of the default entries as you become used to the interface.
However, these settings will initially suffice for most situations.
Before sensor setup, please review the Root group's settings and set the default values to
suit your setup, including necessary credentials for all kinds of systems in your network you
want to monitor (Windows, Linux, virtual servers, etc.).
See section Root Group Set t ings 232 for more details.
Inheritance of Notification Triggers

If you add notification triggers on probe, group, or devices level, these will also be inherited to
all sensors underneath, unless you cancel inheritance with specific settings.
See section Sensor Not ificat ions Set t ings 2484 for details.
02.02.2015 89
Part 4: Understanding Basic Concepts | 5 Tags
4.5 Tags
For every object in your PRTG setup, you cannot only name objects, but also define tags in
the object settings 143 to additionally mark an object as a member of certain categories.
Although there are tags predefined when adding objects 212 , you are completely free in the
way you add tags. For example, you can mark all of the bandwidth sensors which are especially
important for you with the tag bandwidth_important.
Later, you can view lists of objects with certain tags (helpful for multi-edit 2506 of settings), or
choose sensors by tag when creating reports 2549 . A clever arrangement of tags can save you a
lot of time at some point. Press one of the keys enter, space, or comma to confirm a tag.
Note: You can also change tags for several objects at a time using the multi-edit 2506 function.
View and Edit Tags in Basic Sensor Settings
Tags Are Inherited

The tags in the settings of an object are automatically inherited 88 to all other objects
underneath in the hierarchy 83 . So, for example, a device with the tag myExampleTag
automatically and invisibly inherits this tag to all sensors which you create on it. This is not
visible in the sensor tag settings, but the sensors appear in the list whenever you search for
myExampleTag. This is useful, for example, when you add sensors by tag in reports 2549
settings.
This way, to configure your setup for fetching all sensors on a device by tag, you do not have
to tag every single sensor, but it is enough to tag the device. Inheritance for tags cannot be
disabled.
Filtering with Tags

You can use tags to filter table lists 157 for specific objects, or to add sensors to Libraries 2533
and Report s 2549 . For example, you can show only sensors on the sensors overview page 183
which have the tag bandwidth_important. You can also use more than one tag to filter for
monitoring objects like sensors.
When filtering with tags, you can also use plus (+) and minus () signs in front of tags to
categorize them:
90 11.02.2015
Part 4: Understanding Basic Concepts | 5 Tags
Tags with + must exist for an object to be shown

Tags with must not exist for an object to be shown
At least one tag of the tags without + or must exist for an object
The filter shows an object only if all three conditions are true. The order of the tags in a tag
field does not matter.
For example, if you enter windows into a tag field, all sensors/devices that do not have
"windows" as tag are shown. With +windows or windows you filter for objects which are
tagged with "windows".
You can use more than one logical operator in a tag field: For example, if you enter +netflow
bandwidth_important into a tag field, the corresponding list, library, or report includes all
sensors that are tagged with "netflow" but not with the tag "bandwidth_important". If you
enter netflow bandwidth_important, a sensor has to be tagged with "netflow" or
"bandwidth_sensor" or both to be affected.
11.02.2015 91
Part 4: Understanding Basic Concepts | 6 Dependencies
4.6 Dependencies
Using dependencies, you can pause sensor monitoring based on the status of another sensor
in order to avoid false alarms and incorrect downtime recording. A dependency stops the
monitoring of one sensor or a set of sensors as soon as a specific sensor is not in an Up
status. This means, for example, you can stop monitoring remote network services when the
corresponding firewall is down due to connection problems.
When using the auto-discovery 198 function, the Ping sensor on a device is by default set as
the master object for this device. This means that monitoring for the entire device is paused if
the Ping sensor is in a Down status. Usually, it does not make sense to monitor other aspects
of a device with other sensors while the Ping sensor indicates that the device is not even
reachable.
In order to view a list of all dependencies or only selected dependencies, choose Devices |
Dependencies and the corresponding dependencies path from the main menu 181 . From there
you can also access the Dependencies Graph 2514 that visualizes all dependencies within your
network.
Dependenc ies Graph
For more information about the dependency settings, please see the settings of the
respective object 143 you want to set a dependency for.
92 02.02.2015
Part 4: Understanding Basic Concepts | 7 Scheduling
4.7 Scheduling
Using schedules, monitoring of an object can be paused 164 for a certain time, for example,
Sundays between 4 and 8 a.m. A paused sensor will not collect monitoring data, will not
change its status, and will not trigger any notifications 94 . With schedules you can limit the
monitoring time automatically. You can also pause monitoring for planned system maintenance
time spans to avoid false alarms. You can apply different schedules to every object. They are
also used for reports and notifications.
Av ailable Default Sc hedules in Dev ic e Settings
Schedules are user account specific. To change the default pre-defined schedules or to add
your own schedule, please see Account Set t ingsSchedules 2612 section.
Note: If you use failover clustering with nodes in different timezones, scheduling applies at the
local time of each node. For more information, please see section Failover Clust er
Configurat ionBefore Get t ing St art ed 2861 .
02.02.2015 93
Part 4: Understanding Basic Concepts | 8 Notifying
4.8 Notifying
PRTG Network Monitor keeps the administrator or other responsible persons informed about
the current status of the network. There are several methods how the administrator can stay
up to date.
Notifications
This is the most powerful information tool. Whenever PRTG discovers downtime, an overloaded
system, threshold breaches (for example, a disk runs full), or similar situations, it can send a
notification. Notifications use various methods by which you can be notified (for example, email
2598 , SMS 2593 , push messages 2599 , and others). After creating notifications in the system settings,
you can select them on the notifications tab of probes, groups, devices, and sensors, as well
as on the root group. See Not ificat ions 2521 section for more details and Set t ing Up
Not ificat ions Based on Sensor Limit s: Example 2524 for a step-by-step guide.
Limits
In a sensor channel's settings 2477 , you can set limits to change the status of the sensor when
certain limits are breached. This way, you can set, for example, a traffic sensor (typically never
in a error status) to Down status whenever bandwidth values are measured that you consider
critical. This sensor will then show up in the alarms list.
Alarms
The alarms list shows all sensors that are currently in a Down, Down (Acknowledged),
Warning, or Unusual status. This is useful to keep track of all irregularities in your network. In
the table list, you can re-sort the items by clicking on the column's header items. See Alarms
145 section for more details.
Logs
In the logs list, the log file with all monitoring events is shown. In a typical setup, a huge
amount of data is produced here. As the activity of every single object is minuted, you can use
this data to check exactly if your setup works as expected. See Logs 148 section for more
information.
Tickets
The tickets list shows items with important system information or action steps to take for the
administrator. You should view every ticket and take appropriate actions. Per default, an email
is sent to the administrator for every new ticket that is created by the system or another user.
If a ticket is assigned to a specific user, this user will get an email by default. See Ticket s 150
section for more information.
94 02.02.2015
Part 4: Understanding Basic Concepts | 9 Data Reporting
4.9 Data Reporting

With Report s 2549 you can analyze and review monitoring data for specific time spans. There are
several ways to create data reports in PRTG for your individual needs.
View Historic Data

To get a report for a single sensor, there is a function included to review historic data in PRTG.
It allows you to generate reports and charts for a single sensor's data. See Hist oric Dat a
Report s 135 section for more information.
Generate Reports
You can use the sophisticated reports machine included in PRTG to create exhaustive reports
for all monitoring data. See Report s 2549 section for more information.
Export Data Using the API

You can also export all monitoring raw data to XML or CSV files and generate your own
reports using any third party software. See Using t he PRTG API (Applicat ion Programming
Int erface) 2830 section for more information.
Make Data Available

You can make monitoring data available to other persons using a special user with read-only
rights (see User Access Right s 96 section), or you can create public or semi-public HTML
pages with monitoring data using the Maps feature. See Maps 2569 section for more
information.
Bill Customers
You can also create custom billing reports based on PRTG's monitoring data, using the open
source Billing Tool for PRTG. For details and download, please see More 95 section below.
More
Dat a St orage 2871
Paessler Website: Billing Tool

http://www.paessler.com/tools/billingtool
02.02.2015 95
Part 4: Understanding Basic Concepts | 10 User Access Rights
4.10 User Access Rights

The default administrator can use the PRTG installation as the only user or can create an
unlimited number of users. Users are organized in an unlimited number of user groups. Access
rights for each individual object in your PRTG device tree 83 can be given separately for each
user group (except for sensor channels). Access rights to objects can also be inherited 88 .
In addition, every single user has specific rights: There are administrator users, read/write
users, and read only users. You can define these settings in Sy st em Administ rat ionUser
Account s 2644 . With these tools, you can create a rights management that allows you to specify
exactly what users will be able to see and edit.
User Rights in User Ac c ount Settings
Individual user rights in combination with access rights of the group(s) they belong to conduct
the access rights to certain objects in the device tree. This means that group membership
particularly controls what a user is allowed to do and which objects the user will see when
logged in.
The actual access rights for each object in the device tree can be defined in an object's
settings. You can define different access rights for all sensors, devices, groups, or probes via
the corresponding Cont ext Menus 165 or in the Object Set t ings 143 .
Access Rights Overview

The following classes of access rights for objects are available in hierarchical order as they can
be given to user groups (lowest rights to highest rights):
None: The object will not be displayed to the users of the group; no logs, no tickets, no
alarms regarding this object will appear.
Read: Only monitoring results can be seen.
Writ e: Reviewing monitoring results and editing settings is allowed. In addition, objects can
be added to and deleted from the device tree.
Full: Reviewing monitoring results, editing settings, and editing access rights is allowed. In
addition, objects can be added to and deleted from the device tree.
Admin right s: If a user group has administrator rights, all options are available, including
creating users, creating user groups, and deleting objects from the device tree. Access
restrictions to objects cannot be set for this type of user group.
96 02.02.2015
Note: Access rights that are defined locally on an object, for example, on a device, override
inherited 88 rights. On a certain object, the highest directly set access right applies for a user
group. If there is no access right set directly on an object, the next higher object level will be
checked for access rights. This process is repeated until defined access rights are found to be
inherited or there is no higher object level.
Different Ac c ess Rights for a Firewall in the Dev ic e Tree Depending on User Groups
Please see the table below for which user rights apply when. Column headings show access
rights of user groups for objects in the device tree; line headings show the type of user.
Note: Users are either in PRTG user groups or in Active Directory Domain user groups. They
cannot be in both. We recommend to use only one type of user group (either PRTG or Active
Directory) to minimize your administration effort.
PRTG User PRTG User PRTG User PRTG Sy st em

Group Group Group Administ rat or
Domain User Domain User Domain User Domain
Group Group Group Administ rat or
R EAD ACCESS R EAD/WR ITE FU LL ACCESS

ACCESS
PRTG User Read Read-only rights Read-only rights Read-only rights Admin rights
Only
Domain User
Read Only
02.02.2015 97
PRTG User Read-only rights Read/write rights Full access Admin rights
Read/Writ e
Domain User
Read/Writ e
Users in an administ rat or group have always administrator access rights, no matter of the
access rights of an object.
Read-only users have just read rights, no matter of the access rights of their group, except
for users which are members of an administrator group.
Read/writ e users in a group with full access to an object have full access rights to this
object only.
If a user is in more than one group, access rights of the user group with the highest right s
apply .
Administrator rights can only be given via the administrator group.
For more information about defining access rights, please see the following sections:
Sy st em Administ rat ionUser Account s 2644
Sy st em Administ rat ionUser Groups 2649
For information about connecting PRTG to an existing Active Directory, please see Act ive
Direct ory Int egrat ion 2827 .
98 02.02.2015
Part 4: Understanding Basic Concepts | 11 IPv6
4.11 IPv6
PRTG supports the IPv6 protocol for most sensor types. You can define whether data from
your network is queried via IPv4 or IPv6: For each device in PRTG you can select whether PRTG
will connect to it using either IPv4 or IPv6. This is a simple selection in the Device Set t ings 288
of each device. Depending on the setting, the sensors created on this device will use the
respective protocol.
In the Out going IP Set t ings of the PRTG Administ rat ion Tool 2821 , you can additionally
choose which IPv6 address will be used for outgoing monitoring requests.
Note: There is the same option for IPv4, too.
02.02.2015 99
Part 5
Ajax Web InterfaceBasic Procedures
02.02.2015 101
Part 5: Ajax Web InterfaceBasic Procedures |
5 Ajax Web InterfaceBasic Procedures

The Ajax-based web interface is your access to PRTG. Use it to configure devices and sensors,
to set up notifications, as well as to review monitoring results and to create reports. This web
interface is highly interactive, using Asynchronous Java Script and XML (AJAX) to deliver a
powerful and easy-to-use user experience. While you are logged in 104 , the PRTG web interface
permanently refreshes the data on the screen permanently (via Ajax calls) so it always shows
the current monitoring results (you can set 2644 refresh interval and method individually).
Because the web interface works as a Single Page Application (SPA), you rarely see a full page
refresh to avoid this performance impact due to redundant processing. Only single page
elements are refreshed when necessary. The AJAX web interface shows all object setting
dialogs as pop-up layers, so you never lose the current context. This speeds up the user
experience appreciably and makes the configuration of objects in PRTG comprehensible. The
responsive design of the web interface ensures that it always adjusts to the size of your
screen to see more information at a glance.
The following sections introduce the features and concepts of the Ajax Graphical User
Interface (GUI).
102 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures |
Ajax Web InterfaceBasic ProceduresTopics

Login 104
SSL Cert ificat e Warning 107
General Lay out 110
Sensor St at es 123
Review Monit oring Dat a 126
Compare Sensors 132
Hist oric Dat a Report s 135
Similar Sensors 139
Object Set t ings 143
Alarms 145
Logs 148
Ticket s 150
Working wit h Table List s 157
Object Select or 160
Priorit y and Favorit es 161
Pause 164
Cont ext Menus 165
Hover Popup 178
Main Menu St ruct ure 179
Other Ajax Web Interface Sections

Ajax Web Int erfaceDevice and Sensor Set up 196
Ajax Web Int erfaceAdvanced Procedures 2496
Related Topics
Ot her User Int erfaces 2740
02.02.2015 103
Part 5: Ajax Web InterfaceBasic Procedures | 1 Login
5.1 Login
Once the PRTG core server is installed 51 , you can log in to the web interface. In your browser,
load the IP address or DNS name of the computer PRTG is installed on and log in using the
Default Login button.
You can look up and change PRTG's web server settings at any time using the PRTG
Administ rat ion Tool 2796 Windows application on the system where the PRTG core server is
installed on. Especially when accessing PRTG from the internet you should use an SSL
encrypted connection. You can easily switch to SSL using the Yes, swit ch t o SSL button
shown on the welcome screen.
Loading the Web Interface

In a web browser window, please enter the IP address or URL of the system PRTG is installed
on. When using a cluster, please connect to the primary master node. You can also double
click on the PRTG Net work Monit or icon on the desktop of the system PRTG is installed on.
Note: If you run PRTG on localhost, please do not use the DNS name http://localhost to log in
to the web server, as this may considerably slow down PRTG's web interface. Please use your
local IP address or http://127.0.0.1 instead.
Desktop Ic on
If you see a certificate warning in your browser, you can usually just confirm it. For more
information please see SSL Cert ificat e Warning 107 .
Login Screen
After loading the web interface, the login screen is shown. You can either login as default
administrator or as an other PRTG user. As Administrator user you can use all functionalities of
the web interface. Administrators can create additional users 2644 with administrator rights or
with more restricted privileges (for example, read only users).
Additionally, there are different GUI versions available.
104 02.02.2015
PRTG Login Sc reen
Login as Default Administrator (First Time Login)

When logging in for the first time, login name and password for the default administrator login
are both prt gadmin. You can leave the login name and password fields empty and click on
the Default Login button to log in using these default credentials.
Note: After login you should change the default password. To do so, go to Set up | Account
Set t ings | My Account and specify a new password in section User Account .
Note: If you are not logged in into the web interface, you can change the credentials for this
default user account any time in the PRTG Administ rat ion Tool 2805 Windows application.
Login as PRTG User

If you have received user credentials from your administrator, please enter them here to login.
Also, when using other administrator credentials, please enter them here.
Choose GUI version

Depending on the used browser, different Graphical User Interface (GUI) options are shown:
Use AJAX Web GUI (All feat ures, opt imized for deskt op access): The standard interface.
We recommend to use this option for PRTG whenever possible. It offers the full functionality
of PRTG. Use Google Chrome 40 or later (recommended) or Mozilla Firefox 35 or later for
best performance. In some browsers, the Ajax option is not shown, for example, in old
browser versions.
Note: Although you can login using Microsoft Internet Explorer 10 or 11, the Ajax web
interface might not be fully compatible with Internet Explorer! When using Microsoft
Internet Explorer 10 or 11, please set the security level at least to Default level Medium-
high and make sure you do not use the Compat ibilit y View! For detailed information,
please see More 106 section below.
02.02.2015 105
Use Mobile Web GUI (Limit ed funct ionalit y , opt imized for mobile access): The Mobile
Web GUI 2741 interface is optimized for slow network connections and old browsers. It only
offers read-only functionality and comes with less scripting. It is also a fallback solution when
using a browser that is not supported by the Ajax interface.
Download Client Soft ware (for Windows, iOS, Android): This option calls PRTG's download
page in the Mobile Web GUI. You can optionally download the native Windows application
Ent erprise Console to the desktop (called Windows GUI in previous deprecated PRTG
versions). It has to be installed 2688 on the client computer before use. The Enterprise
Console 2688 provides full functionality; however, for some functions the Ajax Web GUI is
opened. As an additional feature, the Enterprise Console can view data of several
independent PRTG core installations in a single application.
You can also access pages on Paessler's website from here for information about the PRTG
apps 2744 PRTG for Android and iPRTG for iOS. These pages contain also the download links
for the apps for your mobile device. Note: Also when using this download option, login
name and password (or a Default Login) are required!
Note: Only Google Chrome 40 or later (recommended) and Mozilla Firefox 35 or later are fully
compatible with the Ajax web interface. For more information about Internet Explorer support,
Click on the Login button to proceed to the PRTG web interface.
More
Knowledge Base: Why are Internet Explorer IE6 and IE7 not supported by PRTG's Ajax Interface?
Knowledge Base: How can I access the AJAX web interface of PRTG with Internet Explorer 9 or
IE10?
106 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 2 SSL Certificate Warning
5.2 SSL Certificate Warning

If you use PRTG outside your internal LAN, especially when you use it on the internet, you
should switch the internal web server to use SSL. After doing so, your browser shows a
certificate warning because the certificate that comes with PRTG cannot be signed by a valid
authority. Anyway, the connection to your PRTG web server is secured via SSL, and you can
confirm the claimed security risk. For more information on secure browser connections, please
see the More 109 section below.
Every browser shows the certificate warning in a different layout. The steps to take are similar
for every browser, yet different in detail:
Google Chrome 107
Mozilla Firefox 108
Internet Explorer 108
Other 109
Google Chrome
In Google Chrome, click on Advanced and then on Proceed t o [y ourPRTGserver] (unsafe)
every time you call the PRTG web interface.
Sec urity Warning in Google Chrome Browser
02.02.2015 107
Mozilla Firefox
In Mozilla Firefox, click on I Underst and t he Risks and then on the Add Except ion... button.
In the appearing window, leave the check mark for Permanent ly st ore t his except ion and
finally click on the Confirm Securit y Except ion button.
Sec urity Warning in Mozilla Firefox
You only have to go through this procedure once for every Firefox browser and PRTG core
server.
Internet Explorer
In Int ernet Explorer, click on Cont inue t o t his websit e (not recommended) every time you
call the web interface.
108 02.02.2015
Sec urity Warning in Internet Explorer
Other
For other browsers that are not officially supported, the procedures to confirm the certificate
are similar to the ones described above.
More
Using Your Own SSL Cert ificat e 2873
Knowledge Base: Why don't I get an SSL connection to the PRTG web interface?
Knowledge Base: Why can't I save my PRTG password in Google Chrome?

02.02.2015 109
Part 5: Ajax Web InterfaceBasic Procedures | 3 General Layout
5.3 General Layout

This manual section provides an overview about the structure of PRTG's web interface. The
main focus is on the Devices view which you can select via the main menu bar, because there
you see your monitoring results at a glance so you will widely use it.
Welcome Page
Once you have run through the Configurat ion Guru 36 , you will see PRTG's welcome page as
default after you log in to the web interface. You can set another homepage in your account
settings 2587 , section Web Int erface.
You have the following options on the welcome page:
Run Configurat ion Guru 36
Download Windows Client App 2680
Perform Net work Aut o-Discovery 198
Inst all Smart phone Client Apps 2744
Review Result s 135
Get Help and Support : Opens the help center where you find links to this manual, to the
Knowledge Base, and the contact Paessler support form 2684 .
PRTG Welc ome Sc reen
110 02.02.2015
Tree View Layout

Click on the Review Result s option on the welcome screen to display the tree-like device
view which will be a starting point for everyday use or on Devices in the main menu bar.
PRTG Dev ic e Tree
From top to bottom, the main layout consists of:
02.02.2015 111
Screen Part Descript ion

Number
1 Global Header This element contains the main menu at the top, the global
Area 113 status bar, the path to the currently selected object, and a
quick search box.
2 Page Header Bar This element contains the page heading with the name of the
114 current object, several tabs with settings, monitoring data, etc.
of the current object, the object's status bar, quick action
buttons, and the QR code linking to the current URL.
3 Device Tree This selection is part of the page header bar. Using the
View 117 provided options you can define how your device tree is
displayed.
4 Page Content This element contains information about the current object and
121 all other objects underneath in the tree hierarchy.
5 Page Footer With these icons you have quick access to the PRTG Auto-
Icons Update page, to PRTG's social network accounts, and to the
contact support form 2684 . There is also a link to context
sensitive help.
When running PRTG in a cluster, you will also see a cluster
related element. It shows the name of the node you are logged
in and displays whether this is a master or a failover node. Click
the bar to show the Clust er St at us 2675 . In a failover node, you
can review all data, but changes in the settings will not be
saved. In order to change settings, please log into the master
node of your cluster.
6 Page Footer Shows information about the current version of PRTG, the
logged in user, the time remaining to the next automatic page
refresh, and the current time.
Simply click on an object to see more details about it. In the page heading of the page header
bar 114 you always see which object you're looking at.
When you navigate through PRTG's web interface you will always use one of the following
navigational paths:
The main menu provides access to all important aspects of the software.
The quick search is often the fastest way to navigate to an object.
Using the page's tabs, you can switch between various sub-pages for an object.
Many objects offer a context menu that will pop up when you right-click them.
Many objects offer a quick-info menu that will pop up when hovering an object
112 02.02.2015
And, finally, you are able to drill down into the object hierarchy of probes, groups, devices,
and sensors in the object tree by merely clicking an sub-object of the currently displayed
object (for example, a sensor on the device page).
These six navigation paths put PRTG's complete functionality at your fingertips. Quite likely you
are already familiar with these techniques from many other websites and web-based user
interfaces.
In the following, the different areas of the web interface are described.
Global Header Area
PRTG's Global Header Area
The header area of the web interface is both base for the most important information of your
installation and starting point for all actions. You can view the global status and navigate
through the web interface using the main menu.
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax
interface on a master node. For other user accounts, interfaces, or nodes, not all of the
options might be available as described. When using a cluster installation, failover nodes are
read-only by default.
The global header area consists of the following parts:
02.02.2015 113

Number
1 Main Menu Bar Navigating through the web interface is performed using the
main menu. Please take a few minutes to familiarize yourself
with all menu items and sub-items. A detailed description can
be found in the Main Menu St ruct ure 179 section.
2 Icons Refresh, With the icons on the right you can reload the current page,
Help Center, open the help center or log the current user out.
Logout
3 White Search To search for any monitoring object, enter the name, part of
Box the name, an IP address, a DNS name or a tag in the search box
on the right and hit the enter key. A web page with all items
that fit the search term will be returnedeven displaying online
help articles.
4 'Breadcrumbs' Below the main menu, there is always a path shown, leading to
the homepage. Use it to go back to where you came from. It
can also help you to orient yourself in case you get lost. If you
click on a 'breadcrumb' item to open a drop-down menu
showing all available object on the same level. Enter a view
letters to search for a name, or select an object directly. For
example, you can use this to directly access all other sensors
or a device, the other devices within a group, another group on
the same probe, or other probes in your root group.
5 Buttons New These buttons show the number of new alarms and new log
Alarms, New Log entries, as well as the number of new tickets. Click on the
Entries, New respective button to view the Alarms 145 , Logs 148 , or Ticket s
Tickets 150 .
6 Global Sensor This area shows the aggregated status of all sensors you have
Status Symbols configured for monitoring, divided into different sensor states.
Depending on the sensors' status you will see colored boxes
with numbers which symbolize the sensors. For example, you
can see how many sensors are in Up, Down, or Warning state.
Click on a box to view a list of all sensors in the respective
status. For a detailed description, please see Sensor St at es 123
section.
Page Header Bar

In the page header under the global header area, you see the name of the current object and
the page content underneath. When displaying a group, aggregated sensor states are shown
in a sensor bar and there is an option to change the tree view. Furthermore, various
information about the current object is reported here.
114 02.02.2015
PRTG's Page Header Bar
The page header and tabs area consists of the following parts:
02.02.2015 115

Number
1 Page Heading This line displays the kind of the current object and the name
as page heading. In the screenshot above, it is a group which is
called Root . Here you also can add the current object to
favorites by clicking on the flag, as well as you can define the
object's priority by clicking on one of the five stars (not
available for the Root group). For details, please see section
Priorit y and Favorit es 161 .
2 Tabs Using the tabs you can navigate to various sub-pages of an

object, showing monitoring data or changing settings. For
more information, please see sections Review Sensor Dat a 126
and Change Device and Sensor Set t ings 143 .
3 Context Buttons On the right side are icons which allow you to perform several
actions. Depending on the currently viewed page within PRTG,
you can pause (and resume) or delete this object, add another
object (for example, a sensor to a device), send a link to the
current page per email, perform an immediate scan, open a
related ticket, and show the corresponding object history page
148 . On device lists, there is also a button to open the QR
codes of all devices in this list in a printable layout.
Click on the down arrow to open the context menu for the
currently displayed object with even more options. For more
information, please see Cont ext Menus 165 section.
4 Object Status This element indicates the current status of the selected
object.
5 Sensor Status This element is visible when viewing a probe, a group

Bar (including Root ), or a device. It is not available when viewing a
sensor's details. The sensor status bar shows the aggregated
status of all sensors for the current object, divided into
different sensor states. They show the number of sensors in
the respective state. For example, you can see how many
sensors are in Up, Down, or Warning state. For a detailed
description of sensor states, please see Sensor St at es 123
section. You can hide sensors that are in a certain state by
removing the check mark symbol in front of the respective
sensor symbol. To show them again, re-add the check mark.
6 Tree Search In the white search box next to the tree view selection, enter a
key word to search the device tree for matching names. The
tree will then highlight matching devices and sensors by
graying out all others. This can help to gain a quick overview
over sensors monitoring a specific part of your network. For
example, you can enter the keyword "firewall" to highlight
devices and sensors which match this name.
116 Device Tree This element is only visible when viewing a probe or a group. It 02.02.2015
7
View is not available when viewing a device's or sensor's details. For
a detailed description, see Switch Device Tree View 117 below.
Depending on the selected object type, the page header bar shows additional information. All
objects underneath the Root group indicate their dependency 92 , groups and devices show
the past time since the last auto-discovery 198 was run on the selected object (hover to show
the exact date and time), and devices show their respective DNS/IP address as defined in the
device settings 288 . Sensors show additional monitoring statistics.
Switch Device Tree View

When viewing a probe or group, you can choose the way your device tree is shown.
Dev ic e Tree View Switc h

Buttons
Switch Device Tree ViewClassic Device Tree

Using the different circle symbols in the page header bar, you can define how much space is
used to show devices and sensors in a hierarchical tree structure. In four steps, you can
switch from a very condensed view (small circle; marked with 1 in the screenshot) up to an
extra large view (big circle; marked with 4 in the screenshot).
In the classic device tree view you can collapse devices, groups, and probes. Click on the
minus box left to the object's name. The sensor states will be summarized then. Each status of
the sensors on this object will be displayed with the number of sensors currently being in this
statuswith the exception of the states Down, Down (Part ial), and Down (Acknowledged).
These will be summarized respectively not before there are more than ten sensors in this
status, otherwise they are displayed individually.
Collapsed Dev ic e With Summarized Ups and Unusuals and Indiv idual Downs
Switch Device Tree ViewExtended Views

There are two additional options to the simple tree views which enable you to display the
status of all sensors of your entire installation in a single overview. Click on one of the icons
to change the view:
Tree Map View (6)

The tree map view tiles all devices of your entire installation into one square, arranged by the
groups you put them into. Each device changes color dynamically to reflect the overall status
of the sensors on the device. You can also adjust the size of the squares: either depending on
a device's priority, or depending on the number of sensors on a device, or depending on both.
For this concern, add a check mark under the point Size by : in front of Sensors and/or
Priorit y in the page header bar (see the mark in the screenshot below).
02.02.2015 117
PRTG Tree Map View
Sunburst View (5)

The sunburst view shows your entire installation in one circle diagram. The groups are
represented as inner circles, and all devices contained within a group are shown as 'cake slices'
attached to the outside of a circle element.
118 02.02.2015
PRTG Sunburst View
For both views:
Colors
A device (or group) element can have different colors, depending on the states of the
sensors running on this device or group (see Sensor St at es 123 ) 123 . A more severe status is
regarded more important and wins the color battle. For example, if a device currently has
sensors in the states Up (green), Paused (blue), and Warning (yellow), the according device
tile in this view would be yellow, indicating that at least one sensor on this device is in
Warning status. If there are any red Down sensors, the according device tile will turn red.
Following, all possible states in both views are listed ordered by their hierarchy:
02.02.2015 119
Flag Flag Color Object St at us Meaning
Red Down At least one sensor of this object shows a red

Down status. Hover an object's name to view
the total number of alarms concerning this
object.
Bright-Red Down At least one sensor of this object is Down and

(Acknowledged) the status was acknowledged by a PRTG user,
applying the Acknowledge Alarm function. The
Down states of all sensors of this object have
to be acknowledgedif at least one sensor is
unacknowledged down, this object will be
displayed as Down.
Yellow Warning At least one sensor of this object shows a

yellow Warning status. There is no sensor in a
Down or Down (Acknowledged) status
concerning this object.
Orange Unusual At least one sensor of this object shows an

orange Unusual status. There is no sensor in a
Down, Down (Acknowledged), or Warning
status concerning this object.
Green Up All sensors of this object are in a green Up

status. There is no sensor in a Down, Down
(Acknowledged), Warning, Paused, or Unusual
Blue Paused All sensors of this object show a blue Paused

(Acknowledged), Warning, Unusual, or Up
Black (Grey) Unknown All sensors of this object have an Unknown

(Acknowledged), Warning, Unusual, Paused, or
Up status concerning this object.
Size by Sensors / Size by Priorit y

You can adjust the size of the different squares. They can be calculated by the number of
sensors running on a device or within a group, or by the sensors' priority (see Priorit y and
Favorit es 161 ), or both. Use the check boxes in the page header bar (see the mark in the
tree map view screenshot) to change view immediately, then use the setting that suits best
for your needs.
120 02.02.2015
Page Content
The page content of the general layout varies dependent on the selected object. It shows
information about the current object and all other objects underneath in the tree hierarchy.
The deeper down in the hierarchy you select an object, the more detailed is the displayed
information.
By default, a Probe Device is created in the device tree on the local probe. It represents the
probe system running with your PRTG installation. PRTG automatically monitors the system
health of the core server and each probe in order to discover overloading situations that may
distort monitoring results. To monitor the system status of the probe computer, PRTG
automatically creates a few sensors. These include a Core/Probe Healt h Sensor, a WMI
sensor that measures disk usage, and a bandwidth sensor for all installed network cards. It is
recommended to keep these sensors, but you can optionally remove all except the Core/
Probe Healt h sensor. In a cluster installation, PRTG also creates a Clust er Probe Device with
a Clust er Probe Healt h Sensor 415 that monitors the cluster's system health.
You can add (or remove) a device or sensor to favorites by one click on the respective flag
displayed with an object (please see the marks in the screenshot below).
One-Clic k Fav orites in the Dev ie Tree
Another one-click option for adding/removing favorites or setting the priority for a selected
device or sensor is given in the page header bar 114 right to the object name (please see
screen number 1 in that subsection). Simply click on the flag for favorites or on a star for
priority.
One-Clic k Fav orite and Priority in the Page Header Bar
A black flag means that the respective object is a favorite already; clicking on the black flag will
remove the object from favorites. A gray flag indicates that it is not a favorite yet. Please see
also Priorit y and Favorit es 161 for this concern.
For more details about page contents, please see the following sections:
02.02.2015 121
Compare Sensors 132
Geo Maps 2516
More
Knowledge Base: How can I change the width of the devices and group "boxes" shown in the
PRTG 9 device tree?
122 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 4 Sensor States
5.4 Sensor States

In PRTG's device tree you usually create several sensors on each 'device 288 '. With sensors, you
can monitor different aspects of your devices. Using a simple color code, they always show
you what is going on in your network.
The color of a sensor always shows its current status. Following, you find a list of states a
sensor can show. This list also reflects the hierarchy of states whenever summarized sensor
states are shown (in the device tree 111 , or on geo maps 2516 ) : the higher a status is in the
hierarchy, the higher will be its priority in displaying sensor states. For example, if all the
sensors of a specific device are Up, but one of its sensors reached a Down status, then the
overall status of this device will be Down as well (for example, displayed red in the Tree Map
View 117 ), as this state is hierarchically higher.
Note: Down and Down (Part ial) states are hierarchically equal.
Sensor Color St at us Name Meaning
Red Down 1. PRTG is not able to reach the device or the

sensor has reached an error state. Please
see Sensor Warning and Down Behavior 124
below for more information. Note: By design,
a sensor does not record any data in its
channels while it shows this status.
2. Another reason for this status can be an
error limit that is set in the Sensor Channels
Set t ings 2477 , or an error status due to a
sensor Lookup 2838 . Note: In this case, the
sensor continues to record data in all sensor
channels although the sensor shows an
error.
Red/Green Down (Part ial) In a cluster, at least one node reports this
sensor as Down, while at least one other node
reports the same sensor as Up.
Bright-Red Down The sensor is Down and the status was

(Acknowledged) acknowledged by a PRTG user, applying the
Acknowledge Alarm function. This can be
helpful to mark that an alarm has already been
attended to. For acknowledged alarms no
more notifications 2521 are sent. To set this
sensor status, right-click on a sensor in a Down
status and from the context menu 165 , select
Acknowledge Alarm.... Then enter a comment
and click OK.
02.02.2015 123
Sensor Color St at us Name Meaning
Yellow Warning There was an error reading the sensor, but

PRTG will try again. The sensor may soon
change to a down status. Please see Sensor
Warning and Down Behavior 124 below for
more information. Another reason for this state
can be a warning limit set in a sensor's Sensor
Channels Set t ings 2477 .
Orange Unusual The sensor reports unusual values for this

weekday and time of day. The unusual
detection is based on the historic average data
and can be configured or disabled in the system
administration 2627 . You can also disable unusual
detection for certain groups only (see Group
Set t ings 286 ).
Green Up The last check was okay and the sensor

receives data.
Blue Paused The sensor is currently paused (for a certain

time or unlimitedly, or by dependency).
Black Unknown The sensor has not been checked yet by PRTG
(Gray) or there is an error in (network) communication,
likely on the probe system. If sensors show this
status persistently, a PRTG restart may be
necessary. For extended trouble shooting
Sensor Warning and Down Behavior

The Down status symbolizes that something is wrong with a monitored device. There can be
various reasons for a down status, for example, an interruption in the physical connection to
the device, an internet connection outage, or a crashed server.
After a failed request, PRTG tries to reach the device again before setting a sensor to Down
status (this is true for almost all types of sensors):
1. If a request to a device fails for the first time, the sensor is set to Warning status. PRTG
repeats the request and tries to re-scan the device immediately.
2. If also the second request fails, the sensor is set to Down status by default until the device
is reachable again. You can change this behavior in the Scanning Int erval 242 settings of any
monitoring object. PRTG tries to reach the device with every scanning interval.
This procedure gives devices and services the chance to recover from a momentary overload
and prevents false alarms. Still, you are informed promptly about any failures occurring.
124 02.02.2015
Note: The behavior described above does not apply to a Warning or Down status that is
activated due to a warning or error limit set in the Sensor Channels Set t ings 2477 .
More
Knowledge Base: What to check if sensors are black (gray)?
02.02.2015 125
Part 5: Ajax Web InterfaceBasic Procedures | 5 Review Monitoring Data
5.5 Review Monitoring Data

Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you can
navigate through various sub-pages of an object in order to show your network's status, view
monitoring results, or change settings.
Tabs Bar on Sensor Pages
Overview
The Overview tab shows an overview of the currently selected object and of its sensors. The
pages share a common layout, but include different elements, depending on the kind of object
you look at:
For probes and groups, the Overview tab shows a tree-like view with devices and sensors,
a Geo Map, as well as summary graphs for different time spans of the current probe or
group.
For devices, the Overview tab shows device details, a Geo Map, and summary graphs for
different time spans, colored gauges for high priority sensors, as well as a table list of all
sensors on this device. Additionally, you see a table list 157 with Recommended Sensors.
PRTG analyzes the devices which you add to PRTG and shows sensors that give you a much
more detailed picture about your devices when you add them. Click on Add Sensors to add
all recommended sensors 2628 of the corresponding table row. Click on Recommend Now to
manually start an analysis.
Note: You can turn off (and disable this table list) the sensor recommendation in Sy st em
Administ rat ionMonit oring 2628 .
Note: To display gauges, you have to tag corresponding sensors with 4 stars (****) or 5
stars (*****) in the priority settings 161 . 5 star sensors are represented with bigger gauges
than 4 star sensors.
For sensors, the Overview tab shows sensor details, current status, colored gauges, sensor
graphs for different time spans, a table with all sensor channels, as well as similar sensors 139
which show correlations in your network.
Gauges represent sensor values on Overview tabs of devices and channel values on
Overview tabs of sensors. They graphically illustrate the current values of a sensor or a
channel so you can use them as a quick status indicator. The red and yellow parts of gauges
correspond to the error and warning limits of the respective sensor channel settings 2477 .
Device overview tabs show gauges of high priority sensors, sensor overview tabs show
gauges of all sensor channels (except the Downt ime channel), the primary channel in
biggest size.
Note: For sensors using lookups 2838 , we recommend staying below 120 lookup values in the
primary channel to get expressive gauges. For sensors with a priority of 4 stars, the upper limit
is around 40 lookup values.
126 02.02.2015
Dev ic e Ov erv iew Tab with Gauges for High Priority Sensors, Sensors Table List, Geo Map,
and Mini Graphs
Toplists
Toplist s are available for xFlow and Packet Sniffer sensors 312 only. Toplist graphs are
displayed right on the sensor overview page. Please see section Toplist s 2498 .
Live Data and Data By x Days

Select one of the tabs Live Dat a (available for sensors only), 2 day s, 30 day s, or 365 day s to
display an object's monitoring data live (sensors only), or for different time spans and in more
or less detail.
Note: The days mentioned here is the default setting. You can change the shown days of the
different graphs under Sy st em Administ rat ionUser Int erface 2622 .
02.02.2015 127
2 Day s Tab of a Firewall with Ov erv iew Graph and Sensor Mini Graphs
Live Data and Data By x DaysProbes, Groups, and Devices

For probes, groups, and devices, each of the tabs shows a summary graph for the current
object and mini graphs for all sensors on this object, as well as a data table for the current
object. There are never more than 50 mini graphs displayed for performance reasons. Hover a
mini graph to see the graph legend.
The summary graph shows the number of alarms as well as three index graphs. These graphs
indicate response time, CPU usage, and bandwidth usage for all sensors. Index graphs are
similar to a stock index. The shown values are based on the readings of all sensors of this
object. PRTG computes these values using statistics and by comparing the values to the
highest and lowest readings ever recorded.
The three index graphs shows overall (or global) trends in your network. If these values
increase during a specific time frame, then CPU load, bandwidth load, or response time
respectively have worsened during this time. For example, a CPU Load Index value of 90%
means that the average CPU load for all CPU sensors of your current configuration is at 90% of
the highest ever measured CPU usage value.
The following four channels are available in the summary graph:
128 02.02.2015
Alarms: Sums up the number of all down states of sensors on this object during the given
time span. This graph provides you a bird's eye view of trouble in your network. It cannot be
hided.
Response Time Index: Indicates request times in your network.
CPU Load Index: Indicates the CPU usage in your network.
Traffic Index: Indicates the bandwidth usage in your network.
See section More 131 for a detailed description of the index graphs.
You can hide single channels individually except the "Alarms" channel. Simply remove the check
mark symbol in front of a channel name besides the graph, and the according channel's line will
disappear. You can also Show all or Hide all channels by clicking on the buttons underneath
the channel names. The graph view will be reset immediately.
Sensor Liv e Data Tab for a Traffic Sensor
Live Data and Data By x DaysSensors

For sensors, the tabs show a graph and data table of the selected sensor. When viewing data
of a sensor running on a cluster probe, you can additionally select if you want to show the
data of all nodes, or of one specific node only. Please use the Select Clust er Member bar
below the tabs.
02.02.2015 129
Note: Multi-node graphs are never displayed filled here, but with single lines only. However,
historic data reports can have filled multi-node graphs.
While viewing a sensor graph you can hide single sensor channels individually. Simply remove
the check mark symbol in front of a channel name underneath the graph, and the according
channel's line will disappear. You can also Show all or Hide all channels by clicking on the
buttons besides the channel names.
Live Data and Data By x DaysInteractive Graphs

On historic data tabs of sensors and in "zoomed graphs in new windows" (see below) of other
monitoring objects, graphs are interactive. You can zoom in and scroll along the time axis with
the corresponding buttons.
Graph Buttons
The following actions for graphs are available:
<< scrolls one graph window left and >> one window right. The scrolled time depends on
the graph you select, for example, 2 days on a 2 days graph.
< scrolls left on the time axis and > right. The scrolled time depends on the graph you select.
+ zooms into and - out of the graph. The shown time depends on the graph you select. For
example, you can zoom a 30 days graph so that it shows data for 6 days.
x resets the graph to the default view.
In the upper right corner of every graph, you see three small icons:
You can do the following with them:
Zoom graph in new window: Opens a larger version of the graph in a new browser window.
Download t he graph (PNG or SVG): Shows a PNG or SVG file of the graph in a new browser
window. You can then save or copy it for later use.
In every graph, you can also choose which channels (only on sensor pages) resp. indexes you
want to see in specific by using the corresponding check boxes or the Show all and Hide all
buttons.
Note: Warning or error limits 2478 are only shown in graphs (highlighted in yellow respectively
red) if you select exactly one channel with a limit.
130 02.02.2015
Historic Data
The Hist oric Dat a tab is available for sensors only. Please see section Hist oric Dat a Report s
135 .
Sensors Lists
Viewing lists of sensors is a great way to keep an eye on your network status because you
can select which kind of sensors you would like to see. There are many different sensor list
views available, such as a list of favorite sensors and top 10 lists, lists filtered by current
sensor status, value, availability, tag, or type, sensor cross reference, and many more.
Sensor lists are available from the main menu bar. Click the Sensors entry to show a table list
of all sensors. In the table list 157 appearing, you can re-sort the items by clicking on the
column's header items (see section Working wit h Table List s 157 ). Hover to show other menu
options. For detailed information about the available options, please see Main Menu
St ruct ure 183 (Sensors) section.
Alarms
The Alarms tab is not available for sensors, but for probes, groups, and devices only. Please
see section Alarms 145 .
Log
The logs tab shows past activities and events regarding the currently selected object. Please
see section Logs 148 .
Related Topics
Compare Sensors 132
More
Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time Index?
02.02.2015 131
Part 5: Ajax Web InterfaceBasic Procedures | 6 Compare Sensors
5.6 Compare Sensors

This function allows you to visually compare the graphs of two or more specific sensors. The
selected graphs are shown next to each other so you can have a look at all of them at the
same time.
To open the page to compare graphs of several sensors, from the main menu, choose Sensors
| Compare Sensors. Hover and select how many sensors you want to compare.
PRTG Main Menu: Compare

Sensors
Choose the number of sensors that you want to compare. This opens an assistant where you
can define your desired sensors and the time span the particular graphs cover.
132 02.02.2015
Compare Graphs of Two Sensors with 30 Day s Time Span
Compare Sensors Settings
OPTIONS
Time Span Specify the time span for which you want to show the graphs for.
Choose between:
2 day s
30 day s
365 day s
Dat a Comparison
Select the objects you want to show a graph for. Click on Please click here t o edit ! to open
the Object Select or 160 . There appear as many selection screens as you defined before.
02.02.2015 133
Selec t the Objec ts to be Compared
The graphs are shown immediately after object selection. You can now work with the
compared graphs like on the historic data tabs of sensors 129 : select the channels you want to
show and zoom and scroll in the graphs. Click on Select New Sensor to choose another
sensor for comparison.
Related Topics
If you want to create a sensor that combines the data of different other sensors, please see
the following sensor type:
Sensor Fact ory Sensor 1190
134 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 7 Historic Data Reports
5.7 Historic Data Reports

For quick reporting on monitoring data, use historic data reports as an alternative to the
exhaustive reports 2549 function. You can view a report of the historic data for each single
sensor, on demand. Additionally, you can also export this data and download it to your
computer for further processing in external applications.
There are two possibilities to call the function for historic data reports: Either you click on the
Hist oric Dat a tab on a sensor's detail page, or you choose Sensors | View Hist oric Dat a
from the main menu 183 .
Historic Data (Sensor Tab)

The Hist oric Dat a tab is available for sensors only (not for probes, groups, or devices). When
you call the historic data reports via this tab, there is no sensor selection available because
you already determined which sensor you want to create a report for. If you want to select
another sensor for the report, choose Sensors | View Hist oric Dat a from the main menu.
Historic Data Tab of Ping Sensor
02.02.2015 135
Historic Monitoring Data (Sensors Main Menu)

When you call historic data reports via the View Hist oric Dat a entry from the Sensors entry in
the main menu, you additionally have to choose the sensor you want to create a report for
with the Object Select or 160 .
Historic Monitoring Data Settings
SETTINGS
Sensor This field is only visible if you call the historic data function via the
main menu. Select the sensor you want to create the report for:
Click on the reading-glass symbol to open the object selector. For
more information, see section Object Select or 160 .
Start Specify the start date and time of the data you want to review. Use
the date time picker to enter the date and time.
End Specify the end date and time of the data you want to review. Use
the date time picker to enter the date and time.
Quick Range In this section you can use several buttons for a faster selection of
start and end dates. Click on any of these links to change the
St art and End values above. Choose between:
1 Day , 2 Day s, 7 Day s, or 14 Day s: Set the date range to the
respective day(s). The current time of the current day is the end
date.
Today , Yest erday , Last Week (Mo-Su), Last Week (Su-Sa), Last
Mont h, 2 Mont hs, 6 Mont hs, 12 Mont hs: Set the date range to
the last matching period. It starts at 00:00 and ends at 00:00 of
the particularly following day.
Average Interval With this option, you can activate and set up averaging. Select an
interval for which PRTG calculates the average value. You can
choose between No Int erval (no averaging is performed and only
raw data displayed), a few seconds, minutes, hours, or a whole day
(24 Hours). A smaller interval results in a more detailed report for
this sensor.
The best settings for you vary, depending on the scanning interval
of the sensor, the selected date period and, of course, the
intended use for the report. It might be useful to try different
settings to see what the results look like. Please also see the
section Aut omat ic Averaging 138 below.
136 02.02.2015
SETTINGS
Channels Select the channels you want to include in the report. You can
select or deselect single channels with the respective check
boxes, and select or deselect all channels with the buttons Show
all resp. Hide all. PRTG shows only the data of selected data in the
report.
Cluster Node This field is only visible if the sensor is running on a cluster probe.
Select the cluster node's data that PRTG uses for the report.
Choose between:
All nodes: Include the data of all cluster nodes in the report.
[Several specific nodes]: Use a specific node's data for the
report. The nodes you see are specific to your setup.
File Format Select the output format for the report. Choose between:
HTML web page: Display the result directly as HTML web page.
This is also a good option to check results before exporting to
another file format.
X ML file: Export the data as Extensible Markup Language (XML)
file. Usually, you browser shows a download dialog when you
use this option.
CSV file: Export the data as Comma Seperated Values (CSV) file,
for example, for import into Microsoft Excel. Usually, you
browser shows a download dialog when you use this option.
INCLU DE PER CENTILES
Percentile Results Select if PRTG shows percentiles in the report. Choose between:
Do not show percent iles: PRTG does not calculate percentiles.
Show percent iles: Enable percentiles in the report. In the
overview table, PRTG displays additional values with averages/
sums for each sensor channel. Define additional settings below.
For more information about percentiles, please see section
Calculat ing Percent iles 2875 .
Percentile This field is only visible if you enable percentile results above. Enter
which percentile you want to calculate. Please enter an integer
value.
02.02.2015 137
INCLU DE PER CENTILES
Percentile Average This field is only visible if you enable percentile results above. Enter
the averaging interval in seconds that is used for percentile
calculation. Please enter an integer value.
Percentile Mode This field is only visible if you enable percentile results above.
Choose between:
Discret e: Chooses the next smaller discrete value.
Cont inuous: Interpolates between discrete values.
See section Calculat ing Percent iles 2875 for more information
about the discrete and continuous modes.
Click on St art to start the generation of a historic data report. Note: Data reporting is limited
to 5 requests per minute.
Automatic Averaging
For performance reasons, PRTG automatically averages monitoring data when calculating data
for large time spans. Data is then averaged regardless of the selected average interval.
TIME SPAN IN R EPOR T MINIMU M LEVEL OF DETAIL (AVER AGE

INTER VAL)
Up to 40 days Any
40 to 500 days 60 minutes/1 hour or larger
A report for a time span of more than 500 days is not possible. If you try to set a larger time
span, it will be reduced to 365 days automatically.
Related Topics
Report s 2549
More
Knowledge Base: Why is there missing data in historical data reports?
138 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 8 Similar Sensors
5.8 Similar Sensors

With PRTG you can detect relationships between different components in your network. This
function is called similar sensors analysis, a heuristic calculation showing similar behavior of
your sensors. The analysis is completely automated and sensor type agnostic. It is based on
mathematics and fuzzy logic. This feature helps you find interconnections in your network you
were not aware of and optimizes your sensor usage by tracking redundant monitoring of
some aspects of your system.
You can adjust the depth of similar sensors analysis or turn it off in Sy st em Administ rat ion
Monit oring 2627 . You can also switch on and off the similarity analysis for specific probes,
groups, and devices and specify inheritance 88 in the respective object settings 143 , section
Aut omat ic Monit oring Analy sis.
There are two possibilities to view similar sensors:
The overview page of sensors contains a similar sensors section. PRTG lists channels there
which show similarities to channels of the current sensor.
In addition, you can call a similar sensors overview page via Sensors | Similar Sensors
Overview from the main menu 183 .
Similar Sensors (Sensor Overview Tab)

On the overview tab of a sensor, PRTG lists channels which show similarities to channels of the
currently selected sensor. The table is empty if PRTG detects no similarities regarding the
selected sensor.
Note: PRTG only shows similar sensors here when channels have at least 85% similarity.
Furthermore, the analysis saves up to 15 entries per sensor at most.
02.02.2015 139
Similar Sensors Sec tion on a Sensor's Ov erv iew Tab
The similar sensors section provides the following information:
SIMILAR SENSOR S
Similarity Shows a measurement of similarity between two channels in

percent.
Channel Shows a channel of the currently selected sensor.
Similar Channel Shows a channel of another sensor similar to a channel of the

currently selected sensor (the one in the "Channel" column in the
same row).
Note: PRTG does not show the similar sensors section when the analysis is off or you have
exceeded 1,000 sensor and selected the automatic analysis depth option 2627 . You see an
according notice in this case.
140 02.02.2015
Similar Sensors Overview (Sensors Menu)

This page shows the results of the similar sensors analysis from the entire monitoring
database. PRTG lists all channels with similarities to another one here. On the table top, you
have several filter options to display similar sensors as you need it. Choose the object of
interest, the degree of similarity, and if you want to display back references. For more details,
see also section Working wit h Table List s 157 .
Note: PRTG only shows similar sensors here when channels have at least 85% similarity.
Furthermore, the analysis saves up to 15 entries per sensor at most.
Similar Sensors Ov erv iew
You can sort the list by clicking on the column headers. The similar sensors overview page
provides the following information:
SIMILAR SENSOR S OVER VIEW
Original Channel Shows channels to which other channels are compared. Click on
the column header to sort the list according to the order on the
device tree in ascending or descending order.
Similarity Shows a measurement of similarity between two channels in

percent. Click on the column header to sort the list according to
the similarities in ascending or descending order.
02.02.2015 141
SIMILAR SENSOR S OVER VIEW
Similar Channel Shows a channel compared to the original channel. Click on the
column header to sort the list according to the order on the
device tree in ascending or descending order.
Item Count Define how many channel similarities are shown on this page.
Choose between 50, 100, or 500.
Note: PRTG does not show the similar sensors overview option in the main menu if you turned
off the analysis or if you have exceeded 1,000 sensors and selected the automatic analysis
depth option.
142 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 9 Object Settings
5.9 Object Settings

Device Tree Management

The Management tab is available when viewing probes or groups. After clicking this tab you
can move devices and sensors right within the tree view. If moving is not possible, the web
interface will start a clone process automatically.
For more information, please see Manage Device Tree 230 section.
General Settings
In the Set t ings tab you can define all settings of the current object. The available options vary,
depending on the kind of object you're changing. Please see the following sections for
information about the respective object types:
Root Group Set t ings 232
Probe Set t ings 248 Neuer Link 96
Group Set t ings 266
Device Set t ings 288
Sensor Set t ings 310
Note: The available setting options are different for each sensor, but always the same for
probes, groups, and devices. Sensor Channels Set t ings 2477 are not reachable via tab but
directly on a sensor's overview page via channel gauges and the channels table.
Notifications Settings
In the Not ificat ions tab, notification triggers can be set for every object. When using these
settings for a probe, group, or device, they will be inherited to all sensors on these objects.
Available notification trigger options are the same for all objects.
For more information, please see Sensor Not ificat ions Set t ings 2484 section.
Comments
In the Comment s tab you can enter free text for each object. This can be used for
documentation purposes or to leave information for other users.
02.02.2015 143
Part 5: Ajax Web InterfaceBasic Procedures | 9 Object Settings
History
In the Hist ory tab all changes in the settings of an object are logged with a timestamp, the
PRTG user which conducted the change, and a message. The history log keeps the last 100
entries.
Note: On some pages, you can access the history of subordinate objects via the according
context button in the page header bar 114 . This includes Sy st em Administ rat ion 2616 and the
overview pages of User Account s 2644 , User Groups 2649 , Report s 2549 , Libraries 2533 , and Maps
2569 . See section Logs (Main Menu) 148 for details.
Related Topics
General Lay out 110
Toplist s 2498
144 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 10 Alarms
5.10 Alarms
The alarms list shows all sensors that are currently in a Down, Down (Part ial), Down
(Acknowledged), Warning, or Unusual status. Sensors in other states (for example, Up,
Paused, or Unknown) do not appear here. This is useful to keep track of all irregularities in
your network.
In the table list, you can re-sort the items by clicking on the column's header items.
Alarms List
There are two possibilities to call the alarms list: Either you click on the Alarms tab on the
detail page of a probe, group, or device (not available for sensors), or you choose the Alarms
entry in the main menu.
Alarms (Object Tab)

Tabs Bar on Group and Probe Lev el
On an object's detail view, click on the Alarms tab to show a table list of all sensors on this
object that currently show a Down, Down (Part ial), Warning, or Unusual status. You will see a
subset of sensors in an alarm state for the current object only. This is a subset of the entries
available via the Alarms | All option in main menu 186 . The tab is not available on a sensor's
detail page.
02.02.2015 145
Alarms (Main Menu)

Click the Alarms entry from the main menu 186 to show a table list of all sensors in your
configuration that currently show a Down, Down (Part ial), Down (Acknowledged), Warning,
or Unusual status. You can also show these sensors as gauges. Hover the Alarms entry and
select another option to only show a subset of sensors in certain states. Choose between:
ALAR MS
All Open a list of all sensors which are currently in Down, Down
(Part ial), Down (Acknowledged), Warning, or Unusual status 123 .
Show as Gauges Open a page with the gauges of all sensors which are currently in
Down, Down (Part ial), Down (Acknowledged), Warning, or
Unusual status. The size of the sensor gauges corresponds to
their respective priority.
Errors Only Open a list of all sensors which are currently in Down, Down
(Part ial), or Down (Acknowledged) status.
Warnings Only Open a list of all sensors which are currently in Warning status.
Unusuals Only Open a list of all sensors which are currently in Unusual status.
Acknowledge Alarm
An acknowledged alarm shows up in the alarms list as "acknowledged" (see Sensor St at es 123 )
and will not trigger 2484 any more notifications 2521 . Note: If the alarm condition clears, the sensor
usually returns into an Up status immediately with the next sensor scan.
To acknowledge an alarm, right-click on a sensor and choose Acknowledge Alarm... from the
context menu, enter a message and click the OK button. The message will appear in the last
message value of the sensor. You can choose between: Acknowledge Indefinit ely ...,
acknowledge For 5 Minut es..., For 15 Minut es..., For 1 Hour..., For 3 Hours..., For 1 Day ...,
or Unt il....
If you choose Unt il... a dialog box appears:
ACKNOWLEDGE ALAR M U NTIL
Selected Objects Shows the sensor(s) for which you want to acknowledge the
alarm. You can acknowledge alarms for more than one sensor
using multi-edit 2506 .
146 02.02.2015
ACKNOWLEDGE ALAR M U NTIL
Message Enter a text, for example, the reason why you acknowledge the
alarm. Please enter a string or leave the field empty.
Until Enter the date when the acknowledge status will end. Use the date
time picker to enter the date and time.
Note: If the alarm condition still persists after the specified date,
the sensor will show a Down status again.
Only users 2644 with write access rights may acknowledge alarms. You can give read-only users
the right to acknowledge alarms, too. See section User Account s Set t ings 2644 , section
Account Cont rol.
More
Knowledge Base: Which audible notifications are available in PRTG? Can I change the default
sound?
02.02.2015 147
Part 5: Ajax Web InterfaceBasic Procedures | 11 Logs
5.11 Logs
The Logs list shows all past activities and events of your PRTG monitoring setup. This is useful
to keep track of all important activities and, for example, to check whether messages were
sent, etc. In a typical setup, a huge amount of data is produced here. As the activity of every
single object is minuted, you can use this data to check exactly if your setup works as
expected.
To support you when viewing the log files, there are several filters available. Please see
Working wit h Table List s 157 section for more information.
List with Log Entries
There are two possibilities to call the logs list: Either you click on the Log tab on the detail
page of a probe, group, device, or sensor, or you choose the Logs entry in the main menu.
Log (Object Tab)

Tabs Bar on Group and Probe Lev el
On an object's detail view, click on the Log tab to show a table list with all log information on
this object. This is a more detailed log than the system log available via the Logs | All option in
main menu 188 .
Logs (Main Menu)

Click the Logs entry from the main menu 188 to show a table list of all system log entries in
your configuration. Hover the Logs entry and select another option to only show a subset of
entries for certain objects for certain kind of entries. Choose between:
148 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 11 Logs
LOGS
All Open a table list 157 with log information for all objects in your
configuration, newest first.
By Group Open a list with log information for objects in a certain group only,
newest first. Hover to show other menu items. Select All, or follow
the menu path (it is specific to your setup) to select a group you
would like to show log information for.
St at us Changes Open a list with log information for certain status changes only.
Hover to show other menu items. Follow the menu path to view
log entries with a special value in the St at us field only. Select
between Up & Down (shows entries with either Up or Down in
the St at us field), Down, Warning, Unusual, Up, Paused/Resumed
(shows entries with either Paused or Resumed in the St at us field),
or Acknowledged Alarms.
Sy st em Event s Open a list with log information regarding certain system event
types only. Hover to show other menu items. Select between the
following event types: Probe Relat ed, Clust er Relat ed, Aut o-
Discovery , Not ificat ions, or St at us Messages.
Object Hist ory Open a list with log information about changes to the PRTG setup
and deletions of subordinate system objects. The object history
page has a tab-like interface. Using the tabs you can navigate
through various sub-pages in order to view the changes to all
related settings and deletions of objects. Select between the
following tabs: My Account , Sy st em Set up, Not ificat ions,
Schedules, User Account s, User Groups, Report s, Libraries, or
Maps.
Note: You can open a specific tab directly with the context button
Hist ory in the page header bar 114 on the corresponding pages.
02.02.2015 149
Part 5: Ajax Web InterfaceBasic Procedures | 12 Tickets
5.12 Tickets
PRTG Network Monitor includes its own ticket system. With tickets you can manage and
maintain various issues which may appear while monitoring a network. A ticket in PRTG
contains information about recent events in your PRTG installation which need a closer look by
the administrator or another responsible person. You can see each ticket as a task for a
particular PRTG user.
Each monitoring related task has a lifecycle in the ticket system. PRTG itself can create tickets,
for example, when Aut o-Discovery 198 has finished, as well as PRTG users can create tickets
for every kind of issue. In addition, you can set up notifications which open a ticket when
something uncommon occurs in your network. The task gets alive when a ticket is created.
Responsible PRTG users then take care of this issue. Once the issue has been resolved, the
ticket can be closed and the lifecycle of the task ends.
Every ticket has a unique ID, a priority, and a status, and you can take several actions on each
ticket. You should view every ticket and conduct a corresponding action. This way, you always
keep an overview about each task and its history in your PRTG installation.
PRTG can also send an email to you whenever there is a ticket assigned to you or one of your
tickets has been changed. See section Ticket s as Emails 154 for details and how to turn off
emails about tickets.
List of Tic kets
150 02.02.2015
Note: You can turn off the tickets system for particular user groups in Sy st em Administ rat ion
User Groups 2649 except for the PRTG Administrators group. The users in the admin group will
not receive new ToDo tickets (and notifications about changes) by default but only the PRTG
System Administrator user. You cannot change this behavior. However, you can turn off ticket
emails 154 for every user account.
Types of Tickets
New tickets are created in the following cases:
New devices or sensors have been created by the auto-discovery process. Note: In the
corresponding ticket, only device templates will be listed through which PRTG created
sensors.
A new probe connects to the core and must be acknowledged.
A new cluster node connects to the cluster and must be acknowledged.
A new version of the software is available.
A new report is ready for review.
In a few other situations, such as when the system runs out of disk space, for licensing
issues, when an error occurred, etc.
A notification 2521 opened a ticket if set in the notification settings.
A user opened a ticket.
Overall, there are three types of tickets:
User Ticket s: Tickets created by PRTG users, for example, to assign monitoring related tasks
to a particular PRTG user (or user group)
ToDo Ticket s: Tickets created by PRTG to show important system information and in case of
specific system events. They are assigned to the PRTG System Administrator user and cannot
be turned off.
Note: The Relat ed Object of ToDo tickets is Sy st em.
Not ificat ion Ticket s: Tickets created via Not ificat ions 2521 in case of monitoring alerts
States of Tickets
Tickets can have three different states depending on the working process regarding the
corresponding issue:
Open: New tickets will be open as long as the corresponding issue exists as described in
the ticket.
Resolved: The issue as described in the ticket does not persist any longer. Someone took
care of it.
Closed: Usually, the ticket has been resolved before, the solution to the issue has been
checked for correctness, and the ticket does not require any other action.
02.02.2015 151
Tickets (Main Menu)

Note: This option is only shown in the main menu bar if the user group of the current user is
allowed to use the ticket system. You can turn off tickets for particular user groups in Sy st em
Administ rat ionUser Groups 2649 . Users with read-only rights are always excluded from the
ticket system and cannot see the tickets entry in the main menu bar.
You have several options to display a list of tickets which is filtered to your needs. In the main
menu bar 179 , hover on Ticket s to show all available filter options or click directly to show all
tickets assigned to the current user. You can also create a new ticket via the main menu.
Available options are:
My Ticket s
Click to show all open tickets which are assigned to the current user. Hover to show other
menu items for filtering these tickets depending on their status:
Open
Resolved
Closed
All
All Ticket s
Click to show all open tickets of all PRTG users. Hover to show other menu items for filtering
these tickets depending on their status:
Open
Resolved
Closed
All
ToDo Ticket s
Click to show all open tickets from the type 151 ToDo. Hover to show other menu items for
filtering these tickets depending on their status:
Open
Click to show all open ToDo tickets. Hover to show other menu items for filtering these
tickets depending on their event type:
Report Relat ed
Aut o-Discovery Relat ed
Probe Relat ed
Sy st em Errors
New Soft ware Version
Resolved
Closed
152 02.02.2015
All
Open Ticket
This will open the New Ticket dialog. In the first step, select the object on which you want
to focus in the ticket via the Object Select or 160 . Click on Cont inue. Note: You can leave
this step out when using the context menu 165 of this object in the device tree to open the
ticket.
In step 2, provide the following information and confirm by clicking on Save to create a User
Ticket:
Subject : Enter a meaningful title for the ticket which indicates the topic of the issue.
Assigned t o: Select a user (or user group) who will be responsible for this issue from the
drop down list.
Priorit y : Define a priority 161 from one to five stars.
Comment s: Enter a text message. This message should describe the issue in detail.
After selecting the desired filter or opening a new user ticket, a corresponding list of tickets
will appear. In this table list, you can re-sort the items by using the respective options 157 .
Additionally, you have several search options using the inline filter directly above the table. The
following filters are available:
Ticket st at us: all, open, resolved, closed

Ticket t y pe: User, ToDo, Notification
Concerned user(s): Show only tickets which are assigned to a specific user or user group.
There are the following types:
any one: no user filter is applied so all tickets on this PRTG server are shown
me: show tickets which are assigned to you (the user who is currently logged in)
Groups: show tickets which are assigned to a specific user group only
Users: show tickets which are assigned to a specific user only

Disallowed: users or user groups which do not have access rights to the selected object
are displayed under Disallowed. This for your information only; you cannot select them!
Relat ionship to a monitoring object: Choose groups, probes, devices, sensors with the
Object Select or 160 .
Note: ToDo tickets are related to Sy st em.
Time span to view tickets by last edit of a ticket: Use the date time picker to enter the date
and time.
Click on the subject of a ticket to open the ticket's detail page. There you can find all related
information, as well as you can conduct several actions.
02.02.2015 153
An Open ToDo Tic ket with Instruc tions
Actions
For best experience with PRTG, check every ticket and select appropriate actions. Note: Only
members of user groups which have the corresponding access rights 96 can view and edit to
tickets which are related to a certain monitoring object.
The following actions are available when viewing the tickets list or a specific ticket:
Edit : Opens a dialog where you can change the subject and the priority of the ticket, as well
as you can assign the ticket to another user. Furthermore, you can add a text message to
this ticket. Confirm your changes by clicking on Save.
Assign: Opens a dialog in which you can give the ticket to another user. Select a user (or
user group) via the drop down menu. Furthermore, you can add a text message to this
ticket. Confirm your assignment by clicking on Save.
Resolve: Opens a dialog where you can resolve the ticket by clicking on Save. The status
resolved indicates that the issue as described in this ticket does not persist. Furthermore,
you can add a text message to this ticket which indicates, for example, what has been done
concerning the issue.
Close: Opens a dialog where you can close the ticket by clicking on Save. Usually, this ticket
has been resolved before and the correct solution of the issue has been checked.
Furthermore, you can add a text message to this ticket.
Reopen: Opens a dialog where you can reopen a ticket after it has been resolved or closed.
Do so, for example, if the solution of the issue turned out to be incorrect. Furthermore, you
can add a text message to this ticket which indicates, for example, why you have opened
the ticket again. Confirm reopening and assignment by clicking on Save.
Tickets as Emails
You can receive all tickets which are assigned to you or to your user group as emails. You will
be also notified each time this ticket is edited via email. This way, you will keep always
informed about new notifications (if set), important system information (if PRTG System
Administrator), or within the communication with other PRTG users. You can turn off the
setting Ticket s as Emails in Sy st em Administ rat ionUser Account s 2644 . If you disable
emails for tickets for a user account, this particular user will not receive any ticket emails
anymore.
154 02.02.2015
Note: If you have defined to get tickets as emails and you are PRTG System Administrator, you
will receive emails for ToDo tickets as well, although ToDo tickets are considered to be
opened by the PRTG System Administrator.
More
Paessler Blog: A New Feature Was Assigned to You in PRTG: Ticket System Keeps Track of
Network Monitoring Issues
http://www.paessler.com/blog/2014/02/03/prtg/ticket-system-keeps-track-of-network-
monitoring-issues
Ajax Web InterfaceBasic ProceduresTopics

Login 104
SSL Cert ificat e Warning 107
General Lay out 110
Sensor St at es 123
Compare Sensors 132
Similar Sensors 139
Alarms 145
Logs 148
Ticket s 150
Working wit h Table List s 157
Object Select or 160
Priorit y and Favorit es 161
Pause 164
Cont ext Menus 165
Hover Popup 178
Main Menu St ruct ure 179
02.02.2015 155

Ajax Web Int erfaceDevice and Sensor Set up 196
Related Topics
156 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 13 Working with Table Lists
5.13 Working with Table Lists

Throughout the web interface often you see table lists of items, for example, sensor or device
lists. Table lists are also available in the overview pages of Libraries 2533 , Maps 2569 , Report s 2549 ,
Not ificat ions 2521 , and Schedules 2612 , as well as in Logs 148 and Ticket s 150 . All these provide
common functionality. Depending on the type of content in the list, tables show various
information in their columns for each object.
On certain overview pages, such as for sensors 183 , tickets 152 , and similar sensors 141 , there is
also an inline filter available directly above the table. The filter options depend on the current
page.
Example of a Table List
02.02.2015 157
FE DISPLAY WHAT IT DOES

AT
U
RE
Pa The content of a table

gin is displayed on several
g pages. Click on the
arrow symbols at the
beginning or the end
of a list to view other
pages, or to jump to
the beginning or the
end of the list.
Ne Click on the window

w symbol at the
Wi beginning or the end
nd of a list to open the
ow table in a new
window.
Da Use the date time

te picker to show table
Ra list entries within a
ng specific time span
e only. Click on the first
date field for the start
date and on the
second field for the
end date. A calender
dialog opens where
you can particularly
select date and time.
Click on the Done
button to apply the
selected date and
time.
Sel When viewing log lists

ect (not available in other
Ra lists), hover the
ng Select Range option
e at the upper right
corner of the list to
select the time span
you want to show log
entries for. Choose
between Today ,
Yest erday , and
several other time
spans. Choose
Unlimit ed to disable
this filter again.
158 02.02.2015
Ite Hover the It ems

ms option at the
Related Topics
Mult i-Edit List s 2506
02.02.2015 159
Part 5: Ajax Web InterfaceBasic Procedures | 14 Object Selector
5.14 Object Selector

For some functions, the object selector is shown. It enables you to browse all objects in your
configuration and select an object in two steps.
Objec t Selec tor
Step 1: Navigate Device Tree

On the left hand side, you see a device tree specific to your setup that you can browse by
clicking on the corresponding nodes. Click on a device to view its sensors on the right hand
side.
You can directly browse for objects in the device tree by entering a probe name, group name,
or device name into the Search... field above the device tree navigation. You can also use a
substring only. The resulting objects will be displayed immediately without any manual
confirmation.
Step 2: Select an Object

If you have selected a device on the left hand side, you will see the sensors on this device
here, on the right hand side. Also, the sensor type is shown. Hover a sensor on the right side
to view its parent device and group.
You can also directly search and find sensors by entering its sensor name, group name, device
name, or tag into the Find... box above the sensor list.
Select an object and click on the Save button.
160 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 15 Priority and Favorites
5.15 Priority and Favorites

You can set priorities for all objects in your setup as well as categorize devices or sensors as
favorites. Both settings affect how your objects are displayed.
Note: Settings for priority and favorites are stored for the entire installation; they are not user
specific.
Priority for All Objects

The priority setting affects in which order your objects are displayed when you view table lists.
PRTG lists objects with a higher priority first, others underneath, depending on their own
priority. Furthermore, device overview pages display gauges 126 for sensors with a high
priority.
To change priority settings, right-click an object to open the context menu 165 and select
Priorit y . You can choose between 5 stars ***** (top priority) and one star * (lowest priority).
By default, all objects are set to medium priority (3 stars ***). In the page header bar and in
lists, you can set a priority directly by one click on a star, for example, for sensors on a device
overview page.
Context Menu: Priority
Note: Select 4 or 5 stars for particular sensors to activate their gauges on device overview
pages.
Favorites for Devices and Sensors

To call a list of all your favorite devices or sensors, select Devices | Favorit e Devices or
Sensors | Favorit e Sensors from the main menu. These lists are sorted by priority as well.
You can mark any device or sensor as favorite to add it to the favorite list. Right click on it to
open the context menu 165 . Select Priorit y /Favorit e | Add t o Favorit es. A small black flag
symbol will be added next to the object's name.
02.02.2015 161
Context Menu:
Priority /Fav orites (Add)
To remove an object from the favorites list, select Priorit y /Favorit e | Remove from
Favorit es from the context menu 165 .
Context Menu:
Priority /Fav orites (Remov e)
There is also the option to add a device or sensor to favorites by one click in the device tree.
Just click on the small flag symbol right to the respective object name for this concern. If the
flag is black, the specific object is already a favorite; clicking anew on the flag will remove it
from favorites and the flag will turn gray again.
One-Clic k Adding to Fav orites in the Dev ic e Tree
162 02.02.2015
Priority and Favorites in the Page Header Bar

You can add any device or sensor to favorites on its respective details page by clicking on the
small flag symbol in the page header bar 114 . If the flag is black, the selected object is already a
favorite; clicking anew on the flag will remove it from favorites and the flag will turn gray again.
It is also possible to set the priority of the object by a click on one of the five stars in the page
header; five stars ***** means top priority, one star * is the lowest priority.
One-Clic k Fav orite and Priority in the Page Header Bar
02.02.2015 163
Part 5: Ajax Web InterfaceBasic Procedures | 16 Pause
5.16 Pause
While a sensor is paused, it will not collect any monitoring data, will not change its status 123 ,
and will not trigger any notifications 94 . You can pause monitoring for every object by
selecting Pause from the context menu 165 of a probe, a group, a device, or a sensor. All
sensors on this object will then be paused. You can choose Pause Indefinit ely , or select a
time after which monitoring will be resumed automatically, such as 5 or 15 minut es, 1 or 3
hours, 1 day , or Unt il a certain date. You can also set up a one-time maintenance window to
pause sensors automatically at a specified time.
Note: When selecting the Pause symbol from an object's hover popup 178 or while using multi-
edit 2506 , the object(s) will be paused indefinitely until resumed.
When selecting a pause option, you are prompted to enter a message. This will be shown in
the status message of the object as long as it is paused. Confirm with OK to pause the object;
click Cancel to not pause it.
PRTG Pause Message Prompt
Note: Monitoring for objects can also be paused by applying a schedule (see Account
Set t ingsSchedules 2612 ) in the Object Set t ings 143 .
Inheritance and Resume

If you pause monitoring for an object in the device tree 110 , all child objects underneath will be
paused as well. For example, when pausing a group, all sensors on all devices in it will also be
paused. Once an object is paused, you can resume monitoring any time by selecting Resume
from the context menu 165 . However, you cannot resume monitoring for single child objects
that are paused by a parent object, but only for the object you originally set to pause. Note:
Also after a restart of PRTG, a pause status will be kept.
164 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 17 Context Menus
5.17 Context Menus

Right-click on an object to view a context menu with many options for direct access to
monitoring data and functions. You can also access many of the functionalities via the main
menu 179 or the hover popup 178 window. However, using the context menus is the easier way
in most cases.
Note: To view your browser's context menu, hold down the Ctrl key (Chrome) or the Shift key
(Firefox) while right-clicking. You will then see the menu of your browser instead of the PRTG
menu. This is not possible with Internet Explorer.
The content of the PRTG context menu varies, depending on the type of object you have
selected. Please see the following sub sections for an overview of the available options.
Probe Cont ext Menu 165
Group Cont ext Menu 169
Device Cont ext Menu 171
Sensor Cont ext Menu 175
Probe Context Menu

The Probe Menu contains actions for your local probe, remote probes, or mini probes 84 .
Probe Context Menu
02.02.2015 165
PR OBE MENU
Check Now Perform an immediate scan for the selected probe. This queries the
data for all devices and sensors underneath in the object hierarchy
83 .
Det ails... Show the overview tab 126 of the selected probe.
Edit Hover to show the Edit menu.
Edit Menu
The following actions are available:

Set t ings...
Open the Probe Set t ings 248 tab of this probe.
Not ificat ions...
Open the Not ificat ions 2521 tab of this probe.
Access Right s...
Open an assistant to edit User Access Right s 96 for this
probe.
Rename...
Open an assistant to edit the name of this probe.
Management ...
Open the Management 230 tab of this probe.
Add Group... Open an assistant which guides you through the process of adding
a new group to the selected probe. For detailed instructions,
please see Add a Group 213 .
Add Aut o-Discovery Open an assistant which guides you through the process of adding
Group... a new auto-discovery group to the selected probe. PRTG creates a
new group and runs an auto-discovery in your network to add
devices and sensors automatically. For more information, please
see section Using t he Aut o-Discovery 198 .
Add Device... Open an assistant which guides you through adding a new device
to the selected probe. For detailed instructions, please see Add a
Device 219 .
166 02.02.2015
PR OBE MENU
Sort Alphabet ically Sort direct children (groups and devices) of the selected probe in
alphabetical order.
Note: The ordering is stored in the monitoring configuration and
cannot be revoked.
Delet e... Delete the selected probe. PRTG will ask for confirmation before
anything is actually deleted.
Move Hover to open the Move menu.
Mov e Menu

Top: Move the probe to the top of the root group.
Up: Move the probe one entry up under the root group.
Down: Move the probe one entry down under the root group.
Bot t om: Move the probe to the bottom of the root group.
Management ...: Open the Management 230 tab of the probe.
Pause Hover to open the Pause menu.

or If the probe is already in paused status, Resume appears. Click to
restart monitoring on this probe.
Resume
Pause Menu
02.02.2015 167
PR OBE MENU
You can pause and resume monitoring on the selected probe. The
monitoring for all sensors in the object hierarchy 83 underneath
will be paused resp. resumed.
You can choose between: Pause Indefinit ely ..., pause For 5
Minut es..., For 15 Minut es..., For 1 Hour..., For 3 Hours..., For 1
Day ..., or Pause Unt il.... If you choose Pause Unt il..., an assistant
appears where you can define a date. Use the date time picker to
enter the date and time. PRTG will resume monitoring after this
date.
You can directly add a One-t ime maint enance window to pause
monitoring during a planned downtime. In the appearing assistant,
define the start and end date of the maintenance window for this
probe. Use the date time picker to enter the date and time.
Priorit y Hover to open the Priorit y menu.
Context Menu Priority
Define the priority of the selected probe. For details, please see
Priorit y and Favorit es 161 .
Hist oric Dat a Hover to open the Hist oric Dat a menu.
Context Menu Historic

Data

Open the historic data report tabs for the specified interval 128 :
Last 2 day s..., Last 30 day s..., or Last 365 day s...
Creat e Report ...: Open an assistant to add a new report to
PRTG. For details, please see Report s St ep by St ep 2553 .
168 02.02.2015
PR OBE MENU
Send Link by Email Send the link to the selected probe by email. Click to create a new
email using your system's standard email client. It contains a direct
link to the overview tab 126 of the selected probe.
Open Ticket Open the New Ticket dialog. For details, please see section
Ticket s 153 .
Group Context Menu

The Group Menu contains actions for your groups 84 .
Note: The context menu of the Root group is special and differs from the other groups' menu.
GR OU P MENU
Check Now Perform an immediate scan for the selected group. This queries the
data for all devices and sensors underneath in the object hierarchy
83 .
Det ails... Show the overview tab 126 of the selected group.
Edit Hover to show the Edit menu. The following actions are available:
Set t ings...
Open the Group Set t ings 266 tab of this group.
Not ificat ions...
Open the Not ificat ions 2521 tab of this group.
Access Right s...
group.
Rename...
Open an assistant to edit the name of this group.
Management ...
Open the Management 230 tab of this group.
Add Group... Open an assistant which guides you through the process of adding
a new group to the selected group. For detailed instructions,
please see Add a Group 213 .
02.02.2015 169
GR OU P MENU
Add Aut o-Discovery Open an assistant which guides you through the process of adding
Group... a new auto-discovery group to the selected group. PRTG creates a
new group and runs an auto-discovery in your network to add
devices and sensors automatically. For more information, please
see section Using t he Aut o-Discovery 198 .
Add Device... Open an assistant which guides you through adding a new device
to the selected group. For detailed instructions, please see Add a
Device 219 .
Sort Alphabet ically Sort direct children (groups and devices) of the selected group in
alphabetical order.
cannot be revoked.
Delet e... Delete the selected group. PRTG will ask for confirmation before
Clone... Open an assistant which guides you through cloning the selected
group. For detailed instructions, please see Clone Object 2504 .
Move Hover to open the Move menu. The following actions are available:
Top: Move the group to the top of the mother node (here
usually a probe or another group).
Up: Move the group one entry up under the mother node.
Down: Move the group one entry down under the mother
node.
Bot t om: Move the group to the bottom of the mother node.
To Ot her Group...: Move the group to another group to
become a sub-group.
Management ...: Open the Management 230 tab of the group.

or If the group is already in paused status, Resume appears. Click to
restart monitoring on this group.
Resume
You can pause and resume monitoring on the selected group. The
monitoring for all sensors in the object hierarchy 83 underneath
will be paused resp. resumed.
170 02.02.2015
GR OU P MENU
date.
group. Use the date time picker to enter the date and time.
Priorit y Hover to open the Priorit y menu. Define the priority of the
selected group. For details, please see Priorit y and Favorit es 161 .
Hist oric Dat a Hover to open the Hist oric Dat a menu. The following actions are
available:
Send Link by Email Send the link to the selected group by email. Click to create a new
link to the overview tab 126 of the selected group.
Ticket s 153 .
Device Context Menu

The Device Menu contains actions for your devices 85 .
DEVICE MENU
Check Now Perform an immediate scan for the selected device. This queries
the data for all sensors underneath in the object hierarchy 83 .
Det ails... Show the overview tab 126 of the selected device.
02.02.2015 171
DEVICE MENU
Set t ings...
Open the Device Set t ings 288 tab of this device.
Not ificat ions...
Open the Not ificat ions 2521 tab of this device.
Access Right s...
device.
Rename...
Open an assistant to edit the name of this device. You can also
select another device icon.
Add Sensor... Open an assistant which guides you through adding a new sensor
to the selected device. For detailed instructions, please see Add a
Sensor 228 .
Aut o-Discovery Hover to show the Aut o-Discovery menu. The following actions
are available:
Run Aut o-Discovery : Start an automatic search immediately to
automatically add new sensors to the selected device. The
search is running in the background. If found, you see new
sensors on this device after a few minutes. For more information,
please see Aut o-Discovery 199 (Run Aut o-Discovery Now).
Run Aut o-Discovery wit h Templat e: Open an assistant 200 to
start an automatic search with a desired device template.
Creat e Device Open an assistant which guides you through creating a new device
Templat e... template. The template is then available in auto-discovery 198 . For
detailed instructions, please see Creat e Device Templat e 2511 .
Recommend Now Start an analysis to get sensor recommendations for this device.
When PRTG has finished the inspection of the device, you see the
sensor recommendations in a table list on the device overview tab
126 where you can add the according sensor types directly.
Note: This option is only available if the recommendation engine is

enabled 2628 .
Sort Alphabet ically Sort the sensors on the selected device in alphabetical order.
cannot be revoked.
Delet e... Delete the selected device. PRTG will ask for confirmation before
172 02.02.2015
DEVICE MENU
device. For detailed instructions, please see Clone Object 2504 .
Top: Move the device to the top of the mother node (here
usually a probe or group).
Up: Move the device one entry up under the mother node.
Down: Move the device one entry down under the mother
node.
Bot t om: Move the device to the bottom of the mother node.
To Ot her Group...: Move the device to another group.

or If the device is already in paused status, Resume appears. Click to
restart monitoring on this device.
Resume
You can pause and resume monitoring on the selected device. The
monitoring for all sensors on this device will be paused resp.
resumed.
date.
device. Use the date time picker to enter the date and time.
Priorit y /Favorit e Hover to open the Priorit y /Favorit e menu. Define the priority of
the selected device or add to resp. remove it from the favorite
devices list. For details, please see Priorit y and Favorit es 161 .
available:
Device Tools Hover to open the Device Tools menu.
02.02.2015 173
DEVICE MENU
Context Menu Dev ic e Tools

Go To Service URL...
Open the service page that you have defined in the Device
Set t ings 288 . If there is no service URL available for this device,
you can enter an address in the appearing assistant.
New window wit h HTTP...
Open a new browser window with Hypertext Transfer Protocol
(HTTP) and the IP address / DNS name of the device.
New window wit h HTTPS...
Open a new browser window with Hypertext Transfer Protocol
Secure (HTTPS) and the IP address / DNS name of the device.
New window wit h FTP...
Open a new browser window with File Transfer Protocol (FTP)
and the IP address / DNS name of the device.
Remot e Deskt op...
Download an .rdp file. When you execute this file, a remote
desktop will start with the IP address / DNS name of the
device.
Note: In Firefox you have to use mstsc.exe (Microsoft Terminal
Service) to open the file.
Tracerout e...
Start a traceroute on the selected device. PRTG will display the
route and measure transit delays of packets across the IP
network.
Inst all Remot e Probe...
Open an assistant to install a Remot e Probe of PRTG on this
device. For more details, please see Remot e Probe Quick
Inst all 2851 .
174 02.02.2015
DEVICE MENU
Find Duplicat es... Search in your PRTG configuration for devices with the same IP
address or DNS name as the selected device. A window with the
results will appear, either showing existing duplicates or a message
indicating that there are no duplicates.
Send Link by Email Send the link to the selected device by email. Click to create a new
link to the overview tab 126 of the selected device.
Ticket s 153 .
Sensor Context Menu

The Sensor Menu contains actions for your sensors 86 .
SENSOR MENU
Check Now Perform an immediate scan for the selected sensor.
Det ails... Show the overview tab 126 of the selected sensor.
Set t ings...
Open the Sensor Set t ings 310 tab of this sensor.
Not ificat ions...
Open the Not ificat ions 2521 tab of this sensor.
Access Right s...
sensor.
Rename...
Open an assistant to edit the name of this sensor.
Acknowledge Alarm This option is available only in the sensor menu when you select a
sensor in a Down or Down (Part ial) status 123 .
You can acknowledge an alarm for the selected sensor. An
acknowledged alarm will show up in the alarms list as
"acknowledged" (see Sensor St at es 123 ) and will not trigger 2484 any
more notifications 2521 .
02.02.2015 175
SENSOR MENU
You can choose between: Acknowledge Indefinit ely ...,

acknowledge For 5 Minut es..., For 15 Minut es..., For 1 Hour...,
For 3 Hours..., For 1 Day ..., or Unt il.... If you choose Unt il... an
assistant appears where you can define a date. Use the date time
picker to enter the date and time. If the alarm condition still exists
after this date, the sensor will show a Down status again.
Note: If the alarm condition clears, the sensor usually returns into
an Up status immediately with the next sensor scan. For details
about acknowledging an alarm, please see Alarms 146 section.
Delet e... Delete the selected sensor. PRTG will ask for confirmation before
sensor. For detailed instructions, please see Clone Object 2504 .
Top: Move the sensor to the top of the device on which it runs.
Up: Move the sensor one entry up on the device.
Down: Move the sensor one entry down on the device.
Bot t om: Move the sensor to the bottom of the device.

or If the sensor is already in paused status 123 , Resume appears. Click
to restart monitoring on this sensor.
Resume
You can pause and resume monitoring of the selected sensor.
Choose between: Pause Indefinit ely ..., pause For 5 Minut es...,
For 15 Minut es..., For 1 Hour..., For 3 Hours..., For 1 Day ..., or
Pause Unt il.... If you choose Pause Unt il..., an assistant appears
where you can define a date. Use the date time picker to enter the
date and time. PRTG will resume monitoring after this date.
sensor. Use the date time picker to enter the date and time.
Simulat e Error St at us Set the selected sensor to a Down status 123 . Like for the paused
status, Resume will appear in the context menu if a the selected
sensor is already in a simulated error status.
176 02.02.2015
SENSOR MENU
Priorit y /Favorit e Hover to open the Priorit y /Favorit e menu. Define the priority of
the selected sensor or add to resp. remove it from the favorite
devices list. For details, please see Priorit y and Favorit es 161 .
available:
Open the historic data tab for the specified interval 129 : Live
Dat a..., Last 2 day s..., Last 30 day s..., or Last 365 day s...
Compare...: Open the Compare Sensors 132 assistant with the
currently selected sensor.
View Hist oric Dat a: Open the Hist oric Dat a 135 tab of this
sensor.
Send Link by Email Send the link to the selected sensor by email. Click to create a
new email using your system's standard email client. It contains a
direct link to the overview tab 126 of the selected sensor.
Ticket s 153 .
02.02.2015 177
Part 5: Ajax Web InterfaceBasic Procedures | 18 Hover Popup
5.18 Hover Popup

Whenever you rest the mouse pointer for a second over an object's icon in the device tree 110 ,
a hover popup window will appear, showing details about this object. It contains information
from the object's overview tab 126 , as well as several graphs. The exact information provided
depends on the kind of object you are hovering.
Hov er Menu Example: VMware Virtual Mac hine Sensor
Note: The hover popup does only appear if your browser is the currently focused window on
your desktop. It disappears with every (automatic) page refresh.
Menu Icons
At the top of the hover popup window, several icons are shown which enable you to view or
edit the current object. These are the most important options from this object's context menu
165 which is shown when right-clicking it.
178 02.02.2015
Part 5: Ajax Web InterfaceBasic Procedures | 19 Main Menu Structure
5.19 Main Menu Structure

You can access all functions of PRTG using the main menu. In this section, you find descriptions
about the most important menu items. Often, you can either click on an item directly, or hover
it to show more items.
PRTG Main Menu Bar
The following menu items are available:
Home 179
Devices 181
Libraries 183
Sensors 183
Alarms 186
Maps 187
Reports 188
Logs 188
Tickets 190
Setup 191
Refresh (Arrows Symbol) 193
Help Center (? Symbol) 193
Logout (Off Symbol) 193
Search Box 193
Home
Click to open the user's homepage. The default setting is the PRTG welcome page 110 . You can
change the homepage in the user account settings 2587 . Hover to show other menu items.
02.02.2015 179
PRTG Main Menu: Home
HOME
Dashboard 1 Choose a preconfigured dashboard to view monitoring data in

Dashboard 3 another layout. Dashboards provide different preset overviews
with the status of your sensors.
Note: Dashboards are not customizable. You can create your own
overview pages using the Maps 2569 feature.
Swit ch Clust er Node This option is only available if PRTG runs in Clust ering 81 mode.
Show available cluster nodes. Hover to show other menu items.
Follow the menu path (it is specific to your setup) to select
another cluster node. The current Master node is shown in bold
letters. Click on a node's name to leave the current node and
connect to the other, showing the same page there.
Sit emap Open the sitemap which contains a flat text view of all menu items.
You can easily search for key words using the search function in
your browser (usually shortcut CTRL-F).
Go t o Mobile Web GUI Switch to the Mobile Web GUI 2741 which is optimized for low
bandwidth and mobile devices. This interface uses less scripting for
more compatibility.
Note: This is a read-only interface for most parts of PRTG.
Welcome t o PRTG Open the welcome screen 110 that shows the Paessler news feed
and provides quick links to the major sections of the web
interface.
Configurat ion Guru Open the Configurat ion Guru welcome page. For details about
the guru, please see section Using t he Configurat ion Guru 36 .
180 02.02.2015
HOME
Make This My Change the page that is loaded when you click on the Home
Homepage button in the main menu. Select this command on any page to set
its URL as the current user's homepage. This setting is user
sensitive. The default homepage is /welcome.htm.
You can change this setting any time by clicking on this command
again, or by changing the Homepage URL in the My Account 2587
settings.
Devices
Click to show a group view of all your devices, starting with the Root group which contains all
other groups of your setup. Hover to show other menu items.
PRTG Main Menu: Dev ic es
DEVICES
All Open the Overview tab of the Root 84 group that shows a group
view of all your devices (the device tree).
Group View Open a tree view of all probes and groups in your setup. Click to
show a group view of all your devices, starting with the Root 84
group which contains all other groups of your setup. Hover to
show other menu items. Follow the menu path (it is specific to
your setup) to view the devices in a specific probe or group only.
Device List Open a list view of all devices in your setup. Click to show a table
list of all devices in your setup. Hover to show other menu items.
Choose Favorit e Devices to show a list of all devices marked as
Favorit e 161 . Follow the menu path (it is specific to your setup) to
view a table list of the devices in a specific probe or group only.
02.02.2015 181
DEVICES
Note: In the table list 157 appearing, you can re-sort the items by
clicking on the column's header items.
Note: On device lists, you can use the Print QR-Codes button to
show the QR codes of all devices in this list in a printable layout.
You can change the size of these QR codes by changing the values
of the according parameters width, height, and margin in the URL.
Favorit e Devices Open a table list of all devices marked as Favorit e 161 . Click on the
Print QR-Codes button to show a printable list of the QR codes of
all your favorite devices.
Note: To mark any device as a favorite device, select Priorit y /
Favorit e | Add t o Favorit es from its context menu or click on the
small flag on a device's details page.
Dependencies Open an overview list of the Dependencies 92 configured for the

objects in your setup. Hover the menu item to show other menu
items. Choose between Select ed Dependencies and Mast er
Dependencies to view a list of all dependencies or explicit ones.
You can select dependencies and define master dependencies in
the Schedules, Dependencies, and Maint enance Windows
settings of a monitoring object 143 (not available for the Root
group).
Click on Dependencies Graph 2514 to visualize the dependencies
between objects in your configuration. Follow the menu path (it is
specific to your setup) to view dependencies of the objects in a
specific probe or group only.
Add Group Start an assistant which guides you through the process of adding
a new group to your setup. For more information, please see
section Creat e Object s Manually 212 .
Note: You can create new groups much faster by choosing Add
Group... from a probe's or group's context menu.
Add Aut o-Discovery Start an assistant which guides you through the process of adding
Group a new auto-discovery group to your setup. PRTG will create a new
group and run an auto-discovery in your network to add devices
and sensors for these devices automatically. For more information,
please see section Using t he Aut o-Discovery 198
Note: You can create new groups much faster by choosing Add
Aut o-Discovery Group... from a probe's or group's context menu.
182 02.02.2015
DEVICES
Add Device Start an assistant which guides you through the process of adding
a new device to an existing group. During the process, you can
choose if PRTG will run an auto-discover for the new device to add
sensors automatically. For more information, please see section
Creat e Object s Manually 212 .
Note: You can create new devices much faster by choosing Add
Device... from a group's context menu.
Libraries
Click to open the Libraries overview list where you can view or add custom views of your
network status and monitoring data. For more information, please see Libraries 2533 section.
Hover to show other menu items.
PRTG Main Menu: Libraries
LIBR AR IES
All Open the Libraries overview list where you can view or add custom
device tree views of your network status and monitoring data.
Add Library Open an assistant to directly create 2536 a new library.
Select Library Open an existing library. Hover to show other menu items. Follow
the menu path (it is specific to your setup) to select a library and
open it.
Sensors
Click to show a table list of all sensors 86 . In the table list 157 appearing, you can re-sort the
items by clicking on the column's header items, as well as you can filter the list by related
object and tag with the inline filter directly above the table. Hover Sensors in the main menu
bar to show other menu items.
Note: The column Last Value shows only the last value of the sensor's primary channel.
02.02.2015 183
Note: For most sensor lists, you can use Mult i-Edit 2506 to change the settings of more than
one sensor at once.
PRTG Main Menu: Sensors
SENSOR S
All Open a table list 157 of all sensors 86 . In the table list appearing,
you can re-sort the items by clicking on the column's header
items.
Note: The column Last Value shows only the last value of the
sensor's primary channel.
Add Sensor Start an assistant which guides you through the process of adding
a new sensor to an existing device. For more information, please
see section Add a Sensor 228 . During the process, you can also
choose to create a new device via the Add a Device 219 assistant
(that you can also open from the "Devices" menu 181 directly).
Favorit e Sensors Open a table list of all sensors which you marked as Favorit e 161 .
Note: To mark any sensor as a favorite sensor, select Priorit y /
Favorit e | Add t o Favorit es from its context menu or click on the
small flag on a device's details page.
184 02.02.2015
SENSOR S
Top 10 List s Open a dashboard view with different top 10 lists which show
best/worst uptime, Ping, bandwidth usage, website response
times, CPU usage, disk usage, memory usage, and system uptime.
Click to show top 10 lists for all sensors. Hover to show other
menu items. Follow the menu path (it is specific to your setup) to
view top 10 lists for a specific probe or group only.
Note: The shown sensors are selected by default tags.
By Current Value Open a list of sensors filtered by value. Hover to show other menu
items. Follow the menu path to view table lists 157 of Fast est or
Slowest sensors for
Ping
Port
Webpages
IMAP/POP3/SMTP
FTP
as well as a list of sensors with Most Used or Least Used
Bandwidt h
CPU
Disk
Memory
Note: The shown sensors are selected by default tags.
By Current St at us Open a list of sensors filtered by status. Hover to show other

menu items. Follow the menu path to view table lists 2455 of all
sensors in a certain status. For more information about sensor
states, please see Sensor St at es 123 section.
By Upt ime/Downt ime Open a list of sensors filtered by different parameters. Hover to
show other menu items. Follow the menu path to view table lists
157 of all sensors sorted by
Best Upt ime (%)

Highest Upt ime (Time)
Worst Downt ime (%)
Highest Downt ime (Time)
02.02.2015 185
SENSOR S
By Group Open a list of sensors filtered by their parent group. Hover to

show other menu items. Follow the menu path (it is specific to
your setup) to view a sensor table list 157 of a specific probe or
group only.
By Ty pe Open a list of sensors filtered by sensor type 311 . Hover to show

other menu items. Follow the alphabetical menu path (it is specific
to your setup) to view a sensor table list 157 containing only
sensors of one specific sensor type.
By Tag Open a list of sensors filtered by tag 90 . Hover to show other

menu items. Follow the alphabetical menu path (it is specific to
your setup) to see available tags. Select a tag view a table list 157
containing only sensors marked with this tag.
Cross Reference Open the sensor cross reference to show information about all
sensors including priority and favorite status 161 , scanning interval
242 , access rights 96 , notification trigger settings 143 , schedule 93 ,
and dependency 92 . Click to show a sensor cross reference for all

sensors. Hover to show other menu items. Follow the menu path
(it is specific to your setup) to view cross reference information for
sensors in a specific probe or group only, or to view them by type
or tag.
Compare Sensors Compare the data graphs of two or more sensors. Hover to show
other menu items. Follow the menu path to open an assistant for
comparing several monitoring objects. For more information,
please see Compare Sensors 132 section.
View Hist oric Dat a Open an assistant for a quick generation of sensor data reports.
For more information, please see Hist oric Dat a Report s 135
section.
Similar Sensors Open an overview page with a list of "similar sensors". For more
Overview information, please see Similar Sensors 139 section.
Alarms
Click to show a all sensors that currently show a Down, Down (Part ial), Warning, or Unusual
status. In the table list 157 appearing, you can re-sort the items by clicking on the column's
header items. If you select Show as Gauges, this command displays the sensor gauges 126 in a
size corresponding to their priority. Hover to show other menu items.
186 02.02.2015
PRTG Main Menu: Alarms
ALAR MS
All Open a list of all sensors which are currently in Down, Down
(Part ial), Down (Acknowledged), Warning, or Unusual status 123 .
Show as Gauges Open a page with the gauges of all sensors which are currently in
Down, Down (Part ial), Down (Acknowledged), Warning, or
Unusual status. The size of the sensor gauges corresponds to
their respective priority.
Errors Only Open a list of all sensors which are currently in Down, Down
(Part ial), or Down (Acknowledged) status.
Warnings Only Open a list of all sensors which are currently in Warning status.
Unusuals Only Open a list of all sensors which are currently in Unusual status.
Maps
Click to open the Maps overview page where you can view or add custom views of your
network status and monitoring data. For more information, please see Maps 2569 section. Hover
to show other menu items.
PRTG Main Menu: Maps
02.02.2015 187
MAPS
All Open the Maps overview page where you can view or add custom
views of your network's status and monitoring data.
Add Map Open an assistant to directly add 2572 a new map.
Select Map Open an existing map. Hover to show other menu items. Follow
the menu path (it is specific to your setup) to select a map.
Reports
Click to open the Reports overview page where you can view or add reports of your
monitoring data. For more information, please see Report s 2549 section. Hover to show other
menu items.
PRTG Main Menu: Reports
R EPOR TS
All Open the Reports overview page where you can view or add
reports of your monitoring data.
Add Report Open an assistant to directly add 2553 a new report.
Select Report Open an existing report. Hover to show other menu items. Follow
the menu path (it is specific to your setup) to select a report.
Configurat ion Create reports for maps, reports, user and user groups, and
Report s system configuration to document changes to the configuration.
Hover to see the available configuration reports 2552 .
Logs
Click to show log information for all objects in your configuration, newest first. In the table list
157 appearing, you can filter the items by using the respective options 157 . Hover to show
other menu items. For more information, please see Logs 148 section.
188 02.02.2015
Note: Logs for monitoring objects (for example, sensors) are available as long as you define
for Logfile Records in the Hist oric Dat a Purging settings under Sy st em Administ rat ion
Core & Probes 2642 .
PRTG Main Menu: Logs
LOGS
All Open a table list 157 with log information for all objects in your
configuration, newest first.
By Group Open a list with log information for objects in a certain group only,
newest first. Hover to show other menu items. Select All, or follow
the menu path (it is specific to your setup) to select a group you
would like to show log information for.
St at us Changes Open a list with log information for certain status changes only.
Hover to show other menu items. Follow the menu path to view
log entries with a special value in the St at us field only. Select
between Up & Down (shows entries with either Up or Down in
the St at us field), Down, Warning, Unusual, Up, Paused/Resumed
(shows entries with either Paused or Resumed in the St at us field),
or Acknowledged Alarms.
Sy st em Event s Open a list with log information regarding certain system event
types only. Hover to show other menu items. Select between the
following event types: Probe Relat ed, Clust er Relat ed, Aut o-
Discovery , Not ificat ions, or St at us Messages.
Object Hist ory Open a list with log information about changes to the PRTG setup
and deletions of subordinate system objects. The object history
page has a tab-like interface. Using the tabs you can navigate
through various sub-pages in order to view the changes to all
related settings and deletions of objects. Select between the
following tabs: My Account , Sy st em Set up, Not ificat ions,
Schedules, User Account s, User Groups, Report s, Libraries, or
Maps.
Note: You can open a specific tab directly with the context button
Hist ory in the page header bar 114 on the corresponding pages.
02.02.2015 189
Tickets
Click to show all tickets which are assigned to the current user. In the table list 157 appearing,
you can re-sort the items by clicking on the column's header items, as well as you can filter the
list with the inline filter directly above the table. Hover to show other menu items.
Tickets show important system information or action steps to take for the administrator. For
best experience with PRTG, check every ticket and conduct appropriate actions. For more
information, please see section Ticket s 150 .
PRTG Main Menu: Tic kets
You have several options to display a list of tickets which is filtered to your needs. You can
also create a new ticket via the main menu.
TICKETS
All Open a list of all open tickets which are assigned to the current
user.
My Ticket s Open a list of all open tickets which are assigned to the current
user. Hover to show other menu items for filtering these tickets
depending on their status.
All Ticket s Open a list of all open tickets of all PRTG users. Hover to show
other menu items for filtering these tickets depending on their
status.
ToDo Ticket s Open a list of open tickets from the type ToDo. Hover to show
other menu items for filtering these tickets depending on their
status.
Open Ticket Open the New Ticket dialog. Provide the needed information and
confirm by clicking on Save to create a User Ticket . For more
information about available options, please refer to section
Ticket s 150 .
190 02.02.2015
Setup
Click to show the setup page. Hover to show other menu items. For more information, please
see Set up 2585 section.
PRTG Main Menu: Setup
SETU P
Overview Open the setup page 2585 .
Account Set t ings Open the My Account 2587 settings. Hover to show and open the
tabs of account settings directly. Choose from:
My Account 2587
Not ificat ions 2593
Not ificat ion Cont act s 2608
Schedules 2612
Sy st em Open the Sy st em Administ rat ion 2616 settings. Hover to show and
Administ rat ion open the tabs of the system administration settings directly.
Choose from:
User Int erface 2616
Monit oring 2626
Not ificat ion Delivery 2631
Core & Probes 2638
Clust er 2658
User Account s 2644
User Groups 2649
Administ rat ive Tools 2653
02.02.2015 191
SETU P
PRTG St at us Open the PRTG St at usSy st em St at us 2660 page. When running a

cluster, hover to show other menu items. Choose from:
Sy st em St at us 2660
Clust er St at us 2675
License Open the license act ivat ion st at us 2677 page. Hover to show
other menu items. Choose from:
St at us 2677 to view information about your license.
Ent er License Key 2678 to enter your license name and key and
to show your licensed PRTG edition.
Aut o-Updat e Open information about the Soft ware Aut o-Updat e 2670 status of
your PRTG installation. On this page, you can also download and
install available updates. Hover to show other menu items. Choose
from:
St at us 2670 to view the update status and to manually check for
the latest update.
Set t ings 2672 to define your update settings.
Downloads / Add-Ons Open the downloads page 2680 of PRTG for additional downloads.
Choose from:
Client App for Windows (Ent erprise Console) 2680
Client Apps for Mobile Devices 2680
Remot e Probe Inst aller 2680
PRTG Add-Ons 2680
PRTG Billing Tool 2681
Deskt op Not ificat ions 2682
PRTG API Open the documentation of the Applicat ion Programming

Int erface (API) Definit ion 2830 for your installation.
Cont act Support Open the Cont act Paessler Support / Send Your Feedback t o
Paessler 2684 form.
192 02.02.2015
Refresh (Arrows Symbol)
PRTG Main Menu: Refresh Button
Click this symbol to refresh all elements on the current page to display current data. Unlike the
reload function of your browser, this merely refreshes the single page elements, not the whole
page.
Help Center (? Symbol)
PRTG Main Menu: Help Button
Open the Help and Support Cent er to get help if you have any questions regarding your
PRTG setup.
Logout (Off Symbol)
PRTG Main Menu: Logout Button
Log out the current user and return to the login screen 104 .
Search Box
Use the search box to find objects and reports, and other items by name or tag, or to search
for help. Click into the field to enlarge it.
Context Menu
Additionally, there are Cont ext Menus 165 available for all objects. Right-click on an object to
open it.
02.02.2015 193
Part 6
Ajax Web InterfaceDevice and Sensor Setup
02.02.2015 195
Part 6: Ajax Web InterfaceDevice and Sensor Setup |
6 Ajax Web InterfaceDevice and Sensor

Setup
The Ajax-based web interface is your access to PRTG. Use it to configure devices and sensors,
to set up notifications, as well as to review monitoring results and to create reports. This web
interface is highly interactive, using Asynchronous Java Script and XML (AJAX) to deliver a
powerful and easy-to-use user experience. While you are logged in 104 , the PRTG web interface
permanently refreshes the data on the screen permanently (via Ajax calls) so it always shows
the current monitoring results (you can set 2644 refresh interval and method individually).
Because the web interface works as a Single Page Application (SPA), you rarely see a full page
refresh to avoid this performance impact due to redundant processing. Only single page
elements are refreshed when necessary. The AJAX web interface shows all object setting
dialogs as pop-up layers, so you never lose the current context. This speeds up the user
experience appreciably and makes the configuration of objects in PRTG comprehensible. The
responsive design of the web interface ensures that it always adjusts to the size of your
screen to see more information at a glance.
The following sections introduce device and sensor setup in the Ajax Graphical User Interface
(GUI).
Ajax Web InterfaceDevice and Sensor SetupTopics

Aut o-Discovery 198
Creat e Object s Manually 212
Manage Device Tree 230
Root Group Set t ings 232
Probe Set t ings 248
Group Set t ings 266
Device Set t ings 288
Sensor Set t ings 310 List of Available Sensor Ty pes 311
Addit ional Sensor Ty pes (Cust om Sensors) 2474
Sensor Channels Set t ings 2477
Sensor Not ificat ions Set t ings 2484
196 02.02.2015
Part 6: Ajax Web InterfaceDevice and Sensor Setup |

Ajax Web Int erfaceBasic Procedures 102
Related Topics
02.02.2015 197
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 1 Auto-Discovery
6.1 Auto-Discovery
PRTG's auto-discovery function is a great way to automatically create a sophisticated and
concise set of sensors for your complete network. It is mainly suitable for LAN discovery since
it involves a lot of SNMP and WMI. For video instructions, please see the More 211 section
below.
For a quick start auto-discovery, please see TWOUsing t he Configurat ion Guru 36 section.
How Auto-Discovery Works

PRTG's auto-discovery process has three stages:
St ep 1
Scanning a network segment for devices using Ping (for groups only).
St ep 2
Assessing the device type for all devices discovered in Step 1 (using SNMP, WMI, and other
protocols).
St ep 3a
Creating sensor sets that match the discovered device types of step 2. This is done based
on built-in device templates with recommended sensors for many device types.
St ep 3b (opt ional)
Creating sensor sets using user created device templates (see Creat e Device Templat e 2511
section).
The auto-discovery can be used on a group level for a range of IP addresses, or for individual
devices which you might have created manually. It can be run just once, on demand via the
context menu, or scheduled every hour, day or week. Running the auto-discovery every day
or week will automatically create new sensors when new devices are connected to the
network. As soon as new devices or sensors are discovered, new Ticket s 150 are created
(which are mailed to the system administrator by default).
Please be aware of the following restrictions of the auto-discovery:
PRTG can not discover devices that can not be pinged, since Step 1 uses pings. If, for
example, a firewall blocks echo requests, a device behind it cannot be discovered.
You should supply authentication settings for Windows Sy st ems, Linux (SSH/WBEM)
Sy st ems, VMware/X EN Servers, and SNMP Devices in order to fully exploit the power of
this feature. We recommend defining these in the Root group settings 232 .
If a device has more than one IP address, it may show up more than once in the discovery
results, even though PRTG tries to identify these situations.
If a device already exists on the same probe, the auto-discovery will skip this device and not
create a duplicate.
Using frequent auto-discoveries of large network segments can lead to performance issues.
We therefore recommend to only schedule regular auto-discoveries where necessary. For
detailed information see the More 211 section below.
198 02.02.2015
Run Auto-Discovery Now

You can run an auto-discovery at any time for a group or a device. To do so, right-click on the
respective object and from the context menu, select Run Aut o-Discovery . PRTG will
immediately start searching for new objects which can be added to the device tree. If used for
a group, PRTG will add devices and sensors, if found. If used for a device, it will add new
sensors, if found. You can always see in the respective page header bar 114 when the last auto-
discovery was run on a selected group or device.
Note: The auto-discovery will also re-add devices or sensors you have manually deleted. If you
do not want this, please create objects manually 212 only.
Creating an Auto-Discovery Group

There are several ways to start auto-discovery:
On the welcome screen 110 , click on the Perform Net work Aut o-Discovery option,
or select Devices | Add Aut o-Discovery Group from the main menu.
To start an automatic detection of devices and sensors in your network an assistant will
appear, leading you through two steps. For faster setup, you can select Add Aut o-Discovery
Group... in the context menu 165 of a probe or group to which you want to add the new
group. This will skip step 1 and lead you directly to step 2.
02.02.2015 199
Add Auto-Disc ov ery Group Dialog
St ep 1
Please choose a probe or group you want to add the new group to. Click on Cont inue.
St ep 2
Add auto-discovery settings as described below.
Add Auto-Discovery Group Settings
GR OU P NAME AND TAGS
Group Name Enter a meaningful name to identify the group. The name will be
shown by default in the devices tree and in all alarms.
Tags Enter one or more tags; confirm each tag by hitting the space,
comma, or enter key. You can use tags to group objects and use
tag-filtered views later on. Tags are not case sensitive. Tags are
automatically inherited 90 .
200 02.02.2015
GR OU P TYPE
Sensor Management Select the method for automatic network discovery. Choose
between:
Aut omat ic device ident ificat ion (st andard, recommended):
Detect mainly based on Ping, SNMP, and WMI. This option should
work fine for most installations.
Aut omat ic device ident ificat ion (det ailed, may creat e many
sensors): Detect in a more detailed way and create more
sensors. This option uses all standard device templates for auto-
discovery. It is suitable for small network segments and
whenever you want to monitor the maximum number of sensors
available.
Aut omat ic sensor creat ion using specific device t emplat e
(s): Manually define the device templates used for auto-
discovery. From the list below, select one or more templates.
Device Template(s) This option is only visible if using specific device templates (last
option) is enabled above. Please choose one or more templates by
adding a check mark in front of the respective template name. You
can also select and deselect all items by using the check box in the
table head. These will be used for auto-discovery on the current
device. Choose from:
ADSL
Cisco ASA VPN
Cisco Device (Generic)
Dell MDI Disk
DNS Server
Environment Jacart a
Environment Poseidon
Frit zbox
FTP Server
Generic Device (PING only )
Generic Device (SNMP-enabled)
Generic Device (SNMP-enabled, Det ailed)
HTTP Web Server
Hy per V Host Server
Linux/UNIX Device (SNMP or SSH enabled)
Mail Server (Generic)
02.02.2015 201
Mail Server (MS Exchange)

Microsoft Sharepoint 2010
NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
NTP Server
Print er (HP)
RDP Server
RMON compat ible device
Server (Compaq/HP agent s)
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
Swit ch (Cisco Cat aly st )
Swit ch (Cisco IOS Based)
Swit ch (HP Procurve)
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
VMware ESX / vCent er Server
Windows (Det ailed via WMI)
Windows (via Remot e Powershell)
Windows (via WMI)
Windows IIS (via SNMP)
X EN Host s
X EN Virt ual Machines
Once the auto-discovery is finished, PRTG will create a new ticket

150 and list the device templates which were actually used to
create new sensors. Templates which were not applied will not be
shown in the ticket.
Discovery Schedule Define when the auto-discovery will be run. Choose between:
202 02.02.2015
Once: Perform auto-discovery only once. New devices and

sensors will be added once. You can run auto-discovery manually
any time using an object's context menu 165 .
Hourly : Perform auto-discovery for new devices and sensors
every 60 minutes. Note: Please use this option with caution!
Frequently executed auto-discoveries might cause performance
issues, especially when large network segments are scanned
every hour.
Daily : Perform auto-discovery for new devices and sensors
every 24 hours. The first auto-discovery will run immediately, all
other discoveries will start on the time defined in the Aut o-
Discovery Set t ings section of the Sy st em Administ rat ion
Monit oring 2629 settings.
Weekly : Perform auto-discovery for new devices and sensors
every 7 days. The first auto-discovery will run immediately, all
IP Selection Method Define how you want to define the IP range for auto-discovery.
Choose between:
Class C base IP wit h st art /end (IPv4): Define an IPv4 class C
address range.
List of individual IPs and DNS names (IPv4): Enter a list of
individual IPv4 addresses or DNS names.
IP and Subnet (IPv4): Enter an IPv4 address and subnet mask.
IP wit h oct et range (IPv4): Enter an IPv4 address range for every
IP octet individually. With this, you can define very customizable
IP ranges.
Use comput ers from t he act ive direct ory (maximum 1000
comput ers): Search in the active directory for computers to
perform auto-discovery. Note: Define your active directory
domain in advance in the system administration. See Sy st em
Administ rat ionCore & Probes 2641 .
Note: Only subnets with up to 65,536 IP addresses can be
discovered! If you define a range with a higher number of
addresses, discovery will stop before it is completed.
IPv4 Base This field is only visible if Class C network detection is selected
above. Enter a class C network as IP base for the auto-discovery.
Enter the first three octets of an IPv4 IP address, for example,
192.168.0
02.02.2015 203
IPv4 Range Start This field is only visible if Class C network detection is selected
above. Enter the IP octet of the class C network specified above
from which PRTG will start the auto-discovery. This will complete
the IP base above to an IPv4 address. For example, enter 1 to
discover from 192.168.0.1.
IPv4 Range End This field is only visible if Class C network detection is selected
above. Enter the IP octet of the class C network specified above at
which PRTG will stop the auto-discovery. This will complete the IP
base above to an IPv4 address. For example, enter 254 to discover
up to 192.168.0.254.
IPv4/DNS Name List This field is only visible if the IP list option is selected above. Enter
IPv6/DNS Name List a list of IP addresses or DNS names which the auto-discovery will
scan. Enter each address in a separate line.
IPv4 and Subnet (IPv4) This field is only visible if the IP and subnet option is selected
above. Enter an expression in the format address/subnet , e.g.
192.168.3.0/255.255.255.0. You can also use the short form like
192.168.3.0/24 in this example. PRTG will scan the complete host
range (without network and broadcast address) defined by the IP
address and the subnet mask.
IP with Octet Range This field is only visible if the octet range option is selected above.
Enter an expression in the format a1.a2.a3.a4, where a1, a2, a3,
and a4 are each a number between 0-255, or a range with two
numbers and a hyphen like 1-127. All permutations of all ranges are
calculated, e.g. 10.0.1-10.1-100 results in 1,000 addresses that
PRTG will scan during auto-discovery.
Organizational Unit This field is only visible if active directory is selected above. Enter
an organizational unit (OU) to restrict the active directory search to
computers which are part of this OU. Just enter the name of the OU
without any other term (i.e., without "OU" in front). If you leave this
field empty, there will not be any restriction.
If you have sub-OUs, consider the correct syntax in the format
Y,OU=X : OUs that are part of another OU have to be listed
together with their parent(s). Enter the sub-OU followed by ,OU=
and the name of the parent OU.
Examples:
Assuming that the organizational unit 'Y' is part of the OU named
'X'. Then the syntax would be Y,OU=X.
For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would
be Z,OU=Y,OU=X.
Note: The order is important, sub-OUs have to be listed left of their

particular parents!
204 02.02.2015
Name Resolution Define how newly discovered devices will be monitored. This only
affects new devices. The setting for existing devices will be kept.
Choose between:
Use DNS / WMI / SNMP names (recommended): Monitor newly
discovered devices via their DNS, WMI, or SNMP names (if
available).
Use IP addresses: Monitor newly discovered devices via their IP
address.
We recommend using the default value.
Device Rescan Define if you want to rescan known devices. Choose between:
Skip aut o-discovery for known devices/IPs (recommended):
Do not re-scan known devices or IP addresses, but only scan for
new devices/IPs when auto-discovering. This can avoid re-
creation of manually deleted sensors. PRTG will also avoid adding
devices that are already included elsewhere in your
configuration, e.g. in other groups.
Perform aut o-discovery for known devices/IPs: Re-scan
known devices and IP addresses with every auto-discovery. This
will re-create manually deleted sensors on existing devices.
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should
be changed there, if necessary. Often, best practice is to change them centrally in the Root 232
group's settings. To change a setting for this object, disable inheritance by clicking on the
check mark symbol in front of the respective setting name. You will then see the options
described below.
If you have not set credentials yet, set them now before starting the auto-discovery in order
to fully exploit the power of this feature!
CR EDENTIALS FOR WINDOWS SYSTEMS
Domain or Computer Define the authority for Windows access. This is used for Windows
Name Management Instrumentation (WMI) and other Windows sensors. If
you want to use a Windows local user account on the target
device, please enter the computer name here. If you want to use a
Windows domain user account (recommended), please enter the
(Active Directory) domain name here. If not explicitly defined, PRTG
will automatically add a prefix in order to use the NT LAN Manager
(NTLM) protocol. Please do not leave this field empty.
02.02.2015 205
Username Enter the username for Windows access. Usually, you will use
credentials with administrator privileges.
Password Enter the password for Windows access. Usually, you will use
CR EDENTIALS FOR LINU X/SOLAR IS/MAC OS (SSH/WBEM) SYSTEMS
Username Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Login Define which authentication method will be used for login. Choose
between:
Login via Password: Provide a password for login. Enter below.
Login via Privat e Key : Provide a private key for authentication.
Note: PRTG can only handle keys in OpenSSH format which are
not encrypted. You cannot use password protected keys here.
In the text field, please paste the entire private key, including the
"BEGIN" and "END" lines. Please make sure the according public
key is provided on the target machine. For details, please see
Monit oring via SSH 2756 .
Password This field is only visible if password login is selected above. Enter a
password for the Linux access via SSH and WBEM. Usually, you will
use credentials with administrator privileges.
Private Key This field is only visible if private key login is selected above. Paste
a private key into the field (OpenSSH format, unencrypted). Usually,
you will use credentials with administrator privileges. Note: If you
do not insert a private key for the first time, but change the private
key, you need to restart your PRTG core server service in order for
the private key change to take effect! For details, please see
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
HTTP: Use an unencrypted connection for WBEM.
HTTPS: Use an SSL-encrypted connection for WBEM.
For WBEM Use Port Define the port that will be used for WBEM. This setting is only
206 02.02.2015
Set aut omat ically (port 5988 or 5989): Use one of the
standard ports, depending on whether unencrypted or
encrypted connection is chosen above.
Set manually : Use a custom port. Define below.
WBEM Port This setting is only visible if manual port selection is enabled
above. Enter the WBEM port number.
SSH Port Define the port number which will be used for SSH connections.
Note: By default, this setting is automatically used for all SSH
sensors 316 , unless you define a different port number in the
sensor settings.
SSH Rights Elevation Define with which rights the command will be executed on the
target system. Choose between:
Run t he command as t he user connect ing (default ): Use the
rights of the user who establishes the SSH connection.
Run t he command as anot her user using 'sudo': Use the rights
of another user, for example, the administrator.
Run t he command as anot her user using 'su': Use the rights of
another target user.
Target Username This field is only visible if sudo or su is enabled above. Enter a
username to run the specified command as another user than root.
If you leave this field empty, the command will be run as root.
Ensure that you set the Linux password even you use a public/
private key for authentication. This is not necessary if the user is
allowed to execute the command without a password.
Password Target User This field is only visible if su is enabled above. Enter the password
for the specified target user.
CR EDENTIALS FOR VMWAR E/XENSER VER
User Enter a login name for access to VMware and XEN servers. Usually,
you will use credentials with administrator privileges.
Password Enter a password for access to VMware and XEN servers. Usually,
02.02.2015 207
VMware Protocol Define the protocol used for the connection to VMware and
XenServer. Choose between:
HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XenServers.
HTTP: Use an unencrypted connection to VMware and
XenServers.
CR EDENTIALS FOR SNMP DEVICES
SNMP Version Select the SNMP version that will be used for device connection.
Choose between:
v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
v2c: Use the more advanced v2c protocol for SNMP
connections. Data is still transferred as clear-text, but it supports
64-bit counters.
v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
Note for SNMP v3: Due to internal limitations you can only monitor
a limited number of sensors per second using SNMP v3. The limit is
somewhere between 1 and 50 sensors per second (depending on
the SNMP latency of your network). This means that using an
interval of 60 seconds you are limited to between 60 and 3000
SNMP v3 sensors for each probe. If you experience an increased
"Interval Delay" or "Open Requests" reading of the probe health
sensor, you need to distribute the load over multiple probes. SNMP
v1 and v2 do not have this limitation.
Community String This setting is only visible if SNMP version v1 or v2c are enabled
above. Enter the community string of your devices. This is a kind of
"clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type This setting is only visible if SNMP version v3 is enabled above.
Choose between:
MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
SHA: Use Secure Hash Algorithm (SHA) for authentication.
The chosen type has to match the authentication type of your
device.
208 02.02.2015
Note: If you do not want to use authentication, but you need SNMP
v3, for example, because your device requires context, you can
leave the field password empty. In this case,
SNMP_SEC_LEVEL_NOAUTH will be used and authentication will be
deactivated entirely.
User This setting is only visible if SNMP version v3 is enabled above.

Enter a username for secure authentication. This value has to
match the username of your device.
Password This setting is only visible if SNMP version v3 is enabled above.

Enter a password for secure authentication. This value has to
match the password of your device.
Encryption Type This setting is only visible if SNMP version v3 is enabled above.
Select an encryption type. Choose between:
DES: Use Data Encryption Standard (DES) as encryption
algorithm.
AES: Use Advanced Encryption Standard (AES) as encryption
algorithm.
The chosen type has to match the encryption type of your device.
Data Encryption Key This setting is only visible if SNMP version v3 is enabled above.
Enter an encryption key here. If you provide a key in this field,
SNMP data packets will be encrypted using the encryption
algorithm selected above, providing increased security. The
provided key here has to match the encryption key of your
device. Note: If the key entered in this field does not match the
key configured in the target SNMP device, you will not get an error
message! Please enter a string or leave the field empty.
Context Name This setting is only visible if SNMP version v3 is enabled above.
Enter a context name only if it is required by the configuration of
the device. Context is a collection of management information
accessible by an SNMP device. Please enter a string.
SNMP Port Enter the port used for SNMP communication. We recommend
using the default value.
SNMP Timeout (sec.) Enter a timeout in seconds for the request. If the reply takes
longer than this value the request is aborted and an error message
is triggered.
02.02.2015 209
PR OXY SETTINGS FOR HTTP SENSOR S
HTTP Proxy Settings The proxy settings determine how a sensor connects to a given
URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS. Note: This setting is valid for the
monitoring only and determines the behavior of sensors. In order
to change proxy settings for the core server, please see Sy st em
Name Enter the IP address or DNS name of the proxy server to use. If
you leave this field empty, no proxy will be used.
Port Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User If the proxy requires authentication, enter the username for the
proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password If the proxy requires authentication, enter the password for the
ACCESS R IGHTS
User Group Access Define which user group(s) will have access to the object you're
editing. A table with user groups and right is shown; it contains all
user groups from your setup. For each user group you can choose
from the following access rights:
Inherit ed: Use the settings of the parent object.
None: Users in this group cannot see or edit the object. The
object does not show up in lists.
Read: Users in this group can see the object and review its
settings.
Writ e: Users in this group can see the object, as well as review
and edit its settings. However, they cannot edit access rights
settings.
Full: Users in this group can see the object, as well as review
and edit its settings and edit access rights settings.
You can create new user groups in the Sy st em Administ rat ion
User Groups 2649 settings.
Click on the Cont inue button to store your settings. If you change tabs or use the main menu,
all changes to the settings will be lost!
210 02.02.2015
Auto-Discovery in Progress
While auto-discovery is running you may experience a lower system performance as usual,
because PRTG works in the background in order to discover your network. Depending on the
IP ranges defined (up to 65,536 addresses) , the discovery may run up to several days before
complete. You can review the status of the discovery process as follows:
In the device tree, behind the group or device name, you will see a percentage value
showing the progress of auto-discovery.
During auto-discovery, the web interface will display a box in the lower right corner, showing
the number of active auto-discovery tasks.
In order to stop a running auto-discovery, right-click the group or device, and select Pause |
For 5 minut es... from the context menu 165 . Monitoring will be paused for 5 minutes, and
auto-discovery tasks will be shut down.
Related Topics
Creat e Device Templat e 2511
More
Video Tutorial: There is a video available on the Paessler video tutorials page.
Knowledge Base: Why can automatic auto-discoveries evoke performance issues?

02.02.2015 211
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
6.2 Create Objects Manually

We recommend using the auto-discovery 198 function to create a basic monitoring setup for
your network. Afterwards, you can manually create devices that could not be discovered, or
arrange 2503 detected devices in groups.
The procedure depends on the kind of object you want to add. Choose between:
Add a Group 213
Add a Device 219
Add a Sensor 228
Add a Remote Probe

Please see Mult iple Probes and Remot e Probes 2847 section for more information.
212 02.02.2015
1 Add a Group
6.2.1 Add a Group
In order to add a group manually, select Devices | Add Group from the main menu. An
assistant will appear, leading you through two steps. For faster setup, you can select Add
Group... in the context menu 165 of a probe or group to which you want to add the new
group. This will skip step 1 and lead you directly to step 2.
St ep 1
Please choose a probe or group you want to add the new group to. Click on Cont inue.
Add Group Assistant Step 2
St ep 2
Add group settings as described below.
Add Group Settings
GR OU P NAME AND TAGS
Tags Enter one or more tags; confirm each tag by hitting the space,
comma, or enter key. You can use tags to group objects and use
tag-filtered views later on. Tags are not case sensitive. Tags are
02.02.2015 213
1 Add a Group
between:
214 02.02.2015
1 Add a Group
sensor settings.
02.02.2015 215
1 Add a Group
XenServers.
Choose between:
64-bit counters.
216 02.02.2015
1 Add a Group
Choose between:
device.


algorithm.
algorithm.
02.02.2015 217
1 Add a Group
is triggered.
ACCESS R IGHTS
object does not show up in lists.
settings.
Writ e: Users in this group can see the object, as well as review
and edit its settings. However, they cannot edit access rights
settings.
Full: Users in this group can see the object, as well as review
and edit its settings and edit access rights settings.
User Groups 2649 settings.
218 02.02.2015
2 Add a Device
6.2.2 Add a Device
To manually add a device, select Devices | Add Device from the main menu. An assistant will
appear, leading you through two steps. For faster setup, you can select Add Device... in the
context menu 165 of a group to which you want to add the new device. This will skip step 1
and lead you directly to step 2.
St ep 1
Please choose a group you want to add the new device to. Click on Cont inue.
Add Dev ic e Assistant Step 2
St ep 2
Add device settings as described below.
Add Device Settings
DEVICE NAME AND ADDR ESS
Device Name Enter a meaningful name to identify the device. The name will be
shown by default in the device tree and in all alarms.
IP Version Define which IP protocol PRTG will use to connect to this device.
The setting is valid for all sensors created on this device. Choose
between:
Connect using IPv4: Use IP version 4 for all requests to this
device.
02.02.2015 219
2 Add a Device
DEVICE NAME AND ADDR ESS

device.
IP Address/DNS Name Enter the IP address (either v4 or v6, depending on your selection
above) or DNS name for the device. Most sensors created on this
device will inherit this setting and they will try to connect to this
address for monitoring. Note: There are some sensor types that
still have their own setting for IP address/DNS name. Those
sensors will use their own settings.
Tags Enter one or more tags; confirm each tag by hitting space, comma,
or enter key. You can use tags to group sensors and use tag-
filtered views later on. Tags are not case sensitive. Tags are
Device Icon Choose a device icon from the list. It will be shown in the device
tree.
DEVICE TYPE
Sensor Management Select which type of auto-discovery you would like to perform for
this device. Choose between:
Manual (no aut o-discovery ): Do not auto-discover any sensors,
but only add sensors manually.
Use a small set of auto-discovery templates. This will scan your
LAN and usually create a view standard sensors on your device.
sensors: Use an extended set of auto-discovery templates. This
will scan your LAN and usually create many sensors on your
device.
Aut omat ic sensor creat ion using specific device t emplat es:
Use specific auto-discovery templates only. Please select
templates below. This will scan your LAN and add sensors
defined in the template.
Discovery Schedule This option is only visible if one of the auto-discovery options is
selected above. Define when the auto-discovery will be run.
Choose between:
Once: Perform auto-discovery only once. For existing devices,
this will initiate a one-time sensor update for the current device.
Hourly : Perform auto-discovery for new sensors every hour.
220 02.02.2015
2 Add a Device
DEVICE TYPE
Daily : Perform auto-discovery for new sensors every day.

Weekly : Perform auto-discovery for new sensors every week.
ADSL
Cisco ASA VPN
Dell MDI Disk
DNS Server
Frit zbox
FTP Server
HTTP Web Server
NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
NTP Server
Print er (HP)
02.02.2015 221
2 Add a Device
DEVICE TYPE
RDP Server
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
Windows (via WMI)
X EN Host s

222 02.02.2015
2 Add a Device
between:
02.02.2015 223
2 Add a Device
sensor settings.
224 02.02.2015
2 Add a Device
XenServers.
Choose between:
64-bit counters.
02.02.2015 225
2 Add a Device
Choose between:
device.


algorithm.
algorithm.
226 02.02.2015
2 Add a Device
is triggered.
ACCESS R IGHTS
object does not show up in lists and in the device tree.
Exception: If a child object is visible to the user, the object is
visible in the device tree, though not accessible.
monitoring results.
Writ e: Users in this group can see the object, review its
monitoring results, and edit the object's settings. They cannot
edit access rights settings.
Full: Users in this group can see the object, review its
monitoring results, edit the object's settings, and edit access
rights settings.
User Groups 2649 settings. To automatically set all objects further
down in the hierarchy to inherit this object's access rights, set a
check mark for the Revert children's access right s t o inherit ed
option.
For more details about access rights, please see section User
Access Right s 96 .
02.02.2015 227
3 Add a Sensor
6.2.3 Add a Sensor
In order to add a sensor manually, select Sensors | Add Sensor from the main menu. An
assistant will appear, leading you through two steps. For faster setup, you can select Add
Sensor... in the context menu 165 of a device to which you want to add the new sensor. This
will skip step 1 and lead you directly to step 2.
St ep 1
Please select Add sensor t o an exist ing device and choose a device you want to add the
new sensor to. Click on Cont inue.
Add Sensor Assistant
228 02.02.2015
3 Add a Sensor
St ep 2
The Add Sensor assistant is shown (see screenshot above). Select a sensor you want to
add and enter the needed settings. You can filter the listed sensors by type, by target
system, and by the used technology. You can choose one aspect per filter. Alternatively or
additionally, you can use the live search by typing in a key term (or a substring) in the Search
box. PRTG also suggests sensor types to create on the selected device; this
recommendation is automatically calculated based on the current user's sensor usage and
shows the ten commonest sensor types by default (if enough sensor types are already in
use). The chosen filter also applies to the recommendation. See section More if you want to
adjust the number of most used sensor types which are shown here or to hide this option
completely.
For more information about a sensor type, please see the manual section of the respective
sensor. See List of Available Sensor Ty pes 311 section to find detailed information about
every sensor type.
More
Knowledge Base: How can I change the number of entries in most used sensor types?
02.02.2015 229
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 3 Manage Device Tree
6.3 Manage Device Tree

While viewing the device tree (or parts of it), click on the Management tab to enter a different
tree view which shows your devices and sensors in a less colorful way. While in this view, you
can move monitoring objects using drag&drop in your browser window. You can also view and
edit object settings by selecting it. Changes take effect immediately. When done, leave the
Management tab.
In order to arrange objects in the tree, you have the following options:
Drag&Drop a Sensor
You can either move a sensor within the same device, or clone a sensor to another device.
Within the same device, drag any sensor and drop it to the place where you want to have it.
A shade will show the future position. When dropping, the sensor will be moved to this
position and existing sensors will be lined up after it. This is a very easy way to reposition
your sensors.
Drag any sensor from one device and drop it on another to clone a sensor. This will create
the same sensor type, with the same settings, on the new device, while maintaining the
original sensor. A shade will show the future position. Note: Cloned sensors are put to
Pause status initially to give you the chance to change any settings before monitoring
begins. Please check the settings 143 and resume 164 monitoring.
Note: You cannot clone 'fixed' objects, such as the root group or a probe device.
Note: In order to clone entire groups or devices, please use the Clone Object 2504 functionality
accessible via the objects' Context Menu 165 .
Drag&Drop a Group or Device

You can change a group's or device's position by using drag&drop.
Within the same probe or group, drag any group or device and move it up or down in the
device tree. A small red arrow will appear, showing the future position. When dropping, the
group or device will be moved to this position and existing probes, groups, and devices will
be lined up underneath. This is a very easy way to reposition your groups or devices.
Drag any group or device from one probe or group and drop it on another probe or group.
A small red arrow will appear, showing the future position. When dropping, the group or
device will be moved to the new probe or group. Existing groups and devices will be lined
up underneath. This is a very easy way to change the probe a group or device is part of, or
to add groups or devices to other groups.
Note: The Local Probe and Remote Probes cannot be moved.
230 02.02.2015
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 3 Manage Device Tree
Multi-Edit Object Properties

You can use Multi-Edit for object settings:
Hold down the Ctrl key and select multiple groups, devices, or sensors (one of a kind).
In the appearing dialog, select the settings you want to edit, change the according values,
and click Save. The changes will be applied to all selected objects.
The dialog is the same as described in the Mult i-Edit 2508 (Edit Settings) section.
Related Topics
For other ways to arrange objects, please see
Arrange Object s 2503
Creat e Device Templat e 2511
Clone Object 2504
02.02.2015 231
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
6.4 Root Group Settings

On the Root group's overview page, click on the Set t ings tab to change settings.
The Root Group is Special

The Root group is the highest instance in the object hierarchy of your PRTG setup and parent
to all other objects. Therefore, all objects inherit settings from the Root group. If you define
important settings on this high level, work will be easier later on. So, before you create your
own sensors, it is a good idea to review the Root group's settings to ensure they suit your
network. There are already reasonable presets made with installation.
Note: If necessary, you can override every setting for every single child object later. To do so,
simply disable the respective Inherit option of an object.
Root Group Settings

The following settings are available in the Set t ings tab. As you may not need all of these, just
regard those settings you really need and ignore the others. All settings you define here can
easily be inherited to all other objects in your setup.
BASIC GR OU P SETTINGS
Status Define if monitoring for this group is started or paused. Choose

between:
St art ed: Monitor this group.
Paused: Pause monitoring for this group. All sensors on all
devices in this group will be paused until this setting is changed
again.
232 02.02.2015
LOCATION
Location (for geo When using geo maps using Google's API 2516 please enter a
maps) location in the first line. Objects will then be displayed on a
geographical map with a flag, showing the current status using a
color code similar to the sensor status icons 123 (green - yellow -
orange - red). You can enter a full postal address, city and country
only, or latitude and longitude. It is possible to enter any text
before, between, and after the coordinates, PRTG will parse latitude
and longitude automatically; for example: 49.452778 11.077778 or
enter 49.452778 any 11.077778 text
A minus sign (-) in the first line will hide an object from geo maps. In
this case you can enter location information in line two and
following.
You can define a specific label for each location: enter a string
denoting the label in the first line and provide geo coordinates in
the second line. This object will be displayed then with the label in
PRTG's geo map.
02.02.2015 233
between:
sensor settings.
234 02.02.2015
XenServers.
02.02.2015 235
Choose between:
64-bit counters.
Choose between:
device.


236 02.02.2015
algorithm.
algorithm.
is triggered.
WINDOWS COMPATIBILITY OPTIONS
When experiencing problems while monitoring via Windows sensors, you can set some
compatibility options for trouble shooting.
Preferred Data Source Define the method Windows sensors will use to query data. This
setting is valid only for hybrid sensors offering performance
counter and Windows Management Instrumentation (WMI)
technology. The setting will be ignored for all other sensors!
Choose between:
02.02.2015 237
Performance Count ers and fallback t o WMI (recommended):

Try to query data via performance counters. If this is not
possible, establish a connection via WMI. This is the
recommended setting to best balance resource usage and
functionality.
Performance Count ers only : Query data via performance
counters only. If this is not possible, a sensor will return no data.
WMI only : Query data via WMI only. If this is not possible, a
sensor will return no data.
Timeout Method Specify the time the sensor will wait for the return of its WMI query
before aborting it with an error message. Choose between:
Use 1.5x scanning int erval (recommended): Use a default of
one and a half times the scanning interval set for the sensor (see
below in this settings).
Set manually : Enter a timeout value manually.
We recommend using the default value. Only if you experience
ongoing timeout errors, try increasing the timeout value.
Timeout Value (Sec.) This field is only visible if the manual timeout method is selected
above. Specify the time the sensor will wait for the return of its
WMI query before aborting with an error message. Please enter an
integer value.
SNMP COMPATIBILITY OPTIONS
When experiencing problems while monitoring via Simple Network Management Protocol
(SNMP) sensors, you can set some compatibility options for trouble shooting.
SNMP Delay (ms) Add a time in milliseconds that will be waited between two SNMP
requests. This can help increase device compatibility. Please enter
an integer value. We recommend using the default value. If you
experience SNMP connection failures, please increase it. You can
define a delay between 0 and 100, higher delays are not supported
and will be discarded.
Failed Requests Define if an SNMP sensor will try again after a request fails.
Ret ry (recommended): Try again if an SNMP request fails. This
can help prevent false error messages due to temporary timeout
failures.
238 02.02.2015
Do not ret ry : Do not retry if an SNMP request fails. With this

setting enabled an SNMP sensor will be set to error status
earlier.
Overflow Values Define how PRTG will handle overflow values. Some devices do not
handle internal buffer overflows correctly. This can cause false
peaks.
Ignore overflow values (recommended): Ignore overflow
values and do not include them in the monitoring data.
Handle overflow values as valid result s: Regard all overflow
values as regular data and include them in the monitoring data.
We recommend using the default value. If you experience
problems, change this option.
Zero Values Define how PRTG will handle zero values. Some devices send
incorrect zero values. This can cause false peaks.
Ignore zero values for delt a sensors (recommended): Ignore
zero values and do not include them in the monitoring data.
Handle zero values as valid result s for delt a sensors: Regard
all zero values as regular data and include them in the monitoring
data.
32-bit/64-bit Counters Define which kind of traffic counters PRTG will search for on a
device.
Use 64-bit count ers if available (recommended): The interface
scan will use 64-bit traffic counters, if available. This can avoid
buffer overflows in the devices.
Use 32-bit count ers only : The interface scan will always use 32-
bit traffic counters, even if 64-bit counters are available. This can
lead to more reliable monitoring for some devices.
Request Mode Define which kind of request method PRTG uses for SNMP sensors.
Use mult i get (recommended): Bundle multiple SNMP requests
into one request.
Use single get : Use one request for each SNMP value. This can
increase compatibility with older devices.
02.02.2015 239

Port Name Template Define how the name of SNMP sensors created on a device will be
put together. Enter a template using several variables. When adding
new sensors, PRTG scans the interface for available counters at
certain OIDs. At each OID usually several fields are available with
interface descriptions. They are different for every device/OID.
PRTG will use the information in these fields to name the sensors. If
a field is empty or not available, an empty string is added to the
name. As default, ([port ]) [ifalias] is set as port name template,
which will create a name such as (001) Ethernet1, for example. You
can use any field names available at a certain OID of your device,
among which are:
[port ]: The port number of the monitored interface.
[ifalias]: The 'alias' name for the monitored interface as specified
by a network manager, providing a non-volatile handling.
[ifname]: The textual name of the monitored interface as
assigned by the local device.
[ifindex]: A unique value, greater than zero, for the monitored
interface.
[ifdescr]: A textual string containing information about the
monitored device or interface, for example, manufacturer,
product name, version.
[ifspeed]: An estimate of the monitored interface's current
bandwidth (KBit/s).
[ifsensor]: The type of the sensor, this is SNMP Traffic or SNMP
RMON. This is useful to differentiate between your SNMP Traffic
1797 and SNMP RMON 1737 sensors.
Combine them as you like to obtain suitable sensor names. See

the More section below for more information about SNMP sensor
names.
Port Name Update Define how PRTG will react if you change port names in your
physical device (e.g. a switch or router). Choose between:
Keep port names (use t his if y ou edit t he names in PRTG): Do
not automatically adjust sensor names. This is the best option if
you want to change names in PRTG manually.
Aut omat ic sensor name updat e if name changes in device: If
PRTG detects changes of port names in your physical device, it
will try to automatically adjust sensor names accordingly. For
detailed information please see More section below.
240 02.02.2015
Port Identification Define which field will be used for SNMP interface identification.
Choose between:
Aut omat ic (recommended): Tries the ifAlias field first to identify
an SNMP interface and then ifDescr. Note: ifName will not be tried
automatically.
Use ifAlias: For most devices ifAlias is the best field to get
unique interface names.
Use ifDescr: Use this option if the port order of your device
changes after a reboot, and there is no ifAlias field available. For
example, this is the best option for Cisco ASA devices. Note:
When using this option it is important that your device returns
unique interface names in the ifDescr field.
Use ifName: You can also use this option if there is no unique
ifAlias available. Note: When using this option it is important that
your device returns unique interface names in the ifName field.
No Port Updat e: Use this option to disable automatic port
identification.
Start Port For SNMP Traffic sensors, define at which port number PRTG will
start to create sensors. Use 0 for automatic. We recommend using
the default value.
End Port For SNMP Traffic sensors, define at which port number PRTG will
stop to create sensors. Use 0 for automatic. We recommend using
the default value.
SNMP Debug Log Define if you want to create an SNMP log file for debugging
purposes. This is only recommended for debugging low level SNMP
issues. Choose between:
No log (recommended): No SNMP debug log file will be created.
Enable debug log: An SNMP log file is written to the Logs
(Debug) directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 2871 section.
02.02.2015 241
242 02.02.2015
SCANNING INTER VAL
Scanning Interval Select a scanning interval (seconds, minutes, or hours) from the
list. The scanning interval determines the time the sensor waits
between two scans. You can change the available intervals in the
system administration 2626 .
When a Sensor Define the number of scanning intervals a sensor has to report an
Reports an Error error until the sensor will be set to a Down status 123 . The sensor
can try reaching a device several times, depending on your setup
you can specify here, to help avoid false alarms if the monitored
device has only temporary issues. For previous scanning intervals
with failed requests, the sensor will show a Warning status.
Choose between:
Set sensor t o "down" immediat ely : The sensor will show an
error after the first failed request.
Set sensor t o "warning" for 1 int erval, t hen set t o
"down" (recommended): After the first failed request, the
sensor will show a yellow warning status. If the following
request also fails, the sensor will show an error.
Set sensor t o "warning" for 2 int ervals, t hen set t o "down":
Show an error status only after three failed requests in a row.
Show an error status only after four failed requests in a row.
Show an error status only after five failed requests in a row.
Show an error status only after six failed requests in a row.
Note: Sensors that monitor via Windows Management
Instrumentation (WMI) always wait at least one scanning interval
until they show an error. It is not possible to set a WMI sensor
"down" immediately, so the first option will not apply to these
sensor types (all other options can apply).
Note: If a sensor has defined error limits for channels, this sensor
will always be set to a Down status immediately, so no "wait"
option will apply.
Note: If a channel uses lookup 2838 values, the sensor will always be
set to a Down status immediately, so no "wait" options will apply.
02.02.2015 243
SCHEDU LES, DEPENDENCIES, AND MAINTENANCE WINDOW
Schedule Select a schedule from the list. Schedules can be used to pause
monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 2593 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Maintenance Window Specify if you want to set-up a one-time maintenance window.

During a maintenance window this object and all child objects will
not be monitored. They will enter a paused state then. Choose
between:
Not set (monit or cont inuously ): No maintenance window will
be set.
Set up a one-t ime maint enance window: Pause monitoring
within a maintenance window.
Maintenance Begins At This field is only visible if maintenance window is enabled above.
Use the date time picker to enter the start date and time of the
maintenance window.
Maintenance End At This field is only visible if maintenance window is enabled above.
Use the date time picker to enter the end date and time of the
maintenance window.
Dependency settings are available only in Probe Settings 248 , Group Settings 266 , Device
Settings 288 , and Sensor Settings 310 .
244 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
CHANNEL U NIT CONFIGU R ATION
Channel Unit Types For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
Bandwidt h
Memory
Disk
File
Cust om
Note: Custom channel types can be set on sensor level only.
02.02.2015 245
AU TOMATIC MONITOR ING DATA ANALYSIS
Unusual Detection Define if unusual detection is enabled for sensors. You can
configure the behavior of unusual detection (or disable it
completely) in the system settings 2627 .
Enabled: Enable unusual detection for this group. Sensors in this
group will turn to orange color if unusual activity is detected.
Disabled: Disable unusual detection for this group. Unusual
values will be ignored for sensors in this group; they will not
show an unusual sensor status.
Similar Sensors Define if similar sensors detection is enabled for sensors. You can
Detection configure the depth of analysis of similar sensors detection (or
disable it completely) in the system settings 2627 .
Enabled: Enable similar sensors detection for this group.
Sensors in this group will be considered during similarity analysis.
Disabled: Disable similar detection for this group. Sensors in this
group will not be taken into account during similarity analysis.
Click on the Save button to store your settings. If you change tabs or use the main menu, all
changes to the settings will be lost!
Notifications
The status or the data of a sensor can trigger notifications. Using this mechanism, you can
configure external alerting tailored to you needs. In an object's detail page, click on the
Not ificat ions tab to change sensor notification triggers. The defined triggers will be inherited
down to sensor level. For detailed information, please see Sensor Not ificat ions Set t ings 2484
section.
Others
For more general information about settings, please see Object Set t ings 143 section.
More
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
246 02.02.2015
Knowledge Base: How can I change the defaults for names automatically generated for new
SNMP sensors?
Knowledge Base: Automatically update port name and number for SNMP Traffic sensors when
the device changes them
02.02.2015 247
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 5 Probe Settings
6.5 Probe Settings

On a probe's overview page, click on the Set t ings tab to change settings.
Add Remote Probe

You can add additional remote probes to your setup to extend you monitoring to networks
that are not directly reachable by your PRTG core installation or cluster.
See Add Remot e Probe 2847 section for more details.
Probe Settings
The following settings are available in the Set t ings tab of every probe. As you may not need
all of these for every probe, just regard those settings you really need, ignoring the others.
We recommend defining as many settings as possible in the Root 232 group, so you can inherit
them to all other objects further down in the tree hierarchy.
BASIC PR OBE SETTINGS
Probe Name Enter a meaningful name to identify the probe. The name will be
or enter key. You can use tags to group objects and use tag-
filtered views later on. Tags are not case sensitive.
Status Choose if monitoring for this probe is started or paused.

St art ed: Monitor this probe.
Paused: Pause monitoring for this probe. All sensors on all
devices on this probe will be paused until this setting is changed
again.
Priority Select a priority for the probe. This setting determines where the
probe will be placed in list views. Top priority will be at the top of a
list. You can choose from one star (low priority) to five stars (top
priority).
248 02.02.2015
Inherited Settings
described below.
LOCATION
enter 49.452778 any 11.077778 text
following.
PRTG's geo map.
02.02.2015 249
between:
250 02.02.2015
sensor settings.
XenServers.
02.02.2015 251
Choose between:
64-bit counters.
Choose between:
device.


252 02.02.2015
algorithm.
algorithm.
is triggered.
Choose between:
02.02.2015 253

functionality.
integer value.
failures.
254 02.02.2015

earlier.
peaks.
data.
device.
into one request.
02.02.2015 255

among which are:
interface.
bandwidth (KBit/s).

names.
256 02.02.2015
Choose between:
automatically.
identification.
the default value.
the default value.
02.02.2015 257
258 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 259
CLU STER U SAGE
Scanning Distribution This box is only visible if you're running a PRTG cluster. Sometimes
you want to exclude a certain node from monitoring the sensors
running on this probe, group, or device, for example, if a device is
not reachable from every node configured in your cluster. In the
list of cluster nodes, please select the nodes that will not be
included in sensor scans. By default, this setting is inherited 88 to
all objects underneath.
Note: Inheritance for schedules, dependencies, and maintenance windows cannot be

interrupted; the according settings from the parent objects will always be active. However,
you can define additional settings here. They will be active in parallel to the parent objects'
settings.
active.

between:
be set.
maintenance window.
Maintenance Ends At This field is only visible if maintenance window is enabled above.
maintenance window.
Dependency Type Define a dependency type. Dependencies can be used to pause

monitoring for an object depending on the status of another. You
can choose between:
260 02.02.2015
Use parent : Pause the current object if its parent object is in a

Down status, or if it is paused by another dependency.
Select object : Pause the current object if its parent object is in
a Down status, or if it is paused by another dependency.
Additionally, pause the current object if a specific other object in
the device tree is in a Down status, or if it is paused by another
dependency. Select below.
Note: Testing your dependencies is easy! Simply choose Simulat e
Error St at us from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused. You can check all dependencies 2514 in your PRTG
installation by selecting Devices | Dependencies from the main
menu bar.
Dependency This field is only visible if the select object option is enabled above.
Click on the reading-glass symbol and use the object selector 160
to choose an object on which the current object will be
dependent on.
Delay (Seconds) Define a time span. After the master object for this dependency
comes back to an Up status, monitoring of the depending objects
will be additionally delayed by the defined time span. This can help
avoid false alarms, for example, after a server restart, by giving
systems more time for all services to start up. Please enter an
integer value in seconds.
02.02.2015 261
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
262 02.02.2015
ADMINISTR ATIVE PR OBE SETTINGS / PR OBE SETTINGS FOR MONITOR ING
Define the IP address used for outgoing monitoring requests.

If there is more than one IP on the current system available, you can specify the IP address
that will be used for outgoing monitoring requests of certain sensor types.
The setting is valid for all monitoring requests sent from this PRTG probe.
This setting will be used for sensors using the following connection types: HTTP, DNS, FTP,
IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. Note: This feature does not support
all sensor types for technical reasons.
This is useful for devices that expect a certain IP address when queried.
Default setting is aut o. PRTG will select an IP address automatically.
Note: If you change this setting, some sensors might stop working. For example, sensors
might show a Down status if the selected IP address is blocked on the way to or directly on
the monitored device.
Outgoing IPv4 Define the IP address for outgoing requests using the IPv4
protocol. The list shows all IP addresses available on the current
system. Choose a specific IP address or select aut o.
02.02.2015 263
ADMINISTR ATIVE PR OBE SETTINGS / PR OBE SETTINGS FOR MONITOR ING
Outgoing IPv6 Define the IP address for outgoing requests using the IPv6
protocol. The list shows all IP addresses available on the current
system. Choose a specific IP address or select aut o. For details
about the basic concept of IPv6 in PRTG, please see IPv6 99
section.
ADMINISTR ATIVE PR OBE SETTINGS: SCHEDU LED R ESTAR TS
Restart Options For best performance, we recommend you to regularly restart the
Windows servers on which PRTG is running. To do this
automatically for PRTG, you can schedule an automatic restart.
Choose between the following options:
Do not perform scheduled reboot /service rest art : Do not
perform any scheduled restart of services automatically. We
recommend a manual restart every few weeks. You can initiate a
restart of your PRTG core server and probes under Sy st em 2653
Administ rat ionAdminist rat ive Tools 2653 in the PRTG web
interface.
Perform scheduled rest art of PRTG services: Restart both
core server and probe service. Enter a schedule below.
Perform scheduled sy st em reboot (recommended): This is the
recommended setting, although not set by default. Enter a
schedule below. We recommend restarting Windows servers
once a month for best performance.
Restart Schedule This setting is only visible if you selected a schedule option above.
Choose how often you want to restart PRTG services or the
Windows server:
Once per week: Select a weekday and time below.
Once per mont h (recommended): Select a day of month and
time below.
Specify Day This setting is only visible if you selected a schedule option above.
Select a specific day of a week (Monday to Sunday) resp. month
(1st to 30th resp. Last). If you select Last , the restart will always be
executed on the last day of the month, regardless of how many
days the month has.
Note: If you select a date that does not exist in every month (for
example, the 30th day in February), PRTG will automatically initiate
the restart on the last day of this month.
264 02.02.2015
ADMINISTR ATIVE PR OBE SETTINGS: SCHEDU LED R ESTAR TS
Specify Hour This setting is only visible if you selected a schedule option above.
Select the time of day when PRTG will perform the restart.
Note: A Windows warning message will be displayed 10 minutes
before restart to inform a logged in user. The actual restart time
can differ up to 30 minutes from the settings you enter below!
Notifications
section.
Others
More
SNMP sensors?
02.02.2015 265
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 6 Group Settings
6.6 Group Settings

On a group's overview page, click on the Set t ings tab to change settings.
Add Group
The Add Group dialog appears when adding a new group to a parent group. It only shows the
setting fields that are imperative for creating the group. Therefore, you will not see all setting
fields in this dialog. For example, the Group St at us option is not available in this step.
You can change all settings in the group's Set t ings tab later.
Group Settings
The following settings are available in the Set t ings tab of every group. As you may not need
all of these for every group, just regard those settings you really need, ignoring the others.
Note: This documentation does not refer to the setting of the special Root group. The
settings available there differ from those described here.
Status Choose if monitoring for this group is started or paused. .We

recommend using the default value. You can add additional tags to
it, if you like.
St art ed: Monitor this group.
Paused: Pause monitoring for this group. All sensors on all
devices in this group will be paused until this setting is changed
again.
or enter key. You can use tags to group objects and use tag-
filtered views later on. Tags are not case sensitive.
266 02.02.2015
Priority Select a priority for the group. This setting determines where the
group will be placed in list views. Top priority will be at the top of a
list. You can choose from one star (low priority) to five stars (top
priority).
GR OU P TYPE
this group. Choose between:
device.
ADSL
Cisco ASA VPN
Dell MDI Disk
DNS Server
Frit zbox
02.02.2015 267
FTP Server
HTTP Web Server
NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
NTP Server
Print er (HP)
RDP Server
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
Windows (via WMI)
268 02.02.2015

X EN Host s

Discovery Schedule Define when the auto-discovery will be run. Choose between:
Once: Perform auto-discovery only once. New devices and
sensors will be added once. You can run auto-discovery manually
any time using an object's context menu 165 .
Hourly : Perform auto-discovery for new devices and sensors
every 60 minutes. Note: Please use this option with caution!
Frequently executed auto-discoveries might cause performance
issues, especially when large network segments are scanned
every hour.
Daily : Perform auto-discovery for new devices and sensors
every 24 hours. The first auto-discovery will run immediately, all
Weekly : Perform auto-discovery for new devices and sensors
every 7 days. The first auto-discovery will run immediately, all
IP Selection Method Define how you want to define the IP range for auto-discovery.
Choose between:
Class C base IP wit h st art /end (IPv4): Define an IPv4 class C
address range.
IP and Subnet (IPv4): Enter an IPv4 address and subnet mask.
IP wit h oct et range (IPv4): Enter an IPv4 address range for every
IP octet individually. With this, you can define very customizable
IP ranges.
02.02.2015 269
Use comput ers from t he act ive direct ory (maximum 1000
comput ers): Search in the active directory for computers to
perform auto-discovery. Note: Define your active directory
domain in advance in the system administration. See Sy st em
Note: Only subnets with up to 65,536 IP addresses can be
discovered! If you define a range with a higher number of
addresses, discovery will stop before it is completed.
IPv4 Base This field is only visible if Class C network detection is selected
above. Enter a class C network as IP base for the auto-discovery.
Enter the first three octets of an IPv4 IP address, for example,
192.168.0
IPv4 Range Start This field is only visible if Class C network detection is selected
above. Enter the IP octet of the class C network specified above
from which PRTG will start the auto-discovery. This will complete
the IP base above to an IPv4 address. For example, enter 1 to
discover from 192.168.0.1.
IPv4 Range End This field is only visible if Class C network detection is selected
above. Enter the IP octet of the class C network specified above at
which PRTG will stop the auto-discovery. This will complete the IP
base above to an IPv4 address. For example, enter 254 to discover
up to 192.168.0.254.
IPv4/DNS Name List This field is only visible if the IP list option is selected above. Enter
IPv6/DNS Name List a list of IP addresses or DNS names which the auto-discovery will
scan. Enter each address in a separate line.
IPv4 and Subnet (IPv4) This field is only visible if the IP and subnet option is selected
above. Enter an expression in the format address/subnet , e.g.
192.168.3.0/255.255.255.0. You can also use the short form like
192.168.3.0/24 in this example. PRTG will scan the complete host
range (without network and broadcast address) defined by the IP
address and the subnet mask.
IP with Octet Range This field is only visible if the octet range option is selected above.
Enter an expression in the format a1.a2.a3.a4, where a1, a2, a3,
and a4 are each a number between 0-255, or a range with two
numbers and a hyphen like 1-127. All permutations of all ranges are
calculated, e.g. 10.0.1-10.1-100 results in 1,000 addresses that
PRTG will scan during auto-discovery.
Organizational Unit This field is only visible if active directory is selected above. Enter
an organizational unit (OU) to restrict the active directory search to
computers which are part of this OU. Just enter the name of the OU
without any other term (i.e., without "OU" in front). If you leave this
field empty, there will not be any restriction.
270 02.02.2015
If you have sub-OUs, consider the correct syntax in the format

Y,OU=X : OUs that are part of another OU have to be listed
together with their parent(s). Enter the sub-OU followed by ,OU=
and the name of the parent OU.
Examples:
Assuming that the organizational unit 'Y' is part of the OU named
'X'. Then the syntax would be Y,OU=X.
For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would
be Z,OU=Y,OU=X.
Note: The order is important, sub-OUs have to be listed left of their

particular parents!
Name Resolution Define how newly discovered devices will be monitored. This only
affects new devices. The setting for existing devices will be kept.
Choose between:
Use DNS / WMI / SNMP names (recommended): Monitor newly
discovered devices via their DNS, WMI, or SNMP names (if
available).
Use IP addresses: Monitor newly discovered devices via their IP
address.
Device Rescan Define if you want to rescan known devices. Choose between:
Skip aut o-discovery for known devices/IPs (recommended):
Do not re-scan known devices or IP addresses, but only scan for
new devices/IPs when auto-discovering. This can avoid re-
creation of manually deleted sensors. PRTG will also avoid adding
devices that are already included elsewhere in your
configuration, e.g. in other groups.
Perform aut o-discovery for known devices/IPs: Re-scan
known devices and IP addresses with every auto-discovery. This
will re-create manually deleted sensors on existing devices.
Inherited Settings
described below.
02.02.2015 271
LOCATION
enter 49.452778 any 11.077778 text
following.
PRTG's geo map.
272 02.02.2015
between:
sensor settings.
02.02.2015 273
XenServers.
274 02.02.2015
Choose between:
64-bit counters.
Choose between:
device.


02.02.2015 275
algorithm.
algorithm.
is triggered.
Choose between:
276 02.02.2015

functionality.
integer value.
failures.
02.02.2015 277

earlier.
peaks.
data.
device.
into one request.
278 02.02.2015

among which are:
interface.
bandwidth (KBit/s).

names.
02.02.2015 279
Choose between:
automatically.
identification.
the default value.
the default value.
280 02.02.2015
02.02.2015 281
SCANNING INTER VAL
Choose between:
option will apply.
282 02.02.2015
CLU STER U SAGE

settings.
active.

between:
be set.
maintenance window.
maintenance window.

can choose between:
02.02.2015 283

menu bar.
dependent on.
284 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 285
NU MBER OF SENSOR S LIMITATION
Sensor Limit This setting allows the administrator to set a limit for the maximum
number of sensors in this group. Subgroups are also included. If
sensors exceed this limitation, they will be paused. This is of
special interest for a Managed Service Provider (MSP). Choose
between:
Allow unlimit ed number of sensors: Disable a limitation of the
number of sensors for this group. Any number of sensors can be
added to this group.
Limit number of sensors in t his group: Enables a limitation of
the number of sensors for this group. Only a limited number of
sensors can be added to this group.
Maximum Number of This field is only visible if limitation is enabled above. Define how
Sensors many sensors can be added to this group. Please enter an integer
value.
286 02.02.2015
Notifications
section.
Others
More
SNMP sensors?
02.02.2015 287
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 7 Device Settings
6.7 Device Settings

On a device's details page, click on the Set t ings tab to change settings.
Add Device
The Add Device dialog appears when adding a new device to a group. It only shows the
setting fields that are imperative for creating the device. Therefore, you will not see all setting
fields in this dialog. For example, the Device St at us option is not available in this step.
You can change all settings in the device's Set t ings tab later.
Device Settings
The following settings are available in the Set t ings tab of every device. As you may not need
all of these for every device, just regard those settings you really need, ignoring the others.
For device settings, there is also multi-edit available. This enables you to change properties of
many devices at a time. For more details, please see Mult i-Edit List s 2506 section.
BASIC DEVICE SETTINGS
Device Name Enter a meaningful name to identify the device. The name will be
shown by default in the device tree and in all alarms.
Status Choose if monitoring for this device is started or paused.

St art ed: Monitor this device.
Paused: Pause monitoring for this device. All sensors on it will be
paused until this setting is changed again.
IP Version Define which IP protocol PRTG will use to connect to this device.
The setting is valid for all sensors created on this device. Choose
between:
device.
device.
288 02.02.2015
BASIC DEVICE SETTINGS
IP Address/DNS Name Enter the IP address (either v4 or v6, depending on your selection
above) or DNS name for the device. Most sensors created on this
device will inherit this setting and they will try to connect to this
address for monitoring. (However, some sensor types still have
their own setting for IP address/DNS name.)
or enter key. You can use tags to group sensors and use tag-
filtered views later on. Tags are not case sensitive. We recommend
using the default value. You can add additional tags to it, if you like.
Priority Select a priority for the sensor. This setting determines where the
sensor will be placed in sensor lists. Top priority will be at the top
of a list. You can choose from one star (low priority) to five stars
(top priority).
ADDITIONAL DEVICE INFOR MATION
Device Icon Choose a device icon from the list. It will be shown in the device
tree. For information on how to add your custom icons, please see
the link in the More 308 section below.
Service URL Specify a URL you would like to open directly when choosing
Device Tools | Go To Service URL from the device's context menu
171 . For example, you can configure this option to call the address
http://www.example.com/service.html. Enter a valid URL or leave

the field empty.
DEVICE TYPE
this device. Choose between:
device.
02.02.2015 289
DEVICE TYPE
Discovery Schedule This option is only visible if one of the auto-discovery options is
selected above. Define when the auto-discovery will be run.
Choose between:
Once: Perform auto-discovery only once. For existing devices,
this will initiate a one-time sensor update for the current device.
Hourly : Perform auto-discovery for new sensors every hour.
Daily : Perform auto-discovery for new sensors every day.
Weekly : Perform auto-discovery for new sensors every week.
ADSL
Cisco ASA VPN
Dell MDI Disk
DNS Server
Frit zbox
FTP Server
HTTP Web Server
290 02.02.2015
DEVICE TYPE

NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
NTP Server
Print er (HP)
RDP Server
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
Windows (via WMI)
X EN Host s
02.02.2015 291
DEVICE TYPE

Inherited Settings
described below.
LOCATION
enter 49.452778 any 11.077778 text
following.
PRTG's geo map.
292 02.02.2015
between:
02.02.2015 293
sensor settings.
294 02.02.2015
XenServers.
Choose between:
64-bit counters.
02.02.2015 295
Choose between:
device.


algorithm.
algorithm.
296 02.02.2015
is triggered.
CR EDENTIALS FOR DATABASE MANAGEMENT SYSTEMS
The settings you define in this section apply to the following sensors:
My SQL v2 Sensor 919
Post greSQL Sensor 1107
For Databases Use Define which ports PRTG will use for connections to the monitored
Port databases. Choose between:
Set aut omat ically (default port , recommended): PRTG
automatically determines the type of the monitored database and
uses the corresponding default port to connect. See below for a
list of default ports.
Define one cust om port valid for all dat abase sensors:
Choose this option if your database management systems do
not use the default ports. Define the port for database
connections manually below. If you choose this option, PRTG will
use the custom port for all database sensors.
If you choose the automatic port selection, PRTG uses the
following default ports:
Microsoft SQL: 1433
MySQL: 3306
Oracle SQL: 1521
PostgreSQL: 5432
Port Enter the number of the port that PRTG will use for database
connections. Please enter an integer value.
Note: All your database sensors will use this port to connect!
Authentication Select the authentication method for the connection to the SQL
database. Choose between:
02.02.2015 297
CR EDENTIALS FOR DATABASE MANAGEMENT SYSTEMS
Windows aut hent icat ion wit h impersonat ion: If you select this
option, PRTG uses the Windows credentials as defined in the
particular device settings 292 for the database connection.
Note: The user whose credentials are used needs to have
permissions to log on to the system on which the PRTG probe
with a database sensor runs. This is required for the
impersonation.
SQL server aut hent icat ion: Choose this option if you want to
use explicit credentials for database connections.
User This field is only visible if you select SQL server authentication
above. Enter the username for the database connection.
Password This field is only visible if you selected SQL server authentication
above. Enter the password for the database connection.
Timeout (Sec.) Enter a timeout in seconds for the request. Please enter an integer
value. If the reply takes longer than this value defines, the sensor
cancels the request and triggers an error message. The maximum
timeout value is 300 seconds (15 minutes).
Choose between:
functionality.
298 02.02.2015
integer value.
failures.
earlier.
peaks.
02.02.2015 299

data.
device.
into one request.
300 02.02.2015
among which are:
interface.
bandwidth (KBit/s).

names.
Choose between:
02.02.2015 301

automatically.
identification.
the default value.
the default value.
302 02.02.2015
02.02.2015 303
SCANNING INTER VAL
Choose between:
option will apply.
304 02.02.2015
CLU STER U SAGE

settings.
active.

between:
be set.
maintenance window.
maintenance window.

can choose between:
02.02.2015 305

menu bar.
dependent on.
306 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 307
Notifications
section.
Others
More
308 02.02.2015
SNMP sensors?
02.02.2015 309
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings
6.8 Sensor Settings

There are more than 200 different sensor types available. In the Add Sensor dialog, all sensors
are categorized into groups to help you quickly find what you need. Once you are familiar with
the interface, you will probably enter the first letters of a sensor type's name into the Search
field in the upper left corner and get to a sensor even faster.
Available Sensor Types

There is a dedicated manual section for every sensor type with details about the available
settings. For more information, please see List of Available Sensors 311 section.
For sensor settings, there is also multi-edit available. This enables you to change properties of
many sensors at a time. For more details, please see Mult i-Edit List s 2506 section.
In order to detect unexpected correlations between your network components, PRTG

provides a Similar Sensors 139 analysis.
Sensor Settings Overview

For information about sensor settings, please see the following sections:
Sensor Set t ings 310 List of Available Sensor Ty pes 311
Sensor Channels Set t ings 2477
Sensor Not ificat ions Set t ings 2484
310 02.02.2015
1 List of Available Sensor Types
6.8.1 List of Available Sensor Ty pes
This chapter lists all available sensors, arranged both by different categories and in alphabetical
order. Note: In the Add a Sensor 228 assistant, PRTG offers you various options to filter for
fitting sensor types easily.
Common Sensors 311
Bandwidth Monitoring Sensors 312
Web Servers (HTTP) Sensors 312
SNMP Sensors 313
Windows WMI/Performance Counters Sensors 315
Linux/Unix/OS X Sensors 316
Virtual Servers Sensors 317
Mail Servers Sensors 317
Database Servers Sensors 318
File Servers Sensors 318
Various Servers Sensors 319
VoIP and QoS Sensors 319
Hardware Parameters Sensors 320
Custom Sensors 321
PRTG Internal Sensors 322
All Sensors in Alphabetical Order 322
More 329
Common Sensors
Cloud Ping Sensor 408
HTTP Sensor 610
Ping Sensor 1047
Port Sensor 1090
02.02.2015 311
Bandwidth Monitoring Sensors

AVM FRITZ!Box WAN Interface v2 Sensor 361
IPFIX Sensor 820
jFlow V5 Sensor 851
Packet Sniffer Sensor 999
sFlow Sensor 1208
Web Servers (HTTP) Sensors

Google Analytics Sensor 600
HTTP Sensor 610
HTTP Advanced Sensor 619
HTTP Apache ModStatus PerfStats Sensor 634
HTTP Apache ModStatus Totals Sensor 644
HTTP Content Sensor 653
HTTP Full Web Page Sensor 664
HTTP Push Count Sensor 675
HTTP Push Data Sensor 683
312 02.02.2015
HTTP Push Data Advanced Sensor 693
HTTP SSL Certificate Expiry Sensor 703
HTTP Transaction Sensor 713
HTTP XML/REST Value Sensor 726
Windows IIS Application Sensor 2085
SNMP Sensors
SNMP Cisco ASA VPN Connections Sensor 1307
SNMP Cisco ASA VPN Users Sensor 1327
SNMP HP ProLiant Logical Disk Sensor 1473
02.02.2015 313
SNMP IBM System X Logical Disk Sensor 1519
SNMP interSeptor Pro Environment Sensor 1555
SNMP Poseidon Environment Sensor 1696
SNMP Printer Sensor 1704
SNMP QNAP Logical Disk Sensor 1712
SNMP Synology Logical Disk Sensor 1764
SNMP System Uptime Sensor 1789
314 02.02.2015
SNMP Windows Service Sensor 1820
Windows WMI/Performance Counters Sensors

Active Directory Replication Errors Sensor 330
Event Log (Windows API) Sensor 473
PerfCounter Custom Sensor 1028
PerfCounter IIS Application Pool Sensor 1037
Windows IIS Application Pool Sensor 1037
Windows CPU Load Sensor 2058
Windows Last Update (Remote Registry) Sensor 2095
Windows Logged In Users Sensor 2104
Windows MSMQ Queue Length Sensor 2112
Windows Pagefile Sensor 2132
Windows Physical Disk Sensor 2141
Windows Print Queue Sensor 2151
Windows Process Sensor 2161
Windows Registry Sensor 2171
Windows Scheduled Task Sensor 2181
Windows System Uptime Sensor 2191
Windows Updates Status (Powershell) Sensor 2200
WMI Event Log Sensor 2230
WMI Free Disk Space (Multi Disk) Sensor 2269
02.02.2015 315
WMI Memory Sensor 2300
WMI Remote Ping Sensor 2356
WMI Security Center Sensor 2364
WMI Service Sensor 2373
WMI Share Sensor 2383
WMI SharePoint Process Sensor 2393
WMI Terminal Services (Windows 2008) Sensor 2402
WMI Terminal Services (Windows XP/Vista/2003) Sensor 2410
WMI UTC Time Sensor 2418
WMI Vital System Data (V2) Sensor 2426
WMI Windows Version Sensor 2455
WSUS Statistics Sensor 2464
Linux/Unix/OS X Sensors
SSH Disk Free Sensor 1835
SSH INodes Free Sensor 1847
SSH Load Average Sensor 1856
SSH Meminfo Sensor 1865
SSH Remote Ping Sensor 1874
SSH Script Advanced Sensor 1933
316 02.02.2015
Virtual Servers Sensors

Amazon CloudWatch Sensor 350
Citrix XenServer Host Sensor 379
Citrix XenServer Virtual Machine Sensor 390
Hyper-V Cluster Shared Volume Disk Free Sensor 740
Hyper-V Host Server Sensor 750
Hyper-V Virtual Machine Sensor 758
Hyper-V Virtual Network Adapter Sensor 769
Hyper-V Virtual Storage Device Sensor 780
SCVMM Host Sensor 1169
SCVMM Virtual Machine Sensor 1180
SSH VMWare ESX(i) Disk Sensor 1943
Virtuozzo Container Disk Sensor 1997
Virtuozzo Container Network Sensor 2005
VMware Host Hardware (WBEM) Sensor 2012
VMware Host Hardware Status (SOAP) Sensor 2020
VMware Host Performance (SOAP) Sensor 2029
VMware Virtual Machine (SOAP) Sensor 2039
Mail Servers Sensors

Exchange Backup (Powershell) Sensor 483
Exchange Database (Powershell) Sensor 493
Exchange Mail Queue (Powershell) Sensor 503
Exchange Mailbox (Powershell) Sensor 513
Exchange Public Folder (Powershell) Sensor 523
IMAP Sensor 789
IP on DNS Blacklist Sensor 811
POP3 Sensor 1072
POP3 Email Count Sensor 1081
SMTP Sensor 1257
02.02.2015 317
SMTP&IMAP Round Trip Sensor 1266
SMTP&POP3 Round Trip Sensor 1278
Database Servers Sensors

ADO SQL Sensor 340
Microsoft SQL Sensor 880
MongoDB System Health Sensor 902
MySQL Sensor 910
MySQL v2 Sensor 919
Oracle SQL Sensor 976
PostgreSQL Sensor 1107
File Servers Sensors

File Sensor 555
File Content Sensor 564
Folder Sensor 573
FTP Sensor 582
FTP Server File Count Sensor 590
INI File Content Check Sensor 803
SFTP Secure File Transfer Protocol Sensor 1231
318 02.02.2015
Share Disk Free Sensor 1240
TFTP Sensor 1981
WMI Free Disk Space (Multi Drive) Sensor 2269
Various Servers Sensors

DHCP Sensor 446
DNS Sensor 455
IPMI System Health Sensor 841
LDAP Sensor 873
Ping Sensor 1047
Ping Jitter Sensor 1056
Pingdom Sensor 1064
Port Sensor 1090
RADIUS Sensor 1145
RADIUS v2 Sensor 1152
RDP (Remote Desktop) Sensor 1161
SNTP Sensor 1828
Syslog Receiver Sensor 1963
Traceroute Hop Count Sensor 1989
VoIP and QoS Sensors

Cisco IP SLA Sensor 370
02.02.2015 319
SIP Options Ping Sensor 1248
QoS (Quality of Service) One Way Sensor 1127
QoS (Quality of Service) Round Trip Sensor 1135
Hardware Parameter Sensors

320 02.02.2015
Custom Sensors
EXE/Script Sensor 533
EXE/Script Advanced Sensor 545
Pingdom Sensor 1064
Sensor Factory Sensor 1190
02.02.2015 321
PRTG Internal Sensors

ClusterState Sensor 415
Core Health Sensor 420
Probe Health Sensor 1120
System Health Sensor 1975
All Sensors in Alphabetical Order

The version numbers show when the respective sensor type was originally introduced to
PRTG.
Active Directory Replication Errors Sensor 330 (v8.3.0)

ADO SQL Sensor 340 (v8.1.0)
Amazon CloudWatch Sensor 350 (v7)
AVM FRITZ!Box WAN Interface v2 Sensor 361 (v14.x.13)
Cisco IP SLA Sensor 370 (v7)
Citrix XenServer Host Sensor 379 (v12.x.1)
Citrix XenServer Virtual Machine Sensor 390 (v8.1.0)
Cloud HTTP Sensor 399 (v14.x.14)
Cloud Ping Sensor 408 (v14.x.14)
ClusterState Sensor 415 (v9.1.0)
Core Health Sensor 420 (v9.1.0)
Dell PowerVault MDi Logical Disk Sensor 427 (v12.x.1)
Dell PowerVault MDi Physical Disk Sensor 436 (v14.x.13)
DHCP Sensor 446 (v8.2.0)
DNS Sensor 455 (v7)
Enterprise Virtual Array Sensor 463 (v13.x.6)
Event Log (Windows API) Sensor 473 (v7)
Exchange Backup (Powershell) Sensor 483 (v13.x.5)
Exchange Database (Powershell) Sensor 493 (v13.x.5)
Exchange Mail Queue (Powershell) Sensor 503 (v13.x.5)
Exchange Mailbox (Powershell) Sensor 513 (v13.x.5)
322 02.02.2015
Exchange Public Folder (Powershell) Sensor 523 (v13.x.5)

EXE/Script Sensor 533 (v7)
EXE/Script Advanced Sensor 545 (v7)
File Sensor 555 (v7)
File Content Sensor 564 (v7)
Folder Sensor 573 (v7)
FTP Sensor 582 (v7)
FTP Server File Count Sensor 590 (v8.3.0)
Google Analytics Sensor 600 (v12.x.1)
HTTP Sensor 610 (v7)
HTTP Advanced Sensor 619 (v7)
HTTP Apache ModStatus PerfStats Sensor 634 (v12.x.3)
HTTP Apache ModStatus Totals Sensor 644 (v12.x.3)
HTTP Content Sensor 653 (v7)
HTTP Full Web Page Sensor 664 (v7)
HTTP Push Count Sensor 675 (v13.4.8)
HTTP Push Data Sensor 683 (v14.1.9)
HTTP Push Data Advanced Sensor 693 (14.1.10)
HTTP SSL Certificate Expiry Sensor 703 (v8.3.0)
HTTP Transaction Sensor 713 (v7)
HTTP XML/REST Value Sensor 726 (v8.3.0)
Hyper-V Cluster Shared Volume Disk Free Sensor 740 (v12.3.4)
Hyper-V Host Server Sensor 750 (v7)
Hyper-V Virtual Machine Sensor 758 (v7)
Hyper-V Virtual Network Adapter Sensor 769 (v9.1.0)
Hyper-V Virtual Storage Device Sensor 780 (v12.4.4)
IMAP Sensor 789 (v7)
INI File Content Check Sensor 803 (v8.3.0)
IP on DNS Blacklist Sensor 811 (v8.3.0)
IPFIX Sensor 820 (v13.x.7)
IPFIX (Custom) Sensor 831 (v13.x.7)
IPMI System Health Sensor 841 (v14.x.11)
jFlow V5 Sensor 851 (v8.2.0)
jFlow V5 (Custom) Sensor 863 (v8.2.0)
02.02.2015 323
LDAP Sensor 873 (v8.1.0)

Microsoft SQL Sensor 880 (v7)
Microsoft SQL v2 Sensor 889 (v14.x.12)
MongoDB System Health Sensor 902 (14.x.13)
MySQL Sensor 910 (v7)
MySQL v2 Sensor 919 (v14.x.12)
NetFlow V5 Sensor 931 (v7)
NetFlow V5 (Custom) Sensor 943 (v7)
NetFlow V9 Sensor 954 (v7)
NetFlow V9 (Custom) Sensor 966 (v7)
Oracle SQL Sensor 976 (v7)
Oracle SQL v2 Sensor 986 (v14.x.13)
Packet Sniffer Sensor 999 (v7)
Packet Sniffer (Custom) Sensor 1010 (v7)
Passive Application Performance Sensor 1020 (v13.x.4)
PerfCounter Custom Sensor 1028 (v12.x.3)
PerfCounter IIS Application Pool Sensor 1037 (v12.x.6)
Ping Sensor 1047 (v7)
Ping Jitter Sensor 1056 (v8.3.0)
Pingdom Sensor 1064 (v8.4.0)
POP3 Sensor 1072 (v7)
POP3 Email Count Sensor 1081 (v8.3.0)
Port Sensor 1090 (v7)
Port Range Sensor 1099 (v12.x.4)
PostgreSQL Sensor 1107 (v14.x.12)
Probe Health Sensor 1120 (v9.1.0)
QoS (Quality of Service) One Way Sensor 1127 (v7)
QoS (Quality of Service) Round Trip Sensor 1135 (v9.1.0)
RADIUS Sensor 1145 (v7)
RADIUS v2 Sensor 1152 (v14.x.13)
RDP (Remote Desktop) Sensor 1161 (v7)
SCVMM Host Sensor 1169 (v12.x.6)
SCVMM Virtual Machine Sensor 1180 (v12.x.6)
Sensor Factory Sensor 1190 (v7)
324 02.02.2015
sFlow Sensor 1208 (v7)

sFlow (Custom) Sensor 1220 (v7)
SFTP Secure File Transfer Protocol Sensor 1231 (v12.x.6)
Share Disk Free Sensor 1240 (v7)
SIP Options Ping Sensor 1248 (v12.x.1)
SMTP Sensor 1257 (v7)
SMTP&IMAP Round Trip Sensor 1266 (v7)
SMTP&POP3 Round Trip Sensor 1278 (v7)
SNMP APC Hardware Sensor 1290 (v9.1.0)
SNMP Cisco ADSL Sensor 1299 (v12.x.1)
SNMP Cisco ASA VPN Connections Sensor 1307 (v12.x.1)
SNMP Cisco ASA VPN Traffic Sensor 1317 (v12.x.1)
SNMP Cisco ASA VPN Users Sensor 1327 (v12.x.5)
SNMP Cisco CBQoS Sensor 1337 (v13.x.5)
SNMP Cisco System Health Sensor 1346 (v12.x.4)
SNMP Cisco UCS Blade Sensor 1355 (v14.x.14)
SNMP Cisco UCS Chassis Sensor 1356 (v13.x.8)
SNMP Cisco UCS Physical Disk Sensor 1365 (v14.1.10)
SNMP Cisco UCS System Health Sensor 1373 (v13.x.8)
SNMP CPU Load Sensor 1382 (v12.x.4)
SNMP Custom Lookup Sensor 1390 (v14.x.14)
SNMP Custom Sensor 1391 (v7)
SNMP Custom String Sensor 1400 (v9.1.0)
SNMP Dell Hardware Sensor 1411 (v7)
SNMP Dell PowerEdge Physical Disk Sensor 1420 (v12.x.4)
SNMP Dell PowerEdge System Health Sensor 1429 (v12.x.4)
SNMP Disk Free Sensor 1439 (v12.x.4)
SNMP GSA System Health Sensor 1447 (v13.x.5)
SNMP Hardware Status Sensor 1456 (v13.x.5)
SNMP HP LaserJet Hardware Sensor 1464 (v9.1.0)
SNMP HP ProLiant Logical Disk Sensor 1473 (v12.x.6)
SNMP HP ProLiant Memory Controller Sensor 1482 (v12.x.6)
SNMP HP ProLiant Network Interface Sensor 1491 (v12.x.4)
SNMP HP ProLiant Physical Disk Sensor 1500 (v12.x.6)
02.02.2015 325
SNMP HP ProLiant System Health Sensor 1509 (v12.x.4)

SNMP IBM System X Logical Disk Sensor 1519 (v13.x.4)
SNMP IBM System X Physical Disk Sensor 1528 (v13.x.4)
SNMP IBM System X Physical Memory Sensor 1537 (v13.x.4)
SNMP IBM System X System Health Sensor 1546 (v13.x.4)
SNMP interSeptor Pro Environment Sensor 1555 (v14.1.10)
SNMP LenovoEMC Physical Disk Sensor 1563 (v13.x.8)
SNMP LenovoEMC System Health Sensor 1571 (v13.x.8)
SNMP Library Sensor 1579 (v7)
SNMP Linux Disk Free Sensor 1590 (v8.1.0)
SNMP Linux Load Average Sensor 1602 (v8.1.0)
SNMP Linux Meminfo Sensor 1610 (v8.1.0)
SNMP Linux Physical Disk Sensor 1618 (v13.x.5)
SNMP Memory Sensor 1626 (v12.x.4)
SNMP NetApp Disk Free Sensor 1634 (v12.x.3)
SNMP NetApp Enclosure Sensor 1643 (v12.x.4)
SNMP NetApp I/O Sensor 1653 (v12.x.3)
SNMP NetApp License Sensor 1662 (v12.x.4)
SNMP NetApp Logical Unit Sensor 1670 (v13.x.7)
SNMP NetApp Network Interface Sensor 1679 (v12.x.3)
SNMP NetApp System Health Sensor 1687 (v12.x.3)
SNMP Poseidon Environment Sensor 1696 (v13.x.5)
SNMP Printer Sensor 1704 (v14.x.11)
SNMP QNAP Logical Disk Sensor 1712 (v13.x.4)
SNMP QNAP Physical Disk Sensor 1720 (v13.x.4)
SNMP QNAP System Health Sensor 1729 (v13.x.4)
SNMP RMON Sensor 1737 (v12.x.1)
SNMP SonicWALL System Health Sensor 1747 (v13.x.5)
SNMP SonicWALL VPN Traffic Sensor 1755 (v13.x.6)
SNMP Synology Logical Disk Sensor 1764 (v13.x.4)
SNMP Synology Physical Disk Sensor 1772 (v13.x.4)
SNMP Synology System Health Sensor 1780 (v13.x.4)
SNMP System Uptime Sensor 1789 (v7)
SNMP Traffic Sensor 1797 (v7)
326 02.02.2015
SNMP Trap Receiver Sensor 1808 (v7)

SNMP Windows Service Sensor 1820 (v13.x.8)
SNTP Sensor 1828 (v8.1.0)
SSH Disk Free Sensor 1835 (v8.1.0)
SSH INodes Free Sensor 1847 (v8.1.1)
SSH Load Average Sensor 1856 (v8.1.0)
SSH Meminfo Sensor 1865 (v8.1.0)
SSH Remote Ping Sensor 1874 (v12.x.1)
SSH SAN Enclosure Sensor 1883 (v14.x.12)
SSH SAN Logical Disk Sensor 1893 (v14.1.9)
SSH SAN Physical Disk Sensor 1902 (v14.1.9)
SSH SAN System Health Sensor 1912 (v14.1.9)
SSH Script Sensor 1922 (v12.x.1)
SSH Script Advanced Sensor 1933 (v12.x.6)
SSH VMWare ESX(i) Disk Sensor 1943 (v8.2.0)
SSL Security Check Sensor 1955 (v14.x.12)
Syslog Receiver Sensor 1963 (v7)
System Health Sensor 1975 (v9.1.0)
TFTP Sensor 1981 (v8.1.0)
Traceroute Hop Count Sensor 1989 (v8.3.0)
Virtuozzo Container Disk Sensor 1997 (v8.2.1)
Virtuozzo Container Network Sensor 2005 (v8.2.1)
VMware Host Hardware (WBEM) Sensor 2012 (v8.1.0)
VMware Host Hardware Status (SOAP) Sensor 2020 (v12.x.1)
VMware Host Performance (SOAP) Sensor 2029 (v12.x.1)
VMware Virtual Machine (SOAP) Sensor 2039 (v7)
WBEM Custom Sensor 2049 (v8.1.0)
Windows CPU Load Sensor 2058 (v7)
Windows IIS 6.0 SMTP Received Sensor 2067 (v8.1.0)
Windows IIS 6.0 SMTP Sent Sensor 2076 (v8.1.0)
Windows IIS Application Sensor 2085 (v12.x.1)
Windows Last Update (Remote Registry) Sensor 2095 (v8.3.0)
Windows Logged In Users Sensor 2104 (v8.3.0)
Windows MSMQ Queue Length Sensor 2112 (v8.3.0)
02.02.2015 327
Windows Network Card Sensor 2122 (v7)

Windows Pagefile Sensor 2132 (v12.x.4)
Windows Physical Disk Sensor 2141 (v9.1.0)
Windows Print Queue Sensor 2151 (v8.3.0)
Windows Process Sensor 2161 (v7)
Windows Registry Sensor 2171 (v9.1.0)
Windows Scheduled Task Sensor 2181 (v9.1.1)
Windows System Uptime Sensor 2191 (v8.1.0)
Windows Updates Status (Powershell) Sensor 2200 (v13.x.6)
WMI Custom Sensor 2209 (v7)
WMI Custom String Sensor 2219 (v12.x.4)
WMI Event Log Sensor 2230 (v7)
WMI Exchange Server Sensor 2241 (v7.1.1)
WMI Exchange Transport Queue Sensor 2251 (v12.x.1)
WMI File Sensor 2261 (v7)
WMI Free Disk Space (Multi Disk) Sensor 2269 (v7)
WMI HDD Health Sensor 2280 (v12.x.1)
WMI Memory Sensor 2300 (v7)

WMI Microsoft SQL Server 2005 Sensor 2308 (v8.1.0)
WMI Microsoft SQL Server 2008 Sensor 2320 (v8.1.0)
WMI Microsoft SQL Server 2012 Sensor 2332 (v12.x.6)
WMI Microsoft SQL Server 2014 Sensor 2344 (v14.x.13)
WMI Remote Ping Sensor 2356 (v12.x.1)
WMI Security Center Sensor 2364 (v9)
WMI Service Sensor 2373 (v7)
WMI Share Sensor 2383 (v8.1.0)
WMI SharePoint Process Sensor 2393 (v12.x.1)
WMI Terminal Services (Windows 2008) Sensor 2402 (v8.1.0)
WMI Terminal Services (Windows XP/Vista/2003) Sensor 2410 (v8.1.0)
WMI UTC Time Sensor 2418 (v9.2.0)
WMI Vital System Data (V2) Sensor 2426 (v7)
WMI Volume Sensor 2436 (v7)
WMI Volume Fragmentation Sensor 2445 (v13.x.8)
328 02.02.2015
WMI Windows Version Sensor 2455 (v8.3.0)

WSUS Statistics Sensor 2464 (v9.1.0)
More
Did not find what you are looking for? Have a look into the Additional Sensor Types (Custom
Sensors) 2474 section.
02.02.2015 329
2 Active Directory Replication Errors Sensor
6.8.2 Active Directory Replication Errors Sensor
The Active Directory Replication Errors sensor uses the Windows credentials of its parent
device to check domain controllers for replication errors.
It can show the following:
Number of consecutive sync failures

If the source is deleted
If the scheduled sync is disabled
Time of the last sync attempt
Result of the last sync
Time of the last sync success
Number of modified consecutive sync failures
Number of pending replication operations
Which channels the sensor actually shows might depend on the monitored device and the
sensor setup.
330 02.02.2015
Ac tiv e Direc tory Replic taion Errors Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ac tiv e_direc tory _replic ation_errors.png
Remarks
Requires 332 valid Windows domain credentials in the settings of the parent device 292 .
Requires 332 the probe system to be part of the domain whose AD you monitor.
Requires 332 .NET 4.0 or higher on the probe system.
We recommend Windows 2012 R2 on the probe system for best performance of this sensor.
This sensor type uses lookups to determine the status values of some sensor channels. For
details, please see manual section Define Lookups 2838 .
Note: This sensor type can have a high impact on the performance of your monitoring
system. Please use it with care! We recommend using not more than 50 sensors, on each
probe, of this type of sensor.
02.02.2015 331
Requirement: .NET Framework

This sensor type requires the Microsoft .NET Framework to be installed on the computer
running the PRTG probe: Either on the local system (on every node, if on a cluster probe), or
on the system running the remote probe 2848 . If the framework is missing, you cannot create
this sensor. Note: You need to install the exact version required (a higher version will usually
not work; an exception applies to .NET 3.5 which comprises .NET 2.0 and .NET 3.0). Generally, it
is possible to run several .NET Framework versions on the same machine side-by-side. Please
install the latest update available for the required version.
Required .NET version: 4.0 (with latest update). Please see section More below for details.
Requirement: Member of Windows Domain

This sensor only works if the computer running the PRTG probe is part of the domain whose
Active Directory you want to monitor. The probe runs either on the local system (on every
node, if on a cluster probe), or on another system as remote probe 2848 . If this requirement is
not met, the sensor will not work.
Requirement: Windows Credentials

Requires credentials for Windows systems to be defined for the device you want to use the
sensor on. In the parent device's 292 Credent ials for Windows Sy st ems settings, please
prefer using Windows domain credentials.
Note: If you use local credentials, please make sure the same Windows user accounts (with
same username and password) exist on both the system running the PRTG probe and the
target computer. Otherwise the sensor cannot connect correctly.
Note: Your Windows credentials may not contain any double quotation marks ("). If they do,
this sensor will not work!
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 228 . It only
shows the setting fields that are imperative for creating the sensor. Therefore, you will not see
all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later.
Select the replications you want to monitor. PRTG creates one sensor for each replication
neighbor you choose in the Add Sensor dialog. The settings you make in this dialog are valid
for all of the sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
332 02.02.2015
SENSOR SETTINGS
Replication Neighbor Select the replication neighbor whose replication you want to add
a sensor for. You see a list with the names of all items which are
available to monitor. Select the desired items by adding check
marks in front of the respective lines. PRTG creates one sensor for
each selection. You can also select and deselect all items by using
the check box in the table head.
Sensor Settings
On the details page of a sensor, click on the Set t ings tab to change its settings.
Note: Usually, a sensor connects to the IP Address or DNS Name of the parent device on
which you created this sensor. See section Device Set t ings 288 for details. For some sensor
types, you can define the monitoring target explicitly in the sensor settings. Please see below
for details about available settings.
BASIC SENSOR SETTINGS
Sensor Name Enter a meaningful name to identify the sensor. By default, PRTG
shows this name in the device tree 111 , and in alarms 145 , logs 148 ,
notifications 2521 , reports 2549 , maps 2569 , libraries 2533 , and tickets 150 .
Tags Enter one or more tags, separated by space or comma. You can
use tags to group sensors and use tag-filtered views later on. Tags
are not case sensitive. We recommend using the default value. You
can add additional tags to it, if you like. Other tags are
automatically inherited 90 from objects further up in the device
tree. Those are not visible here.
sensor is placed in sensor lists. Top priority is at the top of a list.
You can choose from one star (low priority) to five stars (top
priority).
SENSOR SETTINGS
Replication Neighbor Shows the replication neighbor whose replication this sensor
monitors. Once a sensor is created, you cannot change this value.
It is shown for reference purposes only. If you need to change this,
please add the sensor anew.
02.02.2015 333
DEBU G OPTIONS
Sensor Result Define what PRTG will do with the result of the sensor. Choose
between:
Discard sensor result : Do not store the sensor result.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (on the Master node, if in a cluster). File
name: Result of Sensor [ID].txt. This is for debugging purposes.
The file will be overridden with each scanning interval. For
information on how to find the folder used for storage, please
see Dat a St orage 2871 section.
SENSOR DISPLAY
Primary Channel Select a channel from the list to define it as the primary channel. In
the device tree, the last value of the primary channel will always be
displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor. Note: You
can set another primary channel later by clicking on the pin symbol
of a channel in the sensor's overview tab.
Chart Type Define how different channels will be shown for this sensor.
Show channels independent ly (default ): Show an own graph
for each channel.
St ack channels on t op of each ot her: Stack channels on top
of each other to create a multi-channel graph. This will generate
an easy-to-read graph which visualizes the different components
of your total traffic. Note: This option cannot be used in
combination with manual Vertical Axis Scaling (available in the
Sensor Channels Set t ings 2477 settings).
Stack Unit This setting is only available if stacked graphs are selected above.
Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
described below.
334 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 335

settings.
Schedule Select a schedule from the list. Schedules can be used to monitor
for a certain time span (days, hours) throughout the week. With the
period list option it is also possible to pause monitoring for a
specific time span. You can create new schedules and edit existing
ones in the account settings 2593 .
Note: Schedules are generally inherited. New schedules will be
added to existing ones, so all schedules are active.

between:
be set.
within a maintenance window. You can define a time span for a
monitoring pause below and change it even for a running
maintenance window.
Note: To terminate a current maintenance window before the
defined end date, you can change the time in Maint enance End At
field to a date in the past.
maintenance window.
maintenance window.

can choose between:
Use parent : Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another dependency.
Select object : Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
336 02.02.2015
Mast er object for parent : Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
menu bar.
to choose an object on which the current sensor will be
dependent on.
integer value in seconds. Note: This setting is not available if you
choose this sensor to be the Mast er object for parent . In this
case, please define delays in the parent Device Set t ings 288 or the
superior Group Set t ings 266 .
02.02.2015 337
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
338 02.02.2015
More
Edit Sensor Channels

To change display settings, spike filter, and limits, switch to the sensor's Overview tab and
click the gear icon of a specific channel. For detailed information, please see Sensor Channels
Set t ings 2477 section.
Notifications
Click the Not ificat ions tab to change notification triggers. For detailed information, please
see Sensor Not ificat ions Set t ings 2484 section.
Others
02.02.2015 339
3 ADO SQL Sensor
6.8.3 ADO SQL Sensor
The ADO SQL sensor monitors a database using an ActiveX Data Objects (ADO) connection
and executes an Structured Query Language (SQL) query.
Response time of the server

Number of records which were affected by the SQL query
The resulting value of the SQL query in the sensor message
sensor setup.
ADO SQL Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ado_sql.png
Remarks
For security reasons, this sensor requires Windows credentials defined in the settings of the
parent device 292 . With these credentials, the PRTG probe must be able to connect to the
Windows domain. If you do not enter valid credentials, the sensor shows the error message
"Access denied" when scanning.
For details, please see the Knowledge Base: How do I correctly configure credentials for
ADO SQL sensors?
340 02.02.2015
3 ADO SQL Sensor
Knowledge Base: Monitoring (Almost) Any SQL Server Through ADO with PRTG Network
Monitor
Add Sensor
Sensor Settings
priority).
ADO SPECIFIC DATA
Timeout (Sec.) Enter a timeout in seconds for the request. If the reply takes
longer than this value defines, the sensor will cancel the request
and show a corresponding error message. Please enter an integer
value. The maximum value is 900 seconds (15 minutes).
02.02.2015 341
3 ADO SQL Sensor
ADO SPECIFIC DATA
Connection String Enter the string that the sensor uses to connect to the database.
For example, such a string could be: Provider=SQLOLEDB.1;Data
Source=10.0.0.200\SQLEXPRESS;User
ID=user;Password=userpass;Initial Catalog=Northwind.
For more information on how to build connection strings, please
see More 348 section below.
DATA
SQL Expression Enter a valid SQL statement to execute on the server. In your
SELECT statement, please specify the field name explicitly. Do not
use SELECT *!
For example, a correct expression could be: SELECT AVG(UnitPrice)
FROM Products. When the request returns a cursor (for example,
with a SELECT statement), the sensor processes only the first row
of data.
Record Count If you want to know how many records in your database were
affected by your SQL expression as defined above, you can count
the number of concerned records. Choose between:
Do not count number of records: Disable the counting of
affected records. The "Record Count" channel always shows "0" if
you choose this option.
Count number of records: Show the number of affected
records in the "Record Count" channel.
Note: Enabling this option might increase the execution time of
this sensor.
Post-Processing If the SQL expression returns a result set, define if you want to
further process it. Choose between:
Ignore result set : Do not process the data returned.
Process numerical result : Regard the result set returned as
integer or float. You can set the sensor to Warning or Down
status for specific thresholds. Define below.
Process st ring result : Regard the result set returned as a
string. You can set the sensor to error for certain sub-strings
contained or missing. Define below.
342 02.02.2015
3 ADO SQL Sensor
Monit or for changes: Check if the result set has changed since
last sensor scan. The sensor will send an internal message
indicating that its value has changed. In combination with a
Change Trigger, you can use this mechanism to trigger a
notification 2484 whenever a sensor value changes.
Condition "Warning" This field is only visible if you enable numeric results processing
above. Define a condition of the returned numeric SQL result set
that sets the sensor to a Warning status. Choose between:
none: Do not set the sensor to Warning status for any
condition.
equals: Result set must be the same as the value provided
below.
is above: Result set must be above the value provided below.
lower t han: Result set must be below the value provided below.
does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 2477 .
Value This field is only visible if you enable numeric results processing
above. Enter a value of the returned numeric SQL result set that
sets the sensor into a Warning status. Please enter an integer or
float value.
Condition "Down" This field is only visible if you enable numeric results processing
that sets the sensor to a Down status. Choose between:
none: Do not set the sensor to Down status for any condition.
below.
provided below.
sets the sensor to a Down status. Please enter an integer value.
02.02.2015 343
3 ADO SQL Sensor
Response Must Include This field is only visible if you enable string results processing
above. Enter a string that must be part of the returned SQL string.
If this is not the case, the sensor will show a Down status. Please
Response Must Not This field is only visible if you enable string results processing
include above. Enter a string that must not be part of the returned SQL
string. If this is the case, the sensor will show a Down status.
Please enter a string or leave the field empty.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
344 02.02.2015
3 ADO SQL Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 345
3 ADO SQL Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
346 02.02.2015
3 ADO SQL Sensor
menu bar.
dependent on.
02.02.2015 347
3 ADO SQL Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: Monitoring (Almost) Any SQL Server Through ADO with PRTG Network
Monitor
Knowledge Base: How do I correctly configure credentials for ADO SQL sensors?

348 02.02.2015
3 ADO SQL Sensor
Notifications
Others
02.02.2015 349
4 Amazon CloudWatch Sensor
6.8.4 Amazon CloudWatch Sensor
The Amazon CloudWatch sensor monitors performance of Amazon Cloud services.
The following services are available:
Elastic Compute Cloud (EC2)

Simple Queue Service (SQS)
Elastic Load Balancing (ELB)
Elastic Block Store (EBS)
Simple Notification Service (SNS)
Relational Database Service (RDS)
ElastiCache
Depending on the selected service, the sensor can show the following:
CPU utilization
Network load in and out
Disk read and write speed
Number of disk read and write operations per second
sensor setup.
350 02.02.2015
Amazon CloudWatc h Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/amazon_c loudwatc h.png
Remarks
You must enable the CloudWatch option for the instance you want to monitor. You can do
this, for example, using Amazon's AWS console.
Requires 352 access rights for CloudWatch queries. For details, please see the Knowledge
Base: How do I define access rights for Amazon CloudWatch queries?
Note: Amazon will charge you (a small amount) for each "Amazon CloudWatch API Request"
query the sensor sends to the Amazon servers. Depending on the service, each Amazon
CloudWatch sensor sends about 10 to 30 requests with each scanning interval. Last time we
checked the Amazon price list, they charged max. US$ 0.014 per 1,000 requests (depending
on your region).
For details, please see the Knowledge Base: How much does Amazon charge for using the
CloudWatch API?
02.02.2015 351
Requirement: Access Rights for Amazon CloudWatch Queries

The AWS Identity and Access Management (IAM) account that you use with the Amazon
CloudWatch sensor needs specific rights to query any metrics. For details, see section More
359 .

Add Sensor
PRTG will perform a meta scan before you actually add this sensor type and requires basic
information for this scan in advance. Provide the requested information in the appearing
window. During the scan, PRTG will recognize all items available for monitoring based on your
input. The following settings differ in comparison to the sensor's settings page:
AMAZON CR EDENTIALS
Region Select the region in which the instance to be monitored is running.

The settings you make in this dialog are valid for all of the sensors
that are created.
Choose between:
US East (Nort hern Virginia)
US West (Oregon)
US West (Nort hern California)
EU (Ireland)
Asia Pacific (Singapore)
Asia Pacific (Toky o)
Asia Pacific (Sy dney )
Sout h America (Sao Paulo)
352 02.02.2015
AMAZON CR EDENTIALS
Note: The CloudWatch option must be enabled for the instance

you want to monitor (you can do this, for example, using Amazon's
AWS console).
Select which service instances you want to monitor. PRTG creates one sensor for each
instance you choose in the Add Sensor dialog. The settings you make in this dialog are valid
AMAZON CLOU DWATCH SPECIFIC
Service Instance Select the instances you want to add a sensor for. You see a list
with the names of all items which are available to monitor. Select
the desired items by adding check marks in front of the respective
lines. PRTG creates one sensor for each selection. You can also
select and deselect all items by using the check box in the table
head.
Sensor Settings
02.02.2015 353
priority).
AMAZON CR EDENTIALS
AWS Access Key ID Enter your access key ID. You can obtain it from aws.amazon.com.
AWS Secret Access Enter your secret access key. You can obtain it from
Key aws.amazon.com.
Region Shows the region your instance is located at. Once a sensor is
created, you cannot change this value. It is shown for reference
purposes only. If you need to change this, please add the sensor
anew.
Period (Interval) Define in what granularity you want to receive datapoints from
CloudWatch. Choose between:
1 Minut e
2 Minut es
5 Minut es
10 Minut es
30 Minut es
1 Hour
354 02.02.2015
Service Shows the service this sensor is monitoring. Once a sensor is

anew.
Instance Shows the Instance ID of the Amazon Web Services instance this
sensor is monitoring. When using the "Simple Notification Service
(SNS)" service, this field is not visible. Once a sensor is created, you
cannot change this value. It is shown for reference purposes only.
If you need to change this, please add the sensor anew.
Topic Name This field is only visible if you selected a "Simple Notification Service
(SNS)" instance before. It shows the topic name that is monitored
by this sensor. The sensor will show the number and size of
messages published, and the number of notifications delivered and
failed. Each sensor can monitor one topic name only. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
Availability Zone This field is only visible if you selected a "Elastic Load Balancing
(ELB)" instance before. Enter the name of the Availability Zone of
your Load Balancer you want to monitor. If you leave this field
empty, the average value of all zones will be taken.
SENSOR DISPLAY
for each channel.
02.02.2015 355
SENSOR DISPLAY
Inherited Settings
described below.
Note: For Amazon CloudWatch sensors, the scanning interval cannot be inherited. Please use
the individual settings of the sensor to define the interval in which data is received.

settings.

between:
be set.
maintenance window.
356 02.02.2015

maintenance window.
maintenance window.

can choose between:
menu bar.
dependent on.
02.02.2015 357
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
358 02.02.2015
Bandwidt h
Memory
Disk
File
Cust om
More
Knowledge Base: How do I define access rights for Amazon CloudWatch queries?
Knowledge Base: How much does Amazon charge for using the CloudWatch API?
Knowledge Base: Why can't I use EU Frankfurt as region for my Amazon CloudWatch sensor?


Notifications
02.02.2015 359
Others
360 02.02.2015
5 AVM FRITZ!Box WAN Interface v2 Sensor
6.8.5 AVM FRITZ!Box WAN Interface v2 Sensor
The AVM FRITZ!Box WAN Interface Sensor monitors the internet traffic of a FRITZ!Box internet
access router from European manufacturer AVM.
It shows the following:
Incoming and outgoing internet traffic

Number of outgoing calls
Outgoing connection time
AVM FRITZ!Box WAN Interfac e v 2 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/av m_fritzbox_wan_interfac e_v 2.png
Remarks
Requires 362 .NET 4.0 on the probe system.
Note: You have to enable "Transmit status information over UPnP" in the network settings of
your FRITZ!Box for this sensor. See the Knowledge Base for detailed information about
enabling Universal Plug and Play (UPnP): How do I activate UPnP for my Fritz!Box?
Important notice: Currently, this sensor type is in beta status. The methods of operating can
change at any time, as well as the available settings. Do not expect that all functions will
work properly, or that this sensor works as expected at all. Be aware that this type of
sensor can be removed again from PRTG at any time.
02.02.2015 361

Add Sensor
Sensor Settings
priority).
362 02.02.2015
SENSOR SPECIFIC
Login Method Select the login method for your FRITZ!Box. You have to use the
login settings exactly as defined in the FRITZ!Box web interface.
Please check this before you add this sensor. Choose between:
Login wit h FRITZ!Box username and password: Choose this
option if your FRITZ!Box settings require full credentials.
Login wit h FRITZ!Box password: Choose this option if your
FRITZ!Box settings require only a password.
No login: Choose this option if your FRITZ!Box does not require
credentials to login.
FRITZ!Box Username This field is only visible if you select the full credentials option
above. Enter the username for your FRITZ!Box.
FRITZ!Box Password This field is only visible if you select a credentials based login
option above. Enter the password for your FRITZ!Box.
Note: The sensor uses the credentials of the user accounts
defined in your FRITZ!Box and not the general password for the
hardware device.
DEBU G OPTIONS
between:
02.02.2015 363
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
364 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 365

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
366 02.02.2015
menu bar.
dependent on.
02.02.2015 367
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
368 02.02.2015
More
Knowledge Base: How do I activate UPnP for my Fritz!Box?



Notifications
Others
02.02.2015 369
6 Cisco IP SLA Sensor
6.8.6 Cisco IP SLA Sensor
The Cisco IP SLA sensor monitors Voice over IP (VoIP) network parameters using IP Service
Level Agreement (SLA) from Cisco via Simple Network Management Protocol (SNMP).
It shows different aspects provided by the queried device:
Average, maximum, and minimum Round Trip Time (RTT)

Average jitter
Average jitter from source to destination and vice versa
Average latency from source to destination and vice versa
Impairment Calculated Planning Impairment Factor (ICPIF)
Late packets in percent
Average, maximum, and minimum latency from source to destination and vice versa
Mean Opinion Score (MOS)
Number of lost packets and in percent
Packets out of sequence in percent
370 02.02.2015
Cisc o IP SLA Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c isc o_ip_sla.png
Remarks
For a general introduction to the technology behind Quality of Service monitoring, please
see manual section Monit oring Qualit y of Service 2765 .
02.02.2015 371
Add Sensor
IP SLA SPECIFIC
IP SLAs Select the IP SLAs you want to add a sensor for. You see a list with
the names of all items which are available to monitor. Select the
desired items by adding check marks in front of the respective
head. The list options depend on the configuration of the queried
device. If you're missing a type here, please check your device's
configuration. PRTG can support the following operations:
echo
pat hEcho
fileIO
script
udpEcho
t cpConnect
ht t p
dns
jit t er
dlsw
dhcp
ft p
pat h-jit t er
Note: Packet Loss values are summarized, but have no explicit
channel for SourceDestination or DestinationSource values
Sensor Settings
372 02.02.2015
priority).
IP SLA SPECIFIC
ID
Type
These fields show SLA specific settings provided by the queried
SLA device. Once a sensor is created, you cannot change this
Name (Tag)
value. It is shown for reference purposes only. If you need to
change this, please add the sensor anew.
Owner
Frequency
SENSOR DISPLAY
02.02.2015 373
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
374 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 375

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
376 02.02.2015
menu bar.
dependent on.
02.02.2015 377
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
378 02.02.2015
7 Citrix XenServer Host Sensor
6.8.7 Citrix XenServer Host Sensor
The Citrix XenServer Host Sensor monitors a Xen host server via Hypertext Transfer Protocol
(HTTP).
CPU usage
Memory usage (free, used, allocation)
Network usage
Number of running virtual machines
Load average
sensor setup.
02.02.2015 379
Citrix XenServ er Host Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c itrix_xenserv er_host.png
Remarks
The parent device must be a Citrix XenServer version 5.0 or later.
The parent device has to represent one host server of your XenServer pool 381 .
Requires credentials for Xen servers to be defined for the device you want to use the
sensor on.
380 02.02.2015

Knowledge Base: Does PRTG impair my Citrix environment?
Monitoring a XenServer Pool

In a XenServer pool there is one "pool master" that manages the pool. Incoming queries on
any host are automatically forwarded to the pool master. If you want to monitor your virtual
machines, or host servers, simply create respective sensors on a device that represents one
host server of your pool. Internal processes will make sure that monitoring will take place and
continue independently from the physical host. Note: In PRTG's device tree, the sensors for
virtual machines will always remain on the host you originally created it on, also if it is currently
running on a different host.

Add Sensor
Select which XenServer hosts you want to monitor. PRTG creates one sensor for each host
you select in the Add Sensor dialog. The settings you make in this dialog are valid for all of the
sensors that are created.
02.02.2015 381
HOST SETTINGS
Host Select the hosts you want to add a sensor for, including the ones
that are not running. You see a list with the names of all items
which are available to monitor. Select the desired items by adding
check marks in front of the respective lines. PRTG creates one
sensor for each selection. You can also select and deselect all
items by using the check box in the table head.
Sensor Settings
priority).
382 02.02.2015
HOST SETTINGS
UUID Shows the Universally Unique Identifier (UUID) of the host that this
sensor monitors.
Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
Name Shows the name of the host that this sensor monitors.
SENSOR DISPLAY
for each channel.
02.02.2015 383
Inherited Settings
described below.
384 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 385

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
386 02.02.2015
menu bar.
dependent on.
02.02.2015 387
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More


388 02.02.2015
Notifications
Others
02.02.2015 389
8 Citrix XenServer Virtual Machine Sensor
6.8.8 Citrix XenServer Virtual M achine Sensor
The Citrix XenServer Virtual Machine Sensor monitors a virtual machine on a Xen server via
Hypertext Transfer Protocol (HTTP).
CPU usage
Memory usage (available, used)
Disk usage (reads and writes per second)
Network usage (bytes received and sent)
Balloon driver target size
sensor setup.
Citrix XenServ er Virtual Mac hine Sensor
390 02.02.2015
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c itrix_xenserv er_v irtual_mac hine.png
Remarks
The parent device must be a Citrix XenServer (version 5.0 or later).
The parent device has to represent one host server of your XenServer pool 391 .
Requires credentials for Xen servers to be defined for the device you want to use the
sensor on.
Monitoring a XenServer Pool

In a XenServer pool there is one "pool master" that manages the pool. Incoming queries on
any host are automatically forwarded to the pool master. If you want to monitor your virtual
machines, or host servers, simply create respective sensors on a device that represents one
host server of your pool. Internal processes will make sure that monitoring will take place and
continue independently from the physical host. Note: In PRTG's device tree, the sensors for
virtual machines will always remain on the host you originally created it on, also if it is currently
running on a different host.

Add Sensor
Note: PRTG requests a full list of all virtual machines configured on the Xen server. Therefore, it
may take a few seconds before the dialog is loaded.
Select which virtual machines you want to monitor. PRTG creates one sensor for each virtual
machine you select in the Add Sensor dialog. The following settings for this sensor differ in
the 'Add Sensor' dialog in comparison to the sensor's settings page:
02.02.2015 391
VIR TU AL MACHINE SETTINGS
Virtual Machine Select the Virtual Machines (VM) you want to add a sensor for,
including the ones that are not running. You see a list with the
names of all items which are available to monitor. Select the
head.
Sensor Settings
priority).
392 02.02.2015
UUID Shows the Universally Unique Identifier (UUID) of the virtual

machine. Once a sensor is created, you cannot change this value. It
is shown for reference purposes only. If you need to change this,
Name Shows the name of the virtual machine. Once a sensor is created,
you cannot change this value. It is shown for reference purposes
only. If you need to change this, please add the sensor anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 393
SCANNING INTER VAL
Choose between:
option will apply.
394 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 395
menu bar.
dependent on.
396 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More


02.02.2015 397
Notifications
Others
398 02.02.2015
9 Cloud HTTP Sensor
6.8.9 Cloud HTTP Sensor
The Cloud HTTP sensor monitors the loading time of a web server via Hypertext Transfer
Protocol (HTTP) from different locations worldwide. The locations are distributed over five
continents around the globe.
The sensor can show response t ime and response code of the target server monitored from
the following locations:
Asia Pacific: Singapore

Asia Pacific: Sydney
Asia Pacific: Tokyo
EU Central: Frankfurt
EU West: Ireland
South America: Sao Paulo
US East: Northern Virginia
US West: Northern California
US West: Oregon
Global average response time
02.02.2015 399
9 Cloud HTTP Sensor
Cloud HTTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c loud_http.png
Remarks
The URL you monitor must be reachable over the internet.
400 02.02.2015
9 Cloud HTTP Sensor
This sensor type has predefined limits for several metrics. You can change these limits
individually in the channel settings. For detailed information about channel limits, please refer
to the manual section Sensor Channels Set t ings 2477 .
Add Sensor
Sensor Settings
priority).
02.02.2015 401
9 Cloud HTTP Sensor
HTTP SETTINGS
URL Enter the URL the sensor connects to. It has to be URL encoded! If
you enter an absolute URL, the sensor uses this address
independently from the IP address/DNS name setting of the
device on which you create this sensor. You can enter an URL
leading to a webpage (to measure the page source code's loading
time), or enter the URL of an image or of another page asset to
measure this element's availability and loading time.
PRTG uses a smart URL replacement which allows you to use the
parent device's IP address/DNS name setting as part of the URL.
For more information, please see section Smart URL Replacement
below.
Request Method Choose an HTTP request method to determine how the sensor will
request the given URL.
GET: Request the website directly, like browsing the web. We
recommend using this setting for a simple check of a web page.
POST: Send post form data to the URL. If this setting is chosen,
you must enter the data that will be sent in the Post dat a field
below.
HEAD: Only request the HTTP header from the server; without
the actual web page. Although this saves bandwidth since less
data is transferred, it is not recommended because the measured
request time is not the one experienced by your users and you
might not be notified for slow results or timeouts.
Postdata This field is only visible when you select the POST Request
Met hod setting above. Enter the data part for the POST request
here. Note: No XML is allowed here!
Timeout (Sec.) Enter a timeout in seconds for the server request. If the reply
takes longer than this value defines, the PRTG will cancel the
request and shows an error message. The maximum timeout value
is 5 seconds.
Period (Interval) Define the scanning interval of this sensor. The period you choose
here specifies how often the target server is requested from the
source locations.
Note: This sensor cannot inherit scanning intervals nor use other
intervals than given here.
402 02.02.2015
9 Cloud HTTP Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.

settings.
02.02.2015 403
9 Cloud HTTP Sensor


between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
404 02.02.2015
9 Cloud HTTP Sensor

menu bar.
dependent on.
02.02.2015 405
9 Cloud HTTP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Smart URL Replacement

Instead of entering a complete address in the URL field of an HTTP sensor, you can merely
enter the protocol followed by colon and three slashes (that means you can enter either
http:/// or https:/// or even a simple slash / as equivalent for http:///). PRTG will then fill in the
parent device's IP address or DNS name in front of the third slash automatically. Whether this
results in a valid URL or not, depends on the IP address or DNS name of the device where this
HTTP sensor is created on. In combination with cloning devices, the smart URL replacement
makes it easy to create many like devices.
For example, if you create a device with DNS name www.example.com and you put an HTTP
sensor on it, you can provide values the following ways:
Providing the value https:/// in the URL field, PRTG will automatically create the URL https://
www.example.com/ from that.
Using the value /help in the URL field, PRTG will automatically create and monitor the URL
http://www.example.com/help
It is also possible to provide a port number in the URL field which will be taken over by the
device's DNS name and internally added, for example, http://:8080/
406 02.02.2015
9 Cloud HTTP Sensor
Note: Smart URL replacement does not work for sensors running on the "Probe Device".

Notifications
Others
02.02.2015 407
10 Cloud Ping Sensor
6.8.10 Cloud Ping Sensor
The Cloud Ping sensor monitors the ping times to its parent device from different locations
worldwide. These locations are distributed over five continents around the globe.
The sensor can show the response t imes of the target server pinged from the following
locations:
Asia Pacific: Singapore

Asia Pacific: Sydney
Asia Pacific: Tokyo
EU Central: Frankfurt
EU West: Ireland
South America: Sao Paulo
US East: Northern Virginia
US West: Northern California
US West: Oregon
Global average response time
408 02.02.2015
Cloud Ping Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c loud_ping.png
Remarks
The address you define in the parent device settings 288 must be reachable over the internet.
Add Sensor
02.02.2015 409
Sensor Settings
priority).
PING SETTINGS
Packet Size (Bytes) Enter the packet size in bytes for the Ping. You can choose any
value between 1 and 10000. We recommend using the default
value.
Ping Count Enter the number of Pings to be sent in a row to the parent device
with one scan. Please enter an integer value. The default value is 1,
the maximum supported ping count is 5.
Timeout (Sec.) Enter a timeout in seconds for the Ping. If the reply takes longer
than this value defines, the PRTG will cancel the request and shows
an error message. The maximum timeout value is 5 seconds.
Period (Interval) Define the scanning interval of this sensor. The period you choose
here specifies how often the parent device is pinged from the
source locations.
410 02.02.2015
PING SETTINGS
Note: This sensor cannot inherit scanning intervals nor use other
intervals than given here.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 411

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
412 02.02.2015
menu bar.
dependent on.
02.02.2015 413
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
414 02.02.2015
11 ClusterState Sensor
6.8.11 ClusterState Sensor
The ClusterState sensor monitors the health of a PRTG cluster 81 and indicates PRTG's own
system health status.
It measures various internal system parameters of the cluster system:
Number of connects per minute

Cluster in- and outgoing messages per minute
Number of connected and disconnected cluster nodes.
ClusterState Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c lusterstate.png
Remarks
PRTG creates this sensor automatically with a cluster installation. You cannot delete or add it
manually.
If at least one cluster node is disconnected, this sensor shows a Down status by default.
On the sensor's Overview tab you can review the states of each cluster node.
On the monitoring data review tabs 129 you can choose the cluster member of which you
want to show data (or of all nodes).
02.02.2015 415
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
416 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 417
SCANNING INTER VAL
Choose between:
option will apply.
418 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 419
12 Core Health Sensor
6.8.12 Core Health Sensor
The Core Health sensor monitors internal PRTG parameters. It shows the status of the PRTG
core server.
This sensor type checks various parameters of your PRTG core which have an impact on the
stability of the system:
Health: This index value sums up the core state into a value between 100% (healthy) and 0%
(failing). Frequent or repeated health values below 100% should be investigated.
CPU Load: This channel shows the current percentage CPU load. Extensive CPU load can lead
to false, incomplete, and incorrect monitoring results. This value usually should stay below
50%.
Handles: This is a counter for the data structures of the operating system. It is responsible
for internal resource management. Repeated obviously increasing values should be
investigated.
Committed Memory: This channel shows the amount of memory committed to the PRTG core
server as reported by the memory manager.
Free Page File Memory: This channel shows the amount of free page file memory currently
available on the system. Page file memory is aggregated RAM and the size of page file. It is
the maximum amount of memory that is available on the system to be used for all currently
running processes. If it gets too low the system can crash, at least some applications will
throw "Out of memory" errors.
Free Physical Memory: This channel shows the amount of free physical memory currently
available on the system. This is the RAM that is physically built-in in the computer. If it gets
too low the system will become very slow and PRTG is not usable in a reasonable way
anymore. It can happen that some sensors will not be displayed correctly in that case, they
will appear disabled (grayed out).
Free Virtual Memory: This channel shows the accessible address space on the system for
PRTG. PRTG cannot use more memory than reported here, independently from free page file
and physical memory. On a 32bit OS (operating system) the maximum is 2 GB (3 GB with
special settings under Windows); on a 64bit OS it is 4 GB if PRTG is running as 32bit version,
and unlimited as 64bit version (only Core). If free virtual memory gets too low, PRTG will
throw "Out of memory" errors or the message "not enough storage to process this
command" (visible in the Core log).
Threads: This channel shows the number of program parts which are currently running
simultaneously. This number can increase with heavy load. The number should not exceed
100 in normal operation.
Raw Data Buffer: This channel shows how much raw data is temporarily stored on the
physical memory while I/O operations on the disk. Usually, this value should be 0 (or very
low). Investigate increasing values.
420 02.02.2015
Core Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c ore_health.png
Remarks
PRTG creates this sensor automatically and you cannot delete it.
You can set up this sensor only on a Local Probe device!
Sensor Settings
02.02.2015 421
priority).
SENSOR DISPLAY
for each channel.
422 02.02.2015
Inherited Settings
described below.
02.02.2015 423
SCANNING INTER VAL
Choose between:
option will apply.
424 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 425

Notifications
Others
426 02.02.2015
13 Dell PowerVault MDi Logical Disk Sensor
6.8.13 Dell PowerVault M Di Logical Disk Sensor
The Dell PowerVault MDi Logical Disk sensor monitors a virtual disk on a Dell PowerVault
MD3000i, MD3620i, MD3000f, MD3620f, or MD3820i. It might work with other models, too.
Total number of I/O operations

Number of current and maximum I/O operations per second
Current and maximum disk speed
Read and cache hit percentages
sensor setup.
Dell PowerVault MDi Logic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dell_powerv ault_mdi_logic al_disk.png
Remarks
Works with Dell PowerVault MD3000i, MD3620i, MD3000f, MD3620f, or MD3820i, and might
support other models.
02.02.2015 427
Requires 428 Dell Modular Disk Storage Manager on the probe system. Please see the
Knowledge Base: Where do I find the Dell PowerVault Modular Disk Storage Manager for use
with my MDi SAN?
Needs the IP address of the Storage Area Network (SAN) defined in the parent device
settings.
Requirement: Dell Modular Disk Storage Manager

This sensor requires an installation of the Dell "Modular Disk Storage Manager" program. You
have to install it on the computer running the PRTG probe: Either on the local system (on every
node, if on a cluster probe), or on the system running the remote probe 2848 . For details about
setup, please see More section below.
Note: Please create this sensor on a device which has the SAN's IP address configured in the
"IP address/DNS name" field.
Add Sensor
Select which virtual disks you want to monitor. PRTG creates one sensor for each disk you
select in the Add Sensor dialog. The settings you make in this dialog are valid for all of the
SENSOR SETTINGS
Virtual Disks Select the disks you want to add a sensor for. You see a list with
head.
Sensor Settings
428 02.02.2015
priority).
SENSOR SETTINGS
Virtual Disk Shows the name of the virtual disk that this sensor monitors. Once
a sensor is created, you cannot change this value. It is shown for
the sensor anew.
between:
SENSOR DISPLAY
02.02.2015 429
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
430 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 431

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
432 02.02.2015
menu bar.
dependent on.
02.02.2015 433
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
434 02.02.2015
More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?

Notifications
Others
02.02.2015 435
14 Dell PowerVault MDi Physical Disk Sensor
6.8.14 Dell PowerVault M Di Phy sical Disk Sensor
The Dell PowerVault MDi Physical Disk sensor monitors a physical disk on a Dell PowerVault
MD3000i, MD3620i, MD3000f, or MD3620f. It might work with other models, too.
It can show following:
Mode of the physical disk

Status of the physical disk
The sensor shows these channels as reported in the Modular Disk Storage Manager. Status
and mode combined indicate the particular status of a RAID controller physical disk. The table
below provides you the status description according to the Dell documentation:
"St at us" Channel "Mode" Channel Descript ion
Optimal (status: up) Unassigned (status: The physical disk in the indicated slot is
up) unused and available to be configured.
Assigned (status: up) The physical disk in the indicated slot is

configured as part of a disk group.
Hot Spare Standby The physical disk in the indicated slot is

(status: up) configured as a hot spare.
Hot Spare In Use The physical disk in the indicated slot is in

(status: up) use as a hot spare within a disk group.
Failed (status: down) Assigned The physical disk in the indicated slot has
been failed because of an unrecoverable
Unassigned error, an incorrect drive type or drive size,
Hot Spare In Use or by its operational state being set to
failed.
Hot Spare Standby
Replaced (status: up) Assigned The physical disk in the indicated slot has
been replaced and is ready to be, or is
actively being, configured into a disk group.
Pending Failure Assigned A SMART error has been detected on the

(status: down) physical disk in the indicated slot.
Unassigned
Hot Spare In Use
Hot Spare Standby
None (status: None (status: warning) The indicated slot is empty, or the array
warning) cannot detect the physical disk.
436 02.02.2015
"St at us" Channel "Mode" Channel Descript ion
Undefined (status:
down)
Dell PowerVault MDi Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dell_powerv ault_mdi_phy sic al_disk.png
Remarks
Works with Dell PowerVault MD3000i, MD3620i, MD3000f, MD3620f, or MD3820i, and might
support other models.
Requires 436 Dell Modular Disk Storage Manager on the probe system. Please see the
Knowledge Base: Where do I find the Dell PowerVault Modular Disk Storage Manager for use
with my MDi SAN?
Need the IP address of the Storage Area Network (SAN) defined in the parent device
settings.
02.02.2015 437
Requirement: Dell Modular Disk Storage Manager

This sensor requires an installation of the Dell "Modular Disk Storage Manager" program. You
have to install it on the computer running the PRTG probe: Either on the local system (on every
node, if on a cluster probe), or on the system running the remote probe 2848 . For details about
setup, please see More section below.
Note: Please create this sensor on a device which has the SAN's IP address configured in the
"IP address/DNS name" field.
Add Sensor
Select the physical disks you want to monitor. PRTG creates one sensor for each disk you
SENSOR SETTINGS
Physical Disks Select the disks you want to add a sensor for. You see a list with
head.
Sensor Settings
438 02.02.2015
priority).
SENSOR SETTINGS
Physical Disks Shows the disk that this sensor monitors. Once a sensor is
anew.
between:
SENSOR DISPLAY
02.02.2015 439
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
440 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 441

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
442 02.02.2015
menu bar.
dependent on.
02.02.2015 443
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
444 02.02.2015
More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?

Notifications
Others
02.02.2015 445
15 DHCP Sensor
6.8.15 DHCP Sensor
The DHCP sensor monitors a Dynamic Host Configuration Protocol (DHCP) server. It sends a
broadcast message to the network and waits for a DHCP server to respond. On sensor
creation, choose the network card on the probe system which will be used to send the
broadcast message.
If a server responds, the sensor shows the following:
Address of the server and the offered IP in the sensor message. You can check the server's
response using Regular Expressions 2846 .
Response time (msec)
Lease time given by the server (in days)
DHCP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dhc p.png
Remarks
You can set up this sensor only on a Local Probe device!
Add Sensor
446 02.02.2015
15 DHCP Sensor
Select the desired network interfaces to monitor DHCP servers. PRTG creates one sensor for
each network interface you choose in the Add Sensor dialog. The settings you make in this
dialog are valid for all of the sensors that are created.
DHCP SPECIFIC
Specify Network Select the network adapters you want to add a sensor for. You
Interface see a list with the names of all items which are available to monitor.
Select the desired items by adding check marks in front of the
respective lines. PRTG creates one sensor for each selection. You
table head.
Sensor Settings
priority).
02.02.2015 447
15 DHCP Sensor
DHCP SPECIFIC
MAC Shows the MAC address of the network adapter that is used to
send the broadcast message to the network. Once a sensor is
anew.
Client IP Specify if you want to check the returned client IP with a regular
expression. Choose between:
Don't check: The IP will only appear in the sensor message
without further processes.
Check: Enter the regular expression you want to use below.
Client IP Must Include This field is only visible if you chose to check the client IP above. In
the response of the DHCP server, search using a regular
expression. If the answer for the client IP does not contain the
defined string, the sensor shows a Down status 123 .
For example, enter 10\.0\.5\..* to make sure any answering DHCP
server returns an client IP address starting with "10.0.5.". If it does
not, the sensor will show an error. For more details, see Regular
Expressions 2846 section. Leave empty to not use this field.
Client IP Must Not This field is only visible if you choose to check the client IP above.
Include In the response of the DHCP server, search using a regular
expression. If the answer for the client IP contains the defined
string, the sensor shows a Down status.
See example above. For more details, see Regular Expressions 2846
section. Leave empty to not use this field.
Server IP Specify if you want to check the returned server IP with a regular
expression. Choose between:
Don't check: The IP only appears in the sensor message without
further processes.
Check: Enter the regular expression you want to use below.
Server IP Must Include This field is only visible if you choose to check the server IP above.
In the response of the DHCP server, search using a regular
expression. If the answer for the server IP does not contain the
defined string, the sensor shows a Down status.
448 02.02.2015
15 DHCP Sensor
DHCP SPECIFIC
Server IP Must Not This field is only visible if you choose to check the server IP above.
Include In the response of the DHCP server, search using a regular
expression. If the answer for the server IP contains the defined
string, the sensor shows a Down status.
DHCP Server Change If there is more than one DHCP server in the network that may
answer to the broadcast message, the sensor can receive an
answer from a different DHCP server, compared to the last scan of
the sensor. In this case, PRTG can write an entry to the system
Logs 148 . Choose between:
Ignore: Do not write a log entry if the DHCP server changes.
Writ e log ent ry : Write an entry to the system Logs whenever
the DHCP server changes between two sensor scans.
Note: Regardless of this setting, those entries will always be added
to the sensor Log.
Offered IP Change If the IP address offered by the DHCP server changes between two
sensor scans, PRTG can write an entry to the system Logs 148 .
Choose between:
Ignore: Do not write a log entry if the offered IP address

changes.
Writ e log ent ry : Write an entry to the system Logs whenever

the DHCP server offers a different IP address compared to the
last sensor scan.
Note: Regardless of this setting, those entries will always be added
to the sensor Log.
02.02.2015 449
15 DHCP Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
450 02.02.2015
15 DHCP Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 451
15 DHCP Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
452 02.02.2015
15 DHCP Sensor
menu bar.
dependent on.
02.02.2015 453
15 DHCP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
454 02.02.2015
16 DNS Sensor
6.8.16 DNS Sensor
The DNS sensor monitors a Domain Name Service (DNS) server. It resolves a domain name and
compares it to a given IP address.
The sensor shows the response time of the DNS server.

It turns to a Down status if the DNS server does not resolve a given domain name correctly.
DNS Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dns.png
Add Sensor
Sensor Settings
02.02.2015 455
16 DNS Sensor
priority).
DNS SPECIFIC
Port Enter the number of the port to which the sensor tries to connect.
This must be the port the sensor's parent device is running the
DNS service on. Usually you will use port 53. We recommend using
the default value.
Note: The sensor connects to the IP Address or DNS Name value
of the device 288 on which you create it.
Domain Enter the domain name that the sensor resolves using the Domain
Name Service (DNS) server specified in the sensor's parent device
settings 288 . You can enter an internet domain name here (for
example, example.com) or a DNS name in your internal network
(such as computer-xyz), depending on the type of DNS server you
monitor. You can also enter an IP address here.
Query Type Select the type of query that the sensor sends to the DNS server.
Choose between:
Host address IPv4 (A)
Host address IPv6 (AAAA)
Aut horit at ive name server (NS)
456 02.02.2015
16 DNS Sensor
DNS SPECIFIC
St art of a zone of aut horit y marker (SOA)

Domain name point er (PTR)
Mail exchange (MX )
Canonical name for an alias (CNAME)
Check Result Define if the sensor checks the result from the DNS server.
Choose between:
Ignore result : Accept any valid answer of the DNS server.
Check result : Check if the response contains certain strings.
Define below.
Value This field is only visible if you enable result checking above. Enter
elements that the response of the DNS server must contain. Enter
each entry in one line. The received result must contain at least
one of the elements. If none of the element matches the response,
the sensor will show a red Down status.
For example, you can enter an IP address here if your Domain field
contains a host name. Only if the host name is resolved to the
correct IP address, your sensor will show a green Up status.
between:
SENSOR DISPLAY
02.02.2015 457
16 DNS Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
458 02.02.2015
16 DNS Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 459
16 DNS Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
460 02.02.2015
16 DNS Sensor
menu bar.
dependent on.
02.02.2015 461
16 DNS Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
462 02.02.2015
17 Enterprise Virtual Array Sensor
6.8.17 Enterprise Virtual Array Sensor
The Enterprise Virtual Array sensor monitors an HP StorageWorks Enterprise Virtual Array (EVA)
using the sssu.exe from HP Command View EVA Software.
It can show the status of several EVA modules, depending on the available measurement
components:
System controllers
Enclosures
Disks
Disk groups
Folders
Hosts
Snapshots
Data replication
Cabinets
If the devices have measuring tools for fans and temperature, the sensor displays
corresponding data as well.
For these EVA components, this sensor type can show the following:
Operational status
Predicted failures
Accessible media
Allocation in percent
Availability for VRaids in bytes
Exaggerated bytes
Group host access
Number of grouped and ungrouped disks
Age of snapshots
License status
sensor setup.
Remarks
You have to explicitly specify the credentials of the EVA in the sensor settings.
02.02.2015 463
Requires 464 the HP Command View EVA Software on the probe system (or the alternative
below).
Knowledge Base: Do I really have to install the whole Command View on the probe to use
the EVA sensor?
Requirement: Command View

The EVA sensor needs the HP Command View EVA Software to be installed on the probe
system. If you do not want to install the whole command view tool, you can alternatively use
another approach. For details, please see section More 472 .
Add Sensor
PRTG will perform a meta scan before you actually add this sensor type and requires basic
information for this scan in advance. Provide the requested information in the appearing
window. During the scan, PRTG will recognize all items available for monitoring based on your
input. The following settings differ in comparison to the sensor's settings page:
EVA CR EDENTIALS
Scanning Mode Specify the depth of the meta scan. Choose between:
Basic: We recommend using this scanning mode. Various
modules of your EVA will be available for monitoring.
Full Det ail: PRTG will scan for each disk of your EVA. Every disk
will be listed in the module selection.
Select which modules you want to monitor. PRTG will create one sensor for each module you
choose. The settings you make in this dialog are valid for all of the sensors that are created.
464 02.02.2015
EVA SETTINGS
Modules Select the modules you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
EVA CR EDENTIALS
Username Enter the username for the EVA.
Password Enter the password for the EVA.
02.02.2015 465
EVA SETTINGS
Module Shows the monitored module. You can adjust this setting if the
module was renamed or moved to another folder. This way, PRTG
can find the module again and the monitoring history will not be
lost.
System Shows further information about the monitored module. Once a

Module Type reference purposes only. If you need to change this, please add
the sensor anew.
Description
Sensor Result Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
SENSOR DISPLAY
for each channel.
466 02.02.2015
SENSOR DISPLAY
02.02.2015 467
SCANNING INTER VAL
Choose between:
option will apply.
468 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 469
menu bar.
dependent on.
470 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 471
More
Knowledge Base: Do I really have to install the whole Command View on the probe to use the
EVA sensor?

Notifications
Others
472 02.02.2015
18 Event Log (Windows API) Sensor
6.8.18 Event Log (Windows API) Sensor
The Event Log (Windows API) sensor monitors Event Log entries using Windows Application
Programming Interface (API).
It shows the number of new records per second (speed).
Ev ent Log (Windows API) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ev ent_log_windows_api.png
Remarks
Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
Add Sensor
Sensor Settings
02.02.2015 473
priority).
WINDOWS API EVENT LOG SPECIFIC
Log File Specify the log file that this sensor monitors. The Windows event
log provides several different log files which PRTG shows here.
Choose between:
Applicat ion
Sy st em
Securit y
Direct ory Service
DNS Server
File Replicat ion Service
FILTER EVENT LOG ENTR IES
Event Type Specify the type of event that this sensor processes. Other event
type cannot be processed. Choose between the following event
types:
474 02.02.2015
Any
Error
Warning
Informat ion
Securit y Audit Success
Securit y Audit Failure
Filter by Source Filter all received events for a certain event source. If you enable
this option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event source.
On: Enable filtering by event source.
Match String (Event This field is only visible if you enable source filtering above. Enter a
Source) source from which the events come from. Only events from a
source matching this string are regarded, other events are ignored.
Please enter a string.
Filter by ID Filter all received events for a certain event ID. If you enable this
option, this sensor processes only messages that match the
defined value(s). Choose between:
Off: Do not filter by event ID.
On: Enable filtering by event ID.
Match Value (Event ID) This field is only visible if you enable ID filtering above. Enter an
event ID which the events must have. Only events with an ID that
matches this value are regarded.
Note: The Event Log (Windows API) Sensor 473 supports more
than one event ID. Using this sensor type, you can enter a comma
separated list of event IDs to filter for more than one ID.
Note: The WMI Event Log Sensor 2230 supports filtering for only
one ID.
Filter by Category Filter all received events for a certain event category. If you enable
Off: Do not filter by event category.
On: Enable filtering by event category.
02.02.2015 475
Match String (Event This field is only visible if you enable category filtering above. Enter
Category) a category which the events must have. Only events with a
category that matches this string are regarded. Please enter a
string.
Filter by User Filter all received events for a certain event user. If you enable this
Off: Do not filter by event user.
On: Enable filtering by event user.
Match String (Event This field is only visible if you enable user filtering above. Enter a
User) user name that the events must to be assigned to. Only events
with a user name that matches this string are regarded. Please
enter a string.
Filter by Computer Filter all received events for a certain event computer. If you enable
Off: Do not filter by event computer.
On: Enable filtering by event computer.
Match String (Event This field is only visible if you enable computer filtering above.
Computer) Enter a computer name which the events must be assigned to.
Only events with a computer name that matches this string are
regarded. Please enter a string.
Filter by Message Filter all received events for a certain event message. If you enable
Off: Do not filter by event message.
On: Enable filtering by event message.
Match String (Event This field is only visible if you enable message filtering above. Enter
Message) a message that the event must contain. Only events with a
message matching this string are regarded. Please enter a string.
Note: The Event Log (Windows API) Sensor always performs a substring match. Please do not
use any placeholder character. For example, enter RAS for any event source containing this
string in partial or whole form.
476 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 477
SCANNING INTER VAL
Choose between:
option will apply.
478 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 479
menu bar.
dependent on.
480 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 481
Others
482 02.02.2015
19 Exchange Backup (Powershell) Sensor
6.8.19 Exchange Backup (Powershell) Sensor
The Exchange Backup (Powershell) sensor monitors backups of an Exchange server using
Remote PowerShell.
It can show several states of an Exchange database backup, for example:
Past time since the last full backup

Past time since the last copy backup
If a backup is currently running
sensor setup.
Exc hange Bac kup (Powershell) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_bac kup.png
Remarks
The parent device for this sensor must be an Exchange server version 2010 or higher.
sensor on.
Requires 484 Remote PowerShell and Remote Exchange Management Shell on the target
servers and PowerShell 2.0 on the probe system.
02.02.2015 483
Requires 484 the FQDN of the Exchange server in the parent device settings 288 .
Requires 484 elevated rights for the user of this sensor on the Exchange server.
Knowledge Base: PowerShell Sensors: FAQ
Requirement: Remote PowerShell and Remote Exchange Management Shell

This sensor type uses PowerShell commands. In order to monitor Exchange servers with this
sensor, Remot e PowerShell and Remot e Exchange Management Shell have to be enabled
on the target servers which you want to monitor. Also ensure that you have installed
PowerShell 2.0 or later on your probe machine.
Note: In larger environments, the default memory limit for the remote shell might be insufficient
and you might see the error message "The WSMan provider host process did not return a
proper response". In this case, increase the memory limit for Remote PowerShell.
For more information, please see section More below.
Requirement: Fully Qualified Domain Name (FQDN)

In order to connect to Exchange servers, this sensor type needs the fully qualified domain
name (FQDN). In PRTG's device settings of the Exchange server, provide the FQDN instead of
the IP address. For more information, please see section More below.
Requirement: Elevated Rights

The user of this sensor needs elevated rights on the Exchange system. It is not sufficient to
have administrator rights. Please see section More below for detailed information on rights
management.

Add Sensor
484 02.02.2015
Select the Exchange server databases you want to monitor. PRTG creates one sensor for each
database you choose in the Add Sensor dialog. The settings you make in this dialog are valid
SENSOR SETTINGS
Exchange Databases Select the databases you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
02.02.2015 485
SENSOR SETTINGS
Database Shows the name of the monitored database. Once a sensor is

anew.
between:
SENSOR DISPLAY
for each channel.
486 02.02.2015
Inherited Settings
described below.
02.02.2015 487
SCANNING INTER VAL
Choose between:
option will apply.
488 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 489
menu bar.
dependent on.
490 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: Resolving Exchange PowerShell Sensors Issues
Knowledge Base: How do I enable and use remote commands in Windows PowerShell?
Knowledge Base: My Powershell sensor returns an error message. What can I do?
Knowledge Base: "No Logon Servers Available" when Using PowerShell Sensors
Knowledge Base: How can I increase memory for Remote PowerShell?
02.02.2015 491

Notifications
Others
492 02.02.2015
20 Exchange Database (Powershell) Sensor
6.8.20 Exchange Database (Powershell) Sensor
The Exchange Database (Powershell) sensor monitors database information of an Exchange

server using Remote PowerShell.
It shows several states of an Exchange database, for example:
Database size
If the database is mounted
If the database is recognized as valid
sensor setup.
Exc hange Database (Powershell) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_database.png
Remarks
sensor on.
02.02.2015 493



management.

Add Sensor
Select the Exchange server databases you want to monitor. PRTG creates one sensor for each
database you choose in the Add Sensor dialog. The settings you make in this dialog are valid
494 02.02.2015
SENSOR SETTINGS
Exchange Databases Select the databases you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
02.02.2015 495
SENSOR SETTINGS
Database Shows the name of the monitored database. Once a sensor is

anew.
AutoRemount Define if you want the sensor to try to remount the database
Database automatically if it is unmounted. Choose between:
Try t o remount
Just report t he current reading and keep unmount ed
between:
SENSOR DISPLAY
for each channel.
496 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 497
SCANNING INTER VAL
Choose between:
option will apply.
498 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 499
menu bar.
dependent on.
500 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
02.02.2015 501

Notifications
Others
502 02.02.2015
21 Exchange Mail Queue (Powershell) Sensor
6.8.21 Exchange M ail Queue (Powershell) Sensor
The Exchange Mail Queue (Powershell) sensor monitors the number of items in the outgoing
mail queue of an Exchange server using Remote PowerShell.
It can show, for example:
Number of queued mails

Number of retrying mails
Number of unreachable mails
Number of poisonous mails
See section More 511 below for an explanation of the transport queue types. Which channels
the sensor actually shows might depend on the monitored device and the sensor setup.
Exc hange Mail Queue (Powershell) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_mail_queue.png
Remarks
sensor on.
02.02.2015 503



management.

504 02.02.2015
Add Sensor
Select the roles you want to monitor. PRTG creates one sensor for each role you choose in
the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that
are created.
SENSOR SETTINGS
Hub-Transport or Edge- Select the roles you want to add a sensor for. You see a list with
Server the names of all items which are available to monitor. Select the
head.
Sensor Settings
02.02.2015 505
priority).
SENSOR SETTINGS
between:
SENSOR DISPLAY
for each channel.
506 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 507
SCANNING INTER VAL
Choose between:
option will apply.
508 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 509
menu bar.
dependent on.
510 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
02.02.2015 511
Knowledge Base: Types of Transport Queues in Microsoft Exchange


Notifications
Others
512 02.02.2015
22 Exchange Mailbox (Powershell) Sensor
6.8.22 Exchange M ailbox (Powershell) Sensor
The Exchange Mailbox (Powershell) sensor monitors mailboxes of an Exchange server using
Remote PowerShell.
It shows several states of a mailbox, for example:
Total size of items in place

Number of items in place
Past time since the last mailbox logon
sensor setup.
Exc hange Mailbox (Powershell) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_mailbox.png
Remarks
sensor on.
02.02.2015 513



management.

Add Sensor
514 02.02.2015
Select the Exchange server mailboxes you want to monitor. PRTG creates one sensor for each
mailbox you choose in the Add Sensor dialog. The settings you make in this dialog are valid
SENSOR SETTINGS
Mailboxes Select the mailboxes you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
02.02.2015 515
SENSOR SETTINGS
Mailbox Name Shows the name of the monitored mailbox. Once a sensor is
anew.
between:
SENSOR DISPLAY
for each channel.
516 02.02.2015
Inherited Settings
described below.
02.02.2015 517
SCANNING INTER VAL
Choose between:
option will apply.
518 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 519
menu bar.
dependent on.
520 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
02.02.2015 521

Notifications
Others
522 02.02.2015
23 Exchange Public Folder (Powershell) Sensor
6.8.23 Exchange Public Folder (Powershell) Sensor
The Exchange Public Folder (Powershell) sensor monitors public folders of an Exchange server
using Remote PowerShell.
It can show several states of a public folder, for example:
Total size of items in place

Number of items in place
Past time since the last access
sensor setup.
Exc hange Public Folder (Powershell) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_public _folder.png
Remarks
sensor on.
02.02.2015 523



management.

Add Sensor
524 02.02.2015
Select the Exchange server mailboxes you want to monitor. PRTG creates one sensor for each
mailbox you choose in the Add Sensor dialog. The settings you make in this dialog are valid
SENSOR SETTINGS
Public Folder Select the folders you want to add a sensor for. You see a list with
head.
Sensor Settings
priority).
02.02.2015 525
SENSOR SETTINGS
Public Folder Shows the name of the monitored folder. Once a sensor is
anew.
between:
SENSOR DISPLAY
for each channel.
526 02.02.2015
Inherited Settings
described below.
02.02.2015 527
SCANNING INTER VAL
Choose between:
option will apply.
528 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 529
menu bar.
dependent on.
530 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
02.02.2015 531

Notifications
Others
532 02.02.2015
24 EXE/Script Sensor
6.8.24 EXE/Script Sensor
The EXE/Script sensor runs an executable file (EXE, DLL) or a script (batch file, VBScript,
Powershell) on the computer running the local or remote probe. This option is provided as
part of PRTG's Application Programming Interface (API). For details about the return value format
please see the Applicat ion Programming Int erface (API) Definit ion 2830 .
The sensor can show the following:
One value returned by the executable file or script (in one channel only)
Execution time
EXE/Sc ript Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exe_sc ript.png
Remarks
Note: The executable or script file must be stored on the system of the probe the sensor is
created on: If used on a remote probe, the file must be stored on the system running the
remote probe. In a cluster setup, please copy the file to every cluster node.
Note: If you want to execute a custom Windows Management Instrumentation Query
Language (WQL) script, please use the WMI Cust om Sensor 2209 .
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
02.02.2015 533
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
Add Sensor
534 02.02.2015
SENSOR SETTINGS
Script Select an executable file from the list. The sensor will execute it
with every scanning interval.
In this list, files in the corresponding \Cust om Sensors\EX E sub-
directory of the probe system's PRTG program directory are shown
(see Dat a St orage 2871 ). In order for the files to appear in this list,
store them into this folder ending in BAT, CMD, DLL, EXE, PS1, or
VBS. To show the expected values and sensor status, your files
must use the right format for the returned values (in this case,
value:message to standard output). The exit code of the file
determines the sensor status 123 .
For detailed information on how to build custom sensors and for
the expected return format, please see the API documentation
(Applicat ion Programming Int erface (API) Definit ion 2830 ). There,
find detailed information the the "Custom Sensors" tab.
Note: Please do not use the folder \Custom Sensors\Powershell
Scripts to store your files. This remnant from previous software
versions is not used any more and may usually be deleted.
Note: When using custom sensors on the Clust er Probe, please
copy your files to every cluster node installation.
Value Type Define what kind of values your executable or script file gives
back. Choose between:
Int eger: An integer is expected as return value. If the script
gives back a float, PRTG will display the value 0.
Float : A float is expected as return value, with a dot (.) between
pre-decimal position and decimal places. In this setting, the
sensor will also display integer values unless they produce a
buffer overflow.
Count er: Your script returns an integer which increases. PRTG
will show the difference between the values of two sensor
scans.
Note: A counter must return an integer, float is not supported
here!
Channel Name Enter a name for the channel in which the sensor shows returned
values. This is for display purposes only. Please enter a string.
Unit String Enter a string that describes the unit of the returned values. This is
for display purposes only. Please enter a string.
Sensor Settings
02.02.2015 535
priority).
SENSOR SETTINGS
EXE/Script Shows the executable or script file that the sensor executes with
each sensor scan as defined on sensor creation. Once a sensor is
anew.
Parameters If your executable or script file catches command line parameters,

you can define them here. You can use placeholders as well. For a
full list of all placeholders please see the API documentation
(Applicat ion Programming Int erface (API) Definit ion 2830 ).
Note: Please make sure you write the placeholders in quotes to
ensure that they are working properly if their values contain
blanks. Use single quotation marks ' ' with PowerShell scripts, and
double quotes " " with all others. Please enter a string or leave the
field empty.
Environment Choose if PRTG's command line parameters will also be available as

environment parameters.
536 02.02.2015
SENSOR SETTINGS
Default Environment : Do not provide PRTG placeholders' values

in the environment. Choose this secure option if you are not
sure.
Set placeholders as environment values: From within your
executable or script, the values of PRTG's command line
parameters will be available via environment variables. For
example, you can then read and use the current host value of
the PRTG device this EXE/script sensor is created on from within
your script. This option can mean a security risk, because also
credentials are provided in several variables. For a full list of all
available variables please see the API documentation
Security Context Define the Windows user account that the sensor uses to run the
executable or script file. Choose between:
Use securit y cont ext of probe service: Run the selected file
under the same Windows user account the probe runs on. By
default, this is the Windows system user account (if not manually
changed).
Use Windows credent ials of parent device: Use the Windows
user account defined in the settings of the parent device this
sensor is created on. Please go to parent device settings 288 of
this sensor to change these Windows credentials.
Mutex Name Define any desired mutex name for the process. All EXE/Script
sensors having the same mutex name will be executed serially (not
simultaneously). This is useful if you use a lot of sensors and want
to avoid high resource usage caused by processes running
simultaneously. For links to more information, please see the More
543 section below. Please enter a string or leave the field empty.
Value Type Shows the expected value type that you chose on sensor
creation. Once a sensor is created, you cannot change this value. It
Note: The sensor cannot handle string values.
If Value Changes Define what this sensor will do when the sensor value changes.
You can choose between:
02.02.2015 537
SENSOR SETTINGS
Ignore changes (default ): The sensor takes no action on

change.
Trigger 'change' not ificat ion: The sensor sends an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2484 whenever the sensor value changes.
EXE Result Define what this sensor will do with the result that the executable
file gives back. Choose between:
Discard EX E result : Do not store the requested web page.
Writ e EX E result t o disk: Store the last result received from the
script with the file name "Result of Sensor [ID].txt" to the "Logs
(Sensors)" directory (on the Master node, if in a cluster). This is
for debugging purposes. The file will be overridden with each
Writ e EX E result t o disk in case of error: Store the last result
received from the script only if the sensor is in a down status.
The file name is "Result of Sensor [ID].txt" in the "Logs (Sensors)"
directory. Enable this option if you do not want failures to be
overwritten by a following success of the script.
SENSOR DISPLAY
for each channel.
538 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 539
SCANNING INTER VAL
Choose between:
option will apply.
540 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 541
menu bar.
dependent on.
542 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Information about custom scripts and executables
Applicat ion Programming Int erface (API) Definit ion 2830
Knowledge Base: How and Where Does PRTG Store its Data?
02.02.2015 543

Notifications
Others
544 02.02.2015
25 EXE/Script Advanced Sensor
6.8.25 EXE/Script Advanced Sensor
The EXE/Script Advanced sensor runs an executable file (EXE, DLL) or a script (batch file,
VBScript, Powershell) on the computer running the local or remote probe. This option is
provided as part of PRTG's Application Programming Interface (API). The return value of this
sensor must be valid XML. For details about the return value format please see the
Applicat ion Programming Int erface (API) Definit ion 2830 .
The sensor can show values returned by the executable file or script in multiple channels.
EXE/Sc ript Adv anc ed Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exe_sc ript_adv anc ed.png
Remarks
This sensor does not support more than 50 channels 546 officially.
Note: The executable or script file must be stored on the system of the probe the sensor is
created on: If used on a remote probe, the file must be stored on the system running the
remote probe. In a cluster setup, please copy the file to every cluster node.
Note: If you want to execute a custom Windows Management Instrumentation Query
Language (WQL) script, please use the WMI Cust om Sensor 2209 .
02.02.2015 545
Limited to 50 Sensor Channels

PRTG does not support more than 50 sensor channels officially. Depending on the data used
with this sensor type, you might exceed the maximum number of supported sensor channels.
In this case, PRTG will try to display all sensor channels. However, please be aware that you will
experience limited usability and performance.
Add Sensor
SENSOR SETTINGS
EXE/Script Select an executable file from the list. The sensor will execute it
with every scanning interval.
In this list, files in the corresponding \Cust om Sensors\EX EX ML
sub-directory of the probe system's PRTG program directory are
shown (see Dat a St orage 2871 ). To appear in this list, please store
the files into this folder ending in BAT, CMD, DLL, EXE, PS1, or VBS.
To show the expected values and sensor status, your files must
return the expected XML format to standard output. Values and
message must be embedded in the XML.
For detailed information on how to build custom sensors and for
the expected return format, please see the API documentation
find detailed information on the "Custom Sensors" tab.
Note: Please do not use the folder \Custom Sensors\Powershell
Scripts to store your files. This remnant from previous software
versions is not used any more and may usually be deleted.
Note: When using custom sensors on the Clust er Probe, please
copy your files to every cluster node installation.
Sensor Settings
546 02.02.2015
priority).
SENSOR SETTINGS
EXE/Script Shows the executable or script file that the sensor executes with
each scan as defined on sensor creation. Once a sensor is created,
Parameters If your executable or script file catches command line parameters,

you can define them here. You can use placeholders as well. For a
full list of all placeholders please see the API documentation
field empty.
Environment Choose if PRTG's command line parameters will also be available as

environment parameters.
Default Environment : Do not provide PRTG placeholders' values
in the environment. Choose this secure option if you are not
sure.
02.02.2015 547
Set placeholders as environment values: From within your

executable or script, the values of PRTG's command line
parameters will be available via environment variables. For
example, you can then read and use the current host value of
the PRTG device this EXE/script sensor is created on from within
your script. This option can mean a security risk, because also
credentials are provided in several variables. For a full list of all
available variables please see the API documentation
executable or script file. Choose between:
Use securit y cont ext of probe service: Run the selected file
under the same Windows user account the probe is running on.
By default, this is the Windows system user account (if not
manually changed).
sensor is created on. Please navigate to parent device settings
288 of this sensor to change these Windows credentials.
EXE Result Define what the sensor will do with the results the executable file
gives back. Choose between:
Writ e EX E result t o disk: Store the last result received from the
script with the file name "Result of Sensor [ID].txt" to the "Logs
(Sensors)" directory (on the Master node, if in a cluster). This is
for debugging purposes. The file will be overridden with each
Writ e EX E result t o disk in case of error: Store the last result
received from the script only if the sensor is in a down status.
The file name is "Result of Sensor [ID].txt" in the "Logs (Sensors)"
directory. Enable this option if you do not want failures to be
overwritten by a following success of the script.
548 02.02.2015
SENSOR DISPLAY
for each channel.
Note: The St ack Unit option for stacking graphs will only work if you explicitly define the
same <unit> for at least two channels. For detailed information about sensor settings please
see the API documentation (Applicat ion Programming Int erface (API) Definit ion 2830 ).
Inherited Settings
described below.
02.02.2015 549
SCANNING INTER VAL
Choose between:
option will apply.
550 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 551
menu bar.
dependent on.
552 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 553
More

Notifications
Others
554 02.02.2015
26 File Sensor
6.8.26 File Sensor
The File sensor monitors a file located on the probe's local disk or a file accessible via Server
Message Block (SMB). You can monitor changes to the file content and file time stamp.
File size
Past time since the file was modified the last time (in days, hours, and minutes, depending on
the elapsed time)
In contrast to the Folder sensor 573 , you can also monitor if the actual content of a specific
file has changed.
File Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/file.png
Remarks
To monitor files on a share, the "LanmanServer" Windows service must run on the target
computer.
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029
PE032
Add Sensor
02.02.2015 555
26 File Sensor
Sensor Settings
priority).
556 02.02.2015
26 File Sensor
SENSOR SPECIFIC
File Name Enter the full path to the file that this sensor will monitor. For
example, enter C:\Windows\file.txt. If the file is located on a
network device, use the Uniform Naming Convention (UNC) path
without the server part (only enter share\folder\file.txt). The server
part (\\server\) is taken from the parent device settings 288 of this
sensor. Enter a valid path and file name.
Note: To provide any shares, the LanmanServer "Server" Windows
service must be running on the target computer.
Check If Specify when the sensor shows a Down status 123 . Choose
between:
File exist s: The sensor shows Down if the file does not exist.
File does not exist : The sensor shows Down if the file exists.
Monitor File Content Specify if the sensor will send a change notification when the
content of the file changes (based on a checksum). Choose
between:
Ignore changes: No action will be taken on change.
Trigger 'change' not ificat ion: The sensor will send an internal
Monitor File Time Specify if the sensor will send a change notification when the
Stamp content of the file's time stamp changes. Choose between:
SENSOR DISPLAY
02.02.2015 557
26 File Sensor
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
558 02.02.2015
26 File Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 559
26 File Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
560 02.02.2015
26 File Sensor
menu bar.
dependent on.
02.02.2015 561
26 File Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
562 02.02.2015
26 File Sensor
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029 PE032

Notifications
Others
02.02.2015 563
27 File Content Sensor
6.8.27 File Content Sensor
The File Content sensor checks a text file (for example, log files) for certain strings and returns
the following:
Line number of the last match

Number of total matches.
Additionally, the sensor quotes matching lines in the sensor message field.
File Content Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/file_c ontent.png
Remarks
This sensor does not support UTF-16 encoded files! In this case, please try use a custom
sensor like the EX E/Script Sensor 533 or the EX E/Script Advanced Sensor 545 .
This sensor does not support binary files officially! If you still try monitoring binary files
contrary to our recommendation, please choose the option Alway s t ransmit t o PRTG t he
ent ire file in section Net work Usage in the sensor settings.
This sensor supports Unix line feeds.
computer.
564 11.02.2015
Add Sensor
Sensor Settings
priority).
SENSOR SPECIFIC
File Name Enter the full path to the file this sensor will monitor. For example,
enter C:\Windows\file.txt. If the file is located on a network device,
use the Uniform Naming Convention (UNC) path without the server
part (you would only enter share\folder\file.txt). The server part (\
\server\) is taken from the parent device settings 288 of this
sensor. Please enter a valid path and file name.
Note: To monitor shares, the LanmanServer "Server" Windows
11.02.2015 565
SENSOR SPECIFIC
Note: If you define a file on your network here, please be aware

that this might produce high network traffic if you define PRTG to
query the entire file with every scanning interval below.
Search String Define the string inside the log file you want to check for. The
input is not case-sensitive. Please enter a string.
Network Usage Define in which way the sensor will transmit the target file to PRTG.
Choose between:
Only t ransmit t o PRTG new lines at t he end of t he file
(default ): This option improves the performance of the sensor. It
sends the whole file only with the first scan to PRTG. With the
following sensor scans, the sensor will only transmit lines which
were appended since the last scan. All other lines (which already
existed in the previous scan) are not sent. The sensor assumes
that they are unchanged and still counts them.
Note: This option is currently in beta status. Please do not
expect that it will work as expected in every usage scenario!
Alway s t ransmit t o PRTG t he ent ire file: The sensor sends the
whole file with every sensor scanning interval to PRTG. If this
results in too much traffic on the target system, we recommend
you to choose the new lines option.
Note: The sensor can transmit only newly added lines in the
following cases:
The file is bigger than at the previous scan, and
the last line in the file at the previous scan still has to be at the
same place in the file.
Note: The sensor supports Windows and Linux line endings (CRLF
resp. LF).
Search Method Define the method you want to provide the search string with. The
pattern must be in one line and only the last matching line will be
given back. Choose between:
Simple st ring search: Search for a simple plain text expression.
Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 2846 section.
Warning Behavior Define under which condition the sensor will show a Warning
status. Choose between:
566 11.02.2015
SENSOR SPECIFIC
Go int o warning st at us when st ring is not found: The sensor

will show a Warning status if there is no match. Otherwise it will
remain in Up status.
Go int o warning st at us when st ring is found: The sensor will
show a Warning status if there is a match. Otherwise it will
remain in Up status.
change.
SENSOR DISPLAY
for each channel.
11.02.2015 567
Inherited Settings
described below.
568 11.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
11.02.2015 569

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
570 11.02.2015
menu bar.
dependent on.
11.02.2015 571
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
572 11.02.2015
28 Folder Sensor
6.8.28 Folder Sensor
The Folder sensor monitors a folder using Server Message Block (SMB). You can monitor file
changes and file ages.
Folder size in bytes

Number of files in the folder
Past time since the last change to a file in the folder ("newest file")
Past time since the oldest modification of a file in the folder ("oldest file")
Note: The Folder sensor counts all files in a folder, including hidden files.
Folder Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/folder.png
Remarks
This sensor counts all files in a folder, including hidden files.
computer.
PE032
02.02.2015 573
28 Folder Sensor
Add Sensor
Sensor Settings
priority).
574 02.02.2015
28 Folder Sensor
FOLDER MONITOR
Folder Name Enter the full path to the folder this sensor will monitor. For
example, enter C:\Windows. If the file is located on a network
device, use the Uniform Naming Convention (UNC) path without the
server part (you would only enter share\folder). The server part (\
\server\) is taken from parent device settings 288 of this sensor.
Please enter a valid path name.
Note: To monitor shares, the LanmanServer "Server" Windows
Sub-Folder Recursion Specify if the sensor will include subfolders in the folder
monitoring. Choose between:
Do not recurse sub-folders: Only monitor the folder specified
above and do not monitor its subfolders.
Monit or t he folder and it s sub-folders (use wit h caut ion!):
Monitor the folder specified above and all of its subfolders.
Note: Recursing subfolders in large directories with a high
number of branches may evoke timeout errors or performance
issues.
Monitor Folder Specify if the sensor will send a change notification when the
Changes content of the folder changes. Choose between:
Ignore changes: Changes to the folder will not trigger a change
notification.
Trigger 'On Change' not ificat ion: The sensor will trigger a
change notification if a file changes its timestamp or filename, or
if there are new or deleted files.
Check of File Ages Specify if the sensor will monitor the folder for certain file ages and
show a corresponding status 123 . Choose between:
Don't check: Do not check for the age of the files in the
specified folder(s).
Show Warning if older: Set the sensor to Warning status if one
of the files in the specified folder is older than a specific time
unit.
Show Error if older: Set the sensor to Down status if one of
the files in the specified folder is older than a specific time unit.
Show Warning if y ounger: Set the sensor to Warning status if
one of the files in the specified folder is younger than a specific
time unit.
Show Error if y ounger: Set the sensor to Down status if one of
the files in the specified folder is younger than a specific time
unit.
File Age Limit This field is only visible if you enable a file age check above. Enter
02.02.2015 the age of a file in the folder that will trigger the sensor's status 575
change if the defined age is undercut respectively exceeded.
The value will be interpreted as days, hours, or minutes, according
28 Folder Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
576 02.02.2015
28 Folder Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 577
28 Folder Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
578 02.02.2015
28 Folder Sensor
menu bar.
dependent on.
02.02.2015 579
28 Folder Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
580 02.02.2015
28 Folder Sensor
More

Notifications
Others
02.02.2015 581
29 FTP Sensor
6.8.29 FTP Sensor
The FTP sensor monitors file servers using File Transfer Protocol (FTP) and FTP over SSL (FTPS).
It shows the response time of the server.
FTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ftp.png
Add Sensor
Sensor Settings
582 02.02.2015
29 FTP Sensor
priority).
SENSOR SPECIFIC
Port Enter the number of the port the sensor tries to connect to.
Please enter an integer value. We recommend using the default
value.
If you do not get a connection, please try another port number.
FTP Mode Specify which FTP mode the sensor uses for the connection.
Choose between:
Use act ive mode
Use passive mode
We recommend using the default value. If you do not get a
connection, please try the passive mode.
TR ANSPOR T-LEVEL SECU R ITY
FTP Specific Specify if the sensor uses an encryption for the connection.
Choose between:
02.02.2015 583
29 FTP Sensor
Use Transport -Level Securit y if available: The sensor tries to

connect via TLS. It determines automatically whether to connect
via explicit or implicit mode. If TLS is not supported by the server,
the sensor tries connect without encryption and is in Up status if
this works.
Enforce Transport -Level Securit y : The connection must be
established using TLS (explicit or implicit mode). Otherwise, the
sensor goes into Down status.
Do not use Transport -Level-Securit y : The sensor connects to
the FTP server without encryption.
Note: You can see in the sensor logs which method the sensor
used previously to connect to the FTP server.
AU THENTICATION
Username Enter a username for the FTP login. Please enter a string or leave
the field empty.
Note: Default username is "anonymous". If the sensor cannot log
onto the FTP server with this username (or another one that you
define), the sensor message shows that the credentials are
incorrect but the sensor status remains Up.
Password Enter a password for the FTP login. Please enter a string or leave
the field empty.
Note: If the sensor cannot log onto the FTP server with this
password, the sensor message shows that the credentials are
incorrect but the sensor status remains Up.
DEBU G OPTIONS
between:
584 02.02.2015
29 FTP Sensor
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 585
29 FTP Sensor
SCANNING INTER VAL
Choose between:
option will apply.
586 02.02.2015
29 FTP Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 587
29 FTP Sensor
menu bar.
dependent on.
588 02.02.2015
29 FTP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 589
30 FTP Server File Count Sensor
6.8.30 FTP Server File Count Sensor
The FTP Server File Count sensor logs on to an FTP server and can monitor changes to files.
It can show the number of files available in the directory listing.
FTP Serv er File Count Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ftp_serv er_file_c ount.png
Remarks

Required .NET version: 2.0.
590 11.02.2015
Add Sensor
Sensor Settings
priority).
SENSOR SETTINGS
Check Method Define how to access the FTP server directory that this sensor
monitors. Choose between:
Check URL: The sensor uses an explicitly defined URL of an FTP
server to access the target directory.
Check folder on parent device: The sensor uses the IP address
or DNS name of the parent device where you add this sensor to
and monitors a defined folder on this device.
11.02.2015 591
SENSOR SETTINGS
FTP URL This field is only visible if you select the URL method above. Enter
the URL that this sensor checks. The URL can look like this:
ftp://10.0.0.1/upload
Note: When you use this method, this sensor does not use the IP
Address/DNS value of the parent device.
Note: You can add a port number to the URL by using a colon, for
example, ftp://10.0.0.1/upload:21
FTP Port This field is only visible if you select the parent device method
above. Enter the number of the port to which this sensor
connects. Default port is 21.
FTP Folder This field is only visible if you select the parent device method
above. Enter the name of the folder on the parent device that this
sensor monitors, for example, upload
Subfolder Recursion This field is only visible if your select the parent device method
above. Define if the sensor additionally monitors the subfolders of
the FTP folder you specify above. Choose between:
Do not recurse subfolders: The sensor monitors only the
folder that you define above and ignores its subfolders.
Monit or t he folder and it s subfolders (use wit h caut ion!): The
sensor recursively checks all subfolders in addition to the folder
that you define above.
Note: Recursing subfolders in large directories with a high
number of branches may evoke timeout errors or performance
issues.
Username Enter the username for the logon to the FTP server. Please enter a
string.
Password Define the password for the logon to the FTP server. Please enter
a string.
File Count Define which file the sensor counts. Choose between:
Count t he t ot al number of files: The sensor always shows the
total number of all files in the defined folder.
Count only new files: The sensor shows only the number of
new files since the last sensor scan. You can define the
frequency of sensor scans in section Scanning Int erval 594 .
Note: With the every sensor scan, any new files from the
previous scan will be regarded as old.
592 11.02.2015
SENSOR SETTINGS
Security Define the the encryption of the connection. Choose between:

Do not use an encry pt ion: The sensor connects without
encryption.
Use explicit SSL: The sensor establishes the connection to the
FTP server via SSL.
Note: This sensor type supports only explicit SSL.
change.
DEBU G OPTIONS
between:
SENSOR DISPLAY
11.02.2015 593
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
594 11.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
11.02.2015 595

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
596 11.02.2015
menu bar.
dependent on.
11.02.2015 597
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
598 11.02.2015

Notifications
Others
11.02.2015 599
31 Google Analytics Sensor
6.8.31 Google Analy tics Sensor
The Google Analytics sensor queries data from a Google Analytics account via Hypertext
Transfer Protocol (HTTP).
It can show the values for different metrics in different sensor channels, for example:
percentNewVisits
adClicks
adCost
exceptions
exceptionsPerScreenview
fatalExceptions
fatalExceptionsPerScreenview
goalCompletionsAll
goalConversionRateAll
pageviews
percentNewVisits
visits
sensor setup. Please see section More 608 for how to find out available metrics.
600 02.02.2015
Google Analy tic s Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/google_analy tic s.png
Remarks
You have to enable Access for less secure apps in section Account permissions in the
Securit y settings of your Google account for this sensor. Otherwise, you might get the
error message "The remote server returned an error. (403) Forbidden."
This sensor type cannot inherit the scanning interval 242 of parent objects 83 . Please set it
individually below.
Requires 602 .NET 4.0 or later on the probe system.
Knowledge Base: Where do I find my Google Analytics Profile ID?
Knowledge Base: Where do I find available Google Analytics metrics?
02.02.2015 601

Add Sensor
Sensor Settings
priority).
602 02.02.2015
GOOGLE ANALYTICS SETTINGS
Period (Interval) Enter how often the sensor will query data. This setting substitutes
the scanning interval setting. Choose between:
1 Day
2 Day s
3 Day s
1 Week
Username Enter the username of the Google Analytics account you want to
query. Please enter a string.
Password Enter the password of the Google Analytics account you want to
query. Please enter a string.
Profile ID Enter the 8-digits profile ID of the Google Analytics account. For
help, please see More 608 section below.
Metrics Enter a comma separated list with all metrics you want to query. A
default set of metrics is already predefined. For help, please see
More 608 section below.
This sensor also supports the "exception" metrics exceptions,
fatalExceptions, exceptionsPerScreenview, and
fatalExceptionsPerScreenview.
Days Define for how many past days the sensor queries data. Enter 1 to
query yesterday's data only, or define any number of days. Please
enter an integer value. The highest possible value is 366.
Average Define if the sensor will query averaged data. Select between:
Use averaged dat a: Query averaged data. This setting only
takes effect if your entered a higher number than "1" in the Day s
setting above. Data is averaged over the number of days defined
there.
Do not use averaged dat a: Do not query averaged data, but
receive raw data.
DEBU G OPTIONS
between:
02.02.2015 603
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
604 02.02.2015
Note: For Google Analytics sensors, the scanning interval cannot be inherited. Please use the
individual settings of the sensor to define the interval in which data is received.

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 605

menu bar.
dependent on.
606 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 607
More
Knowledge Base: Where do I find my Google Analytics profile ID?
Knowledge Base: Where do I find available Google Analytics metrics?



608 02.02.2015
Notifications
Others
02.02.2015 609
32 HTTP Sensor
6.8.32 HTTP Sensor
The HTTP sensor monitors a web server using Hypertext Transfer Protocol (HTTP). This is the
easiest way to monitor if a website (or a specific website element) is reachable.
It shows the loading time of a web page or element.
HTTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http.png
Add Sensor
Sensor Settings
610 02.02.2015
32 HTTP Sensor
priority).
HTTP SPECIFIC
below.
below.
02.02.2015 611
32 HTTP Sensor
HTTP SPECIFIC
Content Type This setting is only visible when you select the POST Request
Met hod setting above. Define the content type of a POST request.
Choose between:
Default (applicat ion/x-www-form-urlencoded): This is the
default content type used to encode the form data set for
submission to the server.
Cust om: If you need another content type than default, enter
this content type below.
Custom Content Type This field is only visible when you select Cust om above. Define the
content type which is needed, for example, XML, JSON, HTTP.
Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the
TLS protocol.
SENSOR DISPLAY
for each channel.
612 02.02.2015
32 HTTP Sensor
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 613
32 HTTP Sensor
SCANNING INTER VAL
Choose between:
option will apply.
614 02.02.2015
32 HTTP Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 615
32 HTTP Sensor
menu bar.
dependent on.
616 02.02.2015
32 HTTP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

02.02.2015 617
32 HTTP Sensor

Notifications
Others
618 02.02.2015
33 HTTP Advanced Sensor
6.8.33 HTTP Advanced Sensor
The HTTP Advanced sensor monitors the source code of a web page using Hypertext Transfer
Protocol (HTTP). It supports authentication, content checks, and other advanced parameters.
Loading time
Bytes received
Download bandwidth (speed)
Time to first byte
HTTP Adv anc ed Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_adv anc ed.png
Remarks
Supports Smart URL Replacement 633 .
Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?
02.02.2015 619
Add Sensor
Sensor Settings
priority).
HTTP SPECIFIC
620 02.02.2015
HTTP SPECIFIC
below.
below.
Content Type This setting is only visible when you select the POST Request
Met hod setting above. Define the content type of a POST request.
Choose between:
Default (applicat ion/x-www-form-urlencoded): This is the
default content type used to encode the form data set for
submission to the server.
Cust om: If you need another content type than default, enter
this content type below.
Custom Content Type This field is only visible when you select Cust om above. Define the
content type which is needed, for example, XML, JSON, HTTP.
02.02.2015 621
HTTP ENGINE
Monitoring Engine If you encounter unexpected errors with the standard method that
is used to monitor an URL, try to use the compatibility mode which
is based on .NET. Choose between:
Default /High Performance (recommended): This is the default
monitoring method for this sensor type.
Alt ernat e/Compat ibilit y Mode: Try this method as an
alternative for websites that do not work with the default
approach. Using the compatibility mode, this sensor executes an
external exe. Because of this, this method needs more
resources, but it can be helpful in particular cases.
Note: If you select the compatibility mode, the options for the
SSL method will be slightly different. You can also check for
trusted certificates. Please see below.
Note: When using the Compatibility Mode, Smart URL
Replacement will not work, so this sensor will not use the IP
Address/DNS value of the parent device automatically then.
SSL SPECIFIC (WHEN U SING COMPATIBILITY MODE)
SSL Method When using the compatibility mode, the SSL specific settings are a
bit different to the default (automatically used) SSL settings. You
can choose between:
SSL V3
TLS V1
SSL V3 or TLS V1: This is the default setting.
Check SSL Certificates Specify if the sensor will check the certificate of the monitored
URL. Choose between:
Do not check used cert ificat es: Do not consider the
certificates of the monitored web pages. This the default setting.
Check if t he used cert ificat es are t rust ed: Inspect the
certificates. If the certificate of the server is not trusted, the
sensor shows a Down status and displays a corresponding
message.
TLS protocol.
622 02.02.2015
ADVANCED SENSOR DATA
Protocol Version Define the HTTP protocol version that the sensor uses when
connecting to the URL. Choose between:
HTTP 1.0
HTTP 1.1: This is the default setting.
User Agent Choose which user agent string will be sent by this sensor when
connecting to the URL defined above. Choose between:
Use PRTG's default st ring: Do not enter a specific user agent,
use default setting. Usually, this is: Mozilla/5.0 (compatible; PRTG
Network Monitor (www.paessler.com); Windows)
Use a cust om st ring: Use a custom user agent. Define below.
Custom User Agent This field is only visible if you enable custom user agent above.
Enter a string which will be used as user agent when connecting to
the URL specified above.
Use Custom HTTP Define if you want to send custom HTTP headers to the target URL.
Headers Choose between:
Do not use cust om HTTP headers
Use cust om HTTP headers
Custom HTTP Headers This field is only available if you select using custom headers
above. Enter a list of custom HTTP headers with theirs respective
values that you want to transmit to the URL you define above,
each pair in one line. The syntax of a header-value pair is
header1:value1
Note: The sensor does not accept the header field names user-
agent, content-length, host.
Note: Ensure that the HTTP header statement is valid! Otherwise,
the sensor request will not be successful.
Content Changes Define what the sensor will do if the content of the monitored web
page (element) changes. You can choose between:
message indicating that the web page content has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2484 whenever the web page content
changes.
02.02.2015 623
Require Keyword Define if the sensor will check the result at the configured URL for
keywords. Choose between:
Do not check for key word (default ): Do not search for
keywords in the result returned at the URL.
Set sensor t o warning if key word is missing: Check if a
keyword exists in the result and set the sensor to a Warning
status 123 if yes.
Set sensor t o error if key word is missing: Check if a keyword
exists in the result and set the sensor to a Down status 123 if
yes.
Note: The content check is only intended for html websites and
might not work with other target URLs. For example, binary files
are not supported.
Response Must Include This field is only visible if you enable keyword checking above
(include). Define which string must be part of the source code at
the given URL. You can either enter plain text or a Regular
Expression 2846 . Specify below. If the data does not include the
search pattern, the sensor will show the status defined above.
Check Method Define in which format you have entered the search expression in
the field above.
St ring search (default ): Search for the string as plain text. The
characters * and ? work here as placeholder, whereas * stands
for no or any number of characters and ? stands for exactly one
character (as known from Windows search). This behavior cannot
be disabled, so the literal search for these characters is not
possible with plain text search. You can also search for HTML
tags.
Regular Expression: Use the search pattern as a Regular

Expression 2846 .
Exclude Keyword Define if the sensor will check the result at the configured URL for
keywords. Choose between:
Do not check for key word (default ): Do not search for
keywords in the result returned at the URL.
Set sensor t o warning if key word is found: Check if a
keyword exists in the result and set the sensor to a Warning
status 123 if yes.
624 02.02.2015
Set sensor t o error if key word is found: Check if a keyword

exists in the result and set the sensor to a Down status 123 if
yes.
might not work with other target URLs. For example, binary files
are not supported.
Response Must Not This field is only visible if you enable keyword checking (exclude)
include above. Define which string must not be part of the source code at
the given URL. You can either enter plain text or a Regular
Expression 2846 . If the data does include this string, the sensor will
show the status defined above. Please enter a string.
Check Method Define in which format you have entered the search expression in
the field above.
St ring Search (default ): Search for the string as plain text. The
characters * and ? work here as placeholder, whereas * stands
for no or any number of characters and ? stands for exactly one
character (as known from Windows search). This behavior cannot
be disabled, so the literal search for these characters is not
possible with plain text search. You can also search for HTML
tags.
Regular Expression: Use the search pattern as a Regular
Expression 2846 .
Limit Download (kb) Enter a maximum amount of data that the sensor can transfer per
every single request. If you set content checks, please be aware
that only the content downloaded up to this limit can be checked
for search expressions.
Result Handling Define what the sensor will do with the web page loaded at the
given URL. Choose between:
Discard HTML result : Do not store the requested web page.
St ore lat est HTML result : Store the last result of the requested
web page to the "Logs (Sensors)" directory (on the Master node,
if in a cluster). File name: Result of Sensor [ID].txt. This is for
debugging purposes, especially in combination with content
checks. The file will be overridden with each scanning interval.
For information on how to find the folder used for storage,
please see Dat a St orage 2871 section.
02.02.2015 625
Note: This sensor loads the source code at the given URL. If you set up a content check, only
this source code is checked for the keywords. The code is not necessarily identical to the one
used to display the page when opening the same URL in a web browser, as there may be a
reload configured or certain information may be inserted after loading, for example, via
Javascript. PRTG does not follow links to embedded objects nor does it execute scripts. Only
the first page at the given URL is loaded and checked against the expressions configured. For
debugging, please use the Result Handling option to write the source code file to disk and
look up what exactly PRTG gets when calling the URL. If the URL configured does not point to
a web page, but to a binary file, for example, to an image, you usually will not check for
content.
AU THENTICATION
Authentication Define if the web page at the configured URL needs authentication.
Choose between:
No aut hent icat ion needed
Web page needs aut hent icat ion
User This field is only visible if you enable authentication above. Enter a
username. Please enter a string.
Password This field is only visible if you enable authentication above. Enter a
password. Please enter a string.
Authentication Method This field is only visible if enable authentication above. Select the
authentication method the given URL is protected with. Choose
between:
Basic access aut hent icat ion (HTTP): Use simple HTTP
authentication. This is the default setting and suitable for most
cases.
Note: This authentication method transmits credentials as plain
text.
Windows NT LAN Manager (NTLM): Use the Microsoft NTLM

protocol for authentication. This is sometimes used in intranets
for single sign-on.
Digest Access Aut hent icat ion: Use digest access
authentication that applies a hash function to the password
which is safer than basic access authentication.
626 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 627
628 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 629

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
630 02.02.2015
menu bar.
dependent on.
02.02.2015 631
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
632 02.02.2015

More

Notifications
Others
02.02.2015 633
34 HTTP Apache ModStatus PerfStats Sensor
6.8.34 HTTP Apache M odStatus PerfStats Sensor
The HTTP Apache ModStatus PerfStats sensor monitors performance statistics of an Apache
web server using mod_status over Hypertext Transfer Protocol (HTTP).
It can show the following about the Apache at scan time:
CPU load
Server uptime
Requests per second
Bytes per request
Number of current busy workers threads
Number of idle worker threads
sensor setup.
HTTP Apac he ModStatus PerfStats Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_apac he_modstatus_perfstats.png
Remarks
634 02.02.2015
Add Sensor
Sensor Settings
priority).
HTTP SPECIFIC
URL Enter the URL to the mod_status module on your Apache server.
PRTG will append a "/server_status?auto" part automatically. If you
enter an absolute URL, this address will be independent from the IP
address/DNS name setting of the device this sensor is created
on.
02.02.2015 635
HTTP SPECIFIC
below.
TLS protocol.
AU THENTICATION
Choose between:
between:
cases.
text.
for single sign-on.
636 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 637
638 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 639

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
640 02.02.2015
menu bar.
dependent on.
02.02.2015 641
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

642 02.02.2015

Notifications
Others
02.02.2015 643
35 HTTP Apache ModStatus Totals Sensor
6.8.35 HTTP Apache M odStatus Totals Sensor
The HTTP Apache ModStatus Totals sensor monitors the activity of an Apache web server
using mod_status over Hypertext Transfer Protocol (HTTP).
Number of accesses
Transferred data in kBytes per second
sensor setup.
HTTP Apac he ModStatus Totals Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_apac he_modstatus_totals.png
Remarks
Add Sensor
644 02.02.2015
Sensor Settings
priority).
HTTP SPECIFIC
URL Enter the URL to the mod_status module on your Apache server.
PRTG will append a "/server_status?auto" part automatically. If you
enter an absolute URL, this address will be independent from the IP
address/DNS name setting of the device this sensor is created
on.
below.
TLS protocol.
02.02.2015 645
AU THENTICATION
Choose between:
between:
cases.
text.
for single sign-on.
SENSOR DISPLAY
for each channel.
646 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 647
SCANNING INTER VAL
Choose between:
option will apply.
648 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 649
menu bar.
dependent on.
650 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

02.02.2015 651

Notifications
Others
652 02.02.2015
36 HTTP Content Sensor
6.8.36 HTTP Content Sensor
The HTTP Content sensor monitors a numerical value returned by a Hypertext Transfer Protocol
(HTTP) request. In the returned HTML page, each value must be placed between square
brackets [ ]. See the example 662 below.
It shows the returned numbers in dedicated channels, one channel for each value.
sensor setup.
HTTP Content Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_c ontent.png
Remarks
Knowledge Base: How can I monitor internal values of a web application with PRTG
See also the PRTG manual: HTTP Cont ent SensorExample 662

02.02.2015 653
Add Sensor
HTTP SPECIFIC
Value Type Define what kind of values your HTML file gives back. Choose
between:
Int eger: An integer is expected as return value.
sensor will also display integer values unless they don't produce
a buffer overflow.
Number of Channels Define how many values your HTML file gives back. The sensor
handles each value in its own sensor channel 86 . Each value must
be placed between square brackets [ ]. Enter the number of
bracket-value pairs that the defined URL will return.
Note: Do not enter a number less than the number of values
returned. Otherwise you will get an error message.
Sensor Settings
654 02.02.2015
priority).
HTTP SPECIFIC
Script URL Enter the URL the sensor connects to. It has to be URL encoded! If
you enter an absolute URL, this address will be independent from
the IP address/DNS name setting of the device this sensor is
created on.
below.
Value Type Shows the kind of values the HTML file gives back. Once a sensor
is created, you cannot change this value. It is shown for reference
anew.
TLS protocol.
Content Changes Define what the sensor will do if the content of the monitored web
page changes. Choose between:
02.02.2015 655

message indicating that the web page content has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2484 whenever the web page content
changes.
Sensor Result Define what the sensor will do with the results the sensor
receives. Choose between:
Discard sensor result : Do not store the results.
(ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
AU THENTICATION
Choose between:
between:
cases.
text.
for single sign-on.
656 02.02.2015
AU THENTICATION

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 657
658 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 659

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
660 02.02.2015
menu bar.
dependent on.
02.02.2015 661
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Example
For example, consider a URL http://www.example.com/status.html that returns a PHP script
with the current system status in a simple HTML page as follows:
<html>
<body>
Description: Script gives back current status of disk free (%) and CPU usage (%).
[85.5][12.0]
</body>
</html>
You would configure the HTTP Content sensor using the mentioned script URL, value type
Float , and number of channels 2. The sensor calls the URL with every scanning interval and
only regard the two values in square brackets [ ], handling each of them in one sensor channel.
The additional description text and HTML tags are not necessary; in this example they are
added in case a human calls the URL.
662 02.02.2015
Note: If you define the number of channels as 1, the sensor will read only the first value. The
second value will be ignored. Using 3 as number of channels will result in a sensor error
message.

More
Knowledge Base: How can I monitor internal values of a web application with PRTG?

Notifications
Others
02.02.2015 663
37 HTTP Full Web Page Sensor
6.8.37 HTTP Full Web Page Sensor
The HTTP Full Web Page sensor monitors the full download time of a web page including assets
such as images etc. In the background, it opens the web page in a browser instance to
perform the measurement. Links are not followed.
This sensor shows the loading time of the full web page.
Note: Be careful with this sensor, because it can generate considerable internet traffic if you
use it with a low scanning interval!
HTTP Full Web Page Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_full_web_page.png
Remarks
Knowledge Base: What to do when I see a CreateUniqueTempDir() error message for my
HTTP Full Webpage Sensor?
Knowledge Base: HTTP Full Web Page sensor is unable to navigate. What can I do?
Knowledge Base: How can I change the size of PhantomJS full web page screenshots?
664 02.02.2015
Add Sensor
Sensor Settings
priority).
FU LL PAGE DOWNLOAD SETTINGS
URL Enter the address of the web page that the sensor loads. It has to
be URL encoded! If you enter an absolute URL, this address will be
independent from the IP address/DNS name setting of the device
this sensor is created on.
02.02.2015 665
below.
Browser Engine Define which browser the sensor uses to load the web page.
Choose between:
Chromium (recommended): Use the "WebKit" engine that is
delivered with PRTG to perform the loading test. With each
scanning interval, PRTG will load the URL defined above in an
instance of "Chromium" and measure the time until the page is
fully loaded. This is the recommended setting.
Phant omJS (Headless Webkit ): Use the "PhantomJS" engine. This
engine can have a high impact on your probe system's CPU and
memory load, but there are additional options for result handling
available (see below).
Int ernet Explorer: With each scanning interval, the URL defined
above is loaded in the background in an instance of Internet
Explorer. PRTG uses the Internet Explorer of the system running
the PRTG probe.
Note: For full functionality we strongly recommend installing
Internet Explorer 8 or higher on the system running the PRTG
probe. The probe machine is either the local system (on every
node, if on a cluster probe), or the system running the remote
probe 2848 on which the sensor is created on.
Note: For all browser engines, the same proxy settings are used
that are configured for the Windows user account the PRTG probe
is running on (this is usually the Windows local "system" user
account, if not changed). Those settings are accessible via the
Internet Explorer of this system. If you want to e.g. use a proxy for
this full web page sensor test, please adjust the Internet Explorer's
settings accordingly (on the computer running the probe; on all
nodes, if in a cluster).
browser engine. Choose between:
Use securit y cont ext of probe service (default ): Run the
browser engine under the same Windows user account the PRTG
probe is running on. By default, this is the local Windows
"system" user account (if not manually changed).
666 02.02.2015

sensor is created on. Please go to the sensor's parent device's
settings to change the Windows credentials.
Note: When using the Chromium browser engine above, we
recommended this setting here.
Result Handling This setting is only visible if you select the PhantomJS engine
above. This browser engine can render and store screenshots of
the loaded web page. Choose between:
Discard loaded web page (recommended): Do not store the
requested web page.
St ore lat est screenshot of t he web page: Render and store
the last result of the web page to the "Logs (Sensors)" directory
(on the remote system, when used on a remote probe; on the
Master node, if in a cluster). This is for debugging purposes. The
file will be overridden with each scanning interval. It will be
named after the pattern "Fullpage of Sensor (ID).jpg". For
St ore ongoing screenshot s of t he web page (use wit h
caut ion!): Render and store one new screenshot of the web
page with each sensor scan, and store the pictures in the
"Screenshots (Fullpage Sensor)" directory (on the remote system,
when used on a remote probe). For information on how to find
the folder used for storage, please see Dat a St orage 2871
section. This option can be used to create a visual history of the
web page.
Note: Depending on the monitored website and the scanning
interval of the sensor, this option can create a very high amount
of data! Use with care and make sure you set appropriate data
purging limits in the Sy st em Administ rat ionCore & Probes 2642
settings.
Note: If necessary, you can change the window size of the
rendered screenshots. See section More 674 for details.
Authentication This setting is only visible if you select the PhantomJS engine
above. Define if the monitored web page needs authentication for
access. Choose between:
No aut hent icat ion needed: Access to the web page is granted
without authentication.
02.02.2015 667
Web page needs aut hent icat ion: PRTG automatically tries using
HTTP Basic authentication (BA) or Windows NT LAN Manager
(NTLM) to access the web page with authentication. Enter the
credentials below.
Note: Basic access authentication forwards the credentials in
plain text!
User This setting is only visible if you select the PhantomJS engine with
authentication above. Enter the user name for the web page.
Password This setting is only visible if you select the PhantomJS engine with
authentication above. Enter the password for the web page.
SENSOR DISPLAY
for each channel.
668 02.02.2015
Inherited Settings
described below.
02.02.2015 669
SCANNING INTER VAL
Choose between:
option will apply.
670 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 671
menu bar.
dependent on.
672 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

02.02.2015 673
More
Knowledge Base: What to do when I see a CreateUniqueTempDir() error message for my HTTP
Full Webpage Sensor?
Knowledge Base: HTTP Full Web Page sensor is "unable to navigate". What can I do?
Knowledge Base: How can I change the size of PhantomJS full web page screenshots?
Knowledge Base: What is the difference between "HTTP" and "HTTP Full Web Page" Web Server
sensors?

Notifications
Others
674 02.02.2015
38 HTTP Push Count Sensor
6.8.38 HTTP Push Count Sensor
The HTTP Push Count sensor counts received messages which are pushed via an Hypertext
Transfer Protocol (HTTP) request to the PRTG server. It provides a URL that can be used to
push messages to the PRTG server using HTTP.
It shows the number of received messages per second.
HTTP Push Count Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_push_c ount.png
Remarks
For details about the usage, please see manual section HTTP Push Count SensorHow t o
Use 675 .
Note: This sensor type cannot be used in cluster mode. You can set it up on a local probe or
remote probe only, not on a cluster probe.
How to Use
This function is known as webhook. Basically, a webhook works like a push notification:
Webhooks are usually triggered by some event (for example, a new comment to a blog post)
and send according information to a specified URL. The HTTP Push Count sensor then displays
the number of pushed and received messages.
Use the following URL to receive the HTTP requests of the webhook:
ht t p://<probe_ip>:<port_number>/<token>
05.02.2015 675
Replace the parameters <probe_ip>, <port_number>, and <token> with the corresponding
values. You can define port number and identification token in the sensor settings. The "probe
IP" is the IP address of the system your PRTG probe with the sensor is running on.
Example: http://127.0.0.1:5050/XYZ123
Note: You can use several sensors with the same port and identification token. In this case,
the number of push messages will be shown in each of these sensors.
Add Sensor
Sensor Settings
priority).
676 05.02.2015
HTTP PU SH
Request Method Select the request method of your webhook:

ANY: Do not use any filter for the request method.
GET: Choose this method if your webhook uses GET.
POST: Choose this method if your webhook sends post form
data. Postdata has to be applicat ion/x-www-form-urlencoded
with the same parameters as for GET requests.
Port Enter the port number on which this sensor listens for incoming
HTTP requests. Default is 5050.
Identification Token This is the token that is used to find the matching sensor for the
incoming message. While you create the sensor, this token is
{__guid__}. It is replaced with an automatically generated token after
you have completed the sensor creation. If you want to use
another identification token, you can edit it while or after sensor
creation.
Note: The token will not be replaced automatically if you change it
already during sensor creation.
Incoming Request Define what PRTG will do with the incoming messages. Choose
between:
Discard request : Do not store the pushed messages.
Writ e request t o disk (Filename: "Result of Sensor [ID].t xt "):
Store the last message received from the sensor to the "Logs
(Sensor)" directory (on the Master node, if in a cluster). File
name: Request for Sensor [ID].txt. This is for debugging
purposes. The file will be overridden with each scanning interval.
SENSOR DISPLAY
05.02.2015 677
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
678 05.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
05.02.2015 679

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
680 05.02.2015
menu bar.
dependent on.
05.02.2015 681
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
682 05.02.2015
39 HTTP Push Data Sensor
6.8.39 HTTP Push Data Sensor
The HTTP Push Data sensor displays numerical values from received messages which are
pushed via an Hypertext Transfer Protocol (HTTP) request to the PRTG server. It provides a URL
that can be used to push messages to the PRTG server using HTTP.
The sensor shows the received value and an optional message in one channel.
HTTP Push Data Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_push_data.png
Remarks
For details about the usage, please see manual section HTTP Push Dat a SensorHow t o
Use 684 .
05.02.2015 683
How to Use
and send according information to a specified URL. The HTTP Push Data sensor then displays
the data of pushed and received messages.
Use the following URL to receive the HTTP requests of the webhook:
ht t p://<probe_ip>:<port_number>/<token>?value=<integer_or_float>&t ext =<text message>
Replace the parameters <probe_ip>, <port_number>, <token>, and <integer_or_float> with the
corresponding values. The &t ext parameter is optional: You can omit it.
You can define port number and ident ificat ion t oken in the sensor settings.
The probe IP is the IP address of the system on which your PRTG probe with this sensor is
running on.
The value can be an integer or a float value, depending on the data of your application; you
have to set the value type accordingly in the sensor settings. This parameter will be the
sensor value.
Note: If this parameter is missing, the sensor status will be set into a down status.
You can opt ionally add a custom text message by replacing the parameter <text message>
with it. The text will be shown as sensor message. If there is no value but only a text, the
text will be shown as error message.
Note: This text message has to be URL encoded (for example, the whitespaces in the sample
URL below); most browsers achieve this automatically.
Example:
http://127.0.0.1:5050/XYZ123?value=0&text=this%20is%20a%20message
the data of push messages will be shown in each of these sensors.
Remarks
Add Sensor
684 05.02.2015
Sensor Settings
priority).
05.02.2015 685
HTTP PU SH

creation.
between:
686 05.02.2015
HTTP PU SH DATA
No Incoming Data Define which status the sensor will attain if no push message has
been received for at least two sensor scans. Choose between:
Ignore and keep last st at us (default ): The sensor will remain in
the status as defined by the last message received.
Swit ch t o "Unknown" st at us: The sensor will turn into the
Unknown status if it has not received any message for at least
two sensor scans.
Swit ch t o "Error" aft er x minut es: The sensor will turn into
the Error status if it has not received any message within a
defined time span. Define the time threshold below.
Time Threshold This field will only be visible if you selected the error option above.
(Minutes) Enter the time threshold in minutes after which the sensor status
will switch into an Error status if no push message has been
received within this time span. Please enter an integer value.
Value Type Define which type the value of the received data has. If this setting
does not match, the sensor will go into an Error status. Choose
between:
Int eger
Float (with dot "." as delimiter)
SENSOR DISPLAY
for each channel.
05.02.2015 687
SENSOR DISPLAY
Inherited Settings
described below.
688 05.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
05.02.2015 689

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
690 05.02.2015
menu bar.
dependent on.
05.02.2015 691
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
692 05.02.2015
40 HTTP Push Data Advanced Sensor
6.8.40 HTTP Push Data Advanced Sensor
The HTTP Push Data Advanced sensor displays data from received messages which are pushed
via an Hypertext Transfer Protocol (HTTP) request to the PRTG server. It provides a URL that
can be used to push messages to the PRTG server using HTTP.
This sensor can show received values and a message coming in valid XML in multiple
channels.
HTTP Push Data Adv anc ed Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_push_data_adv anc ed.png
Remarks
For details about the usage, please see manual section HTTP Push Dat a Advanced Sensor
How t o Use 694 .
05.02.2015 693
How to Use
and send according information to a specified URL. The HTTP Push Data Advanced sensor then
displays the data of pushed and received messages.
The data which is pushed to this sensor must be valid XML. For details about the return value
format please see the Applicat ion Programming Int erface (API) Definit ion 2830 .
Use the following URLs to receive the HTTP requests of the webhook:
GET requests: ht t p://<probe_ip>:<port_number>/<token>?cont ent =<valid XML>
The XML encoded value of the content parameter has to match the format as defined in the
API documentation 2830 in section Cust om SensorsAdvanced EX E/Script Sensor,
Advanced SSH Script Sensor, and Advanced HTTP Push Dat a Sensor.
POST requests: ht t p://<probe_ip>:<port_number>/<token>
This HTTP request method sends the XML encoded HTTP body as POST data. The body has to
match the format as defined in the API documentation 2830 in section Cust om Sensors
Advanced EX E/Script Sensor, Advanced SSH Script Sensor, and Advanced HTTP Push
Dat a Sensor. We strongly recommend the HTTP content type application/xml.
Replace the parameters <probe_ip>, <port_number>, <token> and <valid XML> (for GET
requests) with the corresponding values:
You can define port number and ident ificat ion t oken in the sensor settings.
The probe IP is the IP address of the system on which your PRTG probe with this sensor is
running on.
The content of GET requests has to be valid XML in the PRTG API format.
Note: The content has to be URL encoded (for example, the whitespaces in the sample URL
below); most browsers achieve this automatically.
Minimum example for t he GET met hod which returns one static channel value:
http://127.0.0.1:5050/XYZ123?content=<prtg><result><channel>MyChannel</channel><value>10</value></result><t
the data of push messages will be shown in each of these sensors.
Add Sensor
694 05.02.2015
priority).
05.02.2015 695
HTTP PU SH

creation.
between:
696 05.02.2015
HTTP PU SH DATA
No Incoming Data Define which status the sensor shows if it did not receive a push
message for at least two sensor scans. Choose between:
Ignore and keep last st at us (default ): The sensor remains in
the status as defined by the last message that the sensor
received.
Note: The probe on which this sensor runs must be connected
to keep the last status. If the probe is disconnected, the sensor
turns into the Unknown status. If the probe is connected again,
the sensor does not automatically return from Unknown to the
last status before the probe disconnect.
Swit ch t o "Unknown" st at us: The sensor turns into the
Unknown status if it did not receive any message for at least two
sensor scans.
Swit ch t o "Error" aft er x minut es: The sensor turns into the
Down status if it has not received any message within a defined
time span. Define the time threshold below.
Threshold (Minutes) This field is only visible if you select the error option above. Enter
the time threshold in minutes after which the sensor switches into
an Down status if it did not receive a push message within this
time span. Please enter an integer value.
SENSOR DISPLAY
for each channel.
05.02.2015 697
SENSOR DISPLAY
Inherited Settings
described below.
698 05.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
05.02.2015 699

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
700 05.02.2015
menu bar.
dependent on.
05.02.2015 701
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
702 05.02.2015
41 HTTP SSL Certificate Expiry Sensor
6.8.41 HTTP SSL Certificate Expiry Sensor
The HTTP SSL Certificate Expiry Sensor checks a specific Hypertext Transfer Protocol Secure
(HTTPS) URL and returns the number of days remaining until the site's SSL certificate expires. It
shows a Warning when only 60 days are left, and a Down status 123 when only 30 days are
remaining until the certificate expires. The sensor reports an error if the certificate is revoked.
The sensor shows the number of days until the expiry of the certificate.
HTTP SSL Certific ate Expiry Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_ssl_c ertific ate_expiry .png
Remarks
Requires 704 .NET 4.0 or later on the probe system.
Note: It might be necessary to run the PRTG probe service with administrative rights if this
sensor does not work (it might show a timeout error with code PE018 without according
rights).
Note: This sensor type might not work on probes running on Windows Server 2003
(including SP1 and SP2).
Knowledge Base: My HTTP sensors could not create an SSL secure channel and are down.
What can I do?
02.02.2015 703

Add Sensor
Sensor Settings
priority).
704 02.02.2015
SENSOR SETTINGS
URL Enter the absolute URL to check for the SSL certificate (this sensor
does not use the IP Address/DNS Name of the parent device). It
has to be URL encoded.
SSL Connection Define the encryption of the connection to the URL configured
above. Choose between:
Use TLS (recommended): The sensor tries to connect via TLS. If
this does not work, the sensor shows a Down status.
Use SSLv3 if available (not recommended): The sensor tries to
connect via TLS or SSL and determines the correct encryption
automatically.
Force usage of SSLv3 (not recommended): The connection
must be established using SSLv3. Otherwise, the sensor goes
into Down status.
Note: The force SSLv3 method does not work when the
requested URL uses forward secrecy. See section More 711 .
Certificate Name Define if you want to check if the defined URL matches the
Validation certificate. Choose between:
The cert ificat e must mat ch t he DNS name: The sensor
compares the certificate and the DNS name. If they do not match,
the sensor shows a Down status 123 .
Accept any cert ificat e: The sensor does not compare the
certificate and the DNS name.
DEBU G OPTIONS
between:
02.02.2015 705
SENSOR DISPLAY
for each channel.
706 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 707
SCANNING INTER VAL
Choose between:
option will apply.
708 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 709
menu bar.
dependent on.
710 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
What can I do?


02.02.2015 711
Notifications
Others
712 02.02.2015
42 HTTP Transaction Sensor
6.8.42 HTTP Transaction Sensor
The HTTP Transaction sensor monitors an interactive website, such as a web shop, by
performing a transaction using a set of Hypertext Transfer Protocol (HTTP) URLs. The sensor
monitors whether logins or shopping carts work properly.
It shows the loading time of single URLs and of the complete transaction.
HTTP Transac tion Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_transac tion.png
Remarks
Knowledge Base: Configuration Tips for HTTP Transaction Sensors
Add Sensor
02.02.2015 713
Sensor Settings
priority).
HTTP SPECIFIC
Timeout (Sec.) Enter a timeout in seconds for all HTTP requests. If the complete
transaction takes longer than this value defines, the sensor
cancels the request and shows an according error message. Please
enter an integer value. The maximum value is 900 seconds (15
minutes).
Single URL Timeout Enter a timeout in seconds for one single HTTP request. If the reply
(Sec.) of any single request takes longer than this value defines, the
sensor cancels the transaction and shows an according error
message. Please enter an integer value. The maximum value is 900
seconds (15 minutes).
714 02.02.2015
HTTP ENGINE
Monitoring Engine If you encounter unexpected errors with the standard method that
is used to monitor an URL, try to use the compatibility mode which
is based on .NET. Choose between:
Default /High Performance (recommended): This is the default
monitoring method for this sensor type.
Alt ernat e/Compat ibilit y Mode: Try this method as an
alternative for websites that do not work with the default
approach. Using the compatibility mode, this sensor executes an
external exe. Because of this, this method needs more
resources, but it can be helpful in particular cases.
Note: If you select the compatibility mode, the options for the
SSL method will be slightly different. You can also check for
trusted certificates. Please see below.
Note: When using the Compatibility Mode, Smart URL
Replacement will not work, so this sensor will not use the IP
Address/DNS value of the parent device automatically then.
SSL SPECIFIC (WHEN U SING COMPATIBILITY MODE)
SSL Method When using the compatibility mode, the SSL specific settings are a
bit different to the default (automatically used) SSL settings. You
can choose between:
SSL V3
TLS V1
SSL V3 or TLS V1: This is the default setting.
Check SSL Certificates Specify if the sensor will check the certificate of the monitored
Do not check used cert ificat es: Do not consider the
certificates of the monitored web pages. This the default setting.
Check if t he used cert ificat es are t rust ed: Inspect the
certificates. If the certificate of the server is not trusted, the
sensor shows a Down status and displays a corresponding
message.
TLS protocol.
02.02.2015 715
Limit Download (kb) Enter a maximum amount of data that is transferred per every
single request. If you set content checks below, please be aware
that the sensor can only check the content downloaded within
this limit for certain search expressions.
Cookie Management Select if cookies are used for the transaction. Choose between:
Use cookies (recommended): Allow cookies to be set and read

during the transaction cycle.
Ignore cookies: Do not allow cookies. Use this option if you
want to test the transaction without the use of cookies.
User Agent Choose which user agent string the sensor sends when
connecting to the defined URLs. Choose between:
Use PRTG's Default St ring: Do not enter a specific user agent,
use the default setting. Usually, this is: Mozilla/5.0 (compatible;
PRTG Network Monitor (www.paessler.com); Windows)
Use a Cust om St ring: Use a custom user agent. Define below.
Custom User Agent This field is only visible if you enable the custom user agent option
above. Enter a string that the sensor uses as user agent when
connecting to the URL specified above.
Result Handling Define what PRTG will do with the web page loaded at the given
Discard HTML result : Do not store the requested web page.
St ore lat est HTML result : Store the last result of the requested
web page to the "Logs (Sensors)" directory (on the Master node,
if in a cluster). File name: Result of Sensor [ID].txt. This is for
debugging purposes, especially in combination with content
checks. The file will be overridden with each scanning interval.
AU THENTICATION
Choose between:
716 02.02.2015
AU THENTICATION
between:
cases.
text.
for single sign-on.
TR ANSACTION U R L
You can define up to 10 different transaction URLs which will all be called in a row. Only if
the complete transaction can be completed, the sensor will be in an Up status 123 . Using this
mechanism you can set up an extended monitoring with multiple URLs. Please enter settings
for at least one transaction URL. You can use as many steps as needed and disable the
other steps.
Transaction Step #x This setting is available for URL #2 through #10. Define if you want
to use this step for your transaction check. Choose between:
Disable st ep #x: Do not use this step. Choose this option if you
do not need all 10 steps for your transaction check.
Enable st ep #x: Enable this step. Further options will be viewed,
as described below.
02.02.2015 717
TR ANSACTION U R L
URL Please enter the URL the sensor will connect to. It has to be URL
encoded! If you enter an absolute URL, this address will be
independent from the IP address/DNS name setting of the device
this sensor is created on. PRTG uses a smart URL replacement
which allows you to use the parent device's IP address/DNS name
setting as part of the URL. For more information, please see
section Smart URL Replacement below.
Request Method The request method determines how the given URL is requested.
below.
Postdata This field is only active when POST is selected in the Request
Met hod setting above. Please enter the data part for the post
request here. Note: No XML is allowed here!
Check For Existing Key Define whether the result at the configured URL will be checked
Words (Positive) for keywords. Choose between:
Disable: Do not search for keywords.
Enable key word check (posit ive): In the result returned at the
URL, check if a key word exists.
might not work with other target URLs.
Response Must Include Define which string must be part of the web at the given URL. If the
data does not include this string, the sensor will be set to an error
state. Please enter a string. Note: Only simple text search is
available here. The characters * and ? work here as placeholder,
whereas * stands for no or any number of characters and ? stands
for exactly one character (as known from Windows search). This
behavior cannot be disabled, so the literal search for these
characters is not possible.
Check For Existing Key Define whether the the result at the configured URL will be
Words (Negative) checked for keywords. Choose between:
718 02.02.2015
TR ANSACTION U R L
Disable: Do not search for keywords.

Enable key word check (negat ive): In the result returned at the
URL, check if a key word does not exist.
might not work with other target URLs.
Response Must Not Define which string must not be part of the web at the given URL.
Include If the data does include this string, the sensor will be set to an
error state. Please enter a string. Note: Only simple text search is
available here. The characters * and ? work here as placeholder,
whereas * stands for no or any number of characters and ? stands
for exactly one character (as known from Windows search). This
behavior cannot be disabled, so the literal search for these
characters is not possible.
SENSOR DISPLAY
for each channel.
02.02.2015 719
Inherited Settings
described below.
720 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 721

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
722 02.02.2015
menu bar.
dependent on.
02.02.2015 723
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

724 02.02.2015
More
Knowledge Base: Configuration Tips for HTTP Transaction Sensors needed

Notifications
Others
02.02.2015 725
43 HTTP XML/REST Value Sensor
6.8.43 HTTP XM L/REST Value Sensor
The HTTP XML/REST Value sensor retrieves an XML file from a given URL and parses it.
It can show the value of a defined XML node.
HTTP XML/REST Value Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_xmlrest_v alue.png
Remarks
Knowledge Base: HTTP XML/REST Value Sensor: FAQ
726 02.02.2015


Add Sensor
SENSOR SETTINGS
Channel Name Enter a name for the channel which will display the value at the
given URL. You can change the name later in the Sensor Channels
Set t ings 2477 .
Sensor Settings
02.02.2015 727
priority).
SENSOR SETTINGS
URL Enter the URL that returns the XML file. It has to be URL encoded! If
independently from the IP Address/DNS Name setting of the
device on which you create this sensor.
738 below.
XML Node (and Enter the name of the node that this sensor checks, or enter a
optional property) node name and a property name to check a property value. To
obtain a value from nested tags, enter the tag names separated by
a slash symbol, for example, use myTag/myTagInside as XML node
value.
Note: You can also check values in JavaScript Object Notation
(JSON) notation. Please see Checking JSON 737 section below.
Note: You can try using XPath syntax here but it does not work in
all cases and we do not provide any technical support for XPath
issues. For further documentation about XPath, please see More
726 section below.
HTTP Username If the URL requires authentication, enter the username. Please
728 02.02.2015
SENSOR SETTINGS
HTTP Password If the URL requires authentication, enter the password. Please
Sensor Value Define what value this sensor shows. Choose between:
Use t he value of t he select ed X ML node: Return the value that
the sensor finds at the specified XML node. If this is non-numeric,
the sensor shows 0.
Use t he number of occurrences of t he select ed X ML node or
it s children/siblings: Return the number of occurrences found.
Define further below.
Count XML Nodes This setting is only visible if you enable the return number option
above. Define which count the sensor shows. Choose between:
Occurrences of t he select ed X ML node: Return how often the
defined XML node occurs at the defined URL.
Child nodes of t he select ed X ML node: Return the number of
child nodes that exist below the node at the defined URL.
Sibling nodes of t he select ed X ML node: Return the number
of sibling nodes that exist next to the node at the defined URL.
Namespaces Define whether namespaces in the XML document are used or not.
Choose between:
Use Namespaces: Process the value you enter in the "XML Node
(and optional property)" field including possibly existing
namespace information.
Remove Namespaces: Ignore namespace information in the XML
document and process the value you enter in the "XML Node
(and optional property)" field as node names only.
For more information see About Namespaces 738 section below.
Content Type in Define what to include in the header of the request sent to the
Header URL defined above. Choose between:
Enable (recommended): This works for most web servers and is
the recommended setting.
Disable: Only very few web servers cannot handle this content-
type and need this setting. Try this if you get an error message
with the enabled option.
Cust om: You can use a custom content type.
Custom Content Type This field is only visible when you enable the custom option above.
Enter a custom content type like text/xml or text/html.
02.02.2015 729
SENSOR SETTINGS
HTTP Headers Optionally enter a list of custom HTTP headers with theirs
respective values that you want to transmit to the URL you define
above. The syntax of a list with header-value pairs is
header1:value1|header2:value2|...|headerx:valuex
Note: The sensor does not accept header field names that include
a dash (-) character. If you want to use such a HTTP header, please
leave out the dash of the name. For example, enter
ContentType:value instead of Content-Type:value.
Example: From:johnqpublic@example.com|AcceptLanguage:en-us
Note: Ensure that the HTTP header statement is valid! Otherwise,
the sensor request will not be successful.
Characters to Remove This field is only visible if you enable the "use value of XML node"
option above. Optionally enter a string that the sensor removes
from the returned XML value. Use this to remove any unwanted
characters from the result, for example, a thousands separator
from numeric values. Please enter a string or leave the field empty.
Decimal Delimiter This setting is only visible if you enable the "use value" option
above. If the sensor value of the selected XML node is of the type
float, you can define any character here which is handled as the
decimal delimiter. Enter one character or leave the field empty.
Custom Message Optionally enter a custom sensor message. Use %1 as a

placeholder to automatically fill in the returned XML value. Please
SSLv3 Connection Define if you want to allow SSLv3 only for connections to the URL
configured above. Choose between:
Use SSLv3 if available
Force usage of SSLv3
Note: The force method does not work when the requested URL
uses forward secrecy. See section More 739 .
change.
730 02.02.2015
SENSOR SETTINGS
Unit String Enter a string that the sensor will add to the retrieved values as a
unit description. This is for display purposes only.
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
02.02.2015 731
Inherited Settings
described below.
732 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 733

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
734 02.02.2015
menu bar.
dependent on.
02.02.2015 735
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
736 02.02.2015
Checking JSON
With the X ML Node (and opt ional propert y ) field you can also check values that are returned
in JavaScript Object Notation (JSON) notation under the defined URL.
Example
A JSON notated section may look like the following:

{
"test": "Hello World",
"object": {
"value": "content",
"AnotherValue": "AnotherContent"
},
"arraytest": [
"one",
"two"
]
}
Depending on your entries in the X ML Node field, the sensor will process the respective
values:
Ent ry in Sensor's "X ML Node" Field (from Processed Value (from Example Above)
Example Above)
test Hello World
object/value content
object/AnotherValue AnotherContent
object contentAnotherContent
arraytest[1] one
arraytest[2] two
02.02.2015 737
About Namespaces
In an XML document, tags may use namespaces.
Example
A namespace notated section may look like the following:

<myNamespace:myNode>
some information
</myNamespace:myNode>
If you set this sensor to Use Namespaces (this is the default setting), it will expect the full
node name, including the namespace information, in the X ML Node (and opt ional propert y )
field. In the example above, this would be myNamespace:myNode.
If your node names are unique even without the namespace information, you can simplify the
settings by setting this sensor to Remove Namespaces. The sensor will then expect the
node name only in the X ML Node (and opt ional propert y ) field. In the example above, this
would be myNode.

738 02.02.2015
More
Knowledge Base: Is there a tool available that can help me building queries for the XML/Rest
Sensor?
Knowledge Base: How do I extract values from XML nodes (with nested tags) using PRTG's
XML/Rest Value Sensor?
Knowledge Base: How can I use XPath with PRTG's XML/Rest Value Sensor?
Knowledge Base: HTTP XML/REST Value Sensor shows protocol violation. What can I do?
Knowledge Base: Why does my HTTP XML/REST Value Sensor return a 404 error?
What can I do?


Notifications
Others
02.02.2015 739
44 Hyper-V Cluster Shared Volume Disk Free Sensor
6.8.44 Hy per-V Cluster Shared Volume Disk Free Sensor
The Hyper-V Cluster Shared Volume Disk Free sensor monitors a Microsoft Hyper-V cluster
shared volume via PowerShell.
Available disk space in percent

Available disk space in bytes
Total disk space
Hy per-V Cluster Shared Volume Disk Free Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/

Hy per_V_Cluster_Shared_Volume_Disk_Free.png
Remarks
Requires 741 Remote PowerShell on the target device.
Requires 741 WSFC PowerShell Interface on the target device.
sensor on.
Note: The parent device for this sensor must be a Windows server running Hyper-V.
Knowledge Base: Why don't my Hyper-V sensors work after changing names?
740 02.02.2015
Requirement: Remote PowerShell

The Hyper-V Cluster Shared Volume Disk Free sensor uses PowerShell commands. In order to
monitor devices with this sensor Remot e PowerShell has to be enabled.
For detailed information, please see More 749 section below.
Requirement: WSFC PowerShell Interface

This sensor type needs the WSFC (Windows Server Failover Clustering) PowerShell Interface to
be installed on the target machine. You can list all modules in the PowerShell console with the
command Get -Module -List Available. Here FailoverClust ers has to appear. Under Windows
2008 and 2012 the interface is part of the VMM Administrator Console, or the VMM 2012
Management Console, respectively.
The interface is everywhere available where the WSFC feature is installed: Windows Server
2008 R2 (SP1) Full and Core (not installed by default); Microsoft Hyper-V Server 2008 R2 (SP1);
Remote Server Administration Tools (RSAT) for Windows 7 (SP1).

Add Sensor
Select the disks you want to monitor. PRTG creates one sensor for each disk you choose in
are created.
02.02.2015 741
DISK FR EE SETTINGS
Disk Select the disks you want to add a sensor for. You see a list with
head.
Note: Ensure the resource name of your disks do not contain
unsupported characters, especially avoid the hash ('#') sign. We
recommend to not rename resource disk name once you have set
up monitoring. For detailed information, please see More 767
section below.
Sensor Settings
priority).
742 02.02.2015
DISK FR EE SETTINGS
Disk Shows the name of the disk. Once a sensor is created, you cannot
change this value. It is shown for reference purposes only. If you
need to change this, please add the sensor anew.
between:
SENSOR DISPLAY
for each channel.
02.02.2015 743
Inherited Settings
described below.
744 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 745

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
746 02.02.2015
menu bar.
dependent on.
02.02.2015 747
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
748 02.02.2015
More



Notifications
Others
02.02.2015 749
45 Hyper-V Host Server Sensor
6.8.45 Hy per-V Host Server Sensor
The Hyper-V Host Server sensor monitors a Microsoft Hyper-V host server via Windows
Performance Counters or Windows Management Instrumentation (WMI), as configured in the
"Windows Compatibility Options" of the parent device.
CPU usage in percent of guests, hypervisor, and total

Number of host health critical values
Number of deposited pages
Network traffic: Sums up the total bytes per second (received and sent) on all ports of your
virtual switch.
Hy per-V Host Serv er Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hy per_v _host_serv er.png
Remarks
sensor on.
Requires 751 Windows Server 2008 or later on the probe system.
Requires 751 the Remote Registry Windows service to be running on the target computer.
750 02.02.2015
Uses a hybrid approach 751 with Windows Performance Counters and WMI as fallback to query
data. Please stay below 200 WMI sensors per probe!
Note: The parent device for this sensor must be a Windows server running Hyper-V.
Hybrid Approach: Performance Counters and WMI

By default, this sensor type uses a hybrid approach, first trying to query data via Windows
Performance Counters (which needs less system resources), and using Windows Management
Instrumentation (WMI) as a fallback in case Performance Counters are not available. When
running in fallback mode, the sensor will re-try to connect via Performance Counters after 24
hours. You can change the default behavior in the Windows Compat ibilit y Opt ions of the
parent device's settings 298 this sensor is created on.
Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on
the system performance! Try to stay below 200 WMI sensors per probe 77 . Above this number,
please consider using multiple Remot e Probes 2848 for load balancing.
section.

target computer. If you fail to do so, a connection via Performance Counters will not be
possible. However, WMI connections may still work.
Requirement: Windows Version

In order for this sensor to work with Windows Performance Counters, please make sure a
Windows version 2008 or later is installed on the computer running the PRTG probe: This is
either on the local system (on every node, if on a cluster probe), or on the system running a
remote probe 2848 .
Requirement: Remote Registry Service

In order for this sensor to work with Windows Performance Counters, please make sure the
Remote Registry Windows service is running on the target computer. If you fail to do so, a
connection via Performance Counters will not be possible. However, WMI connections may still
work.
To enable the service, please log in to the respective computer and open the services
manager (e.g. via services.msc). In the list, find the respective service and set its Start Type to
Automatic.
02.02.2015 751
Add Sensor
Sensor Settings
priority).
DEBU G OPTIONS
between:
752 02.02.2015
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 753
SCANNING INTER VAL
Choose between:
option will apply.
754 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 755
menu bar.
dependent on.
756 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 757
46 Hyper-V Virtual Machine Sensor
6.8.46 Hy per-V Virtual M achine Sensor
The Hyper-V Virtual Machine sensor monitors a virtual machine running on a Microsoft Hyper-V
host server via Windows Performance Counters or Windows Management Instrumentation
(WMI), as configured in the "Windows Compatibility Options" of the parent device.
CPU usage in percent of guests, hypervisor, and total

IDE disk read speed (bytes per second)
IDE disk write speed (bytes per second)
sensor setup.
Hy per-V Virtual Mac hine Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hy per_v _v irtual_mac hine.png
Remarks
sensor on.
758 02.02.2015
Note: The parent device for this sensor must be a Hyper-V server or a System Center Virtual
Machine Manager (SCVMM).
Note: We recommend using System Center Virtual Machine Manager (SCVMM) as parent
device, because this way PRTG will continue to monitor your virtual machines also when they
change the physical host using Live Migration.
Note: To monitor a virtual machine with this sensor, disable User Account Control (UAC) in
the control panel of the Windows operating system which is running on this virtual machine.
Otherwise, the sensor might switch into a Down status with the error message "The virtual
machine is not running or is powered off".

section.


remote probe 2848 .
02.02.2015 759

work.
Automatic.
Add Sensor
Select the virtual machines you want to monitor. PRTG creates one sensor for each VM you
choose in the Add Sensor dialog. The settings you make in this dialog are valid for all of the
Virtual Machine Select the virtual machines (VMs) you want to add a sensor for,
including the ones that are not running. You see a list with the
names of all items which are available to monitor. Select the
head.
Note: Ensure the name of your VMs do not contain unsupported
characters, especially avoid the hash ('#') sign. We recommend to
not rename virtual machines once you have set up monitoring. For
detailed information, please see More 767 section below.
Sensor Settings
760 02.02.2015
priority).
GUID Shows the Globally Unique Identifier (GUID) of the virtual machine
that this sensor monitors. Once a sensor is created, you cannot
Name Shows the name of the virtual machine that this sensor monitors.
Description Shows information about the virtual machine. Once a sensor is

anew.
Powered Off VMs Define how to react to a virtual machine that is powered off.
Choose between:
Alarm when powered off: The sensor will change to a Down 123
status if the virtual machine is powered off. Note: While in Down
status, a sensor does not record any data in all of its channels.
Ignore powered off st at e: The sensor will not change to a
Down status if the virtual machine is powered off. It will report
zero values instead.
02.02.2015 761
between:
SENSOR DISPLAY
for each channel.
762 02.02.2015
Inherited Settings
described below.
02.02.2015 763
SCANNING INTER VAL
Choose between:
option will apply.
764 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 765
menu bar.
dependent on.
766 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 767
Others
768 02.02.2015
47 Hyper-V Virtual Network Adapter Sensor
6.8.47 Hy per-V Virtual Network Adapter Sensor
The Hyper-V Network Adapter sensor monitors virtual network adapters running on a
Microsoft Hyper-V host server via Windows Performance Counters or Windows Management
Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent
device.
Sent, received, and totally transferred bytes

Sent and received packets per second
Sent and received broadcast packets per second
Sent and received directed packets per second
Sent and received multicast packets per second
sensor setup.
02.02.2015 769
Hy per-V Virtual Network Adapter Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hy per_v _v irtual_network_adapter.png
Remarks
sensor on.
Note: The parent device for this sensor must be a Hyper-V server.
770 02.02.2015

section.


remote probe 2848 .

work.
Automatic.
02.02.2015 771
Add Sensor
Select the network adapters you want to monitor. PRTG creates one sensor for each adapter
you choose in the Add Sensor dialog. The settings you make in this dialog are valid for all of
the sensors that are created.
Hyper-V Virtual Select the virtual network adapters you want to add a sensor for.
Network Adapter You see a list with the names of all items which are available to
monitor. Select the desired items by adding check marks in front of
the respective lines. PRTG creates one sensor for each selection.
You can also select and deselect all items by using the check box
in the table head.
Note: We recommend you to not rename virtual machines once
you have set up monitoring. Renaming them will also change the
internal virtual network adapter names, causing the monitoring to
be interrupted. For detailed information about virtual machine
naming, please see More 767 section below.
Sensor Settings
772 02.02.2015
priority).
HYPER -V VIR TU AL NETWOR K ADAPTER SETTINGS
Virtual Network Shows the name of the virtual network adapter monitored by this
Adapter sensor. Once a sensor is created, you cannot change this value. It
between:
SENSOR DISPLAY
02.02.2015 773
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
774 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 775

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
776 02.02.2015
menu bar.
dependent on.
02.02.2015 777
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: Why don't my Hyper-V Virtual Machine sensors work after changing names?

Notifications
778 02.02.2015
Others
02.02.2015 779
48 Hyper-V Virtual Storage Device Sensor
6.8.48 Hy per-V Virtual Storage Device Sensor
The Hyper-V Virtual Storage sensor monitors a virtual storage device running on a Microsoft
Hyper-V host server via Windows Performance Counters or Windows Management
Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent
device.
Read speed in bytes per seconds

Write speed in bytes per second
Number of errors
sensor setup.
Hy per-V Virtual Storage Dev ic e Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hy per_v _v irtual_storage_dev ic e.png
Remarks
sensor on.
780 02.02.2015
Note: The parent device for this sensor must be a Hyper-V server.
Note: This sensor does not support Live Migration.

section.


remote probe 2848 .

work.
02.02.2015 781
Automatic.
Add Sensor
Select the storage devices you want to monitor. PRTG creates one sensor for each storage
HYPER -V VIR TU AL STOR AGE DEVICE SETTINGS
Hyper-V Virtual Storage Select the virtual storage devices you want to add a sensor for.
Device You see a list with the names of all items which are available to
in the table head.
Sensor Settings
782 02.02.2015
priority).
HYPER -V VIR TU AL STOR AGE DEVICE SETTINGS
Virtual Storage Device Shows the unique identifier of the device that this sensor
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
between:
SENSOR DISPLAY
02.02.2015 783
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
784 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 785

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
786 02.02.2015
menu bar.
dependent on.
02.02.2015 787
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
788 02.02.2015
49 IMAP Sensor
6.8.49 IM AP Sensor
The IMAP sensor monitors a mail server using Internet Message Access Protocol (IMAP).
Response time of the mail server

Number of emails in the defined mailbox
It can also check the content of emails for certain key words. This way, you can use this
sensor to monitor backup solutions via emails that are sent out by these solutions. For
more information, see section More 801 .
IMAP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/imap.png
Remarks
Note: If you use content checks, we recommend using a dedicated IMAP account that is only
checked by PRTG. Editing existing mails in the mailbox of the monitored IMAP account can
lead to false alarms or malfunctions of this sensor type.
Note: This sensor type might not work properly when monitoring sub-folders of mailboxes. If
it has to check subsequent emails with identical subjects, later on incoming emails might not
be recognized.
Knowledge Base: My IMAP sensor does not process HTML emails correctly using regex. What
can I do?
02.02.2015 789
49 IMAP Sensor
Knowledge Base: How can I monitor my backup software to be sure backup succeeded last
night?
Add Sensor
Sensor Settings
priority).
IMAP SPECIFIC
790 02.02.2015
49 IMAP Sensor
IMAP SPECIFIC
Port Enter the number of the port that the sensor uses to connect via
IMAP. For non-secure connections, usually port 143 is used. For
SSL connections it is usually port 993. The actual setting depends
on the server you are connecting to. Please enter an integer value.
AU THENTICATION
Username Enter a username for IMAP authentication. Please enter a string.
Password Enter a password for IMAP authentication. Please enter a string.
Sensor Specific Define the security level for the sensor connection. Choose
between:
Use Transport -Level Securit y if available using St art TLS
(default ): Choose this option to try connecting to the server
using TLS and StartTLS. If the server does not support this, the
sensor will try connecting without encryption.
Use Transport -Level Securit y if available: Choose this option
to try connecting to the server using TLS. If the server does not
support this, the sensor will try connecting without encryption.
Enforce Transport -Level Securit y using St art TLS: Choose this
option to try connecting to the server using TLS and StartTLS. If
the server does not support this, the sensor will show a Down
status 123 .
Enforce Transport -Level Securit y : Choose this option to try
connecting to the server using TLS. If the server does not
support this, the sensor will show a Down status 123 .
If the sensor connects to a server via StartTLS, the connection is
established unencrypted first. After the connection is established,
the sensor sends a certain command (StartTLS) over the
unencrypted connection to negotiate a secure connection via the
SSL/TLS protocol.
If the sensor uses TLS without StartTLS, the negotiation of a
secure connection happens immediately (implicitly) so that no
commands are sent in unencrypted plain text. If there is no secure
connection possible, no communication will take place.
02.02.2015 791
49 IMAP Sensor
IDENTIFY EMAIL
Process Email Content This sensor can additionally check the content of all incoming
emails. Choose between:
Do not check email cont ent : Only check availability of the IMAP
server and check if a login is successful (if defined). Do not
process any emails in the IMAP email account.
Read email count : Count the emails in the defined mailbox.
Process emails in t his mailbox: Login in to the IMAP email
account and check the emails which it contains. Define further
options below.
Mailbox Name This field is only visible if you enable email counting or content
processing above. Enter the name of the mailbox (for example, the
name of the IMAP folder) that the sensor checks. Default value is
Inbox. Unless you set a last message date check below, the
sensor will always look at all emails contained in the mailbox.
Note: Ensure you do not manually edit emails in this mailbox with
another email client because this can result in malfunctions of this
sensor's email identification.
Identify by "From" Field This option is only visible if you enable email content processing
above. Define if you want to check the "From" field of the emails.
Choose between:
Don't check: Do not process this field in emails.
Check using st ring search: Process this field in emails using
simple string search.
Check using regular expression: Process this field in emails
using a regular expression. For more information about syntax,
please see Regular Expressions 2846 section.
When using a search, the sensor will scan all emails from the
newest to the oldest.
Note: The sensor finishes the scan with the first match! This means
that after it finds a match in one email, there will be no further
checks performed in older emails.
Search For This field is only visible if you enable a "from" check above. Enter a
search string using the method defined above.
Identify by "Subject" This option is only visible if you enable content processing above.
Field Define if you want to check the "Subject" field of the emails.
Choose between:
Don't check: Do not check this field in emails.
792 02.02.2015
49 IMAP Sensor
IDENTIFY EMAIL
Check using st ring search: Check this field in emails using

simple string search.
Check using regular expression: Check this field in emails using
a regular expression. For more information about syntax, please
see Regular Expressions 2846 section.
Search For This field is only visible if you enable a "subject" check above. Enter
a search string using the method defined above.
Identify by Mail Body This option is only visible if you enable content processing above.
Define if you want to check the mail body of the emails. Choose
between:
Don't check: Do not check the mail body.
Check using st ring search: Check the mail body using simple
string search.
Check using regular expression: Check the mail body using a
regular expression. For more information about syntax, please
see Regular Expressions 2846 section.
Search For This field is only visible if you enable checking the mail body above.
Enter a search string using the method defined above.
Check Last Message This option is only visible if you enable content processing above.
Date Define if you want to check all emails in the mailbox, or only mails
that were received within the last x hours. Choose between:
Don't check message age: Always check all emails contained in
the mailbox.
Check for new messages received wit hin t he last x hours:
Only regard emails that were received in the last hours. Define
below.
02.02.2015 793
49 IMAP Sensor
IDENTIFY EMAIL
Error Threshold (Hours) Enter the maximum age in hours. The sensor processes only emails
that are younger. If there is no matching email in the defined time
span, the sensor will show a Down status 123 .
Warning Threshold Enter the maximum age in hours. The sensor processes only emails
(Hours) that are younger. If there is no matching email in the defined time
span, the sensor will show a Warning status 123 .
SENSOR BEHAVIOR
Set to Error This setting is only visible if you enable email content check above.
Define in which cases the sensor will show a Down status 123 .
Choose between:
Never (default ): Never set this sensor to a Down status based
on email content.
Alway s: Always set this sensor to a Down status in case any
emails could be identified.
If subject cont ains
If subject does not cont ain
If mail body cont ains
If mail body does not cont ain
Check Method This setting is only visible if you select an if-condition above.
Define how you want to check for the above condition. Choose
between:
St ring search: Check the mail body using simple string search.
Regular expression: Check the mail body using a regular
expression. For more information about syntax, please see
Regular Expressions 2846 section.
Note: The sensor finished the scan with the first match! This means
Search Text This setting is only visible if you select an if-condition above. Enter
794 02.02.2015
49 IMAP Sensor
SENSOR BEHAVIOR
Error Message This setting is only visible if you select an alarm condition above.
Define the message that the sensor will show for a Down status
123 .
Set to Warning This setting is only visible if you enable content check above.
Define in which cases the sensor will show a Warning status 123 .
Choose between:
Never (default ): Never set this sensor to a Warning status
based on email content.
Alway s: Always set this sensor to a Warning status in case any
emails could be identified.
If subject cont ains
If subject does not cont ain
If mail body cont ains
If mail body does not cont ain
Check Method This setting is only visible if you select an if-condition above.
Define how you want to check for the above condition. Choose
between:
St ring search: Check the mail body using simple string search.
Regular expression: Check the mail body using a regular
expression. For more information about syntax, please see
Regular Expressions 2846 section.
Search Text This setting is only visible if you enable an if-condition above. Enter
Warning Message This setting is only visible if you select a warning condition above.
Define the message that the sensor will show for a Warning status
123 .
No Matching Mail This setting is only visible if you enable content check above.
Behavior Define how the sensor will react if it does not find matching emails
in the mailbox that it scans. Choose between:
Set sensor t o "Down" st at us
Set sensor t o "Warning" st at us
02.02.2015 795
49 IMAP Sensor
SENSOR BEHAVIOR
None: Do not do anything in this case.
Message This field is only visible if you enable a no matching behavior above.
Define the message that the sensor will show if it did not find any
matching emails together with a Warning or Down status as you
define above.
between:
SENSOR DISPLAY
for each channel.
796 02.02.2015
49 IMAP Sensor
Inherited Settings
described below.
02.02.2015 797
49 IMAP Sensor
SCANNING INTER VAL
Choose between:
option will apply.
798 02.02.2015
49 IMAP Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 799
49 IMAP Sensor
menu bar.
dependent on.
800 02.02.2015
49 IMAP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How can I monitor my backup software to be sure backup succeeded last
night?
Knowledge Base: My IMAP sensor does not process HTML emails correctly using regex. What
can I do?

02.02.2015 801
49 IMAP Sensor
Notifications
Others
802 02.02.2015
50 INI File Content Check Sensor
6.8.50 INI File Content Check Sensor
The INI File Content Check sensor reads an *.ini file. It indicates if the file exists and if it
contains a specified section and field. It will show a Warning status 123 if it cannot find a
section or field, and a Down status 123 if it cannot open the file.
The sensor shows the integer value of the requested field in a channel, or -1 if the field does
not contain an integer.
The sensor message shows [section] field = value, no matter of which type the value is.
INI File Content Chec k Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ini_file_c ontent_c hec k.png
Remarks
computer.
sensor on.
Add Sensor
02.02.2015 803
Sensor Settings
priority).
SENSOR SETTINGS
INI File Name Enter the full path to the file that this sensor monitors. For
example, enter C:\Windows\win.ini. If the file is located on a
network device use the Uniform Naming Convention (UNC) path
without the server part (you would only enter share\folder\file.ini).
The server part (\\server\) is taken from the parent device settings
288 of this sensor. Enter a valid path and file name.
Note: In order to provide any shares, the LanmanServer "Server"

Windows service must be running on the target computer.
INI Section Define the section inside the INI file you would like to check. A
section within the INI file is denoted in square brackets [ ]. Enter
the section name without the brackets here, for example, enter
Mail. This value is not case sensitive. If the section is not found, the
sensor will show a Warning status.
804 02.02.2015
SENSOR SETTINGS
INI Field Define the field inside the section you would like to check. In the
INI file, a field name is written before an equal sign =, followed by its
value. Enter the field name here, for example, enter MAPI. This value
is not case sensitive. The sensor will return the value of this field,
which is the value on the right side of the equal sign. If the field is
not found, the sensor will show a Warning status.
change.
SENSOR DISPLAY
for each channel.
02.02.2015 805
Inherited Settings
described below.
806 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 807

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
808 02.02.2015
menu bar.
dependent on.
02.02.2015 809
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
810 02.02.2015
51 IP on DNS Blacklist Sensor
6.8.51 IP on DNS Blacklist Sensor
The IP on DNS Blacklist sensor checks if the IP address of its parent device is listed on specific
blacklist servers.
The sensor shows the number of blacklist hits it can find.
IP on DNS Blac klist Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ip_on_dns_blac klist.png
Remarks
If a DNS name is used as hostname of the parent device, PRTG will resolve it to an IP address
before querying blacklist servers.
During normal operation, there should be 0 hits and the sensor should show a green Up
status 123 . If the sensor can find the IP address on at least one of the blacklist servers, it will
show a yellow Warning status by default. Note: You can set additional thresholds in the
Sensor Channels Settings 2477 .
Knowledge Base: Is there a list of anti spam black list servers?
02.02.2015 811

Add Sensor
Sensor Settings
priority).
812 02.02.2015
SENSOR SETTINGS
Blacklist Servers Define the blacklist servers that the sensor uses for the check.
You can enter a comma separated list. Default is bl.spamcop.net.
For a list of servers, please see More 818 section below.
Note: With each scanning interval, PRTG will query all servers in the
list! We recommend you do not enter more than 10 servers to
make sure the check can be completed within the scanning interval
of this sensor. If you use too many blacklist servers, the sensor
will show a "Timeout (code: PE018)" error message.
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
02.02.2015 813
SENSOR DISPLAY
Inherited Settings
described below.
814 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 815

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
816 02.02.2015
menu bar.
dependent on.
02.02.2015 817
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: Is there a list of anti spam black list servers?

Notifications
818 02.02.2015
Others
02.02.2015 819
52 IPFIX Sensor
6.8.52 IPFIX Sensor
The IPFIX sensor receives traffic data from an IPFIX (Internet Protocol Flow Information Export)
compatible device and shows traffic by type. There are several filter options available to divide
traffic into different channels. Ensure your device supports IPFIX when using this sensor.
This sensor can show the following traffic types in kbit per second:
Chat (IRC, AIM)

Citrix
FTP/P2P (file transfer)
Infrastructure (network services: DHCP, DNS, Ident, ICMP, SNMP)
Mail (mail traffic: IMAP, POP3, SMTP)
NetBIOS
Remote control (RDP, SSH, Telnet, VNC)
WWW (web traffic: HTTP, HTTPS)
Total traffic
Other protocols (other UDP and TCP traffic)
sensor setup.
820 02.02.2015
52 IPFIX Sensor
IPFIX Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ipfix.png
Remarks
Note: You have to enable IPFIX export on the device for this sensor to work. The device
must send the flow data stream to the IP address of the PRTG probe system on which the
sensor is set up (either a local or remote probe).
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
For a general introduction to the technology behind flow monitoring, please see manual
section Monit oring Bandwidt h via Flows 2760 .
Add Sensor
02.02.2015 821
52 IPFIX Sensor
Sensor Settings
priority).
IPFIX SPECIFIC SETTINGS
Receive IPFIX Packets Enter the UDP port number on which the flow packets are
on UDP Port received. It must match the one you have configured in the IPFIX
export options of your hardware router device. Please enter an
integer value.
Sender IP Enter the IP address of the sending device you want to receive the
IPFIX data from. Enter an IP address to receive data from a specific
device only, or leave the field empty to receive data from any
device on the specified port.
Receive IPFIX Packets Select the IP address(es) on which PRTG listens to IPFIX packets.
on IP The list of IP addresses shown here is specific to your setup. To
select an IP address, add a check mark in front of the respective
line or in the top level box to select all. The IP address selected
here must match the one configured in the IPFIX export options of
your hardware router device.
822 02.02.2015
52 IPFIX Sensor
Active Flow Timeout Enter a time span in minutes after which new flow data must be
(Minutes) received. If the timeout is reached and no new data is received, the
sensor may switch to an Unknown status. Please enter an integer
value. We recommend setting this one minute longer than the
respective timeout configured in your hardware router device.
Note: If you set this value too low, flow information might get lost!
Sampling Mode Define if you want to use the sampling mode. This setting must
accord to the setting in the flow exporter. Choose between:
Off: The standard flow will be used.
On: Switch into sampling mode and specify the sampling rate
below.
Sampling Rate This field is only visible when sampling mode is enabled above.
Enter a number that matches the sampling rate in your exporter
device. If the number is different, monitoring results will be
incorrect. Please enter an integer value.
Log Stream Data to Define if the probe will write a log file of the stream and packet
Disk (for Debugging) data to the data folder (see Dat a St orage 2871 ). Choose between:
None (recommended): Do not write additional log files.
Recommended for normal use cases.
Only for t he 'Ot her' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Ot her channel.
All st ream dat a: Write log files for all data received.
Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
CHANNEL CONFIGU R ATION
Channel Selection Define the categories the sensor accounts the traffic to. There are
different groups of traffic available. Choose between:
Web: Internet web traffic.
File Transfer: Traffic caused by FTP.
Mail: Internet mail traffic.
Chat : Traffic caused by chat and instant messaging.
02.02.2015 823
52 IPFIX Sensor
Remot e Cont rol: Traffic caused by remote control applications,

such as RDP, SSH, Telnet, VNC.
Infrast ruct ure: Traffic caused by network services, such as
DHCP, DNS, Ident, ICMP, SNMP.
Net BIOS: Traffic caused by NetBIOS communication.
Cit rix: Traffic caused by Citrix applications.
Ot her Prot ocols: Traffic caused by various other protocols via
UDP and TCP.
For each traffic group, you can select how many channels will be
used for each group, i.e., how detailed the sensor divides the
traffic. For each group, choose between:
No: Do not account traffic of this group in an own channel. All
traffic of this group is accounted to the default channel named
Ot her.
Yes: Count all traffic of this group and summarize it into one
channel.
Det ail: Count all traffic of this group and further divide it into
different channels. The traffic appears in several channels as
shown in the Cont ent column. Note: Extensive use of this
option can cause load problems on your probe system. We
recommend setting specific, well-chosen filters for the data you
really want to analyze.
Note: You can change the default configuration for groups and
channels. For details, please see section More.
FILTER ING
Include Filter Define if you want to filter any traffic. If you leave this field empty,
all traffic will be included. To include specific traffic only, define
filters using a special syntax. For detailed information, please see
Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 2831
section.
Exclude Filter First, the filters defined in the Include Filt er field are considered.
From this subset, you can explicitly exclude traffic, using the same
syntax. For detailed information, please see Filt er Rules for xFlow,
IPFIX , and Packet Sniffer Sensors 2831 section.
824 02.02.2015
52 IPFIX Sensor
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
Primary Toplist Define which will be your primary toplist. It will be shown in maps
when adding a toplist object. Choose from:
Top Talkers
Top Connect ions
Top Prot ocols
[Any custom toplists you have added]
Inherited Settings
described below.
02.02.2015 825
52 IPFIX Sensor
SCANNING INTER VAL
Choose between:
option will apply.
826 02.02.2015
52 IPFIX Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 827
52 IPFIX Sensor
menu bar.
dependent on.
828 02.02.2015
52 IPFIX Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 829
52 IPFIX Sensor
Toplists
For all flow and packet sniffer sensors there are Toplist s available on the Overview tab of a
sensor's detail page. Using toplists, you can review traffic data of small time periods in great
detail. For more information, please see Toplist s 2498 section.
More
Paessler Website: Paessler NetFlow Testers
http://www.paessler.com/tools/netflowtester
Sniffer sensors?

Notifications
Others
Related Topics
Channel Defint ions for xFlow, IPFIX , and Packet Sniffer Sensors 2835
830 02.02.2015
53 IPFIX (Custom) Sensor
6.8.53 IPFIX (Custom) Sensor
The IPFIX (Custom) sensor receives traffic data from an IPFIX (Internet Protocol Flow Information
Export) compatible device and shows the traffic by type. In this custom sensor, you can define
your own channel definitions to divide traffic into different channels. Ensure your device
supports IPFIX when using this sensor.
This sensor can show traffic by type individually to your needs.
sensor setup.
IPFIX Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ipfix.png
Remarks
Note: In order for this sensor to work, you have to enable IPFIX export on the device. The
device must send the flow data stream to the IP address of the PRTG probe system on which
the sensor is set up (either a local or remote probe).
This sensor type cannot be used in cluster mode. You can set it up on a local probe or
02.02.2015 831

Add Sensor
Sensor Settings
priority).
832 02.02.2015
Receive IPFIX Packets Enter the UDP port number on which the flow packets are
on UDP Port received. It must match the one configured in the IPFIX export
options of your hardware router device. Please enter an integer
value.
IPFIX data from. Enter an IP address to receive data from a specific
Receive IPFIX Packets Select the IP address(es) on which PRTG listens to IPFIX packets.
line. The IP address selected here must match the one configured
in the IPFIX export options of your hardware router device.
value. We recommend setting this one minute longer than the
respective timeout configured in your hardware router device.
below.
Enter a number that matches the sampling rate in your device. If
the number is different, monitoring results will be incorrect. Please
enter an integer value.
Channel Definition Please enter a channel definition to divide the traffic into different
channels. Write each definition in one line. For detailed information,
please see Channel Definit ions for xFlow and Packet Sniffer
Sensors 2835 section. All traffic for which no channel is defined will
be accounted to the default channel named Ot her.
Note: Extensive use of many filters can cause load problems on
your probe system. We recommend defining specific, well-chosen
filters for the data you really want to analyze.
02.02.2015 833

Ot her channel.
only.
SENSOR DISPLAY
for each channel.
834 02.02.2015
FILTER ING
section.
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
02.02.2015 835
SCANNING INTER VAL
Choose between:
option will apply.
836 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 837
menu bar.
dependent on.
838 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 839
Toplists

Notifications
Others
Related Topics
840 02.02.2015
54 IPMI System Health Sensor
6.8.54 IPM I Sy stem Health Sensor
The IPMI System Health sensor monitors the status of a system via the Intelligent Platform
Management Interface (IPMI).
Temperatures of, for example, the system or the peripheral temperature.

Fan rotation per minute
Voltages
Status of a power supply
sensor setup.
IPMI Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ipmi_sy stem_health.png
Remarks
Note: You have to explicitly specify the credentials of the IPMI in the sensor settings.
02.02.2015 841

Add Sensor
Before you can actually add this sensor, PRTG will ask you to provide your credentials for the
Intelligent Platform Management Interface (IPMI) in the add sensor dialog 228 . Enter the
Username and the Password in the respective fields.
Select the metrics you want to monitor. PRTG will create one sensor for each metric you
IPMI SPECIFIC
Group Select the measurements you want to add a sensor for. You see a
list with the names of all items which are available to monitor.
table head.
842 02.02.2015
Sensor Settings
priority).
IPMI CR EDENTIALS
Username Enter the username for the Intelligent Platform Management

Interface (IPMI). If not changed yet, this field shows the username
that you defined during sensor creation.
Password Enter the password for the Intelligent Platform Management

Interface (IPMI). If not changed yet, this field shows the encrypted
password that you defined the sensor creation.
02.02.2015 843
IPMI SPECIFIC
Group Shows the metric that this sensor monitors. Once a sensor is
anew.
Logfile Results Define what PRTG will do with the result of the sensor. Choose
between:
SENSOR DISPLAY
for each channel.
844 02.02.2015
Inherited Settings
described below.
02.02.2015 845
SCANNING INTER VAL
Choose between:
option will apply.
846 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 847
menu bar.
dependent on.
848 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 849
More

Notifications
Others
850 02.02.2015
55 jFlow V5 Sensor
6.8.55 jFlow V5 Sensor
The jFlow V5 sensor receives traffic data from a jFlow V5 compatible device and shows the
traffic by type. On your hardware device, ensure it matches jFlow V5 and disable any sampling
option! There are several filter options available to divide traffic into different channels.
Chat (IRC, AIM)

Citrix
NetBIOS
Total traffic
sensor setup.
02.02.2015 851
55 jFlow V5 Sensor
jFlow V5 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/jflow_v 5.png
Remarks
Note: You have to enable jFlow export of the respective version on the monitored device
for this sensor to work. The device must send the flow data stream to the IP address of the
PRTG probe system on which the sensor is set up (either a local or remote probe).
This sensor does not support sampling, so please disable sampling in your jFlow device!
Add Sensor
852 02.02.2015
55 jFlow V5 Sensor
Sensor Settings
priority).
JFLOW V5 SPECIFIC SETTINGS
Receive jFlow Packets Enter the UDP port number on which PRTG receives the flow
on UDP Port packets. It must match the one you have configured in the jFlow
integer value.
Note: When you configure the export, please make sure you select
the appropriate jFlow version for this sensor.
jFlow from. Enter an IP address to receive data from a specific
02.02.2015 853
55 jFlow V5 Sensor
JFLOW V5 SPECIFIC SETTINGS
Receive jFlow Packets Select the IP address(es) on which PRTG listens to jFlow packets.
on IP The list of IP addresses you see here is specific to your setup. To
line. You can also select and deselect all items by using the check
box in the table head. The IP address you select here must match
the one you configured in the jFlow export options of your
hardware router device.
Active Flow Timeout Enter a time span in minutes after which the sensor must have
(Minutes) received new flow data. If the timeout is reached and no new data
came in, the sensor may switch to an Unknown status. Please
enter an integer value. We recommend setting this one minute
longer than the respective timeout configured in your hardware
router device.
below.
Ot her channel.
only.
854 02.02.2015
55 jFlow V5 Sensor
UDP and TCP.
Ot her.
channel.
FILTER ING
section.
02.02.2015 855
55 jFlow V5 Sensor
FILTER ING
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
856 02.02.2015
55 jFlow V5 Sensor
Inherited Settings
described below.
02.02.2015 857
55 jFlow V5 Sensor
SCANNING INTER VAL
Choose between:
option will apply.
858 02.02.2015
55 jFlow V5 Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 859
55 jFlow V5 Sensor
menu bar.
dependent on.
860 02.02.2015
55 jFlow V5 Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 861
55 jFlow V5 Sensor
Toplists
More
Knowledge Base: Where is the volume line in graphs?

Notifications
Others
Related Topics
862 02.02.2015
56 jFlow V5 (Custom) Sensor
6.8.56 jFlow V5 (Custom) Sensor
The jFlow V5 (Custom) sensor receives traffic data from a jFlow V5 compatible device and
shows the traffic by type. On your hardware device, please make sure it matches jFlow V5 and
disable any sampling option! In this custom sensor, you can define your own channel
definitions to divide traffic into different channels.
sensor setup.
jFlow V5 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/jflow_v 5.png
02.02.2015 863
Remarks
Note: You have to enable jFlow export of the respective version on the monitored device
The sensor does not support sampling, so please disable sampling in your jFlow device!

Add Sensor
Sensor Settings
864 02.02.2015
priority).
JFLOW SPECIFIC SETTINGS
Receive jFlow Packets Enter the UDP port number on which PRTG receives the flow
on UDP Port packets. It must match the one you have configured in the jFlow
integer value.
jFlow from. Enter an IP address to receive data from a specific
Receive jFlow Packets Select the IP address(es) on which PRTG listens to jFlow packets.
on IP The list of IP addresses you see here is specific to your setup. To
line. You can also select and deselect all items by using the check
box in the table head. The IP address you select here must match
the one you configured in the jFlow export options of your
Active Flow Timeout Enter a time span in minutes after which the sensor must have
(Minutes) received new flow data. If the timeout is reached and no new data
came in, the sensor may switch to an Unknown status. Please
enter an integer value. We recommend setting this one minute
longer than the respective timeout configured in your hardware
router device.
below.
02.02.2015 865
JFLOW SPECIFIC SETTINGS
please see Channel Defint ions for xFlow and Packet Sniffer
Sensors 2835 section. All traffic for which no channel is defined will
be accounted to the default channel named Ot her.
filters for the data you really want to analyse.
Ot her channel.
only.
FILTER ING
section.
866 02.02.2015
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
02.02.2015 867
SCANNING INTER VAL
Choose between:
option will apply.
868 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 869
menu bar.
dependent on.
870 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 871
Toplists
More

Notifications
Others
Related Topics
872 02.02.2015
57 LDAP Sensor
6.8.57 LDAP Sensor
The LDAP sensor monitors directory services using Lightweight Directory Access Protocol
(LDAP), connecting to the server trying a "bind". If the server does not respond or
authentication fails, an it will show an error message.
The sensor shows the response time of the server.
LDAP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ldap.png
Add Sensor
Sensor Settings
02.02.2015 873
57 LDAP Sensor
priority).
LDAP SPECIFIC
Port Enter the LDAP port number, usually port 389 for unencrypted
connections. Please enter an integer value.
Distinguished Name Enter the Distinguished Name (DN) you want to authenticate to the
LDAP server. Usually, this is the information for the user you want
to authenticate with. For example, use the format
cn=Manager,dc=my -domain,dc=com for a DN on an OpenLDAP
server.
Password Enter the password for the entered Distinguished Name.
SENSOR DISPLAY
for each channel.
874 02.02.2015
57 LDAP Sensor
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 875
57 LDAP Sensor
SCANNING INTER VAL
Choose between:
option will apply.
876 02.02.2015
57 LDAP Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 877
57 LDAP Sensor
menu bar.
dependent on.
878 02.02.2015
57 LDAP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 879
58 Microsoft SQL Sensor
6.8.58 M icrosoft SQL Sensor
IMPOR TANT NOTICE
This sensor type is outdated. We strongly recommend you to use the Microsoft SQL v2
Sensor 889 instead. This is a new sensor type to monitor databases on Microsoft SQL
servers.
The Microsoft SQL sensor monitors a Microsoft Structured Query Language (SQL) server. It
shows the response time, the number of records, and the value. The sensor can monitor if the
database server accepts connections, processes requests, and returns an expected result
when executing a custom SQL command.
The following SQL servers are supported: SQL Server 2008, SQL Server 2005 (including SQL
Server Express / Server Compact Editions), SQL Server 2000, SQL Server 7 and MSDE (requires
OLE DB installed on the machine running the PRTG probe that accesses the server)
Add Sensor
Sensor Settings
880 02.02.2015
priority).
SQL-SER VER SPECIFIC DATA
Timeout (sec.) Enter a timeout in seconds for the request. If the reply takes
is triggered.
Instance Enter the SQL server instance's name if you want to connect to a
"named instance". For example, such an instance's name could be
SQLEXPRESS. Note: Sometimes you will see connection strings
like SQLSERVER\SQLINSTANCE in database clients. The first part is
the server name configured under the general server settings. The
second part refers to the instance name mentioned above. Never
enter this complete string in this PRTG form, merely provide the
second part (without the backslash). Please enter a string or leave
the field empty.
Port Define the port for the SQL connection. Choose between:
Aut omat ic: Automatically choose the right port.
Manual: Use a specific port. Define below. Standard value is
1433.
Port This field is only visible if manual port selection is enabled above.
Define the port number for the SQL connection. Please enter an
integer value.
DATABASE
Database Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be Northwind
Authentication Define the kind of authentication used for the connection to the
database. Choose between:
SQL Server: Use credentials specific to the SQL server. Please
enter them below.
02.02.2015 881
DATABASE
Windows Aut hent icat ion: Use the Windows credentials defined
for the parent device this sensor is created on. Note: For
successful authentication, the defined Windows credentials must
be known to the SQL server, and SQL server and the computer
the PRTG probe is running on must be in the same domain.
User This field is only visible if SQL server authentication is enabled

above. Enter the user name that will be used for the database
connection.
Password This field is only visible if SQL server authentication is enabled

above. Enter the password that will be used for the database
connection.
DATA
use SELECT *! For example, a correct expression could be: SELECT
ProductName FROM Northwind.dbo.Products. When a cursor is
returned (i.e. with a SELECT statement), only the first row of data
will be processed.
Note: Executing stored procedures is currently not supported.
this sensor.
882 02.02.2015

condition.
below.
provided below.
float value.
below.
provided below.
02.02.2015 883
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
884 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 885

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
886 02.02.2015
menu bar.
dependent on.
02.02.2015 887
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
888 02.02.2015
59 Microsoft SQL v2 Sensor
6.8.59 M icrosoft SQL v2 Sensor
The Microsoft SQL v2 sensor monitors a database on a Microsoft SQL server and executes a
defined query.
Execution time of the whole request (including connection buildup, query execution,
transaction handling, disconnection)
Execution time of the given query
Number of rows which were addressed by the query (including select statements)
It can also process the data table and show defined values in individual channels.
Mic rosoft SQL v 2 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/mic rosoft_sql_v 2.png
Remarks
Define Credent ials for Dat abase Management Sy st ems 297 in settings that are higher in
the Object Hierarchy 83 , for example, in the parent device settings 288 .
Your SQL query must be stored in a file on the system of the probe the sensor is created on:
If used on a remote probe, the file must be stored on the system running the remote probe.
In a cluster setup, please copy the file to every cluster node.
02.02.2015 889
Save the SQL script with the query into the \Cust om Sensors\sql\mssql subfolder of your
PRTG installation. See manual section Dat a St orage 2871 for more information about how to
find this path.
This sensor type supports Microsoft SQL server 2005 or later.
This sensor type supersedes the outdated Microsoft SQL sensor. We recommend you to use
this new sensor to monitor Microsoft SQL databases.

Add Sensor
Sensor Settings
890 02.02.2015
priority).
DATABASE SPECIFIC
Database Enter the name of the SQL database to which the sensor connects.
For example, such a database's name could be MyDatabase. This is
a logical entity on the database server where database objects like
tables or stored procedures exist.
SQL Server Instance Define if you want to use an instance name for the database
connection. Choose between:
No inst ance name required (default ): Use the default instance
for the connection.
Use inst ance name: Use a named instance that you can specify
below.
Instance Name This field is only visible if you enable instance name usage above.
Enter the named instance you want to monitor.
Encryption Define encryption usage for the database connection. Choose

between:
Use server default s (default ): The database connection is only
encrypted if enforced by the database server.
Enforce encry pt ion but do not validat e server cert ificat e:
Choose this option to make sure the database connection is
encrypted.
Enforce encry pt ion and validat e server cert ificat e: Choose
this option to force encryption and to validate the database
server certificate. This approach provides highest security, for
example, it helps preventing "man in the middle" attacks.
Note: The sensor validates the certificate only if the database
server enforces encryption!
02.02.2015 891
DATA
SQL Query File Select an SQL script file that includes a valid SQL statement to
execute on the server. Once a sensor is created, you cannot
The script will be executed with every scanning interval. The list
contains SQL scripts from the database management system
specific \Cust om Sensors\sql subfolder of your PRTG installation.
Store your script there. If used on a remote probe, the file must be
stored on the system running the remote probe. If used on a
cluster probe, you must store the file on all servers running a
cluster node! For more information on how to find this path, please
see Dat a St orage 2871 section. By default, there is the demo script
Demo Serverupt ime.sql available that you can use to monitor the
uptime of the target server.
For example, a correct expression in the file could be: SELECT AVG
(UnitPrice) FROM Products. If you want to use transactions,
separate the individual steps with semicolons ";".
Note: Please be aware that with each request the full result set will
be transferred, so use filters and limits in your query.
Use Transaction Define if you want to use transactions and if they will affect the
database content. Choose between:
Don't use t ransact ion (default ): No transactions will be
executed.
Use t ransact ion and alway s rollback: Choose this option to
ensure that no data in the database will be changed by the
query. In the SQL Query field above, separate the single steps of
the transaction with semicolons.
Use t ransact ion and commit on success: Choose this option
to perform changes on the database with the query. The
changes will only apply if all execution steps succeed without
any errors. In the SQL Query field above, separate the single
steps of the transaction with semicolons.
Data Processing Define if you want to process data from the database. Once a
the sensor anew. Choose between:
Just execut e t he query : If you select this option, the sensor
will only show information about the number of affected rows
and the execution time of the query.
Process dat a t able: Select this option to read and analyze the
queried data table.
892 02.02.2015
DATA
Handle DBNull in This setting is only visible if you selected the process data table
Channel Values as option above. Define the sensor behavior if DBNull is returned by
the query. Choose between:
Error: The sensor will show a Down status if DBNull is reported.
Number 0: The sensor will recognize the result DBNull as a valid
value and interpret it as the number 0.
Select Channel Value This setting is only visible if you selected the process data table
by option above. Define how the desired cell in the database table will
be selected. This is necessary to configure the cells which will be
used in the sensor channels. Choose between:
Column number: The channel value will be determined by using
the value in row 0 of the column whose number you specify
below.
Column name: The channel value will be determined by using the
value in row 0 of the column whose name you specify below.
Row number: The channel value will be determined by using the
value in column 0 of the row whose number you specify below.
Key value pair: The channel value will be determined by
searching in column 0 for the key you specify below and
returning the value in column 1 of the same row where the key
value was found.
Sensor Channel #x This setting is only visible if you selected the process data table
option above. You can define up to 10 different channels for the
data processing of this sensor. You have to define at least one
data channel if you process the data table, so you will see all
available settings for Channel #1 without enabling it manually. For
all other possible channels, choose between:
Disable: This channel will not be added to the sensor.
Enable: This channel will be added to the sensor. Define the
settings as described above.
Name option above. Enter a unique name for the channel. Please enter a
string. Channels will be generated dynamically with this name as
identifier. Once a sensor is created, you cannot change this value.
02.02.2015 893
DATA
Sensor Channel #x This setting is only visible if you selected the column number
Column Number option above. Provide the number of the column which will be
used to determine the channel value. Please enter an integer
value.
Sensor Channel #x This setting is only visible if you selected the column name option
Column Name above. Provide the name of the column which will be used to
determine the channel value. Please enter a string.
Sensor Channel #x This setting is only visible if you selected the row number option
Row Number above. Provide the number of the row which will be used to
determine the channel value. Please enter an integer value.
Sensor Channel #x Key This setting is only visible if you selected the key value pair option
above. Provide the key which will be used to determine the
channel value. Please enter a string.
Mode option above. Define how to display the determined value in the
channel. Once a sensor is created, you cannot change this value. It
please add the sensor anew. Choose between:
Absolut e (recommended): The value will be shown as the
sensor retrieves it from the data table.
Difference: The sensor will calculate and show the difference
between the last and the current value.
Sensor Channel #x This setting is only visible if you have selected the process data
Unit table option above. Define the unit of the channel value. Once a
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
894 02.02.2015
DATA
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
For more information about the available units, please refer to the
PRTG Applicat ion Programming Int erface (API) Definit ion 2830 for
custom sensors.
Sensor Channel #x This setting is only visible if you selected the custom unit option
Custom Unit above. Define a unit for the channel value. Please enter a string.
Use Data Table Value in This setting is only visible if you selected the process data table
Sensor Message option above. Define if the sensor message will show a value from
the data table. Choose between:
Disable: Do not use a custom sensor message.
Enable: Define a custom sensor message with the value of a
defined channel.
Sensor Message This setting is only visible if you selected the column number and
Column Number sensor message options above. Specify the number of the column
whose value will be shown in the sensor message. Please enter an
integer value.
Sensor Message This setting is only visible if you selected the column name and
Column Name sensor message options above. Specify the name of the column
whose value will be shown in the sensor message. Please enter a
string.
Sensor Message Row This setting is only visible if you selected the row number and
Number sensor message options above. Specify the number of the row
integer value.
Sensor Message Key This setting is only visible if you selected the key value pair and
sensor message options above. Specify the key for the value
which will be shown in the sensor message. Please enter a string.
Sensor Message This setting is only visible if you selected the sensor message
option above. Define the sensor message. Please enter a string.
Use the placeholder {0} at the position where the value will be
added.
02.02.2015 895
DATA
between:
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
896 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 897

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
898 02.02.2015
menu bar.
dependent on.
02.02.2015 899
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
900 02.02.2015
Others
02.02.2015 901
60 MongoDB System Health Sensor
6.8.60 M ongoDB Sy stem Health Sensor
The MongoDB System Health sensor monitors the system health of a MongoDB server via
Hypertext Transfer Protocol (HTTP) and the MongoDB admin web console.
Percentage of used connections

Percentage of index misses
Average duration of background flushing
Command operations per second
Delete operations per second
Insert operations per second
Update operations per second
Query operations per second
Get more operations per second
MongoDB Sy stem Health Sensor
902 02.02.2015
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/mongodb_sy stem_health.png
Add Sensor
Sensor Settings
priority).
DATABASE
Port Enter the number of the port to which your MongoDB listens. The
default port is 27017.
Note: The sensor does not use this port. PRTG adds 1,000 to this
port number and uses the result to access the HTTP interface of
your MongoDB server.
02.02.2015 903
DATABASE
Authentication Define if the sensor needs to authenticate at the MongoDB admin

web console. Choose between:
No aut hent icat ion required: Choose this option to connect to
the MongoDB web interface without credentials.
Aut hent icat ion required: Choose this option to authenticate
with MongoDB credentials.
User This field is only visible if you select authentication above. Enter
the username for the MongoDB admin web console. Please enter a
string.
Password This field is only visible if you select authentication above. Enter
the password for MongoDB admin web console. Please enter a
string.
SENSOR DISPLAY
for each channel.
904 02.02.2015
Inherited Settings
described below.
02.02.2015 905
SCANNING INTER VAL
Choose between:
option will apply.
906 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 907
menu bar.
dependent on.
908 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 909
61 MySQL Sensor
6.8.61 M y SQL Sensor
IMPOR TANT NOTICE
This sensor type is outdated. We strongly recommend you to use the My SQL v2 Sensor 919
instead. This is a new sensor type to monitor databases on MySQL servers.
The MySQL sensor monitors a MySQL server. It connects to the server and shows the
response time. Additionally, it can read the number of records and a value.
The following SQL servers are supported: MySQL server 5.1, 5.0, 4.1, 4.0, and 3.23
Add Sensor
Sensor Settings
priority).
910 02.02.2015
61 MySQL Sensor
MYSQL SER VER SPECIFIC DATA
Port Define the port for the SQL connection. Choose between:
Aut omat ic: Automatically choose the right port.
Manual: Use a specific port. Define below. Standard value is
3306.
Timeout (sec.) Enter a timeout in seconds for the request. If the reply takes
is triggered.
DB/SQL DATA
Database Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be MyDatabase. This is
a logical entity on the database server where database objects like
tables or stored procedures exist. In case of the mySQL server it
also reflects a physical directory structure where your database
objects are stored. Enter the appropriate string which is the same
as you would supply when invoking the mysql.exe admin tool (with
the command line switch -p) or after the login with mysql.exe with
the command use.
User Enter the user name that will be used for the database connection.
Password Enter the password that will be used for the database connection.
DATA
AVG(UnitPrice) FROM Products. When a cursor is returned (i.e. with
a SELECT statement), only the first row of data will be processed.
02.02.2015 911
61 MySQL Sensor

this sensor.
condition.
below.
provided below.
float value.
912 02.02.2015
61 MySQL Sensor

below.
provided below.
SENSOR DISPLAY
for each channel.
02.02.2015 913
61 MySQL Sensor
SENSOR DISPLAY
Note: For this sensor type, no port number can be set.
Inherited Settings
described below.
914 02.02.2015
61 MySQL Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 915
61 MySQL Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
916 02.02.2015
61 MySQL Sensor
menu bar.
dependent on.
02.02.2015 917
61 MySQL Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
918 02.02.2015
62 MySQL v2 Sensor
6.8.62 M y SQL v2 Sensor
The MySQL v2 sensor monitors a database on a MySQL server and executes a defined query.
Execution time of a given query
Nmber of rows which were addressed by the query (including select statements)
Remarks
Save the SQL script with the query into the \Cust om Sensors\sql\my sql subfolder of your
find this path.
This sensor type supports MySQL server version 5.0 or later and might also work with
previous versions.
This sensor type supersedes the outdated MySQL sensor. We recommend you to use this
new sensor to monitor MySQL databases.

02.02.2015 919
62 MySQL v2 Sensor
Add Sensor
Sensor Settings
priority).
DATABASE SPECIFIC
Database Enter the name of the MySQL database to which the sensor
connects. For example, such a database's name could be
MyDatabase. This is a logical entity on the database server where
database objects like tables or stored procedures exist.
The database name of a MySQL server also reflects a physical
directory structure where your database objects are stored. Enter
the appropriate string which is the same as you would supply
when invoking the mysql.exe admin tool (with the command line
switch -p) or after the login with mysql.exe with the command use.
920 02.02.2015
62 MySQL v2 Sensor
DATA
executed.
queried data table.
02.02.2015 921
62 MySQL v2 Sensor
DATA
below.
value was found.
922 02.02.2015
62 MySQL v2 Sensor
DATA
value.
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
02.02.2015 923
62 MySQL v2 Sensor
DATA
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
custom sensors.
defined channel.
integer value.
string.
integer value.
added.
924 02.02.2015
62 MySQL v2 Sensor
DATA
between:
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 925
62 MySQL v2 Sensor
SCANNING INTER VAL
Choose between:
option will apply.
926 02.02.2015
62 MySQL v2 Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 927
62 MySQL v2 Sensor
menu bar.
dependent on.
928 02.02.2015
62 MySQL v2 Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 929
62 MySQL v2 Sensor
Others
930 02.02.2015
63 NetFlow V5 Sensor
6.8.63 NetFlow V5 Sensor
The NetFlow V5 sensor receives traffic data from a NetFlow V5 compatible device and shows
the traffic by type. Ensure the sensor matches the NetFlow version your device is exporting!
There are several filter options available to divide traffic into different channels.
Chat (IRC, AIM)

Citrix
NetBIOS
Total traffic
sensor setup.
02.02.2015 931
NetFlow V5 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/netflow_v 5.png
Remarks
Note: You must enable NetFlow export of the respective version on the monitored device
932 02.02.2015
Sniffer sensors?
Add Sensor
Sensor Settings
priority).
NETFLOW SPECIFIC SETTINGS
Receive NetFlow Enter the UDP port number on which the flow packets are
Packets on UDP Port received. It must match the one you have configured in the
NetFlow export options of your hardware router device. Please
02.02.2015 933
Note: When configuring export, make sure you select the

appropriate NetFlow version for this sensor.
NetFlow from. Enter an IP address to receive data from a specific
Receive NetFlow Select the IP address(es) on which PRTG listens to NetFlow

Packets on IP packets. The list of IP addresses you see here is specific to your
setup. To select an IP address, add a check mark in front of the
respective line. You can also select and deselect all items by using
the check box in the table head. The IP address selected here must
match the one you have configured in the NetFlow export options
of your hardware router device.
(Minutes) received. If the timeout is reached and no new data was received
during this time, the sensor switches to an Unknown status. Please
enter an integer value. We recommend setting the timeout one
minute longer than the respective timeout configured in your
below.
Ot her channel.
934 02.02.2015
only.
UDP and TCP.
Ot her.
channel.
02.02.2015 935
FILTER ING
section.
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
Top Talkers
936 02.02.2015
PR IMAR Y TOPLIST
Top Connect ions

Top Prot ocols
Inherited Settings
described below.
02.02.2015 937
SCANNING INTER VAL
Choose between:
option will apply.
938 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 939
menu bar.
dependent on.
940 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 941
Toplists
More
Sniffer sensors?


Notifications
Others
Related Topics
942 02.02.2015
64 NetFlow V5 (Custom) Sensor
6.8.64 NetFlow V5 (Custom) Sensor
The NetFlow V5 (Custom) sensor receives traffic data from a NetFlow V5 compatible device and
shows the traffic by type. Please make sure the sensor matches the NetFlow version your
device is exporting! In this custom sensor, you can define your own channel definitions to
divide traffic into different channels.
sensor setup.
02.02.2015 943
NetFlow V5 Sensor
Remarks
944 02.02.2015

Add Sensor
Sensor Settings
priority).
02.02.2015 945

the check box in the table head. The IP address you select here
must match the one you have configured in the NetFlow export
options of your hardware router device.
Note: When configuring export, please make sure you select the
value. We recommend setting the timeout one minute longer than
the respective timeout configured in your hardware router device.
below.
946 02.02.2015
please see Channel Definit ions for xFlow, IPFIX , and Packet
Sniffer Sensors 2835 section. All traffic for which no channel is
defined will be accounted to the default channel named Ot her.
Ot her channel.
only.
FILTER ING
section.
02.02.2015 947
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
948 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 949

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
950 02.02.2015
menu bar.
dependent on.
02.02.2015 951
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
952 02.02.2015
Toplists
More

Notifications
Others
Related Topics
02.02.2015 953
6.8.65 NetFlow V9 Sensor
The NetFlow V9 sensor receives traffic data from a NetFlow V9 compatible device and shows
the traffic by type. Please make sure the sensor matches the NetFlow version your device is
exporting! There are several filter options available to divide traffic into different channels.
Chat (IRC, AIM)

Citrix
NetBIOS
Total traffic
sensor setup.
954 02.02.2015
NetFlow V9 Sensor
Remarks
Sniffer sensors?
02.02.2015 955
Add Sensor
Sensor Settings
priority).
956 02.02.2015

the check box in the table head. The IP address selected here must
match the one you have configured in the NetFlow export options
of your hardware router device.
(Minutes) received. If the timeout is reached and no new data was received
during this time, the sensor switches to an Unknown status. Please
enter an integer value. We recommend setting the timeout one
minute longer than the respective timeout configured in your
below.
Ot her channel.
02.02.2015 957
only.
UDP and TCP.
Ot her.
channel.
958 02.02.2015
FILTER ING
section.
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
Top Talkers
02.02.2015 959
PR IMAR Y TOPLIST
Top Connect ions

Top Prot ocols
Inherited Settings
described below.
960 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 961

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
962 02.02.2015
menu bar.
dependent on.
02.02.2015 963
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
964 02.02.2015
Toplists
More
Sniffer sensors?


Notifications
Others
Related Topics
02.02.2015 965
6.8.66 NetFlow V9 (Custom) Sensor
The NetFlow V9 (Custom) sensor receives traffic data from a NetFlow V9 compatible device and
shows the traffic by type. Please make sure the sensor matches the NetFlow version your
device is exporting! In this custom sensor, you can define your own channel definitions to
divide traffic into different channels.
sensor setup.
NetFlow V9 Sensor
966 02.02.2015
Remarks

Add Sensor
Sensor Settings
02.02.2015 967
priority).

the check box in the table head. The IP address you select here
must match the one you have configured in the NetFlow export
options of your hardware router device.
Note: When configuring export, please make sure you select the
value. We recommend setting the timeout one minute longer than
the respective timeout configured in your hardware router device.
below.
968 02.02.2015
please see Channel Definit ions for xFlow, IPFIX , and Packet
Sniffer Sensors 2835 section. All traffic for which no channel is
defined will be accounted to the default channel named Ot her.
Ot her channel.
only.
FILTER ING
section.
02.02.2015 969
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
970 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 971

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
972 02.02.2015
menu bar.
dependent on.
02.02.2015 973
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
974 02.02.2015
Toplists
More

Notifications
Others
Related Topics
02.02.2015 975
67 Oracle SQL Sensor
6.8.67 Oracle SQL Sensor
IMPOR TANT NOTICE
This sensor type is outdated. We strongly recommend you to use the Oracle SQL v2
Sensor 986 instead. This is a new sensor type to monitor databases on Oracle servers.
The Oracle SQL sensor monitors an Oracle SQL server. It connects to the server and shows
the response time (measured from the time when the connection is opened to the time when
the return values of the SQL queryif configuredhave been received). Additionally, it can
read the number of records and a value.
The following SQL servers are supported: Supports Oracle servers 11g, 10g, 9i, 8i, 8.0, and 7.3,
including Oracle 10g Express, and Oracle 8i Personal and Lite editions (requires default TCP port
setting 1521).
Note: On the client computer running the PRTG probe where this sensor is created on, Oracle
Net is used for direct TCP/IP communication; OCI is not supported any more. You do not need
to install an Oracle client or define a TNSNAMES.ORA on the client computer.
Note: With Oracle version 11.2.0.4, Oracle's TCP/IP authentication method has changed. You
will encounter connection problems with credential errors when using the direct connection
mode as of this Oracle version. In this case, please install the 32-bit Oracle client on the
machine which is running the PRTG probe and choose Use Oracle client as connection mode
in the sensor settings.
Add Sensor
Sensor Settings
976 02.02.2015
priority).
OR ACLE SPECIFIC DATA
is triggered.
Port Enter the port number that will be used for the connection. Default
value is 1521. Please enter an integer value.
Connection Mode Select which mode you want to use to connect to the Oracle
server. Choose between:
Use direct mode (TCP/IP): Use Oracle Net for direct TCP/IP
communication.
Note: As of Oracle version 11.2.0.4, please use the Oracle client
(see sensor description above).
Use Oracle client : Use the Oracle client for communication. It
needs to be installed the machine which is running the PRTG
probe.
DB/SQL DATA
Service Name / Alias Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be orcl
User Enter the user name that will be used for the database connection.
02.02.2015 977
DB/SQL DATA
Password Enter the password that will be used for the database connection.
DATA
sum(salary) FROM hr.employees. When a cursor is returned (i.e.
with a SELECT statement), only the first row of data will be
processed.
this sensor.
978 02.02.2015

condition.
below.
provided below.
float value.
below.
provided below.
02.02.2015 979
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
980 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 981

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
982 02.02.2015
menu bar.
dependent on.
02.02.2015 983
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How do PRTG sensors connect to Oracle databases?

Notifications
984 02.02.2015
Others
02.02.2015 985
68 Oracle SQL v2 Sensor
6.8.68 Oracle SQL v2 Sensor
The Oracle SQL v2 sensor monitors a database on an Oracle server and executes a defined
query.
Orac le SQL v 2 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/orac le_sql_v 2.png
Remarks
986 02.02.2015
Save the SQL script with the query into the \Cust om Sensors\sql\oracle subfolder of your
find this path.
This sensor type supports Oracle database servers version 10.2 or higher.
This sensor type supersedes the outdated Oracle SQL sensor. We recommend you to use
this new sensor to monitor Oracle SQL databases.

Add Sensor
Sensor Settings
02.02.2015 987
priority).
DATABASE SPECIFIC
System ID Enter the Oracle System ID (SID) of the database the sensor will
connect to. For example, such a system ID can look like this: orcl
DATA
988 02.02.2015
DATA

executed.
queried data table.
below.
02.02.2015 989
DATA

value was found.
value.
990 02.02.2015
DATA
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
custom sensors.
02.02.2015 991
DATA
defined channel.
integer value.
string.
integer value.
added.
between:
992 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 993
SCANNING INTER VAL
Choose between:
option will apply.
994 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 995
menu bar.
dependent on.
996 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 997
Others
998 02.02.2015
69 Packet Sniffer Sensor
6.8.69 Packet Sniffer Sensor
The Packet Sniffer sensor monitors the headers of data packets that pass a local network card
using built-in packet sniffer. You can choose from predefined channels. The sensor analyzes
only header traffic.
Chat (IRC, AIM)

Citrix
NetBIOS
Total traffic
sensor setup.
02.02.2015 999
Pac ket Sniffer Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/pac ket_sniffer.png
Remarks
By default, this sensor works only on a probe device.
Sniffer sensors?
For a general introduction to the technology behind packet sniffing, please see manual
section Monit oring Bandwidt h via Packet Sniffing 2758 .
1000 02.02.2015
Note: By default, you can only monitor traffic passing the PRTG probe system on which's Probe
Device the sensor is set up (either a local or remote probe). To monitor other traffic in your
network, you can configure a monitoring port (if available) to which the switch sends a copy of
all traffic. You can then physically connect this port to a network card of the computer the
PRTG probe (either local or remote probe) is running on. This way, PRTG can analyze the
complete traffic that passes through the switch. This feature of your hardware may be called
Switched Port Analyzer (SPAN), port mirroring, or port monitoring.
Add Sensor
Sensor Settings
priority).
02.02.2015 1001
SNIFFER SPECIFIC
the sensor includes all traffic. To include specific traffic only, define
section.
Exclude Filter First, the filters you define in the Include Filt er field are
considered. From this subset, you can explicitly exclude traffic,
using the same syntax. For detailed information, please see Filt er
Rules for xFlow, IPFIX , and Packet Sniffer Sensors 2831 section.
Network Adapters Define the network adapters that this sensor monitors. You see a
list of names with all adapters available on the probe system. To
select an adapter, set a check mark symbol in front of the
respective name. You can also select and deselect all items by
using the check box in the table head.
None (recommended): Do not write additional log files. We
recommend this for normal use cases.
Ot her channel.
only.
1002 02.02.2015

UDP and TCP.
Ot her.
channel.
SENSOR DISPLAY
for each channel.
02.02.2015 1003
SENSOR DISPLAY
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1004 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1005

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1006 02.02.2015
menu bar.
dependent on.
02.02.2015 1007
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1008 02.02.2015
Toplists
More
Sniffer sensors?


Notifications
Others
Related Topics
02.02.2015 1009
70 Packet Sniffer (Custom) Sensor
6.8.70 Packet Sniffer (Custom) Sensor
The Packet Sniffer (Custom) sensor monitors the headers of data packets that pass a local
network card using built-in packet sniffer. You can define your own channels. There are no
predefined channels for this sensor type. This sensor analyzes only header traffic.
sensor setup.
Pac ket Sniffer Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/pac ket_sniffer.png
1010 02.02.2015
Remarks
By default, this sensor works only on a probe device.
Note: By default, you can only monitor traffic passing the PRTG probe system on which's Probe
Device the sensor is set up (either a local or remote probe). To monitor other traffic in your
network, you can configure a monitoring port (if available) to which the switch sends a copy of
all traffic. You can then physically connect this port to a network card of the computer the
PRTG probe (either local or remote probe) is running on. This way, PRTG will be able to analyze
the complete traffic that passes through the switch. This feature of your hardware may be
called Switched Port Analyzer (SPAN), port mirroring, or port monitoring.

Add Sensor
Sensor Settings
02.02.2015 1011
priority).
SNIFFER SPECIFIC
the sensor includes all traffic. To include specific traffic only, define
Filt er Rules for xFlow and Packet Sniffer Sensors 2831 section.
Exclude Filter First, the filters you define in the Include Filt er field are
considered. From this subset, you can explicitly exclude traffic,
using the same syntax. For detailed information, please see Filt er
Rules for xFlow and Packet Sniffer Sensors 2831 section.
Sensors 2835 section. All traffic for which no channel is defined is
accounted to the default channel named Ot her.
filters for the data you really want to analyze. We recommend you
to not use more than 20 channels in graphs and tables, and not
more than 100 channels in total. For performance reasons, it is
better to add several sensors with less channels each.
Network Adapters Define the network adapters that this sensor monitors. You see a
list of names with all adapters available on the probe system. To
select an adapter, set a check mark symbol in front of the
respective name. You can also select and deselect all items by
using the check box in the table head.
1012 02.02.2015
SNIFFER SPECIFIC

Ot her channel.
only.
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
02.02.2015 1013
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1014 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1016 02.02.2015
menu bar.
dependent on.
02.02.2015 1017
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1018 02.02.2015
Toplists
More

Notifications
Others
Related Topics
02.02.2015 1019
71 Passive Application Performance Sensor
6.8.71 Passive Application Performance Sensor
The Passive Application Performance sensor monitors Transport Control Protocol (TCP)
connection timings using packet sniffer. It can measure the performance of many different web
applications without actually having direct access to neither the client nor the server. To
obtain valuable data, these applications must work TCP-based and initiate a new session with
each request.
Total number of packets per second on the selected network card

Number of dropped packets per second by PRTG because of system overload (more
processor power is required if this value is above zero to cope with the traffic)
Number of currently active connections on all monitored applications.
For defined applications, the sensor can show (together with the corresponding application
name):
Request time in msec: average time between the initial (SYN) packet from the client and the
first request package from the client
Response time in msec: average time between the initial (SYN) packet from the client and
first packet of the result from the server
ACK (acknowledge) time in msec: average time between the initial (SYN) packet of a
connection from the client until the server sends an ACK (acknowledge) packet. This means
that a TCP connection was successfully established (in LANs this value is zero in most cases
and only increases for extreme loads).
Count: total number of observed connections to the service in the last monitoring interval.
This is the number of measurements the average is based on. The higher the value the more
reliable/averaged the data is. If this value is zero, PRTG did not see any packets for this
service.
1020 02.02.2015
Passiv e Applic ation Performanc e Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/passiv e_applic ation_performanc e.png
Remarks
Add Sensor
Sensor Settings
02.02.2015 1021
priority).
APPLICATIONS
Network Adapter Select the network adapter you want to monitor.
Applications Define the applications you want to monitor. For each application,
use one dedicated line. Use the following syntax to define an
application to be monitored: ip:port=application.
Provide the IP address and port number of the application. Behind
the equals sign, enter a name for the application which will be
displayed in the channels. Please enter a string.
This sensor will create four sensor channels with the application
name, for example, "Application (ACK)".
1022 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1023
SCANNING INTER VAL
Choose between:
option will apply.
1024 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1025
menu bar.
dependent on.
1026 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 1027
72 PerfCounter Custom Sensor
6.8.72 PerfCounter Custom Sensor
The PerfCounter Custom sensor monitors a configured set of Windows Performance Counters.
You can define your own channels. There are no predefined channels available for this sensor
type. To find out which performance counters are available on the target system and what
their names are, please see section More 1036 .
This sensor can show Windows performance counters individually to your needs.
sensor setup.
PerfCounter Custom Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/perfc ounter_c ustom.png
Remarks
Requires 1028 Windows credentials in the parent device settings.
Requires 1029 the Windows Remote Registry service to be running on the target computer.
Requires 1029 Windows Server 2008 R2 or later on the probe system.
Knowledge Base: How can I find out the names of available Performance Counters?
Knowledge Base: My Performance Counter sensor does not work. What can I do?
1028 02.02.2015
possible.
Note: The user account has to be a member of the Performance Monitor Users user group on
the target system.

RemoteRegistry "Remote Registry" Windows service is running on the target computer. If you
fail to do so, a connection via Performance Counters will not be possible.
Automatic.
Windows version 2008 R2 or later is installed on the computer running the PRTG probe: This is
remote probe 2848 .
Add Sensor
PER FOR MANCE COU NTER SETTINGS
List of Counters Enter a list of performance counters which will be queried. Define
one counter per row. PRTG will create one channel for each
counter. Use the following syntax: the name of the counter,
followed by two colons (::) and the unit.
Example: \Processor(_Total)\% Processor Time::%
02.02.2015 1029
Mode Define the mode for the return value of the performance counter.
This setting determines if the returning value will be displayed as
absolute value or if the difference between the last and the current
value will be used. Choose between:
Absolut e (recommended): The returning value will be displayed
as absolute value.
Difference: The difference between last and current value will be
displayed. Note: Please make sure that all counters which are
monitored are capable of this mode if you select it.
Sensor Settings
priority).
1030 02.02.2015
List of Counters Shows the performance counters that this sensor monitors. Once
the sensor anew.
Mode Shows the mode in which the sensor displays the returning values.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1031
SCANNING INTER VAL
Choose between:
option will apply.
1032 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1033
menu bar.
dependent on.
1034 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1035
More
Knowledge Base: How can I find out the names of available Performance Counters?
Knowledge Base: Remote Monitoring of Specific Performance Counters


Notifications
Others
1036 02.02.2015
73 PerfCounter IIS Application Pool Sensor
6.8.73 PerfCounter IIS Application Pool Sensor
The PerfCounter IIS Application Pool sensor monitors a Microsoft Internet Information Services
(IIS) application pool using Windows Performance Counters.
Overall status of an application pool

Number of worker processes
Number of failures in worker processes per second
Number of ping failures per second
Number of shutdown failures per second
Number of startup failures per second
sensor setup.
PerfCounter IIS Applic ation Pool Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/PerfCounter_IIS_Applic ation_Pool.png
Remarks
Requires 1038 Microsoft IIS version 7.5 or later on the target system.
02.02.2015 1037

Requires 1038 Windows Server 2008 R2 or later on the probe system.
Requirement: Microsoft IIS Version 7.5

In order to monitor Microsoft Internet Information Services (IIS) application pools, this sensor
needs IIS version 7.5 or later to be installed on the target system.
possible.
Note: The user account has to be a member of the Performance Monitor Users user group on
the target system.

RemoteRegistry "Remote Registry" Windows service is running on the target computer. If you
fail to do so, a connection via Performance Counters will not be possible.
Automatic.
Windows version 2008 R2 or later is installed on the computer running the PRTG probe: This is
remote probe 2848 .
1038 02.02.2015
Add Sensor
Select the Microsoft Internet Information Services (IIS) application pools that you want to
monitor. PRTG creates one sensor for each pool you select in the Add Sensor dialog. The
settings you make in this dialog are valid for all of the sensors that are created.
IIS APPLICATION POOL SPECIFIC
Application Pool Select the application pools you want to add a sensor for. You see
a list with the names of all items which are available to monitor.
table head.
Sensor Settings
02.02.2015 1039
priority).
IIS APPLICATION POOL SPECIFIC
Application Pool Shows the name of the application pool that this sensor monitors.
SENSOR DISPLAY
for each channel.
1040 02.02.2015
Inherited Settings
described below.
02.02.2015 1041
SCANNING INTER VAL
Choose between:
option will apply.
1042 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1043
menu bar.
dependent on.
1044 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1045

Notifications
Others
1046 02.02.2015
74 Ping Sensor
6.8.74 Ping Sensor
The Ping sensor sends an Internet Control Message Protocol (ICMP) echo request ("Ping") from
the computer running the probe to the device it is created on to monitor the availability of a
device. Default is 5 pings per scanning interval.
Ping time
Minimum ping time when using more than one ping per interval
Maximum ping time when using more than one ping per interval
Packet loss in percent when using more than one ping per interval
Ping Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ping.png
Remarks
Knowledge Base: How to create/customize statistical PING sensor?
Knowledge Base: Can I create an inverse Ping sensor?
02.02.2015 1047
74 Ping Sensor
Add Sensor
Sensor Settings
priority).
PING SETTINGS
Timeout (Sec.) Enter a timeout in seconds for the Ping. If the reply takes longer
than this value defines, the sensor will cancel the request and
shows an error message. The maximum timeout value is 300
seconds (5 minutes).
Packet Size (Bytes) Enter the packet size in bytes for the Ping. You can choose any
value between 1 and 10000. We recommend using the default
value.
1048 02.02.2015
74 Ping Sensor
PING SETTINGS
Ping Method Define the kind of Ping check that the sensor performs. Choose
between:
Send one single Ping: With each scanning interval, send a single
Ping only. A sensor in this setting will show the Ping time only.
This setting is good for simple availability monitoring.
Send mult iple Ping request : With each scanning interval, send
multiple Pings in a row. A sensor in this setting will also show
minimum and maximum Ping time as well as packet loss (in
percent). This setting is good if you want to create reports about
average Ping times out of a series of ping requests. This is the
default setting.
Note: When using multiple request, all of them have to get lost to
show a Down status 123 . For example, if there is only one Ping
request answered in a series of five, the sensor will still show a
green Up status.
Ping Count This field is only visible if you enable sending multiple Pings above.
Enter the number of Pings that the sensor sends in a row for one
interval. Please enter an integer value. The default value is 5.
Ping Delay (in ms) This field is only visible if you enable sending multiple Pings above.
Enter the time in milliseconds the sensor waits between two Ping
requests. Please enter an integer value. The default value is 5.
Note: Increase the value if the target device drops Ping packets
due to denial-of-service (DOS) suspicion.
Auto Acknowledge You can define that a Down status of this sensor will be
acknowledged 146 automatically.
Show "Down" st at us on error (default ): Do not automatically
acknowledge an alarm if this sensor changes to a Down status.
Show "Down (Acknowledged)" st at us on error: Automatically
acknowledge an alarm. If this sensor changes to a Down status,
it will automatically change to Down (Acknowledged).
Note: The sensor will also go through a Down status, so any
sensor status triggers 2484 using this will still provoke
notifications, as configured.
02.02.2015 1049
74 Ping Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1050 02.02.2015
74 Ping Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1051
74 Ping Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1052 02.02.2015
74 Ping Sensor
menu bar.
dependent on.
02.02.2015 1053
74 Ping Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How to create/customize statistical PING sensor?
Knowledge Base: Can I create an inverse Ping sensor?


1054 02.02.2015
74 Ping Sensor
Notifications
Others
02.02.2015 1055
75 Ping Jitter Sensor
6.8.75 Ping Jitter Sensor
The Ping Jitter sensor sends a series of Internet Control Message Protocol (ICMP) echo
requests ("Pings") to the given URI to determine the statistical jitter.
This sensor shows the following:
Statistical jitter value

Execution time
The Real Time Jitter value is updated every time a packet is received using the formula
described in RFC 1889:
Jitter = Jitter + ( abs( ElapsedTime OldElapsedTime ) Jitter ) / 16
The Statistical Jitter value is calculated on the first x packets received using the statistical
variance formula:
Jitter Statistical = SquareRootOf( SumOf( ( ElapsedTime[i] Average) ^ 2 ) /

( ReceivedPacketCount 1 ) )
Ping Jitter Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ping_jitter.png
Remarks
1056 02.02.2015

Add Sensor
Sensor Settings
priority).
02.02.2015 1057
SENSOR SETTINGS
Ping Count Define the number of Internet Control Message Protocol (ICMP)
pings that this sensor sends. Please enter an integer value.
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
1058 02.02.2015
Inherited Settings
described below.
02.02.2015 1059
SCANNING INTER VAL
Choose between:
option will apply.
1060 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1061
menu bar.
dependent on.
1062 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 1063
76 Pingdom Sensor
6.8.76 Pingdom Sensor
The Pingdom sensor queries an account at Pingdom.com and retrieves values for one "check"
configured in the respective Pingdom account. With every scanning interval, the sensor always
catches the last value available in the "detailed check log" of your Pingdom account.
The sensor shows the following:
Response time
Execution time
Pingdom Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/pingdom.png
Remarks
1064 02.02.2015
76 Pingdom Sensor

Add Sensor
Sensor Settings
priority).
02.02.2015 1065
76 Pingdom Sensor
SENSOR SETTINGS
Pingdom Check Name Enter the name of the "check" you want to retrieve data for. Enter
it exactly the way configured in your Pingdom account. This setting
is case sensitive! Please enter a string.
Username Enter the username of the Pingdom account you want to query.
Password Enter the password of the Pingdom account you want to query.
change.
DEBU G OPTIONS
between:
SENSOR DISPLAY
1066 02.02.2015
76 Pingdom Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1067
76 Pingdom Sensor
SCANNING INTER VAL
Choose between:
option will apply.
1068 02.02.2015
76 Pingdom Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1069
76 Pingdom Sensor
menu bar.
dependent on.
1070 02.02.2015
76 Pingdom Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 1071
77 POP3 Sensor
6.8.77 POP3 Sensor
The POP3 sensor monitors an email server using Post Office Protocol version 3 (POP3).
POP3 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/pop3.png
Add Sensor
Sensor Settings
1072 02.02.2015
77 POP3 Sensor
priority).
POP3 SPECIFIC
Timeout (Sec.) Enter a timeout in seconds for the request. If the reply takes longer
show a corresponding error message. Please enter an integer
Port Specify the port that the sensor uses for the POP3 connection. This
is usually port 110 for non-secure connections and usually port
995 for SSL connections. The actual setting depends on the server
you are connecting to. Please enter an integer value. We
between:
02.02.2015 1073
77 POP3 Sensor

status 123 .
SSL/TLS protocol.
1074 02.02.2015
77 POP3 Sensor
POP3 AU THENTICATION
Type Select the kind of authentication for the POP3 connection. Choose
between:
Wit hout login: Monitor the connection to the POP3 server only.
Username and password: Log on to the POP3 server with user
name and password (simple login, non-secure).
128-bit MD5 hash value (APOP): Send the password in an

encrypted form using APOP. This option must be supported by
the POP3 server you connect to.
Username This field is only visible if you select an option with login above.
Enter a username for POP3 authentication. Please enter a string.
Password This field is only visible if you select an option with login above.
Enter a password for POP3 authentication. Please enter a string.
between:
SENSOR DISPLAY
for each channel.
02.02.2015 1075
77 POP3 Sensor
SENSOR DISPLAY

Inherited Settings
described below.
1076 02.02.2015
77 POP3 Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1077
77 POP3 Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1078 02.02.2015
77 POP3 Sensor
menu bar.
dependent on.
02.02.2015 1079
77 POP3 Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
1080 02.02.2015
78 POP3 Email Count Sensor
6.8.78 POP3 Email Count Sensor
The POP3 Email Count sensor connects to a POP3 email account and returns the number of
emails stored in it. Additionally, you can filter by to or from address, or by subject, to only
count mails matching the search pattern.
Number of emails in the mailbox

Execution time
POP3 Email Count Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/pop3_email_c ount.png
Remarks
02.02.2015 1081

Add Sensor
Sensor Settings
priority).
1082 02.02.2015
SENSOR SETTINGS
Username Enter the username of the POP3 account you want to log into.
Note: As POP3 server, this sensor uses the IP Address/DNS Name
value that you specify in the parent device settings 288 .
Password Enter the password for the POP3 account.

Mailserver POP3 Port Define the port number the POP3 server is running at. Please enter
an integer value.
Use SSL Define whether to use SSL for the connection to the POP3 server.
Choose between:
No
Yes
Note: As POP3 server, this sensor uses the parent device.
Filter To Address Optionally define a To address. The sensor counts only emails
containing this address. Please enter a string or leave the field
empty.
Filter From Address Optionally define a From address. The sensor counts only emails
containing this address. Please enter a string or leave the field
empty.
Filter Subject Content Optionally define an email Subject. The sensor counts only emails
containing this subject. Please enter a string or leave the field
empty.
change.
02.02.2015 1083
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1084 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1085

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1086 02.02.2015
menu bar.
dependent on.
02.02.2015 1087
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1088 02.02.2015
More

Notifications
Others
02.02.2015 1089
79 Port Sensor
6.8.79 Port Sensor
The Port sensor monitors a network service by connecting to its port. It tries to connect to
the specified TCP/IP port number of a device and waits for the request to be accepted.
Depending on your settings, it can alert you either when the monitored port is open, or when
it is closed.
The sensor shows the time until a request to a port is accepted.
Port Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/port.png
Add Sensor
Sensor Settings
1090 02.02.2015
79 Port Sensor
priority).
POR T SPECIFIC
Port Enter the number of the port to which this sensor connects.
Security Define the security level for the sensor connection. Choose
between:
Use Transport -Level Securit y (default ): Establish the
connection with the strongest TLS method that the target device
provides.
Do not use Transport -Level Securit y : Establish the connection
without encryption.
02.02.2015 1091
79 Port Sensor
ADVANCED SENSOR SETTINGS
Goal Define how the sensor will report on the port defined above.
Choose between:
Open: The sensor shows a green Up status 123 if the port is
open, and a red Down status if the port is closed.
Closed: The sensor shows a green Up status if the port is
closed, and a red Down status if the port is open.
Command Define whether the sensor will send a command after opening the
port. Choose between:
Don't send command: Only check if a connection to the port is
possible.
Send command: Open a Telnet session to the respective port
and send the command.
Note: You cannot use this option if the target machine is a web
server.
Command This field is only visible if you enable sending a command above.
Enter a command that the sensor sends in a Telnet session to the
respective port. You cannot use line breaks, but a simple Telnet
command in a single line only. Please enter a string.
Response Define if the sensor will process the received response further.
Choose between:
Ignore response: Do not check the response.
Check response code (int eger): Check if the response matches
a defined response code. Define below.
Check response t ext : Check if the response matches a defined
response text. Define below.
Allowed Code This field is only visible if you enable response code check above.
Enter a code that the target device must return. If it does not
match, the sensor will show a Down status. Please enter an integer
value.
1092 02.02.2015
79 Port Sensor
Check For Existing This setting is only visible if you activated text processing above.
Keywords (Positive) Check if a certain keyword is part of the received value. If there is
no match, the sensor shows a "Down" status.
Disable: Do not check for positive keywords.
Enable key word check (posit ive): Check if a certain keyword
exists in the received value. Define below.
Text Must Include This setting is only visible if you activated keyword check above.
Enter a search string that the returned value must contain.
For Keyword Search Define the method that you want to use for the search string.
Use Choose between:
Plain Text : Search for a simple string.
Keywords (Negative) Check if a certain keyword is not part of the received value. If
there is a match, the sensor shows a "Down" status.
Disable: Do not check for negative keywords.
Enable key word check (negat ive): Check if a certain keyword

does not exist in the received value. Define below.
Text Must Not Include This setting is only visible if you activated keyword check above.
Enter a search string that the returned value must not contain.
For Keyword Search Define the method you want to use for the search string. Choose
Use between:
DEBU G OPTIONS
between:
02.02.2015 1093
79 Port Sensor
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1094 02.02.2015
79 Port Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1095
79 Port Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1096 02.02.2015
79 Port Sensor
menu bar.
dependent on.
02.02.2015 1097
79 Port Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
1098 02.02.2015
80 Port Range Sensor
6.8.80 Port Range Sensor
The Port Range sensor monitors a network service by connecting to various TCP/IP ports. It
tries to connect to the specified TCP/IP port numbers of a device in succession and waits for
each request to be accepted.
Number of closed ports

Number of open ports
Time until requests are accepted
Optionally, you can set limits in the sensor channel settings 2477 . This way you can get alerts
about open/closed ports.
Port Range Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/port_range.png
Add Sensor
Sensor Settings
02.02.2015 1099
priority).
POR T R ANGE SPECIFIC
Port-by-Port-Delay (ms) Specify in milliseconds how long the sensor will wait to go to the
next port while running through all given ports.
Port Range Selection Define whether you want to monitor all ports within a range or if
Method you want to monitor several individual ports. Choose between:
Port range wit h st art /end: Monitor ports within a range.
List of port s: Monitor several individual ports.
Range Start This field is only visible if you enable the port range method above.
Enter the port number where the scan starts. Please enter an
integer value.
1100 02.02.2015
POR T R ANGE SPECIFIC
Range End This field is only visible if you enable the port range method above.
Enter the port number where the scan ends. Please enter an
integer value.
Port List This field is only visible if you enable the list of ports method
above. Enter the numbers of the ports the sensor will try to
connect to. Enter one or more individual integer values, each port
in one line.
If Value Changes Define what the sensor will do if the number of closed ports or
open ports changes. Choose between:
Ignore changes: No action is taken on change.
SENSOR DISPLAY
for each channel.
02.02.2015 1101
Inherited Settings
described below.
1102 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1103

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1104 02.02.2015
menu bar.
dependent on.
02.02.2015 1105
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
1106 02.02.2015
81 PostgreSQL Sensor
6.8.81 PostgreSQL Sensor
The PostgreSQL sensor monitors a database on a PostgreSQL server and executes a defined
query.
Remarks
Save the SQL script with the query into the \Cust om Sensors\sql\post gresql subfolder of
your PRTG installation. See manual section Dat a St orage 2871 for more information about
how to find this path
This sensor type supports PostgreSQL 7.x or later.

02.02.2015 1107
Add Sensor
Sensor Settings
priority).
DATABASE SPECIFIC
Database Enter the name of the PostgreSQL database to which the sensor
connects. For example, such a database's name could be
MyDatabase. This is a logical entity on the database server where
database objects like tables or stored procedures exist.
1108 02.02.2015
DATABASE SPECIFIC
SSL Mode Select the PostgreSQL SSL mode for the sensor connection.
PostgreSQL SSL connections require OpenSSL to be installed on
both the target server and on the PRTG probe system with this
sensor. The SSL mode options you can choose here are the same
as the values of the PostgreSQL sslmode parameter. PRTG sends it
with the sensor requests.
Choose between these SSL modes:
Disable
Allow
Prefer
Require
For details about the PostgreSQL SSL modes, please refer to the
PostgreSQL documentation.
DATA
executed.
02.02.2015 1109
DATA

queried data table.
below.
value was found.
1110 02.02.2015
DATA
value.
02.02.2015 1111
DATA

BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
custom sensors.
defined channel.
1112 02.02.2015
DATA
integer value.
string.
integer value.
added.
between:
SENSOR DISPLAY
02.02.2015 1113
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1114 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1115

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1116 02.02.2015
menu bar.
dependent on.
02.02.2015 1117
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1118 02.02.2015
Others
02.02.2015 1119
82 Probe Health Sensor
6.8.82 Probe Health Sensor
The Probe Health sensor monitors internal PRTG parameters. It shows the status of the PRTG
probe (either for the local probe, a remote probe 2848 , or a cluster 81 probe).
It checks various parameters of your PRTG system which can affect the quality of the
monitoring results:
Healt h: This index value sums up the probe state into a value between 100% (healthy) and
0% (failing). Frequent or repeated health values below 100% should be investigated.
Probe Process CPU Load: This channel shows the current percentage CPU load that the
probe process causes. Extensive CPU load can lead to false, incomplete, and incorrect
monitoring results. This value usually should stay below 50%.
Dat a St orage Free: This channel shows the free disk space on the probe system.
Approximately you need 200 KB disk space per sensor per day (with a 60 seconds scanning
interval 242 ).
Handles: This is a counter for the data structures of the operating system. It is responsible
for internal resource management. Repeated obviously increasing values should be
investigated.
Int erval Delay non-WMI&SNMP: This channel shows the percentage interval delay for all
sensor types which are not from the type SNMP or WMI. If this value is over 0%, try to
increase the scanning intervals 242 or distribute your sensors over multiple probes 2848 .
Int erval Delay SNMP: This channel shows the percentage interval delay for SNMP sensors. If
this value is above 0%, there are probably too many very slow SNMP V3 sensors. In this case,
try to increase the monitoring intervals 242 or distribute the sensors over several probes 2848 .
Int erval Delay WMI: This channel shows the percentage interval delay for WMI sensors. If
this value is above 0%, WMI sensors could not check the target device according to their
interval. 100% means that WMI sensors on the average are checked with twice their interval.
For values above 0% try to increase the monitoring intervals 242 or distribute the sensors
over several probes 2848 to keep the number of WMI sensors per probe below 120 (with 60
seconds interval) or 600 (with 300 seconds interval).
Lost Flow Packet s: This channel shows the percentage of lost flow 2760 packets. The higher
this value, the less flow packages PRTG can handle. Usually, this value should be 0%.
Investigate increasing values.
Memory Usage: This channel shows the amount of memory being used by the PRTG probe
service as reported by the memory manager. Repeated obviously increasing values should
be investigated. If the value is constantly above 2 GB this indicates that PRTG runs at its
limits. In this case you should distribute some sensors to Remote Probe 2848 .
Message Queue: This channel shows the number of monitoring results from the probe
which have not been processed yet by the core. This value usually should stay below 1/10
of the sensor count.
Open Request s: This channel shows the number of currently active monitoring requests.
This value should stay below the maximum of 500 open requests.
Sy slog Buffer: This channel shows the number of buffered syslog packages. Usually, this
value should be 0 (or very low). Investigate increasing values.
1120 02.02.2015
Threads: This channel shows the number of program parts which are running simultaneously
currently. This value can increase with heavy load. The number should not exceed 100 in
normal operation.
Toplist Memory : This channel shows the amount of RAM that the Toplist s 2498 on this probe
are using. Stay below 1 GB memory usage (depending on available memory on the probe
system). If necessary, reduce the number of toplists or distribute them on multiple probes 2848
.
Trap Buffer: This channel shows the number of buffered SNMP traps. Usually, this value
should be 0 (or very low). Investigate increasing values.
Probe Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/probe_health.png
02.02.2015 1121
Remarks
PRTG creates this sensor automatically and you cannot delete it.
You can create this sensor only on a probe device (either local probe, a remote probe 2848 , or
a cluster 81 probe).
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
1122 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 1123
SCANNING INTER VAL
Choose between:
option will apply.
1124 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1125

Notifications
Others
1126 02.02.2015
83 QoS (Quality of Service) One Way Sensor
6.8.83 QoS (Quality of Service) One Way Sensor
The QoS (Quality of Service) One Way sensor monitors parameters regarding the quality of a
network connection between two probes. This is important, for example, when using Voice
over IP (VoIP) over this connection.
The sensor sends a series of UDP packets from the parent probe to another probe and
measures these parameters:
Jitter in milliseconds (maximum, minimum, average)

Packet delay variation in milliseconds (maximum, minimum, average)
Corrupted packets in percent
Duplicated packets in percent
Lost packets in percent
Packets out of order in percent
Time to last packet in milliseconds
QoS (Quality of Serv ic e) One Way Sensor
11.02.2015 1127
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/qos.png
Remarks
Note: You have to configure at least one remote probe 2847 in your setup for this sensor to
work.
You can create this sensor on the Probe Device of either a local or remote probe.
Add Sensor
Sensor Settings
priority).
1128 11.02.2015
QU ALITY OF SER VICE MEASU R EMENT
Target Probe Define the target probe that will receive the UDP packets. The drop
down menu shows all local and remote probes of your setup.
When running the sensor on the local probe, select a remote
probe as Target Probe. If no remote probe is available, please
install and connect a remote probe 2847 first. When running the
sensor on a remote probe, select either another remote probe or
the local probe as target. The sensor will measure values for the
network track between the probe the sensor is created on and
the target probe.
Note: You must ensure that firewalls, NAT rules, etc. allow UDP
packets to reach the target probe. The Windows firewall on the
target system will be opened automatically by the probe.
Target Host/IP Define the IP address of the target probe to which the probe the
sensor is created on connects. If you do not use NAT rules, this is
usually the address shown above next to the target probe's name.
Port Define the source and t arget port for the UDP packets. This port
is used on both the source and target probe. Use a different port
for each QoS sensor to make sure packets can be assigned
correctly. Enter an integer value between 1024 and 65536.
Note: This port must be available on both the source and target
system.
Number of Packets Define how many packets the sensor sends with each scanning
interval. Please enter an integer value. Default value is 1000. We
Size of Packets (Bytes) Define the size in bytes of the packets which the sensor sends.
Please enter an integer value. Default value is 172. We recommend
Time between Packets Define the time in milliseconds that the sensor waits between two
(ms) packets. Please enter an integer value. Default value is 20. We
11.02.2015 1129
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1130 11.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
11.02.2015 1131

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1132 11.02.2015
menu bar.
dependent on.
11.02.2015 1133
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
1134 11.02.2015
84 QoS (Quality of Service) Round Trip Sensor
6.8.84 QoS (Quality of Service) Round Trip Sensor
The QoS (Quality of Service) Round Trip sensor monitors parameters regarding the quality of a
network connection between two probes. This is important, for example, when using Voice
over IP (VoIP) over this connection. The sensor sends a series of UDP packets from the source
probe to a target at the 'end' of the connection line. Then, the packets are sent back to the
original probe ("round trip").
The sensor measures the following parameters:
Jitter in milliseconds (maximum, minimum, average)

Packet delay variation in milliseconds (maximum, minimum, average)
MOS (Mean Opinion Score)
Corrupted packets in percent
Duplicated packets in percent
Lost packets in percent
Packets out of order in percent
Round trip time (RTT) in milliseconds (maximum, minimum, average)
Time to last packet in milliseconds
02.02.2015 1135
QoS (Quality of Serv ic e) Round Trip Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/qos_round_trip.png
Remarks
Note: You have to configure at least one remote probe 2847 in your setup, or you need to set
up the PRTG QoS Reflector tool on the target machine at the endpoint of the monitored
connection.
Knowledge Base: How can I monitor QoS roundtrips without using remote probes?
Knowledge Base: How does PRTG calculate the MOS score for QoS sensors?
1136 02.02.2015
Add Sensor
Sensor Settings
priority).
02.02.2015 1137
QU ALITY OF SER VICE MEASU R EMENT
QoS Target Define the type of target that will receive the UDP packets. Choose
between:
PRTG Probe (recommended): The connection endpoint is a
PRTG probe.
Cust om Target : Choose this option if you want to use the PRTG
QoS Reflector as connection endpoint. See section More 1143 for
information about this tool.
Target Probe This setting is only available if you select PRTG probe as QoS
target. In the drop down menu, you see all local and remote
probes of your setup.
When running the sensor on the local probe, select a remote
probe as Target Probe. If no remote probe is available, install and
connect a remote probe 2847 first or use the QoS Reflector. When
running the sensor on a remote probe, select either another
remote probe or the local probe as target. The sensor will measure
values for the network track between the probe the sensor is
created on and the target probe.
Note: You must ensure that firewalls, NAT rules, etc. will allow the
UDP packets to reach the target probe. The Windows firewall on
the target system will be automatically opened by the probe.
Target Host/IP Define the IP address of the QoS target. If you use the QoS
Reflector, enter the address of the machine on which the reflector
script runs. If you use a probe, enter the address of the probe to
which the probe the sensor is created on connects. If you do not
use NAT rules, this is usually the address shown above next to the
target probe's name.
Port Define the source and t arget port for the UDP packets. This port
will be used on both the source and target probe resp. machine.
Use a different port for each QoS sensor to make sure packets can
be assigned correctly. Enter an integer value between 1024 and
65536.
Note: This port must be available on both the source and target
system.
Number of Packets Define how many packets the sensor sends for each scanning
interval. Please enter an integer value. Default value is 1000. We
Size of Packets (Bytes) Define the size in bytes of the packets which the sensor sends.
1138 Please enter an integer value. Default value is 172. We recommend 02.02.2015
Time between Packets Define the time in milliseconds that the sensor waits between two
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1139
SCANNING INTER VAL
Choose between:
option will apply.
1140 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1141
menu bar.
dependent on.
1142 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How does PRTG calculate the MOS score for QoS sensors?
Knowledge Base: How can I monitor QoS roundtrips without using remote probes?

02.02.2015 1143
Notifications
Others
1144 02.02.2015
85 RADIUS Sensor
6.8.85 RADIUS Sensor
IMPOR TANT NOTICE
This sensor type is outdated. We strongly recommend you to use the RADIUS v2 Sensor 1152
instead. This is a new sensor type to monitor RADIUS servers and shows the RADIUS code
in addition to the response time.
The RADIUS sensor monitors a Remote Authentication Dial-In User Service (RADIUS) server.
The sensor tries to authenticate at the server and shows the response time. If authentication
fails, the sensor shows a Down status.
Add Sensor
Sensor Settings
priority).
02.02.2015 1145
85 RADIUS Sensor
R ADIU S SPECIFIC
longer than this value, the request is aborted and an error
message is triggered. The maximum value is 900 seconds (15
minutes). Please enter an integer value.
User Define the user name that is used for authentication at the server.
Password Define the password that is used for authentication between the
client and the RADIUS server. Please enter a string. Note: The
password must not be longer than 6 characters.
Secret Define the shared secret that is used for authentication between
the authenticator (here the PRTG Probe) and the server. Please
enter a string.
Port Enter the port number used for connection to the server. Default
value is 1812. Please enter an integer value.
NAS IP Address Define a valid NAS IP address or leave the field empty.
NAS-Identifier Enter a NAS identifier. Please enter a string or leave the field empty.
Chap Define if you want to use the Challenge Handshake Authentication

Protocol. Choose between:
Don't use Chap
Use Chap
SENSOR DISPLAY
for each channel.
1146 02.02.2015
85 RADIUS Sensor
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 1147
85 RADIUS Sensor
SCANNING INTER VAL
Choose between:
option will apply.
1148 02.02.2015
85 RADIUS Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1149
85 RADIUS Sensor
menu bar.
dependent on.
1150 02.02.2015
85 RADIUS Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 1151
86 RADIUS v2 Sensor
6.8.86 RADIUS v2 Sensor
The RADIUS v2 sensor monitors a Remote Authentication Dial-In User Service (RADIUS) server
according to RFC 2865. The sensor tries to authenticate at the server and shows the
following:
Response time
RADIUS code.
If authentication fails, the sensor shows a Down status 123 .
Remarks
Note: This sensor type supersedes the outdated RADIUS sensor. We recommend you to use
this new sensor to monitor RADIUS servers.

Add Sensor
1152 02.02.2015
86 RADIUS v2 Sensor
priority).
02.02.2015 1153
86 RADIUS v2 Sensor
R ADIU S SPECIFIC
longer than this value, the request is aborted and an error
message is triggered. The maximum value is 900 seconds (15
minutes). Please enter an integer value.
User Define the user name that is used for authentication at the server.
Password Define the password that is used for authentication between the
client (this is the PRTG probe on which the sensors runs) and the
RADIUS server. Please enter a string.
Note: The password must not be longer than 6 characters.
Secret Define the shared secret that is used for authentication between
the authenticator (this is the PRTG Probe) and the server. Please
enter a string.
Port Enter the port number that is used for connection to the server.
Default value is 1812. Please enter an integer value.
NAS-IP-Address Define a valid Network Access Server (NAS) IP address or leave the
field empty.
Note: Please define either a NAS-IP-Address or a NAS-Identifier for
the access request.
NAS-Identifier Enter a NAS identifier. Please enter a string or leave the field empty.
Note: Please define either a NAS-IP-Address or a NAS-Identifier for
the access request.
between:
1154 02.02.2015
86 RADIUS v2 Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1155
86 RADIUS v2 Sensor
SCANNING INTER VAL
Choose between:
option will apply.
1156 02.02.2015
86 RADIUS v2 Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1157
86 RADIUS v2 Sensor
menu bar.
dependent on.
1158 02.02.2015
86 RADIUS v2 Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1159
86 RADIUS v2 Sensor
Others
1160 02.02.2015
87 RDP (Remote Desktop) Sensor
6.8.87 RDP (Remote Desktop) Sensor
The RDP (Remote Desktop) Sensor monitors remote desktop services (RDP, Terminal Services
Client).
It shows the response time of the service.
RDP (Remote Desktop) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/rdp_remote_desktop.png
Add Sensor
Sensor Settings
02.02.2015 1161
priority).
SENSOR SPECIFIC
Please enter an integer value. Default value is 3389. We
SENSOR DISPLAY
for each channel.
1162 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 1163
SCANNING INTER VAL
Choose between:
option will apply.
1164 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1165
menu bar.
dependent on.
1166 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1167
Others
1168 02.02.2015
88 SCVMM Host Sensor
6.8.88 SCVM M Host Sensor
The SCVMM Host sensor monitors a host that is managed by a Microsoft System Center Virtual
Machine Manager (SCVMM). This can be, for example, a Hyper-V host, a VMware host, or a
XenServer host.
CPU usage
Free memory (in bytes and percentage)
Overall status
Communication status
Cluster node status
Virtual server status
Computer status
Number of virtual machines
SCVMM Host Sensor
02.02.2015 1169
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sc v mm_host.png
Remarks
Requires 1170 Remote PowerShell 2.0 on the target device.
Requires 1171 the VMM PowerShell Plugin on the target device.
There are requirements 1171 for Windows Server 2012 compatibility.


Requirement: Remote PowerShell 2.0

This sensor type uses PowerShell commands. In order to monitor devices with this sensor,
Remot e PowerShell 2.0 has to be enabled.
1170 02.02.2015
Note: PowerShell 1.0 is not supported.
Requirement: VMM PowerShell Plugin

This sensor type needs the VMM PowerShell Plugin to be installed on the target machine.
Under Windows 2008 and 2012 it is part of the VMM 2008 Administrator Console, or the VMM
2012 Management Console, respectively.
Note: To provide good performance, the System Center Virtual Manager (SCVMM) only reads
the performance data from time to time and caches them. Because of this, updates can take up
to several minutes. If your monitoring returns the same values again and again, please increase
the scanning interval.
Requirement for Windows Server 2012 Compatibility

To make this sensor type compatible for Windows Server 2012 systems, you have to meet the
following requirements:
The SCVMM PowerShell module has to be in the directory C:\Program Files\Microsoft System
Center 2012\Virtual Machine Manager\bin\psModules\virtualmachinemanager
\virtualmachinemanager.
You have to set the execution policy in PowerShell to allow the execution of Import-Module
C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules
\virtualmachinemanager\virtualmachinemanager. Use the command Set -Execut ionPolicy . We
recommend the execution policy Remot eSigned; AllSigned and Unrest rict ed are also
possible.
Add Sensor
Select the hosts you want to monitor. PRTG creates one sensor for each host you select in
are created.
02.02.2015 1171
HOST SETTINGS
Host Select the hosts you want to add a sensor for. You see a list with
head.
Note: Ensure the name of your hosts do not contain unsupported
not rename hosts once you have set up monitoring. For detailed
information, please see More 767 section below.
Sensor Settings
priority).
1172 02.02.2015
HOST SETTINGS
Host Shows the host that this sensor monitors. Once a sensor is
anew.
between:
SENSOR DISPLAY
for each channel.
02.02.2015 1173
Inherited Settings
described below.
1174 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1175

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1176 02.02.2015
menu bar.
dependent on.
02.02.2015 1177
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
1178 02.02.2015


Notifications
Others
02.02.2015 1179
89 SCVMM Virtual Machine Sensor
6.8.89 SCVM M Virtual M achine Sensor
The SCVMM Virtual Machine sensor monitors a virtual machine (VM) that is managed by a
Microsoft System Center Virtual Machine Manager (SCVMM). This can be, for example, a Hyper-
V virtual machine, a VMware virtual machine, or a XenServer virtual machine.
CPU usage
Status of the monitored VM
Disk read speed
Disk write speed
SCVMM Virtual Mac hine Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sc v mm_v irtual_mac hine.png
Remarks
Requires 1181 Remote PowerShell 2.0 on the target device.
Requires 1181 the VMM PowerShell Plugin on the target device.
There are requirements 1182 for Windows Server 2012 compatibility.
1180 02.02.2015


Requirement: Remote PowerShell 2.0

This sensor type uses PowerShell commands. In order to monitor devices with this sensor,
Remot e PowerShell 2.0 has to be enabled.
Note: PowerShell 1.0 is not supported.
Requirement: VMM PowerShell Plugin

This sensor type needs the VMM PowerShell Plugin to be installed on the target machine.
Under Windows 2008 and 2012 it is part of the VMM 2008 Administrator Console, or the VMM
2012 Management Console, respectively.
02.02.2015 1181
Note: To provide good performance, the System Center Virtual Manager (SCVMM) only reads
the performance data from time to time and caches them. Because of this, updates can take up
to several minutes. If your monitoring returns the same values again and again, please increase
the scanning interval.
Requirement for Windows Server 2012 Compatibility

To make this sensor type compatible for Windows Server 2012 systems, you have to meet the
following requirements:
The SCVMM PowerShell module has to be in the directory C:\Program Files\Microsoft System
Center 2012\Virtual Machine Manager\bin\psModules\virtualmachinemanager
\virtualmachinemanager.
You have to set the execution policy in PowerShell to allow the execution of Import-Module
C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules
\virtualmachinemanager\virtualmachinemanager. Use the command Set -Execut ionPolicy . We
recommend the execution policy Remot eSigned; AllSigned and Unrest rict ed are also
possible.
Add Sensor
Select the virtual machines you want to monitor. PRTG creates one sensor for each VM you
Virtual Machine Select the Virtual Machines (VMs) you want to add a sensor for.
You see a list with the names of all items which are available to
in the table head.
Note: Ensure the names of your VMs do not contain unsupported
not rename VMs once you have set up monitoring. For detailed
information, please see More 767 section below.
1182 02.02.2015
Sensor Settings
priority).
Virtual Machine Shows the VM that this sensor monitors. Once a sensor is created,
between:
02.02.2015 1183
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1184 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1185

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1186 02.02.2015
menu bar.
dependent on.
02.02.2015 1187
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
1188 02.02.2015


Notifications
Others
02.02.2015 1189
90 Sensor Factory Sensor
6.8.90 Sensor Factory Sensor
The Sensor Factory sensor is a powerful tool that allows you to create your own sensor with
channels based on data from other sensors. You can define one or more channels using
formulas that combine monitoring results from other sensors.
Samples for usage are:
Show single channels of one or more sensors in one graph.

Use the data from single channels of one or more sensors to calculate new values (for
example, you can subtract, multiply, and divide).
Create graphs with data from other sensor channels and add horizontal lines at specific
vertical positions.
Note: A sensor factory sensor does not show a "Downtime" channel. Downtime cannot be
calculated for this sensor type.
sensor setup.
Sensor Fac tory Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sensor_fac tory .png
Remarks
Knowledge Base: How can I monitor the overall status of the business process "Email"?
1190 09.02.2015
Note: The Sensor Factory sensor might not work with flow sensors 2760 . Sensor types using
active flow timeout, this is, NetFlow and jFlow sensors 312 , are not supported by the Sensor
Factory sensor.

Add Sensor
Sensor Settings
priority).
09.02.2015 1191
SENSOR FACTOR Y SPECIFIC SETTINGS
Channel Definition Enter a channel definition for the sensor. Using a specific syntax,
you can refer to data from channels of other sensors here. You
can also calculate values. Enter one channel definition for each
new channel you want to add to this sensor. Please see section
Define Sensor Channels 1197 below.
Error Handling Define the behavior of the sensor if one of the sensors defined
above is in an error status. In this case, you can set the sensor
factory sensor either to down or to warning status. Choose
between:
Fact ory sensor shows error st at us when one or more source
sensors are in error st at us: If at least one sensor that you use
in a channel definition is in a Down status, the factory sensor
shows a Down status as well until all referred sensors leave this
status. While the factory sensor is Down, it will still show data of
all available sensor channels.
Fact ory sensor shows warning st at us when one or more
source sensors are in error st at us: If at least one sensor that
you use in a channel definition is in a Down status, the factory
sensor shows a Warning status until all referred sensors leave
the Down status.
Use cust om formula: Define the status of the factory sensor by
adding a status definition in the field below.
Status Definition This field is only visible if you enable custom formula above. Define
when the sensor will switch to a Down status. You can use the
status() function in combination with Boolean operations. For
advanced users it is also possible to calculate a status value.
Please see section Define Sensor St at us 1204 below.
If a Sensor Has No Choose how this Sensor Factory sensor reacts if a sensor referred
Data to in the channel definition does not provide any data (for example,
because it is paused or does not exist). Choose between:
Do not calculat e fact ory channels t hat use t he sensor: For
defined channels that use one or more sensor(s) that deliver no
data, no data is shown. Additionally, the factory sensor shows a
Warning status.
Calculat e t he fact ory channels and use zero as source value:
If a sensor that you use in a channel definition does not deliver
any data, zero values will be filled in instead. The sensor factory
calculates the channel value and shows it using these zero
values.
1192 09.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
09.02.2015 1193
SCANNING INTER VAL
Choose between:
option will apply.
1194 09.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
09.02.2015 1195
menu bar.
dependent on.
1196 09.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Define Sensor Channels

The channels of a Sensor Factory sensor are controlled by the Channel Definit ion text field.
Using a special syntax you can refer to other sensor channels, calculate values, and add
horizontal lines. You can define factory sensor channels using data from any other sensor's
channels on your PRTG core server.
09.02.2015 1197
Example
You see a definition of two factory sensor channels. Both use the channel() function which
simply collects data from the channels of other sensors in your monitoring and displays
them:
#1:Local Probe Health
channel(1001,0)
#2:Local Traffic Out[kbit]
channel(1004,1)
The first channel of the factory sensor (#1) collects data from the Healt h channel (ID 0) of
the Probe Healt h sensor (ID 1001) running on the Local Probe device. The second channel
(#2) collects data from the Traffic out channel (ID 1) of a traffic sensor (ID 1004) measuring
the system's local network card. Both channels will be shown together in the factory
sensor's data tables and graphs.
The basic syntax for a sensor factory channel definition looks like this:
#<id>:<name>[<unit>]
<formula>
For each channel one section is used. A section begins with the # sign. Function names in
formulas are not case sensitive.
The parameters are:
<id> is the ID of the factory sensor's channel and must be a unique number > 0.
<name> is the name of the factory sensor's channel (displayed in graphs and tables).
[<unit >] is an optional unit description for the factory sensor's channel (e.g., bytes). If you
do not provide a unit, the sensor factory selects a suitable unit string automatically
(recommended).
<formula> contains the formula to calculate the factory sensor's channel. For the formula,
you can use the following functions: channel() 1199 , min() 1200 , max() 1200 , avg() 1200 , or percent ()
1201 .
Define Sensor ChannelsFormula Calculations

Within a formula, the following elements are allowed to perform calculations with the values
that are returned by one or more functions:
Basic operations: + (add), - (substract), * (multiply), / (divide)

Example: 3 + 5 * 2
Brackets: ( )
Example: 3 * (2 + 6)
1198 09.02.2015
Compare: = (equal), <> (not equal), > (greater), < (less), >= (greater or equal), <= (less or
equal)
If the comparison resolves to true, the value is 10,000; if false, the value is 0. For delta
sensors the speed is compared.
Example
You see a Sensor Factory channel definition with calculation.

#1:Traffic Total x Minus Traffic Out y
( channel(2001,-1) - channel(1004,1) ) * 2
This full channel definition results in a factory sensor that shows a calculation with values
from two channels (channel IDs -1 and 1) of two traffic sensors (sensor IDs 2001 and 1004).
The returned values are subtracted and then multiplied by two.
Channels can be gauge values (e.g., ping ms) or delta values (e.g., traffic kbit/s). Not all
combinations are allowed in a formula. Note: When performing percentage calculation, please
use the percent () Funct ion 1201 to make sure you obtain the expected values!
There are calculations you cannot do:
You cannot add/subtract a delta from a gauge channel (and vice-versa).

You cannot multiply two delta channels.
You cannot compare a delta with a gauge channel.
You cannot use a channel of (another) Sensor Factory sensor channel in the formula.
Define Sensor Channelschannel() Function

The channel() function allows to read the data from a channel of a different sensor. The syntax
is:
channel(<sensorId>,<channelId>)
The parameters are:
<sensorId> is the ID of the sensor. It is displayed on the sensor details page in the page
header bar 114 .
<channelId> is the ID of the sensor channel. It is displayed in the respective field of the
channel settings 2478 .
09.02.2015 1199
Example
channel(2001,2)
This function reads the data from channel ID 2 of the sensor with the ID 2001.
#1:Sample
channel(2001,2)
This full channel definition reads the data from channel ID 2 of the sensor with the ID 2001
and displays it in the first factory sensor channel (#1), without any additional calculations.
Define Sensor Channelsmin() and max() Functions

The min() and max() functions return the minimum or maximum of two values. The syntax is:
min(<a>,)
max(<a>,)
Values for <a> and are either numbers or channel() 1199 functions.
Examples
min(10,5)
This function in the first line returns 5, because this is the smaller value out of 10 and 5.
min( channel(2001,1),channel(2002,1) )
This function returns the minimum of the values of channel 1 of the sensor with ID 2001 and
channel 1 of the sensor with ID 2002.
Define Sensor Channelsavg() Function

The avg() function returns the average of the two values. This equals: (a+b) / 2. The syntax is:
avg(<a>,)
Values for <a> and are either numbers or channel() 1199 functions.
1200 09.02.2015
Examples
avg(20,10)
This function returns 15: (20+10) / 2 = 15.
avg( channel(2001,1),channel(2002,1) )
This function returns the average of channel 1 of the sensor with ID 2001 and channel 1 of
the sensor with ID 2002.
Define Sensor Channelspercent() Function

The percent () function calculates the percent value of two given values, for example, a channel
and a fixed value. The syntax is:
percent(<source>,<maximum>[,<unit>])
The parameters are:
<source> is the value the percent is calculated for. This is usually a channel() 1199 function.
<maximum> is the limit value used for the percent calculation.
[<unit >] is an optional unit the maximum is provided in. You can use constants with this
function (see Const ant s 1203 section below for a list). This can be used for gauge (e.g., Ping
sensors) or delta (e.g., traffic sensors). If no unit is provided 1 will be used. Note: The sensor
adds the unit string % automatically.
PRTG will calculate: <source> / <maximum> * <unit> * 100
09.02.2015 1201
Examples
#1:Usage Traffic In
percent(channel(2001,0),100,kilobit)
#2:Usage Traffic Out
percent(channel(2001,1),100,kilobit)
This full channel definition results in a factory sensor that shows two channels of a traffic
sensor (sensor ID 2001): Traffic in (channel ID 0) and traffic out (channel ID 1). The sensor
displays the values % of maximum bandwidth (100 kilobit/second).
#1:Ping %
percent(channel(2002,0),200)
This full channel definition results in a factory sensor that shows the Ping Time channel
(channel ID 0) of a Ping sensor (sensor ID 2002). The sensor displays the values as a
percentage of 200 ms.
Define Sensor ChannelsHorizontal Lines

You can add lines to the graph using a formula without channel() function. Use a fixed value
instead. The syntax is:
#<id>:<name>[<unit>]
<value>
The parameters are:
<id> is the ID of the factory sensor's channel and must be a unique number > 1. Although
the sensor does not show a horizontal line as a channel, the ID has to be unique.
<name> is the name of the factory sensor's channel. PRTG does not display this name in
graphs and tables, but you can use it as a comment to describe the nature of the line.
[<unit >] is an optional unit description (e.g., kbit/s). If you do not provide a unit, PRTG
applies the line automatically to the scale of the first factory sensor channel. If your factory
sensor uses different units, provide a unit to make sure the line is added for the right scale.
Enter the unit exactly as shown in your graph's legend. If you enter a unit that does not yet
exist in your graph, a new scale will be added automatically.
<value> contains a number defining where the line will be shown in the graph.
1202 09.02.2015
Examples
#5:Line at 100ms [ms]

100
This channel definition results in a graph that shows a horizontal line at the value of 100 on
the ms scale.
#6:Line at 2 Mbit/s [kbit/s]

2000
This channel definition results in a graph that shows a horizontal line at the value of 2000 on
the kbit /s scale.
#1:Ping Time
channel(2002,0)
#2:Line at 120ms [ms]
120
This full channel definition results in a factory sensor that shows the Ping Time channel
(channel ID 0) of a Ping sensor (sensor ID 2002). Additionally, the sensor graphs will show a
horizontal line at 120 ms.
Define Sensor ChannelsConstants

The following constants are defined and can be used in calculations:
one = 1
kilo = 1000
mega = 1000 * kilo
giga = 1000 * mega
t era = 1000 * giga
by t e = 1
kiloby t e = 1024
megaby t e = 1024 * kilobyte
gigaby t e = 1024 * megabyte
t eraby t e = 1024 * gigabyte
bit = 1/8
kilobit = kilo / 8
megabit = mega / 8
09.02.2015 1203
gigabit = giga / 8
t erabit = tera / 8
Define Sensor Statusstatus() Function

The status of a Sensor Factory sensor can be controlled by the St at us Definit ion text field, if
you enable the custom formula option in the Sensor Set t ings 1191 . Using a special syntax, you
can define when the factory sensor changes to a Down status. In all other cases, the sensor
will be in an Up status. The syntax is:
status(sensorID) <boolean> status(sensorID)
The parameters are:
<sensorId> is the ID of the sensor you want to check the status of. It is displayed on the
sensor details page in the page header bar 114 .
<boolean> is one of the Boolean operators AND, OR, or NOT. If the resulting expression is
true, the factory sensor will change to a Down status.
1204 09.02.2015
Examples
status(2031) AND status(2044)
This changes the factory sensor to a Down status if both sensors, with IDs 2031 and 2044,
are Down. Otherwise the factory sensor shows an Up status.
status(2031) OR status(2044)
This changes the factory sensor to a Down status if at least one of the sensors with ID
2031 or ID 2044 is Down. Otherwise the factory sensor shows an Up status.
status(2031) AND NOT status(2044)
This changes the factory sensor to a Down status if the sensor with ID 2031 is Down, but
the sensor with ID 2044 is not in a Down status. Otherwise the factory sensor shows an Up
status.
Note: A status() function with NOT has to be connected with AND or OR if it is combined
with other status() functions:
status(sensorID) AND NOT status(sensorID)
status(sensorID) OR NOT status(sensorID)
( status(2031) AND status(2044) ) OR status(2051)
This changes the factory sensor to a Down status if both the sensor with ID 2031 and the
sensor with ID 2044 is Down, or if the sensor with ID 2051 is Down. Otherwise the factory
sensor shows an Up status.
Additionally, the following elements are allowed to perform calculations and comparisons with
the values that are returned by the status functions:
Basic operations: + (add), - (substract), * (multiply), / (divide)

Example: 3 + 5 * 2
Brackets: ( )
Example: 3 * (2 + 6)
Compare: = (equal), <> (not equal), > (greater), < (less), >= (greater or equal), <= (less or
equal)
If the comparison resolves to true, the value is 10,000; if false, the value is 0. For delta
sensors the speed is compared.
Internally, the status() function returns the downtime channel of the sensor in hundreds of
percent (10,000 = 100%).
true corresponds to a value of 10,000 which is a Down status.

false corresponds to a value of 0 which is an Up status.
09.02.2015 1205
If you understand this, you are able to use more complex formulas.
Example
( status(1031) + status(1032) + status(1033) + status(1034) ) >= 20000
This changes the factory sensor to a Down status if at least any two of the sensors with
IDs 1031, 1032, 1033, or 1034 are Down. Otherwise the factory sensor shows an Up status.
Note: You can also use the status() function in channel definitions 1197 . Using this functionality, it
is possible, for example, to display the numeric status value of sensors in a factory sensor
channel.
Using Factory Sensors in a Cluster Setup

If you run PRTG in Clustering 81 mode, please note these additional facts:
If you add a Sensor Factory sensor underneath the Clust er Probe, and in the Sensor Factory
formula you refer to a channel of a sensor running on the Clust er Probe as well, the Sensor
Factory sensor shows the data of all cluster nodes for this sensor channel.
If you add a Sensor Factory sensor underneath the Local Probe, and in the Sensor Factory
formula you refer to a channel of a sensor running on the Clust er Probe, the Sensor Factory
sensor only shows data of the primary master node for this sensor channel.
More
Knowledge Base: Can I add sensors to Sensor Factory sensors using tags?
Knowledge Base: How can I monitor the overall status of the business process "Email"?

To change display settings and limits, switch to the sensor's Overview tab and click the gear
icon of a specific channel. For detailed information, please see Sensor Channels Set t ings 2477
section.
Notifications
1206 09.02.2015
Others
09.02.2015 1207
91 sFlow Sensor
6.8.91 sFlow Sensor
The sFlow sensor receives traffic data from a sFlow V5 compatible device and shows the traffic
by type. Only header traffic will be analyzed. Ensure the device matches the sFlow version V5!
There are several filter options available to divide traffic into different channels.
Chat (IRC, AIM)

Citrix
NetBIOS
Total traffic
sensor setup.
1208 02.02.2015
91 sFlow Sensor
sFlow Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sflow.png
Remarks
Note: You must enable sFlow V5 export on the monitored device for this sensor to work.
The device must send the flow data stream to the IP address of the PRTG probe system on
which the sensor is set up (either a local or remote probe).
The sensor accepts RAW data only. The stream must be sent via IPv4.
02.02.2015 1209
91 sFlow Sensor
There are several limitations 1210 for this sensor type.
Paessler Website: Paessler sFlow Tester
Sniffer sensors?
Limitations of This Sensor Type

There are some limitations that you want to consider before using this sensor type:
Only sFlow version 5 datagrams are supported
Only IPv4 flows are supported
Only the "raw packet header" format is supported
Only the "Flow sample" format is supported. "Extended flow" and "Counter" formats cannot be
processed
PRTG processes only samples where the source ID matches the ifIndex of the input interface
(avoiding double counted traffic) and ascending sequence numbers. Due to internal
limitations, only interface numbers up to 65535 are supported.
Sample packets have to be of ethernet type "IP" (with optional VLAN tag)
Sampled packets of type TCP and UDP are supported
We recommend using sFlow tester for debugging (see More section below).
Add Sensor
Sensor Settings
1210 02.02.2015
91 sFlow Sensor
priority).
SFLOW SPECIFIC SETTINGS
Receive sFlow Packets Enter the UDP port number on which the flow packets are
on UDP Port received. It must match the one you have configured in the sFlow
export options of your hardware router device. Default value is
6343. Please enter an integer value.
Note: When configuring export, ensure you select the appropriate
sFlow version 5.
sFlow from. Enter an IP address to receive data from a specific
Receive sFlow Packets Select the IP address(es) on which PRTG listens to sFlow packets.
in the sFlow export options of your hardware router device.
sFlow version 5.
02.02.2015 1211
91 sFlow Sensor

UDP and TCP.
Ot her.
channel.
FILTER ING
section.
1212 02.02.2015
91 sFlow Sensor
FILTER ING
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
02.02.2015 1213
91 sFlow Sensor
Inherited Settings
described below.
1214 02.02.2015
91 sFlow Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1215
91 sFlow Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1216 02.02.2015
91 sFlow Sensor
menu bar.
dependent on.
02.02.2015 1217
91 sFlow Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1218 02.02.2015
91 sFlow Sensor
Toplists
More
http://www.paessler.com/tools/sflowtester
Sniffer sensors?


Notifications
Others
Related Topics
02.02.2015 1219
92 sFlow (Custom) Sensor
6.8.92 sFlow (Custom) Sensor
The sFlow (Custom) sensor receives traffic data from a sFlow V5 compatible device and shows
the traffic by type. Please make sure the device matches the sFlow version V5! There are
several filter options available to divide traffic into different channels.
sensor setup.
1220 02.02.2015
sFlow (Custom) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sflow.png
Remarks
Note: You must enable sFlow V5 export on the monitored device for this sensor to work.
The device must send the flow data stream to the IP address of the PRTG probe system on
which the sensor is set up (either a local or remote probe).
The sensor accepts RAW data.
02.02.2015 1221
There are several limitations 1222 for this sensor type.
Limitations of This Sensor Type

There are some limitations that you want to consider before using this sensor type:
Only sFlow version 5 datagrams are supported
Only IPv4 flows are supported
Only the "raw packet header" format is supported
Only the "Flow sample" format is supported. "Extended flow" and "Counter" formats cannot be
processed
PRTG processes only samples where the source ID matches the ifIndex of the input interface
(avoiding double counted traffic) and ascending sequence numbers. Due to internal
limitations, only interface numbers up to 65535 are supported.
Sample packets have to be of ethernet type "IP" (with optional VLAN tag)
Sampled packets of type TCP and UDP are supported
We recommend using sFlow tester for debugging (see More section below).

Add Sensor
Sensor Settings
1222 02.02.2015
priority).
SFLOW SPECIFIC SETTINGS
Receive sFlow Packets Enter the UDP port number on which the flow packets are
on UDP Port received. It must match the one you have configured in the sFlow
export options of your hardware router device. Default value is
6343. Please enter an integer value.
sFlow version 5.
sFlow from. Enter an IP address to receive data from a specific
Receive sFlow Packets Select the IP address(es) on which PRTG listens to sFlow packets.
in the sFlow export options of your hardware router device.
sFlow version 5.
02.02.2015 1223
Channel Definition Enter a channel definition to divide the traffic into different
Sensors 2835 section.
All traffic for which no channel is defined will be accounted to the
default channel named Ot her.
FILTER ING
section.
SENSOR DISPLAY
for each channel.
1224 02.02.2015
SENSOR DISPLAY
PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
02.02.2015 1225
SCANNING INTER VAL
Choose between:
option will apply.
1226 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1227
menu bar.
dependent on.
1228 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1229
Toplists
More
http://www.paessler.com/tools/sflowtester


Notifications
Others
Related Topics
1230 02.02.2015
93 SFTP Secure File Transfer Protocol Sensor
6.8.93 SFTP Secure File Transfer Protocol Sensor
The sFTP Secure File Transfer Protocol sensor monitors FTP servers of a Linux/Unix system
using SSH File Transfer Protocol (FTP over SSH).
It tries to connect and shows the response time of the server.
SFTP Sec ure File Transfer Protoc ol Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sftp_sec ure_file_transfer_protoc ol.png
Remarks
For this sensor type credentials for Linux/Solaris/Mac OS (SSH/WBEM) systems must be
defined for the device you want to use the sensor on.
Note: This sensor type cannot support all Linux/Unix and Mac OS distributions.
For a general introduction to SSH monitoring, please see manual section Monit oring via
SSH 2756 .
Add Sensor
Sensor Settings
02.02.2015 1231
priority).
SSH SPECIFIC
Connection Timeout Enter a timeout in seconds for the request. If the reply takes
(Sec.) longer than this value defines, the sensor will cancel the request
This timeout value determines the time the sensor waits to
establish a connection to the host. Keep this value as low as
possible.
Shell Timeout (Sec.) Define a timeout for the shell response. This is the time in seconds
the sensor waits for the shell to return a response after it has sent
its specific command (for example, cat /proc/loadavg).
SSH Port Define which port this sensor uses for the SSH connection.
Choose between:
Inherit port number from parent device (default ): Use the
SSH port number as defined in the Credentials for Linux/Solaris/
Mac OS (SSH/WBEM) Systems section of the device on which you
create this sensor.
1232 02.02.2015
SSH SPECIFIC
Ent er cust om port number: Do not use the port number from
the parent device settings but define a different port number
below.
Use Port Number This field is only visible if you enable the custom port number
setting above. Enter the port number this sensor uses for the SSH
connection. Please enter an integer value.
Result Handling Define what PRTG will do with the result of the sensor. Choose
between:
SENSOR DISPLAY
for each channel.
Show in and out t raffic as posit ive and negat ive area chart :
Show channels for incoming and outgoing traffic as positive and
negative area chart. This will visualize your traffic in a clear way.
Note: This option cannot be used in combination with manual
Vertical Axis Scaling (available in the Sensor Channels Set t ings
2477 settings).
02.02.2015 1233
SENSOR DISPLAY
Inherited Settings
described below.
1234 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1235

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1236 02.02.2015
menu bar.
dependent on.
02.02.2015 1237
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1238 02.02.2015

Notifications
Others
02.02.2015 1239
94 Share Disk Free Sensor
6.8.94 Share Disk Free Sensor
The Share Disk Free sensor monitors free disk space of a share (Windows/Samba) using Server
Message Block (SMB).
It shows the free disk space in percent and bytes.
Share Disk Free Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/share_disk_free.png
Remarks
Requires 1240 the LanmanServer Windows service to be running on the target device.
Note: This sensor only works if no quotas are enabled on the target share. If there are
quotas enabled for the user account this sensor uses to connect to the share, the absolute
value will be okay, but the percentage variable will show wrong values.
PE032
Requirement: Server Service

In order to monitor shares on Windows machines, please make sure the LanmanServer "Server"
Windows service is running on the target computer.
Automatic.
1240 02.02.2015
Add Sensor
Sensor Settings
priority).
SHAR E CONFIGU R ATION
Share Enter the name of the share this sensor will monitor. Only a share
name is allowed here (for example, enter C$). Please do not enter a
complete UNC name here. The server name (\\server\) is taken
from the parent device of this sensor.
Note: To provide any shares under Windows, the LanmanServer
"Server" Windows service must be running on the target computer.
02.02.2015 1241
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1242 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1243

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1244 02.02.2015
menu bar.
dependent on.
02.02.2015 1245
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1246 02.02.2015
More

Notifications
Others
02.02.2015 1247
95 SIP Options Ping Sensor
6.8.95 SIP Options Ping Sensor
The SIP Options Ping sensor monitors the connectivity for a Session Initiation Protocol (SIP)
server using SIP options "Ping". It can be used to monitor voice-over-IP (VoIP) services. The
sensor sends "auth" and "options" requests to the SIP server. It can alert in case of an error.
It shows the response time of the SIP server.
SIP Options Ping Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sip_options_ping.png
Remarks
Note: A SIP server might return a "480 Service temporarily unavailable" error until at least one
reachable SIP client is connected to the server.

1248 02.02.2015
Add Sensor
Sensor Settings
priority).
SIP SPECIFIC
Please enter an integer value. The default UDP port is 5060.
Username Enter the username of the SIP account this sensor will log on to
after a connection to the SIP server has been established. Please
enter a string.
02.02.2015 1249
SIP SPECIFIC
Password Enter the password of the SIP account this sensor will log on to
after a connection to the SIP server has been established. Please
enter a string.
Timeout (Seconds) Enter the timeout for the connection to the SIP server. Please
enter an integer value. The maximum value is 300.
Retry Count If the connection to the SIP server fails, the sensor can re-try to
connect. Enter the maximum number of retries. After reaching the
maximum count, the sensor will show a red Down status 123 .
SENSOR DISPLAY
for each channel.
1250 02.02.2015
Inherited Settings
described below.
02.02.2015 1251
SCANNING INTER VAL
Choose between:
option will apply.
1252 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1253
menu bar.
dependent on.
1254 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1255
More

Notifications
Others
1256 02.02.2015
96 SMTP Sensor
6.8.96 SM TP Sensor
The SMTP sensor monitors a mail server using Simple Mail Transfer Protocol (SMTP) and can
optionally send a test email with every check.
SMTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/smtp.png
Add Sensor
Sensor Settings
02.02.2015 1257
96 SMTP Sensor
priority).
SMTP SPECIFIC
Port Enter the number of the port that the sensor uses to send an email
via SMTP. For non-secure connections usually port 25 is used and
port 465 or 587 for SSL/TLS connections. The actual setting
depends on the server you connect to.
value. If you do not get a connection, please try another port
number.
AU THENTICATION
Type Select whether to use an authentication method for the SMTP

connection. Choose between:
None: Do not use any authentication method.
Username and password: Authenticate at the SMTP server via
username and password.
1258 02.02.2015
96 SMTP Sensor
AU THENTICATION
Username This field is only visible if you enable SMTP authentication above.
Enter a username for SMTP authentication. Please enter a string.
Password This field is only visible if you enable SMTP authentication above.
Enter a password for SMTP authentication. Please enter a string.
HELO Ident Enter a server name for the HELO part of the email protocol. For
some mail servers, the HELO identifier must be the valid principal
host domain name for the client host. See SMTP RFC 2821.
between:
status 123 .
SSL/TLS protocol.
02.02.2015 1259
96 SMTP Sensor
MONITOR ING
Send Email Define if PRTG sends an email when connecting to the SMTP server.
Choose between:
None: Do not send an email, just connect to the SMTP server.
Send Email: Send an email through the SMTP server. If there is
an error when sending the email, an error message will be
triggered and the sensor will change to a Down status.
From Specify which address the sent emails contain in the from field.
Please enter a valid email address.
To Specify to which address PRTG sends the emails to. If you define
more than one recipient, separate the individual email addresses by
comma. Please enter a valid email address.
Topic Specify which subject the sent emails contain. Please enter a string
or leave the field empty.
Content Specify which body the sent emails contain. Please enter a string
between:
SENSOR DISPLAY
1260 02.02.2015
96 SMTP Sensor
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
02.02.2015 1261
96 SMTP Sensor
SCANNING INTER VAL
Choose between:
option will apply.
1262 02.02.2015
96 SMTP Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1263
96 SMTP Sensor
menu bar.
dependent on.
1264 02.02.2015
96 SMTP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 1265
97 SMTP&IMAP Round Trip Sensor
6.8.97 SM TP&IM AP Round Trip Sensor
The SMTP&IMAP Round Trip sensor monitors the time it takes for an email to reach an Internet
Message Access Protocol (IMAP) mailbox after being sent using Simple Mail Transfer Protocol
(SMTP). It sends an email to the parent device via SMTP and then scans a dedicated IMAP
mailbox until this email comes in. The SMTP&IMAP Round Trip sensor will delete these emails
automatically from the mailbox as soon as PRTG retrieves them. Emails will only remain in the
mailbox particularly if a timeout or a restart of the PRTG server occurred during sensor run-
time.
Response time of SMTP server

Response time of IMAP server
Sum of both response times
SMTP&IMAP Round Trip Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/smtp_imap_round_trip.png
Remarks
Note: Please use dedicated email accounts with this sensor type. If you use more sensors of
this type, please make sure that each sensor uses its own email accounts.
For a general introduction to the technology behind round trip monitoring, please see
Monit oring Email Round Trip 2770 section.
1266 02.02.2015
Add Sensor
We recommend adding this sensor to an SMTP server device only, because this sensor type's
settings are optimized for this scenario.
Sensor Settings
priority).
DEBU G OPTIONS
between:
02.02.2015 1267
DEBU G OPTIONS

EMAIL SETTINGS
From Specify which address the sent emails contain in the from field.
To Specify to which address PRTG sends the emails. Please enter a

valid email address.
HELO Ident Enter a server name for the HELO part of the mail protocol. For
some mail servers the HELO identifier must be the valid principal
1268 02.02.2015
STEP 1: SEND EMAIL TO PAR ENT DEVICE U SING SMTP
In this step, you configure how PRTG sends the emails. As SMTP server, the sensor uses the
IP-Address/DNS Name property's value of the device on which you add this sensor.
via SMTP. Please enter an integer value. For non-secure
connections usually port 25 is used and port 465 or 587 for SSL/
TLS connections. The actual setting depends on the server you are
connecting to.
number.
Timeout for SMTP Enter a timeout in seconds for the request. If the reply takes
Connection (Sec.) longer than this value defines, the sensor will cancel the request
SMTP Authentication Define if you want to use an authentication for the SMTP
Type connection. Choose between:
Username/Password: Authenticate at the SMTP server via
Additional Text for The subject part of the round trip email is created automatically by
Email Subject PRTG. It consists of the string "PRTG Roundtrip Mail:" followed by a
unique GUID to correctly identify the email in the IMAP mailbox (for
example, PRTG Roundtrip Mail: {5E858D9C-AC70-466A-9B2A-
55630165D276}). Use this field to place your custom text before
the automatically created text.
between:
02.02.2015 1269

status 123 .
SSL/TLS protocol.
1270 02.02.2015
STEP 2: CHECK AN IMAP MAILBOX U NTIL EMAIL AR R IVES
In this step, you configure how the sent emails will be received.
IP-Address/DNS Name Specify the IMAP server. Enter a valid IP address or DNS name.
Mailbox Specify the IMAP Mailbox (resp. "IMAP folder") you want to check.
Enter the IMAP mailbox/folder name.
Port Specify the port that the sensor uses for the IMAP connection. For
non-secure connections usually port 143 is used and port 993 for
SSL/TLS connections. The actual setting depends on the server
you connect to.
number.
Connection Interval Enter the number of seconds the sensor will wait between two
(Sec.) connections to the IMAP server. PRTG will repeatedly check the
mailbox in this interval until the email arrives. Please enter an
integer value.
Maximum Trip Time Enter the number of seconds an email may take to arrive in the
(Sec.) IMAP mailbox. PRTG will repeatedly check the mailbox in the
interval specified above until the email arrives. If it does not arrive
within the maximum trip time, the sensor will trigger an error
message. Please enter an integer value.
Username Enter a username for IMAP authentication. Please enter a string.
Password Enter a password for IMAP authentication. Please enter a string.
between:
02.02.2015 1271

status 123 .
SSL/TLS protocol.
SENSOR DISPLAY
for each channel.
1272 02.02.2015
Inherited Settings
described below.
02.02.2015 1273
SCANNING INTER VAL
Choose between:
option will apply.
1274 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1275
menu bar.
dependent on.
1276 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 1277
98 SMTP&POP3 Round Trip Sensor
6.8.98 SM TP&POP3 Round Trip Sensor
The SMTP&POP3 Round Trip sensor monitors the time it takes for an email to reach an Post
Office Protocol version 3 (POP3) mailbox after being sent using Simple Mail Transfer Protocol
(SMTP). It sends an email to the parent device via SMTP and then scans a dedicated POP3
mailbox until the email comes in. The SMTP&POP3 Round Trip sensor will delete these emails
automatically from the mailbox as soon as PRTG retrieves them. Emails will only remain in the
mailbox particularly if a timeout or a restart of the PRTG server occurred during sensor run-
time.
Response time of SMTP server

Response time of POP3 server
Sum of both response times.
SMTP&POP3 Round Trip Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/smtp_pop3_round_trip.png
Remarks
Note: Please use dedicated email accounts with this sensor type. If you use more sensors of
this type, please make sure that each sensor uses its own email accounts.
For a general introduction to the technology behind round trip monitoring, please see
Monit oring Email Round Trip 2770 section.
1278 02.02.2015
Add Sensor
We recommend adding this sensor on an SMTP server device only, as this sensor type's
settings are optimized for this scenario.
Sensor Settings
priority).
DEBU G OPTIONS
between:
02.02.2015 1279
DEBU G OPTIONS

EMAIL SETTINGS
From Specify which address the sent emails will contain in the from field.
To Specify to which address PRTG sends the emails. Please enter a

valid email address.
HELO Ident Enter a server name for the HELO part of the mail protocol. For
some mail servers the HELO identifier must be the valid principal
1280 02.02.2015
STEP 1: SEND EMAIL TO THE PAR ENT DEVICE U SING SMTP
In this step, you configure how PRTG sends the emails. As SMTP server, the sensor uses the
IP-Address/DNS Name property's value of the device on which you add this sensor.
via SMTP. Please enter an integer value. For non-secure
connections usually port 25 is used and port 465 or 587 for SSL/
TLS connections. The actual setting depends on the server you
connect to.
number.
Timeout for SMTP Enter a timeout in seconds for the request. If the reply takes
Connection (Sec.) longer than this value defines, the sensor will cancel the request
SMTP Authentication Define if you want to use an authentication for the SMTP
Type connection. Choose between:
Username/Password: Authenticate at the SMTP server via
Additional Text for The subject part of the round trip email is created automatically by
Email Subject PRTG. It consists of the string "PRTG Roundtrip Mail:" followed by a
unique GUID to correctly identify the email in the POP3 mailbox (for
example, PRTG Roundtrip Mail: {5E858D9C-AC70-466A-9B2A-
55630165D276}). Use this field to place your custom text before
the automatically created text.
between:
02.02.2015 1281

status 123 .
SSL/TLS protocol.
1282 02.02.2015
STEP 2: CHECK A POP3 MAILBOX U NTIL EMAIL AR R IVES
In this step, you configure how the sent emails will be received.
IP-Address/DNS Name Specify the POP3 server. Enter a valid IP address or DNS name.
Port Specify the port that the sensor uses for the POP3 connection. For
non-secure connections usually port 110 is used and port 995 for
SSL/TLS connections. The actual setting depends on the server
you are connecting to.
number.
Connection Interval Enter the number of seconds the sensor will wait between two
(Sec.) connections to the IMAP server. PRTG will repeatedly check the
mailbox in this interval until the email arrives. Please enter an
integer value.
Maximum Trip Time Enter the number of seconds an email may take to arrive in the
(Sec.) IMAP mailbox. PRTG will repeatedly check the mailbox in the
interval specified above until the email arrives. If it does not arrive
within the maximum trip time, the sensor will trigger an error
message. Please enter an integer value.
POP3 Authentication Select the kind of authentication for the POP3 connection.
Type Choose between:
Wit hout Login: Monitor the connection to the POP3 server only.
Username and Password: Log on to the POP3 server with user
name and password (simple login, non-secure).
128-bit MD5 hash value (APOP): Send the password in an

encrypted form using APOP. This option must be supported by
the POP3 server you're connecting to.
Username This field is only visible if you select an option with login above.
Password This field is only visible if you select an option with login above.
02.02.2015 1283
between:
status 123 .
SSL/TLS protocol.
SENSOR DISPLAY
for each channel.
1284 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 1285
SCANNING INTER VAL
Choose between:
option will apply.
1286 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1287
menu bar.
dependent on.
1288 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 1289
99 SNMP APC Hardware Sensor
6.8.99 SNM P APC Hardware Sensor
The SNMP APC Hardware sensor monitors performance counters on an APC UPS device using
Simple Network Management Protocol (SNMP).
Actual voltage of battery

Capacity of battery
Temperature of battery
Remaining runtime of battery
Input and output frequency
Input and output voltage
Output load
sensor setup. For additional counters, please see section More 1297 .
SNMP APC Hardware Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_apc _hardware.png
Remarks
Knowledge Base: How can I monitor additional counters with the SNMP APC Hardware
sensor?
1290 02.02.2015
Add Sensor
Select the performance counters you want to monitor. PRTG creates one sensor for each
counter you select in the Add Sensor dialog. The settings you make in this dialog are valid for
all of the sensors that are created.
APC U PS SPECIFIC
Library OIDs Select the performance counters you want to add a sensor for.
in the table head.
Sensor Settings
02.02.2015 1291
priority).
APC U PS SPECIFIC
Selected Interface Shows the name of the interface (performance counter) that this
sensor monitors. Once a sensor is created, you cannot change this
Unit String Define the unit of the numerical data that the sensor monitors at
the given OID. Please enter a string.
Multiplication If you want to multiply the received data with a certain value, enter
the quotient here. Please enter an integer value.
Division If you want to divide the received data by a certain value, enter the
divisor here. Please enter an integer value.
change.
SENSOR DISPLAY
1292 02.02.2015
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
02.02.2015 1293
SCANNING INTER VAL
Choose between:
option will apply.
1294 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1295
menu bar.
dependent on.
1296 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How can I monitor additional counters with the SNMP APC Hardware sensor?


02.02.2015 1297
Notifications
Others
1298 02.02.2015
100 SNMP Cisco ADSL Sensor
6.8.100 SNM P Cisco ADSL Sensor
The SNMP Cisco ADSL sensor monitors Asymmetric Digital Subscriber Line (ADSL) statistics of a
Cisco router using Simple Network Management Protocol (SNMP).
Speed of downlink
Speed of uplink
Remote and local attenuation
Remote and local SNR (signal-to-noise ratio)
Remote and local power output
sensor setup.
Remarks
Add Sensor
For devices with multiple performance counters, multiple sensors are created at once in the
Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are
created.
CISCO ADSL SETTINGS
Line Index Select the performance counters you want to add a sensor for.
in the table head.
02.02.2015 1299
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
1300 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1301
SCANNING INTER VAL
Choose between:
option will apply.
1302 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1303
menu bar.
dependent on.
1304 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1305
Others
1306 02.02.2015
101 SNMP Cisco ASA VPN Connections Sensor
6.8.101 SNM P Cisco ASA VPN Connections Sensor
The SNMP Cisco ASA VPN Connections sensor monitors the Virtual Private Network (VPN)
connections on a Cisco Adaptive Security Appliance using Simple Network Management
Protocol (SNMP).
Active email sessions

Active Internet Protocol Security (IPsec) sessions
Active L2L sessions
Active LB sessions
Active sessions in total
Active SVC sessions
Active users
Groups with active users
SNMP Cisc o ASA VPN Connec tions Sensor
02.02.2015 1307
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_asa_v pn_c onnec tions.png
Remarks
Add Sensor
Sensor Settings
priority).
1308 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
Choose between:
64-bit counters.
02.02.2015 1309

Choose between:
device.


algorithm.
algorithm.
1310 02.02.2015
is triggered.
02.02.2015 1311
SCANNING INTER VAL
Choose between:
option will apply.
1312 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1313
menu bar.
dependent on.
1314 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1315
Others
1316 02.02.2015
102 SNMP Cisco ASA VPN Traffic Sensor
6.8.102 SNM P Cisco ASA VPN Traffic Sensor
The SNMP Cisco ASA VPN Traffic sensor monitors the traffic of an Internet Protocol Security
(IPsec) Virtual Private Network (VPN) connection on a Cisco Adaptive Security Appliance using
Incoming traffic
Outgoing traffic
SNMP Cisc o ASA VPN Traffic Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_asa_v pn_traffic .png
Remarks
This sensor type is indented to monitor permanent connections. It will show an error if a
connection is interrupted.
This sensor can monitor IPsec connections only!
Add Sensor
11.02.2015 1317
Select the connections you want to monitor. PRTG creates one sensor for each connection
ASA VPN SPECIFIC
Connections Select the IPsec VPN connections you want to add a sensor for.
in the table head.
Note: This sensor type can only monitor VPN connections based
on IPsec. This means, for example, that connections using "Cisco
AnyConnect" are not listed here.
Sensor Settings
priority).
1318 11.02.2015
ASA VPN SPECIFIC
Remote IP Shows the IP address of the connection this sensor monitors.

Note: This sensor type can only monitor VPN connections based
on IPsec.
Sensor Behavior Define the status of the sensor 123 if there is no active connection
available. Choose between:
Show 'Down' st at us if no connect ion is act ive
(recommended)
Show 'Warning' st at us if no connect ion is act ive
St ay in 'Up' st at us if no connect ion is act ive
SENSOR DISPLAY
for each channel.
11.02.2015 1319
Inherited Settings
described below.
Choose between:
64-bit counters.
Choose between:
device.
1320 11.02.2015


algorithm.
algorithm.
is triggered.
11.02.2015 1321
SCANNING INTER VAL
Choose between:
option will apply.
1322 11.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
11.02.2015 1323
menu bar.
dependent on.
1324 11.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
11.02.2015 1325
Others
1326 11.02.2015
103 SNMP Cisco ASA VPN Users Sensor
6.8.103 SNM P Cisco ASA VPN Users Sensor
The SNMP Cisco ASA VPN Users sensor monitors account connections to a Virtual Private
Network (VPN) on a Cisco Adaptive Security Appliance via Simple Network Management
Protocol (SNMP).
Number of currently connected accounts

If a specific user account is currently offline or online
SNMP Cisc o ASA VPN Users Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_asa_v pn_users.png
Remarks
02.02.2015 1327
Add Sensor
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
1328 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
Choose between:
64-bit counters.
02.02.2015 1329
Choose between:
device.


algorithm.
algorithm.
1330 02.02.2015
is triggered.
02.02.2015 1331
SCANNING INTER VAL
Choose between:
option will apply.
1332 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1333
menu bar.
dependent on.
1334 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1335
Others
1336 02.02.2015
104 SNMP Cisco CBQoS Sensor
6.8.104 SNM P Cisco CBQoS Sensor
The SNMP Cisco CBQoS sensor monitors network parameters using Cisco's Class Based Quality
of Service (CBQoS) via Simple Network Management Protocol (SNMP). It supports the classes
Class Map, Match Statement, and Queueing.
The sensor can show the following depending on the particular class type:
Current and maximum queue depth

Pre policy packets
Pre and post policy size
Drop packets and size
Drop packets without buffer
Fragment packets and size.
sensor setup.
SNMP Cisc o CBQoS Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_c bqos.png
02.02.2015 1337
Remarks
Add Sensor
Select the CBQoS entries you want to monitor. To monitor Quality of Service (QoS) via
compatible devices, PRTG creates one sensor for each CBQoS entry you choose in the Add
Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are
created.
CLASS BASED QOS SPECIFIC
CBQoS Entries Select the measurements you want to add a sensor for. You see a
table head.
Sensor Settings
1338 02.02.2015
priority).
CLASS BASED QOS SPECIFIC
Object Type Shows further information about the parameter that this sensor
Interface
Description
BitMask
ObjectID
ConfigID
SENSOR DISPLAY
for each channel.
02.02.2015 1339
SENSOR DISPLAY

Inherited Settings
described below.
1340 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1341

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1342 02.02.2015
menu bar.
dependent on.
02.02.2015 1343
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1344 02.02.2015
Others
02.02.2015 1345
105 SNMP Cisco System Health Sensor
6.8.105 SNM P Cisco Sy stem Health Sensor
The SNMP Cisco System Health sensor monitors the system health of a Cisco device via Simple
Network Management Protocol (SNMP).
It can show the following depending on the available components of your device:
CPU load in percent

Available memory in absolute and percentage values
Status of power supplies
Current temperature and temperature status
sensor setup.
SNMP Cisc o Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_sy stem_health.png
Remarks
1346 02.02.2015
Add Sensor
Select the components you want to monitor. To monitor the system health of a Cisco device,
PRTG creates one sensor for each measurement you choose in the Add Sensor dialog. The
settings you make in this dialog are valid for all of the sensors that are created.
CISCO SYSTEM HEALTH SPECIFIC
Measurement Select the measurements you want to add a sensor for. You see a
table head.
Sensor Settings
02.02.2015 1347
priority).
CISCO SYSTEM HEALTH SPECIFIC
Measurement Shows the ID of the measurement that this sensor monitors. Once
the sensor anew.
SENSOR DISPLAY
for each channel.
1348 02.02.2015
Inherited Settings
described below.
02.02.2015 1349
SCANNING INTER VAL
Choose between:
option will apply.
1350 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1351
menu bar.
dependent on.
1352 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1353
More

Notifications
Others
1354 02.02.2015
106 SNMP Cisco UCS Blade Sensor
6.8.106 SNM P Cisco UCS Blade Sensor
WORK IN PROGRESS
Sorry, this section is not finished yet. Please see future versions of this manual for new
content.
02.02.2015 1355
107 SNMP Cisco UCS Chassis Sensor
6.8.107 SNM P Cisco UCS Chassis Sensor
The SNMP Cisco UCS Chassis sensor monitors the health status of the chassis of a Cisco
Unified Computing System (UCS) device via Simple Network Management Protocol (SNMP).
It can show the states of the following properties:
Configuration
License
Oper
Operability
Power
Thermal
Serial electronic erasable programmable read-only memory (SEEPROM)
sensor setup.
SNMP Cisc o UCS Chassis Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_uc s_c hassis.png
1356 02.02.2015
Remarks
Add Sensor
Select the chassis you want to monitor. PRTG creates one sensor for each chassis you choose
in the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors
that are created.
SENSOR SETTINGS
Chassis Select the chassis you want to add a sensor for. You see a list with
head.
Sensor Settings
02.02.2015 1357
priority).
SENSOR SETTINGS
Chassis Shows the chassis that this sensor monitors. Once a sensor is
anew.
SENSOR DISPLAY
for each channel.
1358 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1359
SCANNING INTER VAL
Choose between:
option will apply.
1360 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1361
menu bar.
dependent on.
1362 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1363
More

Notifications
Others
1364 02.02.2015
108 SNMP Cisco UCS Physical Disk Sensor
6.8.108 SNM P Cisco UCS Phy sical Disk Sensor
The SNMP Cisco UCS Physical Disk sensor monitors a physical disk of a Cisco Unified
Computing System (UCS) device via Simple Network Management Protocol (SNMP).
Operability status of the disk

Connection status of the disk
Remarks
Add Sensor
In order to monitor physical disks in a UCS device, PRTG will create one sensor for each disk
you choose. The settings you make in this dialog are valid for all of the sensors that are
created.
U CS PHYSICAL DISK
Disks Select the disks you want to add a sensor for. You see a list with
head.
Note: Only working disks (with the current status Up or Warning)
will be shown here.
02.02.2015 1365
Sensor Settings
priority).
U CS PHYSICAL DISK
Disk Shows the disk which this sensor monitors. Once a sensor is
anew.
Display Name Shows the display name of the physical disk which this sensor
1366 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1367
SCANNING INTER VAL
Choose between:
option will apply.
1368 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1369
menu bar.
dependent on.
1370 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1371
More

Notifications
Others
1372 02.02.2015
109 SNMP Cisco UCS System Health Sensor
6.8.109 SNM P Cisco UCS Sy stem Health Sensor
The SNMP Cisco UCS System Health sensor monitors the system health of a Cisco Unified
Computing System (UCS) device via Simple Network Management Protocol (SNMP).
Number of operable resp. inoperable fans

Status of fan performance, fan thermal, and fan voltage
If a fan failure is predicted
Number of operable resp. inoperable fan modules
Status of fan module performance, fan module thermal, and fan module voltage
If a fan module failure is predicted
Number of operable resp. inoperable power supplies
Status of power supply performance, power supply thermal, and power supply voltage
If a power supply failure is predicted
Number of minor, major, and critical faults (which are not acknowledged yet in the UCS logs)
Number of warnings (which are not acknowledged yet in the UCS logs)
sensor setup.
02.02.2015 1373
SNMP Cisc o UCS Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_uc s_sy stem_health.png
Remarks
Add Sensor
1374 02.02.2015
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
02.02.2015 1375
SENSOR DISPLAY
Inherited Settings
described below.
1376 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1377

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1378 02.02.2015
menu bar.
dependent on.
02.02.2015 1379
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1380 02.02.2015
More

Notifications
Others
02.02.2015 1381
110 SNMP CPU Load Sensor
6.8.110 SNM P CPU Load Sensor
The SNMP CPU Load sensor monitors the system load using Simple Network Management
Protocol (SNMP).
It shows the load of several CPUs in percent.
SNMP CPU Load Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c pu_load.png
Remarks
1382 02.02.2015
Add Sensor
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
02.02.2015 1383
SENSOR DISPLAY

Inherited Settings
described below.
1384 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1385

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1386 02.02.2015
menu bar.
dependent on.
02.02.2015 1387
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1388 02.02.2015
More

Notifications
Others
02.02.2015 1389
111 SNMP Custom Lookup Sensor
6.8.111 SNM P Custom Lookup Sensor
WORK IN PROGRESS
Sorry, this section is not finished yet. Please see future versions of this manual for new
content.
1390 02.02.2015
112 SNMP Custom Sensor
6.8.112 SNM P Custom Sensor
The SNMP Custom sensor monitors a numerical value returned by a specific Object Identifier
(OID) using Simple Network Management Protocol (SNMP).
It shows the numerical value at a given OID of an SNMP device.
SNMP Custom Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c ustom.png
Remarks
Knowledge Base: How do I find out what OID I need to use for a custom sensor?
Add Sensor
02.02.2015 1391
OID VALU ES
Channel Name Enter a name for the channel in which the sensor shows the
results at the given OID. Please enter a string. You can change this
value later in the respective channel settings 2477 of this sensor.
Value Type Select the expected numeric type of the results at the given OID.
Choose between:
Gauge (unsigned Int eger): For integer values, such as 10 or
120.
Gauge (signed int eger): For integer values, such as -12 or 120.
Gauge (float ): For float values, such as -5.80 or 8.23.
Delt a (Count er): For counter values. PRTG will calculate the
difference between the last and the current value.
Sensor Settings
1392 02.02.2015
priority).
OID VALU ES
OID Value Enter the OID of the SNMP object you want to receive numerical
data from.
Note: Most OIDs begin with 1.3.6.1. However, entering OIDs
starting with 1.0, or 1.1, or 1.2 is also allowed. If you want to
disable the validation of your entry entirely, add the string
norfccheck: to the beginning of your OID, for example,
norfccheck:2.0.0.0.1.
Unit String Define the unit of the numerical data that this sensor receives from
Value Type Shows the value type of the numerical data that this sensor
receives from the given OID. Once a sensor is created, you cannot
the multiplier here. Please enter an integer value. Otherwise, use
the default value 1 to not change the received value.
divisor here. Please enter an integer value. Otherwise, use the
default value 1 to not change the received value.
change.
02.02.2015 1393
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1394 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1395

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1396 02.02.2015
menu bar.
dependent on.
02.02.2015 1397
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More


1398 02.02.2015
Notifications
Others
02.02.2015 1399
113 SNMP Custom String Sensor
6.8.113 SNM P Custom String Sensor
The SNMP Custom String sensor monitors a string returned by a specific OID using Simple
Network Management Protocol (SNMP). It can check for keywords. If you want to use limits for
the sensor channel value, you can also extract a numeric value contained in the string.
Response time of the monitored device

Optionally a value extracted from the string
SNMP Custom String Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c ustom_string.png
Remarks
Example: Number Extraction with Regular Expression 1409
Add Sensor
Sensor Settings
1400 02.02.2015
priority).
02.02.2015 1401
OID VALU ES
OID Value Enter the OID of the SNMP object you want to receive a string
from.
Note: Most OIDs begin with 1.3.6.1. However, entering OIDs
starting with 1.0, or 1.1, or 1.2 is also allowed. If you want to
disable the validation of your entry entirely, add the string
norfccheck: at the beginning of your OID, for example,
norfccheck:2.0.0.0.1.
Maximum Length of Define the maximum allowed length of the string to be received
String from the SNMP object at the given OID. If the string is longer than
this value, the sensor shows a Down status 123 . Please enter an
integer value or leave the field empty.
change.
1402 02.02.2015
KEYWOR D SEAR CH
Response Must Include Define which string must be part of the data that is received from
(Error State) the SNMP object at the given OID. You can either enter plain text
or a Regular Expression 2846 . If the data does not include the
search pattern, the sensor shows a Down status 123 . Please enter a
string or leave the field empty.
For Keyword Search Define in which format you have entered the search expression in
Use the field above.
Plain Text : Search for the string as plain text. The characters *
and ? work here as placeholder, whereas * stands for no or any
number of characters and ? stands for exactly one character (as
known from Windows search). This behavior cannot be disabled,
so the literal search for these characters is not possible with
plain text search.
Regular Expression: Treat the search pattern as a Regular
Expression 2846 .
Response Must Not Define which string must not be part of the data that is received
Include (Error State) form the SNMP object at the given OID. You can either enter plain
text or a Regular Expression 2846 . If the data does include the
search pattern, the sensor shows a Down status 123 . Please enter a
string or leave the field empty.
plain text search.
Expression 2846 .
Response Must Include Define which string must be part of the data that is received from
(Warning State) the SNMP object at the given OID. You can either enter plain text
or a Regular Expression 2846 . If the data does not include the
search pattern, the sensor shows a Warning status 123 . Please
plain text search.
02.02.2015 1403
Expression 2846 .
EXTENDED PR OCESSING
Interpret Result as Define the type of the received string. Choose between:
St ring (default ): Handle the result as common string.
Hexadecimal by t es (as in MAC addresses): Handle the result
as hexadecimal bytes. For example, choose this option when
monitoring MAC addresses.
Decimal by t es (as in IP addresses): Handle the result as decimal
bytes. For example, choose this option when monitoring IP
addresses.
Extract Number Using Define if you want to filter out a numeric value from the string
Regular Expression received from the SNMP object at the given OID. You can convert
this into a float value to use it with channel limits (see Sensor
Channels Set t ings 2477 ).
No ext ract ion: Do not extract a float value. Use the result as a
string value.
Ext ract a numeric value using a regular expression: Use a
regular expression to identify a numeric value in the string and
convert it to a float value. Define below. See also the example
1409 below.
Regular Expression This setting is only visible if you enable number extraction above.
Enter a Regular Expression 2846 to identify the numeric value you
want to extract from the string returned by the SNMP object at the
given OID. You can use capturing groups here. Make sure the
expression returns numbers only (including decimal and thousands
separators). The result will be further refined by the settings
below.
Index of Capturing This setting is only visible if you enable number extraction above. If
Group your regular expression uses capturing groups, please specify
which one will be used to capture the number. Please enter an
integer value or leave the field empty.
Decimal Separator This setting is only visible if you enable number extraction above.
Define which character is used as decimal separator for the number
extracted above. Please enter a string or leave the field empty.
Thousands Separator This setting is only visible if you enable number extraction above.
Define which character is used as thousands separator for the
number extracted above. Please enter a string or leave the field
empty.
1404 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1405
SCANNING INTER VAL
Choose between:
option will apply.
1406 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1407
menu bar.
dependent on.
1408 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Example: Number Extraction with Regular Expression

If you want to extract a number in the response string using a regular expression, please note
that the index for captures in this sensor is based on 1 (not on 0). Furthermore, capturing
groups are not created automatically. The example below will illustrate this issue.
Consider the following string as returned by a request for CPU usage:

5 Sec (3.49%), 1 Min (3.555%), 5 Min (3.90%)
Assuming you would like to filter for the number 3.555, i.e., the percentage in the second
parentheses. Then enter the following regex in the Regular Expression field:
(\d+\.\d+).*(\d+\.\d+).*(\d+\.\d+)
As Index of Capt uring Group enter 3. This will extract the desired number 3.555.
02.02.2015 1409
The index has to be 3 in this case because the capturing groups here are the following:
Group 1 contains "3.49%), 1 Min (3.555), 5 Min (3.90"

Group 2 contains "3.49"
Please keep in mind this note about index and capturing groups when using number
extraction.
More


Notifications
Others
1410 02.02.2015
114 SNMP Dell Hardware Sensor
6.8.114 SNM P Dell Hardware Sensor
The SNMP Dell Hardware sensor monitors performance counters on a Dell hardware device
using Simple Network Management Protocol (SNMP). The data that you can monitor with this
sensor depends on the available performance counters on the target system.
This sensor shows a value returned by a specific Dell hardware OID, for example:
Data about the system management software

Data about system status
Information about chassis and BIOS
Various hardware parameters
Other valuable data
sensor setup.
SNMP Dell Hardware Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_dell_hardware.png
Remarks
Requires 1412 the Dell OpenManage Server Administrator to be installed on the monitored Dell
device.
Knowledge Base: What do I need to monitor Dell servers?
02.02.2015 1411
Requirement: Dell OpenManage Server Administrator

This sensor needs the Dell OpenManage Server Administrator tool to be installed on the Dell
hardware device to monitor it. Please make sure that you enable SNMP in the OpenManage
Server Administrator. For details, please see section More 1418 below.
Add Sensor
Select the Dell performance counter you want to monitor. PRTG creates one sensor for each
OID you choose in the Add Sensor dialog. The settings you make in this dialog are valid for all
of the sensors that are created.
DELL HAR DWAR E SPECIFIC
Library OIDs Select the performance counters you want to add a sensor for.
in the table head.
Sensor Settings
1412 02.02.2015
priority).
Selected Interface Shows the name of the interface (performance counter) that this
Unit String Define the unit of the numerical data that the sensor receives at
the multiplier here. Please enter an integer value.
divisor here. Please enter an integer value.
change.
02.02.2015 1413
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1414 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1415

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1416 02.02.2015
menu bar.
dependent on.
02.02.2015 1417
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More


1418 02.02.2015
Notifications
Others
02.02.2015 1419
115 SNMP Dell PowerEdge Physical Disk Sensor
6.8.115 SNM P Dell PowerEdge Phy sical Disk Sensor
The SNMP Dell PowerEdge Physical Disk sensor monitors a physical disk in a Dell PowerEdge
server using Simple Network Management Protocol (SNMP).
Disk status
Roll up status
Component status
If there is currently a warning regarding the Self-Monitoring, Analysis and Reporting
Technology (S.M.A.R.T.) status
SNMP Dell PowerEdge Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_dell_poweredge_phy sic al_disk.png
Remarks
Requires 1421 iDRAC 7 or the Dell OpenManage Server Administrator to be installed on the
monitored server.
Knowledge Base: My Dell PowerEdge sensor fails to validate and I can't add it. What can I do?
1420 02.02.2015
Requirement: Dell OpenManage Server Administrator or iDRAC 7

PowerEdge server to monitor it. Please make sure that you enable SNMP in the OpenManage
Server Administrator. For details, please see section More below. Note: You can also monitor
Dell PowerEdge servers with this sensor type via Integrated Dell Remote Access Controller
(iDRAC) 7.
Add Sensor
Select the disks you want to monitor. PRTG creates one sensor for each disk you select in
are created.
DELL POWER EDGE PHYSICAL DISK SETTINGS
head.
Sensor Settings
02.02.2015 1421
priority).
DELL POWER EDGE PHYSICAL DISK SETTINGS
Disk Shows the name of the disk that this sensor is monitoring. Once a
the sensor anew.
Data Source Shows the interface which is used to get monitoring data. This is
either Dell OpenManage Server Administrator (OMSA) or Integrated
Dell Remote Access Controller (iDRAC).
SENSOR DISPLAY
for each channel.
1422 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 1423
SCANNING INTER VAL
Choose between:
option will apply.
1424 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1425
menu bar.
dependent on.
1426 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1427
More


Notifications
Others
1428 02.02.2015
116 SNMP Dell PowerEdge System Health Sensor
6.8.116 SNM P Dell PowerEdge Sy stem Health Sensor
The SNMP Dell PowerEdge System Health sensor monitors the system health of a Dell
PowerEdge server using Simple Network Management Protocol (SNMP).
It can show the states of the following components, depending on their availability:
Global system
Power supply
Temperature
Cooling device
Memory device
Voltage
sensor setup.
02.02.2015 1429
SNMP Dell PowerEdge Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_dell_poweredge_sy stem_health.png
Remarks
Requires 1431 iDRAC 7 or the Dell OpenManage Server Administrator to be installed on the
monitored server.
1430 02.02.2015
Requirement: Dell OpenManage Server Administrator or iDRAC 7

PowerEdge server to monitor it. Please make sure that you enable SNMP in the OpenManage
Server Administrator. For details, please see section More below. Note: You can also monitor
Dell PowerEdge servers with this sensor type via Integrated Dell Remote Access Controller
(iDRAC) 7.
Add Sensor
Select the Dell PowerEdge chassis you want to monitor.PRTG creates one sensor for each
chassis you choose in the Add Sensor dialog. The settings you make in this dialog are valid for
all of the sensors that are created.
DELL POWER EDGE SYSTEM HEALTH SPECIFIC
Chassis Select the chassis you want to add a sensor for. You see a list with
head.
Sensor Settings
02.02.2015 1431
priority).
DELL POWER EDGE SYSTEM HEALTH SPECIFIC
Chassis Shows the chassis that this sensor monitors. Once a sensor is
anew.
Channel Mask Shows the channel mask that describes which sensors are
available. Once a sensor is created, you cannot change this value.
Data Source Shows the interface which is used to get monitoring data. This is
either Dell OpenManage Server Administrator (OMSA) or Integrated
Dell Remote Access Controller (iDRAC).
SENSOR DISPLAY
1432 02.02.2015
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
02.02.2015 1433
SCANNING INTER VAL
Choose between:
option will apply.
1434 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1435
menu bar.
dependent on.
1436 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1437
More


Notifications
Others
1438 02.02.2015
117 SNMP Disk Free Sensor
6.8.117 SNM P Disk Free Sensor
The SNMP Disk Free sensor monitors the free disk space on a logical disk via Simple Network
Management Protocol (SNMP).
Free disk space in percent

Free disk space in bytes
Total disk space
SNMP Disk Free Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_disk_free.png
Remarks
This sensor uses more generic Object Identifier (OID) values compared to the SNMP Linux
Disk Free Sensor 1590 .
Add Sensor
02.02.2015 1439
Select the disk(s) you want to monitor. PRTG creates one sensor for each disk you choose in
are created.
DISK FR EE SETTINGS
Disk Select one or more disks you want to add a sensor for. You see a
table head.
Sensor Settings
priority).
1440 02.02.2015
DISK FR EE SETTINGS
Disk Shows the name of the disk that this sensor is monitoring. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1441
SCANNING INTER VAL
Choose between:
option will apply.
1442 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1443
menu bar.
dependent on.
1444 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1445
More

Notifications
Others
1446 02.02.2015
118 SNMP GSA System Health Sensor
6.8.118 SNM P GSA Sy stem Health Sensor
The SNMP GSA System Health sensor monitors the system health of a Google Search Appliance
(GSA) via Simple Network Management Protocol (SNMP).
Number of queries per minute

Number of processed documents
Number of indexed documents
Number of processed bytes
Activity status of crawling
Crawling rate per second
Health status of disk
Health status of temperature
Health status of machine
02.02.2015 1447
SNMP GSA Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_gsa_sy stem_health.png
Remarks
PRTG shows the location you provide in the GSA's SNMP configuration section in Geo Maps
2516 .
To use SNMP v3 for monitoring, you need to add an SNMP v3 user to the GSA's SNMP
configuration.
Add Sensor
1448 02.02.2015
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
02.02.2015 1449
SENSOR DISPLAY
Inherited Settings
described below.
1450 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1451

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1452 02.02.2015
menu bar.
dependent on.
02.02.2015 1453
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1454 02.02.2015
Others
02.02.2015 1455
119 SNMP Hardware Status Sensor
6.8.119 SNM P Hardware Status Sensor
The SNMP Hardware Status sensor monitors the status of a hardware component of a server
via Simple Network Management Protocol (SNMP).
Current status of the monitored hardware component

Number of errors per time period
SNMP Hardware Status Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hardware_status.png
Remarks
Add Sensor
1456 02.02.2015
Select the hardware components you want to monitor. PRTG creates one sensor for each
component you choose in the Add Sensor dialog. The settings you make in this dialog are
valid for all of the sensors that are created.
HAR DWAR E SPECIFIC
Hardware Component Select the hardware components you want to add a sensor for.
in the table head.
Sensor Settings
priority).
02.02.2015 1457
HAR DWAR E SPECIFIC
Hardware Component
Product ID
Shows further information about the hardware component. Once a
Description reference purposes only. If you need to change this, please add
the sensor anew.
Type
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1458 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1459

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1460 02.02.2015
menu bar.
dependent on.
02.02.2015 1461
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1462 02.02.2015
Others
02.02.2015 1463
120 SNMP HP LaserJet Hardware Sensor
6.8.120 SNM P HP LaserJet Hardware Sensor
The SNMP HP LaserJet Hardware sensor monitors performance counters on a HP LaserJet

hardware device using Simple Network Management Protocol (SNMP).
It can show the following, depending on what category you monitor:
Status of toner
Status of paper
Paper jam status
SNMP HP LaserJet Hardware Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_laserjet_hardware.png
Remarks
Add Sensor
1464 02.02.2015
Select the categories you want to monitor. PRTG creates one sensor for each category you
Library OIDs Select the categories you want to add a sensor for. You see a list
head.
The following performance counters for your printer are available:
Toner/St at us
Paper/St at us
Jam/St at us
Sensor Settings
02.02.2015 1465
priority).
HP LASER JET SPECIFIC
Selected Interface Shows the name of the category (performance counter) that this
change.
SENSOR DISPLAY
for each channel.
1466 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1467
SCANNING INTER VAL
Choose between:
option will apply.
1468 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1469
menu bar.
dependent on.
1470 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1471
Others
1472 02.02.2015
121 SNMP HP ProLiant Logical Disk Sensor
6.8.121 SNM P HP ProLiant Logical Disk Sensor
The SNMP HP ProLiant Logical Disk sensor monitors a logical disk in an HP server via Simple
Disk status
Completion in percent: This is only important when the disk status is "Reconstructing" or
"Expanding" and illustrates the progress of this task.
SNMP HP ProLiant Logic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_proliant_logic al_disk.png
Remarks
Requires 1474 HP Insight Management Agents and HP Insight Management WBEM Providers to
be installed on the target device.
Knowledge Base: Monitor HP ProLiant via SNMP?
If the sensor shows a "cannot find such device types" error message, use an HP iLO interface
1474 as parent device for this sensor (if available).
This sensor type supports monitoring HP Integrated Lights-Out (iLO) as of iLO version 3. We
recommend you to use iLO 4 because this version applies its own dedicated SNMP counters
while iLO 3 only forwards SNMP counters from the particular operating system.
02.02.2015 1473
Requirement: HP System Management Tools

This sensor needs a specific HP system management tool to be installed on the target device,
so it reports data via SNMP: HP Insight Management Agents for Windows Server 2003/2008. To
receive SNMP data from RAID controllers, you additionally need HP Insight Management WBEM
Providers. For more details and download links please refer to the subsection More below.
Note: Some of the HP Object Identifiers (OIDs) which this sensor type uses are only accessible
via the HP Integrated Lights-Out (iLO) interface. If this sensor throws an error that it cannot
find "such device types", please create a device in PRTG which points to the address of the HP
iLO interface (if available) and add the sensor to this device. We recommend using the
Agentless Management feature with configured SNMP. You can set this up in the iLO
configuration interface under Administ rat ion | Management | SNMP Set t ings.
Add Sensor
Select the disks in the HP server you want to monitor. PRTG creates one sensor for each disk
HP PR OLIANT LOGICAL DISK SETTINGS
head.
Sensor Settings
1474 02.02.2015
priority).
HP PR OLIANT LOGICAL DISK SETTINGS
Disk Shows the name of the disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
02.02.2015 1475
SENSOR DISPLAY
Inherited Settings
described below.
1476 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1477

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1478 02.02.2015
menu bar.
dependent on.
02.02.2015 1479
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1480 02.02.2015
More
Knowledge Base: Monitor HP ProLiant via SNMP


Notifications
Others
02.02.2015 1481
122 SNMP HP ProLiant Memory Controller Sensor
6.8.122 SNM P HP ProLiant M emory Controller Sensor
The SNMP HP ProLiant Memory Controller sensor monitors a memory controller in an HP server
Error status of the controller

Condition of the controller
States and conditions of available modules.
SNMP HP ProLiant Memory Controller Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_proliant_memory _c ontroller.png
1482 02.02.2015
Remarks
Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory
Controller Sensor?
Note: If modules are inserted at a later point, you have to add this sensor anew.

Add Sensor
Select the memory controllers in the HP server you want to monitor. PRTG creates one sensor
for each controller you choose in the Add Sensor dialog. The settings you make in this dialog
are valid for all of the sensors that are created.
02.02.2015 1483
HP PR OLIANT MEMOR Y CONTR OLLER SETTINGS
Controller Select the controllers you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
HP PR OLIANT MEMOR Y CONTR OLLER SETTINGS
Controller Shows the name of the controller that this sensor monitors. Once
the sensor anew.
1484 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1485
SCANNING INTER VAL
Choose between:
option will apply.
1486 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1487
menu bar.
dependent on.
1488 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1489
More
Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory
Controller Sensor?


Notifications
Others
1490 02.02.2015
123 SNMP HP ProLiant Network Interface Sensor
6.8.123 SNM P HP ProLiant Network Interface Sensor
The SNMP HP ProLiant Network Interface sensor monitors a network interface in an HP server
Traffic in
Traffic out
Number of transmitted and received good frames
Number of transmitted and received bad frames
Alignment errors
FCS (Frame Check Sequence) errors
Late and excessive collisions
Carrier sense errors
If frames are too long
Remarks
Note: When adding the sensor, the status of each available network interface is shown. If
this status is Link Failure, it is still possible to add a sensor for the respective interface.
Though, most likely the sensor for this interface will not work correctly. The error message
in this case will be "No Such Name (SNMP error # 2)".

02.02.2015 1491
Add Sensor
Select the network interfaces in the HP server you want to monitor. PRTG creates one sensor
for each interface you choose in the Add Sensor dialog. The settings you make in this dialog
HP PR OLIANT NETWOR K INTER FACE SETTINGS
Network Interface Select the interfaces you want to add a sensor for. You see a list
head.
Note: If this status is Link Failure, it is still possible to add a sensor
for the respective interface. Though, most likely the sensor for this
interface will not work correctly. The error message in this case
will be "No Such Name (SNMP error # 2)".
Sensor Settings
1492 02.02.2015
priority).
HP PR OLIANT NETWOR K INTER FACE SETTINGS
Network Interface Shows the name of the interface that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
02.02.2015 1493
SENSOR DISPLAY
2477 settings).
Inherited Settings
described below.
1494 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1495

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1496 02.02.2015
menu bar.
dependent on.
02.02.2015 1497
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1498 02.02.2015
More


Notifications
Others
02.02.2015 1499
124 SNMP HP ProLiant Physical Disk Sensor
6.8.124 SNM P HP ProLiant Phy sical Disk Sensor
The SNMP HP ProLiant Physical Disk sensor monitors a physical disk in an HP server via Simple
Read and written sectors

Hard and corrected read errors
Hard and corrected write errors
Disk status
Drive condition
Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status
If the threshold is passed
SNMP HP ProLiant Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_proliant_phy sic al_disk.png
1500 02.02.2015
Remarks

Add Sensor
Select the physical disks in the HP server you want to monitor. PRTG creates one sensor for
each disk you choose in the Add Sensor dialog. The settings you make in this dialog are valid
02.02.2015 1501
HP PR OLIANT PHYSICAL DISK SETTINGS
head.
Sensor Settings
priority).
HP PR OLIANT PHYSICAL DISK SETTINGS
Disk Shows the identifier of the disk that this sensor monitors. Once a
the sensor anew.
1502 02.02.2015
SENSOR DISPLAY
for each channel.
2477 settings).
Inherited Settings
described below.
02.02.2015 1503
SCANNING INTER VAL
Choose between:
option will apply.
1504 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1505
menu bar.
dependent on.
1506 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1507
More


Notifications
Others
1508 02.02.2015
125 SNMP HP ProLiant System Health Sensor
6.8.125 SNM P HP ProLiant Sy stem Health Sensor
The SNMP HP ProLiant System Health sensor monitors the system health of an HP ProLiant
server via Simple Network Management Protocol (SNMP).
Overall status
Thermal status
System fan status
CPU fan status
Number of broken and running fans
Number of broken and running fans that are fault tolerant
Status and condition of the power supply
Temperatures for various components of the server, for example, memory, power supply,
CPU, system, and storage.
Power consumption
Disk controller status
These channels are created at run-time, depending on the available measurement components.
sensor setup.
02.02.2015 1509
SNMP HP ProLiant Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_proliant_sy stem_health.png
Remarks
This sensor has predefined limits for temperatures and broken frames. You can change these
limits individually in the channel settings 2477 .
1510 02.02.2015
Note: RAID controllers which have no hard disks assigned might cause a Down status 123 . In
this case, deactivate the respective controller(s) in the HP ProLiant BIOS to avoid sensor
errors.

Add Sensor
Sensor Settings
02.02.2015 1511
priority).
SENSOR DISPLAY
for each channel.
2477 settings).
1512 02.02.2015
Inherited Settings
described below.
02.02.2015 1513
SCANNING INTER VAL
Choose between:
option will apply.
1514 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1515
menu bar.
dependent on.
1516 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1517
More

Knowledge Base: Why is my SNMP HP ProLiant System Health sensor in error status after
updating PRTG?

Notifications
Others
1518 02.02.2015
126 SNMP IBM System X Logical Disk Sensor
6.8.126 SNM P IBM Sy stem X Logical Disk Sensor
The SNMP IBM System X Logical Disk sensor monitors a logical disk in an IBM server via Simple
It shows the status of a logical disk in an IBM server.
SNMP IBM Sy stem X Logic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_ibm_sy stemx_logic al_disk.png
Remarks
Requires 1519 the IBM Systems Director Platform to be installed on the target device.
Knowledge Base: What are the requirements to monitor IBM System x?
Requirement: IBM Systems Director Platform Agent

This sensor type needs the IBM Systems Director Platform Agent to be installed on the target
IBM device in order to monitor it through SNMP. For more information, please see section
More below.
02.02.2015 1519
Add Sensor
Select the logical disks of the IBM device you want to monitor. PRTG creates one sensor for
IBM SYSTEM X LOGICAL DISK SETTINGS
Disk Select the logical disks you want to add a sensor for. You see a list
head.
Sensor Settings
1520 02.02.2015
priority).
IBM SYSTEM X LOGICAL DISK SETTINGS
Disk Shows the ID of the logical disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
02.02.2015 1521
Inherited Settings
described below.
1522 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1523

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1524 02.02.2015
menu bar.
dependent on.
02.02.2015 1525
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1526 02.02.2015
More


Notifications
Others
02.02.2015 1527
127 SNMP IBM System X Physical Disk Sensor
6.8.127 SNM P IBM Sy stem X Phy sical Disk Sensor
The SNMP IBM System X Physical Disk sensor monitors a physical disk in an IBM server via
It shows the status of a physical disk.
SNMP IBM Sy stem X Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_ibm_sy stemx_phy sic al_disk.png
Remarks

More below.
1528 02.02.2015
Add Sensor
Select the physical disks of the IBM device you want to monitor. PRTG creates one sensor for
IBM SYSTEM X PHYSICAL DISK SETTINGS
Disk Select the physical disks you want to add a sensor for. You see a
table head.
Sensor Settings
02.02.2015 1529
priority).
IBM SYSTEM X PHYSICAL DISK SETTINGS
Disk Shows the ID of the physical disk that this sensor monitors. Once
the sensor anew.
SENSOR DISPLAY
for each channel.
1530 02.02.2015
Inherited Settings
described below.
02.02.2015 1531
SCANNING INTER VAL
Choose between:
option will apply.
1532 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1533
menu bar.
dependent on.
1534 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1535
More


Notifications
Others
1536 02.02.2015
128 SNMP IBM System X Physical Memory Sensor
6.8.128 SNM P IBM Sy stem X Phy sical M emory Sensor
The SNMP IBM System X Physical Memory sensor monitors the memory modules in an IBM
server via Simple Network Management Protocol (SNMP).
Condition of memory controller

Power status (on or off)
SNMP IBM Sy stem X Phy sic al Memory Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_ibm_sy stemx_phy sic al_memory .png
Remarks

More below.
02.02.2015 1537
Add Sensor
Select the memory modules of the IBM server you want to monitor. PRTG creates one sensor
for each module you choose in the Add Sensor dialog. The settings you make in this dialog
IBM SYSTEM X PHYSICAL MEMOR Y SETTINGS
Module Select the memory modules you want to add a sensor for. You see
table head.
Sensor Settings
1538 02.02.2015
priority).
IBM SYSTEM X PHYSICAL MEMOR Y SETTINGS
Name
Caption
Shows further information about the module. Once a sensor is
Serial Number purposes only. If you need to change this, please add the sensor
anew.
Size
SENSOR DISPLAY
for each channel.
02.02.2015 1539
Inherited Settings
described below.
1540 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1541

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1542 02.02.2015
menu bar.
dependent on.
02.02.2015 1543
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1544 02.02.2015
More


Notifications
Others
02.02.2015 1545
129 SNMP IBM System X System Health Sensor
6.8.129 SNM P IBM Sy stem X Sy stem Health Sensor
The SNMP IBM System X System Health sensor monitors the system health of an IBM device via
It can show the following, depending on what measurement you select:
Revolutions per minute of fans (or the current percentage of the possible maximum)
Temperature of ambient and CPUs
Voltage of planars
Status of power supplies
These channels are created at run-time, depending on the available measurement components.
sensor setup.
SNMP IBM Sy stem X Sy stem Health Sensor
1546 02.02.2015
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_ibm_sy stemx_sy stem_health.png
Remarks
Note: This sensor can also run directly on an Integrated Management Module (IMM) network
port and can show the overall health on IMMs.
Note: If the IBM device returns a string in an unexpected format for the percentage of fan
revolutions (for example, "offline"), this sensor will show -1% in the corresponding channel.
You can define a Down status 123 for this via channel limits 2478 .

More below.
Note: The SNMP IBM System X System Health sensor can also run directly on an Integrated
Management Module (IMM) network port and can show the overall health on IMMs.
Add Sensor
Select the measurements of the IBM device you want to monitor. PRTG creates one sensor for
each measurement you choose in the Add Sensor dialog. The settings you make in this dialog
02.02.2015 1547
IBM SYSTEM X SYSTEM HEALTH SPECIFIC
Measurement Select the measurements you want to add a sensor for. You see a
table head.
Sensor Settings
priority).
1548 02.02.2015
IBM SYSTEM X SYSTEM HEALTH SPECIFIC
Source Shows the source of the measurement that this sensor monitors.
Measurement Shows the measurement that this sensor monitors. Once a sensor
anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1549
SCANNING INTER VAL
Choose between:
option will apply.
1550 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1551
menu bar.
dependent on.
1552 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1553
More


Notifications
Others
1554 02.02.2015
130 SNMP interSeptor Pro Environment Sensor
6.8.130 SNM P interSeptor Pro Environment Sensor
The SNMP interSeptor Pro Environment sensor queries data from a Jacarta interSeptor Pro
environmental monitoring system via Simple Network Management Protocol (SNMP).
It can shows the following as measured by the Jacarta interSeptor Pro device:
Temperature
Humidity
Remarks
Note: To monitor data of an interSeptor Pro device with this sensor, you have to add the IP
address of your PRTG installation to Access Cont rol in the interSeptor Pro control panel.
Open the interSeptor Pro web interface, select Int erSept or Pro Menu | Sy st em
Configurat ion | Access Cont rol, and allow access for PRTG's IP address.
Add Sensor
Select the measuring points of interSeptor Pro device you want to monitor. PRTG creates one
sensor for each measuring point you choose in the Add Sensor dialog. The settings you make
in this dialog are valid for all of the sensors that are created.
INTER SEPTOR ENVIR ONMENT SPECIFIC
Measuring Point Select the measuring points you want to add a sensor for. You see
table head.
Sensor Settings
02.02.2015 1555
priority).
INTER SEPTOR ENVIR ONMENT SPECIFIC
Name Shows information about the measurement which this sensor

Measuring Point Shows the measuring point which this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
1556 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1557
SCANNING INTER VAL
Choose between:
option will apply.
1558 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1559
menu bar.
dependent on.
1560 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1561
More

Notifications
Others
1562 02.02.2015
131 SNMP LenovoEMC Physical Disk Sensor
6.8.131 SNM P LenovoEM C Phy sical Disk Sensor
The SNMP Lenovo Physical Disk sensor monitors a physical disk in a LenovoEMC Network
Attached Storage (NAS) via Simple Network Management Protocol (SNMP).
It shows the overall disk status.
States of the disk can be:
Normal (sensor status 123 Up),

Unknown (sensor status Warning)
Foreign (sensor status Warning)
Faulted (sensor status Down)
Missing (sensor status Down)
Remarks
Add Sensor
Select the physical disks in the LenovoEMC NAS. PRTG creates one sensor for each disk you
LENOVOEMC PHYSICAL DISK SETTINGS
head.
02.02.2015 1563
Sensor Settings
priority).
LENOVOEMC PHYSICAL DISK SETTINGS
Disk Shows the disk monitored by this sensor. Once a sensor is

anew.
Name Shows the name of the disk monitored by this sensor. Once a
the sensor anew.
Size Shows the size of the disk monitored by this sensor. Once a
the sensor anew.
1564 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1565
SCANNING INTER VAL
Choose between:
option will apply.
1566 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1567
menu bar.
dependent on.
1568 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1569
Others
1570 02.02.2015
132 SNMP LenovoEMC System Health Sensor
6.8.132 SNM P LenovoEM C Sy stem Health Sensor
The SNMP LenovoEMC System Health sensor monitors the system health of a LenovoEMC
Network Attached Storage (NAS) via Simple Network Management Protocol (SNMP).
It shows the overall status of the RAID.
Sensor states 123 can be:
Normal (sensor status Up)

Unknown (sensor status Warning)
Rebuilding (sensor status Warning)
Degraded (sensor status Warning)
RebuildFS (sensor status Warning)
Faulted (sensor status Down)
Furthermore, this sensor can show, for example, states of several fans, voltages, and
temperatures. These channels are created at run-time depending on the available measurement
components in the LenovoEMC NAS. Which channels the sensor actually shows might depend
on the monitored device and the sensor setup.
Remarks
Add Sensor
Sensor Settings
02.02.2015 1571
priority).
SENSOR DISPLAY
for each channel.
1572 02.02.2015
Inherited Settings
described below.
02.02.2015 1573
SCANNING INTER VAL
Choose between:
option will apply.
1574 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1575
menu bar.
dependent on.
1576 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1577
Others
1578 02.02.2015
133 SNMP Library Sensor
6.8.133 SNM P Library Sensor
The SNMP Library sensor monitors a device using Simple Network Management Protocol
(SNMP) in combination with a compiled Management Information Base (MIB) library file. This
provides extended monitoring beyond the standard SNMP sensors of PRTG.
To monitor any SNMP capable device, you can download the manufacturer's MIB files for these
devices, convert them to the Paessler oidlib format, and import them into PRTG. To make your
monitoring setup as convenient as possible, PRTG is delivered with pre-compiled oidlib library
files that already contain the Object Identifier (OID) of SNMP counters for the most common
devices in a network. See section More 1588 for details.
SNMP Library Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_library .png
Remarks
Knowledge Base: How do SNMP, MIBs and OIDs work?
Knowledge Base: How can I import my MIB files into PRTG?
Add Sensor
Manually add 228 a new sensor to an SNMP device. From the Add Sensor dialog, select SNMP
Library sensor. PRTG will show a list of oidlib files available on the system. This contains all
library files stored at the \snmplibs folder of your PRTG installation directoryboth the ones
delivered with PRTG and your own files. For details about directory paths, please see section
Dat a St orage 2871 .
02.02.2015 1579
List of SNMP Library Files
The file names in the list indicate the potential purpose. Select a name that appears appropriate
for your device (for example, choose an MIB file that you imported before) and confirm with
the OK button. Often, Paessler common oid library .oidlib is a good start. If the file does not
fit to your device, this will result in the error message the scan for available monitoring items
has failed on this device: No such object (SNMP error # 222). If you see this message, please
hit the Cancel button and try adding the sensor with another file. If counters were found for
your device, you will see the sensor's settings.
Default OIDLIB Files Overview

The following files are delivered with PRTG and allow to extend your SNMP monitoring for many
devices. Please be aware that not all devices and/or parameters may be supported by the
libraries.
APC UPS.oidlib
Can be used to monitor uninterruptible power supplies (UPS) from APC American Power
Conversion Corp.
APCSensorst at ionlib.oidlib
Can be used to monitor alarm status, communication status, humidity, and temperature as
shown by an APC sensor station.
Basic Linux Library (UCD-SNMP-MIB).oidlib

Can be used to monitor basic system parameters on Linux systems, such as memory, disk
and swap, CPU, etc.
1580 02.02.2015
cisco-int erfaces.oidlib
Can be used to monitor Cisco specific parameters, for example, the number of present
network interfaces on a system, several states of an interface (admin, oper, speed, type,
errors, discards, etc.), and more.
cisco-queue.oidlib
Can be used to monitor queues on a Cisco interface, for example, queue depth and its
maximum, discarded messages from the queue, the number of the queue within the queue
set, etc.
Dell St orage Management .oidlib

Can be used to monitor Dell storage devices. Possible parameters include disk arrays,
battery and power supply, fan and temperature, virtual disk, etc.
Dell Sy st ems Management Inst rument at ion.oidlib

Can be used to monitor the hardware of Dell systems. Possible parameters include ACPower
and battery, alerts, base board, Bios, BMC, chassis, COO, cooling, event log, firmware, IDE,
keyboard, memory, port, network, processor, SCSI, system, temperature, USB, UUID, etc.
HP LaserJet St at us.oidlib
Can be used to monitor toner, paper, and jam status of an HP LaserJet printer.
Linux SNMP (AX BGP DisMan Et herLike Host ).oidlib

Can be used to monitor different aspects of Linux systems. Note: This file can find a very
large number of possible interfaces. It may take a few seconds until the selection table is
shown.
Linux SNMP (Framework Proxy Not i v2).oidlib

shown.
Linux SNMP (IP Net SNMP Not i OSPF RMON SMUX ).oidlib
shown.
Linux SNMP (Source TCP UCD UDP).oidlib

shown.
Paessler Common OID Library .oidlib

Can be used to monitor many common hardware devices. It is used for several sensors and
is encrypted.
SNMP Informant st d.oidlib

Can be used to monitor logical disks, processor, memory, and network interface on
Windows systems.
02.02.2015 1581
Import MIB Files

Additionally you can create your own oidlib files by importing your device manufacturers' MIB
files with the free tool Paessler MIB Import er. Simply convert your mib files and save the
resulting oidlib files to the \snmplibs subfolder of your PRTG program directory. For details
about directory paths, please see Dat a St orage 2871 . For more information and download of
MIB Import er, please see the link in the More 1588 section below.
SNMP Library SensorAdd Sensor Settings

SNMP LIBR AR Y SPECIFIC
Library This shows the path to the oidlib file selected before. This setting
is shown for your information only and cannot be changed here.
Library-OIDs Select the aspects of the device you want to monitor. A list
specific to your setup is shown. It contains all counters found in
the chosen library that match your device. Select one or more
items by adding a check mark in front of the respective line. You
table head. For each selection, PRTG will create one sensor when
you click the Cont inue button.
Sensor Settings
1582 02.02.2015
priority).
SNMP LIBR AR Y SPECIFIC
Selected Interface Shows the counter that this sensor monitors. Once a sensor is
anew.
Unit String Enter a string that represents the unit of the returned values. This
is for display purposes for the sensor data only. Please enter a
string.
Multiplication Enter the multiplier if you want to multiply the received data with a
certain value. Please enter an integer value.
Division Enter the divisor if you want to divide the received data by a
certain value. Please enter an integer value.
change.
02.02.2015 1583
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1584 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1585

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1586 02.02.2015
menu bar.
dependent on.
02.02.2015 1587
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How do SNMP, MIBs and OIDs work?
Knowledge Base: How can I import my MIB files into PRTG?



1588 02.02.2015
Notifications
Others
02.02.2015 1589
134 SNMP Linux Disk Free Sensor
6.8.134 SNM P Linux Disk Free Sensor
The SNMP Linux Disk Free sensor monitors free space on disks of a Linux/Unix system using
Free total disk space in bytes

Free space in bytes for every mounted partition
Free space in percent for every mounted partition
Free inodes in percent for every mounted partition
Note: The free space returned by this sensor type shows the disk space that is not yet used.
Not all of this space may be available for use, as a part of this space can be reserved by the
system, for example, for redundancy purposes. For details, please see the article linked in the
More 1601 section below.
1590 02.02.2015
SNMP Linux Disk Free Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_linux_disk_free.png
Remarks
Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values for
my target Linux system?
Knowledge Base: Checklist: Setting up SNMP on Linux
02.02.2015 1591
Add Sensor
Sensor Settings
priority).
SET LIMITS CHECKED AGAINST ALL DISKS
In this section you can set limits that are valid for all channels and all drives. By entering
limits, you can define when the sensor will enter a Warning or Down status, depending on
the data provided by all drives that this sensor monitors. If you want to define limits for
separate channels individually please use the limit settings in the sensor Channel settings.
Note: All limits that you define here are valid additionally to the limits defined in the
particular Channels settings! The limits are valid simultaneously, so the first limit that is
breached applies.
1592 02.02.2015
Percentage Limit Check Enable or disable a limit check for the free space in percentage
channels of all drives. By default, percentage limits are enabled with
lower warning and lower error limit. Choose between:
Only use t he limit s in t he set t ings of t he percent age
channels: Do not define sensor limits which are valid for all
percentage channels. The sensor only uses limits which you
define in the settings of the particular "free space in percent"
channels to determine the status.
Use t he limit s of bot h t he sensor and t he channel set t ings:
Define limits for the sensor which are valid for all drives
(percentage channels). Additional fields appear below. The
sensor enters a Warning or Down status when free space limits
are undercut or overrun.
Upper Error Limit This field is only visible if you enable percentage limit check above.
Specify an upper limit in percent for a Down status. If the free disk
space of one of your drives overruns this percent value, the
sensor switches to Down. Please enter an integer value or leave
the field empty.
Note: The limits set here are valid for all channels of this sensor.
You can additionally set individual limits for each sensor channel in
the Sensor Channels Set t ings 2477 . The limits set here and in the
channel settings are valid simultaneously!
Upper Warning Limit This field is only visible if you enable percentage limit check above.
Specify an upper limit in percent for a Warning status. If the free
disk space of one of your drives overruns this percent value, the
sensor switches to Warning. Please enter an integer value or leave
the field empty.
Lower Warning Limit This field is only visible if you enable percentage limit check above.
Specify a lower limit in percent for a Warning status. If the free disk
space of one of your drives undercuts this percent value, the
sensor switches to warning. Please enter an integer value or leave
the field empty.
02.02.2015 1593
Lower Error Limit This field is only visible if you enable percentage limit check above.
Specify a lower limit in percent for a Down status. If the free disk
the field empty.
Size Limit Check Enable or disable a limit check for the free bytes channels of all
drives. By default, byte size limits are not enabled for drives.
Choose between:
Only use t he limit s in t he set t ings of t he by t e size channels:
Do not define sensor limits which are valid for all byte size
channels. The sensor only uses limits which you define in the
settings of the particular free space in bytes channels to
determine the status.
Define limits for the sensor which are valid for all drives (byte
size channels). Additional fields appear below. The sensor enters
a Warning or Down status when free space limits are undercut
or overrun.
Upper Error Limit This field is only visible if you enable byte limit check above. Specify
an upper limit. Use the same unit as shown by the free bytes
channels of this sensor (by default this is MByte). If the free disk
space of one of your drives overruns this bytes value, the sensor
switches to Down. Please enter an integer value or leave the field
empty.
Upper Warning Limit This field is only visible if you enable byte limit check above. Specify
switches to Warning. Please enter an integer value or leave the
field empty.
1594 02.02.2015
Lower Warning Limit This field is only visible if you enable byte limit check above. Specify
a lower limit. Use the same unit as shown by the free bytes
space of one of your drives undercuts this bytes value, the sensor
field empty.
Lower Error Limit This field is only visible if you enable byte limit check above. Specify
empty.
Alarm on Missing/ If a monitored disk is removed or not found, values are set to
Removed Disk zero. Select the alarming approach in this case. Choose between:
Deact ivat e alarm (default ): Select this option if you do not
want an alarm for a removed disk.
Act ivat e alarm: Select this option if you want to be alerted if a
monitored disk is removed.
SENSOR DISPLAY
for each channel.
02.02.2015 1595
SENSOR DISPLAY

Inherited Settings
described below.
1596 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1597

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1598 02.02.2015
menu bar.
dependent on.
02.02.2015 1599
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1600 02.02.2015
More



Notifications
Others
02.02.2015 1601
135 SNMP Linux Load Average Sensor
6.8.135 SNM P Linux Load Average Sensor
The SNMP Load Average sensor monitors the system load average of a Linux/Unix system
using Simple Network Management Protocol (SNMP).
Average system load within a 1 minute interval

Average system load within a 5 minutes interval
SNMP Linux Load Av erage Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_linux_load_av erage.png
Remarks
Add Sensor
1602 02.02.2015
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
02.02.2015 1603
SENSOR DISPLAY
Inherited Settings
described below.
1604 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1605

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1606 02.02.2015
menu bar.
dependent on.
02.02.2015 1607
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More


1608 02.02.2015
Notifications
Others
02.02.2015 1609
136 SNMP Linux Meminfo Sensor
6.8.136 SNM P Linux M eminfo Sensor
The SNMP Linux Meminfo sensor monitors the memory usage of a Linux/Unix system using
It shows the following :
Available memory in absolute and percentage values

Used physical memory (free memory plus buffer plus cache) in percent
Free physical memory (free memory plus buffer plus cache) in bytes
Used swap memory in percent
Free swap memory in bytes
Used memory on the whole system (physical memory plus swap) in percent
Free memory on the whole system (physical memory plus swap) in bytes
SNMP LInux Meminfo Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_linux_meminfo.png
1610 02.02.2015
Remarks
Add Sensor
Sensor Settings
priority).
02.02.2015 1611
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1612 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1613

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1614 02.02.2015
menu bar.
dependent on.
02.02.2015 1615
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1616 02.02.2015
More


Notifications
Others
02.02.2015 1617
137 SNMP Linux Physical Disk Sensor
6.8.137 SNM P Linux Phy sical Disk Sensor
The SNMP Linux Physical Disk sensor monitors input/output (I/O) on disks of a Linux/Unix
system using Simple Network Management Protocol (SNMP).
Read bytes per second

Written bytes per second
Number of read accesses per second
Number of write accesses per second
SNMP Linux Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_linux_phy sic al_disk.png
Remarks
Add Sensor
1618 02.02.2015
Select the disks of the Linux/Unix system you want to monitor. PRTG creates one sensor for
PHYSICAL DISK SETTINGS
head.
Sensor Settings
priority).
02.02.2015 1619
PHYSICAL DISK SETTINGS
Disk Shows further information about the disk that this sensor
Bitmask please add the sensor anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1620 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1621

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1622 02.02.2015
menu bar.
dependent on.
02.02.2015 1623
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1624 02.02.2015
More


Notifications
Others
02.02.2015 1625
138 SNMP Memory Sensor
6.8.138 SNM P M emory Sensor
The SNMP Memory sensor monitors the memory usage of a system via Simple Network
Available memory in bytes

Available memory in percent
Total memory
Note: This sensor uses more generic Object Identifier (OID) values compared to the SNMP
Linux Meminfo Sensor 1610 .
SNMP Memory Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_memory .png
Remarks
Add Sensor
1626 02.02.2015
Select the memory types you want to monitor. PRTG creates one sensor for each memory
type you choose in the Add Sensor dialog. The settings you make in this dialog are valid for all
MEMOR Y SETTINGS
Memory Select one or more memory types you want to add a sensor for.
in the table head.
Sensor Settings
priority).
02.02.2015 1627
MEMOR Y SETTINGS
Memory Shows the type of the memory that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1628 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1629

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1630 02.02.2015
menu bar.
dependent on.
02.02.2015 1631
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1632 02.02.2015
More

Notifications
Others
02.02.2015 1633
139 SNMP NetApp Disk Free Sensor
6.8.139 SNM P NetApp Disk Free Sensor
The SNMP NetApp Disk Free sensor monitors free space on disks of a NetApp storage system
Free disk space in bytes and percent

Deduplication saved space in bytes and percent
Deduplication shared space in bytes and percent
Disk free status
Free files in percent
Free INodes in percent
SNMP NetApp Disk Free Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_disk_free.png
1634 02.02.2015
Remarks
Knowledge Base: How can I monitor capacity and used disk space on a NetApp?
Add Sensor
Select the disk on the NetApp you want to monitor. PRTG creates one sensor for each disk
NETAPP DISK FR EE SETTINGS
File System Select the disks you want to add a sensor for. You see a list with
head.
Sensor Settings
02.02.2015 1635
priority).
File System Shows the name of the disk that this sensor is monitoring. Once a
the sensor anew.
Virtual Disk Shows the name of the virtual disk that this sensor is monitoring (if
applicable). Once a sensor is created, you cannot change this
SENSOR DISPLAY
for each channel.
1636 02.02.2015
SENSOR DISPLAY
2477 settings).
Inherited Settings
described below.
02.02.2015 1637
SCANNING INTER VAL
Choose between:
option will apply.
1638 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1639
menu bar.
dependent on.
1640 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1641
More
Knowledge Base: How can I monitor capacity and used disk space on a NetApp?


Notifications
Others
1642 02.02.2015
140 SNMP NetApp Enclosure Sensor
6.8.140 SNM P NetApp Enclosure Sensor
The SNMP NetApp Enclosure sensor monitors the power supply and cooling of an enclosure
that is part of a NetApp storage system via Simple Network Management Protocol (SNMP).
It can show the following, depending on the measurements you choose:
Temperatures
Rotations per minute (RPM) of fans and the number of failed fans
Voltages in mV, the number of broken electronic parts, and the number of broken power
supplies
Currents in mA
SNMP NetApp Enc losure Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_enc losure.png
02.02.2015 1643
Remarks
Add Sensor
Select the power supply and cooling measurements of an enclosure on a NetApp you want to
monitor. PRTG creates one sensor for each enclosure/measurement combination you choose
that are created.
NETAPP ENCLOSU R E SETTINGS
Enclosure Select the enclosures with the desired measurement you want to
add a sensor for. You see a list with the names of all items which
are available to monitor. Select the desired items by adding check
Sensor Settings
1644 02.02.2015
priority).
NETAPP ENCLOSU R E SETTINGS
Enclosure Shows the identifier of the enclosure that this sensor is

monitoring. Once a sensor is created, you cannot change this
Measurement Shows the monitored measurement. Once a sensor is created, you

02.02.2015 1645
NETAPP SPECIFIC
N/A Measurements Define the sensor behavior if the requested NetApp value is not
available ("N/A" values). Choose between:
Int erpret as error (default ): Choose this option to set the
sensor to a Down status if a measurement is not available. We
recommend you to use this setting to not miss any hardware
errors.
Int erpret as valid: Choose this option to handle unavailable
measurements as valid sensor results to keep the sensor in Up
status. This might be useful, for example, if a hardware sensor on
the NetApp is disabled for some reason but actually there is no
hardware error. If the NetApp returns an "N/A" measurement, the
sensor interprets this as "0".
We recommend you to use the lookup file
prt g.st andardlookups.net app.not available.ovl for channels
with unavailable measurements if you choose this option. This
replaces "0" with the message "Not Available". Open the Sensor
Channels Set t ings 2477 of the affected channel(s) and choose this
file in section Value Lookup. For details, please see section
Define Lookups 2838 .
SENSOR DISPLAY
for each channel.
2477 settings).
1646 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1647
SCANNING INTER VAL
Choose between:
option will apply.
1648 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1649
menu bar.
dependent on.
1650 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1651
More

Notifications
Others
1652 02.02.2015
141 SNMP NetApp I/O Sensor
6.8.141 SNM P NetApp I/O Sensor
The SNMP NetApp I/O sensor monitors input/output operations (IOPS) on a NetApp storage
system via Simple Network Management Protocol (SNMP).
FCP read speed

CIFS operations per second
Disk read speed
Disk write speed
FCP operations per second
FCP read speed
FCP write speed
HTTP operations per second
ISCSI operations per second
ISCSI read speed
ISCSI write speed
Network received bytes
Network sent bytes
NFS operations per second
Tape read speed
Tape write speed
02.02.2015 1653
SNMP NetApp I/O Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_io.png
Remarks
Add Sensor
1654 02.02.2015
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
02.02.2015 1655
SENSOR DISPLAY
2477 settings).
Inherited Settings
described below.
1656 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1657

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1658 02.02.2015
menu bar.
dependent on.
02.02.2015 1659
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1660 02.02.2015
More

Notifications
Others
02.02.2015 1661
142 SNMP NetApp License Sensor
6.8.142 SNM P NetApp License Sensor
The SNMP NetApp License sensor monitors the licenses for the services of a NetApp storage
It shows how much time is left until the license for a service expires. This can help you to
detect when a timely limited NetApp license is going to expire.
SNMP NetApp Lic ense Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_lic ense.png
Remarks
Add Sensor
Select the NetApp license you want to monitor. PRTG creates one sensor for each license you
1662 02.02.2015
NETAPP LICENSE SETTINGS
License for Service Select the licenses you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
NETAPP LICENSE SETTINGS
License for Service Shows the name of the service whose license this sensor
02.02.2015 1663
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1664 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1665

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1666 02.02.2015
menu bar.
dependent on.
02.02.2015 1667
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1668 02.02.2015
More

Notifications
Others
02.02.2015 1669
143 SNMP NetApp Logical Unit Sensor
6.8.143 SNM P NetApp Logical Unit Sensor
The SNMP NetApp Logical Unit sensor monitors the input/output operations (IOPS) on a logical
unit of a NetApp storage system via Simple Network Management Protocol (SNMP).
Total number of operations per second

Data read speed
Data write speed
Number of errors per second
Number of read operations per second
Number of write operations per second
Number of other operations per second
Status of the logical unit (online or offline)
SNMP NetApp Logic al Unit Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_logic al_unit.png
1670 02.02.2015
Remarks
Add Sensor
Select the logical units on the NetApp you want to monitor. PRTG creates one sensor for each
unit you choose in the Add Sensor dialog. The settings you make in this dialog are valid for all
Logical Unit Select the logical units you want to add a sensor for. You see a list
head.
Sensor Settings
02.02.2015 1671
priority).
Logical Unit Shows the name of the logical unit that this sensor monitors. Once
the sensor anew.
SENSOR DISPLAY
for each channel.
1672 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1673
SCANNING INTER VAL
Choose between:
option will apply.
1674 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1675
menu bar.
dependent on.
1676 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1677
More

Notifications
Others
1678 02.02.2015
144 SNMP NetApp Network Interface Sensor
6.8.144 SNM P NetApp Network Interface Sensor
The SNMP NetApp Network Interface sensor monitors a network card of a NetApp storage
Traffic in
Traffic out
Number of errors per second (in and out).
SNMP NetApp Network Interfac e Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_network_interfac e.png
Remarks
Add Sensor
02.02.2015 1679
Select the network interfaces on the NetApp you want to monitor. PRTG creates one sensor
for each interface you choose in the Add Sensor dialog. The settings you make in this dialog
NETAPP NETWOR K INTER FACE SETTINGS
Network Interface Select the interfaces you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
1680 02.02.2015
NETAPP NETWOR K INTER FACE SETTINGS
Network Interface Shows the name of the interface that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
2477 settings).
Inherited Settings
described below.
02.02.2015 1681
SCANNING INTER VAL
Choose between:
option will apply.
1682 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1683
menu bar.
dependent on.
1684 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1685
More

Notifications
Others
1686 02.02.2015
145 SNMP NetApp System Health Sensor
6.8.145 SNM P NetApp Sy stem Health Sensor
The SNMP NetApp System Health sensor monitors the status of a NetApp storage system via
CPU load in percent

Number of active restores
Number of current CIFS users
Number of active disks
Number of disks being added
Number of disks being scrubbed
Number of failed disks
Number of soon failing disks
Number of disks being out of date
Number of reconstructing (parity) disks
Number of spare disks
Total number of disks
Number of verifying (parity) disks
Number of failed fans
Number of failed power supplies
Maximum used disk space in percent
Maximum used INodes in percent
If the environment is over temperature
sensor setup.
02.02.2015 1687
SNMP NetApp Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_sy stem_health.png
Remarks
1688 02.02.2015
Add Sensor
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
02.02.2015 1689
SENSOR DISPLAY

2477 settings).
Inherited Settings
described below.
1690 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1691

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1692 02.02.2015
menu bar.
dependent on.
02.02.2015 1693
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1694 02.02.2015
More

Notifications
Others
02.02.2015 1695
146 SNMP Poseidon Environment Sensor
6.8.146 SNM P Poseidon Environment Sensor
The SNMP Poseidon Environment sensor monitors performance counters for environmental
measurements on Poseidon hardware via Simple Network Management Protocol (SNMP).
It can show, depending on available measurement components on the hardware device and
what measurement you choose:
Humidity
Temperature
sensor setup.
SNMP Poseidon Env ironment Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_poseidon_env ironment.png
Remarks
Add Sensor
1696 02.02.2015
In order to monitor performance counters for environmental measurements on Poseidon

hardware, PRTG will create one sensor for each measuring point you choose. The settings you
make in this dialog are valid for all of the sensors that are created.
POSEIDON ENVIR ONMENT SPECIFIC
Measuring Point Select the measurements you want to add a sensor for. You see a
table head.
Sensor Settings
priority).
02.02.2015 1697
POSEIDON ENVIR ONMENT SPECIFIC
Name
Shows further information about the measurement. Once a sensor
Unit is created, you cannot change this value. It is shown for reference
Measuring Point anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1698 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1699

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1700 02.02.2015
menu bar.
dependent on.
02.02.2015 1701
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1702 02.02.2015
Others
02.02.2015 1703
147 SNMP Printer Sensor
6.8.147 SNM P Printer Sensor
The SNMP Printer sensor is a generic sensor which monitors various types of printers via
Total number of printed pages

Fill level of cartridges and toners
Status of the printer cover
Additionally, the sensor shows the printer status as sensor message.
SNMP Printer Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_printer.png
Remarks
This sensor type supports the following printers, among others: HP OfficeJet printers, HP
LaserJet printers, RICOH SP 5200, SP 3410, SP C242DN, MP C3003, MP C2503
1704 02.02.2015
Add Sensor
Sensor Settings
priority).
02.02.2015 1705
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1706 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1707

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1708 02.02.2015
menu bar.
dependent on.
02.02.2015 1709
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1710 02.02.2015
Others
02.02.2015 1711
148 SNMP QNAP Logical Disk Sensor
6.8.148 SNM P QNAP Logical Disk Sensor
The SNMP QNAP Logical Disk sensor monitors a logical disk in a QNAP Network Attached
Storage (NAS) via Simple Network Management Protocol (SNMP).

Free disk space in bytes
Status of the volume
SNMP QNAP Logic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_qnap_logic al_disk.png
Remarks
Add Sensor
1712 02.02.2015
Select the logical disks in the QNAP NAS you want to monitor. PRTG creates one sensor for
QNAP NAS SETTINGS
head.
Sensor Settings
priority).
02.02.2015 1713
QNAP NAS SETTINGS
Disk
Shows further information about the disk that this sensor
Description monitors. Once a sensor is created, you cannot change this value.
File System please add the sensor anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1714 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1715

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1716 02.02.2015
menu bar.
dependent on.
02.02.2015 1717
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1718 02.02.2015
Others
02.02.2015 1719
149 SNMP QNAP Physical Disk Sensor
6.8.149 SNM P QNAP Phy sical Disk Sensor
The SNMP QNAP Physical Disk sensor monitors a physical disk in a QNAP Network Attached
Temperature
Disk status
Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status of the disk.
SNMP QNAP Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_qnap_phy sic al_disk.png
Remarks
Add Sensor
1720 02.02.2015
Select the physical disks in the QNAP NAS you want to monitor. PRTG creates one sensor for
each disk you choose in the Add Sensor dialog. You can also define the unit of the
temperature measurement. The settings you make in this dialog are valid for all of the sensors
that are created.
QNAP NAS SETTINGS
table head.
Unit Select the unit of the temperature measurement. Choose

between Celsius and Fahrenheit .
Sensor Settings
02.02.2015 1721
priority).
QNAP NAS SETTINGS
Disk
Description
Model Shows further information about the disk. Once a sensor is

Capacity purposes only. If you need to change this, please add the sensor
anew.
Unit
SENSOR DISPLAY
for each channel.
1722 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1723
SCANNING INTER VAL
Choose between:
option will apply.
1724 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1725
menu bar.
dependent on.
1726 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1727
Others
1728 02.02.2015
150 SNMP QNAP System Health Sensor
6.8.150 SNM P QNAP Sy stem Health Sensor
The SNMP QNAP System Health sensor monitors the system health of a QNAP Network
It can show the following, depending on the available measurement components:
CPU usage in percent

Temperature of CPU
Temperature of system
Revolutions of fans per minute (RPM)
sensor setup.
SNMP QNAP Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_qnap_sy stem_health.png
Remarks
02.02.2015 1729
Add Sensor
To monitor the system health of a QNAP NAS, specify the unit of the temperature
measurement.
QNAP NAS SETTINGS

Sensor Settings
priority).
1730 02.02.2015
QNAP NAS SETTINGS
Unit Shows the unit of temperatures as monitored with this sensor.

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1731
SCANNING INTER VAL
Choose between:
option will apply.
1732 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1733
menu bar.
dependent on.
1734 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1735
Others
1736 02.02.2015
151 SNMP RMON Sensor
6.8.151 SNM P RM ON Sensor
The SNMP RMON sensor monitors traffic on a device using the Remote Monitoring (RMON)
standard via Simple Network Management Protocol (SNMP). You can create it on an SNMP
compatible device that provides traffic data via RMON. Depending on the data returned by your
device, traffic data for each port can be displayed in different channels, allowing detailed
analysis.
For each port, the sensor can show, for example:
Transmitted kbit/s
Packets (#/s)
Broadcast Packets (#/s)
Multicast Packets (#/s)
CRC Errors (#/s)
Undersize Packets (#/s)
Oversize Packets (#/s)
Fragments (#/s)
Jabbers (#/s)
Collisions (#/s)
Packets <= 64 Byte (#/s)
Packets 65 - 127 Bytes (#/s)
Drop Events (#/s)
sensor setup.
02.02.2015 1737
SNMP RMON Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_rmon.png
Remarks
Note: You can define the displayed sensor name with port name templates in the SNMP
Compat ibilit y Opt ions 299 of the parent device.
Knowledge Base: What value does the "Transmitted" channel of an RMON sensor show?
1738 02.02.2015
Knowledge Base: How do PRTG's automatic port name and number updates work for SNMP
traffic sensors?
Add Sensor
Select the ports you want to monitor. PRTG creates one sensor for each port you choose in
are created.
R MON SPECIFIC
Ports Select the ports you want to add a sensor for. You see a list with
head.
Sensor Settings
02.02.2015 1739
priority).
R MON SPECIFIC
Port Shows the number of the interface port in your physical device
that this sensor monitors. Once a sensor is created, you cannot
Channel Mask Describes which channels are available and might be useful for
technical support. This setting is shown for your information only
and cannot be changed here.
SENSOR DISPLAY
for each channel.
1740 02.02.2015
SENSOR DISPLAY
2477 settings).
Inherited Settings
described below.
02.02.2015 1741
SCANNING INTER VAL
Choose between:
option will apply.
1742 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1743
menu bar.
dependent on.
1744 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1745
More
Knowledge Base: What value does the "Transmitted" channel of an RMON sensor show?
traffic sensors?



Notifications
Others
1746 02.02.2015
152 SNMP SonicWALL System Health Sensor
6.8.152 SNM P SonicWALL Sy stem Health Sensor
The SNMP SonicWALL System Health sensor monitors health values of a Dell SonicWALL
Network Security Appliance (NSA) via Simple Network Management Protocol (SNMP).

Memory usage in percent
Connection cache usage in percent
SNMP Sonic WALL Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sonic wall_sy stem_health.png
Remarks
Knowledge Base: Why does PRTG write error messages into my SonicWALL log?
Add Sensor
02.02.2015 1747
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
1748 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1749
SCANNING INTER VAL
Choose between:
option will apply.
1750 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1751
menu bar.
dependent on.
1752 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1753
More

Notifications
Others
1754 02.02.2015
153 SNMP SonicWALL VPN Traffic Sensor
6.8.153 SNM P SonicWALL VPN Traffic Sensor
The SNMP SonicWALL VPN Traffic sensor monitors the traffic of an Internet Protocol Security
(IPsec) Virtual Private Network (VPN) on a Dell SonicWALL Network Security Appliance (NSA) via
Number of encrypted and decrypted packets per second

Bytes of encrypted and decrypted transmissions per second
Number of in- and outgoing fragmented packets per second
SNMP Sonic WALL VPN Traffic Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sonic wall_v pn_traffic .png
Remarks
02.02.2015 1755
Add Sensor
Select the connections of the SonicWALL VPN you want to monitor. PRTG creates one sensor
for each connection you choose in the Add Sensor dialog. The settings you make in this
SONICWALL VPN SPECIFIC
Connections Select the connections you want to add a sensor for. You see a
table head.
Identification Method Select the criteria to use for connection identification. PRTG always
uses the first connection found that matches all criteria. Choose
between:
By Index: Every connection has a unique index. This is the safest
method to identify your connection. Though, if the connection is
lost and reconnected, a new index will be assigned.
By Remot e IP: If the target of the VPN has always the same IP,
you can use this IP to identify the connection.
By Securit y Policy Name: If you use a different Security Policy
for every VPN, you can use its name to identify the connection.
By Remot e IP and Securit y Policy Name: You can also combine
both identification methods.
Sensor Settings
1756 02.02.2015
priority).
SONICWALL VPN SPECIFIC
Security Policy Shows further information about the monitored connection. Once
Remote IP
the sensor anew.
Index
Identification Method
SENSOR DISPLAY
for each channel.
02.02.2015 1757
SENSOR DISPLAY

Inherited Settings
described below.
1758 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1759

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1760 02.02.2015
menu bar.
dependent on.
02.02.2015 1761
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1762 02.02.2015
More

Notifications
Others
02.02.2015 1763
154 SNMP Synology Logical Disk Sensor
6.8.154 SNM P Sy nology Logical Disk Sensor
The SNMP Synology Logical Disk sensor monitors a logical disk in a Synology Network
It can show the status of a volume.
SNMP Sy nology Logic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sy nology _logic al_disk.png
Remarks
Add Sensor
Select the logical disks in the Synology NAS. PRTG creates one sensor for each disk you
1764 02.02.2015
SYNOLOGY NAS SETTINGS
head.
Sensor Settings
priority).
Disk
Name It is shown for reference purposes only. If you need to change
02.02.2015 1765
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1766 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1767

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1768 02.02.2015
menu bar.
dependent on.
02.02.2015 1769
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1770 02.02.2015
Others
02.02.2015 1771
155 SNMP Synology Physical Disk Sensor
6.8.155 SNM P Sy nology Phy sical Disk Sensor
The SNMP Physical Disk sensor monitors a physical disk in a Synology Network Attached
Temperature
Disk status
SNMP Sy nology Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sy nology _phy sic al_disk.png
Remarks
Add Sensor
Select the physical disks in the Synology NAS you want to monitor. PRTG creates one sensor
for each disk you choose in the Add Sensor dialog. The settings you make in this dialog are
1772 02.02.2015
table head.
Sensor Settings
priority).
02.02.2015 1773
Disk
Name
Model It is shown for reference purposes only. If you need to change
Type
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1774 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1775

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1776 02.02.2015
menu bar.
dependent on.
02.02.2015 1777
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
1778 02.02.2015
Others
02.02.2015 1779
156 SNMP Synology System Health Sensor
6.8.156 SNM P Sy nology Sy stem Health Sensor
The SNMP Synology System Health sensor monitors the system health of a Synology Network
It can show the following, depending on the available measurement components:
Temperature
System status
Power status
Fan status
Memory usage in percent
CPU load in percent
sensor setup.
SNMP Sy nology Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sy nology _sy stem_health.png
1780 02.02.2015
Remarks
Add Sensor
To monitor the system health of a Synology NAS, please specify the unit of the temperature
measurement.

Sensor Settings
02.02.2015 1781
priority).
Unit Shows the unit of temperatures which this sensor monitors. Once
the sensor anew.
SENSOR DISPLAY
for each channel.
1782 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1783
SCANNING INTER VAL
Choose between:
option will apply.
1784 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1785
menu bar.
dependent on.
1786 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1787
Others
1788 02.02.2015
157 SNMP System Uptime Sensor
6.8.157 SNM P Sy stem Uptime Sensor
The SNMP System Uptime sensor monitors the time a device is running via Simple Network
It reads the system uptime value of the monitored device and shows it.
SNMP Sy stem Uptime Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sy stem_uptime.png
Remarks
Knowledge Base: Why does the SNMP System Uptime sensor report wrong values?
Add Sensor
Sensor Settings
02.02.2015 1789
priority).
SENSOR DISPLAY
for each channel.
1790 02.02.2015
Inherited Settings
described below.
02.02.2015 1791
SCANNING INTER VAL
Choose between:
option will apply.
1792 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1793
menu bar.
dependent on.
1794 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: Why does the SNMP System Uptime sensor report wrong values?


02.02.2015 1795
Notifications
Others
1796 02.02.2015
158 SNMP Traffic Sensor
6.8.158 SNM P Traffic Sensor
The SNMP Traffic sensor monitors traffic on a device using Simple Network Management
Protocol (SNMP). You can create it on a device that provides traffic data, one traffic sensor for
each individual port.
Traffic in
Traffic out
Traffic total
You can also add additional channels:
Errors in and out

Discards in and out
Unicast packets in and out
Non unicast packets in and out
Multicast packets in and out
Broadcast packets in and out
Unknown protocols
02.02.2015 1797
SNMP Traffic Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_traffic .png
Remarks
You can define the displayed sensor name with port name templates in the SNMP
Compat ibilit y Opt ions 299 of the parent device.
traffic sensors?
1798 02.02.2015
Add Sensor
Select the ports on SNMP devices with multiple interfaces you want to monitor. PRTG creates
one sensor for each port you choose in the Add Sensor dialog. The settings you make in this
TR AFFIC SPECIFIC
Interface Number You see a list with the names of all items which are available to
in the table head. You can see the connection status of an
interface in the respective table column.
Note: You can group-select and -unselect interfaces by using the
buttons Select all connect ed int erfaces, Select all
disconnect ed int erfaces, and Deselect all int erfaces.
Description "IN" For the standard channel "Traffic In", enter the channel name here.
Channel The sensor shows it in graphs and tables. You can change this
description and the description of all other channels in the sensor
channel settings 2477 later.
Description "OUT" For the standard channel "Traffic Out", enter the channel name
Channel here. The sensor shows it in graphs and tables. You can change
this description and the description of all other channels in the
sensor channel settings 2477 later.
Description "TOTAL" For the standard channel "Traffic Total" enter the channel name
Channel here. The sensor shows it in graphs and tables. You can change
this description and the description of all other channels in the
sensor channel settings 2477 later.
Sensor Settings
02.02.2015 1799
priority).
1800 02.02.2015
TR AFFIC SPECIFIC
Interface Number Shows the number and name of the interface in your physical
device that this sensor monitors. Once a sensor is created, you
Additional Channels By default, the channels "Traffic In", "Traffic Out", and "Traffic Total"
are created for each SNMP Traffic sensor. Choose additional
channels for all selected interfaces. Click on the respective channel
name(s) to mark them and monitor their data.
You can choose from the following additional channels:
Errors In & Out : The number of in-/outbound packets that could
not be delivered because of errors.
Discards In & Out : The number of discarded in-/outbound
packets even though no errors had been detected.
Unicast Packet s In & Out : The number of unicast packets that
were delivered.
Non Unicast Packet s In & Out (32-bit only ): The number of
non-unicast packets that were delivered.
Mult icast Packet s In & Out (64-bit only ): The number of
delivered packets which were addressed to a multicast address.
Broadcast Packet s In & Out (64-bit only ): The number of
delivered packets which were addressed to a broadcast address
Unknown Prot ocols: The number of received packets which
were discarded because of an unknown or unsupported
protocol.
Channels that are once created cannot be deleted later. You can
disable them only.
Connection Status Define how PRTG will react when an interface is operational. A
Handling interface which is not operational is, for example, an ethernet port
on a switch with no cable plugged in. This setting is valid for all
interfaces selected above. You can choose between:
Show alarm for all "disconnect ed" st at es: The sensor for the
interface will always turn into a red error status for a
disconnected interface. This applies if the ifOperStatus of the
interface is not "up".
Show alarm when disconnect ed, but ignore when
deact ivat ed: The sensor will go into an error status for a
disconnected interface only if it is not deliberately deactivated in
the configuration. This applies if the ifOperStatus of the interface
is not "up" and the ifAdminStatus is "up". So the sensor will keep
the Up status when the interface has been deactivated.
Ignore all "disconnect ed" st at es: The sensor will not show an
alarm and its status remains green. Monitoring will be
discontinued without notice.
02.02.2015 1801
SENSOR DISPLAY
for each channel.
2477 settings).
Inherited Settings
described below.
1802 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1803

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1804 02.02.2015
menu bar.
dependent on.
02.02.2015 1805
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1806 02.02.2015
More
traffic sensors?



Notifications
Others
02.02.2015 1807
159 SNMP Trap Receiver Sensor
6.8.159 SNM P Trap Receiver Sensor
The SNMP Trap Receiver sensor receives and analyzes Simple Network Management Protocol
(SNMP) traps.
Overall number of received traps per second

Trap messages categorized as "warning" per second
Trap messages categorized as "error" per second
Number of dropped packets per second
The actual trap messages
SNMP Trap Rec eiv er Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_trap_rec eiv er.png
Remarks
With the available filter options, you can define individually which types of messages will be
considered for monitoring, and which messages will be recognized as warning or error
messages. Depending on the filters, received messages will be counted in the respective
channels.
1808 11.02.2015
You can add the sensor to the probe device on the one hand; then the sensor will receive all
messages of the system running the probe. Alternatively, you can add the sensor to a
specific device to gain all messages from this device directly; this will make this sensor type
faster than just using source filters.
You can use trap specific placeholders in email notification templates 2597 to see the
messages when you receive an email notification. See the Knowledge Base: What
placeholders can I use with PRTG?
You can copy the Management Information Base (MIB) file for your traps into the \MIB
subfolder of your PRTG installation 2871 . PRTG will then be able to translate the OIDs for the
traps into readable messages. For example, instead of the Object Identifier (OID)
1.3.6.1.4.1.32446.1.1.2 you would see SNMPv2-SMI-v1::enterprises.32446.1.1.2 = 0 (example
from the PRTG MIB).
Note: If you do not add the sensor to a probe device but to another device in PRTG, be
careful with the configuration: Ensure that the IP address or DNS name of the parent device
matches the proper trap sender. For example, if you want to receive traps from a Storage
Area Network (SAN), you might have to add a device to PRTG using the IP address of a
specific array member that sends the messages. Providing a DNS name that points to the IP
address of a whole group might not work for SANs.
Knowledge Base: How do I test an SNMP Trap Receiver Sensor?
For a general introduction to the SNMP trap receiver's configuration, please see manual
section Monit oring Sy slogs and SNMP Traps 2784 .
Add Sensor
Sensor Settings
11.02.2015 1809
priority).
SNMP TR AP SPECIFIC
Listen on Port Enter the port the sensor will listen on for SNMP traps. Usually
port 162 is used. Please enter an integer value. We recommend
Purge Messages After Define how long received trap messages will be stored for
analysis. Choose a period of time from the drop down list.
FILTER
Include Filter Define if you want to filter traps. If you leave this field empty or use
the keyword "any", all data will be processed. To include specific
types of traps only, define filters using a special syntax. For more
information, see section Filt er Rules 1817 .
Exclude Filter Define which types of traps will be discarded and not processed.
To exclude specific types of traps, define filters using a special
syntax. For more information, see section Filt er Rules 1817 .
Warning Filter Define which types of traps will count for the Warnings channel.
To categorize received traps as warning messages, define filters
using a special syntax. For more information, see section Filt er
Rules 1817 .
1810 11.02.2015
FILTER
Note: Messages are collected until a scanning interval ends; as

long as the scanning interval is running, no status change will
happen. By default, the sensor will turn into a Warning status after
a scanning interval has finished and there was at least one warning
message (and no error message) during this interval. The status will
remain Warning at least until the succeeding scanning interval has
finished. If in this scanning interval no warning or error message
occurred, the status of the sensor will turn Up again after the
interval.
Error Filter Define which types of traps will count for the Errors channel. To
categorize received traps as error messages, define filters using a
special syntax. For more information, see section Filt er Rules 1817 .
happen. By default, the sensor will turn into a Down status after a
scanning interval has finished and there was at least one error
message during this interval. The status will remain Down at least
until the succeeding scanning interval has finished. If in this
scanning interval no warning or error message occurred, the status
of the sensor will turn Up again after the interval.
SENSOR DISPLAY
for each channel.
11.02.2015 1811
SENSOR DISPLAY
Inherited Settings
described below.
1812 11.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
11.02.2015 1813

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1814 11.02.2015
menu bar.
dependent on.
11.02.2015 1815
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1816 11.02.2015
DEBU GGING
Log Data to Disk Define if the probe will write a log file of the received data to the
data folder (see Dat a St orage 2871 ) to the disk for debugging
purposes. Choose between:
Off (recommended): Do not write additional log files.
On: Write log files for all data received.
only.
Filter Rules for Traps

Filter rules are used for the include, exclude, warning, and error definition fields of the Trap
Receiver sensor. They are based on the following format:
field[filter]
You can use various filters suitable to your needs. Include and exclude filters define which
traps will be monitored; warning and error filters define how received traps will be categorized.
Provide these filters in the sensor settings as formulas. Formulas are fields which can be
combined with boolean operators (AND, OR, NOT) and brackets.
Field Paramet er Examples
source[ip] Enter an IP address where the UDPs come from; IP source[10.0.23.50],

masks and ranges 2837 are also possible. source[10.0.23.10-50],
source[10.0.23.10/255]
agent [ip] Enter an IP address which specifies the object that agent[10.0.0.1]
creates the SNMP trap. Only v1 is supported.
ent erprise Enter an OID which specifies the object that enterprise
[oid] originates the trap. Only v1 is supported. [1.3.6.1.4.1.2.6.182.1.2.3
1.1.0]
bindings Enter a substring to match all OIDs and values in the bindings[ERROR],
[text] bindings. bindings
[1.3.6.1.4.1.2.6.182.1.2.3
1.1.0]
bindings Enter an OID and a substring to match a value in the bindings
[oid,value] given OID. Separate OID and value with a comma. [1.3.6.1.4.1.2.6.182.1.2.3
1.1.0,error]
gent rap Enter a number which specifies the generic trap gentrap[3], gentrap[2-6]
[number] type. Ranges are also possible.
11.02.2015 1817
spect rap Enter a number which defines the specific trap spectrap[4], spectrap[0-3]
[number] code. Ranges are also possible.
version Enter a number (1 or 2) which specifies the SNMP version[1], version[2]
[number] version.
communit y Enter a community string for exact, case sensitive community[public],
[text] match. community[private]
Messages Tab: Review and Analyze Traps

Received traps are stored as common files in PRTG's data folder (see section Dat a St orage 2871
). In order to review and analyze all received messages, you can access the most recent data
directly in PRTG's web interface via the respective sensors on the Overview tab in a table list
157 . Note: Received traps are only shown after an (automatic) page refresh following to a
sensor scan in the table on the Overview tab (default for auto refresh 2587 is 30 seconds).
For more details and further filter options, click on the Messages tab of the SNMP Trap
Receiver sensor. You will see all received messages in a table list 157 . On the top, you have
display filter options to drill down into the data for specific events of your interest. The filters
are the same as available in the sensor settings, but you can define them without using
formulas. Provide the desired parameters and PRTG will load the filtered list automatically. Note:
You can automatically add a filter by clicking on the content of a column.
Advanced Filt er Set t ings
You can open advanced filter settings with a click on the gear icon in the Filt er row. The
Advanced Filt er will appear in a popup window. In the text field, you can define a filter using
the syntax as given in section Filt er Rules for Traps 1817 . If you have provided filter parameters
on the Messages tab, these will be already included in the advanced filter as a corresponding
formula with the correct syntax. You can adjust this filter to your needs. You can also copy the
automatically created and manually adjusted formula for usage in the filter fields of the sensor
settings.
More
Blog Article: Introducing the New High Performance Syslog and SNMP Trap Receiver Sensors
http://www.paessler.com/blog/2013/10/11/prtg/introducing-the-new-high-performance-
syslog-and-snmp-trap-receiver-sensors
Knowledge Base: How do I test an SNMP Trap Receiver Sensor?

Knowledge Base: What placeholders can I use with PRTG?

1818 11.02.2015

Notifications
Others
11.02.2015 1819
160 SNMP Windows Service Sensor
6.8.160 SNM P Windows Service Sensor
The SNMP Windows Service sensor monitors a Windows service via Simple Network
It shows the operating status of the monitored service.
Operating states can be:
Active (sensor status 123 Up)

Continue-Pending
Pause-Pending
Paused (all with sensor status Down)
SNMP Windows Serv ic e
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_windows_serv ic e.png
Remarks
This sensor type cannot distinguish the status "not installed" from "not running".
1820 02.02.2015
Add Sensor
Select the Windows services you want to monitor. PRTG creates one sensor for each service
SNMP WINDOWS SER VICE MONITOR
Service Select the services you want to add a sensor for. You see a list
head.
Sensor Settings
02.02.2015 1821
priority).
SNMP WINDOWS SER VICE MONITOR
Service Shows the Windows service that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
1822 02.02.2015
Inherited Settings
described below.
02.02.2015 1823
SCANNING INTER VAL
Choose between:
option will apply.
1824 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1825
menu bar.
dependent on.
1826 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 1827
161 SNTP Sensor
6.8.161 SNTP Sensor
The SNTP Sensor monitors a Simple Network Time Protocol (SNTP) server.
Response time of the server

Time difference in comparison to the local system time
The sensor tries to get a valid timestamp from the server up to three times per scan until it
reports an error.
SNTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sntp.png
Add Sensor
Sensor Settings
1828 02.02.2015
161 SNTP Sensor
priority).
SENSOR SPECIFC
SENSOR DISPLAY
for each channel.
02.02.2015 1829
161 SNTP Sensor
SENSOR DISPLAY

Inherited Settings
described below.
1830 02.02.2015
161 SNTP Sensor
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1831
161 SNTP Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1832 02.02.2015
161 SNTP Sensor
menu bar.
dependent on.
02.02.2015 1833
161 SNTP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
1834 02.02.2015
162 SSH Disk Free Sensor
6.8.162 SSH Disk Free Sensor
The SSH Disk Free sensor monitors free space on disks of a Linux/Unix system using Secure
Shell (SSH).
Free disk space in bytes for every mounted partition

Free disk space in percent for every mounted partition
Total disk space
Note: The free space returned by this sensor type shows the available disk space of the
volume, minus a reserve defined for this volume (for example, for redundancy purposes). So,
this sensor shows the disk space that is actually available for use. The size of the reserved
disk space can be defined with tune2fs. For details, please see the More 1846 section below.
SSH Disk Free Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_disk_free.png
02.02.2015 1835
Remarks
SSH 2756 .
Add Sensor
Sensor Settings
priority).
1836 02.02.2015
SSH SPECIFIC
Connection Timeout Define a timeout for the connection. This is the the time the
(Sec.) sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
its specific command (e.g. cat /proc/loadavg). The maximum value
is 60 seconds (1 minute). Please enter an integer value.
Choose between:
port number as defined in the Credentials for Linux/Solaris/Mac
OS (SSH/WBEM) Systems section of the device this sensor is
created on.
the parent device settings, but define a different port number
below.
Use Port Number This field is only visible if you enabled the custom port number
setting above. Enter the port number (between 1 and 65535) that
this sensor uses for the SSH connection. Please enter an integer
value.
between:
02.02.2015 1837
breached applies.
the field empty.
the field empty.
the field empty.
1838 02.02.2015
the field empty.
Choose between:
or overrun.
empty.
field empty.
02.02.2015 1839
field empty.
empty.
SENSOR DISPLAY
1840 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1841
SCANNING INTER VAL
Choose between:
option will apply.
1842 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1843
menu bar.
dependent on.
1844 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1845
More

Notifications
Others
1846 02.02.2015
163 SSH INodes Free Sensor
6.8.163 SSH INodes Free Sensor
The SSH INodes Free sensor monitors the free index nodes on disks of Linux/Unix and Mac OS
systems via Secure Shell (SSH).
It shows free index nodes in percent, for each mount in an own sensor channel.
UNIX file systems only allow a limited number of index nodes. If the limit is exceeded, no more
data can be stored, although there might be still free space available. This sensor can help you
to notice early on if one of your drives is running out of INodes.
SSH INodes Free Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_inodes_free.png
Remarks
SSH 2756 .
02.02.2015 1847
Add Sensor
Sensor Settings
priority).
SSH SPECIFIC
1848 02.02.2015
SSH SPECIFIC
Choose between:
created on.
below.
value.
between:
SENSOR DISPLAY
for each channel.
02.02.2015 1849
SENSOR DISPLAY

Inherited Settings
described below.
1850 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1851

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1852 02.02.2015
menu bar.
dependent on.
02.02.2015 1853
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1854 02.02.2015
More

Notifications
Others
02.02.2015 1855
164 SSH Load Average Sensor
6.8.164 SSH Load Average Sensor
The SSH Load Average sensor monitors the load average of a Linux/Unix system using Secure
Shell (SSH).
Average system load within a 1 minute interval

SSH Load Av erage Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_load_av erage.png
Remarks
SSH 2756 .
1856 02.02.2015
Add Sensor
Sensor Settings
priority).
SSH SPECIFIC
02.02.2015 1857
SSH SPECIFIC
Choose between:
created on.
below.
value.
between:
SENSOR DISPLAY
for each channel.
1858 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 1859
SCANNING INTER VAL
Choose between:
option will apply.
1860 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1861
menu bar.
dependent on.
1862 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1863
More

Notifications
Others
1864 02.02.2015
165 SSH Meminfo Sensor
6.8.165 SSH M eminfo Sensor
The SSH Meminfo sensor monitors the memory usage of a Linux/Unix system using Secure
Shell (SSH).

Available memory in percent
SSH Meminfo Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_meminfo.png
Remarks
SSH 2756 .
Note: This sensor type is not compatible with Mac OS systems.
Add Sensor
02.02.2015 1865
Sensor Settings
priority).
SSH SPECIFIC
Choose between:
created on.
1866 02.02.2015
SSH SPECIFIC
below.
value.
between:
SENSOR DISPLAY
for each channel.
02.02.2015 1867
Inherited Settings
described below.
1868 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1869

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1870 02.02.2015
menu bar.
dependent on.
02.02.2015 1871
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1872 02.02.2015
More

Notifications
Others
02.02.2015 1873
166 SSH Remote Ping Sensor
6.8.166 SSH Remote Ping Sensor
The SSH Remote Ping sensor remotely monitors the connectivity between a system running
Linux/OS X and another device, using Internet Control Message Protocol (ICMP) echo requests
("Ping") and Secure Shell (SSH).
Packet loss in percent

Minimum, maximum, and average response times measured from the remote device you
connect to
SSH Remote Ping Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_remote_ping.png
Remarks
SSH 2756 .
1874 02.02.2015
Add Sensor
Sensor Settings
priority).
SSH R EMOTE PING CONFIGU R ATION
Target Enter the DNS name or IP address of the target device the Ping is
sent to. The sensor will remotely connect to the parent device it is
created on via SSH, then perform a ping request from this remote
device to the target device/server. Please enter a string.
Packet Size (Bytes) Enter the packet size in bytes for the ping. You can choose any
value between 1 and 10000. Please enter an integer value. We
02.02.2015 1875
SSH R EMOTE PING CONFIGU R ATION
Packet Count Enter the number of packets that is sent with each scanning
interval.
Custom Parameter Optionally enter additional parameters that will be added at the end
of the ping command. Please do not use parameters that change
the output format of the result to make sure it can still be parsed.
You cannot enter another command here. Please enter a string or
leave the field empty.
SSH SPECIFIC
Choose between:
created on.
below.
value.
between:
1876 02.02.2015
SSH SPECIFIC

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1877
SCANNING INTER VAL
Choose between:
option will apply.
1878 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1879
menu bar.
dependent on.
1880 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1881
Others
1882 02.02.2015
167 SSH SAN Enclosure Sensor
6.8.167 SSH SAN Enclosure Sensor
The SSH SAN Enclosure sensor monitors a Storage Area Network (SAN) enclosure via Secure
Shell (SSH). The SAN has to provide a command-line interface (CLI) for this purpose.
Overall status of the enclosure

Health status of the power supplies
Health status of the controllers
Remarks
This sensor type does not support every SAN, even if it provides a CLI. The sensor only
works with specific devices, for example, with the HP P2000.
Note: Sometimes the devices which you monitor with this sensor return status values which
are not officially documented so that the shown sensor status in PRTG differs from the "real"
device status. For more information regarding this issue, please see the Knowledge Base:
Knowledge Base: Why does my SSH SAN sensor show a wrong status?
For this sensor type, you must define corresponding credentials in section Credent ials for
Linux/Solaris/Mac OS (SSH/WBEM) Sy st em in the settings of the device 288 you want to
use the sensor on.
Add Sensor
Select the SAN enclosures you want to monitor. PRTG creates one sensor for each enclosure
02.02.2015 1883
SSH SAN ENCLOSU R E SETTINGS
Enclosure Select the enclosures you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
1884 02.02.2015
SSH SAN ENCLOSU R E SETTINGS
Enclosure Shows the identifier of the enclosure that this sensor monitors.
Durable ID Shows the durable identifier of the enclosure that this sensor
Name Shows the name of the enclosure that this sensor monitors. Once
the sensor anew.
WWN Shows the WWN (World Wide Name) of the enclosure that this
SSH SPECIFIC
Choose between:
created on.
below.
02.02.2015 1885
SSH SPECIFIC
value.
between:
SENSOR DISPLAY
for each channel.
1886 02.02.2015
Inherited Settings
described below.
02.02.2015 1887
SCANNING INTER VAL
Choose between:
option will apply.
1888 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1889
menu bar.
dependent on.
1890 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 1891
Others
1892 02.02.2015
168 SSH SAN Logical Disk Sensor
6.8.168 SSH SAN Logical Disk Sensor
The SSH SAN Logical Disk sensor monitors a logical disk on a Storage Area Network (SAN) via
Secure Shell (SSH). The SAN has to provide a command-line interface (CLI) for this purpose.
It can show the health status of the disk.
SSH SAN Logic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_san_logic al_disk.png
Remarks
use the sensor on.
02.02.2015 1893
Add Sensor
Select the volumes on the SAN device you want to monitor. PRTG creates one sensor for each
volume you choose. The settings you make in this dialog are valid for all of the sensors that
are created.
SSH SAN LOGICAL DISK SETTINGS
Volume Select the volumes you want to add a sensor for. You see a list
head.
Sensor Settings
1894 02.02.2015
priority).
SSH SPECIFIC
Choose between:
created on.
below.
value.
between:
02.02.2015 1895
SSH SAN LOGICAL DISK SETTINGS
Volume Shows the volume that this sensor monitors. Once a sensor is
anew.
Size Shows the size of the volume that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
1896 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1897

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1898 02.02.2015
menu bar.
dependent on.
02.02.2015 1899
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1900 02.02.2015
More

Notifications
Others
02.02.2015 1901
169 SSH SAN Physical Disk Sensor
6.8.169 SSH SAN Phy sical Disk Sensor
The SSH SAN Physical Disk sensor monitors a physical disk on a Storage Area Network (SAN)
via Secure Shell (SSH). The SAN has to provide a command-line interface (CLI) for this purpose.
Health status of the disk

Number of I/O operations per second
Transferred data per second
SSH SAN Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_san_phy sic al_disk.png
Remarks
use the sensor on.
1902 02.02.2015
Add Sensor
Select the disks on the SAN device you want to monitor. PRTG creates one sensor for each
disk you choose in the Add Sensor dialog. The settings you make in this dialog are valid for all
SSH SAN PHYSICAL DISK SETTINGS
head.
Sensor Settings
02.02.2015 1903
priority).
SSH SPECIFIC
Choose between:
created on.
below.
value.
between:
1904 02.02.2015
SSH SAN PHYSICAL DISK SETTINGS
Disk Shows the disk that this sensor monitors. Once a sensor is
anew.
Disk Name Shows the label of disk that this sensor monitors. Once a sensor is
anew.
Size Shows the size of the disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
02.02.2015 1905
Inherited Settings
described below.
1906 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1907

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1908 02.02.2015
menu bar.
dependent on.
02.02.2015 1909
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1910 02.02.2015
More

Notifications
Others
02.02.2015 1911
170 SSH SAN System Health Sensor
6.8.170 SSH SAN Sy stem Health Sensor
The SSH SAN System Health sensor monitors the system health of a Storage Area Network
(SAN) via Secure Shell (SSH). The SAN has to provide a command-line interface (CLI) for this
purpose.
The sensor can show several metrics of an SAN, depending on the available measurement
components on the SAN:
Overall unit status

Temperature and temperature states
Voltage and voltage states
Capacitor charge and status
sensor setup.
SSH SAN Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_san_sy stem_health.png
Remarks
1912 02.02.2015
use the sensor on.
Add Sensor
Select the metrics you want to monitor. PRTG creates one sensor for each metric you choose
that are created.
SSH SAN SPECIFIC
Metric Select the metrics you want to add a sensor for. You see a list with
head.
Sensor Settings
02.02.2015 1913
priority).
SSH SAN SPECIFIC
Metric Shows the metric this sensor monitors. Once a sensor is created,
SSH SPECIFIC
Choose between:
created on.
1914 02.02.2015
SSH SPECIFIC
below.
value.
between:
SENSOR DISPLAY
for each channel.
02.02.2015 1915
Inherited Settings
described below.
1916 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1917

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1918 02.02.2015
menu bar.
dependent on.
02.02.2015 1919
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
1920 02.02.2015
More

Notifications
Others
02.02.2015 1921
171 SSH Script Sensor
6.8.171 SSH Script Sensor
The SSH Script sensor connects to a Linux/Unix system via Secure Shell (SSH) and executes a
script file located on the target system.
Execution time
One value returned by the executable file or script (in one channel only).
SSH Sc ript Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_sc ript.png
Remarks
For details about the return value format please see the Applicat ion Programming
Int erface (API) Definit ion 2830 .
Note: For security reasons, you must store your script file on the target system. The file
must be located in the directory /var/prt g/script s. Ensure the script has executable rights.
If the script is not available or it was deleted from the script folder, you get the error
message "Script not found (237)".
1922 02.02.2015
SSH 2756 .
Add Sensor
SENSOR SETTINGS
Script Select a script file from the list. The drop down menu will list all
script files available in the /var/prtg/scripts directory on the target
Linux/Unix system. In order for the files to appear in this list, store
them into this directory. Ensure the script has executable rights.
In order for the sensor to show the expected values and sensor
status, your files must use the right format for the returned values
(in this case, exitcode:value:message to stdout). The exit code
determines the sensor status.
For detailed information on the expected return format and on
how to build custom sensors, please see the API documentation
find detailed information the the "Custom Sensors" tab. For an
example script, please see More 1932 section below.
Value Type Define what kind of values your script file gives back. Choose
between:
Int eger: An integer is expected as return value. If the script
gives back a float, PRTG will display the value 0.
sensor will also display integer values unless they don't produce
a buffer overflow.
Count er: Your script returns an integer which increases. PRTG
will show the difference between the values of two sensor
scans. Note: A counter must return an integer; float is not
supported here!
Sensor Settings
02.02.2015 1923
priority).
SENSOR SETTINGS
Script Shows the script that is executed with each sensor scan, as
defined on sensor creation. Once a sensor is created, you cannot
Parameters If your script file catches command line parameters, you can define
them here. Placeholders can be used as well. For a full list of all
placeholders please see the API documentation (Applicat ion
Programming Int erface (API) Definit ion 2830 ).
field empty.
simultaneously.
1924 02.02.2015
SENSOR SETTINGS
For links to more information, please see the More 543 section
below. Please enter a string or leave the field empty.
Value Type Shows the expected value type, chosen on sensor creation. Once
the sensor anew.
change.
SSH SPECIFIC
Choose between:
created on.
below.
02.02.2015 1925
SSH SPECIFIC
value.
between:
SENSOR DISPLAY
for each channel.
1926 02.02.2015
Inherited Settings
described below.
02.02.2015 1927
SCANNING INTER VAL
Choose between:
option will apply.
1928 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1929
menu bar.
dependent on.
1930 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1931
More
Knowledge Base: Is there a shell script example for PRTG's SSH Script Sensor?


Notifications
Others
1932 02.02.2015
172 SSH Script Advanced Sensor
6.8.172 SSH Script Advanced Sensor
The SSH Script Advanced sensor connects to a Linux/Unix system via Secure Shell (SSH) and
executes a script file located on the target system.
Execution time
Values returned by the script in multiple channels. The return value of this sensor must be
valid XML.
SSH Sc ript Adv anc ed Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_sc ript_adv anc ed.png
Remarks
For details about the return value format please see the Applicat ion Programming
Int erface (API) Definit ion 2830 .
Note: For security reasons, the script file must be stored on the target system. Please make
sure the script has executable rights.
02.02.2015 1933
SSH 2756 .

Add Sensor
SENSOR SETTINGS
Script Select a script file from the list. The drop down menu will list all
script files available in the /var/prtg/scriptsxml directory on the
target Linux/Unix system. In order for the files to appear in this list,
please store them into this directory. Please make sure the script
has executable rights. In order for the sensor to show the
expected values and sensor status, your files must return the
expected XML format to standard output. Values and message
must be embedded in the XML. For detailed information on the
expected return format and on how to build custom sensors,
please see the API documentation (Applicat ion Programming
Int erface (API) Definit ion 2830 ). There, find detailed information the
the "Custom Sensors" tab.
Sensor Settings
1934 02.02.2015
priority).
SENSOR SETTINGS
Script Shows the script that is executed with each sensor scan, as
defined on sensor creation. Once a sensor is created, you cannot
Parameters If your script file catches command line parameters, you can define
them here. Placeholders can be used as well. For a full list of all
placeholders please see the API documentation (Applicat ion
Programming Int erface (API) Definit ion 2830 ). Note: Please make
sure you write the placeholders in quotes to ensure that they are
working properly if their values contain blanks. Use single
quotation marks ' ' with PowerShell scripts, and double quotes " "
with all others. Please enter a string or leave the field empty.
EXE Result Define what to do with the results the executable file gives back.
Choose between:
02.02.2015 1935
SENSOR SETTINGS
Writ e EX E result t o disk (Filename: "Result of Sensor

[ID].t xt "): Store the last result received from the script to the
"Logs (Sensors)" directory (on the Master node, if in a cluster).
This is for debugging purposes. The file will be overridden with
each scanning interval. For information on how to find the folder
used for storage, please see Dat a St orage 2871 section.
SSH SPECIFIC
Choose between:
created on.
below.
value.
between:
1936 02.02.2015
SSH SPECIFIC

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1937
SCANNING INTER VAL
Choose between:
option will apply.
1938 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1939
menu bar.
dependent on.
1940 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1941
More

Notifications
Others
1942 02.02.2015
173 SSH VMWare ESX(i) Disk Sensor
6.8.173 SSH VM Ware ESX(i) Disk Sensor
The SSH VMWare ESX(i) Disk sensor monitors free space on disks of a VMware ESX(i) system
using Secure Shell (SSH).
It shows the free disk space in bytes and percent.
SSH VMWare ESX(i) Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_v mware_esxi_disk.png
Remarks
Requires 1943 root credentials for the VMWare host in the parent device settings.
Knowledge Base: Why do I need root credentials when monitoring VMware hosts via SSH?
Knowledge Base: Settings on ESXi 5 host when monitoring via SSH VMware ESX(i) Disk
Sensor
SSH 2756 .
Requirement: Root Credentials

In the parent device's Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems settings,
please use the root user of your VMware host for authentication! See More 1954 section below.
02.02.2015 1943
Please make sure you enable SSH on your VMware system!
Add Sensor
Select the disks on the ESX(i) system you want to monitor. PRTG creates one sensor for each
disk you select in the Add Sensor dialog. The settings you make in this dialog are valid for all
ESX(I) DISK SPECIFIC
head.
Sensor Settings
1944 02.02.2015
priority).
ESX(I) DISK SPECIFIC
Disk Shows the ID of the disk that this sensor monitors. Once a sensor
anew.
SSH SPECIFIC
Choose between:
created on.
below.
value.
between:
02.02.2015 1945
SSH SPECIFIC

breached applies.
the field empty.
1946 02.02.2015
the field empty.
the field empty.
the field empty.
Choose between:
or overrun.
02.02.2015 1947
empty.
field empty.
field empty.
empty.
1948 02.02.2015

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 1949
SCANNING INTER VAL
Choose between:
option will apply.
1950 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1951
menu bar.
dependent on.
1952 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1953
More
Knowledge Base: Settings on ESXi 5 host when monitoring via SSH VMware ESX(i) Disk Sensor
Knowledge Base: Why do I need root credentials when monitoring VMware hosts via SSH?

Notifications
Others
1954 02.02.2015
174 SSL Security Check Sensor
6.8.174 SSL Security Check Sensor
The SSL Security Check sensor monitors the Secure Sockets Layer (SSL) connectivity to the
port of a device. It tries connecting to the specified TCP/IP port number of a device with
various SSL/TLS protocol versions and shows if a particular protocol is supported.
The sensor checks connectivity with the following protocols in particular channels 86 with the
possible values Accept ed (sensor can connect with this protocol) or Denied (sensor cannot
connect with this protocol):
SSL 2.0: weak security (warning if accepted, up if denied)

SSL 3.0: weak security (warning if accepted, up if denied)
TLS 1.0: strong security (up if accepted, otherwise gray)
TLS 1.1: strong security (up if accepted, otherwise gray)
TLS 1.2: perfect security (up if accepted, otherwise gray)
The default primary channel Securit y Rat ing shows the connection security to the defined
port with one of the following states 123 :
Down: There is no secure protocol available. The sensor cannot connect with one of the
given protocols.
Warning (weak): The sensor can connect with at least one of the weak protocols SSL 2.0 or
3.0.
Up (strong): The sensor can connect with a strong protocol only (TLS 1.0, TLS 1.1, TLS 1.2).
Connecting with a weak protocol is not possible.
02.02.2015 1955
SSL Sec urity Chec k Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssl_sec urity _c hec k.png
Remarks
Add Sensor
Settings
1956 02.02.2015
priority).
SSL SPECIFIC
Please enter an integer value. The default port is 443.
SENSOR DISPLAY
for each channel.
02.02.2015 1957
SENSOR DISPLAY

Inherited Settings
described below.
1958 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1959

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1960 02.02.2015
menu bar.
dependent on.
02.02.2015 1961
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
1962 02.02.2015
175 Syslog Receiver Sensor
6.8.175 Sy slog Receiver Sensor
The Syslog Receiver sensor receives and analyzes syslog messages.
Number of received syslog messages per second

Number of messages categorized as "warning" per second
Number of messages categorized as "error" per second
Number of dropped packets per second
Sy slog Rec eiv er Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sy slog_rec eiv er.png
Remarks
With the available filter options, you can define individually which types of messages will be
considered for monitoring and thus stored, and which messages will be recognized as
warning or error messages. Depending on the filters, received messages will be counted in
the respective channels. The messages are stored in an internal database for later analysis.
The received data will be available on your respective probe system as common files, as well
as via the web interface.
11.02.2015 1963
You can add the sensor to the probe device on the one hand; then the sensor will receive all
messages of the system running the probe. Alternatively, you can add the sensor to a
specific device to gain all messages from this device directly; this will make this sensor type
faster than just using source filters.
You can use syslog specific placeholders in email notification templates 2597 to see the
messages when you receive an email notification. See the Knowledge Base: What
placeholders can I use with PRTG?
Note: If you do not add the sensor to a probe device but to another device in PRTG, be
careful with the configuration: Ensure that the IP address or DNS name of the parent device
matches the proper syslog sender. For example, if you want to receive syslogs from a
Storage Area Network (SAN), you might have to add a device to PRTG using the IP address of
a specific array member that sends the messages. Providing a DNS name that points to the IP
address of a whole group might not work for SANs.
For a general introduction to the syslog receiver's configuration, please see manual section
Monit oring Sy slogs and SNMP Traps 2784 .
Add Sensor
Sensor Settings
1964 11.02.2015
priority).
SYSLOG SPECIFIC
Listen on Port Enter the port the sensor will listen on for Syslog messages.
Usually port 514 is used. Please enter an integer value. We
Purge Messages After Define how long received syslog messages will be stored for
analysis. Choose a period of time from the drop down list.
FILTER
Include Filter Define if you want to filter syslog messages. If you leave this field
empty or use the keyword "any", all data will be processed. To
include specific types of messages only, define filters using a
special syntax. For more information, see section Filt er Rules 1972 .
Exclude Filter Define which types of syslog messages will be discarded and not
processed. To exclude specific types of messages, define filters
using a special syntax. For more information, see section Filt er
Rules 1972 .
Warning Filter Define which types of syslog messages will count for the Warnings
channel. To categorize received messages as warning messages,
define filters using a special syntax. For more information, see
section Filt er Rules 1972 .
11.02.2015 1965
FILTER

happen. By default, the sensor will turn into a Warning status after
a scanning interval has finished and there was at least one warning
message (and no error message) during this interval. The status will
remain Warning at least until the succeeding scanning interval has
finished. If in this scanning interval no warning or error message
occurred, the status of the sensor will turn Up again after the
interval.
Error Filter Define which types of syslog messages will count for the Errors
channel. To categorize received messages as error messages,
define filters using a special syntax. For more information, see
section Filt er Rules 1972 .
happen. By default, the sensor will turn into a Down status after a
scanning interval has finished and there was at least one error
message during this interval. The status will remain Down at least
until the succeeding scanning interval has finished. If in this
scanning interval no warning or error message occurred, the status
of the sensor will turn Up again after the interval.
SENSOR DISPLAY
for each channel.
1966 11.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
11.02.2015 1967
SCANNING INTER VAL
Choose between:
option will apply.
1968 11.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
11.02.2015 1969
menu bar.
dependent on.
1970 11.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
11.02.2015 1971
DEBU GGING
Log Data to Disk Define if the probe will write a log file of the received data to the
data folder (see Dat a St orage 2871 ) to the disk for debugging
purposes. Choose between:
Off (recommended): Do not write additional log files.
On: Write log files for all data received.
only.
Filter Rules for Syslog Messages

Filter rules are used for the include, exclude, warning, and error definition fields of the Syslog
Receiver sensor. They are based on the following format:
field[filter]
You can use various filters suitable to your needs. Include and exclude filters define which
messages will be monitored; warning and error filters define how received messages will be
categorized. Provide these filters in the sensor settings as formulas. Formulas are fields which
can be combined with boolean operators (AND, OR, NOT) and brackets.
Field Paramet er Example
source[ip] the IP address where the messages will be source[10.0.23.50]

received from; masks and ranges are also
possible source[10.0.23.10-50]
source[10.0.23.10/255]
facilit y any number (or range) from 0 to 23 specifying facility[2]

[number] the type of program sending the message
facility[5-7]
facility[5] OR facility[6]
severit y any number (or range) from 0 (emergency) to 7 severity[4]

[number] (debug) specifying the type of message
severity[1-3]
severity[1] AND severity
[2]
1972 11.02.2015
host name any string specifying the hostname of a device hostname

[text] in the message [www.example.com]
t ag[text] any string specifying the tag of a program or tag[su]

process in the message
appname any string specifying the appname part of the appname[myproc]
[text] message
appname[demo] AND
msgid[m42]
procid any string specifying the process identifier part procid[1860]

[text] of the message
msgid[text] any string specifying the message identifier part msgid[ID47]
of the message
message any string specifying the message part of the message[Error]
[parttext] message (substring will match; case insensitive!)
dat a checks the SD-ID block of the message's data
[id structured data for a parameter matching the [exampleSDID@12345,ev
,param,value] given value entSource,Application]
dat a checks if the given substring matches on data

[parttext] structured data as displayed in the [exampleSDID@1234]
corresponding table
dat a checks if the parameter exists in the given ID data
[id,param] element [exampleSDID@1234,eve
ntSource]
Note: String parameters (except the substring in message) have to match exactly the particular
parts of the message; they are case sensitive!
Messages Tab: Review and Analyze Syslog Messages

Received syslog messages are stored as common files in PRTG's data folder (see section Dat a
St orage 2871 ). In order to review and analyze all received messages, you can access the most
recent data directly in PRTG's web interface via the Overview tab of the respective sensor in a
table list 157 . Note: Received syslogs are only shown after an (automatic) page refresh
following to a sensor scan in the table on the Overview tab (default for auto refresh 2587 is 30
seconds).
For more details and further filter options, click on the Messages tab of the Syslog Receiver
sensor. You will see all received messages in a table list 157 . On the top, you have display filter
options to drill down into the data for specific events of your interest. The filters are the same
as available in the sensor settings, but you can define them without using formulas. Provide
the desired parameters and PRTG will load the filtered list automatically. Note: You can
automatically add a filter by clicking on the content of a column.
11.02.2015 1973
Advanced Filt er Set t ings
You can open advanced filter settings with a click on the gear icon in the Filt er row. The
Advanced Filt er will appear in a popup window. In the text field, you can define a filter using
the syntax as given in section Filt er Rules for Sy slog Messages 1972 . If you have provided filter
parameters on the Messages tab, these will be already included in the advanced filter as a
corresponding formula with the correct syntax. You can adjust this filter to your needs. You
can also copy the automatically created and manually adjusted formula for usage in the filter
fields of the sensor settings.
More
Blog Article: Introducing the New High Performance Syslog and SNMP Trap Receiver Sensors
http://www.paessler.com/blog/2013/10/11/prtg/introducing-the-new-high-performance-
syslog-and-snmp-trap-receiver-sensors
Knowledge Base: What placeholders can I use with PRTG?


Notifications
Others
1974 11.02.2015
176 System Health Sensor
6.8.176 Sy stem Health Sensor
The System Health sensor monitors internal PRTG parameters. It shows the status of the
system on which a probe runs. PRTG creates this sensor type automatically and cannot be
deleted.
It checks various parameters of your PRTG system which can affect the quality of the
monitoring results:
Healt h: This index value sums up the probe state into a value between 100% (healthy) and
0% (failing). Frequent or repeated health values below 100% should be investigated.
Available Memory : This channel shows the amount of free memory available on the system.
This value should not fall below 500 MB. This way PRTG still can request resources during
report generation, auto-discoveries, and other issues.
Available Memory Percent : This channel shows the free memory available on the system in
percent.
Sy st em CPU Load: This channel shows the current percentage CPU load on the system with
the probe. Extensive CPU load can lead to false, incomplete, and incorrect monitoring
results. This value usually should stay below 50%.
Sy stem Health Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sy stem_health.png
Sensor Settings
02.02.2015 1975
priority).
SENSOR DISPLAY
for each channel.
1976 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 1977
SCANNING INTER VAL
Choose between:
option will apply.
1978 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1979

Notifications
Others
1980 02.02.2015
177 TFTP Sensor
6.8.177 TFTP Sensor
The TFTP sensor monitors a Trivial File Transfer Protocol (TFTP) server and checks if a certain file
is available for download.
TFTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/tftp.png
Add Sensor
Sensor Settings
02.02.2015 1981
177 TFTP Sensor
priority).
SENSOR SPECIFIC
Timeout (Sec.) Enter a timeout in seconds for the request. If the reply takes longer
show a corresponding error message. Please enter an integer
Port Enter the number of the port the TFTP service is running on. The
sensor connects to this port. Please enter an integer value.
Filename Enter the name of the file that this sensor checks. If this file name is
not available on the server, the sensor shows a Down status 123 .
SENSOR DISPLAY
1982 02.02.2015
177 TFTP Sensor
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
02.02.2015 1983
177 TFTP Sensor
SCANNING INTER VAL
Choose between:
option will apply.
1984 02.02.2015
177 TFTP Sensor

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 1985
177 TFTP Sensor
menu bar.
dependent on.
1986 02.02.2015
177 TFTP Sensor
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 1987
177 TFTP Sensor

Notifications
Others
1988 02.02.2015
178 Traceroute Hop Count Sensor
6.8.178 Traceroute Hop Count Sensor
The Traceroute Hop Count sensor traces the number of hops needed from the probe system
the sensor is running on to the IP Address/DNS Name defined in the sensor's parent device.
Execution time
Number of hops.
If the number of hops (the route) changes, you can additionally define another sensor status
123 .
Trac eroute Hop Count Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/trac eroute_hop_c ount.png
Remarks
Requires 1990 .NET 4.0 to be installed on the probe system.
02.02.2015 1989

Add Sensor
Sensor Settings
priority).
1990 02.02.2015
SENSOR SETTINGS
If Route Changes Define what to do if the route has changed since the last check.
Choose between:
Ignore: Do not perform any action.
Set sensor t o "Warning": Set the sensor to Warning status.
Set sensor t o "Error": Set the sensor to Down status.
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
02.02.2015 1991
SENSOR DISPLAY
Inherited Settings
described below.
1992 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 1993

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
1994 02.02.2015
menu bar.
dependent on.
02.02.2015 1995
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
1996 02.02.2015
179 Virtuozzo Container Disk Sensor
6.8.179 Virtuozzo Container Disk Sensor
server. This sensor must be created on a Windows server parent device running Virtuozzo.
For each container, it can show the following:

Used disk space (kb-blocks)
Allowed quota (kb-blocks)
Hard limit (kb-blocks)
Virtuozzo Container Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v irtuozzo_c ontainer_disk.png
Add Sensor
Select the containers you want to monitor. PRTG creates one sensor for each disk you
02.02.2015 1997
CONTAINER SETTINGS
Container Select all containers for which you want to create a sensor for disk
monitoring. You see a list with the names of all items which are
available to monitor. Select the desired items by adding check
Sensor Settings
priority).
CONTAINER SETTINGS
Env ID Shows the unique ID of the container. Once a sensor is created,

1998 02.02.2015
CONTAINER SETTINGS
Name Shows the name of the monitored container. Once a sensor is

anew.
OS Shows the operating system running on the container. Once a

the sensor anew.
Description Shows a description for the container. Once a sensor is created,

Powered Off Define if the sensor will go into an error state if the container is
Containers powered off.
Alarm when powered off: Set the sensor for a container to
error if the container is powered off.
Ignore powered off st at e: Only show zero values for a sensor
when the monitored container is powered off. Do not set the
sensor to error.
SENSOR DISPLAY
for each channel.
02.02.2015 1999
SENSOR DISPLAY
Inherited Settings
described below.
2000 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 2001

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
2002 02.02.2015
menu bar.
dependent on.
02.02.2015 2003
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
2004 02.02.2015
180 Virtuozzo Container Network Sensor
6.8.180 Virtuozzo Container Network Sensor
The Virtuozzo Container Network sensor monitors the network traffic of a container on a
device running Virtuozzo.
For each container, it can show the following network usage parameters:
Incoming bytes per 30 seconds

Incoming packets per 30 seconds
Outgoing bytes per 30 seconds
Outgoing packets per 30 seconds
Transmitted bytes in total
Virtuozzo Container Network Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v irtuozzo_c ontainer_network.png
Add Sensor
02.02.2015 2005
Select the containers you want to monitor. PRTG creates one sensor for each disk you
CONTAINER SETTINGS
Container Select all containers for which you want to create a sensor. You
see a list with the names of all items which are available to monitor.
table head.
Sensor Settings
priority).
2006 02.02.2015
CONTAINER SETTINGS
Env ID Shows the unique ID of the container. Once a sensor is created,

Name Shows the name of the monitored container. Once a sensor is

anew.
OS Shows the operating system running on the container. Once a

the sensor anew.
Description Shows a description for the container. Once a sensor is created,

Powered Off Define if the sensor will go into an error state if the container is
Containers powered off.
Alarm when powered off: Set the sensor for a container to
error if the container is powered off.
Ignore powered off st at e: Only show zero values for a sensor
when the monitored container is powered off. Do not set the
sensor to error.
SENSOR DISPLAY
for each channel.
02.02.2015 2007
SENSOR DISPLAY

SCANNING INTER VAL
Interval The scanning interval of this sensor type cannot be inherited or

changed. Due to internal restrictions of the Virtuozzo system, a fix
value must be used.
Inherited Settings
described below.

settings.
2008 02.02.2015

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2009

menu bar.
dependent on.
2010 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 2011
181 VMware Host Hardware (WBEM) Sensor
6.8.181 VM ware Host Hardware (WBEM ) Sensor
The VMware Host Hardware sensor monitors hardware information of a ESX/ESXi server using
Web-Based Enterprise Management (WBEM).
It can show the following, depending on the selected ESX component:
Health status
Temperature
Power
Fan rotations per minute (RPM)
Battery voltage
sensor setup.
VMWare Host Hardware (WBEM) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_host_hardware_wbem.png
Remarks
The parent device must be a VMware ESX/ESXi server version 3.5, 4.0, 5.0, 5.1, or 5.5.
2012 02.02.2015
Add Sensor
Select the ESX components you want to monitor. PRTG creates one sensor for each hardware
element you choose in the Add Sensor dialog. The settings you make in this dialog are valid
ESX SER VER ELEMENTS
ESX Element Select the hardware elements you want to add a sensor for. You
see a list with the names of all items which are available to monitor.
table head.
Sensor Settings
02.02.2015 2013
priority).
ESX SER VER ELEMENTS
Element Shows the ESX element that this sensor monitors. Once a sensor
anew.
Automatic Sensor Define if the sensor will change its status dependent on the health
State state reading. Choose between:
Set sensor st at e aut omat ically t o 'Warning' or 'Down': Set
the sensor to a Warning or Down status when the server
returns respective values. The sensor will additionally change to
a Down status if the connection to the server fails.
Just report t he current reading, ignore Server Healt h Value:
Never change the sensor's status dependent on the values
returned by the server. The sensor will only change to a Down
status if the connection to the server fails.
between:
2014 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 2015
SCANNING INTER VAL
Choose between:
option will apply.
2016 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2017
menu bar.
dependent on.
2018 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 2019
182 VMware Host Hardware Status (SOAP) Sensor
6.8.182 VM ware Host Hardware Status (SOAP) Sensor
The VMware Host Hardware Status (SOAP) sensor monitors the hardware status of a VMware
host server using Simple Object Access Protocol (SOAP).
It shows the total number of items in "Normal", "Warning," and "Alert" status, just as the
vSphere client reports.
This sensor is intended to give you a general status overview for your host. Any states other
than "Normal" will be reported in the sensor message.
VMware Host Hardware Status (SOAP) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_host_hardware_status_soap.png
Remarks
For this sensor type credentials for VMware servers must be defined for the device you want
to use the sensor on. Ensure you enter a user with sufficient access rights to obtain
statistics (read-only usually works).
This sensor only shows items that report an actual status, so you might see more "sensors"
in your vSphere client than the number of states available in the channels of this PRTG
sensor.
The parent device must be a VMware ESX/ESXi server version 3.5, 4.0, 5.0, 5.1, or 5.5. We
recommend to not use this sensor type on your vCenter. Reliable hardware information can
only be provided when this sensor is created on your physical host server as parent device.
2020 02.02.2015
If you consider timeouts (error code PE121), try increasing the connection limit on the
VMware system. See the Knowledge Base: How can I increase the connection limit on
VMware systems?
Note: If you use this sensor on a probe that runs on Windows Server 2003 (including SP1
and SP2) and the target system is VMware ESXi 5.1 or later, you might receive the error
message "The underlying connection was closed: An unexpected error occurred on a send."
Please note that PRTG does not officially support Windows Server 2003! For details, please
see the Knowledge Base: Monitoring ESXi 5.1 and higher: Handshake Failure on Windows
XP/Server 2003

Settings on VMware Host System

If you set up this sensor on different probes (for example, when using remote probes 2848 or
when running a cluster 81 setup), you might need to change the settings of your VMware
host, so it accepts more incoming connections. Otherwise you might get connection timeouts
when running plenty of VMware sensors with a short scanning interval.
For details about this setting, please see More section below.
Add Sensor
Select the VMware hosts you want to monitor. PRTG creates on sensor for each host server
02.02.2015 2021
VMWAR E HOST SETTINGS
Host Server Select the host server you want to add a sensor for. You see a list
head.
Sensor Settings
priority).
MoID Shows the Managed Object ID (MoID) of the host that this sensor
2022 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 2023
SCANNING INTER VAL
Choose between:
option will apply.
2024 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2025
menu bar.
dependent on.
2026 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How can I increase the connection limit on VMware systems?
Knowledge Base: Monitoring ESXi 5.1 and higher: Handshake Failure on Windows XP/Server
2003

02.02.2015 2027

Notifications
Others
2028 02.02.2015
183 VMware Host Performance (SOAP) Sensor
6.8.183 VM ware Host Performance (SOAP) Sensor
The VMware Host Performance (SOAP) sensor monitors a VMware host server using Simple
Object Access Protocol (SOAP).

Network usage
Disk usage
Active memory in bytes
Consumed memory in bytes and percent
Used memory swap
Disk and data store latency (read and write)
Network received and transmitted speed
Power status
sensor setup.
02.02.2015 2029
VMware Host Performanc e (SOAP) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_host_performanc e_soap.png
Remarks
2030 02.02.2015
VMware systems?
XP/Server 2003


Add Sensor
Sensor Settings
02.02.2015 2031
priority).
MoID Shows the Managed Object ID (MoID) of the host that this sensor
SENSOR DISPLAY
for each channel.
2032 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 2033
SCANNING INTER VAL
Choose between:
option will apply.
2034 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2035
menu bar.
dependent on.
2036 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
2003

02.02.2015 2037

Notifications
Others
2038 02.02.2015
184 VMware Virtual Machine (SOAP) Sensor
6.8.184 VM ware Virtual M achine (SOAP) Sensor
The VMware Virtual Machine (SOAP) sensor monitors a virtual machine on a VMware host
server using Simple Object Access Protocol (SOAP).

Active memory in bytes
Consumed memory in bytes and percent
Read and write latency
Network usage (total, received, and transmitted bytes per second)
sensor setup.
VMware Virtual Mac hine (SOAP) Sensor
02.02.2015 2039
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_v irtual_mac hine_soap.png
Remarks
Note: For VMware virtual machines, disk usage channels are only available as of virtual
hardware version 8.
VMware systems?
XP/Server 2003


2040 02.02.2015
Add Sensor
Note: PRTG requests a full list of all virtual machines configured on the device. Because of this,
it may take a few seconds before the dialog is loaded.
Select the VMware virtual machines you want to monitor. PRTG creates one sensor for each
virtual machine you choose in the Add Sensor dialog. The settings you make in this dialog are
Virtual Machine You see a list of all virtual machines (VMs) available on the host
server on this device, including the ones that are not running. All
VMs are listed with name and the OS it is running on. Select the
lines. One sensor will be created for each selection. You can also
head.
Sensor Settings
02.02.2015 2041
priority).
MoID Shows the Managed Object ID (MoID) of the virtual machine that
this sensor monitors. Once a sensor is created, you cannot change
this value. It is shown for reference purposes only. If you need to
Handling of "Powered Define how the sensor will react to a virtual machine that is
off" VM powered off. Choose between:
Ignore "powered off" st at e (default ): The sensor will not
change to a Down status 123 if the virtual machine is powered off.
It will report zero values instead.
Alarm when VM is "powered off": The sensor will change to a
Down 123 status if the virtual machine is powered off. Note: While
in Down status, a sensor does not record any data in all of its
channels.
SENSOR DISPLAY
for each channel.
2042 02.02.2015
SENSOR DISPLAY

Inherited Settings
described below.
02.02.2015 2043
SCANNING INTER VAL
Choose between:
option will apply.
2044 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2045
menu bar.
dependent on.
2046 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
2003

02.02.2015 2047

Notifications
Others
2048 02.02.2015
185 WBEM Custom Sensor
6.8.185 WBEM Custom Sensor
The WBEM Custom Sensor performs a custom query via Web-Based Enterprise Management
(WBEM)
It can show the retrieved parameters from the monitored interface in several channels.
WBEM Custom Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wbem_c ustom.png
02.02.2015 2049
Remarks
Add Sensor
Sensor Settings
priority).
CU STOM QU ER Y SPECIFIC
Namespace Enter the namespace for the query. Default value is root /cimv2.
2050 02.02.2015
WBEM Query (WQL) Enter the WBEM query that this sensor performs with every
scanning interval. It has to be written in WQL (WBEM Query
Language) or CQL (CIM Query Language). For example, a query can
look like this:
SELECT * FROM Linux_UnixProcess WHERE ModulePath = "/sbin/
portmap"
Numeric Format Define the expected type of the returned values. Choose
between:
Int eger: The query returns integer values.
Float : The query returns float values.
between:
SENSOR DISPLAY
for each channel.
02.02.2015 2051
SENSOR DISPLAY
Inherited Settings
described below.
2052 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 2053

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
2054 02.02.2015
menu bar.
dependent on.
02.02.2015 2055
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
2056 02.02.2015
More
For more tips and tricks regarding WQL scripts, please see the Paessler Knowledge Base and
search for WQL.
http://kb.paessler.com/en/tags/wql/

Notifications
Others
02.02.2015 2057
186 Windows CPU Load Sensor
6.8.186 Windows CPU Load Sensor
The Windows CPU Load sensor monitors the CPU load on a computer via Windows
It shows the CPU usage of all processors and the total load in percent.
Windows CPU Load Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_c pu_load.png
Remarks
Requires 2059 Windows credentials in the parent device settings 288 .
Requires 2059 Windows 2008 or later on the probe system.
Uses a hybrid approach 2059 to query monitoring data: Performance counters as standard
approach and WMI as fallback.
2058 02.02.2015

section.


remote probe 2848 .

work.
Automatic.
02.02.2015 2059
Add Sensor
Sensor Settings
priority).
WMI ALTER NATIVE QU ER Y
Errors and Invalid Data This is an extended help field only. PRTG's WMI sensors are
equipped with the most efficient and accurate WMI queries.
However, Microsoft has changed (and will continue to do that in
the future) some WMI classes over the various Windows/
ServicePack/patchlevel versions, resulting in errors like "class not
valid" or "invalid data". Wherever possible, PRTG features an
alternative query that might work in your specific configuration.
When you keep getting errors for this sensor, please try enabling
the alternative query method below.
2060 02.02.2015
WMI ALTER NATIVE QU ER Y
Alternative Query Choose the method PRTG uses to query via WMI. For compatibility
reasons, you can enable an alternative query method. We
recommend using the default value. You can choose between:
Use default (recommended): Use PRTG's standard method to
query WMI. This is the best setting in most cases.
Use alt ernat ive (if default does not work): Use an alternative
method to query WMI. If you keep getting errors with the default
setting, please try this setting.
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 2061
SCANNING INTER VAL
Choose between:
option will apply.
2062 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2063
menu bar.
dependent on.
2064 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 2065
More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?

Notifications
Others
2066 02.02.2015
187 Windows IIS 6.0 SMTP Received Sensor
6.8.187 Windows IIS 6.0 SM TP Received Sensor
The Windows IIS 6.0 SMTP Receiver Sensor monitors Microsoft's Internet Information Services
regarding the number of received emails for an IIS 6.0 SMTP service (Exchange 2003) using
Windows Performance Counters or Windows Management Instrumentation (WMI), as configured
in the "Windows Compatibility Options" of the parent device.
It shows the number and bytes of received messages.
Remarks
This service is not used by Exchange Server 2007 and higher. Exchange Server 2007 uses its
own SMTP stack implemented in the Microsoft Exchange Transport service.

section.

02.02.2015 2067

remote probe 2848 .

work.
Automatic.
Add Sensor
Sensor Settings
2068 02.02.2015
priority).
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
02.02.2015 2069
SENSOR DISPLAY
Inherited Settings
described below.
2070 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 2071

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
2072 02.02.2015
menu bar.
dependent on.
02.02.2015 2073
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
2074 02.02.2015
More

Notifications
Others
02.02.2015 2075
188 Windows IIS 6.0 SMTP Sent Sensor
6.8.188 Windows IIS 6.0 SM TP Sent Sensor
The Windows IIS 6.0 SMTP Sent Sensor monitors Microsoft's Internet Information Services
regarding the number of sent emails for an IIS 6.0 SMTP service (Exchange 2003) using
Windows Performance Counters or Windows Management Instrumentation (WMI), as configured
in the "Windows Compatibility Options" of the parent device.
Number and bytes of sent messages

Number of retries per second for sent messages
Remarks
This service is not used by Exchange Server 2007 and higher. Exchange Server 2007 uses its
own SMTP stack implemented in the Microsoft Exchange Transport service.

section.

2076 02.02.2015

remote probe 2848 .

work.
Automatic.
Add Sensor
Sensor Settings
02.02.2015 2077
priority).
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
2078 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 2079
SCANNING INTER VAL
Choose between:
option will apply.
2080 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2081
menu bar.
dependent on.
2082 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 2083
More

Notifications
Others
2084 02.02.2015
189 Windows IIS Application Sensor
6.8.189 Windows IIS Application Sensor
The Windows IIS Application sensor monitors a Microsoft Internet Information Services server
using Windows Performance Counters or Windows Management Instrumentation (WMI), as
configured in the "Windows Compatibility Options" of the parent device. It can also monitor
applications that use IIS, such as Microsoft SharePoint or Microsoft Reporting Services (SSRS).
Sent and received bytes per second

Number of sent and received files per second
Number of anonymous and known users per second
Number of Common Gateway Interface (CGI) requests per second
Number of GET and POST requests per second
Number of not found errors per second
Windows IIS Applic ation Sensor
02.02.2015 2085
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_iis_applic ation.png
Remarks

section.


remote probe 2848 .
2086 02.02.2015

work.
Automatic.
Add Sensor
Select the web service instances you want to monitor. PRTG creates one sensor for each
instance you choose in the Add Sensor dialog. The settings you make in this dialog are valid
WMI INTER NET INFOR MATION SER VICES
Specify Instance You see a list with the names of all items which are available to
in the table head.
Sensor Settings
02.02.2015 2087
priority).
WMI INTER NET INFOR MATION SER VICES
Instance Shows the name of the web service instance that this sensor
SENSOR DISPLAY
for each channel.
2088 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 2089
SCANNING INTER VAL
Choose between:
option will apply.
2090 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2091
menu bar.
dependent on.
2092 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 2093
More

Notifications
Others
2094 02.02.2015
190 Windows Last Update (Remote Registry) Sensor
6.8.190 Windows Last Update (Remote Registry ) Sensor
The Windows Last Update sensor uses the Windows Remote Registry service to read the
number of days since the last Windows update from its parent device.
Elapsed time since the last update. Use threshold triggers 2484 to get notified if this number
breaches a certain value.
Execution time
Windows Last Update (Remote Registry ) Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_last_update.png
Remarks
Knowledge Base: Fixing a Protocol Error Appearing With Windows Last Update Sensor
02.02.2015 2095



In order for this sensor to work, you need to enable the RemoteRegistry "Remote Registry"
Windows service on the target machine. To do so, please log in to this machine and open the
services manager (for example, start services.msc). In the list of services, find the Remot e
Regist ry service and set its Start Type to Automatic. For details, see section More 2102 .
Add Sensor
Sensor Settings
2096 02.02.2015
priority).
SENSOR SETTINGS
change.
DEBU G OPTIONS
between:
02.02.2015 2097
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
2098 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 2099

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
2100 02.02.2015
menu bar.
dependent on.
02.02.2015 2101
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How do I enable the Remote Registry Service on a Windows PC?
Knowledge Base: Fixing a Protocol Error Appearing With Windows Last Update Sensor


2102 02.02.2015
Notifications
Others
02.02.2015 2103
191 Windows Logged In Users Sensor
6.8.191 Windows Logged In Users Sensor
The Windows Logged In Users sensor queries the number of users logged in to a Windows
installation on the parent device.
Total number of logged in users

Execution time
Names of all logged in users. You can optionally filter for certain user names.
Windows Logged In Users Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_logged_in_users.png
Remarks
2104 02.02.2015


Add Sensor
Sensor Settings
02.02.2015 2105
priority).
SENSOR SETTINGS
User Filter (optional) To filter the value returned by certain user names, define them
here. Enter a comma separated list of user names, or leave the field
empty.
Processing of Users in Define how the user names entered above are used. Choose
"User Filter" between:
Do not count users list ed in "User Filt er": Exclude the users
entered above from counting and only count other users.
Only count users list ed in "User Filt er": Ignore all other users
and only count user names from the list entered above.
Show Usernames in Define if the sensor shows the names of logged in users in its last
the Sensor Message message. Choose between:
Yes, show list of logged in usernames: The sensor message
shows the names of all logged in users.
No, only show t he amount of logged in users: The sensor
message shows the number of logged in users.
change.
2106 02.02.2015
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 2107
SCANNING INTER VAL
Choose between:
option will apply.
2108 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2109
menu bar.
dependent on.
2110 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .

Notifications
Others
02.02.2015 2111
192 Windows MSMQ Queue Length Sensor
6.8.192 Windows M SM Q Queue Length Sensor
The Windows MSMQ Queue Length sensor reads the number of messages in a Microsoft
Message Queue of the parent device.
Total number of messages in the queue

Execution time
Windows MSMQ Queue Length Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_msmq_queue_length.png
Remarks
Requires 2113 the MSMQ service to be running on both the probe and the target system.
Knowledge Base: How do I activate Message Queuing in my Windows installation?
2112 02.02.2015


Requirement: Message Queuing Service

In order for this sensor to work, the MSMQ "Message Queuing" service must be started both
on the target system and on the computer running the PRTG probe: Either on the local system
(on every node, if on a cluster probe), or on the system running the remote probe 2848 .
Additionally, the MSMQ "Message Queuing" service must also be started on the target
computer.
Automatic.
Depending on your Windows version you may first need to install the Microsoft Message
Queue (MSMQ) Server.
Note: When installing Microsoft Message Queue (MSMQ) Server, make sure you install it
including the Directory Service. Depending on your Windows installation this might have
different names, such as
MSMQ Active Directory Domain Service Integration

Directory Service Integration
Active Directory Integration
For details, please see More 2120 section below.
02.02.2015 2113
Add Sensor
Select the message queues you want to monitor. PRTG creates one sensor for each queue
SENSOR SETTINGS
Message Queue You see a list with the names of all items which are available to
in the table head. If there are no message queues available, you will
see a corresponding message.
Note: This sensor cannot monitor sub-queues.
Sensor Settings
2114 02.02.2015
priority).
SENSOR SETTINGS
Message Queue Shows the name of the queue that this sensor monitors. Once a
the sensor anew.
Message Queue Type Shows the type of the queue that this sensor monitors. Once a
the sensor anew.
Min. Message Age Optionally define an age in minutes the message has to be old to
be counted. If set, messages younger than this age are not
regarded. If you leave this field blank, the sensor will not check for
the message age. Please enter an integer value or leave the field
empty.
change.
DEBU G OPTIONS
between:
02.02.2015 2115
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
2116 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 2117

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
2118 02.02.2015
menu bar.
dependent on.
02.02.2015 2119
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How do I activate Message Queuing in my Windows installation?

Notifications
2120 02.02.2015
Others
02.02.2015 2121
193 Windows Network Card Sensor
6.8.193 Windows Network Card Sensor
The Windows Network Card sensor monitors bandwidth usage and traffic of a network
interface using Windows Performance Counters or Windows Management Instrumentation
(WMI), as configured in the "Windows Compatibility Options" of the parent device.
Total traffic on the network card

Traffic in and traffic out
Number of packets per second.
Windows Network Card Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_network_c ard.png
Remarks
This sensor type supports teamed network adapters ("NIC teaming") on Windows Server
2012.
2122 02.02.2015

section.


remote probe 2848 .

work.
Automatic.
02.02.2015 2123
Add Sensor
Select the network cards you want to monitor PRTG creates one sensor for each interface you
SENSOR SPECIFIC
Network Interface Select the network card(s) you want to add a sensor for. You see a
table head.
Sensor Settings
2124 02.02.2015
priority).
SENSOR SPECIFIC
Selected Interface Shows the name of the network card that this sensor monitors.
SENSOR DISPLAY
for each channel.
2477 settings).
02.02.2015 2125
SENSOR DISPLAY
Inherited Settings
described below.
2126 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 2127

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
2128 02.02.2015
menu bar.
dependent on.
02.02.2015 2129
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
2130 02.02.2015
More

Notifications
Others
02.02.2015 2131
194 Windows Pagefile Sensor
6.8.194 Windows Pagefile Sensor
The Windows Pagefile sensor monitors the Windows pagefile usage via Windows Performance
Counters or Windows Management Instrumentation (WMI), as configured in the "Windows
Compatibility Options" of the parent device.
It shows the pagefile usage in percent.
Windows Pagefile Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_pagefile.png
Remarks
Note: This sensor does not work with Windows 2000, because the respective WMI class
does not exist on this operating system!

2132 02.02.2015
section.


remote probe 2848 .

work.
Automatic.
Add Sensor
Sensor Settings
02.02.2015 2133
priority).
SENSOR DISPLAY
for each channel.
2134 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 2135
SCANNING INTER VAL
Choose between:
option will apply.
2136 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2137
menu bar.
dependent on.
2138 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 2139
Others
2140 02.02.2015
195 Windows Physical Disk Sensor
6.8.195 Windows Phy sical Disk Sensor
The Windows Physical Disk sensor monitors parameters of a physical disk of a Windows device
using Windows Performance Counters or Windows Management Instrumentation (WMI), as
configured in the "Windows Compatibility Options" of the parent device.
It can show the following, for example:
Accumulated disk read, write, and transfer time and bytes

Idle time
Queue length
Split IO
sensor setup.
Windows Phy sic al Disk Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_phy sic al_disk.png
Remarks
02.02.2015 2141

section.


remote probe 2848 .

work.
Automatic.
2142 02.02.2015
Add Sensor
Select the physical disks you want to monitor. PRTG creates one sensor for each disk you
select in the Add Sensor dialog.
WINDOWS PHYSICAL DISK SPECIFIC
Physical Disks You see a list showing the Name of the counters you can monitor,
as well as the Inst ance, that is, the respective logical disk (or
'_Total'). If there are no logical disks available, you see a
corresponding message. From the list, choose all Name/Inst ance
combinations you want to monitor by adding a check mark in front
of the respective line (for example, choose '% Disk Read Time for
C:').
in the table head.
Sensor Settings
02.02.2015 2143
priority).
R EADINGS ACCESSIBLE U SING WMI
Display Name These fields show the parameters that are used to query data for
this sensor from the target device.Once a sensor is created, you
Instance cannot change this value. It is shown for reference purposes only.
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
between:
2144 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 2145
SCANNING INTER VAL
Choose between:
option will apply.
2146 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2147
menu bar.
dependent on.
2148 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 2149
More

Notifications
Others
2150 02.02.2015
196 Windows Print Queue Sensor
6.8.196 Windows Print Queue Sensor
The Windows Print Queue sensor reads the print queue on its parent device and returns the
number of jobs in the print queue. It can monitor queues for all printers that are installed
locally. For example, you can use this sensor to monitor all print queues on your Windows
print server and retrieve information about all available jobs which are longer in the queue than
defined.
Number of jobs in the queue

Execution time
Additionally, this sensor can change to a defined status if there is a printer problem. See
section Sensor Set t ings 2153 for available parameters.
Windows Print Queue Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_print_queue.png
Remarks
Requires 2152 Windows credentials in the parent device settings
Requires 2152 the Print Spooler Windows service to be running on the target device.
You can add a 'change' trigger 2597 to this sensor to get a notification when the number of
jobs in the queue changes.
02.02.2015 2151


Requirement: Print Spooler Service

In order for this sensor to work, the Spooler "Print Spooler" service must be started on the
target computer.
Automatic.
Add Sensor
Select the print queues you want to monitor. PRTG creates one sensor for each task you
2152 02.02.2015
SENSOR SETTINGS
Print Queue You see a list with the names of all items which are available to
in the table head. If there are no print queues available, you see a
corresponding message.
Note: If a printer name changes after you created a sensor for its
queue, please add the sensor anew.
Sensor Settings
priority).
02.02.2015 2153
SENSOR SETTINGS
Print Queue Shows the name of the task that this sensor monitors. Once a
the sensor anew.
Advanced Status You can optionally define specific Sensor St at es 123 for several
Option return messages of the monitored printer. Choose between:
Hide: Do not define sensor states for specific return messages.
Show: If you choose this option, you can define sensor states
for various messages which the monitored printer reports.
Door Open These settings are only available if you select the advanced status
option above. For each reported problem of the monitored printer,
Manual Feed Required you can define the status which the sensor shows. Choose
between:
Needs User Ignore: The sensor remains in the current status if this message
Intervention is reported by the printer.
Warning: The sensor shows the Warning status if this message
Offline is reported by the printer.
Error: The sensor shows a Down status if this message is
Out of Memory reported by the printer.
Out of Paper
Paper Jammed
Paper Problem
Paused
Printer Error
Printer Not Available
Toner Low
Toner Out
Min. Print Job Age Optionally define the age of the print job in seconds. If set, jobs
(Sec.) younger than this value are not regarded. If you leave this field
blank, the sensor will not check for the print job age. Please enter
an integer value or leave the field empty.
2154 02.02.2015
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 2155
SCANNING INTER VAL
Choose between:
option will apply.
2156 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2157
menu bar.
dependent on.
2158 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
02.02.2015 2159
Others
2160 02.02.2015
197 Windows Process Sensor
6.8.197 Windows Process Sensor
The Windows Process sensor monitors a Windows process using Windows Performance
Counters or Windows Management Instrumentation (WMI), as configured in the "Windows
Compatibility Options" of the parent device.
It shows the following parameters about the process:
Absolute working set in bytes

Private bytes
Number of threads
Number of handles
Number of instances
Average CPU usage (if there are multiple instances running)
Total CPU usage
For the "total CPU usage" value of a process, all CPU usage values are summed up. The total is
divided by the number of all CPUs; the maximum value is 100%. This corresponds to the CPU
usage of all instances of this specific process. Regarding the "per instance" value, the summed
up CPU usage value is divided by the number of all instances. It shows the average CPU usage
of a single instance of the process on one CPU.
Windows Proc ess Sensor
02.02.2015 2161
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_proc ess.png
Remarks
Does not support 64bit processes 2162 on devices with the address "localhost", "127.0.0.1",
"::1". Use the IP address in the network instead.
Monitoring 64bit Processes on "localhost"

This sensor type does not support 64bit processes on devices with the address "localhost",
"127.0.0.1" (IPv4 address), or "::1" (IPv6 address) in PRTG. This is the case for probe devices, for
example. The sensor works on all other target devices in your network though. So if you want
to monitor 64bit processes on your local machine, add this device to PRTG with one of the IP
addresses under which it is reachable in the local network (for example, 10.0.10.20 instead of
127.0.0.1) and create the sensor on this device.

section.

2162 02.02.2015

remote probe 2848 .

work.
Automatic.
Add Sensor
Sensor Settings
02.02.2015 2163
priority).
WINDOWS PR OCESS MONITOR
Executable Enter the name of the process that you want to monitor. Please
enter the name of an executable file without the .exe extension
(for example, enter firefox to monitor firefox.exe). The sensor
goes into a Down status if the process is not active on the device.
SENSOR DISPLAY
for each channel.
2164 02.02.2015
Inherited Settings
described below.
02.02.2015 2165
SCANNING INTER VAL
Choose between:
option will apply.
2166 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2167
menu bar.
dependent on.
2168 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 2169
More

Notifications
Others
2170 02.02.2015
198 Windows Registry Sensor
6.8.198 Windows Registry Sensor
The Windows Registry sensor checks if a key and the defined string value exists in the
Windows registry.
It can show the retrieved value in its last message field.

Additionally, the sensor can process the result using a keyword search and switch to a
defined status.
It shows also the response time.
Windows Registry Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_registry .png
Remarks
Note: This sensor type can process REG_SZ values only.
Requires 2171 the Remote Registry Windows service to be running on both the target and the
probe system.
Requires 2172 Windows credentials in the parent device settings and the Windows user
account running the PRTG Probe service must have access to the registry. Probe and target
computer must be member of the same domain.

In order for this sensor to work, ensure the RemoteRegistry "Remote Registry" Windows
service is running on both the computer running the PRTG probe and the target machine.
02.02.2015 2171
Automatic.

sensor on.
Please make sure that the Windows user account running the PRTGProbeService "PRTG Probe
Service" on the computer running the PRTG probe has access to the registry of the remote
computer (by default, this is the probe computer's local Windows "system" account).
Additionally, the computer running the PRTG probe and the target computer must be member
of the same Windows local domain.
Note: You cannot perform a remote registry call with a Windows user account for which no
password is defined.
Add Sensor
Sensor Settings
2172 02.02.2015
priority).
R EGISTR Y SETTINGS
Root Select the root key of the registry entry you want to monitor.
Choose between:
HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE
HKEY_USERS
HKEY_PERFORMANCE_DATA
HKEY_CURRENT_CONFIG
HKEY_DYN_DATA
Key Name Enter the path of the key you want to monitor. Enter the full path
after the root, each subkey separated by a backslash. For example,
enter Software\Microsoft\Windows\CurrentVersion
Value Name Enter the name of the value you want to monitor. For example,
enter ProductId to read the product ID of the target computer's
Windows installation.
64-Bit Selection Define how the sensor looks up the provided key name. This is
relevant for some registry keys only, for example those containing
the Wow6432Node subkey. Choose between:
Use 32-bit regist ry view: The key provided above is copied
from the 32-bit registry editor.
Use 64-bit regist ry view: The key provided above is copied
from the 64-bit registry editor.
For more information, see the More 2179 section below.
Value Select if the sensor processes the returned result further. Choose
between:
Ignore Value: Do not perform any keyword checks. The sensor
checks only if the defined key and value exists.
02.02.2015 2173
R EGISTR Y SETTINGS
Process Text : Use the returned value to perform keyword

checks. Select below. If you choose this setting, the sensor
shows the registry value in its last message field.
Keywords (Positive) Check if a certain keyword is part of the received value. If there is
no match, the sensor shows a "Down" status.
Disable: Do not check for positive keywords.
Enable key word check (posit ive): Check if a certain keyword
exists in the received value. Define below.
Text Must Include This setting is only visible if you activated keyword check above.
Enter a search string that the returned value must contain.
For Keyword Search Define the method that you want to use for the search string.
Use Choose between:
Keywords (Negative) Check if a certain keyword is not part of the received value. If
there is a match, the sensor shows a "Down" status.
Disable: Do not check for negative keywords.
Enable key word check (negat ive): Check if a certain keyword

does not exist in the received value. Define below.
Text Must Not Include This setting is only visible if you activated keyword check above.
Enter a search string that the returned value must not contain.
For Keyword Search Define the method you want to use for the search string. Choose
Use between:
2174 02.02.2015
SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 2175
SCANNING INTER VAL
Choose between:
option will apply.
2176 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2177
menu bar.
dependent on.
2178 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
How do I discern 32-bit registry values vs. 64-bit registry values?

Notifications
02.02.2015 2179
Others
2180 02.02.2015
199 Windows Scheduled Task Sensor
6.8.199 Windows Scheduled Task Sensor
The Windows Scheduled Task sensor monitors the time of the last run of a scheduled task. If a
task was never run, the sensor shows an error.
Time since the last run of the specified task

The corresponding exit code
Windows Sc heduled Task Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_sc heduled_task.png
Remarks
Requires 2182 the Remote Registry Windows service to be running on both the probe and the
target system.
For this sensor type, we recommend running the PRTG probe on Windows 2012 R2 2182 or
later.
You can define limits (in seconds) in the channel settings 2477 for Last Run to set the sensor
into a Warning or Down status 123 if the last run of the task was too long ago.
02.02.2015 2181


In order for this sensor to work, ensure the RemoteRegistry "Remote Registry" Windows
service is running on both the computer running the PRTG probe and the target machine.
Automatic.

Requirement: Monitored Systems

Note: We recommend running the PRTG probe on Windows 2012 R2 or later.
Microsoft implemented two versions of scheduled task, V1 and V2. Windows 2000, Windows
XP, and Windows Server 2003 create scheduled tasks V1 by default. Later Windows versions
can create and read both versions.
If the system running the PRTG probe (either on the core server or a remote probe) runs on
one of these early Windows versions, you will not be able to monitor scheduled tasks of V2.
In this case, please create the tasks on the monitored machines compatible with "Windows
Server 2003, Windows XP, or Windows 2000" if there is a newer Windows version installed.
Note: These Windows versions are not officially supported by PRTG; see section Sy st em
Requirement s 21 .
2182 02.02.2015
If the system running the PRTG probe (either on the core server or a remote probe) runs on
Windows Vista or later, you will be able to monitor scheduled tasks of both V1 and V2 (i.e.
from all Windows versions).
Add Sensor
Select the scheduled tasks you want to monitor. PRTG creates one sensor for each task you
SENSOR SETTINGS
Task Name You see a list with the names of all items which are available to
in the table head. If there are no scheduled tasks found in the
Windows Task Scheduler on the target device, you see a
corresponding message.
Note: If a task name changes after you created a sensor for it,
Sensor Settings
02.02.2015 2183
priority).
SENSOR SETTINGS
Ignore Status Codes Define exit codes of the monitored task which are not processed
by the sensor. If the external program returns one of these values,
they are converted into the code 0. Enter a comma separated list
of exit codes or leave this field empty.
Name Shows the name of the task that this sensor monitors. Once a
the sensor anew.
change.
DEBU G OPTIONS
between:
2184 02.02.2015
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
described below.
02.02.2015 2185
SCANNING INTER VAL
Choose between:
option will apply.
2186 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2187
menu bar.
dependent on.
2188 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Bandwidt h
Memory
Disk
File
Cust om
02.02.2015 2189
More

Notifications
Others
2190 02.02.2015
200 Windows System Uptime Sensor
6.8.200 Windows Sy stem Uptime Sensor
The Windows System Uptime sensor monitors uptime of a Windows system using Windows
It shows the total uptime of the system in days, hours, minutes.
Windows Sy stem Uptime Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_sy stem_uptime.png
Remarks

02.02.2015 2191
section.


remote probe 2848 .

work.
Automatic.
Add Sensor
Sensor Settings
2192 02.02.2015
priority).
SENSOR DISPLAY
for each channel.
02.02.2015 2193
SENSOR DISPLAY
Inherited Settings
described below.
2194 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 2195

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
2196 02.02.2015
menu bar.
dependent on.
02.02.2015 2197
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

Notifications
2198 02.02.2015
Others
02.02.2015 2199
201 Windows Updates Status (Powershell) Sensor
6.8.201 Windows Updates Status (Powershell) Sensor
The Windows Updates Status (Powershell) sensor monitors the status of Windows updates on
a computer and counts the available and installed Windows updateseither from Microsoft or
from the local Windows Server Update Services (WSUS) server.
Elapsed time since the last update

Installed Windows updates
Missing Windows updates
Installed security updates with low, moderate, important, and critical priority
Missing security updates with low, moderate, important, and critical priority
You can find the considered updates in Server Manager (WSUS) under Roles | Windows Server
Updat e Services | Updat e Services | Comput ers | Report s.
Windows Updates Status (Powershell) Sensor
2200 02.02.2015
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_updates_status_powershell.png
Remarks
Requires 2201 Remote PowerShell to be enabled on the target system and PowerShell 2.0 on
the probe system.
sensor on.
Note: If the sensor cannot determine the "Time since last update" (for example, because the
list of updates is empty), it will show the value -1s and turn into a Warning status 123 .
Note: We recommend setting the scanning interval 2203 of this sensor to at least 12 hours to
limit the load on the server being monitored.

Requirement: Remote PowerShell

The Windows Updates Status (Powershell) sensor uses PowerShell commands. To monitor
devices with this sensor, Remot e PowerShell access has to be enabled on the target
computer. Also ensure that you have installed PowerShell 2.0 or later on your probe machine.
Add Sensor
02.02.2015 2201
Sensor Settings
priority).
SENSOR DISPLAY
for each channel.
2202 02.02.2015
SENSOR DISPLAY
Inherited Settings
described below.
02.02.2015 2203
SCANNING INTER VAL
Choose between:
option will apply.
2204 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2205
menu bar.
dependent on.
2206 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More

02.02.2015 2207

Notifications
Others
2208 02.02.2015
202 WMI Custom Sensor
6.8.202 WM I Custom Sensor
The WMI Custom Sensor performs a custom query via Windows Management Instrumentation
(WMI).
It shows the retrieved value.
Note: Your Windows Management Instrumentation Query Language (WQL) query code must be
stored in a file on the system of the probe the sensor is created on: If used on a remote
probe, the file must be stored on the system running the remote probe. In a cluster setup,
please copy the file to every cluster node.
Save the file with the query into the \Cust om Sensors\WMI WQL script s subfolder of your
PRTG installation. See section Dat a St orage 2871 for more information about how to find this
path
WMI Custom Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_c ustom.png
Remarks
sensor on.
Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high
impact on the system performance! Try to stay below 200 WMI sensors per probe 77 . Above
this number, please consider using multiple Remot e Probes 2848 for load balancing.
For a general introduction to the technology behind WMI, please see manual section
Monit oring via WMI 2753 .
02.02.2015 2209
Add Sensor
Channel Name Enter a name for the channel in which PRTG shows the received
data. This name will be displayed in graphs and tables. Please enter
a string. You can change the name later in the sensor's channel
settings 2477 .
WQL File Select a file that this sensor will use from the list. The sensor
executes it with every scanning interval. The menu contains WQL
scripts from the \Cust om Sensors\WMI WQL script s subfolder of
your PRTG installation. Please store your script there.
If used on a remote probe, you must store the file on the system
running the remote probe. If used on a cluster probe, you must
store the file on all servers running a cluster node. For more
information on how to find this path, please see Dat a St orage 2871
section.
Note: Your query must return an integer or float value. Strings are
not supported!
Sensor Settings
2210 02.02.2015
priority).
Namespace Enter the namespace for the query.
WQL File Shows the WQL file that this sensor executes with every scanning
interval. Once a sensor is created, you cannot change this value. It
Placeholder <#PH1> In your WQL script, you can use up to three placeholders that you
can assign a value to using this field. Please enter a string for
variable <#PH1> or leave the field empty.
change.
02.02.2015 2211
Unit String Enter a unit for the data that the sensor receives from your script.
This is for displaying purposes only. The unit will be displayed in
graphs and tables. Please enter a string.
Multiplication Define a multiplier for the received values. By default, this is set to
1 in order to not change received values. Please enter an integer
value.
Division Define a divisor for the received values. By default, this is set to 1
in order to not change received values. Please enter an integer
value.
SENSOR DISPLAY
for each channel.
2212 02.02.2015
Inherited Settings
described below.
02.02.2015 2213
SCANNING INTER VAL
Choose between:
option will apply.
2214 02.02.2015

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
02.02.2015 2215
menu bar.
dependent on.
2216 02.02.2015
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
More
Knowledge Base: How do I properly configure a WMI custom sensor?

My WMI sensors don't work. What can I do?


02.02.2015 2217
Notifications
Others
2218 02.02.2015
203 WMI Custom String Sensor
6.8.203 WM I Custom String Sensor
The WMI Custom String sensor performs a custom string query via Windows Management
Instrumentation (WMI).
It shows the retrieved string value in the sensor message.

It shows also the response time.
Note: Your Windows Management Instrumentation Query Language (WQL) query code must be
stored in a file on the system of the probe the sensor is created on: If used on a remote
probe, the file must be stored on the system running the remote probe. In a cluster setup,
please copy the file to every cluster node.
WMI Custom String Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_c ustom_string.png
Remarks
sensor on.
02.02.2015 2219
Add Sensor
Channel Name Enter a name for the channel in which the received data will be
presented. The name will be displayed in graphs and tables. Please
enter a string. You can change the name later in the sensor's
channel settings 2477 .
WQL File Select a file that will be used for this sensor from the drop down
menu. It will be executed with every scanning interval. The menu
contains WQL scripts from the \Cust om Sensors\WMI WQL
script s sub folder of your PRTG installation. Please store your
script there. If used on a remote probe, the file must be stored on
the system running the remote probe. If used on a cluster probe,
you must store the file on all servers running a cluster node! For
more information on how to find this path, please see Dat a
St orage 2871 section.
Sensor Settings
2220 02.02.2015
priority).
Namespace Enter the namespace for the query.
WQL File Shows the name of the file that this sensor uses. Once a sensor is
anew.
Unit String Enter a unit for the data that will be received by your script. This is
for displaying purposes only. The unit will be displayed in graphs
and tables. Please enter a string.
change.
02.02.2015 2221

Response Must Include Define which string must be part of the data that is received form
the WMI object. You can either enter plain text or a Regular
Expression 2846 . If the data does not include the search pattern, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
Response Must Not Define which string must not be part of the data that is received
Include form the WMI object. You can either enter plain text or a Regular
Expression 2846 . If the data does include the search pattern, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
plain text search.
Expression 2846 .
Maximum Length of Define the maximum allowed length of the string that will be
String received from the WMI object. If it is longer than this value, the
sensor will be set to an error status. Please enter an integer value
Extract Number Using Define if you want to filter out a numeric value from the string
Regular Expression received from the WMI object. You can convert this into a float
value, in order to use it with channel limits (see Sensor Channels
Set t ings 2477 ).
No ext ract ion: Do not extract a float value. Use the result as a
string value.
Ext ract a numeric value using a regular expression: Use a
regular expression to identify a numeric value in the string and
convert it to a float value. Define below. See also the example
2228 below.
2222 02.02.2015
Regular Expression This setting is only visible if number extraction is enabled above.
Enter a Regular Expression 2846 to identify the numeric value you
want to extract from the string returned by the WMI object. You
can use capturing groups here. Make sure the expression returns
numbers only (including decimal and thousands separators). The
result will be further refined by the settings below.
Index of Capturing This setting is only visible if number extraction is enabled above. If
Group your regular expression uses capturing groups, specify which one
will be used to capture the number. Please enter an integer value
Decimal Separator This setting is only visible if number extraction is enabled above.
Define which character to use as decimal separator for the number
extracted above. Please enter a string or leave the field empty.
Thousands Separator This setting is only visible if number extraction is enabled above.
Define which character to use as thousands separator for the
number extracted above. Please enter a string or leave the field
empty.
between:
SENSOR DISPLAY
02.02.2015 2223
SENSOR DISPLAY

for each channel.
Inherited Settings
described below.
2224 02.02.2015
SCANNING INTER VAL
Choose between:
option will apply.
02.02.2015 2225

settings.

between:
be set.
maintenance window.
maintenance window.
maintenance window.

can choose between:
2226 02.02.2015
menu bar.
dependent on.
02.02.2015 2227
ACCESS R IGHTS
monitoring results.
rights settings.
option.
Access Right s 96 .
Example: Number Extraction with Regular Expression

If you want to extract a number in the response string using a regular expression, please note
that the index for captures in this sensor is based on 1 (not on 0). Furthermore, capturing
groups are not created automatically. The example below will illustrate this issue.
Consider the following string as returned by a request for CPU usage:

5 Sec (3.49%), 1 Min (3.555%), 5 Min (3.90%)
Assuming you would like to filter for the number 3.555, i.e., the percentage in the second
parentheses. Then enter the following regex in the Regular Expression field:
(\d+\.\d+).*(\d+\.\d+).*(\d+\.\d+)
As Index of Capt uring Group enter 3. This will extract the desired number 3.555.
2228 02.02.2015
The index has to be 3 in this case because the capturing groups here are the following:
Group 1 contains "3.49%), 1 Min (3.555), 5 Min (3.90"

Please keep in mind this note about index and capturing groups when using number
extraction.
More
My WMI sensors don't work. What can I do?

Notifications
Others
02.02.2015 2229
204 WMI Event Log Sensor
6.8.204 WM I Event Log Sensor
The WMI Event Log sensor monitors a specific Windows log file using Windows Management
Instrumentation (WMI).
It shows the number of new records per second.
You can set the sensor to a desired status individually according to a new event log entry. For
details and how to find out the correct filter, see section More 2239 .
WMI Ev ent Log Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_ev ent_log.png
Remarks
sensor on.
2230 02.02.2015
Add Sensor
Select the log files you want to monitor. PRTG creates one sensor for each log you choose in
are created.
WMI EVENT LOG MONITOR
Log File The Windows event log provides several different log files. You see
table head.
Sensor Settings
02.02.2015 2231
priority).
WMI EVENT LOG MONITOR
Log File Shows the Windows log file that this sensor monitors. Once a
the sensor anew.
between:
Event Type Specify the type of event that this sensor processes. Other event
type cannot be processed. Choose between the following event
types:
Any
Error
Warning
Informat ion
Securit y Audit Success
Securit y Audit Failure
Filter by Source Filter all received events for a certain event source. If you enable
2232 02.02.2015
Off: Do not filter by event source.

On: Enable filtering by event source.
Match String (Event This field is only visible if you enable source filtering above. Enter a
Source) source from which the events come from. Only events from a
source matching this string are regarded, other events are ignored.
Filter by ID Filter all received events for a certain event ID. If you enable this
defined value(s). Choose between:
Off: Do not filter by event ID.
On: Enable filtering by event ID.
Match Value (Event ID) This field is only visible if you enable ID filtering above. Enter an
event ID which the events must have. Only events with an ID that
matches this value are regarded.
Note: The Event Log (Windows API) Sensor 473 supports more
than one event ID. Using this sensor type, you can enter a comma
separated list of event IDs to filter for more than one ID.
Note: The WMI Event Log Sensor 2230 supports filtering for only
one ID.
Filter by Category Filter all received events for a certain event category. If you enable
Off: Do not filter by event category.
On: Enable filtering by event category.
Match String (Event This field is only visible if you enable category filtering above. Enter
Category) a category which the events must have. Only events with a
category that matches this string are regarded. Please enter a
string.
Filter by User Filter all received events for a certain event user. If you enable this
Off: Do not filter by event user.
On: Enable filtering by event user.
02.02.2015 2233
Part 6: Ajax Web InterfaceDevice and S

PRTG Ver 13 Manual Usuario

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PRTG Ver 13 Manual Usuario

Uploaded by

Copyright:

Available Formats

PRTG Net work Monit or User Manual

Printed: Februar 2015 in Nuremberg

Part 1 Welcome to PRTG Network M onitor 14

Part 2 Quick Start Guide 32

Part 3 Installing the Software 44

Part 4 Understanding Basic Concepts 76

Part 5 Ajax Web InterfaceBasic Procedures 102

4 Sensor States 123

Part 6 Ajax Web InterfaceDevice and Sensor Setup 196

Exchange Database (Powershell) Sensor 493

Passive Application Performance Sensor 1020

SNMP HP ProLiant Memory Controller Sensor 1482

SSH VMWare ESX(i) Disk Sensor 1943

WMI Vital System Data (V2) Sensor 2426

Part 7 Ajax Web InterfaceAdvanced Procedures 2496

Optional Downloads and Add-Ons 2680

Part 8 Enterprise Console 2688

Part 9 Other User Interfaces 2740

Part 10 Sensor Technologies 2748

Part 11 PRTG Administration Tool 2794

Part 12 Advanced Topics 2826

1 Active Directory Integration 2827

Part 13 Appendix 2878

1 Welcome to PRTG Network Monitor

Why Network Monitoring is Important

1. Set up a well-planned network with reliable components.

Monitoring Networks with PRTG Network Monitor

1.1 About this Document

1.2 Key Features

What PRTG Can Be Used For

What PRTG Includes

1.3 New in This Version

Paessler Blog: Version 12 of PRTG introduces "Continuous Rollout"

1.4 Available Licenses

Is for free for personal and commercial use.

Can monitor an unlimited number of sensors.

Can monitor maximum number of sensors (from 100 to unlimited).

Paessler Website: Request a Free PRTG Trial Key for Evaluation

1.5 System Requirements

Planning an Installation With Hundreds of Sensors or More?

In general, consider the following rules:

SNMP V1 and V2, Ping, Port , and HTTP

Ot her sensor t y pes

Knowledge Base: Planning Large Installations of PRTG Network Monitor

Knowledge Base: How can I speed up PRTGespecially for large installations?

Knowledge Base: Increasing Maximum Connections for VMware Sensors

Knowledge Base: Checklist for Running PRTG on VMware

Knowledge Base: Which ports does PRTG use on my system?

Knowledge Base: Which .NET version does PRTG require?

1.5.1 Detailed Sy stem Requirements

Support ed Operat ing Sy st ems 23

Net work Size: Recommendat ions 25

Running PRTG on Virt ual Machines 26

Running PRTG in a Failover Clust er 26

Web Browser Requirement s 27

Screen Resolut ion 27

Requirement s for Monit ored Devices 27

Requirement s for t he Ent erprise Console 27

Requirement s for Mobile Web GUI 28

Requirement s for Smart phones 28

Supported Operating Systems

Microsoft Windows Server 2012 R2** (recommended)

the operating system is a 64-bit Windows system, and