Prtgmanual PDF

PRTG Net work Monit or User Manual
© 2017 Paessler AG
All rights reserved. No parts of this work may be reproduced in any form or by any means—graphic,
electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval
systems—without 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: December 2017 in Nuremberg

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

1 About this Document 16
2 Key Features 17
3 New in This Version 20
4 Available Licenses 21
5 System Requirements 23
Detailed System Requirements 26
6 Introduction: Monitoring with PRTG 34
Part 2 Quick Start Guide 46

1 ONE—Download, Installation, and First Login 48
2 TWO—Smart Setup 52
Part 3 Using PRTG in the Cloud 62

1 Create a PRTG in the Cloud Instance 63
2 Manage a PRTG in the Cloud Subscription 69
Part 4 Installing the Software 76

1 Download PRTG 77
2 Update From Previous Versions 79
3 Install a PRTG Core Server 85
4 Install a PRTG Cluster 89
5 Enter a License Key 90
6 Activate the Product 92
7 Install a PRTG Remote Probe 94
8 Install the Enterprise Console 105
9 Uninstall PRTG Products 111
Part 5 Understanding Basic Concepts 116

1 Architecture and User Interfaces 117
2 Clustering 122
3 Object Hierarchy 125
4 Inheritance of Settings 129
5 Tags 131
6 Dependencies 133
7 Scheduling 134
8 Notifying 135
Alerts 136
9 User Access Rights 148
10 Data Reporting 152
11 IPv6 153
3
Contents
Part 6 Ajax Web Interface—Basic Procedures 156

1 Login 158
2 SSL Certificate Warning 162
3 Welcome Page 165
Customer Service 168
4 General Layout 170
5 Sensor States 183
6 Review Monitoring Data 186
7 Historic Data Reports 192
8 Similar Sensors 197
9 Recommended Sensors 201
10 Object Settings 205
11 Alarms 207
12 System Information 210
13 Logs 216
14 Tickets 218
15 Working with Table Lists 225
16 Object Selector 228
17 Priority and Favorites 229
18 Pause 232
19 Context Menus 234
20 Hover Popup 249
21 Main Menu Structure 250
Part 7 Ajax Web Interface—Device and Sensor Setup 266

1 Auto-Discovery 267
2 Create Objects Manually 285
Add a Group 286
Add a Device 295
Add a Sensor 309
3 Manage Device Tree 312
4 Root Group Settings 314
5 Probe Settings 334
6 Group Settings 358
7 Device Settings 385
8 Sensor Settings 411
List of Available Sensor Types 412
Active Directory Replication Errors Sensor 435
ADO SQL v2 Sensor 445
Amazon CloudWatch Alarm Sensor 461
Amazon CloudWatch EBS Sensor 471
Amazon CloudWatch EC2 Sensor 483
Amazon CloudWatch ElastiCache Sensor 495
Amazon CloudWatch ELB Sensor 508
Amazon CloudWatch RDS Sensor 520
Amazon CloudWatch SNS Sensor 532
4
Contents
Amazon CloudWatch SQS Sensor 544

Business Process Sensor 556
Cisco IP SLA Sensor 568
Citrix XenServer Host Sensor 577
Citrix XenServer Virtual Machine Sensor 587
Cloud HTTP Sensor 597
Cloud Ping Sensor 606
Cluster Health Sensor 615
Common SaaS Sensor 620
Core Health Sensor 628
Dell PowerVault MDi Logical Disk Sensor 635
Dell PowerVault MDi Physical Disk Sensor 644
DHCP Sensor 654
DNS Sensor 664
Docker Container Status Sensor 673
Dropbox Sensor 683
Enterprise Virtual Array Sensor 693
Event Log (Windows API) Sensor 703
Exchange Backup (Powershell) Sensor 713
Exchange Database (Powershell) Sensor 722
Exchange Database DAG (Powershell) Sensor 733
Exchange Mail Queue (Powershell) Sensor 743
Exchange Mailbox (Powershell) Sensor 753
Exchange Public Folder (Powershell) Sensor 763
EXE/Script Sensor 772
EXE/Script Advanced Sensor 784
File Sensor 796
File Content Sensor 805
Folder Sensor 815
FTP Sensor 825
FTP Server File Count Sensor 834
GitLab Build Status Sensor 844
Google Analytics Sensor 853
Google Drive Sensor 865
HTTP Sensor 875
HTTP Advanced Sensor 885
HTTP Apache ModStatus PerfStats Sensor 901
HTTP Apache ModStatus Totals Sensor 911
HTTP Content Sensor 921
HTTP Data Advanced Sensor 933
HTTP Full Web Page Sensor 946
HTTP Push Count Sensor 957
HTTP Push Data Sensor 966
HTTP Push Data Advanced Sensor 977
HTTP Transaction Sensor 988
HTTP XML/REST Value Sensor 1002
Hyper-V Cluster Shared Volume Disk Free Sensor 1017
Hyper-V Host Server Sensor 1028
Hyper-V Virtual Machine Sensor 1037
Hyper-V Virtual Network Adapter Sensor 1048
Hyper-V Virtual Storage Device Sensor 1058
5
Contents
IMAP Sensor 1067

IP on DNS Blacklist Sensor 1081
IPFIX Sensor 1090
IPFIX (Custom) Sensor 1104
IPMI System Health Sensor 1116
jFlow V5 Sensor 1126
jFlow V5 (Custom) Sensor 1140
LDAP Sensor 1153
Microsoft OneDrive Sensor 1160
Microsoft SQL v2 Sensor 1170
MySQL v2 Sensor 1187
NetApp Aggregate Sensor 1203
NetApp I/O Sensor 1214
NetApp LIF Sensor 1225
NetApp LUN Sensor 1235
NetApp NIC Sensor 1246
NetApp Physical Disk Sensor 1256
NetApp SnapMirror Sensor 1266
NetApp System Health Sensor 1277
NetApp Volume Sensor 1288
NetFlow V5 Sensor 1299
NetFlow V5 (Custom) Sensor 1313
NetFlow V9 Sensor 1326
NetFlow V9 (Custom) Sensor 1340
Oracle SQL v2 Sensor 1353
Oracle Tablespace Sensor 1369
Packet Sniffer Sensor 1379
Packet Sniffer (Custom) Sensor 1392
PerfCounter Custom Sensor 1404
PerfCounter IIS Application Pool Sensor 1414
Ping Sensor 1424
Ping Jitter Sensor 1433
POP3 Sensor 1442
Port Sensor 1451
Port Range Sensor 1461
PostgreSQL Sensor 1469
Probe Health Sensor 1484
Python Script Advanced Sensor 1491
QoS (Quality of Service) One Way Sensor 1501
QoS (Quality of Service) Round Trip Sensor 1510
RADIUS v2 Sensor 1520
RDP (Remote Desktop) Sensor 1530
REST Custom Sensor 1538
Share Disk Free Sensor 1562
Sensor Factory Sensor 1570
sFlow Sensor 1589
sFlow (Custom) Sensor 1603
SFTP Secure File Transfer Protocol Sensor 1615
SIP Options Ping Sensor 1624
SMTP Sensor 1633
SMTP&IMAP Round Trip Sensor 1642
6
Contents
SMTP&POP3 Round Trip Sensor 1653

SNMP APC Hardware Sensor 1664
SNMP Buffalo TS System Health Sensor 1673
SNMP Cisco ADSL Sensor 1681
SNMP Cisco ASA VPN Connections Sensor 1689
SNMP Cisco ASA VPN Traffic Sensor 1699
SNMP Cisco ASA VPN Users Sensor 1710
SNMP Cisco CBQoS Sensor 1720
SNMP Cisco System Health Sensor 1729
SNMP Cisco UCS Blade Sensor 1738
SNMP Cisco UCS Chassis Sensor 1746
SNMP Cisco UCS Physical Disk Sensor 1755
SNMP Cisco UCS System Health Sensor 1763
SNMP CPU Load Sensor 1771
SNMP Custom Sensor 1779
SNMP Custom Advanced Sensor 1788
SNMP Custom String Sensor 1798
SNMP Custom String Lookup Sensor 1810
SNMP Custom Table Sensor 1820
SNMP Dell EqualLogic Logical Disk Sensor 1832
SNMP Dell EqualLogic Member Health Sensor 1841
SNMP Dell EqualLogic Physical Disk Sensor 1851
SNMP Dell Hardware Sensor 1860
SNMP Dell PowerEdge Physical Disk Sensor 1869
SNMP Dell PowerEdge System Health Sensor 1879
SNMP Disk Free Sensor 1889
SNMP Hardware Status Sensor 1897
SNMP HP BladeSystem Blade Sensor 1905
SNMP HP BladeSystem Enclosure System Health Sensor 1913
SNMP HP LaserJet Hardware Sensor 1921
SNMP HP ProLiant Logical Disk Sensor 1930
SNMP HP ProLiant Memory Controller Sensor 1939
SNMP HP ProLiant Network Interface Sensor 1948
SNMP HP ProLiant Physical Disk Sensor 1957
SNMP HP ProLiant System Health Sensor 1966
SNMP IBM System X Logical Disk Sensor 1975
SNMP IBM System X Physical Disk Sensor 1984
SNMP IBM System X Physical Memory Sensor 1993
SNMP IBM System X System Health Sensor 2002
SNMP interSeptor Pro Environment Sensor 2011
SNMP Juniper NS System Health Sensor 2019
SNMP LenovoEMC Physical Disk Sensor 2027
SNMP LenovoEMC System Health Sensor 2036
SNMP Library Sensor 2044
SNMP Linux Disk Free Sensor 2058
SNMP Linux Load Average Sensor 2069
SNMP Linux Meminfo Sensor 2077
SNMP Linux Physical Disk Sensor 2085
SNMP Memory Sensor 2094
SNMP NetApp Disk Free Sensor 2103
SNMP NetApp Enclosure Sensor 2112
7
Contents
SNMP NetApp I/O Sensor 2121

SNMP NetApp License Sensor 2130
SNMP NetApp Logical Unit Sensor 2138
SNMP NetApp Network Interface Sensor 2147
SNMP NetApp System Health Sensor 2155
SNMP Poseidon Environment Sensor 2164
SNMP Printer Sensor 2172
SNMP QNAP Logical Disk Sensor 2180
SNMP QNAP Physical Disk Sensor 2188
SNMP QNAP System Health Sensor 2197
SNMP RMON Sensor 2205
SNMP SonicWALL System Health Sensor 2216
SNMP SonicWALL VPN Traffic Sensor 2224
SNMP Synology Logical Disk Sensor 2233
SNMP Synology Physical Disk Sensor 2241
SNMP Synology System Health Sensor 2249
SNMP System Uptime Sensor 2257
SNMP Traffic Sensor 2265
SNMP Trap Receiver Sensor 2277
SNMP Windows Service Sensor 2290
SNTP Sensor 2298
SSH Disk Free Sensor 2305
SSH INodes Free Sensor 2318
SSH Load Average Sensor 2328
SSH Meminfo Sensor 2337
SSH Remote Ping Sensor 2346
SSH SAN Enclosure Sensor 2356
SSH SAN Logical Disk Sensor 2367
SSH SAN Physical Disk Sensor 2378
SSH SAN System Health Sensor 2389
SSH Script Sensor 2399
SSH Script Advanced Sensor 2412
SSL Certificate Sensor 2424
SSL Security Check Sensor 2434
Syslog Receiver Sensor 2443
System Health Sensor 2456
TFTP Sensor 2462
Traceroute Hop Count Sensor 2470
VMware Datastore (SOAP) Sensor 2479
VMware Host Hardware (WBEM) Sensor 2490
VMware Host Hardware Status (SOAP) Sensor 2499
VMware Host Performance (SOAP) Sensor 2509
VMware Virtual Machine (SOAP) Sensor 2519
Windows CPU Load Sensor 2529
Windows IIS 6.0 SMTP Received Sensor 2539
Windows IIS 6.0 SMTP Sent Sensor 2548
Windows IIS Application Sensor 2557
Windows MSMQ Queue Length Sensor 2566
Windows Network Card Sensor 2577
Windows Pagefile Sensor 2588
Windows Physical Disk I/O Sensor 2597
8
Contents
Windows Print Queue Sensor 2607

Windows Process Sensor 2618
Windows System Uptime Sensor 2628
Windows Updates Status (Powershell) Sensor 2637
WMI Custom Sensor 2647
WMI Custom String Sensor 2657
WMI Event Log Sensor 2669
WMI Exchange Server Sensor 2680
WMI Exchange Transport Queue Sensor 2690
WMI File Sensor 2700
WMI Free Disk Space (Multi Disk) Sensor 2709
WMI HDD Health Sensor 2721
WMI Logical Disk I/O Sensor 2731
WMI Memory Sensor 2740
WMI Microsoft SQL Server 2005 Sensor (Deprecated) 2749
WMI Microsoft SQL Server 2008 Sensor 2762
WMI Remote Ping Sensor 2810
WMI Security Center Sensor 2819
WMI Service Sensor 2829
WMI Share Sensor 2839
WMI SharePoint Process Sensor 2849
WMI Terminal Services (Windows 2008+) Sensor 2858
WMI Terminal Services (Windows XP/Vista/2003) Sensor 2866
WMI UTC Time Sensor 2874
WMI Vital System Data (V2) Sensor 2882
WMI Volume Sensor 2892
WSUS Statistics Sensor 2901
9 Additional Sensor Types (Custom Sensors) 2911
10 Sensor Channels Settings 2915
11 Sensor Notifications Settings 2924
Part 8 Ajax Web Interface—Advanced Procedures 2938

1 Toplists 2940
2 Arrange Objects 2945
3 Clone Object 2946
4 Multi-Edit 2949
5 Create Device Template 2954
6 Show Dependencies 2959
7 Geo Maps 2961
8 Notifications 2966
Setting up Notifications Based on Sensor Limits: Example 2969
Setting up Notifications Based on Libraries: Example 2978
9 Libraries 2984
Libraries Step By Step 2987
Management 2991
Libraries and Node Settings 2993
9
Contents
Context Menus 2999

10 Reports 3000
Reports Step By Step 3005
View and Run Reports 3009
Report Settings 3013
11 Maps 3026
Maps Step By Step 3031
Map Designer 3034
Maps Settings 3043
12 Setup 3048
Account Settings—My Account 3050
Account Settings—Notifications 3057
Account Settings—Notification Contacts 3075
Account Settings—Schedules 3079
System Administration—User Interface 3084
System Administration—Monitoring 3096
System Administration—Notification Delivery 3102
System Administration—Core & Probes 3108
System Administration—User Accounts 3116
System Administration—User Groups 3123
System Administration—Administrative Tools 3128
System Administration—Cluster 3133
PRTG Status—System Status 3135
PRTG Status—Auto-Update 3146
PRTG Status—Cluster Status 3150
PRTG Status—Licensing Status and Settings 3152
Optional Downloads and Tools 3158
Desktop Notifications 3160
Support—Contact Support 3162
Part 9 Enterprise Console 3168

1 First Start 3171
2 General Layout 3172
3 Menu Tabs and Page Content 3176
Devices 3177
Libraries 3184
Sensors 3186
Alarms 3188
Maps 3190
Reports 3192
Logs 3194
Tickets 3196
Setup 3198
Search Results 3200
4 PRTG Servers 3201
5 Options 3204
6 Windows Menu Structure 3210
7 Context Menus 3218
8 Shortcuts Overview 3219
10
Contents
Part 10 PRTG Apps for M obile Network M onitoring 3222
Part 11 Sensor Technologies 3226

1 Monitoring via SNMP 3227
Choosing the Right SNMP Sensor 3232
2 Monitoring via WMI 3244
3 Monitoring via SSH 3247
4 Monitoring Bandwidth via Packet Sniffing 3249
5 Monitoring Bandwidth via Flows 3251
6 Bandwidth Monitoring Comparison 3254
7 Monitoring Quality of Service and VoIP 3256
8 Monitoring Email Round Trip 3261
9 Monitoring Backups 3263
10 Monitoring Virtual Environments 3264
11 Monitoring Databases 3271
12 Monitoring Syslogs and SNMP Traps 3276
13 Monitoring via Push 3284
14 Monitoring via HTTP 3288
Part 12 PRTG Administration Tool 3296

1 PRTG Administration Tool on Core Server System 3297
2 PRTG Administration Tool on Remote Probe Systems 3319
Part 13 Advanced Topics 3332

1 Active Directory Integration 3333
2 Application Programming Interface (API) Definition 3336
3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors 3337
4 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors 3342
5 Define IP Ranges 3344
6 Define Lookups 3345
7 Regular Expressions 3355
8 Calculating Percentiles 3357
9 Add Remote Probe 3358
Remote Probes and Multiple Probes 3359
Remote Probe Quick Setup 3362
Remote Probe Setup Using Installer 3368
10 Failover Cluster Configuration 3369
Failover Cluster Step by Step 3376
11 Data Storage 3383
12 Using Your Own SSL Certificate with PRTG's Web Server 3385
Part 14 Appendix 3388

1 Glossary 3389
2 List of Abbreviations 3397
3 List of Icons 3402
11
Contents
4 Support and Troubleshooting 3403

5 Differences between PRTG on Premises and PRTG in the Cloud 3404
6 Legal Notices 3414
Index 0
12
Part 1
Welcome to PRTG Network Monitor
11/24/2017 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.
A PRTG Network Monitor Standard Installation
Why Network Monitoring is Important

Today, nearly every business relies 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 economic success of an organization is tightly connected to a hitch-free flow
of data.
That's why your computer network has to work successfully: reliability, speed, and efficiency
are crucial. 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.
So 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 the network to get informed about failures when 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.
14 11/24/2017
Part 1: Welcome to PRTG Network Monitor |
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, even on remote
machines. PRTG 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.
PRTG Network Monitor offers two options to monitor your network: PRTG on premises and
PRTG in the cloud. With PRTG on premises, the core server and local probe run within your
network. PRTG in the cloud is the PRTG cloud solution, where we at Paessler run the core
server and cloud probe for you. The PRTG web interface 156 for monitoring configuration and
reviewing monitoring data is the same for both, PRTG in the cloud and PRTG on premises.
Do you want to get an overview of PRTG in 90 seconds? See this video on our website:
PRTG Network Monitor in 90 Seconds
More
Video Demo: PRTG Network Monitor in 90 Seconds
§ https://www.paessler.com/support/videos/about-paessler/prtg-90-sec
Video Demo: What is Unified Monitoring?
§ https://www.paessler.com/support/videos/all-about-monitoring
11/24/2017 15
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 to be a reference for all available settings in PRTG. Short
contextual help is already provided within the Ajax web interface of PRTG. In this manual you
often get some more help regarding the different options that are available. No matter whether
you use PRTG in the cloud or PRTG on premises, you will find all of the information that you
need in this document.
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, see the Quick St art Guide 46 section. To learn more
about monitoring with PRTG, see section Int roduct ion: Monit oring wit h PRTG 34 . For
more detailed instructions, browse the manual content or use the manual search with
keywords and choose the section you want to read.
For an overview of the icons and abbreviations that are used in this document, see the
Appendix 3388 section.
16 11/24/2017
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
1.2 Key Features

PRTG Network Monitor follows and analyzes your network and requires no third-party
software. It's quick to download and install, or you create a PRTG instance in the cloud with a
few clicks. PRTG will be up and running in a just a few minutes including a first auto-
configuration. Smart Set up 52 , the built-in interactive guidance dialog, will lead you through
the whole process.
What is PRTG for?
Monitoring with PRTG
§ Monitoring and alerting you to up and downtimes or slow servers

§ System health monitoring of your various hardware devices
§ Network device monitoring, bandwidth accounting
12/11/2017 17
§ Application monitoring
§ Monitoring virtual servers
§ Service Level Agreement (SLA) monitoring
§ System usage monitoring (for example, CPU loads, free memory, free disk space)
§ Database performance and table values monitoring
§ Email server monitoring and reviewing various backup solutions
§ Monitoring your network's physical environment
§ Classifying network traffic by source or destination, as well as content
§ Discovering unusual, suspicious, or malicious activity with devices or users
§ Measuring Quality of Service (QoS) and Voice over IP (VoIP) parameters
§ Cloud monitoring services
§ Discovering and evaluating network devices
§ Collecting system information for various hardware types
§ Finding unexpected relationships between your network components to detect potential
security issues and assessing the real usage of your network and hardware
§ Fail-safe monitoring using a failover cluster setup
What is Included in PRTG?

The PRTG on premises installer or a PRTG in the cloud instance contains everything necessary
to run your monitoring system immediately without any third-party modules.
§ High performance: the fast and efficient database system that PRTG includes stores 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 on multiple probes.
§ Low system requirements: For PRTG on premises an average PC (not older than 2 years) is
sufficient and even a netbook can monitor over a thousand sensors. For detailed system
requirements see here 23 . PRTG in the cloud does not even require any hardware for the
PRTG core server!
§ High security standards: SSL encryption for connections and web servers, a personalized
user rights management, and much more.
§ A 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 pages.
§ A built-in email relay server for automatic email delivery.
§ Customizable, personalized alerting
§ Various notification technologies, for example, email, push, SMS text messages, syslog and
SNMP traps, HTTP requests, event logs, Amazon SNS, executing scripts.
18 12/11/2017
§ Multiple triggers, for example, status alerts, limit alerts, threshold alerts, multiple condition
alerts, escalation alerts.
§ Gradual dependencies to avoid alarm floods, acknowledging certain 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,
PDF, and as CSV or XML data files. Several report templates are available by default.
§ Graphics engine for user-friendly live and historic data graphs.
§ Network analysis modules 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 dashboards—private and public—including live performance
and status information. You can design these maps as you like with many different objects,
as well as integrate external custom objects.
§ Multiple languages such as English, German, Spanish, French, Portuguese, Dutch, Japanese,
Russian, and Simplified Chinese.
§ Customization: The PRTG Application Programming Interface (API) allows you to develop your
own features. Additionally, you can create custom sensors, notifications, and device
templates according to your specific requirements.
PRTG Network Monitor supports monitoring up to several thousand sensors per installation,
depending on various parameters. It can optionally work with multiple remote probes to
monitor multiple sites or network segments from one central core installation, and to
distribute high monitoring 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 that has been constantly
improving since 1997. There are already more than 200,000 PRTG installations running all over
the world. Our outstanding support 3162 ensures your inquiries are answered within one
business day for best possible network monitoring. Attractive licensing packages from
freeware (up to 100 sensors) to enterprise level (with thousands of sensors) and the free
choice between PRTG on premises and PRTG in the cloud make sure every user finds the best-
possible solution.
12/11/2017 19
Part 1: Welcome to PRTG Network Monitor | 3 New in This Version
1.3 New in This Version

Our continuous development and rollout constantly improves and expands the functionalities
provided by PRTG. Instead of delivering only a few versions each year with massive changes in
every update, PRTG is automatically and seamlessly enhanced with new features and fixes—fast
and with high quality.
We provide three release channels for PRTG on premises:
§ St able: Best tested version of PRTG for live systems. It is updated about once or twice a
month and for use on live systems.
§ Preview: Offers the latest features and fixes and is updated several times a month. Consider
this version as "beta", so do not use this version on live systems you depend on!
§ Canary : Providing "nightly builds" and is updated very often. It is not tested extensively.
Never use on live systems you depend on!
Via these three channels, you can choose either maximum stability, early access to new
features, or a mix of both.
PRTG in the cloud does not have release channels. Instead, we roll out the latest Stable
version to PRTG in the cloud instances in stages.
For an overview of all recent changes in the current version, visit the release notes for the
stable release channel on our website.
More
Paessler Website: Release Notes for the "Stable" Release Channel
§ https://www.paessler.com/prtg/history/stable
Paessler Website: PRTG Network Monitor Version History
§ https://www.paessler.com/prtg/history
Paessler Blog: Version 12 of PRTG will introduce "Continuous Rollout"
§ https://www.paessler.com/blog/prtg-12-introduces-continuous-rollout
20 12/11/2017
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
1.4 Available Licenses

Our licenses count by sensors. We define one sensor as one aspect that you monitor on a
device.
There are three different PRTG flavors available.
Freeware Edition
The Freeware Edition is a good solution to get started with PRTG or for private use:
§ Free for personal and commercial use.

§ Can monitor up to 100 sensors.
§ Supports all available sensor types.
If you want to use the Freeware Edition, please first install the Trial Edit ion 21 and get a
free trial key. After the trial period has ended, your Trial Edition automatically turns into a
Freeware Edition.
This option is not available in PRTG in the cloud.
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.

§ For PRTG on premises you have to request the temporary license key from our website.
Usually you see the license details including the key if you click the free download button on
paessler.com
§ The trial period of PRTG on premises is limited to 30 days and automatically reverts to
Freeware Edition 21 afterwards.
§ PRTG in the cloud provides a 10 days trial. Afterwards, your instance will be deleted if you do
not purchase a commercial edition.
§ Each PRTG on premises license includes one single failover cluster setup 122 , consisting of
two nodes. 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 PRTG on premises Trial Edition automatically turns into a
Freeware Edition, allowing you to monitor up to 100 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:
11/24/2017 21
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
§ Can monitor a maximum number of sensors (please consider our recommendations 28 ).

§ Each PRTG on premises license includes one single failover cluster setup 122 , consisting of
two nodes. 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 the Paessler FAQs:
What is the difference between the PRTG Network Monitor licenses?
More
Paessler Website: Get a Free PRTG Trial Key and Download PRTG for Evaluation
§ https://www.paessler.com/prtg/trial
Paessler FAQs: What is the difference between the PRTG Network Monitor licenses?
§ https://www.paessler.com/support/faqs#e1912
22 11/24/2017
Part 1: Welcome to PRTG Network Monitor | 5 System Requirements
1.5 System Requirements

PRTG Network Monitor consists of two main system parts, the PRTG core server and one or
more probes. For details, see section Archit ect ure and User Int erfaces 117 .
§ If you want to use PRTG on premises, you need to install the PRTG server on a computer that
meets the Sy st em Requirement s for PRTG Core Server (PRTG on Premises) 23 .
§ If you want to use PRTG in the cloud, you need to install at least one remote probe on a
computer the meets the Sy st em Requirement s for PRTG Remot e Probes 23 .
System Requirements for PRTG Core Server (PRTG on Premises)

To install a PRTG on premises server and work with it, you need to meet the following
requirements:
§ A current PC or server with at least a dual core CPU and a minimum of 2048 MB RAM memory
is sufficient for the PRTG server.
§ We recommend that you use the operating system Microsoft Windows Server 2012 R2 for
best performance.
§ A web browser to access the web interface. The following browsers are officially supported:
§ Google Chrome 61 or later (recommended)
§ Mozilla Firefox 56 or later
§ Microsoft Internet Explorer 11
PRTG in the cloud does not require any hardware for the PRTG server, but at least one
remote probe installation is necessary to monitor your local network when using PRTG in
the cloud.
System Requirements for PRTG Remote Probes

§ Hardware
A current PC or server with at least a dual core CPU and a minimum of 2048 MB RAM memory
is sufficient for remote probes.
§ Operat ing sy st em
We recommend that you use the operating system Microsoft Windows Server 2012 R2 for
best performance. Microsoft Windows 10 and Windows Server 2016 are also good options
for remote probes.
§ St able net work connect ion
Remote probes require a stable network connection between the PRTG server and the
remote probe. Remote probes that connect to a PRTG in the cloud server need a reliable
internet connection. Unstable connections, for example via 3G, might work but it is possible
that you lose monitoring data if the connection is non-reliable.
Why are remote probes helpful for monitoring with PRTG? Because you can extend your
monitoring.
12/8/2017 23
§ Remote probes allow you to monitor different sub-networks that are separated by a firewall
from your PRTG on premises core server and to keep an eye on remote locations. You can
install one or more remote probes 3359 .
§ Remote probes are useful if you want to distribute monitoring load by taking it from the
system running the PRTG core server and putting it on one or more remote probe machines.
§ You will need a remote probe if you want to monitor your local network using a PRTG in the
cloud instance.
§ Remote probes may be suitable monitoring components in several individual scenarios that
depend on your custom network setup.
Planning a PRTG on Premises Installation With Hundreds of Sensors or More?

The maximum number of sensors you can monitor with one PRTG on premises installation
mainly depends on the monitoring technology and the monitoring intervals you use. In general,
we recommend that you use a dedicated physical machine to run both the PRTG core server
and PRTG remote probes.
For more information, see section Det ailed Sy st em Requirement s 26 .
PRTG in the cloud is restricted to max. 5,000 sensors, more sensors are not possible. This
number of sensors is available in the PRTG-5000 subscription.
More
§ Updat e From Previous Versions 79
Paessler Website: System Requirements for PRTG Network Monitor—Recommended Setup for
Most PRTG Users
§ https://www.paessler.com/prtg/requirements
Knowledge Base: Planning Large Installations of PRTG Network Monitor
§ https://kb.paessler.com/en/topic/26383
Knowledge Base: How can I speed up PRTG—especially for large installations?
Knowledge Base: Checklist for Running PRTG on VMware
Knowledge Base: Which ports does PRTG use on my system?
Knowledge Base: Which servers does PRTG connect to for Software Auto-Update, Activation,
etc.?
Knowledge Base: Which .NET version does PRTG require?
PRTG in the cloud: Enter a New Era of Monitoring
24 12/8/2017
§ https://my-prtg.com
12/8/2017 25
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 monitoring your network.
§ Supported Operating Systems 26
§ Hardware Requirements 27
§ Network Size: Recommendations 28
§ Running PRTG on Virtual Machines 30
§ Running PRTG in a Failover Cluster 30
§ Web Browser Requirements 31
§ Screen Resolution 31
§ Requirements for Monitored Devices 31
§ Requirements for the Enterprise Console 32
§ Requirements for Smartphones 32
§ More 32
the cloud.
Supported Operating Systems for PRTG Server and Remote Probes

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 2016*
§ Microsoft Windows Server 2012*
§ Microsoft Windows 10**
§ Microsoft Windows 8.1
§ Microsoft Windows 8
§ Microsoft Windows 7
§ Microsoft Windows Server 2008 R2*
* Windows servers in Core mode or Minimal Server Interface are not officially supported.
** The PRTG Enterprise Console is not fully compatible with Windows 10.
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
26 12/8/2017
§ the system provides 6 GB RAM or more.
Otherwise the 32-bit version of the PRTG Core Server will be installed.
§ For best performance of VMware sensors, EXE/Script sensors, and some other sensor types,
we recommend Windows Server 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 3359 .
§ 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 3359 .
§ Microsoft .NET Framework: We recommend that you provide Microsoft .NET Framework
versions 4.5 or later (with latest updates) on all systems running a PRTG probe.
The .NET framework is imperatively needed for monitoring VMware and XenServer virtual
environments. Also some other 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 3359 . Required
versions are 4.5, 4.6, or 4.7. For details, see the Knowledge Base: Which .NET version does
PRTG require?
§ Disabled FIPS Mode: Ensure the FIPS (Federal Information Processing Standards) mode
(Windows security option "System Cryptography: Use FIPS compliant algorithms for
encryption, hashing, and signing.") is disabled on Windows systems running the PRTG core or
probe service. FIPS-compliant encryption may cause errors of sensors which use the .NET
framework. For details, see the Knowledge Base: Why should I disable the FIPS mode under
Windows?
Hardware Requirements for PRTG Server and Remote Probes

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 with at least a dual core CPU 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 additional CPU core and 1 GB RAM per additional 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.
12/8/2017 27
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 3358 . For clusters we recommend that you stay below 2,500 sensors per
cluster.
It is crucial for a properly working PRTG server to have a certain amount of hardware
resources available. If the server run out of resources, PRTG will send warning and
emergency messages to the primary email address of the PRTG Sy st em Administ rat or user.
You will receive warning messages if available disk space falls below 1 GB or memory below
500 MB, and emergency messages if available disk space or memory falls below 50 MB. Please
react immediately and free system resources!
Network Size: Recommendations

§ Rule of thumb: Typical PRTG installations almost never run into performance issues when
they stay under 5,000 sensors, under 30 remote probes, and under 30 user accounts.
§ PRTG can scale much higher if the installation is well planned. 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 10,000 sensors from one instance of PRTG
on a physical device or more than 5,000 sensors with PRTG running on a virtual machine we
ask you to contact your presales team for consultation.
§ To give you an impression: To monitor 5,000 sensors in a 1-minute interval, PRTG takes 7.2
million measurements and evaluates, notifies, and stores them—this adds 700 MB of
additional data to the database every single day.
PRTG in the cloud is restricted to max. 5,000 sensors, more sensors are not possible. This
number of sensors is available in the PRTG-5000 subscription.
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.
SIZE R ECOMMENDATIONS
Operating System We recommend that you use 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 1424 and SNMP sensors 414 create much less load than complex
sensors like xFlow sensors 3251 , VMware sensors 418 , Sensor
Factory sensors 1570 , WMI sensors 416 , or Syslog 2443 /Trap receiver 2277
sensors, for example.
Scanning Interval We recommend that you mainly use 1-minute scanning intervals 328
for up to 2,000 sensors and 5-minute intervals if you have more

sensors.
28 12/8/2017
SIZE R ECOMMENDATIONS
Number of Users We recommend that you stay below 30 active user accounts 3116 for
each PRTG core server. You can work well with more users if these
do not all use the user interfaces at the same time (including public
dashboards).
Number of Remote Our general recommendation is to stay below 30 remote probes

Probes 3359 on one PRTG core server. PRTG still scales well up to 60 probes
as long as you have less than 100 sensors per probe.
CPU Intensive Features Try keeping the usage of the following features down: Many
quickly refreshed dashboards 3026 , frequent generation of huge
sensor reports 3000 , heavy usage of packet sniffing 3249 , factory
sensors 1570 , and toplists 2940 , frequent automatically scheduled auto-
discoveries 267 for large network segments, constant queries of
monitoring data via the API 3336 , 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.
In general, consider the following rules for the performance impact of different sensor types:
§ SNMP V1 and V2, Ping, Port , and HTTP

We recommend that you use these sensor types for scenarios with thousands of sensors.
§ SNMP V3
You can 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 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. On probes running on Windows Server 2012 R2, you can
use more VMware sensors. These limitations issue from the VMware platform. For details,
see this Knowledge Base article: Increasing Maximum Connections for VMware sensors
12/8/2017 29
§ 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 3359 or more.
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 that you use a dedicated physical machine to run the PRTG
core server or the PRTG remote probes 3359 .
There are several reasons why we recommend that you run 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 5,000 sensors per virtual
machine and consider running several PRTG core server instances instead.
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.
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 lead to massive performance issues. Do not distribute CPU cores over different CPU
sockets in your VM configuration. Scheduling threads does not work properly in this case,
which results in performance issues.
For more details, see this Knowledge Base article: Checklist for Running PRTG on VMware
Running PRTG in a Failover Cluster

We recommend a single failover setup 122 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.
This feature is not available in PRTG in the cloud.
30 12/8/2017
Web Browser Requirements

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

§ Mozilla Firefox 56 or later
For security and performance reasons, we strongly recommend that you always use the latest
version of Google Chrome to access the PRTG web interface.
Firefox is potentially vulnerable for cross-site scripting (XSS) attacks. These XSS exploits
are possible if you click phishing links that contain malicious code, for example, in emails,
and you are currently logged in to PRTG with Firefox. For more information, see this
Knowledge Base article: How secure is it to access the PRTG web interface with Firefox?
Microsoft Internet Explorer 11 and Microsoft Edge, as well as other current browsers that
are not officially supported have issues with some functionalities of the PRTG web
interface. However, you can access the web interface with any browser.
Deprecated Internet Explorer versions as well as some mobile browsers might not be able
to display the fully featured Ajax web int erface 156 .
Plugins may have an effect when viewing the PRTG web interface. Please make sure to add
exceptions for PRTG in the plugins' settings.
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 (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. For details,
see section Monit oring via SNMP 3227 .
§ 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 26
are officially supported, but do not use Windows 2008 for WMI monitoring (strong
performance issues). For details, see section Monit oring via WMI 3244 .
§ xFlow (IPFIX , Net Flow, sFlow) monit oring
The device must be configured to send NetFlow data packets (NetFlow version 5, 9, or IPFIX)
or sFlow packets (version 5) to the machine running the PRTG probe. For details, see
section Monit oring Bandwidt h via Flows 3251 .
12/8/2017 31
§ 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. For details, see section Monit oring Bandwidt h via Packet Sniffing 3249 .
§ Ot her sensor t y pes
Depending on the specific sensor type, you can find requirements (for example, modules,
components, device configurations) that may have to be fulfilled in the corresponding manual
section, as well as when adding the sensor to a device.
Requirements for the Enterprise Console

The optional PRTG Ent erprise Console 3168 (EC) runs under all supported Windows versions 26 ,
but it is not fully compatible with Windows 10. Running the EC on Windows 10 results in
several issues so please use another operating system. We will consider full Windows 10
support for future PRTG desktop clients.
PRTG in the cloud does not support connections from the Enterprise Console. If you want
to use it, please connect the Enterprise Console to a PRTG on premises instance.
The EC has a built-in webkit browser engine and requires no specific browser installed on the
system. See also Ent erprise Console—Requirement s for Connect ions t o PRTG Web Server
(s) 3169 .
Requirements for Smartphones and Tablets

PRTG supports optional mobile apps for iOS and Android devices.
For more information and system requirements, see section PRTG Apps for Mobile
Net work Monit oring 3222 .
More
§ Updat e From Previous Versions 79
Paessler Website: System Requirements for PRTG Network Monitor—Recommended Setup for
Most PRTG Users
§ https://www.paessler.com/prtg/requirements
Knowledge Base: How can I speed up PRTG—especially 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: Increasing Maximum Connections for VMware Sensors
Knowledge Base: My SNMP sensors don't work. What can I do?
32 12/8/2017
Knowledge Base: Checklist for Running PRTG on VMware
Knowledge Base: Which ports does PRTG use on my system?
Knowledge Base: How secure is it to access the PRTG web interface with Firefox?
Knowledge Base: Why should I disable the FIPS mode under Windows?
12/8/2017 33
Part 1: Welcome to PRTG Network Monitor | 6 Introduction: Monitoring with PRTG
1.6 Introduction: Monitoring with PRTG

This manual section provides an overview of basic principles of PRTG Network Monitor. It
shows you how you can prepare your IT infrastructure for monitoring with PRTG. Of course,
you do not have to re-configure your whole network for PRTG, but there are several topics
that are useful to consider before actually using PRTG.
You can immediately start monitoring without complicated configuration steps. See the Quick
St art Guide 46 for details. If you want to know more details right from the beginning, read
through the manual section below. It covers these topics:
§ Overview 34
§ What PRTG Does 34
§ Where to Install PRTG 36
§ How to Monitor 36
§ What can PRTG Monitor 36
§ How to Prepare 37
§ What Hardware Do I Want to Monitor 38
§ Types of Logins and Credentials 38
§ Monitoring Technologies 39
§ Notifications from PRTG 43
§ Advanced Topics 43
Overview
PRTG Network Monitor is a monitoring software that is flexible and easy to use. You can
download, install, and configure 48 PRTG on premises or create a PRTG in the cloud instance 63
within minutes and start monitoring right away.
That said, you will not immediately have full access to all relevant information unless your
network is completely ready for monitoring—for example, PRTG needs credentials to access
devices in your network. During the PRTG on premises install process, PRTG will automatically
add devices with some default sensors, such as the Ping sensor 1424 . But it will only add devices
and sensors where no credentials or certain technologies are needed. For PRTG in the cloud
you will need to install a remote probe in your LAN first to monitor your network.
What PRTG Does

PRTG is a Unified Monitoring Tool that allows you to monitor pretty much anything with an IP
address. PRTG consists of a core server 118 which is responsible, for example, for the
configuration, data management, and web server, and one or more probes 118 (local or cloud,
remote 3359 ), which perform data collection and monitoring processes on devices 127 via
sensors 127 .
34 12/11/2017
PRTG Arc hitec ture
Sensors are the basic building blocks of PRTG and are organized in an Object Hierarchy 125 . A
sensor can tell you about one or more aspects (referred to as channels 128 ) of a device or
node. For example:
§ Uptime
§ Load
§ Interface throughput
§ Bandwidth usage (for example, flows)
§ Loading times
§ Speed
§ Hardware status
§ Temperature
§ Quality
§ Resource consumption
§ User counts
§ Record counts
§ Log events
§ Database requests
12/11/2017 35
Where to Install PRTG

For best performance, we will always recommend that you install PRTG on premises on a
physical machine. Any current PC or server with at least a dual core CPU and 2048 MB RAM will
suffice for most average installations. PRTG can also run on a virtual machine (VM), but we have
a recommended limit 30 on the number of sensors due to the hypervisor overhead.
For remote sites and for offloading work, you can use the PRTG Remote Probe 3359 . Remote
probes offer a smaller footprint data collector that reports back to the PRTG core server and
so helps minimize performance impacts. At least one remote probe is required for PRTG in the
cloud to monitor your local network.
the cloud.
How to Monitor
There are the following ways for PRTG to receive monitoring data from target devices:
§ Polling or querying sensor data: PRTG actively obtains data from a device and refreshes it in
regular intervals. This includes, for example, device status, resource usage, and performance
metrics. Most sensor types use this method. PRTG can also consume and collect sensor data
based on interface with, for example, HTTP(S) requests, port checks, email checks, FTP
downloads, and database requests.
§ Listening or receiving sensor data: PRTG passively receives data that is pushed to PRTG by a
device or application. This includes, for example, unexpected events, Syslogs and SNMP
traps, detailed data flow (bandwidth monitoring), and event log messages.
Most of the monitoring data that PRTG collects is actively queried. It is the basis for statistical
sampling to see how a device or application is performing over time. For more information, see
section Monit oring Technologies 39 below.
What Can PRTG Monitor

Out of the box, PRTG comes with more than 200 different sensor types 412 ranging from
specific platform sensors over generic hardware and bandwidth sensors to custom scripts.
Specific sensors that are pre-configured for common configurations allow you to quickly
gather the information you need. Just add these sensors to the target devices they are
designed for and receive monitoring data instantly.
Additionally, PRTG provides the possibility to add custom sensors. For example, you can create
individual sensors for devices that PRTG does not provide sensor types for out of the box, or
write scripts that return data from some application. See also the PRTG Script World fur
custom sensors that are ready to use.
36 12/11/2017
What Can PRTG Monitor?
How to Prepare
Best practice for the first step in good monitoring is to make a plan. Think about the following
questions.
1. What needs to be monitored in my IT infrastructure?

2. How can I retrieve the needed information? Which technologies and credentials are required?
3. Which notification methods do I want to use to get alerted if there is something wrong?
You can take the following sections as a basis for your monitoring planning.
12/11/2017 37
What Hardware Do I Want to Monitor

When choosing what to monitor, we recommend that you add the most important devices
within your infrastructure first. Start with the core network and other infrastructure that all
network devices depend upon, your Business Critical Tier-1. This usually includes key
infrastructure such as core routers, switches, Virtual Private Network (VPN), firewalls, and basic
network services such as Dynamic Host Configuration Protocol (DHCP), Domain Name Service
(DNS), and authentication like Lightweight Directory Access Protocol (LDAP).
As an example, if you are a web business, your web infrastructure is absolutely critical. You will
want to add devices in order of importance to your business: file services, databases, and
other systems. Usually, you would monitor devices from several perspectives, like hardware
health, service availability, and performance.
See also our video tutorial on webserver monitoring.
Hardware Overview
There is a huge number of different vendors with uncountable variations of hardware devices,
so hardware details go beyond the scope of this article. Every IT infrastructure is individual, but
here are the main points you should consider.
1. Core infrastructure
a. Routers, switches, firewalls
b. Core network services: DNS, Active Directory, LDAP servers
2. For your hardware devices, you need statistics on availability, usage, and performance.
3. PRTG will retrieve data using standard protocols:
a. Ping, Simple Network Management Protocol (SNMP); web queries via HTTP and HTTPS; email
via Post Office Protocol version 3 (POP3), Internet Message Access Protocol (IMAP), Simple
Mail Transfer Protocol (SMTP)
b. Hardware parameters via SNMP, SSH, Simple Object Access Protocol (SOAP)
c. Bandwidth usage via xFlow (NetFlow, IPFIX, sFlow, jFlow), packet sniffing, SNMP
d. Windows systems via Windows Management Instrumentation (WMI)
e. Other interfaces via Secure Shell (SSH) and scripts (for example, PowerShell and Python)
PRTG will monitor, track, and chart data, as well as generate alarms.
Types of Logins and Credentials
Many of the sensors included in PRTG rely on access through logins to specific systems. You
will need different credentials with sufficient permission for all the different devices, operating
systems, and domains. The configuration may also be different if you want PRTG to act as a
Syslog or SNMP trap receiver or for tracking flows.
38 12/11/2017
In most cases, PRTG will use the following credential types to access the devices that you want
to monitor.
§ SNMP credentials
§ Windows credentials (WMI)
§ Linux, Solaris, and MacOS credentials (SSH/WBEM)
§ VMware and XenServer credentials
§ Database Management Systems (DBMS) credentials
§ Other credentials (for example, Amazon CloudWatch keys, HTTP proxy)
Define your (administrative) credentials for all types of target devices that you want to monitor
in the Root group of the device tree. Devices that you add to PRTG will inherit 129 these
automatically, so often you will not have to re-enter credentials, depending on the used
monitoring technology.
Monitoring Technologies
This section briefly describes the most common monitoring technologies.
For details, see manual section Sensor Technologies 3226 .
Monit oring wit h Simple Net work Management Prot ocol (SNMP)
SNMP is a set of standards for communication with devices in a TCP/IP network. SNMP
monitoring is useful if you are responsible for servers and network devices such as hosts,
routers, hubs, and switches. It enables you to keep an eye on network and bandwidth usage,
and monitor important issues such as uptime and traffic levels.
You can use SNMP to monitor the bandwidth usage of routers and switches on a port-by-port
basis, as well as device readings such as memory and CPU load. The target devices must
support SNMP. Most devices with enabled SNMP require the same configuration like SNMP
version and community string. To find out how to set up SNMP on a specific device, search in
the internet for your device name or model and SNMP configuration. You will likely get plenty
of information on how to configure SNMP.
12/11/2017 39
Network Monitoring v ia SNMP
When you use a sensor with this technology, PRTG sends small data packets to devices, for
example, querying routers, switches, and servers for the traffic counters of each port. These
queries trigger reply packets from the device. Compared to PRTG's other bandwidth monitoring
technologies via flows, packet sniffing, or WMI, the SNMP option creates the least CPU and
network load.
PRTG supports three versions of the SNMP protocol: Version 1, version 2c, and version 3.
SNMP Version 1
This is the oldest and most basic version of SNMP.
§ Pro: Supported by most SNMP-compatible devices; simple to set up.

§ Con: Limited security because it only uses a simple password (community string 3230 ) and
sends data in clear text (unencrypted). Because of this, you should only use it inside LANs
behind firewalls, but not in WANs. Version 1 only supports 32-bit counters, which are not
enough for high-load (gigabits/second) bandwidth monitoring.
SNMP Version 2c
This version adds 64-bit counters.
§ Pro: Supports 64-bit counters to monitor bandwidth usage in networks with gigabits/second
loads.
§ Con: Limited security (same as with SNMP V1).
SNMP Version 3
This version adds authentication and encryption to SNMP.
§ Pro: Offers user accounts and authentication for multiple users and optional data packet
encryption, increasing available security; plus all advantages of Version 2c.
40 12/11/2017
§ Con: Difficult to configure and higher overhead for the probe, which will reduce the number
of devices that you can monitor (see here 3229 for more information).
SNMP Traps
Various devices can send SNMP trap messages to notify you of system events.
§ PRTG supports SNMP v1 and SNMP v2c traps.

§ Destination for SNMP traps: IP address of the trap receiver, which is the IP of the PRTG probe
system (server with either a local or remote probe running on it) to which you add the SNMP
Trap Receiver Sensor 2277 .
Which SNMP Version Should I Choose?
The SNMP version to choose depends on your environment, but as a guideline:
§ If your network is publicly accessible, you may want to use SNMP v3, which has encryption
and secure access. However security and encryption adds overhead, which results in less
performance.
§ If your network is isolated or well protected behind firewalls, the lower security of SNMP v1
or SNMP v2c may be sufficient.
§ From the PRTG perspective, if you have a lot of devices to monitor, the SNMP v2c is
preferable. It will allow you to monitor more devices on a shorter monitoring interval and
supports 64-bit counters.
The most important thing is to set the same SNMP version in the PRTG settings (for example,
on Root level) as you have configured in your target device. If you select an SNMP version that
is not supported by the server or device you want to monitor, you receive an error message.
Unfortunately, in most cases, these error messages do not explicitly point to the possibility
that you use the incorrect SNMP version. These messages provide minimum information only,
such as cannot connect or similar. Similar errors occur when community strings, usernames, or
passwords do not match.
For basic requirements for SNMP monitoring, see this Knowledge Base article: My SNMP
sensors don't work. What can I do?
Monit oring Windows Sy st ems
You can monitor Windows systems via Windows Management Instrumentation (WMI) 3244 and
Windows Performance Counters 3244 . WMI is the Microsoft base technology for monitoring and
managing Windows based systems. PRTG uses this technology to access data of various
Windows configuration parameters and status values. However, sensors using the WMI
protocol generally have a high impact on system performance. In addition to strict WMI
sensors, there are sensors that can use Performance Counters to monitor Windows systems.
To monitor via WMI and Performance Counters it is usually sufficient to provide Credent ials for
Windows Sy st ems in PRTG. However, monitoring via WMI is not always trivial and often causes
issues.
See this article in our Knowledge Base if you run into issues: My WMI sensors don't work.
What can I do?
12/11/2017 41
It is also possible to use Simple Network Management Protocol (SNMP) for Windows devices.
The same information is often available using any of these protocols. From a performance
perspective, the preference would be SNMP, and then WMI or Performance Counters.
Bandwidt h and Traffic Monit oring: Flows and Packet Sniffing
Using flow protocols, you can monitor the bandwidth usage of all packets going through a
device. In PRTG, you can view Toplist s 2940 for all xFlow (NetFlow, IPFIX, sFlow, jFlow) sensors.
Flows are a type of monitoring data pushed from network devices to PRTG. You can use it to
monitor where data is traveling from and to, and how much. This way it determines which
machine, protocol, and user is consuming bandwidth. PRTG currently supports the following
flow types:
§ NetFlow v5/v9 and IPFIX: Originally introduced by Cisco and supported by several vendors
§ jFlow: Traffic sampling technology introduced by Juniper networks
§ sFlow: Short for sampled flow, introduced by HP. sFlow uses statistical sampling of the traffic
at defined intervals to achieve scalability for high volume interfaces.
You can also use packet sniffing 3249 for bandwidth monitoring if your hardware does not
support any of these flow versions.
Monit oring Passively Received Dat a
PRTG provides the option to monitor passively received data. For this purpose, you can set up
a device in a way that it automatically sends the data to PRTG. Specific sensor types can
receive this data and alarm you based on your individual settings. For example, all Linux/Unix
and most network devices support remote devices generating data that has to be configured
on each device, and sending the messages to a PRTG probe system 118 . Usually, only the
destination IP and port are required.
Examples of this monitoring technology are HTTP Push 3284 sensors, as well as Syslog 2443 and
SNMP Trap 2277 receivers.
For more information, see our tutorial videos about the Syslog Receiver sensor and the
SNMP Trap Receiver sensor.
Monit oring wit h Hy pert ext Transfer Prot ocol (HTTP)
The Hypertext Transfer Protocol (HTTP) is a standard application layer protocol and the basis
for data communication in the internet. HTTP is a request-response method for client-server
architectures, where the client sends a request and the server processes and responds to the
request.
Monitoring via HTTP is useful if you want to monitor websites or web servers. It enables you to
keep an eye on the availability and download times of a website or the performance statistics
of a web server. There are also a lot of other possible use cases for HTTP sensors. For
example, you can request any Application Programming Interface (API) that is reachable via HTTP
and monitor returned values. This approach makes it possible to include almost any type of
device or application into your monitoring.
42 12/11/2017
Notifications from PRTG

PRTG can notify you in various ways 3062 if it detects that there is something wrong in your
network. You can individually define in which case (for example, based on thresholds 2969 or on
sensor states 183 ) and how you want to receive notifications from PRTG. The most common
methods would be email 3063 , SMS text message 3065 , and push notifications 3064 to your
smartphone which runs a PRTG mobile app 3222 .
For your critical infrastructure it is best practice to set up two redundant notifications with
different delivery methods (for example, email and SMS via a gateway).
For more information about notifications, see our video tutorials PRTG – Not ificat ions
and Use Cases for PRTG Not ificat ions.
Email Not ificat ions
The most common notification method is to send emails using a Simple Mail Transfer Protocol
(SMTP) server built-in in PRTG. This means no SMTP server setup or configuration is required,
but if you want to deliver through your email server, you will have to configure it in the PRTG
SMTP settings 3102 .
SMS Text Not ificat ions
PRTG on premises can also notify you on your mobile phone. To deliver SMS text notifications
3105 , you can select one of the SMS service providers that PRTG includes by default and use it
with your credentials for this provider. Of course, you can also use any other service provider
by defining a custom URL (look in your provider's documentation for the required format). You
can also use an SMS gateway to receive messages even if your internet connection is down.
See our Knowledge Base for a list of third-party tools.
Push Not ificat ions
PRTG can send push notifications to iOS and Android,when you run the according PRTG mobile
app on your smartphone.
See the article How can I use push notifications with PRTG? in our Knowledge Base for
more details.
Advanced Topics
So, now that you are ready for monitoring with PRTG, enjoy having all important information
about your IT infrastructure available at a glance. To dive deeper into network monitoring with
PRTG we entrust you to have a look at our video tutorials for advanced topics. Of course, you
will also find all relevant information about network monitoring in the PRTG User Manual!
More
Video Tutorials: PRTG Basics
§ https://www.paessler.com/support/videos/prtg-basics
12/11/2017 43
Video Tutorial: Webserver Monitoring

§ https://www.paessler.com/support/videos/prtg-basics/webserver-monitoring
Video Tutorial: SNMP Trap Receiver
§ https://www.paessler.com/support/videos/prtg-advanced/snmp-trap-receiver
Video Tutorial: Syslog Receiver
§ https://www.paessler.com/support/videos/prtg-advanced/syslog-receiver
Video Tutorial: PRTG – Notifications
§ https://www.paessler.com/support/videos/prtg-basics/notifications
Video Tutorial: Use Cases for PRTG Notifications
§ https://www.paessler.com/support/videos/prtg-basics/notifications-use-cases
Knowledge Base: My WMI sensors don't work. What can I do?
Knowledge Base: How can I send SMS text message notifications via a modem or a mobile
phone with PRTG?
Knowledge Base: How can I use push notifications with PRTG?
44 12/11/2017
Part 2
Quick Start Guide
12/11/2017 45
Part 2: Quick Start Guide |
2 Quick Start Guide

Welcome to PRTG Network Monitor! This section gives 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 PRTG installer
from the Paessler website and run through the installation wizard, or set up a PRTG in the
cloud instance on https://my-prtg.com and install a remote probe in your LAN. Provide some
information about your network in the Smart Set up 52 and PRTG will start monitoring your
network immediately without any further complicated stumbling blocks! Of course, later on,
you can still adjust everything to your needs.
See the following quick steps.
46 12/11/2017
Part 2: Quick Start Guide |
Quick Start Guide—Topics

§ ONE—Download, Installation, and First Login 48
§ TWO—Smart Setup 52
12/11/2017 47
Part 2: Quick Start Guide | 1 ONE—Download, Installation, and First Login
2.1 ONE—Download, Installation, and First Login

We offer two options to monitor your network with PRTG Network Monitor: use PRTG on
premises to run the PRTG in your network, use PRTG in the cloud to run PRTG in the cloud.
If you want to use PRTG on premises, just download it from our website and install it on a
Windows computer.
PRTG in the cloud does not require a download or installation to set up the PRTG server,
just create an instance on https://my-prtg.com
For video tutorials with PRTG basics, see the video sections on paessler.com.
Download PRTG on Premises

You can find the installer for PRTG on our website https://www.paessler.com. There you can
also login to the Paessler shop to buy or upgrade your license, or to renew your maintenance.
This only applies to PRTG on premises instances, not to PRTG in the cloud.
Download PRTG Network Monitor
48 12/11/2017
Downloading PRTG Network Monitor

Please download the latest publicly available program version from the Paessler website.
Simultaneously, you will receive a trial key. Enter this license key during the installation of
PRTG. If you have already purchased a commercial license, use your commercial key. Please log
in to the Paessler website to find your license key,
§ ht t ps://www.paessler.com/prt g/download
§ ht t ps://shop.paessler.com/account s/login/
Every freeware installation starts as a trial version that allows you to use an unlimited number
of sensors for 30 days. After the trial period has expired, your installation automatically reverts
to the freeware edition with 100 sensors. Please understand that customers with a commercial
license get prioritized support.
To upgrade your running trial or freeware version to a commercial edition, please purchase a
commercial license key on https://shop.paessler.com and enter this key on the license page
3152 in the PRTG web interface.
Updates are free to customers with an active maintenance contract. If you do not have an
active maintenance contract, please log in to the Paessler shop to renew it or contact
sales@paessler.com.
Once installed, the PRTG Soft ware Aut o-Updat e 3146 will automatically download and install
new software versions. This helps you keep PRTG up to date without manually installing
new PRTG versions.
Install PRTG on Premises

Double-click the setup file on the computer that you want to use as PRTG server. Follow the
installation wizard and install the software.
At the end of the installation, PRTG opens a new browser window automatically. It connects to
the PRTG web interface, shows the device tree 170 , and starts the setup assistant 52 . Please
load the web interface with one of the officially supported browsers:
§ Google Chrome 61 or later (recommended),

§ Mozilla Firefox 56 or later,
We recommend that you use Google Chrome to access the PRTG web interface. Firefox has
security issues and Internet Explorer as well as Microsoft Edge and other current browsers
might have issues with some functionalities. See Det ailed Sy st em Requirement s 31 for more
details.
Due to scripting incompatibilities, you might not be able to use all functionalities of the
PRTG Ajax web interface with Internet Explorer 10 or earlier and other older browsers. If
you cannot access the PRTG web interface, please open the URL of PRTG in another browser.
12/11/2017 49
Create a PRTG in the cloud Instance

PRTG in the cloud runs in the cloud, so setting up the PRTG server does not require a
download or installation.
§ Open https://my-prtg.com with a browser.

§ You can directly start a free trial from there: enter your desired domain name (between 4 and
60 characters) and click St art Free Trial Now. You can reach your PRTG in the cloud
instance with your browser under <yourdomain>.my-prtg.com later.
§ A window where you have to sign in will appear. You can directly sign in using your Google,
Facebook, Windows, or Amazon account (via Auth0). In this case, click the desired service
and sign in with your credentials. Alternatively, you can register at my-prtg.com using
dedicated credentials.
§ After signing in, choose your subscription plan, for example, you can start with a free trial for
10 days. Click Subscribe Now and PRTG will create an instance for you.
As soon as your instance is ready, the PRTG web interface will open, show the device tree, and
start the smart setup 52 . You can also instantly monitor all servers, services, and devices that
are publicly available via the internet.
Please make sure you load the web interface with one of the supported browsers 31 . We
recommend that you always use the latest version of Google Chrome.
Login
If everything works fine, the first thing you will see will not be the login screen, but the device
tree. You only have to log in manually if you use a different browser.
PRTG Login Sc reen
§ The default administrator credentials (login name prt gadmin and password prt gadmin) are
automatically filled in. Select Login to proceed if you use PRTG on premises.
50 12/11/2017
PRTG in the Cloud Login Sc reen
§ If you use PRTG in the cloud, click one of the social login buttons and log in with the
according credentials using Auth0, or enter your dedicated my-prtg.com credentials and
click Login. See section Creat e a PRTG in t he Cloud Inst ance 63 for more information on
how to get started with PRTG in the cloud.
Make sure you use a supported web browser when logging in to PRTG. Please use Google
Chrome 61 or later (recommended), Mozilla Firefox 56 or later, or Microsoft Internet Explorer
11.
See the next step for more information about the initial configuration of PRTG using the
Smart Set up 52 !
More
Video tutorials for PRTG Network Monitor:
§ https://www.paessler.com/support/videos
12/11/2017 51
Part 2: Quick Start Guide | 2 TWO—Smart Setup
2.2 TWO—Smart Setup

PRTG will automatically start the Smart Set up on a new PRTG instance. This setup assistant,
represented by a member of the Paessler team, will guide you through the initial setup of your
network monitoring system. The Smart Setup will reappear until you have completed all steps.
You can skip the introduction altogether right at the beginning.
The Smart Setup in PRTG in the cloud differs in some details from the Smart Setup in PRTG
on premises. For example, it will ask you right at the beginning to install a remote probe
94 in your local network. This is required to monitor your LAN, so we strongly recommend
that you follow the smart setup!
First Start
When logging in for the first time, PRTG will show you the device tree 170 . PRTG on premises
already contains several devices 127 with sensors 127 that monitor your network, ordered in
different suitable groups 126 . PRTG automatically creates the device tree during the installation
process by using its Aut o-Discovery 267 function. You do not have to fill out any forms but will
directly see the availability and first monitoring results of various devices in your network
when you first start PRTG!
PRTG scans your network by pinging IP addresses in the subnet of your PRTG system and adds
all reachable devices to your specific network monitoring structure.
The smart setup scans only for devices with IP addresses in private network ranges. You
can manually start an Auto-Discovery for other subnets later.
Dev ic e Tree after Initial Auto-Disc ov ery
52 12/11/2017
You will notice a Paessler employee in the upper-right corner of the PRTG web interface. He will
guide you through 5 simple setup steps where you can enter more information about your
network. PRTG will run another auto-discovery with this information to add additional devices
and sensors to your monitoring. Of course, you can still edit the monitoring settings provided
during the Smart Setup later on. And you can always adjust the monitoring to your needs.
Click OK! to start a guided tour, follow the instructions, and discover your network with PRTG!
If you choose Skip int roduct ion now, then the Smart Setup assistant will never appear
again! We strongly recommend that you take the guided tour if you are new to PRTG.
Start Your Introduc tion to PRTG
The steps to take are:
§ Provide Credentials 53
§ Enter Location Information 56
§ Change Your PRTG Login Password 56
§ Confirm Your Email Address 57
§ Switch to SSL 58 (if you access PRTG from another computer)
Step 1: Provide Credentials

Your personal setup assistant Greg asks you to provide credentials for devices in your
network. Click OK, show me!, follow the animated yellow mouse pointer, and open the
Set t ings tab of the Root group.
12/11/2017 53
Hav e Your Credentials Ready
In the Set t ings tab, enter various administrator credentials for your network environment.
With these credentials, PRTG can add a large number of additional devices and sensors
automatically to your device tree. This way, PRTG helps you set up your network monitoring so
there is no need for you to manually add every single device one by one.
54 12/11/2017
Prov ide Credentials...
§ To monitor your Windows clients and servers via Windows Management Instrumentation
(WMI), enter Windows administrator credentials for your network. We recommend that you
use Domain Administrator credentials (if you use an Active Directory). For a general
introduction to the technology behind WMI, see the manual section Monit oring via WMI 3244 .
§ If you have systems running on Linux, Solaris, or Mac OS X, enter root access credentials for
these systems. For a general introduction to SSH monitoring, see the manual section
Monit oring via SSH 3247 .
§ If you use the virtual environments VMware or Citrix XenServer, enter root access
credentials for these systems. For a general introduction to the monitoring of virtual
environments, see the manual section Monit oring Virt ual Environment s 3264 .
§ To monitor your hardware (router, switches, etc.), Simple Network Management Protocol
(SNMP) is the most commonly used protocol. Usually, all SNMP-enabled devices use the same
settings by default: SNMP v2c, community string public, and SNMP port 161. For a general
introduction to the technology behind SNMP, see the manual section Monit oring via SNMP
3227 .
PRTG will store these credentials in the Root 314 group of your device tree. All dependent
devices automatically inherit and use them for monitoring. You can discontinue Inherit ance of
Set t ings 129 at any level if you enter other credentials instead.
12/11/2017 55
Click OK, done! to finish this setup step and confirm to start a detailed auto-discovery with
the OK, do it ! button.
...and Start a Detailed Auto-Disc ov ery
For details about the available options, see the manual section Root Group Set t ings 315 .
Step 2: Enter Location Information

While PRTG runs a new auto-discovery in your network with the provided credentials, the
setup assistant asks you to provide the location of your PRTG server. This information will be
displayed on PRTG Geo Maps 2961 . Enter your location and confirm with OK, done!. Click OK,
show me! to get back to the device tree.
Enter Your Loc ation
For details about the available options, see the manual section Root Group Set t ings 314 .
Step 3: Change Your PRTG Login Password

Back on the device tree, the PRTG on premises setup assistant asks you to change your
password. Click OK, show me! and follow the assistant to your account settings. By default,
PRTG uses the administrator account with login name prt gadmin and password prt gadmin.
So we strongly recommend that you change the password to secure your PRTG installation
against unauthorized access.
56 12/11/2017
Follow the Assistant...
Enter your New Password, confirm it with Ret y pe Password. The password must meet the
following requirements:
§ at least eight characters long

§ at least one numeral
§ at least one capitalized letter
Click OK, done! to save your new password.
...to Change the Default Password
For details about the available options, see the manual section Account Set t ings—My
Account 3050 .
Step 4: Confirm Your Email Address

To complete the PRTG Smart Setup, check whether the email address that you have entered
during the installation is correct.
A working email address is absolutely mandatory for PRTG to reach you via email
notifications, alarms, and for other important messages.
12/11/2017 57
If the address is correct, click OK, done! and follow the assistant back to the device tree.
Verify Your Email Address
For details about the available options, see the manual section Account Set t ings—My
Account 3050 .
Step 5: Switch to SSL

If you access the PRTG on premises web interface from a computer other than the computer
where you installed PRTG, the assistant will appear and ask you to switch to a secure
connection with Secure Sockets Layer (SSL)/Transport Layer Security (TLS) encryption. We
strongly recommend that you run the PRTG web interface using SSL encryption (Hypertext
Transfer Protocol Secure (HTTPS)), especially if you make your web interface available from the
internet. Without encryption, your passwords are sent unencrypted over your network.
§ Click OK, swit ch now! to get more information about using SSL for the PRTG web server.
§ In the new window, click the button Yes, swit ch t o SSL now to switch to an SSL-encrypted
connection.
§ PRTG must restart its services to apply the changes and is reachable under an HTTPS URL
afterwards.
§ When the web interface reloads, most likely it will show a certificate warning 162 . Confirm it to
proceed to the login screen.
58 12/11/2017
Switc h to a Sec ure SSL Connec tion
For more details, see the manual sections Sy st em Administ rat ion—User Int erface 3087 and
SSL Cert ificat e Warning 162 .
You Are Done!
You Are Done with the Smart Setup!
While you were busy with the Smart Setup, PRTG created additional devices and sensors for
you. There are first monitoring values available, too. Now you are all-in in your personal unified
network monitoring!
To become familiar with the PRTG web interface, we recommend that you read on in the
manual section General Lay out 170 of the web interface.
More
Video Tutorial: PRTG Installation and Smart Setup
§ https://www.paessler.com/support/videos/prtg-basics/installation_of_prtg_network_monitor
12/11/2017 59
Part 3
Using PRTG in the Cloud
8/10/2017 61
Part 3: Using PRTG in the Cloud |
3 Using PRTG in the Cloud

The following sections show you how to Creat e a PRTG in t he cloud Inst ance 63 and how
to Manage a PRTG in t he cloud Subscript ion 69 .
See the Paessler website for PRTG in t he Cloud – Service Descript ion and FAQ – PRTG in
t he Cloud.
More
Paessler Website: PRTG in the Cloud – Service Description
§ https://www.paessler.com/prtg/prtg-on-demand-service-description
Paessler Website: FAQ – PRTG in the Cloud
§ https://www.paessler.com/support/faqs/faq-prtg-on-demand
PRTG Manual:
§ Differences bet ween PRTG on Premises and PRTG in t he Cloud 3404
Using PRTG in the cloud—Topics

§ Create a PRTG in the Cloud Instance 63
§ Manage a PRTG in the Cloud Subscription 69
62 8/10/2017
Part 3: Using PRTG in the Cloud | 1 Create a PRTG in the Cloud Instance
3.1 Create a PRTG in the Cloud Instance

To create a PRTG in the cloud instance, open your web browser (Google Chrome 61 or later
(recommended)) and go to https://my-prtg.com. This is the PRTG in the cloud web portal.
Start Free Trial Now
Enter a domain name of your choice, such as myfirstdomain. The domain name can be
anywhere from 4 and 60 characters long and is where you can reach your PRTG in the cloud
instance with your browser later. So if you enter myfirstdomain as the domain name here, your
PRTG in the cloud instance will be reachable under myfirstdomain.my-prtg.com. Click St art
Free Trial Now to continue.
11/24/2017 63
PRTG in the Cloud Signup
You can sign up with your Google+, Facebook, Windows, or Amazon account via single sign-on
(Auth0). This account will then always be automatically used for login and will be connected to
your PRTG in the cloud account. Just click the respective button and follow the instructions
there.
Alternatively, you can sign up via email by entering a valid Email address, a Password, and
confirming it with Confirm Password. The password must meet the following requirements:
§ at least 8 characters long

§ at least one uppercase letter
§ at least one lowercase letter
§ at least one numeral
Click Sign Up to register for your PRTG in the cloud instance. PRTG then notifies you that a
verification email has been sent to your inbox.
64 11/24/2017
Verify Email Address Notific ation
Go to your inbox and open the email.
11/24/2017 65
Verify Email Address
Click Verify Email Address to verify your email address and go to the login screen.
66 11/24/2017
Login Sc reen
Enter your credentials and click Login to log in to PRTG in the cloud.
While we prepare your subscription, a welcome video plays that introduces the basics of
network monitoring with PRTG in the cloud.
Your PRTG is Ready
11/24/2017 67
When your subscription is ready, click the URL with your domain to open the Ajax web
interface 156 .
Welc ome
Congratulations, your PRTG in the cloud instance is up and running! To open the device tree,
click View Result s or Devices in the main menu bar 250 .
PRTG in the cloud has automatically created a Cloud Probe that runs on the cloud instance. It
shows several health values of the instance and you can instantly monitor all servers, services,
and devices that are publicly available via the internet with this probe. See also section
Archit ect ure and User Int erfaces—Probe(s) 118 .
A Paessler employee will guide you through the Smart Set up 52 . In particular, you will install a
remote probe 3359 , which is required for monitoring your LAN. We strongly recommend that you
follow the instructions for best monitoring experience!
68 11/24/2017
Part 3: Using PRTG in the Cloud | 2 Manage a PRTG in the Cloud Subscription
3.2 Manage a PRTG in the Cloud Subscription

PRTG Network Monitor offers Monitoring as a Service with PRTG in the cloud. PRTG in the cloud
runs in the cloud and does not require a PRTG core server installation inside your network,
making monitoring even easier. We offer subscription plans that you can tailor to your needs
and manage via the PRTG in the cloud web portal on my-prtg.com.
All you need to do is open a web browser (Google Chrome 61 or later (recommended)), go to
https://my-prtg.com, and log in to manage your subscription.
For details about setting up a PRTG in the cloud instance, see manual section Creat e a
PRTG in t he Cloud Inst ance 63 .
Login Sc reen
Provide the credentials you entered when signing up and click Login or use single sign-on and
continue with your Google+, Facebook, Windows, or Amazon account via the respective
button.
11/24/2017 69
Dashboard
The Dashboard tab gives you an overview of your PRTG in the cloud subscription. Here you
can manage or cancel your subscription, or add a new subscription. If you have purchased a
subscription, you will also see when your next payment is due. You can also click the link
under Domain to open the PRTG web interface 156 .
PRTG in the Cloud Dashboard
Click Manage Subscript ion to view your subscription details. The following information is
displayed where you can edit your plan, payment, or billing address. Click Change Plan to save
your changes.
70 11/24/2017
Add a New Subsc ription
Click New Subscript ion to add a new subscription to your account.
11/24/2017 71
Add a New Subsc ription
Enter a domain name, for example myseconddomain.my-prtg.com, choose a plan, and then
enter your credit card information and billing address. Click Subscribe Now to add the
subscription.
Click Cancel Subscript ion to cancel your PRTG in the cloud subscription. Enter CANCEL in the
field and click Cancel Subscript ion again to finalize the cancellation.
Canc el a Susbc ription
72 11/24/2017
History
This tab gives you an overview of the history of your subscriptions.
Subsc ription History
Account Settings— Profile

Here you can view your profile, view or update your payment information, and view your
invoices.
Account Settings—Payment
When purchasing a subscription, you will need your payment information. Enter your credit
card information and billing address here to save it for later use.
11/24/2017 73
Pay ment Informaton
Account Settings—Invoices
Here you can view and download all of your invoices.
Logout
Click Logout in the upper-right corner to log out of your account.
74 11/24/2017
Part 4
Installing the Software
8/10/2017 75
Part 4: Installing the Software |
4 Installing the Software

The following sections show you how to download and install your PRTG on premises
instance. If you want to use PRTG in the cloud, just go straight to section Create a PRTG in the
Cloud Instance 63 to get started.
Installing the Software—Topics

§ Download PRTG 77
§ Update From Previous Versions 79
§ Install a PRTG Core Server 85
§ Create a PRTG in the Cloud Instance 63
§ Install a PRTG Cluster 89
§ Enter a License Key 90
§ Activate the Product 92
§ Install a PRTG Remote Probe 94
§ Install the Enterprise Console 105
§ Uninstall PRTG Products 111
76 8/10/2017
Part 4: Installing the Software | 1 Download PRTG
4.1 Download PRTG

You can find the installer for PRTG on our website https://www.paessler.com. There you can
also login to the Paessler shop to buy or upgrade your license, or to renew your maintenance.
Download PRTG Network Monitor
Downloading PRTG Network Monitor

Please download the latest publicly available program version from the Paessler website.
Simultaneously, you will receive a trial key. Enter this license key during the installation of
PRTG. If you have already purchased a commercial license, use your commercial key. Please log
in to the Paessler website to find your license key,
§ ht t ps://www.paessler.com/prt g/download
§ ht t ps://shop.paessler.com/account s/login/
Every freeware installation starts as a trial version that allows you to use an unlimited number
of sensors for 30 days. After the trial period has expired, your installation automatically reverts
to the freeware edition with 100 sensors. Please understand that customers with a commercial
license get prioritized support.
12/12/2016 77
Part 4: Installing the Software | 1 Download PRTG
To upgrade your running trial or freeware version to a commercial edition, please purchase a
commercial license key on https://shop.paessler.com and enter this key on the license page
3152 in the PRTG web interface.
Updates are free to customers with an active maintenance contract. If you do not have an
active maintenance contract, please log in to the Paessler shop to renew it or contact
sales@paessler.com.
Once installed, the PRTG Soft ware Aut o-Updat e 3146 will automatically download and install
new software versions. This helps you keep PRTG up to date without manually installing
new PRTG versions.
78 12/12/2016
Part 4: Installing the Software | 2 Update From Previous Versions
4.2 Update From Previous Versions

If you already have a previous software version installed, there are several things you have to
consider before you update to the current PRTG version. Please see section Det ailed Sy st em
Requirement s 26 to see all requirements for the current PRTG version.
We recommend that 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. For details, see the Knowledge Base: How do I backup
all data and configuration of my PRTG installation?
On PRTG in the cloud instances, the update process is managed automatically, so you do
not have to care about updating your PRTG.
Update from PRTG Network Monitor 16.1.22 or later

If you run PRTG Network Monitor with version 16.1.22 or later, simply install 85 the latest
version on top of the previous version. Your configuration will be kept. PRTG updates remote
probes 3359 automatically as well. If you have configured PRTG as a cluster 122 , you only have to
install an update on any node server (master or failover). PRTG deploys the new version to the
cluster automatically.
We recommend that you use the Aut o-Updat e 3146 of PRTG to install the latest version. Please
always have a proper backup of your monitoring data.
Import ant not es:
§ PRTG 17.3.34 comes with a completely rewritten web interface. If you have customized the
PRTG web interface using one of the dedicated files in a prior version, all your
customizations will be lost as soon as you install PRTG 17.3.34. You will have to redo your
changes to keep the customizations. For details, see the Knowledge Base: Customizing and
Re-Branding the PRTG Web Interface
§ As of PRTG 17.3.34, sensor types that require the .NET framework need version .NET 4.5 or
later. For details, see the Knowledge Base: Which .NET version does PRTG require?
§ With PRTG 16.3.26, the Mobile Web GUI has been removed from PRTG.
§ With PRTG 16.2.25, several sensor types have been removed from PRTG 80 .
Update from PRTG Network Monitor 13.1.1 through 16.1.21

As of version 16.1.22, PRTG is signed with renewed certificates. To be able to seamlessly
update to version 16.1.22 or later an int ermediat e updat e is required for the PRTG core
server and all probes if you currently run a PRTG version previous to 16.1.21.1691/1692. If
you auto-update 3146 from previous versions (lower than 16.1.21.1691/1692), PRTG will
automatically install this intermediate version first. You have to perform an additional auto-
update to install the latest version. PRTG will notify you with a ticket 218 about this approach.
Your configuration will be kept.
11/24/2017 79
We recommend that you use the auto-update 3146 to install the latest PRTG version. If you
update manually with an installer downloaded from the Paessler online shop, the
intermediate update is only necessary if you currently run a PRTG version previous t o
16.1.21.1691/1692 wit h one or more remot e probes or in a clust er set up. If you do not
perform this intermediate update, you will have to update your remote probes and cluster
nodes manually. Please contact our technical support team 3162 to get the installer for this
version if you do not use the auto-update.
§ As of PRTG 14, Int ernet Explorer 9 is no longer officially support ed for access to the
PRTG web interface.
§ Also as of PRTG 14, PRTG core and probes no longer officially support Windows X P and
Windows Server 2003 (including SP1 and SP2).
§ As of PRTG 15, Int ernet Explorer 10 is no longer officially support ed for access to the
PRTG web interface.
Removed Sensor Types as of PRTG Network Monitor 16.2.25

We have removed several sensor types from PRTG with version 16.2.25. Sensors of these
types that you still use in your PRTG installation will stop monitoring and show a down status
as soon as you update to 16.2.25 or later. Most of the affected sensor types have been
deprecated as of PRTG version 16.2.23 or before. You will receive tickets from PRTG that
inform you if your PRTG setup is affected.
These sensor types were used by very few PRTG users and/or created substantial load for
both our technical support and development team. We believe that the majority of PRTG users
prefers that we focus on features that many customers use everyday rather than spending our
precious energy on niche issues. We want to keep PRTG as easy to use as possible!
For a list of all discontinued sensors, possible alternatives, and more details about this
approach, see this article: https://kb.paessler.com/en/topic/68227
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
anymore. This means that if you update from a PRTG version older than 13.2.3 to the current
version, all existing customizations of the web interface will be disabled and you have to revise
them. You may find a way for a similar customization that you can add to the files in the
current webroot folder that contains the web interface files now.
For details, see the Knowledge Base: What about my web interface customizations as of
PRTG 13.2.3?
Update from PRTG Network Monitor 9 and 12

We strongly recommend that you perform a clean install of the latest PRTG version instead
of updating from an existing PRTG 9 or 12!
If you use PRTG 9 or 12 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.
80 11/24/2017
We recommend that you always have a proper backup of your monitoring data.
§ Int ermediat e versions: You have to install two intermediate versions before you can
update to the latest version.
· If you currently run PRTG version 12.4.5.3164/3165 or lower, install the int ermediat e
version 12.4.7.3507 before you proceed.
· If you have installed version 12.4.7.3507, install the int ermediat e version
16.1.21.1691/1692 before you proceed. Afterwards you can seamlessly update to the
latest PRTG version. For details about this intermediate update, see section Updat e from
PRTG Net work Monit or 13.1.1 t hrough 16.1.21 79 above.
· We recommend that you use the Aut o-Updat e 3146 feature. In this case PRTG will
automatically install the intermediate versions. Run the auto-update three times if you
come from a version previous to 12.4.7.3507, run it twice if you come from a version
previous to 16.1.21.1691/1692. If you do not use the auto-update, please contact our
technical support team 3162 to get the installers for these intermediate versions.
§ 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 that you to pause them to keep their data. To
continue monitoring, please add the sensors anew (for example, using the auto-discovery).
§ Please inst all .NET 4.0: We strongly recommend that you install .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 418 auto-discovery and monitoring, Citrix XenServer 577 auto-
discovery and monitoring, SIP Options Ping Sensor 1624 , Windows Last Update Sensor
(deprecated as of PRTG 16.x.23).
§ 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 anymore. This means that 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 anymore with the current PRTG version.
We recommend that you to have a look at the Det ailed Sy st em Requirement s 26 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

We strongly recommend that you perform a clean install of the latest PRTG version instead
of updating from an existing PRTG 7 or 8!
11/24/2017 81
If you use PRTG 7 or 8 now, you have to update PRTG to intermediate versions first to ensure
all data is carried over correctly. You cannot updat e t o PRTG 15 or lat er direct ly from PRTG
7 or 8!
§ We recommend that you first update to the latest PRTG 8 version.

§ From the latest PRTG 8 version update to PRTG version 9.
§ From PRTG 9, update to both intermediate versions 80 12.4.7.3507 and 16.1.21.1691/1692
and then to the current PRTG version.
Please contact our technical support 3403 to obtain download links for these PRTG versions.
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 anymore. 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.
§ You may experience a slow Enterprise Console 3168 (former 'Windows GUI') due to different
reasons.
§ 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 354 .
§ 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.
§ System Requirements for the PRTG core server and probes: please have a look at our latest
Det ailed Sy st em Requirement s 26 .
§ 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.
82 11/24/2017
§ 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.
We strongly recommend that you have a look at the Det ailed Sy st em Requirement s 26
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 strictly as
of PRTG 8. If you use custom sensors with PRTG 7, these may not work with the current
PRTG version if they do not fully apply to the API definition 3336 .
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 the Aut o-Discovery 267
in PRTG is the easiest way to quickly configure a monitoring of your entire network.
For more information, see the manual section Quick St art Guide 46 .
More
Knowledge Base: How do I backup all data and configuration of my PRTG installation?
Knowledge Base: Customizing and Re-Branding the PRTG Web Interface
Knowledge Base: What about my web interface customizations as of PRTG 13.2.3?
Knowledge Base: How and where does PRTG store its data?
Knowledge Base: Updating from Version 7, 8, 9 or 12? Read this important message!
Knowledge Base: Can I update from PRTG Traffic Grapher or IP Check 5 to the current PRTG
version?
Knowledge Base: What does error code PE251 mean?
11/24/2017 83
Knowledge Base: The signature of my PRTG server is not valid. What can I do?
Knowledge Base: Which sensor types do you remove from PRTG and what are the alternatives?
84 11/24/2017
Part 4: Installing the Software | 3 Install a PRTG Core Server
4.3 Install a PRTG Core Server

Installing PRTG Network Monitor is easy and works like other Windows-based applications. To
install PRTG, 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 PRTG installation dialog will guide you through the installation process.
Setup Language Selec tion
Select a language for the program and click the OK button. The available language options
depend on both your Windows version and the setup file.
12/8/2017 85
Setup Dialog: Lic ense Agreement
Accept the license agreement and click Next .
Administrator Email Address
Enter a valid email address. Your PRTG server will send important and urgent system alerts to
this address. Click the Next button to continue.
For more information on how we process your personal data, see our Privacy Policy.
86 12/8/2017
Lic ense Key Information
Enter your license information. You have to provide the License Name and the License Key
exactly as you received it in the email or license document from us, the Paessler AG. We
recommend that you use copy&paste to avoid typos. Click Next to confirm.
You will find the label License Owner in some documents from the Paessler shop. License
Owner is the same as License Name for which you will be asked while installing PRTG or
when you change your license key 90 .
Setup: Installing PRTG
12/8/2017 87
After installation, PRTG opens the Ajax Web Int erface 156 in your system's default browser.
Make sure there is Google Chrome 61 or later (recommended), Mozilla Firefox 56 or later, or
Microsoft Internet Explorer 11 available on the system, and set as default browser (see
Sy st em Requirement s 23 ).
Enter License Information

PRTG will validate your license information during the install process by connecting to the
activation server. If you have entered incorrect license information before, PRTG will ask you to
re-enter a correct License Name and key. Please enter both License Name and License Key
exactly as received from Paessler. We recommend that you use copy&paste to avoid typing
mistakes.
For more details, see Ent er a License Key 90 .
If you think that you have correctly entered your license information but get a License Invalid
message, please contact sales@paessler.com.
More
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?
License Agreement
§ https://www.paessler.com/company/terms
Privacy Policy
§ https://www.paessler.com/company/privacypolicy
88 12/8/2017
Part 4: Installing the Software | 4 Install a PRTG Cluster
4.4 Install a PRTG Cluster

PRTG offers single failover clustering in all licenses—even 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, see Failover Clust er Configurat ion 3369 .
More
Knowledge Base: What's the Clustering Feature in PRTG?
11/24/2017 89
Part 4: Installing the Software | 5 Enter a License Key
4.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 that consists of 8 blocks with 5 characters each.
Your Personal License Information

You have received the License Name and the License Key from Paessler via email or in a
license document on Paessler shop. Please copy this information and insert it when PRTG asks
you to about your license information in the setup dialog.
For the Trial and Freeware editions, you will receive the required license information on
the Paessler webpage when you download the trial or freeware version of PRTG. For a
commercial edition, use your commercial license information.
EXAMPLE OF LICENSE INFOR MATION
License Name: John Q. Public

License Key: P1000-FFSEJ-ZHGRD-UR1CS-U73FG-G645F-YVF1D-H8323
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 installer dialog.
§ Trial/Freeware license key : When entering a Trial license key, you can experience unlimited
functionality of PRTG during the 30-day trial period. Your installation automatically switches to
a Freeware Edition afterwards. For details about how to get your free Trial edition, please
see Download PRTG 77 section.
§ Commercial license key : You can only enter this key if you have purchased a commercial
license. Your installation allows the number of sensors according to your license 21 .
Change License Key

Usually you do not need to enter a key manually after the installation to activate it, because
PRTG asks for it during the install process. However, there are still scenarios where you need
to change your key and activate this license. You have to provide your commercial license key,
for example, if you have purchased a PRTG Commercial Edition and want to upgrade your
running PRTG Freeware or Trial installation, or if you upgrade an existing commercial license to
a higher edition.
§ To enter a new license key, log in to the PRTG web interface 156 .
§ Choose Set up | License from the main menu bar 250 .
90 11/24/2017
Part 4: Installing the Software | 5 Enter a License Key
§ Click Change License Key .

§ The Updat e Your License page appears where you can activate your new license.
§ Choose the activation type Aut omat ic (online act ivat ion wit h opt ional HTTP proxy ) if
your PRTG server can connect to the internet.
Without internet access, you have to choose Manual (offline act ivat ion). The activation
process works a bit different in this case and requires manual interactions.
§ Provide your license information and click Updat e License.

§ PRTG will connect to the Paessler activation server via SSL on port 443 and validate your
license.
§ If everything works fine, you will see the message Act ivat ion was successful as License
St at us on top of the page.
For details, see manual section PRTG St at us—Licensing St at us and Set t ings: Updat e
Your License 3154 .
The PRTG core server needs an internet connection on port 443 to activate. If a proxy
connection is needed, please configure it in Step 3: Activate 3155 on the Updat e Your
License page. If activation fails, you can also try an offline activation.
Update Your Lic ense: Clic k Change Lic ense Key
More
Video Tutorial: PRTG License and Maintenance
§ https://www.paessler.com/support/videos/prtg-basics/license-maintenance
Video Tutorial: PRTG Sensor Count and License Upgrade
§ https://www.paessler.com/support/videos/prtg-basics/sensor-count
Knowledge Base: How do I upgrade to a higher edition of PRTG?
11/24/2017 91
Part 4: Installing the Software | 6 Activate the Product
4.6 Activate the Product

PRTG will activate your license automatically via the internet during the install process. Only if
PRTG cannot connect to the internet directly and so cannot access the activation server, will
you have to activate your license manually.
You have to complete the product activation process once to use PRTG, otherwise it will not
run. Do not forget to activate your commercial license when you want to upgrade your trial or
freeware installation!
Online Activation
Usually you do not need to enter a key manually after the installation to activate it, because
PRTG asks for it during the install process. However, there are still scenarios where you need
to change your key and activate this license. You have to provide your commercial license key,
for example, if you have purchased a PRTG Commercial Edition and want to upgrade your
running PRTG Freeware or Trial installation, or if you upgrade an existing commercial license to
a higher edition.
§ To enter a new license key, log in to the PRTG web interface 156 .
§ Choose Set up | License from the main menu bar 250 .
§ The Updat e Your License page appears where you can activate your new license.
§ Choose the activation type Aut omat ic (online act ivat ion wit h opt ional HTTP proxy ) if
your PRTG server can connect to the internet.
Without internet access, you have to choose Manual (offline act ivat ion). The activation
process works a bit different in this case and requires manual interactions.
§ Provide your license information and click Updat e License.

§ PRTG will connect to the Paessler activation server via SSL on port 443 and validate your
license.
Your License 3154 .
The PRTG core server needs an internet connection on port 443 to activate. If a proxy
connection is needed, please configure it in Step 3: Activate 3155 on the Updat e Your
License page. If activation fails, you can also try an offline activation.
92 12/8/2017
Part 4: Installing the Software | 6 Activate the Product
Offline Activation
If there is no internet connection available, you have to activate PRTG manually.
§ In the PRTG web interface 156 , choose Set up | License from the main menu bar 250 .
§ The Updat e Your License page appears where you can activate your license.
§ Choose the activation type Manual (offline act ivat ion) if your PRTG server cannot connect
to the internet.
§ Provide your license information and follow the instructions in step 3 3156 and step 4 3156 .
§ Click Updat e License.
Your License 3154 .
If your PRTG server is offline, you need to manually activate your license after you have
renewed your maintenance. This ensures you can enjoy the benefits of an active
maintenance like the possibility to install updates. Your maintenance information has to fit the
PRTG installer, so accomplish your offline activation before you install an update.
More
Knowledge Base: Which servers does PRTG connect to for Software Auto-Update and for
Activation?
12/8/2017 93
Part 4: Installing the Software | 7 Install a PRTG Remote Probe
4.7 Install a PRTG Remote Probe
Why are remote probes helpful for monitoring with PRTG? Because you can extend your
monitoring.
§ Remote probes allow you to monitor different sub-networks that are separated by a firewall
from your PRTG on premises core server and to keep an eye on remote locations. You can
install one or more remote probes 3359 .
§ Remote probes are useful if you want to distribute monitoring load by taking it from the
system running the PRTG core server and putting it on one or more remote probe machines.
§ You will need a remote probe if you want to monitor your local network using a PRTG in the
cloud instance.
§ Remote probes may be suitable monitoring components in several individual scenarios that
depend on your custom network setup.
All you need is a computer on which you can install your remote probe. See also the Sy st em
Requirement s for PRTG Remot e Probes 23 .
Steps to Go
To install a PRTG Remote Probe, follow these steps:
1. Prepare the PRTG Core Server 94 : only required for PRTG on premises
2. Download the Remote Probe Installer 97 : start here if you use PRTG in the cloud
3. Install the Remote Probe 97
4. Approve New Probe and Start Monitoring 100
Your PRTG on premises or PRTG in the cloud installations already include a local probe 3392
or cloud probe 3389 on the PRTG core server. This is why you cannot additionally install a
remote probe on your core server system.
PRTG updates remote probes automatically, but in rare cases a manual probe update is
required. You will receive a ToDo ticket 218 in this case. Please follow the steps below 97
to manually update a remote probe.
If you have issues after the installation, see this section: Debugging Remote Probe
Connection Problems 102
Do you run PRTG in a cluster? Then mind this important note 96 .
1. Prepare the PRTG Core Server
94 12/11/2017
So, if you use PRTG in the cloud, you can start with 2. Download t he Remot e Probe
Inst aller from t he PRTG Web Int erface 97 right away.
Because your remote probe needs to connect to your PRTG core server, PRTG needs to
accept incoming remote probe connections. So, on PRTG on premises, prepare your PRTG
server first when want you install the remote probe.
Edit the relevant settings in Sy st em Administ rat ion—Core & Probes 3108 . From the main menu
in the PRTG web interface 158 , select Set up | Sy st em Administ rat ion | Core & Probes to
access the probes settings and go to the Probe Connect ion Set t ings.
Probe Connec tion Settings in Sy stem Administration
St ep 1: Probe Connect ion IPs
By default, a core server accepts connections from the Local Probe only (IP address
127.0.0.1). This setting is the most secure setting, but it does not allow any remote probe to
connect to your PRTG core server.
To accept remote probes, choose one of the following settings:
§ All IPs available on t his comput er: Any IP on your core server system accepts incoming
probe connections.
§ Specify IPs: Specify selected IP addresses that accept incoming connections.
St ep 2: Allow IPs
12/11/2017 95
In the Allow IPs field, you can enter the IP address of the computer you want to install a
remote probe on. To make things easier, you can also enter the word any . Any will set the
PRTG core server to accept remote probes connecting from any IP address.
If you use any , make sure you write the word in lower case only! Any other variations will
not be valid!
Changing other settings is not required. For details about the fields for Access Key s, Deny
IPs, and Deny GIDs see section Sy st em Administ rat ion—Core & Probes 3109 .
When you are done, click Save to save your settings.
If you change this setting, PRTG needs to restart the core server to apply your changes.
After clicking the Save button, a dialog box appears that asks you to confirm the required
core server restart. Click OK to trigger the restart and follow the instructions on the screen.
During the restart all the users of the PRTG web interface, of the Ent erprise Console 3168 , or of
PRTG Apps for Mobile Net work Monit oring 3222 will be disconnected and reconnected.
To edit the core–probe connection settings you can also use the PRTG Administ rat ion
Tool 3297 on your core server.
PRTG Clust er and Remot e Probes Out side t he LAN
If you use the Clust ering 122 feature of PRTG and you want to run remote probes outside
your local network, you have to make sure your cluster nodes and the addresses they
use are reachable from the outside! Check your cluster node settings under Sy st em
Administ rat ion—Clust er 3133 before installing a remote probe outside your local network.
Enter addresses (DNS names or IPs) that are valid for both cluster nodes to reach each other
and for remote probes to reach all cluster nodes individually. Remote probes outside your LAN
cannot connect to your cluster nodes if they use local addresses.
If you already have a remote probe installed outside your LAN and the probe is
disconnected because of this, please follow these steps:
1. Uninstall the current remote probe.

2. Update the cluster node settings 3133 with addresses that are reachable from outside your
LAN.
3. Restart your PRTG core servers.
4. Install the remote probe again. It will then obtain the IP address or DNS name entries that it
can reach.
See also section Failover Clust er Configurat ion—Remot e Probes in Clust er 3372 .
96 12/11/2017
2. Download the Remote Probe Installer from the PRTG Web Interface
On the computer on which you want to install a remote probe, log in to the PRTG web
interface 158 . From the main menu bar 250 , select Set up | Downloads | Remot e Probe Inst aller.
Click Add Remot e Probe to start the installation assistant. In the appearing dialog window,
click Prepare and Inst all to start the download. Save the setup program to your local disk.
The Add Remot e Probe button is also available in the device tree.
Using the installation approach with the assistant, PRTG will guide you through the install
process. If you Download t he Remot e Probe Inst aller direct ly , you have to install the
remote probe without the assistant.
If you connect your remote probe to a PRTG on premises instance, prepare 94 your Probe
Connect ion Set t ings first.
Add Remote Probe Assistant
The version numbers of core and probe services must match. PRTG updates probes
automatically when a new version is installed on the PRTG core server. If PRTG advises you
to update your remote probe manually, open a web browser on your remote computer and
download the remote probe installer as described in this manual section.
The PRTG core system already includes a local probe or cloud probe service. This is why
you cannot additionally install a remote probe on that system.
3. Install the Remote Probe

§ Execute the setup program that you have just downloaded.
§ Confirm the Windows User Account Control dialog with Yes to allow the installation. The
usual software installation wizard will guide you through the installation process.
§ Click Inst all to start the installation process of your remote probe.
12/11/2017 97
PRTG Remote Probe Setup Installing
Please wait until the installation is completed. The remote probe will automatically connect to
your PRTG core server.
98 12/11/2017
PRTG Remote Probe Setup Connec ting to Serv er
If the remote probe successfully connects to your PRTG core server, you can complete the
setup of your new remote probe.
To allow your new remote probe to connect to a PRTG in the cloud instance, PRTG
automatically sets the Allow IPs field in Sy st em Administ rat ion—Core & Probes 3109 to
any . You can also use any for PRTG on premises, but we recommend that you use this setting
in intranets only. If any is not an option for you, cancel it in the Allow IPs field and enter the IP
address of your remote probe instead.
12/11/2017 99
PRTG Remote Probe Suc c essful Setup
Click Cont inue to finish the remote probe installation.
Finally, click Finish to exit the installation wizard. The remote probe is now installed on your
computer as a Windows service.
Approve the New Probe and Start Monitoring
Remember to log in to the PRTG web interface, confirm that the installation is done, and
acknowledge your new remote probe!
In the installation assistant, click Inst allat ion Done.
100 12/11/2017
Confirm that Installation is Done
If you successfully installed the remote probe from a PRTG in the cloud installation, you will
see the following dialog box.
Approv e PRTG Remote Probe for PRTG on demand
Click Approve and aut o-discover new probe to include your new remote probe device and
network in your device tree and to start the PRTG auto-discovery 267 . It helps you discover
devices and automatically create suitable sensors. Optionally, you can also choose to only
approve your remote probe without starting an auto-discovery by clicking Approve new
probe. The probe now appears as a new object in your device tree.
For unwanted probe connections, you can click Deny new probe. Note that this does not
uninstall the remote probe, but only prohibits the probe from connecting to the PRTG core
server.
If you deny or remove a remote probe, PRTG will automatically add this device's global ID
(GID) to the Deny GIDs list in Sy st em Administ rat ion—Core & Probes 3108 . Future probe
connections from this device will be denied automatically.
12/11/2017 101
Denying the remote probe in the PRTG device tree does not uninstall the probe, but only
denies access to the core server. The probe will continue to run on the target system
until you uninstall it manually.
PRTG Remote Probe Approv ed
In the Approving probe dialog, click OK to exit the dialog, or click Show probe in device
t ree to open the new probe in the device tree directly.
Once approved, PRTG automatically creates a set of sensors for the probe to ensure you can
detect bottle-necks on the probe system immediately. We recommend that you keep these
sensors. You can now create groups, devices, and sensors for monitoring via the new probe.
You do not have to approve remote probes after updates.
When a new probe connects to the core server for the first time, you will receive a new ToDo
ticket 218 in the PRTG ticket system.
Debugging Remote Probe Connection Problems

If you have trouble with your core probe connection, make sure that you meet the following
requirements:
§ The IP address of the computer on which you want to install a remote probe is not listed in
the Deny IPs field in Sy st em Administ rat ion—Core & Probes 3108 .
§ The default port 23560 for probe connections is not blocked by firewall rules on your PRTG
core server's side.
If you need to set a different port (not recommended), see this Knowledge Base article:
How can I customize PRTG's ports for core-probe-connections?
§ You can also take a look at the probe's logfiles. The probe process writes logfiles with a file
name in the format PRTG Probe Log (x).log. Open the one with the most recent date.
For a correct connection the probe log should look similar to this:
102 12/11/2017
11/6/2017 1:21:58 PM PRTG Probe V17.4.36.3253

11/6/2017 1:21:58 PM System time zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
11/6/2017 1:21:58 PM libeay32.dll=1.0.2.11
11/6/2017 1:21:58 PM ssleay32.dll=1.0.2.11
11/6/2017 1:21:58 PM PRTG Probe "example-DNS" starting on "example-DNS" (GID={AAAA1111-22BB-33CC-DD44-EEEEE
11/6/2017 1:21:58 PM Memory Manager: NexusMM4
11/6/2017 1:21:58 PM OS: Microsoft Windows 10 Enterprise (10.0 Build 15063), 4 CPUs (Quad x64 Model 78 Step
11/6/2017 1:21:58 PM Data Path: C:\ProgramData\Paessler\PRTG Network Monitor\
11/6/2017 1:21:58 PM System Path: C:\Program Files (x86)\PRTG Network Monitor\
11/6/2017 1:21:58 PM Local IP: 0.0.0.0
11/6/2017 1:21:58 PM Core Server IP: example-DNS.exampledomain.com
11/6/2017 1:21:58 PM Core Server Port: 23560
11/6/2017 1:21:58 PM SSL Enabled
11/6/2017 1:21:58 PM Probe GID: {AAAA1111-22BB-33CC-DD44-EEEEEE555555}
[...]
11/6/2017 1:21:58 PM Start Connection
11/6/2017 1:21:58 PM Start Done
11/6/2017 1:21:58 PM (14608):Initializing WMIConnectionPool
11/6/2017 1:21:58 PM (14608):WMIConnectionPool maximum number of concurrrent establishings is set to: 20
11/6/2017 1:22:03 PM Connect from to example-DNS.exampledomain.com:23560
11/6/2017 1:22:03 PM TCP connected from 10.49.12.51:55199 to example-DNS.exampledomain.com:23560
11/6/2017 1:22:03 PM State changed to connected (example-DNS.exampledomain.com:23560)
11/6/2017 1:22:03 PM Reconnect
11/6/2017 1:22:04 PM Connected
11/6/2017 1:22:10 PM Send Login
11/6/2017 1:22:10 PM Local: 11/6/2017 1:22:10 PM UTC: 11/6/2017 12:22:10 PM
11/6/2017 1:22:10 PM MarkUnused
11/6/2017 1:22:10 PM Login OK: Welcome to PRTG
If the connection fails, for example due to an incorrect Access Key , or due to incorrect IP
settings (see Prepare t he PRTG Core Server 94 ), you will see:
11/6/2017 1:42:02 PM Try to connect...
11/6/2017 1:42:02 PM Connected to 10.0.2.167:23560
11/6/2017 1:42:07 PM Login NOT OK: Access key not correct!
If you need to adjust any probe settings for the connection to the PRTG core server, use the
PRTG Administ rat ion Tool 3319 on your remote probe system.
12/11/2017 103
Remote Probe Settings in PRTG Administrator
In the Connect ion t o PRTG Core Server tab, you can then edit the following settings:
§ Server: Enter the IP address or DNS name of the core server the remote probe will connect
to. If Network Address Translation (NAT) is used, this has to be the IP address that is
externally visible, because the remote probe will connect from outside your network.
§ Probe Access Key and Confirm Access Key : Enter the access key that the probe will send
to the core server. This access key has to be defined on the PRTG core server in Sy st em
Administ rat ion—Core & Probes 3108 . Make sure the key phrases match exactly.
Remember to always click Save & Close to confirm your settings and to (re)start the probe
service.
For more detailed information about these settings, see section PRTG Administ rat ion
Tool 3319 .
More
Knowledge Base: How can I customize PRTG's ports for core-probe-connections?
104 12/11/2017
Part 4: Installing the Software | 8 Install the Enterprise Console
4.8 Install the Enterprise Console

The Enterprise Console is already included in a PRTG core server installation 85 (PRTG on
premises only) You can install additional Enterprise Consoles on other computers.
PRTG in the cloud does not support connections from the Enterprise Console. If you want
to use it, please connect the Enterprise Console to a PRTG on premises instance.
Download Enterprise Console from the Web Interface

The version of the Enterprise Console (EC) has to match the PRTG core server version you
want to connect to. It can connect to a PRTG server where the third entry in the version
number is equal to the third entry of the EC version number. For example, EC version
15.1.16.2023 can connect to any PRTG server with version 15.1.16.xxxx.
1. From the computer you want to install the Enterprise Console on, connect to the Ajax 156
web interface of PRTG.

2. On the login screen 158 of the web interface, enter login name and password and click
Download Client Soft ware (opt ional, for Windows, iOS, Android).
3. You will see the downloads page 3158 where you can download the EC.
4. Click Download: PRTG Ent erprise Console and save the setup program to the local hard
disk drive.
Install Enterprise Console

Execute the setup program PRTG_Ent erprise_Console_Inst aller.exe 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 assistant will guide you through the installation process.
11/24/2017 105
Setup Language Selec tion
Select a language for the program and click the OK button. The available language options
depend on both your Windows version and the setup file.
Enterprise Console Setup: Welc ome Sc reen
Click Next to walk through the wizard.
106 11/24/2017
Enterprise Console Setup: Lic ense Agreement
After accepting the license agreement, you can choose the folder you wish to install the
software in. We recommend that you use the default value.
11/24/2017 107
Enterprise Console Setup: Installation Folder
Select the start icons you want to create for the Enterprise Console. We recommend that you
use the default value.
108 11/24/2017
Enterprise Console Setup: Additional Tasks
Click Next to copy the necessary files to the disk of your computer.
After installation, click Finish to start the Enterprise Console. Enter the settings for the
connection to your PRTG server 3169 in the appearing dialog.
11/24/2017 109
Enterprise Console Setup: Finish
More
See the section Ent erprise Console 3168 for more information on how to use this Graphical
User Interface (GUI).
110 11/24/2017
Part 4: Installing the Software | 9 Uninstall PRTG Products
4.9 Uninstall PRTG Products

The uninstall process has six steps—regardless 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, run Uninst all PRTG Net work Monit or, Uninst all PRTG
Ent erprise Console, or Uninst all PRTG Remot e Probe, or open your Windows Control Panel
and choose the desired entry in the Programs section. Depending on the installed products,
not all uninstall programs are available.
Step 2
If asked, confirm the question of the Windows User Account Control with Yes to allow the
program to uninstall. The software uninstall dialog will guide you through the uninstall process.
Step 3
Confirm the removal of the software by clicking the Yes button.
Uninstall PRTG Network Monitor Step 1
Step 4
Wait while the software is being removed.
12/8/2017 111
Step 5
Confirm a system restart by clicking the Yes button.
Step 6
After system restart, the software is removed, but there still will be some custom data in the
PRTG program folder. 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, 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 on where the data is stored see the Dat a St orage 3383 section.
More
Knowledge Base: Can we remotely and silently uninstall a Remote Probe?
112 12/8/2017
12/8/2017 113
Part 5
Understanding Basic Concepts
3/7/2017 115
Part 5: Understanding Basic Concepts |
5 Understanding Basic Concepts

There is 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
52 .
Nevertheless, there are some basic principles we would like to explain to you. Please read
these sections carefully to understand the underlying workflow like architecture of the
monitoring system, hierarchy of objects, settings inheritance, and notifying. You will be able to
enhance your monitoring experience permanently as soon as you know the basic principles of
PRTG!
Understanding Basic Concepts—Topics

§ Architecture and User Interfaces 117
§ Clustering 122
§ Object Hierarchy 125
§ Inheritance of Settings 129
§ Tags 131
§ Dependencies 133
§ Scheduling 134
§ Notifying 135
§ Data Reporting 152
§ User Access Rights 148
§ IPv6 153
116 3/7/2017
Part 5: Understanding Basic Concepts | 1 Architecture and User Interfaces
5.1 Architecture and User Interfaces

What is PRTG Network Monitor and how does it work? If you are new to PRTG or simply want
to check if you got PRTG right, you are welcome on this page! We are glad to introduce PRTG
and its components to you.
Overview
You can classify the PRTG Network Monitor components in three main categories: System
parts, control interfaces, and a basic administration interface.
TYPE PAR T OF PR TG
System Parts Core Server 118

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 as a Windows service that runs
permanently.
Probe(s) 118
The part of PRTG that performs the actual monitoring. There are
local probes, remote probes, and cluster probes in PRTG on
premises, and there are cloud probes and remote probes in PRTG
in the cloud. All monitoring data is forwarded to the central core
server. Probes are configured as Windows services that run
permanently.
We assume that all computers on which the PRTG core server
with its local probe or any remote probes run are secure. It is
every administrator's responsibility to make sure that only
authorized persons can access these machines. For this reason
we highly recommend that you use dedicated machines for your
PRTG system parts.
User Interfaces PRTG Web Interface 156

The Ajax-based web interface is used for configuration of devices
and sensors, as well as for the review of monitoring results. Also
system administration and user management are configured here.
Enterprise Console 3168
A native Windows application 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!
PRTG Apps for Mobile Network Monitoring 3222
Monitor your network on the go with PRTG and apps for iOS and
Android.
12/8/2017 117
TYPE PAR T OF PR TG
System Administration PRTG Administration Tool on Core Server System 3297

Program Used to configure basic core server settings in PRTG on premises,
such as administrator login, web server IPs and port, probe
connection settings, cluster mode, system language, and more.
PRTG Administration Tool on Remote Probe System 3319
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 monitoring objects (for example, servers, workstations,

printers, switches, routers, virtual machines, and many more)
§ 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 PRTG on premises cluster 122 , 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 you access it via a browser
and also answers PRTG Application Programming Interface (API) calls (for example, for user
scripts or the Enterprise Console).
Core server and probe(s) are configured as Windows services that 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 via the sensors created on a device (for
example, computer, router, server, firewall). The probe receives its configuration from the core
server, runs the monitoring processes, and delivers monitoring results back to the core
server.
118 12/8/2017
On every system running a PRTG on premises core server, there is always a local probe
running on the same machine.
In PRTG in the cloud instances, there is always a cloud probe running on the PRTG core
server system that we host for you.
PRTG Core Serv er and Loc al Probe Monitoring a Loc al Area Network
Clic k here to enlarge.
The actual monitoring is performed by PRTG probe processes that run on one or more
computers.
Core server and probe(s) are configured as Windows services that are permanently run by
the Windows system without the requirement for a logged-in user.
Local Probe in PRTG on premises
During installation of PRTG on premises, the system automatically creates the Local Probe. In a
single-probe installation—which is the default setup—the local probe performs all monitoring.
The PRTG on premises core server with the local probe inside the corporate LAN (bottom-right
in the figure above) is able to monitor services and servers in the entire Local Area Network
(LAN). In PRTG in the cloud you need at least one remote probe 94 installation in your network
for this purpose.
Cloud Probe in PRTG in t he cloud
When creating a PRTG in the cloud instance, the system automatically adds the Cloud Probe.
The cloud probe shows monitoring values of the cloud instance and is able to monitor devices,
servers, and services that are publicly accessible in the internet like, for example, websites. To
monitor your Local Area Network (LAN), you need at least one remote probe 94 installation in
your network. The local probe is not available in PRTG in the cloud.
Remot e Probes
12/8/2017 119
You can create additional Remot e Probes to achieve monitoring of multiple locations, for LAN
monitoring with PRTG in the cloud, or for several other scenarios. They use Transport Layer
Security (TLS)-secured connections to the core and allow you to securely monitor services and
systems inside remote networks that are not openly accessible or are secured by firewalls. For
more information, please see Remot e Probes and Mult iple Probes 3358 .
For more information, see this video tutorial on our website: Distributed Monitoring with
PRTG using Remote Probes
Remote Probes: Monitoring of Sev eral Sc enarios
Clust er Probes in PRTG on premises
In a cluster setup 122 , a cluster probe runs on all nodes. This is the additional Clust er Probe. All
devices that you create 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.
Mini Probes in PRTG on premises
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 you can create them on any platform. For more information, see the Mini Probe API
definition in the PRTG web interface (see section Applicat ion Programming Int erface (API)
Definit ion 3336 ).
120 12/8/2017
System Health Monitoring

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
Healt h 628 and Probe Healt h 1484 , Sy st em Healt h 2456 , Clust er Healt h 615 , disk free 2709 , and
bandwidth 2577 sensors for all installed network cards, as well as a Common SaaS sensor 620
that checks the availability of widely used SaaS providers.
We recommend that you keep 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 computes a resulting value. Frequent or
repeated values below 100% should be investigated. Please check the channels 186 of a
particular sensor for details.
More
Looking for a comprehensive PRTG training? PRTG e-learning in 9 modules:
§ https://www.paessler.com/support/training/e-learning
Video Tutorials: Learn about the PRTG Network Monitor basics on the Paessler video tutorials
page.
§ https://www.paessler.com/support/videos/prtg-basics
Video Tutorial: Distributed Monitoring with PRTG using Remote Probes
§ https://www.paessler.com/support/videos/prtg-basics/distributed_monitoring
Video Tutorial: What is a sensor?
§ https://www.paessler.com/support/videos/prtg-basics/what-is-a-sensor
Video Tutorial: PRTG User Interfaces
§ https://www.paessler.com/support/videos/prtg-basics/user-interfaces
12/8/2017 121
Part 5: Understanding Basic Concepts | 2 Clustering
5.2 Clustering
The main goal of any monitoring solution is to help you reach 100% availability of your IT and
network infrastructure and avoid costly downtimes. Because of this, it is necessary to
permanently monitor the IT infrastructure and so the objective is to reach true 100% uptime for
the monitoring tool. It needs a high availability mechanism for this purpose like, for example,
clustering.
PRTG Network Monitor not only allows you to monitor all your infrastructure with only one
tool, but also to monitor it twenty-four hours a day and offers a high availability cluster out-of-
the-box. With clustering, 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.
A PRTG Cluster consists of two or more installations of PRTG 85 that work together to form a
high availability monitoring system. All PRTG on premises licenses allow you to have a simple
cluster, composed of two PRTG installations working together.
How a PRTG Cluster Works

A PRTG cluster consists of at least two nodes: one Primary Mast er Node and one or more
Failover Nodes, where up to 4 failover nodes are possible. Each cluster node is simply a full
installation of PRTG that could perform the whole monitoring and alerting on its own.
Cluster 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.
Cluster with Two Nodes
During normal operation you configure devices, sensors, and all other monitoring objects on
the Primary Mast er using the web interface 156 or Enterprise Console 3168 . The master node
automatically distributes the configuration to all other nodes in real time.
122 12/8/2017
All devices that you create on the Clust er Probe are monitored by all nodes in the cluster, so
data from different perspectives is available and monitoring for these devices always continues,
even if one of the nodes fails. If the Primary Mast er fails, one of the Failover Nodes will take
over the master role and control the cluster until the master node is back. This ensures a fail-
safe monitoring with gapless data.
A PRTG cluster works in act ive-act ive mode. This means that all cluster nodes are
permanently monitoring the network according to the common configuration received from
the current master node and each node stores the results into its own database. The storage
of monitoring results is also distributed among the cluster. PRTG updates need to be installed
on one node only. This node will automatically deploy the new version to all other nodes.
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 (for
example, via email, SMS text message, push message). Because of this, the administrator will
not be flooded with notifications from all cluster nodes in case failures occur.
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.
Because the monitoring configuration is managed centrally, you can only change it on the
master node, but you can review the monitoring results by logging in to the web interface of
any of the failover nodes in read-only mode.
If you use remote probes in a cluster 3372 , each probe connects to each node of your cluster
and sends the data to all cluster nodes, the current primary master as well as the failover
nodes. You can define Clust er Connect ivit y of each probe in the Probe Administ rat ive
Set t ings 354 .
Performance Considerations for PRTG Cluster

As a consequence of this concept, monitoring traffic and load on the network is multiplied by
the number of used cluster nodes. Moreover, the devices on the cluster probe are monitored
by all cluster nodes, so you will encounter an increase of monitoring load on these devices.
This will not be a problem for most usage scenarios, but consider the Det ailed Sy st em
Requirement s 30 . As a rule of thumb, each additional node in the cluster results in dividing the
number of sensors that you can use by two.
More than 5,000 sensors per cluster are not officially supported. Please contact your
presales team if you exceed this limit and see this Knowledge Base article for possible
alternatives to a cluster: Are there alternatives to the PRTG cluster when running a large
installation?
Set Up a PRTG Cluster

For detailed information, see Failover Clust er Configurat ion 3369 .
12/8/2017 123
More
Knowledge Base: What's the Clustering Feature in PRTG?
Knowledge Base: In which web interface do I log in if the Master Node fails?
Knowledge Base: Are there alternatives to the PRTG cluster when running a large installation?
Video Tutorial: Cluster in PRTG — This is how it works
§ https://www.paessler.com/support/videos/prtg-advanced/cluster-animation
Video Tutorial: How to set up a PRTG cluster
§ https://www.paessler.com/support/videos/prtg-advanced/how-to-set-up-a-cluster
124 12/8/2017
Part 5: Understanding Basic Concepts | 3 Object Hierarchy
5.3 Object Hierarchy

All objects in a PRTG monitoring configuration are arranged in a treelike 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 particular locations. This hierarchical order 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 129 ).
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 several groups.
§ A Group contains one or several devices.
§ A Device represents a physical or virtual component in your network that is reachable via an
IP address. Several sensors are attached to one device.
§ A Sensor monitors one single aspect of a device and has at least one channel.
§ A Channel tracks one specific data stream and displays it as 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 129 mechanism, we recommend that you adjust the default settings for
the Root group 314 . This will make configuration easier later on, because all other objects then
inherit these standard settings by default. Thus, you will not have to set up the same
configuration for each object anew.
11/24/2017 125
Probe
Each group (except the Root group) is part of a Probe. This is the platform where the
monitoring takes place. All objects configured below a probe will be monitored via that probe.
Every PRTG on premises core server installation automatically installs a Local Probe service,
every PRTG in the cloud instance comes with a Cloud Probe.
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 3358 ). In a PRTG on premises 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 so that they inherit the same settings. To a group, you add
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.
PRTG Dev ic e Tree View
126 11/24/2017
Device
You can add Devices that you want to monitor to each probe or group. 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
Sometimes you may want to add the same device in PRTG several times to receive a better
overview when using a large number of sensors for 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 where the probe is running and monitors its health
parameters with several sensors running on it.
To get a better and more detailed picture about your devices, PRTG automatically analyzes the
devices that you add and recommends appropriate sensor types 412 on the device overview
tab 186 . In the Recommended Sensors table, click the Add These Sensors button in the
corresponding table row to create recommended sensor types with one click.
You can turn off the sensor recommendation in Sy st em Administ rat ion—Monit oring 3100 .
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.
For more information, see this video tutorial: What is a sensor?
11/24/2017 127
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
§ Response t ime of a Ping request to a device
§ Response t ime of a Remote Desktop service
§ etc.
More
Video Tutorial: What is a sensor?
§ https://www.paessler.com/support/videos/prtg-basics/what-is-a-sensor
128 11/24/2017
Part 5: Understanding Basic Concepts | 4 Inheritance of Settings
5.4 Inheritance of Settings

The hierarchical tree 125 does not only help organize the devices and keep everything neat and
tidy. There is also an important aspect involved that we call inheritance. To ensure
administration is quick and easy—especially for large monitoring setups—certain settings are
inherited from the higher 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 not be affected.
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 148
§ Tags 131
§ Paused status: If an object is paused by the user, or a schedule, all sensors on it are paused
as well
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 cannot be changed on sensor level.
The screenshot below shows the Windows systems credentials settings inherited from the
parent.
Inherited Credentials for Windows

Sy stems
Click next to inherit from [parent object ] to override the parent's settings and enter new
settings for this object and all objects underneath in the hierarchy.
11/24/2017 129
Part 5: Understanding Basic Concepts | 4 Inheritance of Settings
Credentials for Windows Sy stems
Click Save for your settings to take effect. Clicking after entering your settings inherits
the parent settings again and your settings will not take effect.
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 settings and set the default values to suit
your setup. This should include the credentials for the types of systems in your network that
you want to monitor (Windows, Linux, virtual servers, etc.).
See section Root Group Set t ings 314 for more details.
Inheritance of Notification Triggers

If you add notification triggers at probe, group, or device level, these will also be inherited to
all sensors underneath, unless you break the inheritance manually.
See section Sensor Not ificat ions Set t ings 2924 for details.
130 11/24/2017
Part 5: Understanding Basic Concepts | 5 Tags
5.5 Tags
For every object in your PRTG setup, you cannot only name objects, you can also define tags
in the object settings 205 to additionally mark an object as a member of certain categories.
Although some tags are automatically predefined when adding objects 285 , you are completely
free in which tags you want to add. For example, you can mark all of the bandwidth sensors
that are especially important for you with the tag bandwidth_important.
Later on, you can view lists of objects with certain tags (helpful for multi-edit 2949 of settings), or
select sensors via tags when creating reports 3000 . A smart arrangement of tags can be a huge
time saver. The keys enter, space, or comma confirm a tag.
You can also change tags for several objects simultaneously using the multi-edit 2949
function.
View and Edit Tags in Basic Sensor Settings
Tags are Inherited

The tags in the settings of an object are automatically inherited 129 by all other objects
underneath in the Object Hierarchy 125 . You can view inherited tags in section Parent Tags in
the settings of a sensor 127 , device 127 , or group 126 . So, for example, a device with the tag
myExampleTag automatically passes on this tag to all sensors that you add to it. These sensors
appear in lists whenever you search for myExampleTag. This is useful, for example, when you
add sensors by tag in reports 3000 settings, because you do not have to tag every single sensor
manually.
Inheritance for tags cannot be disabled.
11/24/2017 131
Part 5: Understanding Basic Concepts | 5 Tags
Filtering with Tags

You can use tags to filter table lists 225 for specific objects, or to add sensors to Libraries 2984
and Report s 3000 . For example, you can restrict the sensors overview page 254 to the sensors
that 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 the tags to
include or exclude them:
§ 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 either a + or – must exist on 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 that 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.
It is not possible to search or filter for tags that include a closing round parenthesis ")"
because it will be removed when confirming the tag input into the filter field.
132 11/24/2017
Part 5: Understanding Basic Concepts | 6 Dependencies
5.6 Dependencies
You can use dependencies to make PRTG pause sensor monitoring based on the status 183 of
another (master) sensor 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 in Down status or in Paused status caused by another dependency. This means, for
example, that you can stop monitoring remote network services when the corresponding
firewall is down due to connection problems.
When using the auto-discovery 267 function, the Ping Sensor 1424 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 Down status or in Paused status caused by another dependency. Usually,
it makes little sense to monitor any other parameters while the Ping sensor indicates that the
device can't even be reached.
You do not trigger a status change by dependency if you manually pause a master object
or if you pause it by schedule 134 . See also this Knowledge Base article Why will dependent
objects not go into paused status automatically when I pause the master object?
To view the list of dependencies, choose Devices | Dependencies and the corresponding
dependencies path from the main menu 252 . From there you can also access the
Dependencies Graph 2959 that visualizes all dependencies within your network.
Dependenc ies Graph
For more information about the dependency settings, see the settings of the object 205
you want to set a dependency for, section Schedules, Dependencies, and Maint enance
Window 405 respectively.
11/24/2017 133
Part 5: Understanding Basic Concepts | 7 Scheduling
5.7 Scheduling
With the help of schedules you can pause 232 the monitoring of certain objects automatically
for a certain time, for example, on 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 135 . You
can also pause monitoring for planned system maintenance time spans to avoid false alarms.
You can apply different schedules to every object. Schedules are also used for reports and
notifications.
If you pause a master object by schedule or manually, you do not trigger a status change
by dependency 133 . See also this Knowledge Base article Why will dependent objects not
go into paused status automatically when I pause the master object?
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, see Account Set t ings—Schedules 3079 section.
If you use failover clustering with nodes in different timezones, scheduling applies at the
local time of each node. For more information, see section Failover Clust er
Configurat ion—Before Get t ing St art ed 3370 .
134 11/24/2017
Part 5: Understanding Basic Concepts | 8 Notifying
5.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 with which you can be notified (for example,
email 3063 , SMS 3057 , push messages 3064 , 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 2966 section for more details and Set t ing Up Not ificat ions Based on
Sensor Limit s: Example 2969 for a step-by-step guide.
Limits
In a sensor channel's settings 2915 , 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 an 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 for keeping 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 207 section for more details.
Logs
In the logs list, the logfile with all monitoring events is shown. In a typical setup, a huge
amount of log data is produced. 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 216 section for more
information.
Tickets
The tickets list shows items with important system information or action steps for the
administrator to take. You should view every ticket and take appropriate actions. By 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
218 section for more information.
12/11/2017 135
1 Alerts
5.8.1 Alerts
Alerting is a helpful and important part of monitoring that informs you when there are issues,
when values exceed thresholds or a sensor status has changed, for example. PRTG offers
many ways to alert you about your monitoring data like internal sensor alerts, limits, and
lookups. You can also create custom alerts and define trigger notifications as extensions to
alerts. If a sensor does not have pre-configured limits, you can also configure them accordingly
so that you are notified when something is wrong.
Internal Sensor Alerts

Some sensor types display internal alerts when there are errors. These default alerts range
from disconnected probes to socket or timeout errors. For example, the HTTP sensors show
pre-configured internal alerts according to certain HTTP status codes.
There are also sensor types that let you modify the internal sensor alerts. To see if you can
modify an alert, check the sensor's settings for customizable options.
See Which HTTP status code leads to which HTTP sensor status? for more information.
See What does error code PExxx mean? for more information on error codes.
Here is an example of a sensor that is in Down status 183 because of an internal sensor alert.
Probe Health Sensor with Disc onnec ted Probe Alert
136 11/24/2017
1 Alerts
Standard Limits for Channels

Another type of alerts are alerts due to limits. These alerts are triggered when the measured
value of a sensor is below or above a configured threshold limit. These limits change the
sensor's status when they are breached. For example, you can set an SNMP CPU Load sensor
to Warning status whenever it measures values that you consider critical. This sensor then
shows up in the alarms 207 list.
This type of alert is only displayed when the value breaches the configured limits. If the
value is normal again in the next sensor scan, the sensor returns to the Up status.
§ To review or modify threshold limits for single sensors, open the sensor's channel settings
2915 via the gear icon in the respective channel gauge or in the channels table.
§ Enable Limit s at the bottom of the channel settings dialog and specify your desired limits in
the correct fields.
§ You can also optionally add messages that appear in the sensor message on the Overview
tab or leave these fields empty to display the default message.
This limit only applies to the respective channel.
11/24/2017 137
1 Alerts
Setting Limits for Sensor Channels
For more information on setting limits, see this video on our website: How to Set Channel
Limits
With the above configuration, the sensor turns to a Warning status (the gauge needle points
to the yellow area in the example below) if the channel values exceed the upper warning limit
of 60 percent and the Warning Limit Message is displayed in the sensor status. If the channel
value exceeds the upper error limit of 80, the sensor will turn to a Down status (the gauge
needle will point to the red area) and the Error Limit Message will be displayed.
138 11/24/2017
1 Alerts
CPU Load Sensor in Warning Status
You can use Mult i-Edit 2952 if you want to apply the same limits for sensors of the same type in
a batch operation.
§ To see all sensors of this type at a glance, just filter for it: From the PRTG main menu bar,
choose Sensors | By Ty pe | SNMP CPU Load.
§ Mark the checkboxes of the sensors you want to edit.
§ Click the wrench symbol in the menu.
§ Open the Channel Set t ings tab.
§ Select the channel you want to add a limit for; in this example we use the channel Tot al,
which is common to all selected sensors.
§ Then Enable Limit s at the bottom of the dialog and enter the number in the correct field as
described above.
When you are done, Save these settings—the new limit is then applied to all selected channels
from all selected sensors.
Multi-edit is only available for channels that are common to all selected sensors.
11/24/2017 139
1 Alerts
Setting Channel Limits with Multi-Edit
Some sensors have pre-defined limits in the sensor settings, for example the SNMP Linux
Disk Free Sensor 2058 . Refer to the sensor's settings to adjust the limits (or behavior) for
these sensors.
Absolut e and Delt a Values in Limit s
The value that needs to be configured in the limits depends on the type of data that the
sensor's channel delivers.
For channels that measure absolute values (for CPU load and memory usage, for example) limits
will also be set using absolute values like in the example above.
140 11/24/2017
1 Alerts
You can also set limits for channels that measure delta (x.xx/sec) values. Let's say you have an
SNMP Traffic Sensor 2265 and want to receive an alert when it reports errors. In this case, you
need take into account that this is a delta measurement. In this example, you could set the
following limits for the channel Errors in with a standard scanning interval (60 seconds).
§ Set the sensor to Warning status when 1 error occurs

§ Set the sensor to Down status when 30 errors occur
This example shows how to configure the limits for delta channels.
Setting Channel Limits with Delta Values
Because this channel uses per second (delta) measurements, a single error that occurs over a
standard 60-second scanning interval is reported as 0.016 # per second. So the warning limit
for one single RX error within an interval is 0.1 (errors/sec). To get an alert when there are 30
errors within a scanning interval, the limit needs to be 0.5 (errors/sec).
11/24/2017 141
1 Alerts
If no new errors occur in the next scanning interval, the sensor will turn back to the Up
status. To ensure that you do not miss any notifications for this sensor, set a notification
trigger with 0 seconds. For more information, see Triggers (Not ificat ions) as Ext ensions t o
Alert s 145 below.
Standard Lookups for Channels

PRTG also uses lookups for some sensor types. In general, lookups make data more human
friendly because they map status values as returned by a device (usually integers) to more
informative expressions in words that show you the status of a monitored device as a clear
message.
Additionally, lookups can also define the sensor status that will be shown in correlation with
certain status codes, just like sensor channel limits can define a sensor status, too. For
example, PRTG can show a sensor in a gray Inact ive status with channel values, provided by
lookups, like Inact ive instead of a numerical value like -1.
The various states displayed in gauges always follow the clockwise order Up (green) <
Warning (yellow) < Down (red) < Unknown (Gray / Black).
SNMP HP LaserJet Hardware Gauge
Modifying a Standard Lookup: Example

You can also modify standard lookups to include new definitions according to your monitoring
needs. The following code illustrates the lookup definition for the paper status of the SNMP
HP LaserJet Hardware 1921 sensor:
142 11/24/2017
1 Alerts
<?xml version="1.0" encoding="UTF-8"?>

<ValueLookup id="oid.paessler.hplaserjet.paperstatus" desiredValue="0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=
"PaeValueLookup.xsd">
<Lookups>
<SingleInt state="Ok" value="0">
Paper Okay
</SingleInt>
<SingleInt state="Error" value="1">
Out of Paper or No Cassette Loaded
</SingleInt>
Manual Paper Feed Required
</SingleInt>
</Lookups>
</ValueLookup>
Imagine you do not want to be alerted in case the printer is out of paper. You basically have to
do the following:
1. Copy the file oid.paessler.hplaserjet.paperstatus.ovl to the \lookups\cust om subfolder of

the PRTG program directory 3383 (ensure you do not change the file name!).
2. Open this file with an editor.
3. Replace the first SingleInt state "Error" with "Ok".
4. Optionally replace the message "Out of Paper or No Cassette Loaded" to "Ok".
5. Save the file.
6. Reload 3354 the custom lookup folder in PRTG.
The channel gauge now displays the new state and the new message.oid
SNMP HP LaserJet Hardware Gauge Modified
11/24/2017 143
1 Alerts
For more information on how lookups are defined, see section Define Lookups 3345 .
Creat ing a New Lookup
It is also possible to create new lookups to use with any custom or standard sensor that
supports lookups. If you want to create a new lookup with the example 142 above, you
basically follow the same procedure except you save the lookup file in the \lookups\cust om
subfolder with a new name, for example oid.paessler.hplaserjet.mynewpaperstatus.ovl. Select
the newly created lookup file in the sensor's channel settings.
Selec ting a Newly Created Lookup
Cust om St ring Lookups
144 11/24/2017
1 Alerts
You can also set up custom string lookups, which can exclusively be used with the SNMP
Cust om St ring Lookup Sensor 1810 . This is useful if you are using an OID that returns a known
string value stating possible states or values. To inform PRTG of the possible statues or values,
you have to create a new lookup file defining them.
See the Knowledge Base article Monitor and "Lookup" a SNMP String value for more
information.
Triggers (Notifications) as Extensions to Alerts

The status or the data of a sensor can trigger notifications. Using this mechanism, you can
configure external alerting tailored to your needs. Which trigger types are available depends
on the kind of object you edit. You can define triggers that are activated by an 'on change'
event. Some sensors offer the option to send such a trigger whenever sensor values have
changed.
Create Triggers to Alert You When a Value Changes

Before you set up a change trigger, make sure that the Trigger 'change' not ificat ion
setting is enabled in the sensor's settings, otherwise the notification will never be sent.
Trigger 'Change' Notific ation Setting
11/24/2017 145
1 Alerts
Select the Not ificat ions tab to create a change trigger for this sensor. Hover over and
select Add Change Trigger from the menu to add a new trigger, or click the Edit button next
to an existing notification to change it. Every trigger will provoke one or more notification(s)
3057 to be executed.
Adding a Change Trigger Notific ation
Save the trigger. You will now be notified when sensor values change.
For more information on triggers, see section Sensor Not ificat ions Set t ings 2924 .
Create Triggers to Match Your Limits/Lookups (status-based)

After you have set up alerts using limits or lookups, you can complement them with state-
based triggers. On the Not ificat ions tab, hover over and select Add St at e Trigger from
the menu to add a new trigger.
Adding a State Trigger Notific ation
Save the trigger. You will now be notified according to the notification settings.
If you want to receive alerts for more than one status, you have to add a trigger for each
status.
A sensor's status can change for other reasons such as internal sensor alerts 136 . If you
configure state-based triggers, you will be notified of these changes as well.
146 11/24/2017
1 Alerts
More
Knowledge Base: Monitor and "Lookup" a SNMP String value
Knowledge Base: Which HTTP status code leads to which HTTP sensor status?
Knowledge Base: What does error code PExxx mean?
Video Tutorial: How to Configure Lookups in PRTG Network Monitor
§ https://www.paessler.com/support/videos/prtg-advanced/prtg-lookups
11/24/2017 147
Part 5: Understanding Basic Concepts | 9 User Access Rights
5.9 User Access Rights

Define which user can access what in your PRTG Network Monitor installation and manage all
user rights with the access rights system of PRTG.
The default administrator can be the only user of a PRTG installation, but can also create a
nearly unlimited number of other users. Individual users are organized in a nearly unlimited
number of user groups. Each user group can separately have access rights for each individual
object 125 in your PRTG device tree (except for sensor channels). Objects can also inherit 129
access rights according to the hierarchic structure of the device tree.
In addition, every user has specific rights: There are administrator users, read/write users, and
read-only users. You can define these settings in System Administration—User Accounts 3116 .
Via these tools, you can create an access rights management that allows you to specify
exactly what users will be able to see and edit and what they will not be able to access.
User Rights in User Ac c ount Settings
Individual user rights, in combination with the access rights of the group(s) they belong to,
determine the access rights to certain objects in the device tree. This means that group
membership specifically determines 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 the object's
settings. You can define different access rights for all sensors, devices, groups, or probes via
the corresponding Context Menus 234 or in the Object Settings 205 .
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):
148 11/24/2017
§ 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: You can only see monitoring results and change your own password if allowed by
your administrator.
§ Writ e: You are allowed to review monitoring results and edit settings. In addition, you can
add objects to and delete them from the device tree.
§ Full: Review monitoring results, edit settings, and edit access rights. In addition, you can add
objects to and delete them 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. Users in the
administrator user group always have maximum access rights to all objects and will never
have access restrictions.
Access rights that are defined locally on an object, for example, on a device, override
inherited rights. For a certain object, the highest directly defined 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 129 or there is no higher object level.
11/24/2017 149
Different Ac c ess Rights Depending on User Groups
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.
Users are either members in PRTG user groups or in Active Directory Domain user groups.
They cannot be members in both. We recommend that you 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
150 11/24/2017
§ PRTG User Read Read-only rights Read-only rights Read-only rights Admin rights
Only
§ Domain User
Read Only
§ 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 always have administrator access rights, no matter what
access rights have been defined for an object.
§ Read-only users just have reading permission, no matter what access rights their group has.
Users who are members of an administrator group are an exception. Read-only users can
change their own passwords in their user account settings 3116 , if the administrator has
enabled them to do so.
§ Read/writ e users in a group with full access to a given object have full access rights to this
object only.
§ If a user is in more t han one group, access rights of the user group with the highest rights
apply.
§ Administrator rights can only be granted by membership in the administ rat or group.
For more information about defining access rights, see the following sections:
§ Sy st em Administ rat ion—User Account s 3116
§ Sy st em Administ rat ion—User Groups 3123
For information about connecting PRTG to an existing Active Directory, see Act ive
Direct ory Int egrat ion 3333 .
11/24/2017 151
Part 5: Understanding Basic Concepts | 10 Data Reporting
5.10 Data Reporting

With Report s 3000 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 the Hist oric Dat a
Report s 192 section for more information.
Generate Reports
You can use the sophisticated reports machine included in PRTG to create comprehensive and
detailed reports for all monitoring data. See the Report s 3000 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 the Using t he PRTG API (Applicat ion
Programming Int erface) 3336 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 the User Access Right s 148 section), or you can create public or semi-public HTML
pages with monitoring data using the Maps feature. See the Maps 3026 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, see the Paessler website: Billing Tool
More
§ Dat a St orage 3383
Paessler Website: Billing Tool

§ https://www.paessler.com/tools/billingtool
152 11/24/2017
Part 5: Understanding Basic Concepts | 11 IPv6
5.11 IPv6
PRTG supports the IPv6 protocol for most sensor types. You can choose whether you want
PRTG to query data from your network devices via an IPv4 or IPv6 connection. Indicate your
preference in the Device Set t ings 385 of each device. The sensors you add to the device will
use the protocol you have indicated.
In the Out going IP Set t ings of the PRTG Administ rat ion Tool 3323 , you can additionally
choose which IPv6 address will be used for outgoing monitoring requests. The the same
option is also available for IPv4.
Not all sensor types are IPv6 compatible. You can see which sensors support IPv6 in the
Add Sensor 309 dialog. Incompatible sensors are not selectable on IPv6 devices.
The Cloud HTTP Sensor 597 and the Cloud Ping Sensor 606 do not support IPv6 although
you can add them to IPv6 devices. You will receive an error message if you do so.
6/9/2017 153
Part 6
Ajax Web Interface—Basic Procedures
6/9/2017 155
Part 6: Ajax Web Interface—Basic Procedures |
6 Ajax Web Interface—Basic 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 and uses Asynchronous Java Script and XML (AJAX) to deliver a
powerful and easy-to-use user experience. While you are logged in 158 , the PRTG web interface
continuously refreshes the data on the screen (via Ajax calls) so it always shows the current
monitoring results (you can set 3116 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 a 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 so that you see more information at a glance.
The following sections introduce the features and concepts of the Ajax Graphical User
Interface (GUI).
If you are interested in a video overview of the PRTG web interface, see this video tutorial:
The PRTG Web User Interface—Overview
Ajax Web Interface—Basic Procedures—Topics

§ Login 158
§ SSL Certificate Warning 162
§ Welcome Page 165
· Customer Service 168
§ General Layout 170
§ Sensor States 183
§ Review Monitoring Data 186
§ Compare Sensors
§ Historic Data Reports 192
§ Similar Sensors 197
§ Recommended Sensors 201
§ Object Settings 205
§ Alarms 207
§ System Information 210
§ Logs 216
§ Tickets 218
§ Working with Table Lists 225
156 6/9/2017
Part 6: Ajax Web Interface—Basic Procedures |
§ Object Selector 228
§ Priority and Favorites 229
§ Pause 232
§ Context Menus 234
§ Hover Popup 249
§ Main Menu Structure 250
Other Ajax Web Interface Sections

§ Ajax Web Interface—Device and Sensor Setup 266
§ Ajax Web Interface—Advanced Procedures 2938
Related Topics
§ Enterprise Console 3168
§ PRTG Apps for Mobile Network Monitoring 3222
6/9/2017 157
Part 6: Ajax Web Interface—Basic Procedures | 1 Login
6.1 Login
For PRTG on premises instances, you can log in to the web interface once the PRTG core
server is installed 85 . In your browser, load the IP address or DNS name of the computer PRTG
is installed on and log in using the Login button. For PRTG in the cloud instances, open your
registered PRTG in the cloud domain and log in to the web interface.
You can look up and change the web server settings of PRTG on premises instances at any
time using the PRTG Administ rat ion Tool 3298 Windows application on the system where the
PRTG core server is installed. 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. If
you are using PRTG in the cloud, enter the URL of your instance, for example myfirstdomain.my-
prtg.com to access the web interface with a supported browser 31 .
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 the PRTG web interface. Please use
your local IP address or http://127.0.0.1 instead.
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 162 .
Login Screen PRTG on Premises

After loading the web interface, the login screen is visible. You can either login as default
administrator or as any other PRTG user. As PRTG Administrator user you can use all
functionalities of the web interface. Administrators can create additional users 3116 with
administrator rights or with more restricted privileges (for example, read-only users).
158 12/8/2017
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. PRTG automatically fills in the default credentials and shows the
password in plain text.
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 .
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 3308 Windows application.
If you enter another login name or change your password, the password is no longer
shown in plain text.
Login as PRTG User
If you have received user credentials from your administrator, please enter them here to log in.
Also, when using other administrator credentials, please enter them here.
Login Options
§ Login: Log in to the fully featured Ajax web interface, which is the standard interface. We
recommend that you use this option for PRTG whenever possible. It offers the full
functionality of PRTG. Use Google Chrome 61 or later (recommended) or Mozilla Firefox 56
or later for best performance. In some browsers, the Ajax option is not shown, for example,
in old browser versions.
12/8/2017 159
Although you can log in using Microsoft Internet Explorer 11, the Ajax web interface
might not be fully compatible with Internet Explorer! When using Microsoft Internet
Explorer 11, please set the security level to Medium-high (or lower) and make sure no
Compat ibilit y View is enabled!
§ Download Client Soft ware (opt ional, for Windows, iOS, Android): This option opens the
PRTG download page 3158 in the web interface. You can optionally download the native
Windows application Ent erprise Console to the desktop. You have to install 3168 it on the
client computer before use. The Enterprise Console 3168 provides full functionality. However,
for some functions the Ajax Web GUI opens. As an additional feature, the Enterprise Console
can view data of several independent PRTG core installations in one single application.
Also, when using this download option, your name and password (or the default
credentials) are required for login!
Only Google Chrome 61 or later (recommended) and Mozilla Firefox 56 or later are fully
compatible with the Ajax web interface.
Enter specific credentials or use the default credentials, which are automatically filled in, and
click the Login button to proceed to the PRTG web interface.
Login Screen PRTG in the cloud

For PRTG in the cloud instances, load the PRTG web interface with the domain you have
registered at https://my-prtg.com and use the login method that you chose when signing up.
PRTG in the Cloud Login Sc reen
To log in with Facebook, Google+, Windows, or Amazon, click the respective button. A popup
window appears where you can enter your credentials for the respective account.
Alternatively, you can log in with the email and password that you chose when signing up. If
you have received an invitation to PRTG in the cloud, click the link in the invitation and proceed
to log in.
160 12/8/2017
Recover Password
If you cannot remember your PRTG on premises password, click the Forgot password? link.
The Password Recovery page opens. Enter your Login Name, click Request a New
Password, and PRTG will send a new password to the primary email address of this PRTG user
account. The Need Help? link will open the current manual page.
If you cannot remember your PRTG in the cloud password, click the Change/reset password
link. You are then asked to enter your email address. Click Change/reset password again and
PRTG will send you an email to reset your password.
12/8/2017 161
Part 6: Ajax Web Interface—Basic Procedures | 2 SSL Certificate Warning
6.2 SSL Certificate Warning

If you use PRTG on premises outside your internal LAN, especially when you use it on the
internet, you should switch the internal web server to use SSL 3087 . 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.
Every browser shows a slightly different certificate warning. The necessary steps are similar for
every browser, with a few small differences:
§ Google Chrome 162
§ Mozilla Firefox 163
§ Internet Explorer 163
§ Other 164
You can avoid these browser warnings by using your own trusted SSL certificate 3385 with PRTG.
For this purpose we provide the freeware tool PRTG Certificate Importer 3385 .
Google Chrome
In Google Chrome, click Advanced and then Proceed t o [y ourPRTGserver] (unsafe) every
time you call the PRTG web interface.
SSL Warning in Chrome
162 11/24/2017
Mozilla Firefox
In Mozilla Firefox, click Advanced and then click the Add Except ion... button. A window
opens, leave the check mark for Permanent ly st ore t his except ion and finally click the
Confirm Securit y Except ion button.
SSL Warning in Firefox
%P_ENLARGE%>
You only have to go through this procedure once for every Firefox browser and PRTG core
server.
Internet Explorer
In Int ernet Explorer, click Cont inue t o t his websit e (not recommended) every time you call
the web interface.
11/24/2017 163
SSL Warning in IE
%P_ENLARGE%>
Other
For other, not officially supported browsers, the procedure is similar.
More
§ Using Your Own SSL Cert ificat e 3385
Freeware Network Tools: PRTG Certificate Importer—Installing Trusted SSL Certificates for PRTG
Network Monitor
§ https://www.paessler.com/tools/certificateimporter
Knowledge Base: Why can't I save my PRTG password in Google Chrome?
164 11/24/2017
Part 6: Ajax Web Interface—Basic Procedures | 3 Welcome Page
6.3 Welcome Page

After completing the Smart Set up 52 , you will see PRTG's welcome page by default when you
log in to the web interface. You can set another homepage in your account settings 3050 ,
section Web Int erface.
This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax
interface on a master node. If you use other user accounts, interfaces, or nodes, you
might not see all of the options in the way described here. If you use a cluster installation,
note that failover nodes are read-only by default.
Welc ome to PRTG Network Monitor
The PRTG welcome page shows you various information about your PRTG installation at a
glance, similar to a dashboard. The welcome page keeps you informed about all Sensors 254
and current Alarms 207 :
§ Sensors: Open the Top 10 Lists 254 for sensors.

§ View All Alarms: Open a list of alarms 207 in your PRTG installation.
11/24/2017 165
Welc ome Page: A Good Starting Point for Your Daily Monitoring Ac tiv ities
You can also directly access several pages in the PRTG web interface from the welcome page:
§ View Result s: Open the device tree 170 that shows your monitoring results.
§ Inst all Smart phone App: Open the download page for PRTG's mobile apps 3158 .
§ Download Ent erprise Console: Open the download page for the Enterprise Console 3158 in
PRTG (PRTG on premises only).
§ Get Help and Support : Open the PRTG help and support page from where you can access
the PRTG user manual, the Knowledge Base, and video tutorials. You can also open support
tickets 3162 and contact our customer service 168 from this page.
§ Manage Subscript ion: Open your PRTG in the cloud dashboard and manage your
subscriptions.
Welc ome Page: Your PRTG
Other sections are:
§ Paessler Blog: Shows recent information about PRTG and Paessler. Click the heading of an
article to open it on paessler.com with your browser.
§ Yest erday 's Act ivit y : Shows what your PRTG server did for you on the day before. Point
with your mouse to the mini graph to show the number of sensor scans on a specific day.
See also manual section PRTG St at us—Sy st em St at us 3139 , section Act ivit y Hist ory .
166 11/24/2017
§ License St at us: Shows the number of your remaining maintenance days for PRTG on
premises and the number of sensors you can still add with your current license. Click Get
Maint enance to open the Paessler shop and extend your maintenance for PRTG on
premises installations. Click Get More Sensors to open the Paessler shop and upgrade your
license. See also manual section PRTG St at us—License St at us and Set t ings 3152 .
The number of available sensors that is displayed here does not consider paused
sensors 232 for technical reasons. However, paused sensors do not count against the
maximum number of sensors that your license allows. Add the number of your paused
sensors to the displayed number to know exactly how many sensors are still available on
your installation.
If you use a PRTG on premises license with an unlimited number of sensors, PRTG takes
10,000 sensors as starting point to calculate the number of available sensors, which is
displayed here. Please consider the system requirements 26 for a properly working PRTG
setup and click Recommended Set up for more information.
§ Updat e Available: Shows the version number of your PRTG on premises core server and
the version number of the latest available PRTG version. You will see the label NEW if there is
a newer version available. Click Inst all Updat e to open the PRTG Aut o-Updat e 3146 page.
§ If your PRTG on premises installation is currently not SSL-secured, the welcome page will ask
you to enable SSL encryption for the PRTG website. Click Yes, Swit ch t o SSL to enable SSL
encryption or Don't Tell Me Again to remove this note from the welcome page. See also
manual section Sy st em Administ rat ion—User Int erface 3087 .
§ If you still use the default password of the PRTG System Administrator user (prtgadmin) on a
PRTG on premises installation, the welcome page will ask you to set a secret password if
your PRTG website is publicly accessible. Click Change Default Password Now to define a
new password. See also manual section Sy st em Administ rat ion—User Account s 3117 .
§ In the video sect ion you find informative and helpful videos about monitoring with PRTG.
Click a video to open and play it on paessler.com.
The collected information about your PRTG installation makes the welcome page a good
starting point for your daily monitoring activities. Of course, you can also set up your custom
dashboards in PRTG. The Maps 3026 feature of PRTG enables you to create dashboards exactly
like you want.
11/24/2017 167
1 Customer Service
6.3.1 Customer Service
If you have any questions about license purchase, upgrade, or maintenance extension, you can
directly contact the Paessler Cust omer Service from the Help and Support Cent er in the
PRTG web interface. We will readily assist you with quotes or information about licensing and
maintenance, and guide you through the purchasing process. Our Customer Services team will
also gladly send you the contact information of a knowledeable PRTG partner in your region or
research any technical specifications you might need beforehand.
PRTG transmits your feedback or questions securely to Paessler via the PRTG Cloud. Please
make sure your PRTG server has access to the internet and can reach the URL https://
api.prtgcloud.com:443 for successful transmission.
Customer Serv ic e Contac t Form
168 11/24/2017
1 Customer Service
Ask a Question or Give Us Your Feedback

Provide the following information in this section of the Cont act Paessler Cust omer Service
form:
§ Your Name: Enter your full name for contact information.

§ Your Email Address: Enter an email address under which we can reach you.
§ Your Count ry : Select the country in which you run PRTG so we can provide you contact
information for a partner near you.
§ Your Phone Number: Enter a phone number under which we can reach you.
§ How can we help? Select the scope of your question.
§ Emot ional St at e: If you want to, you can indicate your current feelings about PRTG and your
purchase process.
§ Describe y our quest ion in one sent ence: Provide short information that indicates the topic
of your request.
§ Do y ou have any furt her comment s? Enter your comments here. This can be feedback or
any questions for our customer service.
Click Submit to send your question or feedback to our customer service. Click Cancel to
close the customer service contact form without sending it.
If you have technical questions regarding your already existing PRTG setup, contact our
technical support 3162 .
11/24/2017 169
Part 6: Ajax Web Interface—Basic Procedures | 4 General Layout
6.4 General Layout

This manual section provides a general overview of the structure of the web interface of PRTG.
Central focus is the Devices view, which you can select via the main menu bar. The Devices
view presents the monitoring results at a glance—you will widely use it.
Welcome Page
When you log in to the PRTG web interface, by default you will see the Welcome Page 165 . You
can set another homepage in your account settings 3050 , section Web Int erface.
Click View Result s to open the device tree window.
Tree View Layout

Click View Result s on the welcome screen to display the device tree window. This will be a
good starting point for your everyday work with PRTG.
PRTG Dev ic e Tree
From top to bottom, the device tree screen has several areas that will be covered in further
detail in this section. For a general overview of the device tree consider the table below.
170 12/4/2017
Page area name Descript ion
Global Header This area contains the main menu at the very top, the global status bar,
Area 172 the path to the currently selected object, and a quick search box.
Page Header Bar This area contains the page heading with the name of the current
174 object, several tabs with settings, monitoring data of the current
object, and quick action buttons.
Page Content 175 This area contains information about the current object and all other
objects underneath in the tree hierarchy, the object's status bar, a
quick search box, and the QR code that links to the current URL.
Viewing options These buttons are part of the page content. Here you can adjust how
176 your device tree is displayed.
Page Footer Shows information about the current version of PRTG, the logged in
PRTG user account, and the current time (depending on the timezone
settings 3120 for the currently logged in user).
A timer counts down how much time remains until the next automatic
page refresh. You can pause the refresh timer with the pause icon and
resume with the play icon. If you open another page while the refresh
timer is paused, the timer will resume automatically, starting with the
defined Aut o Refresh Int erval that you can configure in your account
settings 3050 .
Page Footer Icons With these icons you have quick access to the PRTG Aut o-Updat e 3146
page if a new version is available and to the contact support form 3162 .
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 that you are logged in to and
displays whether this is a master or a failover node. Click the bar to
show the Clust er St at us 3150 . 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 in to the master node of your cluster.
Click an object to see its details page. In the page heading of the page header bar 174 you
always see the name of the object that you have currently selected.
When navigat ing PRTG's web int erface, t he following pat hs are available:
§ The main menu provides access to all important aspects of the software.
§ The quick search is often the fastest way to find a specific object (for example, a sensor or a
device).
§ Using the page tabs, you can switch between various sub-pages.
§ Right-clicking objects will open a context menu 234 .
12/4/2017 171
§ When pausing over objects, the tool tip appears, and after further hovering a quick-access
window (Hover Popup 249 ) will open.
§ You can drill down into the object hierarchy of probes, groups, devices, and sensors in the
object tree by merely clicking a sub-object of the currently displayed object (for example, a
sensor on the device page).
These navigation paths offer complete access to the functionality of PRTG, often you will find
multiple means of accessing information or navigating to a certain setting.
In the following, the different areas of the web interface are described.
Global Header Area
Global Header Area
The header area of the web interface provides central, very condensed information about your
installation and offers access to all content and every setting within PRTG. The following table
lists the elements that the global header area is made up of.
172 12/4/2017
Screen Part Descript ion

Number
1 Main Menu Bar For starting to navigate through the web interface, the main
menu is the best starting point. We recommend that you take a
few minutes to familiarize yourself with the menu bar and its
sub-items. For a detailed description see the Main Menu
St ruct ure 250 section.
2 New Alarms, The information boxes show how many new alarms, new log
New Log entries, and updated tickets have occurred. Click the
Entries, New respective box to view the lists of Alarms 207 , Logs 216 , or
Tickets Ticket s 218 .
3 Global Sensor This area shows the accumulated states of all sensors you have
Status Symbols configured for monitoring, divided according to the different
sensor states. Depending on each respective status, you will
see colored boxes with numbers that symbolize the amount of
sensors that are in the respective status. For example, you can
see how many sensors are in Up, Down, or Warning status.
Click a box to view a list of all sensors in the respective status.
For a detailed description, see the Sensor St at es 183 section.
4 Search Bar, Via the icons in the top-right corner you can start a search or
Logout log out.
To search for a monitoring object, enter a name, parts of a
name, an IP address, a DNS name, or a tag in the search box on
the right and confirm with enter. PRTG will perform a string
search in your entire monitoring setup, including groups,
devices, sensors, libraries, maps, reports, tickets, and object
comments.
A page with the items that are related to the search term will
open—even displaying online help articles.
5 Breadcrumbs Below the main menu, PRTG shows a path that retraces the
steps back to the welcome screen (or your defined starting
page). Use it to quickly jump back to where you came from.
Breadcrumbs can also help you to orient yourself if you get
lost. If you click a breadcrumb item, a dropdown menu opens
that shows all objects on the same level. You can either search
for an object, or select one directly. For example, you can use
this to directly access all other sensors or a device, other
devices within a group, and another group on the same probe.
Other probes in your root group are also available.
12/4/2017 173
Page Header Bar

The page header bar, below the global header area, consists of a number of elements shown in
the table below.
Page Header Bar
Screen Part Descript ion

Number
1 Page Heading This line displays the current object's type and name as page
heading. In the screenshot above, it is a group that is called
Root . Here you can define the object's priority by clicking on
one of the five stars (not available for the Root group). For
details, see section Priorit y and Favorit es 229 .
2 Context Buttons On the right side is a row of icons for several actions.
Depending on the currently viewed page within PRTG, you can
pause (and resume) or delete the respective object. You can
also 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, or show the corresponding object
history page 217 . On device lists, there is also a button to open
the QR codes of all devices on this list in a printable layout.
Click the down arrow to open the context menu for the
currently displayed object for further options. For more
information, see Cont ext Menus 234 section.
3 Tabs Via tabs you can navigate to the various sub-pages of an

object, for example, to its monitoring data or settings. For
more information, see sections Review Sensor Dat a 186 and
Change Device and Sensor Set t ings 205 .
Depending on the selected object type, the page header bar shows additional information:
§ All objects underneath the Root group show their dependency 133 .
174 12/4/2017
§ Groups and devices display the time elapsed since the last execution of the auto-discovery
267 on the selected object.
§ Devices show their respective DNS/IP address as defined in the device settings 385 and the
time elapsed since the last execution of the sensor recommendation 201 on this device.
§ Sensors show additional monitoring statistics.
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.
Page Content
12/4/2017 175
1 Sensor Status This element is visible when viewing a probe, a group

Bar (including Root ), or a device. It is not available when the
sensor details page is open. The sensor status bar shows the
accumulated states of all sensors for the current object,
divided into different sensor states. They show the number of
sensors in the respective status.
For example, you can see how many sensors are in Up, Down,
or Warning state. For a detailed description of sensor states,
see the Sensor St at es 183 section. You can hide sensors that
are in a certain state by removing the check mark in front of
the respective status. To show them again, re-add the check
mark.
2 Viewing options This element is only visible when viewing a probe or a group. It
is not available when you view device or sensor details. For a
detailed description, see Switch Device Tree View 176 below.
3 Tree Search In the white search box to the right of the tree view selection,
enter a key word to search the device tree for matching items.
The tree will 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 matching this name.
4 Add Button Use this button to add new objects to your monitoring setup.
For a detailed description, see Add Button 181 below.
5 Object Status, This element displays the current status of the selected object,
Scanning the time interval in which PRTG scans the current object, the ID
Interval, Object of the current object, and the QR code for the current page. If
ID, QR Code you use a PRTG mobile app 3222 , you can scan the code to view
the current object directly on your mobile device. Click the QR
code to enlarge it for scanning.
Switch Device Tree View

Wherever a probe or group is displayed, you can choose between a number of viewing
options.
Dev ic e Tree Viewing

Options
176 12/4/2017
Switch Device Tree View—Classic Device Tree

Via the sizes in the page header bar, you can adjust how much information will be included
next to each object. Using the various buttons, you can switch from a very condensed view
(SM) to an extra spacious view (XL).
In the classic device tree view you can collapse devices, groups, and probes. Click the minus
box left of the object name. The sensor states will then be summarized. The states of all
sensors on this object will be displayed. Right next to the status, the amount of sensors in
this status will be displayed, with the exception of the states Down, Down (Part ial), and Down
(Acknowledged). In the default settings, the sensors will be grouped together if there are
more than ten sensors with the same status, otherwise they will be displayed individually.
Collapsed Dev ic e With Summarized Ups and Unusuals and Indiv idual Downs
Switch Device Tree View—Extended Views

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

The tree map view displays all devices of your entire installation as tiles sorted into a square
and arranged according to the groups they belong to. Each device dynamically changes color
to reflect the overall status of the sensors on the device. You can also adjust the square size:
either depending on a device's priority, or depending on the number of sensors on a device, or
depending on both. To do this, click the Size by : Sensors and/or Priorit y setting in the page
header bar (see the mark in the screenshot below).
12/4/2017 177
PRTG Tree Map View
Sunburst View (5)

The sunburst view displays your entire installation as a 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.
The sunburst is interactive:
§ You can click elements to open the details view of your monitoring objects.
§ You can zoom in and out by using the plus + and minus – buttons or your mouse wheel.
§ You can change the position of the sunburst on the overview tab with drag & drop.
178 12/4/2017
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 183 ) 183 . A higher status is
regarded as more important and takes precedence (prioritized higher). For example, if a
device currently has sensors in the states Up (green), Paused (blue), and Warning (yellow),
according to the device prioritization, this tile would then be yellow, indicating that at least
one sensor on this device is in Warning status. If a single sensor changes to Down status,
the corresponding device tile will turn red. Correspondingly, the PRTG states (for both views)
are shown here in order of their prioritization:
12/4/2017 179
Flag Flag Color Object St at us Meaning
Red Down At least one sensor 'belonging to' this object

shows a red Down status. Point to an object's
name to view the total number of alarms
concerning this object.
Bright-Red Down At least one sensor belonging to this object is

(Acknowledged) Down and the status has been acknowledged
by a PRTG user via the Acknowledge Alarm
function. All of this devices Down states must
have been acknowledged—if at least one sensor
is not acknowledged, this object will be
displayed as Down.
Yellow Warning At least one sensor belonging to 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 belonging to 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 belonging to this object are in a

green Up status. There is no sensor in a Down,
Down (Acknowledged), Warning, Paused, or
Unusual status concerning this object.
Blue Paused All sensors belonging to this object show a

blue Paused status. There is no sensor in a
Down, Down (Acknowledged), Warning,
Unusual, or Up status concerning this object.
Black (Grey) Unknown All sensors belonging to this object have an

Unknown status. There is no sensor in a Down,
Down (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 amount of
sensors running on a device or within a group, or by the sensors' priority (see Priorit y and
Favorit es 229 ), or both. Use the check boxes in the page header bar (see below) to change
the view immediately, then use the setting that suits you best.
Sorting Chec kboxes
180 12/4/2017
Add Button
Hover over to add new objects to your monitoring setup. An assistant will appear, leading
you through the necessary steps.
The content of the PRTG context menu varies, depending on the menu item or tab you
have selected.
Add Button Menu
See the following for more information:
§ Add Remote Probe 3358
§ Add a Group 286
§ Auto-Discovery—Creating an Auto-Discovery Group 268
§ Add a Device 295
§ Add a Sensor 309
§ Add Mobile Android Probe
Default Objects in the Device Tree

By default, a Probe Device is created in the device tree on the local probe 3392 or cloud probe
3389 . It represents the probe system running with your PRTG installation. PRTG automatically
monitors the system health of the core server and 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:
§ Core Health Sensor 628
§ Probe Health Sensor 1484
§ System Health Sensor 2456
§ Some further device specific sensors for disk usage and bandwidth
In a cluster installation, PRTG also creates a Clust er Probe Device with a Clust er Healt h
Sensor 615 that monitors the cluster's system health.
We recommend that you keep these sensors, but they all are removable.
12/4/2017 181
Priority and Favorites

You can tag a device or sensor as 'favorite' by clicking the flag displayed to the right of it (see
the screenshot below). To untag devices, proceed the same way.
One-Clic k Fav orites in the Dev ic e Tree
The favorite flag for sensors is available for the LG or XL viewing options.
A quick and easy way of adjusting priority is located in the page header bar 174 right next to
the object name (see screen number 1 in that subsection). Click the a stars to adjust priority (5
is highest 1 lowest).
One-Clic k Fav orite and Priority in the Page

Header Bar
A blue flag indicates that the respective object is a favorite already. After clicking the blue flag,
the object will no longer be a favorite. A gray flag indicates that it is not yet a favorite. See the
Priorit y and Favorit es 229 chapter for further information.
For more details about page contents, see the following sections:
§ Review Monit oring Dat a 186
§ Hist oric Dat a Report s 192
§ Object Set t ings 205
§ Geo Maps 2961
182 12/4/2017
Part 6: Ajax Web Interface—Basic Procedures | 5 Sensor States
6.5 Sensor States

In the PRTG device tree you usually create several sensors for each device 385 . 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. In the below table, you will 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 170 , or on geo maps 2961 ) : 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 reaches a Down status, then the
overall status of this device will be Down as well (for example, displayed red in the Tree Map
View 176 ), because this status is higher up in the hierarchy.
Down and Down (Part ial) states are equal in the status hierarchy.
Sen Colo St at us Meaning

sor r Name
Red Down 1. PRTG is unable to reach the device, or the sensor has changed
to the error state. See the Sensor Warning and Down Behavior
184 below for more information.
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 2915 , or an error status due to a
sensor Lookup 3345 .
In this case, the sensor continues to record data in all
sensor channels although the sensor shows an error.
Gree Down In a cluster, at least one node reports this sensor as Down, while
n/ (Part ial) at least one other node reports the same sensor as Up.
Red
This status is not available for sensors on remote probes in a
failover cluster 122 .
Brigh Down The sensor is Down and the status was acknowledged by a PRTG
t-Red (Acknowl user, applying the Acknowledge Alarm function. This can be
edged) helpful to mark that an alarm has already been brought to
attention. For acknowledged alarms no further notifications 2966 are
sent. To set this sensor status, right-click the sensor in Down
status and from the context menu 234 , select Acknowledge
Alarm.... Then enter a comment and click OK.
12/8/2017 183
Sen Colo St at us Meaning

sor r Name
Yello Warning The sensor gives an error reading, but PRTG will try again. The
w sensor may soon change to a down status. See the Sensor
Warning and Down Behavior 184 below for more information.
Another reason for this status can be a warning limit set in a
sensor's Sensor Channels Set t ings 2915 .
Oran Unusual The sensor reports unusual values for this weekday and time of
ge day. The unusual detection is based on the historic average data
and can be configured or disabled in the system administration 3097 .
You can also disable unusual detection for certain groups only
(see Group Set t ings 382 ).
Gree Up The last scan was okay and the sensor currently receives data.
n
Blue Paused The sensor is currently paused (for a certain timespan, indefinitely,
or triggered by a dependency 133 ).
Black Unknown The sensor has not received any data yet or there is an error in
(Gray) (network) communication, likely on the probe system. If sensors
show this status persistently, a PRTG restart may be necessary.
For extended troubleshooting, see this Knowledge Base
article: What to check if sensors are black (gray)?
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 re-contact the device 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 will change to Warning status. PRTG
repeats the request and attempts to re-scan the device immediately.
2. If the second request also fails, the sensor changes to Down status by default until the
device is reachable again. You can change this behavior in the Scanning Int erval 328 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 network issues.
The behavior described above does not apply to Warning or Down states that are
activated due to a warning or error limit set in the Sensor Channels Set t ings 2915 or to
channels using lookups 3345 .
184 12/8/2017
More
Video Tutorial: The PRTG Sensor States
§ https://www.paessler.com/support/videos/prtg-basics/sensor-states
Knowledge Base: What to check if sensors are black (gray)?
12/8/2017 185
Part 6: Ajax Web Interface—Basic Procedures | 6 Review Monitoring Data
6.6 Review Monitoring Data

Probe, group, device, and sensor pages have tabs that you can use to navigate between the
different options. For example, you can view 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 its sensors. The
pages share a common structure, but some elements differ, depending on the type of object.
§ Probes and Groups: the tab shows a tree-like view with devices and sensors, a Geo Map, as
well as summary graphs for different timespans of the current probe or group.
§ Devices: the tab shows device details, a Geo Map, and summary graphs for different
timespans, colored gauges for high priority sensors, as well as a table list of all sensors on
this device, and a table list 225 with Recommended Sensors 201 .
§ Sensors: the tab shows sensor details, current status, colored gauges, sensor graphs for
different timespans, a table with all sensor channels, as well as similar sensors 197 , which
show correlations in your network.
You can turn off the sensor recommendation and disable the table list in Sy st em
Administ rat ion—Monit oring 3100 .
Assign 4 star (****) or 5 star (*****) priorities to sensors to display their gauges on your
device overview pages. 5 star sensors are represented by larger gauges (upper row on
the screenshot) rather than 4 star sensors (lower row on the screenshot).
Gauges represent sensor values on the Overview tab of devices and channel values on
Overview tabs of sensors. They visualize the current value of a sensor or a channel, so you
can use them as a quick status indicator.
§ Red and yellow sections of gauges correspond to the error and warning limits of the sensor
channel settings 2915 .
§ Device overview tabs only show gauges of high priority sensors, sensors with priorities of 3
stars (***) or less are omitted here.
§ Sensor overview tabs show gauges of all sensor channels (except the Downt ime channel),
regardless of priority. The primary channel is displayed with the large gauge.
§ Sensor channels that display binary values such as on/off or successful/failing due to their
lookup 3345 configuration are visualized as switches not gauges. Switches only show red or
green for their respective two states.
For the gauge to remain legible, we recommend that you stay below 120 lookup 3345 values
for primary channels, which belong to sensors with a 5 star priority. For sensors with a
priority of 4 stars, the recommended limit is around 40 lookup values.
186 12/8/2017
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 413 only. Toplist graphs are
displayed right on the sensor overview page.
For more information, see the section Toplist s 2940 .
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 timespans and in more
or less detail. The time that graph legends and data tables show depends on the time zone
settings 3120 for the currently logged in user.
The days mentioned here is the default setting. You can change the shown days of the
different graphs under Sy st em Administ rat ion—User Int erface 3092 .
Graphs label minimum and maximum values of a sensor's primary channel and minimum and
maximum values of the Response Time Index of other objects. A maximum value of 100%
will not be labeled.
12/8/2017 187
2 Day s Tab of a Dev ic e with Ov erv iew Graph and Sensor Mini Graphs
Live Data and Data By x Days—Probes, 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. For performance reasons, PRTG never displays more than 50 mini graphs. Hover over a
mini graph to display the graph legend.
Summary graphs show 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 show overall (or global) trends in your network. If these values
increase over 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:
§ 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 your network issues. It cannot be
hidden.
§ Response Time Index: Indicates the request times in your network.
§ CPU Load Index: Indicates the CPU usage in your network.
188 12/8/2017
§ Traffic Index: Indicates the bandwidth usage in your network.
For more details about the index graphs, see the Knowledge Base: How does PRTG
compute CPU Index, Traffic Index and Response Time Index?
You can hide all channels individually except the "Alarms" channel. To do this, remove the
check mark symbol in front of a channel name besides the graph, and the corresponding
channel's line will disappear. You can also Show all or Hide all channels by clicking on the
buttons below 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 Days—Sensors

For sensors, each tab shows a graph and data table for the selected sensor. When viewing the
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.
Multi-node graphs are never displayed as filled graphs, but are displayed with 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 below 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.
12/8/2017 189
Live Data and Data By x Days—Interactive Graphs

The graphs on a sensor's historic data tabs and in "zoomed graphs in new windows" (see
below) belonging to other monitoring objects are all interactive. You can zoom in and scroll
along the time axis with the corresponding buttons.
Graph Buttons
The following actions are available for graphs:
§ << scrolls one graph window left and >> one graph window right. The scrolled time depends
on the graph you select, for example, 2 days on a 2 days graph.
§ < scrolls left and > right on the time axis. The scrolled time depends on the graph you select.
§ + zooms into and - out of the graph. The displayed time depends on the graph selected. For
example, you can zoom in 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 each graph, three small icons are located :
§ 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.
§ Zoom graph in new window: Opens a larger version of the graph in a new browser
window.
For each graph, you can also choose which specific channels (only on sensor pages) or
indexes you want to see via the corresponding check boxes or the Show all and Hide all
buttons.
Warning or error limits 2916 are only shown in graphs (highlighted in yellow or red) if you
select exactly one channel with a limit.
Historic Data
The Hist oric Dat a tab is available for sensors only.
For more information, section Hist oric Dat a Report s 192 .
Sensor 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.
190 12/8/2017
Sensor lists are accessible via the main menu bar. Click the Sensors entry to show a table list
of all sensors. In the table list 225 displayed here, you can re-arrange the items by clicking the
column's header items (see section Working wit h Table List s 225 ). Hover over it to show
other menu options.
For detailed information about the available options, see the Main Menu St ruct ure 254
(Sensors) section.
Alarms
The Alarms tab is not available for sensors, but for probes, groups, and devices only.
For more information, see the Alarms 207 section.
System Information
The Sy st em Informat ion tab is available for devices only.
For more information, see section Sy st em Informat ion 210 .
Log
The Logs tab shows past activities and events regarding the currently selected object.
For more information, see the Logs 216 section.
Related Topics
§ Object Set t ings 205
More
Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time Index?
12/8/2017 191
Part 6: Ajax Web Interface—Basic Procedures | 7 Historic Data Reports
6.7 Historic Data Reports

For quick reviews of a sensor's monitoring data, use the historic data reports as an alternative
to the comprehensive Report s 3000 function. You can run and view a report of the historic data
for each single sensor, on demand. Additionally, you can export this sensor data as XML or
CSV files to your computer for further processing with third-party applications.
There are two ways to open PRTG historic data reports: either you click 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
254 .
Historic Data (Sensor Tab)

change settings.
The Hist oric Dat a tab is available for sensors only (not for probes, groups, or devices). When
you open the historic data tab of a sensor, there is no sensor selection available. If you want
to select a different sensor for the report, select Sensors | View Hist oric Dat a from the main
menu in the PRTG web interface.
Historic Data Tab of Ping Sensor
192 12/11/2017
Historic Monitoring Data (Sensors Main Menu)

When you open historic data reports via Sensors | View Hist oric Dat a in the main menu, PRTG
will ask you to choose the sensor you want to create a report for with the Object Select or
228 .
Historic Monitoring Data Settings
SETTINGS
Sensor This field is only visible if you open the historic data function via
the main menu. Select the sensor you want to create the report
for: click the reading-glass symbol to open the object selector. For
more information, see section Object Select or 228 .
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.
You cannot start the report generation if monitoring data has
been purged 3113 after the defined start date. Please set the
start for the report to a date where data is available.
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 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 configure averaging. Select
an interval for which PRTG will calculate 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 shorter interval results in a more detailed report for
this sensor.
The best settings for you may vary, depending on the scanning
interval of the sensor, the selected date period, and the intended
use for the report. It might be useful to try different settings and
compare what the results look like.
12/11/2017 193
SETTINGS
See the section Aut omat ic Averaging 196 below.
Channels in Graph Select the channels that you want to include in the graph of the
report. You can select or deselect individual channels with the
respective check boxes, and select or deselect all channels with
the buttons Show all or Hide all. PRTG will only show the data of
selected channels in the graph of the report.
The report table will always show the data of all channels.
Cluster Node This field is only visible if the sensor is running on a cluster probe.
Select the cluster node's data that PRTG will include in 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, your 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, your
browser shows a download dialog when you use this option.
INCLU DE PER CENTILES
Percentile Results Define if you want to include an additional percentile calculation 3357
of your data in the report. Choose between:

§ Do not show percent iles: PRTG does not use a percentile
formula to calculate your monitoring results. It will show only the
standard values.
§ Show percent iles: PRTG adds a column to the result data tables
that shows percentiles for every sensor channel.
194 12/11/2017
INCLU DE PER CENTILES
Percentiles are not available for all report templates. If a

template does not support percentiles, they will simply not
show up in the report, even when you enable this setting.
Likewise, percentiles are not available in a cluster setup if you
choose the option All Nodes in the Clust er Node setting in the
sensor section above.
Percentile Type This setting is only visible if you select Show percent iles above.
Enter the percentile type you want PRTG to use for the calculation.
If you choose, for example, to calculate the 95th percentile, enter
"95" here and 5 % of peak values will be discarded.
Please enter an integer value.
Percentile Average This setting is only visible if you select Show percent iles above.
Interval Enter a value to define the averaging interval on which PRTG bases
the percentile calculation. The default value is 300 seconds (5
minutes). This means that PRTG takes 5 minute averages as basic
values for the percentile calculation. Please enter an integer value.
Percentile Mode This setting is only visible if you select Show percent iles above.
Choose the mode for percentile calculation:
§ Discret e: PRTG takes discrete values to calculate percentile
results.
§ Cont inuous: PRTG interpolates between discrete values and
bases the calculation on interpolated values.
Click St art to generate a historic data report.
You cannot start the report generation if monitoring data has been purged 3113 after the
defined start date. Please set the start for the report to a date where data is available.
Any sensor graph in your report will only show channels that are enabled via the Show in
Graphs option in the Sensor Channels Set t ings 2915 .
Reports cannot show uptime or downtime data for the Sensor Fact ory Sensor 1570 .
Reports show statistics for uptime (Up and Down in percent) and requests (Good and
Failed in percent). Values between 5% and 95%, as well as 100% and 0%, are rounded to
whole numbers without decimal places. Other values are shown with 3 decimal places.
Data reporting is limited to 5 requests per minute.
12/11/2017 195
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
Reports for time spans of more than 500 days are not possible. If you enter a longer time
span, it will automatically be shortened to 365 days.
Related Topics
§ Report s 3000
More
Knowledge Base: Why is there missing data in historical data reports?
196 12/11/2017
Part 6: Ajax Web Interface—Basic Procedures | 8 Similar Sensors
6.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 that shows similar behavior in
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 that
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 3099 . You can also enable or disable the similarity analysis for specific probes,
groups, and devices and specify inheritance 129 in the corresponding object settings 205 ,
section Aut omat ic Monit oring Analy sis.
There are two options to view similar sensors:
§ The overview page of sensors contains a similar sensors section. PRTG lists channels there
that 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 254 .
Similar Sensors (Sensor Overview Tab)

change settings.
On the overview tab of a sensor, PRTG lists channels that show similarities to channels of the
currently selected sensor. The table is empty if PRTG detects no similarities regarding the
selected sensor.
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.
11/24/2017 197
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 Shows a channel of another sensor similar to a channel of the currently

Channel selected sensor (the one in the "Channel" column in the same row).
PRTG does not show the similar sensors section when the analysis is off or when you
have exceeded 1,000 sensors and selected the automatic analysis depth option 3099 . You
will see a notice in this case.
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 225 .
198 11/24/2017
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 the column headers. The similar sensors overview page
provides the following information:
SIMILAR SENSOR S OVER VIEW
Original Shows channels that other channels are compared to. Click the column header
Channel to sort the list according to the order in the device tree in ascending or
descending order.
Similarity Shows a measurement of similarity between two channels in percent. Click the
column header to sort the list according to the similarities in ascending or
descending order.
11/24/2017 199
SIMILAR SENSOR S OVER VIEW
Similar Shows a channel compared to the original channel. Click the column header to
Channel sort the list according to the order in 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.
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.
200 11/24/2017
Part 6: Ajax Web Interface—Basic Procedures | 9 Recommended Sensors
6.9 Recommended Sensors

The Recommended Sensors function is one of the options that PRTG supports you in setting
up a comprehensive monitoring. PRTG can explore any device and check which sensors you
have already created. If it finds useful sensors that can complete your monitoring 186 and are
not yet created, you will find a list of recommended sensors for your specific device. By adding
these sensors, you will not miss important monitoring data anymore!
You cannot use this feature on the Cloud Probe of a PRTG in the cloud instance. You can
use this feature on remote probes 3359 .
Rec ommended Sensors on Dev ic e Ov erv iew Tab
Get Sensor Recommendations

You want to know which sensors can complete the monitoring of your devices? By default,
PRTG recommends sensors for any device that you add to PRTG and shows the suggested
sensor types for it on the Overview tab of the device, as long as your installation contains
less than 5,000 sensors in total. All you have to do is click the Add These Sensors button to
enhance your monitoring experience.
If you want to manually start the detection engine for sensor recommendations on any desired
device, follow the steps below.
You can see the time passed since the last execution of the sensor recommendation in the
page header bar 174 on the Overview tab of this device.
11/24/2017 201
Step 1: Choose the Device

Open the Overview 186 tab of the device that you want to analyze.
change settings.
Step 2: Recommend Now

To start the analysis of your device, click the Recommend Now button or choose the option
Recommend Now in the context menu 241 .
If you do not see the Recommend Now option, make sure that the sensor
recommendation is enabled in the Sy st em Administ rat ion—Monit oring 3100 settings.
Probe devices do not offer this option.
Depending on the complexity of your device, it can take some time until you see the results of
the analysis. Stay tuned!
Rec ommended Sensors Inv estigation
PRTG runs the device analysis in the background with low priority to prevent potential
performance issues. Consequently, the recommended sensors analysis can take more time
than expected if PRTG needs resources to ensure gapless monitoring of your network in the
first place. By default, the sensor recommendation engine starts automatically when you add a
new device, when you do not have more than 5,000 sensors, or when the last analysis was
executed more than 30 days ago. You can change these settings in the Sy st em
Administ rat ion—Monit oring 3100 .
To recommend SNMP sensors 414 for a device, the detection engine uses the SNMP version
that you defined in the Credent ials for SNMP Devices 394 section of the device settings.
Step 3: Get the Results

After analyzing your device, PRTG suggests a list of sensors that are useful for a more
comprehensive monitoring.
202 11/24/2017
List of Rec ommended Sensors
The list of recommended sensors provides the following information:
R ECOMMENDED SENSOR S
Priority Shows which priority 229 the suggested sensors will have when
you add them. The recommended sensors table is sorted by
priority, beginning with top priority (5***** stars) in the first row.
You can manually change the priority of a sensor after adding
it.
Sensors Shows the suggested sensors and the number of sensors from
one type PRTG recommends for this device (for example, you might
want to add a sensor from the type SNMP Traffic 2265 multiple times
because of several network interfaces).
Total Sensors Shows the total number of suggested sensors per table row.
These sensors have the same priority.
Links Displays an Add These Sensors button for every table row. Click
to automatically add the sensors listed in this table row to the
device.
The detection engine checks if a certain sensor type currently exists on your device and
recommends that you add this sensor if it does not exist. If this sensor type already
existed previously on the device but you have deleted it, PRTG will suggest this sensor type
again. Please ignore the suggestion of this sensor type or follow Step 4 203 .
Step 4: Add Recommended Sensors

Click the Add These Sensors button in a table row to add all sensors in this row to the
analyzed device.
If you want to add all suggested sensors regardless of their priority, click every Add
These Sensors button in the recommended sensors table. If you want to add only some
of the sensors of a certain priority and not all of them, please click Add These Sensors first
and then delete 246 or pause 232 the ones you do not need.
11/24/2017 203
Settings for the Recommended Sensors Analysis

You can also adjust the recommended sensors detection. Go to Sy st em Administ rat ion—
Monit oring 3100 to select whether
§ you want PRTG to decide on the sensor recommendation (default), or

§ you want the recommended sensors to always be displayed, or
§ you want to turn off the recommended sensors function.
If you use the default setting, PRTG uses an intelligent assistant that takes care of your specific
network monitoring situation. PRTG automatically counts the number of sensors you have and
decides whether to start the recommended sensors detection or not. It will not start if your
PRTG installation comprises 5,000 sensors or more to prevent performance issues. We
recommend that you set this default option so you do not miss any important monitoring data
about your network, without risking running into performance issues.
Disable the recommended sensors feature if you encounter performance issues or if you
do not want to display this information on device overview tabs.
More
Do you want to get more help with choosing and creating useful sensors? This is possible in
PRTG with the Aut o-Discovery 267 ! You can activate it when adding a new device 297 to PRTG,
manually at any time 268 , or choose if you want PRTG to analyze a whole section 270 of your
network, for example, devices covered by a certain IP range.
The auto-discovery has a higher priority than the recommended sensors detection. If both
are active, PRTG will queue the sensor recommendation and execute the auto-discovery
first.
204 11/24/2017
Part 6: Ajax Web Interface—Basic Procedures | 10 Object Settings
6.10 Object Settings

change settings.
Device Tree Management

The Management tab is available when viewing probes or groups. After clicking this tab you
can move devices and sensors directly in the tree view. If moving is not possible, the web
interface will automatically start a clone process.
For more information, see the Manage Device Tree 312 section.
General Settings
In the Set t ings tab you can define all settings for the current object. The available options
vary, depending on the kind of object you're changing. See the following sections for
information about the respective object types:
§ Root Group Set t ings 314
§ Probe Set t ings 334
§ Group Set t ings 358
§ Device Set t ings 385
§ Sensor Set t ings 411
The available setting options are different for each sensor, but always the same for probes,
groups, and devices. Sensor Channels Set t ings 2915 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, see Sensor Not ificat ions Set t ings 2924 section.
Comments
On the Comment s tab you can enter free text for each object. You can use this function for
documentation purposes or to leave information for other users.
Click Save to save your settings. If you change tabs or use the main menu, all changes to the
settings will be lost!
11/24/2017 205
Part 6: Ajax Web Interface—Basic Procedures | 10 Object Settings
History
In the Hist ory tab all changes in the settings of an object are logged with a timestamp, the
name of the PRTG user who made the change, and a message. The history log retains the last
100 entries.
On some pages, you can access the history of subordinate objects via the corresponding
context button in the page header bar 174 . This includes Sy st em Administ rat ion 3084 and
the overview pages of User Account s 3116 , User Groups 3123 , Report s 3000 , Libraries 2984 , and
Maps 3026 . See the Logs (Main Menu) 217 for details.
Related Topics
§ General Lay out 170
§ Toplist s 2940
206 11/24/2017
Part 6: Ajax Web Interface—Basic Procedures | 11 Alarms
6.11 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 for keeping track of all irregularities in
your network.
In the table list 225 , you can re-sort the items by clicking the column's header items.
Alarms List
There are two ways to display the alarms list: either click the Alarms tab on the detail page of
a probe, group, or device (not available for sensors), or click Alarms in the main menu bar 250 .
By default, table lists with alarms are ordered by priority 229 .
Alarms (Object Tab)

change settings.
Tabs Bar on Group and Probe Lev el
On an object's detail view, click 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 status for the current object only. This is a subset of the entries
available via the Alarms | All option in the main menu bar 257 . The tab is not available on a
sensor's detail page.
11/24/2017 207
Alarms (Main Menu)

Click Alarms in the main menu bar 257 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. Click Alarms in the main menu bar 250 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 that are currently in Down, Down
(Part ial), Down (Acknowledged), Warning, or Unusual status 183 .
Show as Gauges Open a page with the gauges of all sensors that 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 that are currently in Down, Down
(Part ial), or Down (Acknowledged) status.
Warnings Only Open a list of all sensors that are currently in Warning status.
Unusuals Only Open a list of all sensors that are currently in Unusual status.
Acknowledge Alarm
An acknowledged alarm shows up in the alarms list as "acknowledged" (see Sensor St at es 183 )
and will not trigger 2924 any more notifications 2966 .
If the alarm condition clears, the sensor usually returns to an Up status immediately with
the next sensor scan.
To acknowledge an alarm, right-click a sensor entry 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:
208 11/24/2017
ACKNOWLEDGE ALAR M U NTIL
Selected Objects Shows the sensor(s) that you want to acknowledge the alarm for.
You can acknowledge alarms for more than one sensor using multi-
edit 2949 .
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.
If the alarm condition still persists after the specified date, the
sensor will show a Down status again.
Only users 3116 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 3117 , section
Account Cont rol.
More
Knowledge Base: Which audible notifications are available in PRTG? Can I change the default
sound?
11/24/2017 209
Part 6: Ajax Web Interface—Basic Procedures | 12 System Information
6.12 System Information

The Sy st em Informat ion is a great feature to see at a glance what is going on on the systems
you have in your network. You get
§ basic system data of your device like bios serial number or MAC and IP addresses,
§ all connected hardware types as well as their states and properties,
§ the software you have installed, including version and vendor information,
§ the users connected to your system and their domain,
§ a list of all active or stopped Windows system services plus their properties, and
§ a list of all processes running on your system, including their ID and start time.
Together with your everyday monitoring you will receive a really profound knowledge about
your IT infrastructure from only one single source—your PRTG Network Monitor!
Sy stem Information Tab on a Windows Dev ic e
Sy st em Informat ion is available for all devices that you add to PRTG and run with an officially
supported Windows version 26 . You can also retrieve system information from Linux, Unix, or
other devices that have Simple Network Management Protocol (SNMP) enabled.
Some of the above listed system information may not be available depending on the
request method you use (Windows Management Instrumentation (WMI) or Simple Network
Management Protocol (SNMP)). To get all information available, activate both request methods
(Windows Management Instrumentation (WMI) and Simple Network Management Protocol
(SNMP)), as far as possible.
210 12/11/2017
Find and Use System Information

Go to the overview page of a device and click the Sy st em Informat ion tab to see available
information.
Basically, it is not necessary to configure anything special to use the Sy st em Informat ion
feature, if you already monitor a network device with WMI 416 and SNMP sensors 414 . The PRTG
Sy st em Informat ion uses the same technologies 3226 . So, you already meet the main
prerequisites for retrieving system information for your device. The data will be displayed in the
corresponding Sy st em Informat ion table automatically and you can analyze your system
directly 212 . If you are not using Windows Management Instrumentation (WMI) or Simple
Network Management Protocol (SNMP) sensors yet, see section Prerequisit es 211 below that
shows in detail what you need to get system information.
Sy st em Informat ion is enabled by default. To retrieve the data, PRTG will automatically
use Credent ials for Windows Sy st ems and Credent ials for SNMP Devices as defined in
the device settings 385 or as inherited 125 from a parent object like the Root group. Please
consider this when you monitor devices outside the local network, especially when using
SNMP v1 or v2c that do not provide encryption.
System Information is not supported by the Enterprise Console 3168 . Please use the PRTG
web interface 156 to access the system information of a device.
System Information for your devices only has informational purposes. We cannot
guarantee that the data displayed in PRTG Network Monitor fully corresponds to the
device parameters.
Prerequisites
Fulfill the following requirements to show all available system information data for a device. It is
not necessary to meet every single prerequisite but then some tables will not show all data or
may even remain empty. For example, if you do not configure SNMP on the target device, you
will get less information for the Sy st em table.
§ Valid credent ials in the device settings 385 (or inherited 125 ): Enter correct settings for the
target device in the sections Credent ials for Windows Sy st ems and Credent ials for SNMP
Devices.
§ Remot e Regist ry Windows service: Enable the Remote Registry Windows service on the
target computer, for example, via services.msc, and set the start type to aut omat ic.
§ Remot e Procedure Call (RPC) Windows service: Enable the RPC Windows service on the
target computer, for example, via services.msc, and set the start type to aut omat ic.
§ WMI on probe and target computer: Configure Windows Management Instrumentation (WMI)
on the target computer and on the computer that runs the PRTG probe with the device.
Especially configure the firewall of the target computer to allow WMI. For more details, see
manual section Monit oring via WMI 3244 and the Knowledge Base article General
Int roduct ion t o WMI and PRTG.
12/11/2017 211
§ SNMP on target computer: Configure Simple Network Management Protocol (SNMP) on the
target computer. For more details, see manual section Monit oring via SNMP 3227 and the
Knowledge Base article General Int roduct ion t o SNMP and PRTG.
Usually you will see data coming in after a few minutes, depending on the protocols you use
(WMI takes longer than SNMP). A Sy st em Informat ion table will show an error message, if
PRTG cannot get data, for example, because of misconfiguration.
For details about error messages, see this Knowledge Base article: How can PRTG get data
for System Information tables?
No Data Av ailable: Chec k the Prec onditions
System Information (Device Tab)

change settings.
Tabs Bar on Dev ic e Lev el
On the details page of a device, click the Sy st em Informat ion tab.
If you do not see a Sy st em Informat ion tab for your device, you need to enable Sy st em
Informat ion in section Advanced Net work Monit oring 408 in the device settings (or
inherit it from an object higher in the hierarchy 125 ). Sy st em Informat ion is enabled by default.
If Sy st em informat ion is disabled, the Sy st em Informat ion tab will not be available for the
device.
Analyze Your Systems

On the Sy st em Informat ion page, PRTG displays a table for each system information category
about this device: Sy st em, Hardware, Soft ware, Users, Services, and Processes.
212 12/11/2017
CATEGOR SYSTEM INFOR MATION R EQU EST

Y METHOD
Sy st em Shows information about the device like BIOS serial number, IP WMI
addresses, MAC addresses, and Windows version.
SNMP
Hardware Shows hardware that is connected to the device like disk WMI
drives, CD/DVD, video controllers, processors, network
adapters, sound devices, printers, and memory. You can see SNMP
Class and Capt ion of a hardware device. In the Propert ies
column you get more information about the hardware (for
example, the description).
Soft ware Shows installed software and the Version number on the WMI
device. In the Propert ies column you get more information
about the software (for example, the size). SNMP
PRTG uses Uninstall registry keys to retrieve the list of
installed software, so the displayed software might differ
from the software that the target Windows system shows
under Programs and Features.
The Sy st em Informat ion scan for software on the probe
device uses the credentials the probe 118 runs with and
ignores credentials from the Set t ings tab.
Users Shows the user accounts connected to the device and their WMI
Domain.
SNMP
Services Shows the available Windows services on the device. This table WMI
shows the St at e of the service (running, stopped) and the start
type (St art mode automatic, manual, or disabled). In the SNMP
Propert ies column you can get more information about a
service (for example, the description).
Processes Shows the processes that are currently running on the device WMI
as listed on the Processes tab of the Windows Task Manager.
You can also see the St art Time (only WMI) and Process ID of a SNMP
process.
Click the refresh button in the upper-right corner of a table to retrieve current information for
this Sy st em Informat ion category. The timestamp shows the time passed since the last table
refresh.
Table Refresh
12/11/2017 213
PRTG automatically retrieves data for all tables, including Sy st em, Hardware, and Soft ware,
once every 24 hours. The tables Users, Services, and Processes refresh each time you open
the Sy st em Informat ion tab. PRTG also updates all system information tables when the PRTG
server is restarted, for example, after an update.
PRTG can perform up to 24 system information scans simultaneously so it may take some
time until the tables are filled after a server restart.
You can sort each table by clicking the column headers. See Working wit h Table List s 225
section for more information.
PRTG user accounts with read-only access rights 148 to a device can view system
information on this device but they cannot refresh tables manually.
Data Storage
PRTG stores data files with the retrieved system information in the corresponding \Sy st em
Informat ion Dat abase subfolder of the PRTG data folder 3383 .
If you delete a device in PRTG, the system information files of this device will remain in
these folders unless you delete them manually.
PRTG uses the following subfolders for Sy st em Informat ion data.
SYSTEM INFOR MATION DATABASE: DATA FOLDER S
hardware Data for the Hardware table
loggedonusers Data for the Users table
processes Data for the Processes table
services Data for the Services table
software Data for the Soft ware table
system Data for the Sy st em table
More
Knowledge Base: How can PRTG get data for System Information tables?
Knowledge Base: General Introduction to WMI and PRTG
214 12/11/2017
Knowledge Base: General Introduction to SNMP and PRTG

12/11/2017 215
Part 6: Ajax Web Interface—Basic Procedures | 13 Logs
6.13 Logs
Logs show all past activities and events of your PRTG monitoring setup. This is useful for
researching past user activities, system events, and, for example, to check whether messages
were sent. In a typical setup, a huge amount of log data is produced. Because the activity of
every single object is recorded, you can use this information to check if your setup works
exactly as desired.
There are several filters available to make navigating the log entries easier. See the Working
wit h Table List s 225 section for more information.
List with Log Entries
There are two options to open the logs list: Either you click the Log tab on the detail page of
a probe, group, device, or sensor, or you choose the Logs item in the main menu.
change settings.
Tabs Bar on Group and Probe Lev el
Click 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 259 .
216 11/24/2017
Part 6: Ajax Web Interface—Basic Procedures | 13 Logs
Logs (Main Menu)

Click Logs in the main menu bar 259 to show a table list of all system log entries in your
configuration. Hover over Logs and select another option to narrow down your log search.
Choose between:
LOGS
All Open a table list 225 with log information for all objects in your
configuration, newest first.
St at us Changes › Open a list with log information for certain status changes only.
Hover over St at us Changes 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 over Sy st em Event s 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 Administ rat ion,
Not ificat ions, Schedules, User Account s, User Groups, Report s,
Libraries, or Maps.
You can open a specific tab directly with the context-button
Hist ory in the page header bar 174 on the corresponding
pages.
11/24/2017 217
Part 6: Ajax Web Interface—Basic Procedures | 14 Tickets
6.14 Tickets
PRTG Network Monitor includes its own ticket system. With tickets you can manage and
maintain various issues that may appear while monitoring a network. A ticket in PRTG contains
information about recent events in your PRTG installation that 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 267 has finished, and PRTG users can create tickets as well
for every kind of issue. In addition, you can set up notifications that open a ticket when
something uncommon occurs in your network. The task comes to life 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 take 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 a ticket is assigned to you or if one of your
tickets has been changed. See section Ticket s as Emails 222 for details and how to turn off
emails about tickets.
List of Tic kets
You can turn off the tickets system for particular user groups in Sy st em Administ rat ion—
User Groups 3123 except for the PRTG Administrators group. The users in the admin group
will not receive new ToDo tickets (and notifications about changes) by default, only the PRTG
System Administrator user. You cannot change this behavior. However, you can turn off ticket
emails 222 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.

In the corresponding ticket, only device templates will be listed that PRTG used to create
sensors.
218 12/11/2017
§ 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 occurs, etc.
§ A notification 2966 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.
The Relat ed Object of ToDo tickets is Sy st em.
§ Not ificat ion Ticket s: Tickets created via Not ificat ions 2966 in case of monitoring alerts
States of Tickets
Tickets can have three different states depending on the working process regarding the
corresponding issue:
Sy m St at e Descript ion
bol
Open New tickets will be open as long as the corresponding issue exists as
described in the ticket.
Resol The issue as described in the ticket does not persist any longer. Someone
ved took care of it.
Close Usually, the ticket has been resolved before, the solution to the issue has
d been checked for correctness, and the ticket does not require any other
action.
12/11/2017 219
Tickets (Main Menu)

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 ion—User Groups 3123 . 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 that is filtered to your needs. In the main
menu bar 250 , hover over 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 that are assigned to the current user. Hover over My Ticket s
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 over All Ticket s 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 218 ToDo. Hover over ToDo Ticket s to show
other menu items for filtering these tickets depending on their status:
§ Open
Click to show all open ToDo tickets. Hover over Open 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
220 12/11/2017
§ All
§ Open Ticket
Hover over and select Open Ticket from the menu. This will open the Open Ticket
dialog. In the first step, select the object on which you want to focus in the ticket via the
Object Select or 228 . Click OK.
You can leave this step out when using the context menu 234 of this object in the device
tree to open the ticket.
In step 2, provide the following information and confirm by clicking on OK to create a User
Ticket:
§ Subject : Enter a meaningful title for the ticket that indicates the topic of the issue.
§ Assigned t o: Select a user (or user group) who will be responsible for this issue from the
dropdown list.
§ Priorit y : Define a priority 229 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 225 .
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 that 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 that are assigned to you (the user who is currently logged in)
· Groups: show tickets that are assigned to a specific user group only
· Users: show tickets that are assigned to a specific user only

· Disallowed: users or user groups that 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, or sensors with the
Object Select or 228 .
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 conduct several actions.
12/11/2017 221
An Open ToDo Tic ket with Instruc tions
Actions
For best experience with PRTG, check every ticket and select appropriate actions.
Only members of user groups that have the corresponding access rights 148 can view and
edit tickets that 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 assign the ticket to another user. Furthermore, you can add a text message to this ticket.
Confirm your changes by clicking OK.
§ Assign: Opens a dialog where you can give the ticket to another user. Select a user (or user
group) via the dropdown menu. Furthermore, you can add a text message to this ticket.
Confirm your assignment by clicking Save.
§ Resolve: Opens a dialog where you can resolve the ticket by clicking 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 that indicates, for example, what has been done
concerning the issue.
§ Close: Opens a dialog where you can close the ticket by clicking 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 that indicates, for example, why you have opened the
ticket again. Confirm reopening and assignment by clicking Save.
Tickets as Emails
You can receive all tickets that are assigned to you or to your user group as emails. You will
also be notified via email each time this ticket is edited. This way, you will always be 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 ion—User Account s 3116 . If you disable emails for tickets for a
user account, this particular user will not receive any ticket emails anymore.
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.
222 12/11/2017
More
Paessler Blog: A New Feature Was Assigned to You in PRTG: Ticket System Keeps Track of
Network Monitoring Issues
§ https://www.paessler.com/blog/2014/02/03/prtg/ticket-system-keeps-track-of-network-
monitoring-issues
Ajax Web Interface—Basic Procedures—Topics

§ Login 158
§ SSL Certificate Warning 162
§ Welcome Page 165
· Customer Service 168
§ General Layout 170
§ Sensor States 183
§ Review Monitoring Data 186
§ Compare Sensors
§ Historic Data Reports 192
§ Similar Sensors 197
§ Recommended Sensors 201
§ Object Settings 205
§ Alarms 207
§ System Information 210
§ Logs 216
§ Tickets 218
§ Working with Table Lists 225
§ Object Selector 228
§ Priority and Favorites 229
§ Pause 232
§ Context Menus 234
§ Hover Popup 249
§ Main Menu Structure 250

§ Ajax Web Interface—Device and Sensor Setup 266
12/11/2017 223
Related Topics
224 12/11/2017
Part 6: Ajax Web Interface—Basic Procedures | 15 Working with Table Lists
6.15 Working with Table Lists

Throughout the web interface you often see table lists of items, for example, sensor or device
lists. Table lists are also available on the overview pages of Libraries 2984 , Maps 3026 , Report s 3000
, Not ificat ions 2966 , and Schedules 3079 , as well as in Logs 216 and Ticket s 218 . 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, like for sensors 254 , tickets 220 , and similar sensors 198 , there is also
an in-line filter available directly above the table. The filter options depend on the current page.
Example of a Table List
11/24/2017 225
FEAT DISPLAY WHAT IT DOES

URE
Paging The content of a table is displayed over

several pages. Click the arrow symbols at
the end of a list to view other pages, or to
jump to the beginning or the end of the list.
New Click the window symbol at the beginning

Windo of a list to open the table in a new window.
w
Date Use the date and time picker to show table

Range list entries within a specific time span. Click
the first date field for the start date and the
second field for the end date. A calender
dialog opens where you can select date and
time. Click the Done button to apply the
selected date and time.
Select When viewing log lists (not available in other

Range lists), click Select Range in 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.
Items Click It ems at the beginning of the list to

select how many rows are shown on each
page. Choose between 50, 100, 500, and
1000.
Sorting Click the column headers to sort lists by the

respective column. You select all words
with arrows next to them for sorting, for
example, by St at us, Last Value, Priorit y ,
and more. The available options vary
depending on the type of list.
Show Click the XML option at the beginning of a

XML list to download the current page in XML
format. Your browser will usually show a
download dialog.
Filterin Use the filter options to show specific

g objects in the list. Enter one or more Tags
131 into the field Tagged Wit h to filter the
list for corresponding objects. You can use

the add (+) and remove (X) signs to
categorize tags as "must have this tag" or
"must not have this tag".
226 11/24/2017
Click the entry below Relat ed t o to
choose an object from the device tree with
the Object Select or 228 to show
corresponding objects.
Related Topics
§ Mult i-Edit List s 2949
11/24/2017 227
Part 6: Ajax Web Interface—Basic Procedures | 16 Object Selector
6.16 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 the corresponding nodes. Click 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 over a sensor on the right
side to view its parent device and group.
You can also directly search and find sensors by entering the sensor name, group name, device
name, or tag into the Find... box above the sensor list.
Select an object and click the Save button.
228 11/24/2017
Part 6: Ajax Web Interface—Basic Procedures | 17 Priority and Favorites
6.17 Priority and Favorites

You can set priorities for all your monitoring objects and also categorize devices or sensors as
favorites. Both settings affect how your objects are displayed.
Settings for priority and favorites are stored for the entire installation. They are not user
specific.
Priority for All Objects

The priority setting affects the order in which 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 186 for sensors with a high
priority.
To change priority settings, right-click an object to open the context menu 234 and select
Priorit y /Favorit e. 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 with one click on a star, for example, for sensors on
a device overview page.
Context Menu:
Priority
Select 4 or 5 stars for particular sensors to activate their gauges on device overview
pages.
Select 5 stars for a map to show it as an entry in the main menu bar 250 under Home.
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 it to
open the context menu 234 . Select Priorit y /Favorit e | Add t o Favorit es. A small black flag
symbol will be added next to the object's name.
11/24/2017 229
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 234 .
Context Menu: Priority /Fav orites

(Remov e)
There is also the option to add a device or sensor to favorites with one click in the device
tree. Just click the small flag symbol to the right of the respective object name. If the flag is
black, the specific object is already a favorite; clicking the flag again 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
230 11/24/2017
Priority and Favorites in the Page Header Bar

You can add any device or sensor to favorites on its details page by clicking the small flag
symbol in the page header bar 174 . If the flag is blue, the selected object is already a favorite.
Clicking the flag again will remove it from favorites and the flag will turn gray again. It is also
possible to set the priority of the object by clicking 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
11/24/2017 231
Part 6: Ajax Web Interface—Basic Procedures | 18 Pause
6.18 Pause
If you want to pause monitoring, you have several possibilities to do so in PRTG. You can
pause monitoring for a single sensor, a whole device, group, or even probe.
While a sensor is paused, it will not collect any monitoring data, will not change its status
183, and will not trigger any notifications 135 . An object will keep its pause status also after a
restart of PRTG.
Pause by Intention—Manually or by Schedule

Navigate to the desired object in the device tree and select Pause from the context menu 234 .
You can choose Pause Indefinit ely , or select a time after which monitoring will resume
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.
When selecting the Pause symbol from an object's hover popup 249 or while using multi-
edit 2949 , the object(s) will be paused indefinitely until resumed.
When selecting a pause option, you are prompted to enter a message. It will be shown in the
status message of the object as long as it is paused. Confirm with OK to pause the object or
click Cancel to not pause it.
PRTG Pause Message Prompt
Monitoring for objects can also be paused by applying a schedule (see Account Set t ings
—Schedules 3079 ) in the Object Set t ings 205 . If you pause a master object by schedule or
manually, you do not trigger a status change by dependency 133 . See this Knowledge Base
article Why will dependent objects not go into paused status automatically when I pause the
master object?
232 11/24/2017
Part 6: Ajax Web Interface—Basic Procedures | 18 Pause
Pause by Hierarchy
If you pause monitoring for a given object in the device tree 170 , all child objects underneath
will be paused as well. For example, if you pause a group, all sensors on all devices in this
group will also be paused. Once an object is paused, you can resume monitoring at any time
by selecting Resume from the context menu 234 . However, you cannot resume monitoring for
single child objects that are paused by a parent object, only for the object you originally set to
pause.
Pause by Dependency
There is a way you can make PRTG pause objects automatically. If you have a master object, for
example, a master Ping sensor for a device, PRTG can pause all dependent sensors on the
device automatically in case the master object is down. See Dependencies 133 for more
information and mind this Knowledge Base article Why will dependent objects not go into
paused status automatically when I pause the master object?
11/24/2017 233
Part 6: Ajax Web Interface—Basic Procedures | 19 Context Menus
6.19 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 250 or the hover popup 249 window. However, using the context menus is the easier way
in most cases.
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. See the following subsections for an overview of the available options.
§ Probe Context Menu 234
§ Group Context Menu 238
§ Device Context Menu 241
§ Sensor Context Menu 246
Probe Context Menu

The Probe Menu contains actions for your local probe, cloud probe, remote probes, or mini
probes 126 .
Probe Context Menu
234 11/24/2017
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
125 .
Det ails... Show the overview tab 186 of the selected probe.
Edit › Hover over Edit to show the Edit menu.
Edit Menu
The following actions are available:

§ Set t ings...
Open the Probe Set t ings 334 tab of this probe.
§ Not ificat ions...
Open the Not ificat ions 2966 tab of this probe.
§ Access Right s...
Open an assistant to edit User Access Right s 148 for this
probe.
§ Rename...
Open an assistant to edit the name of this probe.
§ Management ...
Open the Management 312 tab of this probe.
Add Group... Open an assistant that guides you through the process of adding a
new group to the selected probe.
For detailed instructions, see Add a Group 286 .
Add Aut o-Discovery Open an assistant that guides you through the process of adding a
Group... 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, see
section Using t he Aut o-Discovery 267 .
This option is not available on the Cloud Probe of a PRTG in

the cloud instance.
11/24/2017 235
PR OBE MENU
Add Device... Open an assistant that guides you through adding a new device to
the selected probe.
For detailed instructions, see Add a Device 295 .
Sort Alphabet ically Sort direct children (groups and devices) of the selected probe in
alphabetical order.
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 over Move 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 312 tab of the probe.
Pause › Hover over Pause to open the Pause menu.

—or— If the probe is already in paused or in "simulate error" status,
Resume appears. Click to restart monitoring on this probe.
Resume
236 11/24/2017
PR OBE MENU
Pause Menu
You can pause and resume monitoring on the selected probe. The
monitoring for all sensors in the object hierarchy 125 underneath
will be paused or 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 over Priorit y to open the Priorit y menu.
Context Menu Priority
Define the priority of the selected probe.

For details, see Priorit y and Favorit es 229 .
Hist oric Dat a › Hover over Hist oric Dat a to open the Hist oric Dat a menu.
11/24/2017 237
PR OBE MENU
Context Menu Historic

Data

§ Open the historic data report tabs for the specified interval 188 :
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, see Report s St ep by St ep 3005 .
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 186 of the selected probe.
Open Ticket Open the New Ticket dialog.

For details, see the section Ticket s 221 .
Group Context Menu

The Group Menu contains actions for your groups 126 .
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
125 .
Det ails... Show the overview tab 186 of the selected group.
Edit › Hover over Edit to show the Edit menu. The following actions are
available:
238 11/24/2017
GR OU P MENU
§ Set t ings...
Open the Group Set t ings 358 tab of this group.
Open the Not ificat ions 2966 tab of this group.
group.
§ Rename...
Open an assistant to edit the name of this group.
§ Management ...
Open the Management 312 tab of this group.
Add Group... Open an assistant that guides you through the process of adding a
new group to the selected group.
For detailed instructions, see Add a Group 286 .
Add Aut o-Discovery Open an assistant that guides you through the process of adding a
Group... 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 267 .

the cloud instance.
Add Device... Open an assistant that guides you through adding a new device to
the selected group.
For detailed instructions, see Add a Device 295 .
Aut o-Discovery This option is only available for auto-discovery groups. These are
groups with automatic device identification or sensor creation
enabled 359 . Hover over Aut o-Discovery to show its 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 runs in the background and uses the option you set in
the Sensor Management section of the group settings 359 . If
found, you see new devices with sensors after a few minutes (if
found). For more information, please see Aut o-Discovery 268
(Run Aut o-Discovery Now).
11/24/2017 239
GR OU P MENU
§ Run Aut o-Discovery wit h Templat e: Open an assistant 270 to

start an automatic search with a desired device template. This is
the Sensor Management option Aut omat ic sensor creat ion
using specific device t emplat e(s). Other automatic device
identification options are not available. The option you set in the
Sensor Management section of the group settings 359 will not
apply.

the cloud instance.
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 that guides you through cloning the selected
group.
For detailed instructions, see Clone Object 2946 .
Move › Hover over Move 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 312 tab of the group.

—or— If the group is already in paused or in "simulate error" 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 125 underneath
will be paused or resumed.
240 11/24/2017
GR OU P MENU
date.
group. Use the date time picker to enter the date and time.
Priorit y › Hover over Priorit y to open the Priorit y menu. Define the priority
of the selected group.
Hist oric Dat a › Hover over Hist oric Dat a to open the Hist oric Dat a menu. The
PRTG.
Send Link by Email Send the link to the selected group by email. Click to create a new
link to the overview tab 186 of the selected group.

For details, see section Ticket s 221 .
Device Context Menu

The Device Menu contains actions for your devices 127 .
DEVICE MENU
Check Now Perform an immediate scan for the selected device. This queries
the data for all sensors underneath in the object hierarchy 125 .
11/24/2017 241
DEVICE MENU
Det ails... Show the overview tab 186 of the selected device.
available:
§ Set t ings...
Open the Device Set t ings 385 tab of this device.
Open the Not ificat ions 2966 tab of this device.
device.
§ Rename...
Open an assistant to edit the name of this device. You can also
select another device icon.
Add Sensor... Open an assistant that guides you through adding a new sensor to
the selected device.
For detailed instructions, see Add a Sensor 309 .
Aut o-Discovery Hover over Aut o-Discovery to show the Aut o-Discovery menu.
§ Run Aut o-Discovery : Start an automatic search immediately to
automatically add new sensors to the selected device. The
search runs in the background and uses the option you set in
the Sensor Management section of the device settings 385 . If
found, you see new sensors on this device after a few minutes.
For more information, please see Aut o-Discovery 268 (Run Aut o-
Discovery Now).
If you have set the option Manual (no aut o-discovery ) in
the device settings section 387 Sensor Management and
start the auto-discovery from the context menu, PRTG will run it
using the standard device identification and change the device
setting to Aut omat ic device ident ificat ion (st andard,
recommended). Please note that the Enterprise Console 3211
behaves differently in this case.
§ Run Aut o-Discovery wit h Templat e: Open an assistant 270 to
start an automatic search with a desired device template. This is
the Sensor Management option Aut omat ic sensor creat ion
using specific device t emplat e(s). Other automatic device
identification options are not available, The option you set in the
Sensor Management section of the device settings 387 will not
apply.
242 11/24/2017
DEVICE MENU
Creat e Device Open an assistant that guides you through creating a new device
Templat e... template. The template is then available in auto-discovery 267 .
For detailed instructions, see Creat e Device Templat e 2954 .
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
186 where you can add the according sensor types directly.
This option is only available if the recommendation engine is

enabled 3100 .
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
device.
are available:
§ 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 or "simulate error" 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 or
resumed.
11/24/2017 243
DEVICE MENU
date.
device. Use the date time picker to enter the date and time.
Priorit y /Favorit e › Hover over Priorit y /Favorit e to open the Priorit y /Favorit e
menu. Define the priority of the selected device, or add to or
remove it from the favorite devices list.
PRTG.
Device Tools › Hover over Device Tools to open the Device Tools menu.

the cloud instance.
Context Menu Dev ic e Tools
244 11/24/2017
DEVICE MENU
§ Go To Service URL...
Open the service page that you have defined in the Device
Set t ings 385 . 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.
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, see Remot e Probe Quick Inst all 3362
This option is only available on devices on local probes.
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 186 of the selected device.

11/24/2017 245
Sensor Context Menu

The Sensor Menu contains actions for your sensors 127 .
SENSOR MENU
Check Now Perform an immediate scan for the selected sensor.
Det ails... Show the overview tab 186 of the selected sensor.
available:
§ Set t ings...
Open the Sensor Set t ings 411 tab of this sensor.
Open the Not ificat ions 2966 tab of this sensor.
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 183 .
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 183 ) and will not trigger 2924 any
more notifications 2966 .
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.
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, see Alarms 208 section.
Delet e... Delete the selected sensor. PRTG will ask for confirmation before
sensor.
246 11/24/2017
SENSOR MENU
are available:
§ 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 183 or in Simulat e Error
St at us, Resume appears. Click Resume to restart monitoring on
Resume this sensor.
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.
Inheritance of the Schedules, Dependencies, and Maint enance
Window setting from a parent device, group, or probe will be
suspended for this timeframe and set again afterwards.
Simulat e Error St at us Set the selected sensor to a Down status 183 . Like for the paused
status, Resume will appear in the context menu if a the selected
sensor is already in a simulated error status.
"Simulate error status" does not work for sensors that run on
a PRTG Mini Probe.
Priorit y /Favorit e › Hover over Priorit y /Favorit e to open the Priorit y /Favorit e
menu. Define the priority of the selected sensor, or add or remove
it from the favorite devices list.
11/24/2017 247
SENSOR MENU
§ Open the historic data tab for the specified interval 189 : Live
Dat a..., Last 2 day s..., Last 30 day s..., or Last 365 day s...
§ View Hist oric Dat a: Open the Hist oric Dat a 192 tab of this
sensor.
PRTG.
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 186 of the selected sensor.

248 11/24/2017
Part 6: Ajax Web Interface—Basic Procedures | 20 Hover Popup
6.20 Hover Popup

Whenever you rest the mouse pointer for a second over an object's icon in the device tree 170 ,
a hover popup window will appear, showing details about this object. It contains information
from the object's overview tab 186 , as well as several graphs. The exact information provided
depends on the kind of object you are hovering over.
Hov er Menu Example: Ac tiv e Direc tory Replic ation Errors Sensor
The hover popup only appears 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 that enable you to view or
edit the current object. These are the most important options from this object's context menu
234 , which is shown when right-clicking it.
11/24/2017 249
Part 6: Ajax Web Interface—Basic Procedures | 21 Main Menu Structure
6.21 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 an item directly, or hover
over it to show more items.
PRTG Main Menu Bar
The following menu items are available:
§ Home 250
§ Devices 252
§ Libraries 254
§ Sensors 254
§ Alarms 257
§ Maps 258
§ Reports 259
§ Logs 259
§ Tickets 260
§ Setup 261
§ Search Box 263
§ Logout (Off Symbol) 264
Home
Click to open the user's homepage. The default setting is the PRTG welcome page 170 . You can
change the homepage in the user account settings 3050 . Point to Home to show other menu
items.
250 11/24/2017
PRTG Main Menu: Home
HOME
Sample Dashboard Open a preconfigured dashboard to view monitoring data in

another layout. Dashboards provide different preset overviews
with the status of your sensors. This dashboard is one of the
default Maps 3026 that PRTG creates automatically with a new
installation.
The Home menu shows maps that have a 5***** priority 229 .
You can include up to 10 map entries in this menu.
You can change the appearance of the default dashboard with

the Map Designer 3034 . To not show the sample dashboard in
the menu, define a priority 229 lower than 5***** for this map.
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.
These dashboards are not customizable. You can create your
own overview pages using the Maps 3026 feature. New
installations of PRTG do not include these dashboards anymore.
Swit ch Clust er Node › This option is only available if PRTG runs in Clust ering 122 mode.
Show available cluster nodes. Hover over Swit ch Clust er Node 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.
11/24/2017 251
HOME
Welcome t o PRTG Open the Welcome Page 165 that shows the Paessler news feed
and various information about your PRTG installation, and it
provides quick links to major sections of the web interface.
This is the default homepage of the PRTG web interface.
Make This My Change the page that is loaded when you click Home in the main
Homepage 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 this command
again, or by changing the Homepage URL in the My Account 3050
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 over Devices to show other menu items.
PRTG Main Menu: Dev ic es
DEVICES
All Open the Overview tab of the Root 125 group that shows a group
view of all your devices (the device tree).
Favorit e Devices Open a table list of all devices marked as Favorit e 229 . Click the
Print QR-Codes button to show a printable list of the QR codes of
all your favorite devices.
252 11/24/2017
DEVICES
To mark any device as a favorite device, select Priorit y /

Favorit e | Add t o Favorit es from its context menu or click
the small flag on a device's details page.
Device List Open a list view of all devices in your setup. Click to show a table
list of all devices in your setup.
In the table list 225 that appears, you can re-sort the items by
clicking the column's header items.
Dependencies Open an overview list of the Dependencies 133 configured for the
objects in your setup. You can select dependencies and define
master dependencies in the Schedules, Dependencies, and
Maint enance Windows settings of a monitoring object 205 (not
available for the Root group).
Add Group Start an assistant that guides you through the process of adding a
new group to your setup.
For more information, see section Creat e Object s Manually
285 .
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 that guides you through the process of adding a
Group 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, see section Using t he Aut o-Discovery
267
You can create new groups much faster by choosing Add

Aut o-Discovery Group... from a probe's or group's context
menu.

the cloud instance.
Add Device Start an assistant that 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.
11/24/2017 253
DEVICES
For more information, see section Creat e Object s Manually

285 .
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. Hover over Libraries to show other menu items.
For more information, see Libraries 2984 section.
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 create 2987 a new library.
Select Library › Open an existing library. Hover over Select Library to show more
options. Follow the alphabetical menu path (it is specific to your
setup) to view your libraries. Click a library to open it.
Sensors
Click to show a table list of all sensors 127 . In the table list 225 that appears, you can re-sort the
items by clicking the column's header items and you can filter the list by related object and tag
with the inline filter directly above the table. Hover over Sensors in the main menu bar to show
other menu items.
254 11/24/2017
The column Last Value shows only the last value of the sensor's primary channel.
For most sensor lists, you can use Mult i-Edit 2949 to change the settings of more than one
sensor at once.
PRTG Main Menu: Sensors
SENSOR S
All Open a table list 225 of all sensors 127 . In the table list appearing,
you can re-sort the items by clicking the column's header items.
The column Last Value shows only the last value of the
sensor's primary channel.
Add Sensor Start an assistant that guides you through the process of adding a
new sensor to an existing device. For more information, see
section Add a Sensor 309 . During the process, you can also
choose to create a new device via the Add a Device 295 assistant
(that you can also open from the "Devices" menu 252 directly).
Favorit e Sensors Open a table list of all sensors that you marked as Favorit e 229 .
To mark any sensor as a favorite sensor, select Priorit y /
Favorit e | Add t o Favorit es from its context menu or click
the small flag on a device's details page.
11/24/2017 255
SENSOR S
Top 10 List s › Open a dashboard view with different top 10 lists that show best
or 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 over Top 10 List s 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.
The shown sensors are selected by default tags.
By Current Value › Open a list of sensors filtered by value. Hover over By Current
Value to show other menu items. Follow the menu path to view
table lists 225 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 Sensors
§ CPUs
§ Disks
§ Memory
The shown sensors are selected by default tags.
By Current St at us › Open a list of sensors filtered by status. Hover over By Current

St at us to show other menu items. Follow the menu path to view
table lists 225 of all sensors in a certain status.
For more information about sensor states, see Sensor St at es
183 section.
By Upt ime/Downt ime Open a list of sensors filtered by different parameters. Hover over
› By Upt ime/Downt ime to show other menu items. Follow the
menu path to view table lists 225 of all sensors sorted by
§ Best Upt ime (%)
§ Highest Upt ime (Time)
§ Worst Downt ime (%)
§ Highest Downt ime (Time)
256 11/24/2017
SENSOR S
By Ty pe › Open a list of sensors filtered by sensor type 412 . Hover over By

Ty pe to show other menu items. Follow the alphabetical menu
path (it is specific to your setup) to view a sensor table list 225
containing only sensors of one specific sensor type.
By Tag › Open a list of sensors filtered by tag 131 . Hover over By Tag to
show other menu items. Follow the alphabetical menu path (it is
specific to your setup) to see available tags. Select a tag to view a
table list 225 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 229 , scanning interval
328 , access rights 148 , notification trigger settings 205 , schedule 134 ,
and dependency 133 . Click to show a sensor cross reference for all
sensors. Hover over Cross Reference to show other menu items.
Follow the menu path (it is specific to your setup) to view cross
reference information for sensors by type or tag.
View Hist oric Dat a Open an assistant for a quick generation of sensor data reports.
For more information, see Hist oric Dat a Report s 192 section.
Similar Sensors Open an overview page with a list of similar sensors.

Overview
For more information, see Similar Sensors 197 section.
Alarms
Click to show all sensors that currently show a Down, Down (Part ial), Warning, or Unusual
status. In the table list 225 that appears, you can re-sort the items by clicking the column's
header items. If you select Show as Gauges, this command displays the sensor gauges 186 in a
size corresponding to their priority. Hover over Alarms to show other menu items.
PRTG Main Menu: Alarms
11/24/2017 257
ALAR MS
All Open a list of all sensors that are currently in Down, Down
(Part ial), Down (Acknowledged), Warning, or Unusual status 183 .
Show as Gauges Open a page with the gauges of all sensors that 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 that are currently in Down, Down
(Part ial), or Down (Acknowledged) status.
Warnings Only Open a list of all sensors that are currently in Warning status.
Unusuals Only Open a list of all sensors that 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. Hover over Maps to show other menu items.
For more information, see Maps 3026 section.
PRTG Main Menu: Maps
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 3031 a new map.
Select Map › Open an existing map. Hover over Select Map to show other
menu items. Follow the menu path (it is specific to your setup) to
select a map.
258 11/24/2017
Reports
Click to open the Report s overview page where you can view or add reports of your
monitoring data. Hover over Report s to show other menu items.
For more information, see Report s 3000 section.
PRTG Main Menu: Reports
R EPOR TS
All Open the Report s overview page where you can view or add
reports of your monitoring data.
Add Report Open an assistant to directly add 3005 a new report.
Select Report › Open an existing report. Point to Select Report to show other
menu items. Follow the menu path (it is specific to your setup) to
select a report.
Configuration Reports › Create reports for maps, reports, users & user groups, and system
configuration to document changes to the configuration. Point to
Report s | Configurat ion Report s to see the available
configuration reports 3004 .
Logs
Click to show log information for all objects in your configuration, newest first. In the table list
225 appearing, you can filter the items by using the respective options 225 . Hover over Logs to
show other menu items.
For more information, see Logs 216 section.
Logs for monitoring objects (for example, sensors) are available as long as you define
Logfile Records in the Hist oric Dat a Purging settings under Sy st em Administ rat ion—
Core & Probes 3113 .
11/24/2017 259
PRTG Main Menu: Logs
LOGS
All Open a table list 225 with log information for all objects in your
configuration, newest first.
St at us Changes › Open a list with log information for certain status changes only.
Hover over St at us Changes 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 over Sy st em Event s 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 Administ rat ion,
Not ificat ions, Schedules, User Account s, User Groups, Report s,
Libraries, or Maps.
You can open a specific tab directly with the context-button
Hist ory in the page header bar 174 on the corresponding
pages.
Tickets
Click to show all tickets that are assigned to the current user. In the table list 225 that appears,
you can re-sort the items by clicking the column's header items, and you can filter the list with
the inline filter directly above the table. Hover over Ticket s to show other menu items.
260 11/24/2017
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, see section Ticket s 218 .
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 that are assigned to the current user.
My Ticket s › Open a list of all open tickets that are assigned to the current
user. Hover over My Ticket s 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 over All
Ticket s 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 over ToDo
Ticket s 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 OK to create a User Ticket .
For more information about available options, refer to section
Ticket s 218 .
Setup
Click to show the setup page. Hover over Set up to show other menu items.
For more information, see Set up 3048 section.
11/24/2017 261
PRTG Main Menu: Setup
SETU P
Overview Open the setup page 3048 .
Account Set t ings › Open the My Account 3050 settings. Hover over Account Set t ings
to show and open the tabs of account settings directly. Choose
from:
§ My Account 3050
§ Notifications 3057
§ Notification Contacts 3075
§ Schedules 3079
Sy st em Open the Sy st em Administ rat ion 3084 settings. Hover over

Administ rat ion › Sy st em Administ rat ion to show and open the tabs of the system
administration settings directly. Choose from:
§ Manage Subscriptions 69 (PRTG in the cloud only)

§ User Interface 3084
§ Monitoring 3096
§ Notification Delivery 3102
§ Core & Probes 3108
§ Cluster 3133 (PRTG on premises only)

§ User Accounts 3116
§ User Groups 3123
§ Administrative Tools 3128
262 11/24/2017
SETU P
PRTG St at us Open the PRTG St at us—Sy st em St at us 3135 page. When running a

cluster, hover over PRTG St at us to show other menu items.
Choose from:
§ System Status 3135
§ Cluster Status 3150
License Open the license act ivat ion st at us 3152 page.
Aut o-Updat e › Open information about the Soft ware Aut o-Updat e 3146 status of
your PRTG installation. On this page, you can also download and
install available updates. Hover over Aut o-Updat e to show other
menu items. Choose from:
§ St at us 3146 to view the update status and to manually check for
the latest update.
§ Set t ings 3147 to define your update settings.
Downloads › Open the downloads page 3158 of PRTG for additional downloads.
Choose from:
§ Client App for Windows (Enterprise Console) 3158 (PRTG on

premises only)
§ Client Apps for Mobile Devices 3158
§ Remote Probe Installer 3158
§ PRTG Tools 3159
§ Desktop Notifications 3160
PRTG API Open the documentation of the Applicat ion Programming

Int erface (API) Definit ion 3336 for your installation.
Cont act Support Open the Cont act Paessler Support / Send Your Feedback t o
Paessler 3162 form.
Search (Reading-glass Symbol)
PRTG Main Menu: Searc h Box
11/24/2017 263
Click the Search box to find objects in your monitoring setup. Enter your search term, and
start the search with the enter key. PRTG will perform a string search in your entire monitoring
setup, including groups, devices, sensors, libraries, maps, reports, tickets, and object
comments, as well as in the PRTG user manual. You will see all search results on a new page.
You can only search for names that are actually displayed. For example, to search for a
specific user, use their display name. The login name or email address of a user account
will not be used.
Logout (Off Symbol)
PRTG Main
Menu:
Logout
Button
Log out the current user and return to the login screen 158 .
Context Menu
Additionally, there are Cont ext Menus 234 available for all objects. Right-click an object to
open it.
264 11/24/2017
Part 7
Ajax Web Interface—Device and Sensor Setup
3/7/2017 265
Part 7: Ajax Web Interface—Device and Sensor Setup |
7 Ajax Web Interface—Device 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 and uses Asynchronous Java Script and XML (AJAX) to deliver a
powerful and easy-to-use user experience. While you are logged in 158 , the PRTG web interface
continuously refreshes the data on the screen (via Ajax calls) so it always shows the current
monitoring results (you can set 3116 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 a 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 so that you see more information at a glance.
The following sections introduce device and sensor setup in the Ajax Graphical User Interface
(GUI).
Ajax Web Interface—Device and Sensor Setup—Topics

§ Auto-Discovery 267
§ Create Objects Manually 285
§ Manage Device Tree 312
§ Root Group Settings 314
§ Probe Settings 334
§ Group Settings 358
§ Device Settings 385
§ Sensor Settings 411 —List of Available Sensor Types 412
§ Additional Sensor Types (Custom Sensors) 2911
§ Sensor Channels Settings 2915
§ Sensor Notifications Settings 2924

§ Ajax Web Interface—Basic Procedures 156
Related Topics
266 3/7/2017
Part 7: Ajax Web Interface—Device and Sensor Setup | 1 Auto-Discovery
7.1 Auto-Discovery
The PRTG auto-discovery 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 because it
involves a lot of SNMP and WMI.
PRTG already runs a quick initial auto-discovery as soon as you finish the installation of
PRTG to automatically show you several available devices in your network.
How Auto-Discovery Works

The PRTG 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 device templates that PRTG users created (see Creat e Device
Templat e 2954 section).
You can use the auto-discovery on group level for a range of IP addresses, or for individual
devices that you have created manually. You can run the auto-discovery just once, on demand
via the context menu, or scheduled every hour, day, or week. Running the auto-discovery daily
or weekly on group level automatically creates new devices when they are connected to the
network and adds according sensors.
PRTG will create a notifying ticket 218 when at least one new device or sensor has been
discovered. You will also receive a ticket in case of an error. By default, PRTG sends tickets
as email as well. You can change this behavior in your user account settings, section Ticket
Sy st em 3055 .
Restrictions
Please be aware of the following restrictions of the auto-discovery:
§ PRTG cannot discover devices that cannot be pinged, because Step 1 uses pings. If, for
example, a firewall blocks echo requests, PRTG cannot discover a device behind it.
§ Please define authentication settings for Windows Sy st ems, Linux (SSH/WBEM) Sy st ems,
VMware/X EN Servers, SNMP Devices, Dat abase Management Sy st ems, and Amazon
CloudWat ch to fully benefit from the power of this feature. We recommend that you define
these settings in the Root group 314 .
§ 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.
12/8/2017 267
§ If a device already exists on the same probe, the auto-discovery will skip this device and not
create a duplicate. If a device with the same IP address as a found device already exists on
another probe, it will be added to the probe where the auto-discovery runs nevertheless.
This is because new remote probes might run in another network.
§ Auto-discovery on group level will not create new sensors on devices that already exist in
PRTG but only on newly discovered devices. If you want to automatically add sensors to an
existing device, please run the auto-discovery on this device.
§ Using frequent auto-discoveries of large network segments can lead to performance issues.
Because of this we recommend that you only schedule regular auto-discoveries where
necessary. For detailed information, see this Knowledge Base article: Why can automatic
auto-discoveries evoke performance issues?
§ PRTG automatically adds suitable device icons to discovered devices. PRTG uses a device's
MAC address for this purpose, which it determines via ARP (Address Resolution Protocol).
This only works via IPv4 and not with IPv6. Usually, ARP works only in the local network
unless your router supports ARP and you configure it accordingly.
§ If you use Multi-Edit 2949 to automatically create sensors using specific device template(s), the
Auto-Discovery is not automatically started. To manually start the Auto-Discovery, right-click
the individual devices and select Aut o-Discovery | Run Aut o-Discovery .
HTTP sensors indicate the access type to the target device with their names (HTTP, HTTP
(8080), and HTTPS). This approach helps to distinguish HTTP sensors if the auto-discovery
adds more than one instance to a device.
Run Auto-Discovery Now

You can run an auto-discovery at any time for a group or a device. To do so, right-click the
object to analyze and select Run Aut o-Discovery from the context menu 234 . PRTG
immediately starts searching for new objects that can be added to the device tree. If you use it
for an auto-discovery group (not available on cloud probes), PRTG will add devices with
according sensors, if found. If you use it for a device, PRTG will add new sensors, if found. You
can always see in the corresponding page header bar 174 when PRTG ran the last auto-
discovery on a selected group or device.
The auto-discovery will also re-add devices or sensors you have manually deleted. If you
do not want this, please create objects manually 285 only.
Creating an Auto-Discovery Group

There are several ways to start auto-discovery:
§ Select Devices | Add Aut o-Discovery Group from the main menu bar 250 . 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 234 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.
268 12/8/2017
Add Auto-Disc ov ery Group Dialog
§ St ep 1
Choose a probe or group you want to add the new group to. Click Cont inue.
§ St ep 2
Add auto-discovery settings as described below.
12/8/2017 269
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 131 .
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 works
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 you enable using specific device
templates above. 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. PRTG will use the selected templates for auto-discovery on
the current device. Choose from:
§ ADSL
§ Amazon Cloudwat ch
§ Buffalo TeraSt at ion NAS
§ Cisco ASA VPN
§ Cisco Device (Generic)
270 12/8/2017
§ Dell EqualLogic
§ Dell MDI Disk
§ DNS Server
§ Environment Jacart a
§ Environment Poseidon
§ FTP Server
§ Generic Device (PING only )
§ Generic Device (SNMP-enabled)
§ Generic Device (SNMP-enabled, Det ailed)
§ HTTP Web Server
§ Hy per V Host Server
§ IPMI enabled devices
§ Juniper NS Device
§ Linux/UNIX Device (SNMP or SSH enabled)
§ Mail Server (Generic)
§ Mail Server (MS Exchange)
§ Microsoft Sharepoint 2010
§ NAS LenovoEMC
§ NAS QNAP
§ NAS Sy nology
§ Net App
§ NTP Server
§ Print er (HP)
§ Print er Generic
§ RDP Server
§ RMON compat ible device
§ Server (Compaq/HP agent s)
§ Server (Dell)
§ Server Cisco UCS
§ Server IBM
§ SonicWALL
§ SSL Securit y Check
§ Swit ch (Cisco Cat aly st )
12/8/2017 271
§ Swit ch (Cisco IOS Based)

§ Swit ch (HP Procurve)
§ UNIX /Linux Device
§ UPS Healt h (APC)
§ UPS Healt h (Generic)
§ UPS Healt h (Liebert )
§ VMware ESX / vCent er Server
§ Webserver
§ 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

218 and list the device templates that it used to create new
sensors. The ticket will not show templates that were not applied.
Discovery Schedule Define when PRTG will run the auto-discovery. Choose between:
§ Once: Perform auto-discovery only once. PRTG will add new
devices and sensors once. If you select this option, you have to
start the auto-discovery manually 268 , it will not run automatically.
§ Hourly : Perform auto-discovery for new devices and sensors
every 60 minutes.
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 at the time defined in the Aut o-
Discovery Set t ings section of the Sy st em Administ rat ion—
Monit oring 3101 settings.
§ Weekly : Perform auto-discovery for new devices and sensors
every 7 days. The first auto-discovery will run immediately, all
The Discovery Schedule will be set to Once on all devices
created by the scheduled auto-discovery for performance
reasons.
272 12/8/2017
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.
Define your active directory domain in advance in the system
administration.
See Sy st em Administ rat ion—Core & Probes 3112 .
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 you select Class C network detection
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 you select Class C network detection
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 you select Class C network detection
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 you select the IP list option above. Enter a
IPv6/DNS Name List list of IP addresses or DNS names that the auto-discovery will scan.
Enter each address in a separate line.
12/8/2017 273
IPv4 and Subnet (IPv4) This field is only visible if you select the IP and subnet option
above. Enter an expression in the format address/subnet , for
example, 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 you select the octet range option 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. For example, 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 you select active directory above. Enter
an organizational unit (OU) to restrict the active directory search to
computers that are part of this OU. Just enter the name of the OU
without any other term (so without "OU" in front). If you leave this
field empty, there will not be any restriction.
Make sure that the OU contains a host. If the OU is empty, you

will receive an error message.
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
The order is important, sub-OUs have to be listed left of their
particular parents!
Name Resolution Define how to monitor newly discovered devices. This affects only
new devices. The setting for existing devices will remain
unchanged. Depending on your selection the IP Address/DNS
Name field of an added device 385 shows the DNS name or IP
address that PRTG uses to access the target device. Choose
between:
§ Use DNS names (recommended): Monitor newly discovered
devices via their DNS names (if available).
§ Use IP addresses: Monitor newly discovered devices via their IP
address.
We recommend that you use the default value.
This setting does not affect how PRTG shows the devices in
the device tree.
274 12/8/2017
Device Rescan Define if you want to add devices that already exist in your PRTG
installation also to the currently selected group. Choose between:
§ Skip aut o-discovery for known devices/IPs (recommended):
Do not re-scan known devices or IP addresses, only add devices
with new IPs or DNS names when auto-discovering. PRTG will not
add devices that are already included elsewhere in your
configuration, for example, in other groups.
§ Perform aut o-discovery for known devices/IPs: Re-scan
devices with known IP addresses with every auto-discovery. This
option will add devices that already exist in other groups also to
this group and runs the auto-discovery on the newly added
devices.
The auto-discovery will not run on devices that already exist
in this group. If you want to run the auto-discovery for an
existing device, you have to start the auto-discovery on this
device.
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 314
group's settings, see section Inheritance of Settings 129 for more information. To change a
setting only for this object, disable inheritance by clicking the button next to inherit from
under the corresponding 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 to fully
exploit the power of this feature!
CR EDENTIALS FOR WINDOWS SYSTEMS
Click to disrupt the inheritance. See section Inheritance of Settings 129 for more
information.
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, enter the computer name here. If you want to use a
Windows domain user account (recommended), 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. Do not leave this field empty.
User Enter the username for Windows access. Usually, you will use
credentials with administrator privileges.
12/8/2017 275
Password Enter the password for Windows access. Usually, you will use
CR EDENTIALS FOR LINU X/SOLAR IS/MAC OS (SSH/WBEM) SYSTEMS
information.
User Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Login Define the authentication method to use 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.
PRTG can only handle keys in OpenSSH format that are not
encrypted. You cannot use password protected keys here.
In the text field, 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, see Monit oring via
SSH 3247 .
Password This field is only visible if you select password login 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 you select private key login above. Paste
a private key into the field (OpenSSH format, unencrypted). Usually,
you will use credentials with administrator privileges.
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 3128 in order for the private key change to take effect! For
details, see Monit oring via SSH 3247 .
For WBEM Use Protocol Define the protocol to use for WBEM. This setting is only relevant if
you use 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 to use for WBEM. This setting is only relevant if you
use WBEM sensors. Choose between:
276 12/8/2017
§ Set aut omat ically (port 5988 or 5989): Use one of the
standard ports, depending on whether you choose unencrypted
or encrypted connection above.
§ Set manually : Use a custom port. Define below.
WBEM Port This setting is only visible if you enable manual port selection
above. Enter the WBEM port number.
SSH Port Enter the port number to use for SSH connections.
By default, PRTG uses this setting automatically for all SSH
sensors 417 , unless you define a different port number in the
sensor settings.
SSH Rights Elevation Define the rights that you want to use to execute the command
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, as
defined above.
§ Run t he command as anot her user using 'sudo' (wit h
password): Use the rights of another user with a password
required for sudo to run commands on the target device, for
example, as root user.
§ Run t he command as anot her user using 'sudo' (wit hout
password): Use the rights of another user without a password
§ Run t he command as anot her user using 'su': Use the rights of
another user with su to run commands on the target device.
Target User This field is only visible if you choose sudo or su above. Enter a
username to run the specified command as a user other than root.
If you leave this field empty, you will run the command as root.
Ensure you set the Linux password even if you use a public or
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 you choose to run the commands using
su or sudo with password above. Enter the password for the
specified target user.
SSH Engine Select the method you want to use to access data with SSH
sensors 3247 . We strongly recommend that you keep the default
engine! For now, you still can use the legacy mode to ensure
compatibility with your target systems. Choose between:
12/8/2017 277
§ Default (recommended): This is the default monitoring method

for SSH sensors. It provides best performance and security.
§ Compat ibilit y Mode (deprecat ed): Try this legacy method only
if the default mode does not work on a target device. The
compatibility mode is the SSH engine that PRTG used in previous
versions and is deprecated. We will remove this legacy option
soon, so please try to get your SSH sensors running with the
default SSH engine.
You can also individually select the SSH engine for each SSH
sensor in the sensor settings.
CR EDENTIALS FOR VMWAR E/XENSER VER
information.
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,
Single Sign-On (SSO) passwords for vSphere do not support
special characters. See the manual sections for VMware
sensors for details.
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.
Session Pool Define if you want to use session pooling for VMware sensors.
Choose between:
§ Reuse session for for mult iple scans (recommended): Select
this option to use session pooling. With session pooling, a
VMware sensor uses the same session as created in advance
to query data and needs not to log in and out for each sensor
scan. We recommend that you choose this option because it
reduces network load and log entries on the target device,
resulting in better performance.
278 12/8/2017
§ Creat e a new session for each scan: If you select this option
and disable session pooling, a VMware sensor has to log in
and out for each sensor scan. We recommend that you use the
session pooling option above for better performance.
CR EDENTIALS FOR DATABASE MANAGEMENT SYSTEMS
information.
The settings you define in this section apply to the following sensor types:
§ ADO SQL v2 Sensor 445
§ Microsoft SQL v2 Sensor 1170
§ My SQL v2 Sensor 1187
§ Oracle SQL v2 Sensor 1353
§ Post greSQL Sensor 1469
Port for Databases Define which ports PRTG will use for connections to the monitored
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
12/8/2017 279
Custom Database Port Enter the number of the port that PRTG will use for database
connections. Please enter an integer value.
All database sensors on this device will use this port to
connect.
Authentication Mode Select the authentication method for the connection to the SQL
database. Choose between:
§ 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 390 for the database connection.
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 select 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 (5 minutes).
CR EDENTIALS FOR AMAZON CLOU DWATCH
information.
Access Key Enter your Amazon Web Services (AWS) access key. Please see the
corresponding Amazon CloudWatch sensor 418 documentation to
learn more about the rights that are required for querying AWS
CloudWatch metrics.
Secret Key Enter your Amazon Web Services (AWS) secret key. Please see the
CloudWatch metrics.
280 12/8/2017
CR EDENTIALS FOR SNMP DEVICES
information.
SNMP Version Select the SNMP version for the device connection. Choose
between:
§ v1: Use the simple v1 protocol for SNMP connections. This
protocol only offers clear-text data transmission, but it is usually
supported by all devices.
SNMP v1 does not support 64-bit counters.
This may result in invalid data when monitoring traffic via
SNMP.
§ v2c (recommended): Use the more advanced v2c protocol for
SNMP connections. This is the most common SNMP version. Data
is still transferred as clear-text, but it supports 64-bit counters.
§ v3: Use the v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
When using SNMP v3 you can only monitor a limited number of
sensors per second due to internal limitations. 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 limits you to between 60 and 3000 SNMP v3
sensors for each probe. If you experience an increased Interval
Delay or Open Requests with the Probe Healt h Sensor 1484 ,
distribute the load over multiple probes 3359 . SNMP v1 and v2 do not
have this limitation.
Community String This setting is only visible if you select SNMP version v1 or v2c
above. Enter the community string of your devices. This is a kind of
"clear-text password" for simple authentication. We recommend
that you use the default value.
Authentication Type This setting is only visible if you select SNMP version v3 above.
Choose between:
§ MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
§ SHA: Use Secure Hash Algorithm (SHA) for authentication.
The type you choose must match the authentication type of your
device.
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 is used and authentication deactivated
entirely.
12/8/2017 281
User This setting is only visible if you select SNMP version v3 above.
Enter a username for secure authentication. This value must match
the username of your device.
Password This setting is only visible if you select SNMP version v3 above.
Enter a password for secure authentication. This value must match
the password of your device.
Encryption Type This setting is only visible if you select SNMP version v3 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.
AES 192 and AES 256 are not supported by Net-SNMP.
They lack RFC specification.
The type that you choose must match the encryption type of
your device.
Data Encryption Key This setting is only visible if you select SNMP version v3 above.
Enter an encryption key here. If you provide a key in this field,
SNMP data packets are encrypted using the encryption algorithm
selected above, which provides increased security. The key that
you enter here must match the encryption key of your device.
If the key you enter in this field does not match the key
configured on the target SNMP device, you will not get an
error message about this! Please enter a string or leave the field
empty.
Context Name This setting is only visible if you select SNMP version v3 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 for the SNMP communication. We recommend that
you use the default value.
SNMP Timeout (Sec.) Enter a timeout in seconds for the request. If the reply takes
longer than the value you enter here, the request is aborted and
an error message triggered.
282 12/8/2017
PR OXY SETTINGS FOR HTTP SENSOR S
information.
HTTP Proxy Settings The proxy settings determine how a sensor connects to a given
URL. You can enter data for an HTTP proxy server that sensors will
use when connecting via HTTP or HTTPS.
This setting affects monitoring only and determines the
behavior of HTTP sensors. To change proxy settings for the
core server, see Sy st em Administ rat ion—Core & Probes 3108 .
The SSL Cert ificat e Sensor 2424 and the SSL Securit y Check
Sensor 2434 do not support HTTP proxies, but you can configure
connections via SOCKS proxies in their sensor settings.
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.
User If the proxy requires authentication, enter the username for the
proxy login.
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
proxy login.
ACCESS R IGHTS
User Group Access Define which user group(s) will have access to the object that you
are editing. A table with user groups and rights 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.
12/8/2017 283
ACCESS R IGHTS
§ 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 as well as edit access rights.
You can create new user groups in the Sy st em Administ rat ion—
User Groups 3123 settings.
Click the Cont inue button to save your settings. If you leave the current page, all changes to
the settings will be lost!
Auto-Discovery in Progress
While auto-discovery is running you may experience a lower system performance as usual,
because PRTG works in the background to discover your network. Depending on the IP
ranges defined (up to 65,536 addresses), the discovery may run up to several days before it is
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 that
shows the number of active auto-discovery tasks.
§ To stop a running auto-discovery, right-click the group or device, and select Pause | For 5
minut es... from the context menu 234 . PRTG will pause 232 monitoring for 5 minutes and stop
auto-discovery tasks.
Related Topics
§ Creat e Device Templat e 2954
More
Knowledge Base: Why can automatic auto-discoveries evoke performance issues?
284 12/8/2017
Part 7: Ajax Web Interface—Device and Sensor Setup | 2 Create Objects Manually
7.2 Create Objects Manually

We recommend that you use the auto-discovery 267 function to create a basic monitoring setup
for your network. Afterwards, you can manually create devices that could not be discovered,
or arrange 2945 detected devices in groups.
The procedure depends on the kind of object you want to add. Choose between:
§ Add a Group 286
§ Add a Device 295
§ Add a Sensor 309
Add a Remote Probe

See section Mult iple Probes and Remot e Probes 3358 for more information.
11/24/2017 285
1 Add a Group
7.2.1 Add a Group
There are several ways to add a group manually:
§ Select Devices | Add Group from the main menu. An assistant will appear, leading you
through two steps.
§ Hover over and select Add Group from the menu. An assistant will appear, leading you
through two steps.
§ For faster setup, you can select Add Group... in the context menu 234 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
Choose a probe or group you want to add the new group to. Click on Cont inue.
286 11/24/2017
1 Add a Group
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,
11/24/2017 287
1 Add a Group
information.
information.

between:
SSH 3247 .
288 11/24/2017
1 Add a Group
sensor settings.
defined above.
11/24/2017 289
1 Add a Group
default SSH engine.
information.
290 11/24/2017
1 Add a Group
XenServers.
Choose between:
information.
between:
SNMP.
11/24/2017 291
1 Add a Group

Choose between:
device.
entirely.
algorithm.
algorithm.
292 11/24/2017
1 Add a Group
your device.
empty.
ACCESS R IGHTS
User Group Access Define which user group(s) will have access to the object that you
are editing. A table with user groups and rights 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.
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 as well as edit access rights.
11/24/2017 293
1 Add a Group
ACCESS R IGHTS
User Groups 3123 settings.
294 11/24/2017
2 Add a Device
7.2.2 Add a Device
There are several ways to add a device manually:
§ Select Devices | Add Device from the main menu. An assistant will appear, leading you
through two steps.
§ Hover over and select Add Device from the menu. An assistant will appear, leading you
through two steps.
§ For faster setup, you can select Add Device... in the context menu 234 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
Choose a group you want to add the new device to. Click on OK.
11/24/2017 295
2 Add a Device
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.
296 11/24/2017
2 Add a Device
DEVICE NAME AND ADDR ESS
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.
§ Connect using IPv6: Use IP version 6 for all requests to this
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.
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 the space,
comma, or enter key. You can use tags to group sensors and use
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 ): Select this if you want to only
create sensors manually.
Use a small set of auto-discovery templates. This will scan your
LAN and usually create a set of 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.
(s): Use specific auto-discovery templates only. Please select
templates below. This will scan your LAN and add sensors
defined in the template.
11/24/2017 297
2 Add a Device
DEVICE TYPE
Discovery Schedule This option is only visible if you select one of the auto-discovery
options above. Define when the auto-discovery will run. Choose
between:
§ Once: Perform auto-discovery only once. For existing devices,
this will initiate a one-time sensor update for the current device.
If you select this option, you have to start the auto-discovery
manually 268 , it will not run automatically.
§ 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.
Device Template(s) This option is only visible if using specific device templates (last
option) is enabled above. 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
§ Dell EqualLogic
§ Dell MDI Disk
§ DNS Server
§ FTP Server
§ HTTP Web Server
298 11/24/2017
2 Add a Device
DEVICE TYPE

§ NAS LenovoEMC
§ NAS QNAP
§ NAS Sy nology
§ Net App
§ NTP Server
§ Print er (HP)
§ Print er Generic
§ RDP Server
§ Server (Dell)
§ Server Cisco UCS
§ Server IBM
§ SonicWALL
§ Webserver
11/24/2017 299
2 Add a Device
DEVICE TYPE

§ X EN Host s

218 and list the device templates that were actually used to create
new sensors. Templates that were not applied will not be shown in
the ticket.
information.
information.
300 11/24/2017
2 Add a Device

between:
SSH 3247 .
sensor settings.
11/24/2017 301
2 Add a Device
defined above.
default SSH engine.
302 11/24/2017
2 Add a Device
information.
XenServers.
Choose between:
information.
between:
11/24/2017 303
2 Add a Device

SNMP.
Choose between:
device.
entirely.
304 11/24/2017
2 Add a Device
algorithm.
algorithm.
your device.
empty.
11/24/2017 305
2 Add a Device
information.
§ MySQL: 3306
§ Oracle SQL: 1521
§ PostgreSQL: 5432
connect.
306 11/24/2017
2 Add a Device
impersonation.
information.
CloudWatch metrics.
CloudWatch metrics.
11/24/2017 307
2 Add a Device
ACCESS R IGHTS
information.
User Group Access Define which user group(s) will have access to the object you're
editing. A table with user groups and types of access rights 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 access rights settings of the parent object.
object neither shows up in lists nor 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 3123 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 on access rights, see the section User
Access Right s 148 .
308 11/24/2017
3 Add a Sensor
7.2.3 Add a Sensor
There are several ways to add a sensor manually:
§ Select Sensors | Add Sensor from the main menu. An assistant will appear, leading you
through two steps.
§ Hover over and select Add Sensor from the menu. An assistant will appear, leading you
through two steps.
§ For faster setup, you can select Add Sensor... in the context menu 234 of a device to which
you want to add the new sensor. This will skip step 1 and lead you directly to step 2 310 .
§ You can also click the Add Sensor button at the end of a device's sensor list on the device
tree screen or above the Geo Map on the right.
Step 1 - Select Device
Add Sensor Dialog
11/24/2017 309
3 Add a Sensor
§ Select Add sensor t o an exist ing device (default setting).

§ Choose the device you want to add the new sensor to.
§ Click Cont inue.
The add sensor assistant appears.
Step 2 - Choose Sensor Type
Add Sensor Assistant
The add sensor assistant helps you choose the correct sensor (see screenshot above).
§ Narrow down the sensor types:
· Choose appropriate criteria to filter the shown sensor types.
· Enter (parts of) the name into the search box.
· Go through the detailed list of sensors matching the selected device.

· If you cannot find a suitable sensor, search for custom sensors in our PRTG Script World.
Just click Looking For More Sensor Ty pes? below the list of sensor types. See section
List of Available Sensor Types—Script World Sensors 432 .
§ Choose which sensor best monitors the parameters you require.
§ Click the sensor box to select this sensor.
310 11/24/2017
3 Add a Sensor
The sensor settings dialog opens.
§ Enter suitable sensor settings.
PRTG 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
most commonly used sensor types (if enough sensor types are already in use).
If you are unsure which sensor type will provide the information you require, then we
recommend that you use the filter categories to progressively narrow down your
choices.
You can either:
§ Select the type of parameter you want to monitor via Monit or What ?.
§ Specify the type of target system you want to monitor and see what sensors are available
for this type of hardware in Target Sy st em Ty pe?.
§ Choose the technology that you want to use for monitoring (for example SNMP or WMI) in
Technology Used?.
Please also consider whether a sensor’s performance impact is high or low by checking
the bar in the lower left corner of the sensor box. For further information, see this
Knowledge Base article: How to Speed Up PRTG (especially section 4 - Sensor Type and
Monitoring Considerations)
§ Confirm via Cont inue.
PRTG will now create the sensor. The device tree opens.
For more information about a sensor type, see the manual section of the respective
sensor (directly accessible via the question mark (?) symbol in the top-right corner). You
can also go to the List of Available Sensor Ty pes 412 section to find a comprehensive
overview of sensor types.
More
Knowledge Base: How can I change the number of entries in most used sensor types?
Knowledge Base: How to Speed Up PRTG (especially section 4 Sensor Type and Monitoring
Considerations)
11/24/2017 311
Part 7: Ajax Web Interface—Device and Sensor Setup | 3 Manage Device Tree
7.3 Manage Device Tree

While viewing the device tree (or parts of it), click the Management tab to enter a different
tree view that 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 the object. Changes take effect immediately. When done,
leave the Management tab.
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 shadow 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.
Cloned sensors are put to Pause status initially to give you the chance to change any
settings before monitoring begins. Please check the settings 205 and resume 232
monitoring.
You cannot clone fixed objects, such as the root group, a probe device, or PRTG system
internal sensors.
To clone entire groups or devices, please use the Clone Object 2946 functionality
accessible via the objects' Context Menu 234 .
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.
You cannot move the Local Probe, Cloud Probe and Remot e Probes.
312 11/24/2017
Part 7: Ajax Web Interface—Device 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 2950 (Edit Settings) section.
Related Topics
For other ways to arrange objects, see
§ Arrange Object s 2945
§ Creat e Device Templat e 2954
§ Clone Object 2946
11/24/2017 313
Part 7: Ajax Web Interface—Device and Sensor Setup | 4 Root Group Settings
7.4 Root Group Settings

On the Root group's overview page, click 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.
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 the 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.
314 5/30/2017
LOCATION
information.
Location (for Geo When you want to use Geo Maps 2961 , enter a location in the first
Maps) line. Geographical maps will display objects (devices, groups) then
with a flag, showing the current status using a color code similar to
the sensor status icons 183 (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 geo marker will show then the object with
the label in the PRTG geo map.
The preview map will always hava a road map layout regardless
of the map layout you set in User Int erface 3086 .
information.
5/30/2017 315
information.

between:
SSH 3247 .
316 5/30/2017
sensor settings.
defined above.
default SSH engine.
5/30/2017 317
information.
XenServers.
Choose between:
318 5/30/2017
information.
between:
SNMP.
Choose between:
device.
entirely.
5/30/2017 319
algorithm.
algorithm.
your device.
empty.
320 5/30/2017
information.
§ MySQL: 3306
§ Oracle SQL: 1521
§ PostgreSQL: 5432
connect.
5/30/2017 321
impersonation.
information.
CloudWatch metrics.
CloudWatch metrics.
322 5/30/2017
WINDOWS COMPATIBILITY OPTIONS
information.
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:
§ Performance Count ers and fallback t o WMI: Try to query data
via performance counters. If this is not possible, establish a
connection via WMI.
§ Performance Count ers only : Query data via performance
counters only. If this is not possible, a sensor will return no data.
§ WMI only (recommended): Query data via WMI only. If this is not
possible, a sensor will return no data. In current PRTG versions,
this is our recommendation to achieve best performance and
stability.
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 that you use 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. Enter the time the sensor will wait for the return of its WMI
query before aborting with an error message. Please enter an
integer value. The maximum value is 900 seconds (15 minutes).
SNMP COMPATIBILITY OPTIONS
information.
5/30/2017 323
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 that you use 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.
§ 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: 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.
If you experience problems because of strange peaks in your
data graphs, change this option. Peaks might indicate that the
monitored device resets counters without an overflow. PRTG
interprets such a behavior as overflow that results in data peaks.
Choose the option Ignore overflow values in this case. For more
details, see this Knowledge Base article: What is the Overflow
Values setting in the SNMP Compatibility Options?
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.
We recommend that you use the default value. If you experience
problems, change this option.
324 5/30/2017
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.
PRTG uses paging for SNMP requests. This means that if a

sensor has to query more than 20 OIDs, it will automatically
poll the OIDs in packages of 20 OIDs each per request.
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 and 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.
§ [ifdescr]: A textual string containing information about the
monitored device or interface, for example, manufacturer,
product name, version.
5/30/2017 325
§ [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
2265 and SNMP RMON 2205 sensors.
Combine them as you like to obtain suitable sensor names.

For more information about SNMP sensor names, see this
Knowledge Base article: How can I change the defaults for
names automatically generated for new SNMP sensors?
Port Name Update Define how PRTG will react if you change port names in your
physical device (for example, 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 more information about automatic updates of names, see
this Knowledge Base article: Automatically update port name
and number for SNMP Traffic sensors when the device changes
them
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.
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.
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.
returns unique interface names in the ifName field.
326 5/30/2017
§ No Port Updat e: Use this option to disable automatic port

identification.
Start Interface Index For SNMP Traffic sensors 2265 , define at which index PRTG will start
to query the interface range during sensor creation. Use 0 for
automatic mode. We recommend that you use the default value.
End Interface Index For SNMP Traffic sensors 2265 , define at which index PRTG will stop
information.
proxy login.
proxy login.
5/30/2017 327
SCANNING INTER VAL
information.
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 3096 on PRTG on premises installations.
If a Sensor Query Fails Define the number of scanning intervals that a sensor has time
reach and check a device again in case a sensor query fails. The
sensor can try to re-reach and check a device several times,
depending on the option you select here, before it will be set to a
Down status 183 . This helps you 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 immediately 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 continuously failed
requests.
Show an error status only after four continuously failed
requests.
Show an error status only after five continuously failed requests.
Show an error status only after six continuously failed requests.
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 to "down" immediately, so the first option will not apply to
these sensor types. All other options can apply.
If a sensor has defined error limits for channels, it will always
show a Down status immediately, so no "wait" option will
apply.
328 5/30/2017
SCANNING INTER VAL
If a channel uses lookup 3345 values, it will always show a Down

status immediately, so no "wait" options will apply.
SCHEDU LES, DEPENDENCIES, AND MAINTENANCE WINDOW
information.
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 3057 .
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.
To terminate a current maintenance window before the
defined end date, you can change the time in Maint enance
Ends field to a date in the past.
Maintenance Begins 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 Ends 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 334 , Group Settings 358 , Device
Settings 385 , and Sensor Settings 411 .
5/30/2017 329
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
330 5/30/2017
CHANNEL U NIT CONFIGU R ATION
information.
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
Custom channel types can be set on sensor level only.
ADVANCED NETWOR K ANALYSIS
information.
Unusual Detection Define if you want to benefit from unusual detection 3097 for
sensors. You can configure the behavior of unusual detection (or
disable it completely) in the system settings 3097 . Choose between:
§ Enabled: Activate unusual detection for this object and, by
default, for all objects underneath in the hierarchy 125 of the
device tree. Sensors affected by this setting will turn to orange
color (unusual sensor status 183 ) if PRTG detects unusual activity.
§ Disabled: Do not activate unusual detection. PRTG will ignore
unusual values for sensors affected by this setting. These sensor
will not show an unusual sensor status.
Similar Sensors Define if you want to activate Similar Sensors 197 analysis. You can
Detection configure the depth of analysis of similar sensors detection (or
§ Enabled: Activate similar sensors detection for this object and,
by default, for all objects underneath in the hierarchy 125 of the
device tree. PRTG considers all sensors affected by this setting
during similarity analysis.
5/30/2017 331
§ Disabled: Do not activate similar sensors detection. PRTG will

not consider sensors affected by this setting during similarity
analysis.
System Information Define if you want to retrieve and show Sy st em Informat ion 210
for your devices. Choose between:

§ Enabled: Activate the system information feature for this object
and, by default, for all objects underneath in the hierarchy 125 of
the device tree.
§ Disabled: Do not activate system information.
Sy st em Informat ion is enabled by default. To retrieve the

data, PRTG will automatically use Credent ials for Windows
Sy st ems and Credent ials for SNMP Devices as defined in
the device settings 385 or as inherited 125 from a parent object like
the Root group. Please consider this when you monitor devices
outside the local network, especially when using SNMP v1 or v2c
that do not provide encryption.
This setting is not available on the Cloud Probe of a PRTG in

the cloud instance.
Notifications
configure external alerting tailored to your needs. In an object's detail page, click the
Not ificat ions tab to change sensor notification triggers. The defined triggers will be inherited
down to sensor level. For detailed information, see Sensor Not ificat ions Set t ings 2924
section.
Others
For more general information about settings, see Object Set t ings 205 section.
More
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
332 5/30/2017
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
Knowledge Base: What is the Overflow Values setting in the SNMP Compatibility Options?
5/30/2017 333
Part 7: Ajax Web Interface—Device and Sensor Setup | 5 Probe Settings
7.5 Probe Settings

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

You can add additional remote probes to your setup to extend your monitoring to networks
that are not directly reachable by your PRTG core installation or cluster.
See section Add Remot e Probe 3358 for more details.
Probe Settings
The following settings are available in the Set t ings tab of every probe. Because you may not
need all of these for every probe, just regard the settings you really need, ignoring the others.
We recommend that you define as many settings as possible in the Root 314 group, so you can
inherit them to all other objects further down in the device tree hierarchy 125 .
BASIC PR OBE SETTINGS
Probe Name Enter a meaningful name to identify the probe. The name will be
Tags Enter one or more Tags 131 . Confirm each tag by hitting the space,
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).
334 8/10/2017
Inherited Settings
LOCATION
information.
49.452778 any 11.077778 text
following.
information.
8/10/2017 335
information.

between:
SSH 3247 .
336 8/10/2017
sensor settings.
defined above.
8/10/2017 337
default SSH engine.
information.
338 8/10/2017

XenServers.
Choose between:
information.
between:
SNMP.
8/10/2017 339

Choose between:
device.
entirely.
algorithm.
algorithm.
340 8/10/2017
your device.
empty.
information.
8/10/2017 341

§ MySQL: 3306
§ Oracle SQL: 1521
§ PostgreSQL: 5432
connect.
impersonation.
342 8/10/2017
information.
CloudWatch metrics.
CloudWatch metrics.
information.
Choose between:
connection via WMI.
8/10/2017 343
stability.
value.
information.
failures.
344 8/10/2017

earlier.
peaks.
data.
device.
8/10/2017 345

into one request.

among which are:
bandwidth (KBit/s).

346 8/10/2017

them
Choose between:
ifAlias available.

identification.
8/10/2017 347
information.
proxy login.
proxy login.
SCANNING INTER VAL
information.
348 8/10/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

8/10/2017 349
CLU STER U SAGE
information.
Scanning Distribution This box is only visible if you run 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 129 to
all objects underneath.
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.

between:
be set.
maintenance window.
350 8/10/2017
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:
§ 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.
You do not trigger a status change by dependency if you
manually pause a master object or if you pause it by schedule.
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 2959 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 228
to choose an object on which the current object will be
dependent on.
Dependency Delay This field is only visible if you select another object than the parent
(Sec.) as dependency type. Define a time span in seconds for
dependency delay.
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.
8/10/2017 351
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
352 8/10/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
information.
8/10/2017 353

analysis.

the device tree.


the cloud instance.
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 PRTG will use for outgoing monitoring requests of certain sensor types.
§ This setting will be used for sensors using the following connection types: HTTP, DNS, FTP,
IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP.
§ The setting is valid for all monitoring requests sent from this PRTG probe.
§ This setting is useful for devices that expect a certain IP address when queried.
§ Default setting is aut o. PRTG will select an IP address automatically.
This feature does not support all sensor types for technical reasons.
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.
354 8/10/2017
PR OBE SETTINGS FOR MONITOR ING
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.
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, see the
IPv6 153 section.
Cluster Connectivity This box is only visible if you run a PRTG cluster. Define if this
probe connects to all cluster nodes, including the failover nodes,
or only to the primary master node. Choose between:
§ Probe sends dat a only t o primary mast er node: The probe
connects only to the primary master node. You are not able to
review monitoring data on failover nodes. Consider to choose
this option if you have bandwidth limitations in your network or
if the probe cannot access your failover node(s).
§ Probe sends dat a t o all clust er nodes: This is the default
option. The probe connects to all nodes in your cluster and
sends monitoring data to the failover node(s) in addition to the
primary master. The probe is visible on all your nodes as soon as
it connects automatically to the correct IP addresses and ports
of the failover nodes. If your master node fails, you can still see
monitoring data of this probe.
PRTG will not notify you if a remote probe is disconnected
from a cluster node. Please check explicitly on a cluster node if
your remote probes are connected (for example, via the device
tree in the PRTG web interface on a cluster node).
SCHEDU LED R ESTAR T SETTINGS
This setting is not available on the Cloud Probe of a PRTG in the cloud instance.
Restart Options For best performance, we recommend that you 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:
8/10/2017 355
SCHEDU LED R ESTAR T SETTINGS
§ No scheduled reboot or 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 Administ rat ion—
Administ rat ive Tools 3128 in the PRTG web interface.
§ Scheduled rest art of PRTG services: Restart all PRTG services
on the system where this probe runs on. If you choose this
option on the local probe, the PRTG core server will restart as
well. Define a schedule below.
§ Scheduled sy st em reboot (recommended): We recommend
this setting, although it is not set by default. Enter a schedule
below. We recommend that you restart Windows servers once a
month for best performance.
Restart Schedule You can only see this setting 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 day of the week and a time below.
§ Once per mont h (recommended): Select a day of the month
and a time below.
Specify Day You can only see this setting if you selected a schedule option
above. Select a specific day of a week (Monday to Sunday) or
month (1st to 30th or 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.
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.
Specify Hour You can only see this setting if you selected a schedule option
above. Select the time of day when PRTG will perform the restart.
You will get a Windows warning message 10 minutes before
the restart to inform you if you are a currently logged in user.
The actual restart time can differ up to 30 minutes from the
settings you enter here.
356 8/10/2017
Notifications
section.
Others
More
SNMP sensors?
8/10/2017 357
Part 7: Ajax Web Interface—Device and Sensor Setup | 6 Group Settings
7.6 Group Settings

On a group's overview page, click 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 the settings you really need, ignoring the others.
This documentation does not refer to the setting of the special Root group. The settings
available there differ from those described here.
BASIC GR OU P SETTINGS
Status Choose if monitoring for this group is started or paused. .We

recommend that you use 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.
Parent Tags Shows Tags 131 that this group inherits 131 from its parent probe 125
. This setting is shown for your information only and cannot be

changed here.
358 11/24/2017
BASIC GR OU P SETTINGS
Tags Enter one or more Tags 131 . Confirm each tag by hitting the space,
tag–filtered views later on. Tags are not case sensitive.
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:
§ Manual (no aut o-discovery ): Do not auto-discover any sensors,
only add sensors manually.
sensors: Use an extended set of auto-discovery templates. This
device.
§ Aut omat ic sensor creat ion using specific device t emplat es:
Use specific auto-discovery templates only. Select templates
below. This will scan your LAN and add sensors defined in the
template.
Device Template(s) This option is only visible if you enable using specific device
templates above. 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. PRTG will use the selected templates for auto-discovery on
the current device. Choose from:
§ ADSL
§ Cisco ASA VPN
11/24/2017 359
§ Dell EqualLogic
§ Dell MDI Disk
§ DNS Server
§ FTP Server
§ HTTP Web Server
§ NAS LenovoEMC
§ NAS QNAP
§ NAS Sy nology
§ Net App
§ NTP Server
§ Print er (HP)
§ Print er Generic
§ RDP Server
§ Server (Dell)
§ Server Cisco UCS
§ Server IBM
§ SonicWALL
360 11/24/2017

§ Webserver
§ X EN Host s

218 and list the device templates that it used to create new
sensors. The ticket will not show templates that were not applied.
Discovery Schedule Define when PRTG will run the auto-discovery. Choose between:
§ Once: Perform auto-discovery only once. PRTG will add new
devices and sensors once. If you select this option, you have to
start the auto-discovery manually 268 , it will not run automatically.
§ Hourly : Perform auto-discovery for new devices and sensors
every 60 minutes.
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
The Discovery Schedule will be set to Once on all devices
created by the scheduled auto-discovery for performance
reasons.
11/24/2017 361
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.
§ 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.
Define your active directory domain in advance in the system
administration.
See Sy st em Administ rat ion—Core & Probes 3112 .
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 you select Class C network detection
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 you select Class C network detection
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 you select Class C network detection
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 you select the IP list option above. Enter a
IPv6/DNS Name List list of IP addresses or DNS names that the auto-discovery will scan.
Enter each address in a separate line.
362 11/24/2017
IPv4 and Subnet (IPv4) This field is only visible if you select the IP and subnet option
above. Enter an expression in the format address/subnet , for
example, 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 you select the octet range option 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. For example, 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 you select active directory above. Enter
an organizational unit (OU) to restrict the active directory search to
computers that are part of this OU. Just enter the name of the OU
without any other term (so without "OU" in front). If you leave this
field empty, there will not be any restriction.
Make sure that the OU contains a host. If the OU is empty, you

will receive an error message.
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
The order is important, sub-OUs have to be listed left of their
particular parents!
Name Resolution Define how to monitor newly discovered devices. This affects only
new devices. The setting for existing devices will remain
unchanged. Depending on your selection the IP Address/DNS
Name field of an added device 385 shows the DNS name or IP
address that PRTG uses to access the target device. Choose
between:
§ Use DNS names (recommended): Monitor newly discovered
devices via their DNS names (if available).
§ Use IP addresses: Monitor newly discovered devices via their IP
address.
This setting does not affect how PRTG shows the devices in
the device tree.
11/24/2017 363
Device Rescan Define if you want to add devices that already exist in your PRTG
installation also to the currently selected group. Choose between:
§ Skip aut o-discovery for known devices/IPs (recommended):
Do not re-scan known devices or IP addresses, only add devices
with new IPs or DNS names when auto-discovering. PRTG will not
add devices that are already included elsewhere in your
configuration, for example, in other groups.
§ Perform aut o-discovery for known devices/IPs: Re-scan
devices with known IP addresses with every auto-discovery. This
option will add devices that already exist in other groups also to
this group and runs the auto-discovery on the newly added
devices.
The auto-discovery will not run on devices that already exist
in this group. If you want to run the auto-discovery for an
existing device, you have to start the auto-discovery on this
device.
Inherited Settings
LOCATION
information.
49.452778 any 11.077778 text
following.
364 11/24/2017
LOCATION
information.
information.

between:
11/24/2017 365

SSH 3247 .
sensor settings.
366 11/24/2017

defined above.
default SSH engine.
11/24/2017 367
information.
XenServers.
Choose between:
information.
between:
368 11/24/2017

SNMP.
Choose between:
device.
entirely.
11/24/2017 369
algorithm.
algorithm.
your device.
empty.
370 11/24/2017
information.
§ MySQL: 3306
§ Oracle SQL: 1521
§ PostgreSQL: 5432
connect.
11/24/2017 371
impersonation.
information.
CloudWatch metrics.
CloudWatch metrics.
372 11/24/2017
information.
Choose between:
connection via WMI.
stability.
value.
information.
11/24/2017 373
failures.
earlier.
peaks.
data.
374 11/24/2017
device.
into one request.

among which are:
11/24/2017 375

bandwidth (KBit/s).

them
Choose between:
ifAlias available.
376 11/24/2017

identification.
information.
proxy login.
proxy login.
11/24/2017 377
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.
378 11/24/2017
SCANNING INTER VAL

CLU STER U SAGE
information.

objects' settings.

between:
be set.
11/24/2017 379

maintenance window.
maintenance window.

can choose between:

menu bar.
dependent on.
dependency delay.
380 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 381
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
information.
382 11/24/2017

analysis.

the device tree.


the cloud instance.
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 in
this limitation. If the amount of sensors exceeds the limitation,
surplus sensors will be paused 232 . This is of special interest for a
Managed Service Provider (MSP). Choose between:
§ Allow unlimit ed number of sensors: Do not limit the number of
sensors for this group. Any number of sensors can be added to
this group and its subgroups.
§ Limit number of sensors in t his group: Enable a limitation for
the number of sensors in this group. Only a defined number of
sensors can monitor in this group and its subgroups.
Maximum Number of This field is only visible if you enable limitation above. Define how
Sensors many sensors are allowed in this group and its subgroups. Sensors
that exceed this group sensor limit will be paused. Please enter an
integer value.
11/24/2017 383
NU MBER OF SENSOR S LIMITATION
Sensors in paused status 183 count for this group limit as well
(for example, manually paused sensors, sensors paused by
dependency or schedule), but not for the number of available
sensors in your license.
Manually paused sensors will override the sensor message
"exceeds group sensor limit".
Notifications
section.
Others
More
SNMP sensors?
384 11/24/2017
Part 7: Ajax Web Interface—Device and Sensor Setup | 7 Device Settings
7.7 Device Settings

On the details page of a device, click the Set t ings tab to change settings.
Add Device
The Add Device dialog appears when you add a new device to a group. It only shows the
setting fields that are imperative for creating the device in PRTG. Because of this, 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 Set t ings tab of the device later.
Device Settings
The following settings are available in the Set t ings tab of every device. Because you do not
need all of these for every device, depending on the device type, just define the settings you
really need and ignore the others.
For device settings, there is also multi-edit available. This enables you to change the properties
of many devices at a time.
For more details, see Mult i-Edit List s 2949 section.
BASIC DEVICE SETTINGS
Device Name Enter a meaningful name to identify the device. PRTG shows this
name by default in the device tree 170 and in all Alarms 207 and
Not ificat ions 2966 .
Status Define the activity status of the device. Choose between:

§ St art ed: Monitor this device.
§ Paused: Pause monitoring for this device. All sensors on it are in
status 183 Paused until you change this setting again.
11/24/2017 385
BASIC DEVICE SETTINGS
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:
§ IPv4 device: Use IP version 4 for all requests to this device.
§ IPv6 device: Use IP version 6 for all requests to this 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 you create on
this device will inherit this setting and try connecting to this
address for monitoring.
Some sensor types have their own setting for IP address/DNS
name to which they connect.
Parent Tags Shows Tags 131 that this device inherits 131 from its parent group
and probe 125 . This setting is shown for your information only and
cannot be changed here.
Tags Enter one or more Tags 131 . Confirm each tag by with the space,
comma, or enter key. Sensors on this device inherit these tags.
You can use tags to group sensors and tag–filtered views, for
example, in Libraries 2984 . Tags are not case sensitive. We
recommend that you use the default value. You can add additional
tags to it, if you like.
Priority Select a priority 229 for the device. This setting determines the
order in which your devices are displayed when you view table
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. PRTG shows it in the device
tree.
For information on how to add your custom icons to PRTG on
premises instances, see this article in the Knowledge Base:
How can I add my own device icons for use in the PRTG web
interface?
386 11/24/2017
ADDITIONAL DEVICE INFOR MATION
Service URL Specify a URL you would like to open directly when you select
Device Tools | Go To Service URL from the context menu 241 of
the device. 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:
§ Manual (no aut o-discovery ): Select this if you want to only
create sensors manually.
sensors): Use an extended set of auto-discovery templates. This
device.
(s): 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 you select one of the auto-discovery
options above. Define when the auto-discovery will run. Choose
between:
§ Once: Perform auto-discovery only once. For existing devices,
this will initiate a one-time sensor update for the current device.
If you select this option, you have to start the auto-discovery
manually 268 , it will not run automatically.
§ 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.
11/24/2017 387
DEVICE TYPE
Device Template(s) This option is only visible if using specific device templates (last
option) is enabled above. 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
§ Dell EqualLogic
§ Dell MDI Disk
§ DNS Server
§ FTP Server
§ HTTP Web Server
§ NAS LenovoEMC
§ NAS QNAP
§ NAS Sy nology
§ Net App
§ NTP Server
388 11/24/2017
DEVICE TYPE
§ Print er (HP)
§ Print er Generic
§ RDP Server
§ Server (Dell)
§ Server Cisco UCS
§ Server IBM
§ SonicWALL
§ Webserver
§ X EN Host s

218 and list the device templates that were actually used to create
new sensors. Templates that were not applied will not be shown in
the ticket.
11/24/2017 389
Inherited Settings
LOCATION
information.
49.452778 any 11.077778 text
following.
information.
390 11/24/2017
information.

between:
SSH 3247 .
11/24/2017 391
sensor settings.
defined above.
392 11/24/2017
default SSH engine.
information.
11/24/2017 393

XenServers.
Choose between:
information.
between:
SNMP.
394 11/24/2017

Choose between:
device.
entirely.
algorithm.
algorithm.
11/24/2017 395
your device.
empty.
information.
396 11/24/2017

§ MySQL: 3306
§ Oracle SQL: 1521
§ PostgreSQL: 5432
connect.
impersonation.
11/24/2017 397
information.
CloudWatch metrics.
CloudWatch metrics.
information.
Choose between:
connection via WMI.
398 11/24/2017
stability.
value.
information.
failures.
11/24/2017 399

earlier.
peaks.
data.
device.
400 11/24/2017

into one request.

among which are:
bandwidth (KBit/s).

11/24/2017 401

them
Choose between:
ifAlias available.

identification.
402 11/24/2017
information.
proxy login.
proxy login.
SCANNING INTER VAL
information.
11/24/2017 403
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

404 11/24/2017
CLU STER U SAGE
information.

objects' settings.

between:
be set.
maintenance window.
11/24/2017 405
maintenance window.

can choose between:

menu bar.
dependent on.
dependency delay.
406 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 407
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
information.
408 11/24/2017

analysis.

the device tree.


the cloud instance.
Notifications
section.
Others
More
11/24/2017 409
SNMP sensors?
410 11/24/2017
Part 7: Ajax Web Interface—Device and Sensor Setup | 8 Sensor Settings
7.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, see the List of Available Sensors 412 .
For sensor settings, there is also multi-edit available. This enables you to change
properties of many sensors at a time. For more details, see section Mult i-Edit List s 2949 .
To detect unexpected correlations between your network components, PRTG provides a

Similar Sensors 197 analysis.
Sensor Settings Overview

For information about sensor settings, see the following sections:
§ Sensor Set t ings— 411 List of Available Sensor Ty pes 412
§ Addit ional Sensor Ty pes (Cust om Sensors) 2911
§ Sensor Channels Set t ings 2915
§ Sensor Not ificat ions Set t ings 2924
11/24/2017 411
1 List of Available Sensor Types
7.8.1 List of Available Sensor Ty pes
This chapter lists all available sensors, arranged both by different categories and in alphabetical
order.
In the Add a Sensor 309 assistant, PRTG offers you various options to easily filter for fitting
sensor types.
§ Common Sensors 412
§ Bandwidth Monitoring Sensors 413
§ Web Servers (HTTP) Sensors 413
§ SNMP Sensors 414
§ Windows WMI/Performance Counters Sensors 416
§ Linux/Unix/OS X Sensors 417
§ Virtual Servers Sensors 418
§ Mail Servers Sensors 418
§ Database Servers Sensors 419
§ Storage and File Servers Sensors 419
§ Various Servers Sensors 421
§ VoIP and QoS Sensors 421
§ Hardware Parameters Sensors 422
§ Cloud Services Sensors 423
§ Custom Sensors 424
§ PRTG Internal Sensors 424
§ All Sensors in Alphabetical Order 425
§ Script World Sensors 432
§ More 434
Common Sensors
§ Cloud HTTP Sensor 597
§ Cloud Ping Sensor 606
§ HTTP Sensor 875
§ Ping Sensor 1424
§ Port Sensor 1451
§ Port Range Sensor 1461
§ SNMP Traffic Sensor 2265
§ SSL Certificate Sensor 2424
412 11/24/2017
§ SSL Security Check Sensor 2434
§ Windows Network Card Sensor 2577
Bandwidth Monitoring Sensors

§ IPFIX Sensor 1090
§ IPFIX (Custom) Sensor 1104
§ jFlow V5 Sensor 1126
§ jFlow V5 (Custom) Sensor 1140
§ NetFlow V5 Sensor 1299
§ NetFlow V5 (Custom) Sensor 1313
§ NetFlow V9 Sensor 1326
§ Packet Sniffer Sensor 1379
§ Packet Sniffer (Custom) Sensor 1392
§ sFlow Sensor 1589
§ sFlow (Custom) Sensor 1603
§ SNMP Cisco ADSL Sensor 1681
§ SNMP Cisco ASA VPN Traffic Sensor 1699
§ SNMP Library Sensor 2044
§ SNMP NetApp Network Interface Sensor 2147
§ SNMP RMON Sensor 2205
Web Servers (HTTP) Sensors

§ Cloud HTTP Sensor 597
§ Common SaaS Sensor 620
§ HTTP Sensor 875
§ HTTP Advanced Sensor 885
§ HTTP Apache ModStatus PerfStats Sensor 901
§ HTTP Apache ModStatus Totals Sensor 911
§ HTTP Content Sensor 921
§ HTTP Data Advanced Sensor 933
§ HTTP Full Web Page Sensor 946
§ HTTP Push Count Sensor 957
11/24/2017 413
§ HTTP Push Data Sensor 966
§ HTTP Push Data Advanced Sensor 977
§ HTTP Transaction Sensor 988
§ HTTP XML/REST Value Sensor 1002
§ REST Custom Sensor 1538
§ SSL Certificate Sensor 2424
§ Windows IIS Application Sensor 2557
SNMP Sensors
§ SNMP APC Hardware Sensor 1664
§ SNMP Buffalo TS System Health Sensor 1673
§ SNMP Cisco ADSL Sensor 1681
§ SNMP Cisco ASA VPN Connections Sensor 1689
§ SNMP Cisco ASA VPN Traffic Sensor 1699
§ SNMP Cisco ASA VPN Users Sensor 1710
§ SNMP Cisco CBQoS Sensor 1720
§ SNMP Cisco System Health Sensor 1729
§ SNMP Cisco UCS Blade Sensor 1738
§ SNMP Cisco UCS Chassis Sensor 1746
§ SNMP Cisco UCS Sensor 1755
§ SNMP Cisco UCS System Health Sensor 1763
§ SNMP CPU Load Sensor 1771
§ SNMP Custom Sensor 1779
§ SNMP Custom Advanced Sensor 1788
§ SNMP Custom String Sensor 1798
§ SNMP Custom String Lookup Sensor 1810
§ SNMP Custom Table Sensor 1820
§ SNMP Dell EqualLogic Logical Disk Sensor 1832
§ SNMP Dell EqualLogic Member Health Sensor 1841
§ SNMP Dell EqualLogic Physical Disk Sensor 1851
§ SNMP Dell Hardware Sensor 1860
§ SNMP Dell PowerEdge Physical Disk Sensor 1869
§ SNMP Dell PowerEdge System Health Sensor 1879
414 11/24/2017
§ SNMP Disk Free Sensor 1889
§ SNMP Hardware Status Sensor 1897
§ SNMP HP BladeSystem Server Blade Sensor 1905
§ SNMP HP BladeSystem System Health Sensor 1913
§ SNMP HP LaserJet Hardware Sensor 1921
§ SNMP HP ProLiant Logical Disk Sensor 1930
§ SNMP HP ProLiant Memory Controller Sensor 1939
§ SNMP HP ProLiant Network Interface Sensor 1948
§ SNMP HP ProLiant Physical Disk Sensor 1957
§ SNMP HP ProLiant System Health Sensor 1966
§ SNMP IBM System X Logical Disk Sensor 1975
§ SNMP IBM System X Physical Disk Sensor 1984
§ SNMP IBM System X Physical Memory Sensor 1993
§ SNMP IBM System X System Health Sensor 2002
§ SNMP interSeptor Pro Environment Sensor 2011
§ SNMP Juniper System Health Sensor 2019
§ SNMP LenovoEMC Physical Disk Sensor 2027
§ SNMP LenovoEMC System Health Sensor 2036
§ SNMP Linux Disk Free Sensor 2058
§ SNMP Linux Load Average Sensor 2069
§ SNMP Linux Meminfo Sensor 2077
§ SNMP Linux Physical Disk Sensor 2085
§ SNMP Memory Sensor 2094
§ SNMP NetApp Disk Free Sensor 2103
§ SNMP NetApp Enclosure Sensor 2112
§ SNMP NetApp I/O Sensor 2121
§ SNMP NetApp License Sensor 2130
§ SNMP NetApp Logical Unit Sensor 2138
§ SNMP NetApp System Health Sensor 2155
§ SNMP Poseidon Environment Sensor 2164
§ SNMP Printer Sensor 2172
§ SNMP QNAP Logical Disk Sensor 2180
11/24/2017 415
§ SNMP QNAP Physical Disk Sensor 2188
§ SNMP QNAP System Health Sensor 2197
§ SNMP RMON Sensor 2205
§ SNMP SonicWALL System Health Sensor 2216
§ SNMP SonicWALL VPN Traffic Sensor 2224
§ SNMP Synology Logical Disk Sensor 2233
§ SNMP Synology Physical Disk Sensor 2241
§ SNMP Synology System Health Sensor 2249
§ SNMP System Uptime Sensor 2257
§ SNMP Trap Receiver Sensor 2277
§ SNMP Windows Service Sensor 2290
Windows WMI/Performance Counters Sensors

§ Active Directory Replication Errors Sensor 435
§ Event Log (Windows API) Sensor 703
§ PerfCounter Custom Sensor 1404
§ PerfCounter IIS Application Pool Sensor 1414
§ Windows IIS 6.0 SMTP Received Sensor 2539
§ Windows IIS 6.0 SMTP Sent Sensor 2548
§ Windows IIS Application Pool Sensor 1414
§ Windows CPU Load Sensor 2529
§ Windows MSMQ Queue Length Sensor 2566
§ Windows Pagefile Sensor 2588
§ Windows Physical Disk I/O Sensor 2597
§ Windows Print Queue Sensor 2607
§ Windows Process Sensor 2618
§ Windows System Uptime Sensor 2628
§ Windows Updates Status (Powershell) Sensor 2637
§ WMI Custom Sensor 2647
§ WMI Custom String Sensor 2657
§ WMI Event Log Sensor 2669
§ WMI Exchange Server Sensor 2680
416 11/24/2017
§ WMI Exchange Transport Queue Sensor 2690
§ WMI File Sensor 2700
§ WMI Free Disk Space (Multi Disk) Sensor 2709
§ WMI HDD Health Sensor 2721
§ WMI Logical Disk I/O Sensor 2731
§ WMI Memory Sensor 2740
§ WMI Microsoft SQL Server 2005 Sensor 2749
§ WMI Remote Ping Sensor 2810
§ WMI Security Center Sensor 2819
§ WMI Service Sensor 2829
§ WMI Share Sensor 2839
§ WMI SharePoint Process Sensor 2849
§ WMI Terminal Services (Windows 2008+) Sensor 2858
§ WMI Terminal Services (Windows XP/Vista/2003) Sensor 2866
§ WMI UTC Time Sensor 2874
§ WMI Vital System Data (V2) Sensor 2882
§ WMI Volume Sensor 2892
§ WSUS Statistics Sensor 2901
Linux/Unix/OS X Sensors
§ Python Script Advanced Sensor 1491
§ SNMP Linux Load Average Sensor 2069
§ SNMP Linux Meminfo Sensor 2077
§ SSH Disk Free Sensor 2305
§ SSH INodes Free Sensor 2318
§ SSH Load Average Sensor 2328
§ SSH Meminfo Sensor 2337
§ SSH Remote Ping Sensor 2346
11/24/2017 417
§ SSH Script Sensor 2399
§ SSH Script Advanced Sensor 2412
§ SSH SAN Enclosure Sensor 2356
§ SSH SAN Logical Disk Sensor 2367
§ SSH SAN Physical Disk Sensor 2378
§ SSH SAN System Health Sensor 2389
Virtual Servers Sensors

§ Citrix XenServer Host Sensor 577
§ Citrix XenServer Virtual Machine Sensor 587
§ Docker Container Status Sensor 673
§ Enterprise Virtual Array Sensor 693
§ Hyper-V Cluster Shared Volume Disk Free Sensor 1017
§ Hyper-V Host Server Sensor 1028
§ Hyper-V Virtual Machine Sensor 1037
§ Hyper-V Virtual Network Adapter Sensor 1048
§ Hyper-V Virtual Storage Device Sensor 1058
§ VMware Datastore (SOAP) Sensor 2479
§ VMware Host Hardware (WBEM) Sensor 2490
§ VMware Host Hardware Status (SOAP) Sensor 2499
§ VMware Host Performance (SOAP) Sensor 2509
§ VMware Virtual Machine (SOAP) Sensor 2519
Mail Servers Sensors

§ Exchange Backup (Powershell) Sensor 713
§ Exchange Database (Powershell) Sensor 722
§ Exchange Database DAG (Powershell) Sensor 733
§ Exchange Mail Queue (Powershell) Sensor 743
§ Exchange Mailbox (Powershell) Sensor 753
§ Exchange Public Folder (Powershell) Sensor 763
§ IMAP Sensor 1067
§ IP on DNS Blacklist Sensor 1081
§ POP3 Sensor 1442
§ SMTP Sensor 1633
§ SMTP&IMAP Round Trip Sensor 1642
418 11/24/2017
§ SMTP&POP3 Round Trip Sensor 1653
§ WMI Exchange Server Sensor 2680
§ WMI Exchange Transport Queue Sensor 2690
§ Windows IIS 6.0 SMTP Received Sensor 2539
§ Windows IIS 6.0 SMTP Sent Sensor 2548
Database Servers Sensors

§ MySQL v2 Sensor 1187
§ Oracle Tablespace Sensor 1369
§ PostgreSQL Sensor 1469
Storage and File Servers Sensors

§ Dell PowerVault MDi Logical Disk Sensor 635
§ Dell PowerVault MDi Physical Disk Sensor 644
§ File Sensor 796
§ File Content Sensor 805
§ Folder Sensor 815
§ FTP Sensor 825
§ FTP Server File Count Sensor 834
§ Hyper-V Cluster Shared Volume Disk Free Sensor 1017
§ Hyper-V Virtual Storage Device Sensor 1058
§ NetApp Aggregate Sensor 1203
§ NetApp I/O Sensor 1214
§ NetApp LIF Sensor 1225
§ NetApp LUN Sensor 1235
11/24/2017 419
§ NetApp NIC Sensor 1246
§ NetApp Physical Disk Sensor 1256
§ NetApp SnapMirror Sensor 1266
§ NetApp System Health Sensor 1277
§ NetApp Volume Sensor 1288
§ SFTP Secure File Transfer Protocol Sensor 1615
§ Share Disk Free Sensor 1562
§ SNMP Cisco UCS Physical Disk Sensor 1755
§ SNMP HP ProLiant Logical Disk Sensor 1930
§ SNMP IBM System X Logical Disk Sensor 1975
§ SNMP NetApp Disk Free Sensor 2103
§ SNMP NetApp License Sensor 2130
§ SNMP QNAP Logical Disk Sensor 2180
§ SNMP Synology Logical Disk Sensor 2233
420 11/24/2017
§ TFTP Sensor 2462
§ VMware Datastore (SOAP) Sensor 2479
§ Windows Physical Disk I/O Sensor 2597
§ WMI File Sensor 2700
§ WMI Free Disk Space (Multi Disk) Sensor 2709
§ WMI Logical Disk I/O Sensor 2731
§ WMI Volume Sensor 2892
Various Servers Sensors

§ DHCP Sensor 654
§ DNS Sensor 664
§ IPMI System Health Sensor 1116
§ LDAP Sensor 1153
§ Ping Sensor 1424
§ Ping Jitter Sensor 1433
§ Port Sensor 1451
§ Port Range Sensor 1461
§ RADIUS v2 Sensor 1520
§ RDP (Remote Desktop) Sensor 1530
§ SNMP Trap Receiver Sensor 2277
§ SNTP Sensor 2298
§ Syslog Receiver Sensor 2443
§ Traceroute Hop Count Sensor 2470
VoIP and QoS Sensors

§ Cisco IP SLA Sensor 568
§ SIP Options Ping Sensor 1624
§ QoS (Quality of Service) One Way Sensor 1501
§ QoS (Quality of Service) Round Trip Sensor 1510
§ SNMP Cisco CBQoS Sensor 1720
11/24/2017 421
Hardware Parameter Sensors

§ Dell PowerVault MDi Logical Disk Sensor 635
§ Dell PowerVault MDi Physical Disk Sensor 644
§ NetApp Aggregate Sensor 1203
§ NetApp I/O Sensor 1214
§ NetApp LIF Sensor 1225
§ NetApp LUN Sensor 1235
§ NetApp NIC Sensor 1246
§ NetApp Physical Disk Sensor 1256
§ NetApp SnapMirror Sensor 1266
§ NetApp System Health Sensor 1277
§ NetApp Volume Sensor 1288
§ SNMP APC Hardware Sensor 1664
§ SNMP Cisco System Health Sensor 1729
§ SNMP Cisco UCS Blade Sensor 1738
§ SNMP Cisco UCS Chassis Sensor 1746
§ SNMP Cisco UCS Physical Disk Sensor 1755
§ SNMP Cisco UCS System Health Sensor 1763
§ SNMP CPU Load Sensor 1771
§ SNMP Dell Hardware Sensor 1860
§ SNMP Dell PowerEdge System Health Sensor 1879
§ SNMP Disk Free Sensor 1889
§ SNMP Hardware Status Sensor 1897
§ SNMP HP BladeSystem Blade Sensor 1905
§ SNMP HP BladeSystem Enclosure System Health Sensor 1913
§ SNMP HP LaserJet Hardware Sensor 1921
§ SNMP HP ProLiant Memory Controller Sensor 1939
422 11/24/2017
§ SNMP HP ProLiant Network Interface Sensor 1948
§ SNMP HP ProLiant System Health Sensor 1966
§ SNMP IBM System X Physical Memory Sensor 1993
§ SNMP IBM System X System Health Sensor 2002
§ SNMP Juniper NS System Health Sensor 2019
§ SNMP Memory Sensor 2094
§ SNMP SonicWALL System Health Sensor 2216
§ SNMP SonicWALL VPN Traffic Sensor 2224
§ WMI HDD Health Sensor 2721
Cloud Services Sensors

§ Amazon CloudWatch Alarm Sensor 461
§ Amazon CloudWatch EBS Sensor 471
§ Amazon CloudWatch EC2 Sensor 483
§ Amazon CloudWatch ElastiCache Sensor 495
§ Amazon CloudWatch ELB Sensor 508
11/24/2017 423
§ Amazon CloudWatch RDS Sensor 520
§ Amazon CloudWatch SNS Sensor 532
§ Amazon CloudWatch SQS Sensor 544
§ Common SaaS Sensor 620
§ Dropbox Sensor 683
§ GitLab Build Status Sensor 844
§ Google Analytics Sensor 853
§ Google Drive Sensor 865
§ Microsoft OneDrive Sensor 1160
Custom Sensors
§ EXE/Script Sensor 772
§ EXE/Script Advanced Sensor 784
§ IPFIX (Custom) Sensor 1104
§ jFlow V5 (Custom) Sensor 1140
§ Packet Sniffer (Custom) Sensor 1392
§ Python Script Advanced Sensor 1491
§ REST Custom Sensor 1538
§ Sensor Factory Sensor 1570
§ sFlow (Custom) Sensor 1603
§ SNMP Custom Sensor 1779
§ SNMP Custom Advanced Sensor 1788
§ SNMP Custom Lookup Sensor 1810
§ SNMP Custom String Sensor 1798
§ SNMP Custom Table Sensor 1820
§ SSH Script Sensor 2399
§ WMI Custom Sensor 2647
§ WMI Custom String Sensor 2657
PRTG Internal Sensors

§ Cluste Health Sensor 615
§ Core Health Sensor 628
§ Probe Health Sensor 1484
424 11/24/2017
§ System Health Sensor 2456
All Sensors in Alphabetical Order

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

§ ADO SQL v2 Sensor 445 (v16.x.24)
§ Amazon CloudWatch Alarm Sensor 461 (v16.x.22)
§ Amazon CloudWatch EBS Sensor 471 (v15.x.19)
§ Amazon CloudWatch EC2 Sensor 483 (v15.x.19)
§ Amazon CloudWatch ElastiCache Sensor 495 (v15.x.19)
§ Amazon CloudWatch ELB Sensor 508 (v15.x.19)
§ Amazon CloudWatch RDS Sensor 520 (v15.x.19)
§ Amazon CloudWatch SNS Sensor 532 (v15.x.19)
§ Amazon CloudWatch SQS Sensor 544 (v15.x.19)
§ Business Process Sensor 556 (v15.x.20)
§ Cisco IP SLA Sensor 568 (v7)
§ Citrix XenServer Host Sensor 577 (v12.x.1)
§ Citrix XenServer Virtual Machine Sensor 587 (v8.1.0)
§ Cloud HTTP Sensor 597 (v14.x.14)
§ Cloud Ping Sensor 606 (v14.x.14)
§ Cluster Health Sensor 615 (v9.1.0)
§ Common SaaS Sensor 620 (v15.x.19)
§ Core Health Sensor 628 (v9.1.0)
§ Dell PowerVault MDi Logical Disk Sensor 635 (v12.x.1)
§ Dell PowerVault MDi Physical Disk Sensor 644 (v14.x.13)
§ DHCP Sensor 654 (v8.2.0)
§ DNS Sensor 664 (v7)
§ Docker Container Status Sensor 673 (v16.x.22)
§ Dropbox Sensor 683 (v15.x.19)
§ Enterprise Virtual Array Sensor 693 (v13.x.6)
§ Event Log (Windows API) Sensor 703 (v7)
§ Exchange Backup (Powershell) Sensor 713 (v13.x.5)
§ Exchange Database (Powershell) Sensor 722 (v13.x.5)
11/24/2017 425
§ Exchange Database DAG (Powershell) Sensor 733 (v15.x.18)

§ Exchange Mail Queue (Powershell) Sensor 743 (v13.x.5)
§ Exchange Mailbox (Powershell) Sensor 753 (v13.x.5)
§ Exchange Public Folder (Powershell) Sensor 763 (v13.x.5)
§ EXE/Script Sensor 772 (v7)
§ EXE/Script Advanced Sensor 784 (v7)
§ File Sensor 796 (v7)
§ File Content Sensor 805 (v7)
§ Folder Sensor 815 (v7)
§ FTP Sensor 825 (v7)
§ FTP Server File Count Sensor 834 (v8.3.0)
§ GitLab Build Status Sensor 844 (v16.3.26)
§ Google Analytics Sensor 853 (v15.x19)
§ Google Drive Sensor 865 (v15.x.19)
§ HTTP Sensor 875 (v7)
§ HTTP Advanced Sensor 885 (v7)
§ HTTP Apache ModStatus PerfStats Sensor 901 (v12.x.3)
§ HTTP Apache ModStatus Totals Sensor 911 (v12.x.3)
§ HTTP Content Sensor 921 (v7)
§ HTTP Data Advanced Sensor 933 (v15.x.16)
§ HTTP Full Web Page Sensor 946 (v7)
§ HTTP Push Count Sensor 957 (v13.4.8)
§ HTTP Push Data Sensor 966 (v14.1.9)
§ HTTP Push Data Advanced Sensor 977 (14.1.10)
§ HTTP Transaction Sensor 988 (v7)
§ HTTP XML/REST Value Sensor 1002 (v8.3.0)
§ Hyper-V Cluster Shared Volume Disk Free Sensor 1017 (v12.3.4)
§ Hyper-V Host Server Sensor 1028 (v7)
§ Hyper-V Virtual Machine Sensor 1037 (v7)
§ Hyper-V Virtual Network Adapter Sensor 1048 (v9.1.0)
§ Hyper-V Virtual Storage Device Sensor 1058 (v12.4.4)
§ IMAP Sensor 1067 (v7)
§ IP on DNS Blacklist Sensor 1081 (v8.3.0)
§ IPFIX Sensor 1090 (v13.x.7)
426 11/24/2017
§ IPFIX (Custom) Sensor 1104 (v13.x.7)

§ IPMI System Health Sensor 1116 (v14.x.11)
§ jFlow V5 Sensor 1126 (v8.2.0)
§ jFlow V5 (Custom) Sensor 1140 (v8.2.0)
§ LDAP Sensor 1153 (v8.1.0)
§ Microsoft OneDrive Sensor 1160 (v15.x.19)
§ Microsoft SQL v2 Sensor 1170 (v14.x.12)
§ MySQL v2 Sensor 1187 (v14.x.12)
§ NetApp Aggregate Sensor 1203 (v17.3.33)
§ NetApp I/O Sensor 1214 (v17.3.33)
§ NetApp LIF Sensor 1225 (v17.3.33)
§ NetApp LUN Sensor 1235 (v17.3.33)
§ NetApp NIC Sensor 1246 (v17.3.33)
§ NetApp Physical Disk Sensor 1256 (v17.3.33)
§ NetApp SnapMirror Sensor 1266 (v17.4.35)
§ NetApp System Health Sensor 1277 (v17.3.33)
§ NetApp Volume Sensor 1288 (v17.3.33)
§ NetFlow V5 Sensor 1299 (v7)
§ NetFlow V5 (Custom) Sensor 1313 (v7)
§ NetFlow V9 Sensor 1326 (v7)
§ NetFlow V9 (Custom) Sensor 1340 (v7)
§ Oracle SQL v2 Sensor 1353 (v14.x.13)
§ Oracle Tablespace Sensor 1369 (v15.x.18)
§ Packet Sniffer Sensor 1379 (v7)
§ Packet Sniffer (Custom) Sensor 1392 (v7)
§ PerfCounter Custom Sensor 1404 (v12.x.3)
§ PerfCounter IIS Application Pool Sensor 1414 (v12.x.6)
§ Ping Sensor 1424 (v7)
§ Ping Jitter Sensor 1433 (v8.3.0)
§ POP3 Sensor 1442 (v7)
§ Port Sensor 1451 (v7)
§ Port Range Sensor 1461 (v12.x.4)
§ PostgreSQL Sensor 1469 (v14.x.12)
§ Probe Health Sensor 1484 (v9.1.0)
11/24/2017 427
§ Python Script Advanced Sensor 1491 (v15.x.19)

§ QoS (Quality of Service) One Way Sensor 1501 (v7)
§ QoS (Quality of Service) Round Trip Sensor 1510 (v9.1.0)
§ RADIUS v2 Sensor 1520 (v14.x.13)
§ RDP (Remote Desktop) Sensor 1530 (v7)
§ REST Custom Sensor 1538 (v17.3.33)
§ Sensor Factory Sensor 1570 (v7)
§ sFlow Sensor 1589 (v7)
§ sFlow (Custom) Sensor 1603 (v7)
§ SFTP Secure File Transfer Protocol Sensor 1615 (v12.x.6)
§ Share Disk Free Sensor 1562 (v7)
§ SIP Options Ping Sensor 1624 (v12.x.1)
§ SMTP Sensor 1633 (v7)
§ SMTP&IMAP Round Trip Sensor 1642 (v7)
§ SMTP&POP3 Round Trip Sensor 1653 (v7)
§ SNMP APC Hardware Sensor 1664 (v9.1.0)
§ SNMP Buffalo TS System Health Sensor 1673 (v17.1.29)
§ SNMP Cisco ADSL Sensor 1681 (v12.x.1)
§ SNMP Cisco ASA VPN Connections Sensor 1689 (v12.x.1)
§ SNMP Cisco ASA VPN Traffic Sensor 1699 (v12.x.1)
§ SNMP Cisco ASA VPN Users Sensor 1710 (v12.x.5)
§ SNMP Cisco CBQoS Sensor 1720 (v13.x.5)
§ SNMP Cisco System Health Sensor 1729 (v12.x.4)
§ SNMP Cisco UCS Blade Sensor 1738 (v14.x.14)
§ SNMP Cisco UCS Chassis Sensor 1746 (v13.x.8)
§ SNMP Cisco UCS Physical Disk Sensor 1755 (v14.1.10)
§ SNMP Cisco UCS System Health Sensor 1763 (v13.x.8)
§ SNMP CPU Load Sensor 1771 (v12.x.4)
§ SNMP Custom Sensor 1779 (v7)
§ SNMP Custom Advanced Sensor 1788 (v15.x.18)
§ SNMP Custom String Sensor 1798 (v9.1.0)
§ SNMP Custom String Lookup Sensor 1810 (v14.x.14)
§ SNMP Custom Table Sensor 1820 (v15x.18)
§ SNMP Dell EqualLogic Logical Disk Sensor 1832 (v16.x.24)
428 11/24/2017
§ SNMP Dell EqualLogic Member Health Sensor 1841 (v16.x.24)

§ SNMP Dell EqualLogic Physical Disk Sensor 1851 (v16.x.24)
§ SNMP Dell Hardware Sensor 1860 (v7)
§ SNMP Dell PowerEdge Physical Disk Sensor 1869 (v12.x.4)
§ SNMP Dell PowerEdge System Health Sensor 1879 (v12.x.4)
§ SNMP Disk Free Sensor 1889 (v12.x.4)
§ SNMP Hardware Status Sensor 1897 (v13.x.5)
§ SNMP HP BladeSystem Blade Sensor 1905 (v15.x.18)
§ SNMP HP BladeSystem Enclosure System Health Sensor 1913 (v15.x.18)
§ SNMP HP LaserJet Hardware Sensor 1921 (v9.1.0)
§ SNMP HP ProLiant Logical Disk Sensor 1930 (v12.x.6)
§ SNMP HP ProLiant Memory Controller Sensor 1939 (v12.x.6)
§ SNMP HP ProLiant Network Interface Sensor 1948 (v12.x.4)
§ SNMP HP ProLiant Physical Disk Sensor 1957 (v12.x.6)
§ SNMP HP ProLiant System Health Sensor 1966 (v12.x.4)
§ SNMP IBM System X Logical Disk Sensor 1975 (v13.x.4)
§ SNMP IBM System X Physical Disk Sensor 1984 (v13.x.4)
§ SNMP IBM System X Physical Memory Sensor 1993 (v13.x.4)
§ SNMP IBM System X System Health Sensor 2002 (v13.x.4)
§ SNMP interSeptor Pro Environment Sensor 2011 (v14.1.10)
§ SNMP Juniper NS System Health Sensor 2019 (v15.2.16)
§ SNMP LenovoEMC Physical Disk Sensor 2027 (v13.x.8)
§ SNMP LenovoEMC System Health Sensor 2036 (v13.x.8)
§ SNMP Library Sensor 2044 (v7)
§ SNMP Linux Disk Free Sensor 2058 (v8.1.0)
§ SNMP Linux Load Average Sensor 2069 (v8.1.0)
§ SNMP Linux Meminfo Sensor 2077 (v8.1.0)
§ SNMP Linux Physical Disk Sensor 2085 (v13.x.5)
§ SNMP Memory Sensor 2094 (v12.x.4)
§ SNMP NetApp Disk Free Sensor 2103 (v12.x.3)
§ SNMP NetApp Enclosure Sensor 2112 (v12.x.4)
§ SNMP NetApp I/O Sensor 2121 (v12.x.3)
§ SNMP NetApp License Sensor 2130 (v12.x.4)
§ SNMP NetApp Logical Unit Sensor 2138 (v13.x.7)
11/24/2017 429
§ SNMP NetApp Network Interface Sensor 2147 (v12.x.3)

§ SNMP NetApp System Health Sensor 2155 (v12.x.3)
§ SNMP Poseidon Environment Sensor 2164 (v13.x.5)
§ SNMP Printer Sensor 2172 (v14.x.11)
§ SNMP QNAP Logical Disk Sensor 2180 (v13.x.4)
§ SNMP QNAP Physical Disk Sensor 2188 (v13.x.4)
§ SNMP QNAP System Health Sensor 2197 (v13.x.4)
§ SNMP RMON Sensor 2205 (v12.x.1)
§ SNMP SonicWALL System Health Sensor 2216 (v13.x.5)
§ SNMP SonicWALL VPN Traffic Sensor 2224 (v13.x.6)
§ SNMP Synology Logical Disk Sensor 2233 (v13.x.4)
§ SNMP Synology Physical Disk Sensor 2241 (v13.x.4)
§ SNMP Synology System Health Sensor 2249 (v13.x.4)
§ SNMP System Uptime Sensor 2257 (v7)
§ SNMP Traffic Sensor 2265 (v7)
§ SNMP Trap Receiver Sensor 2277 (v7)
§ SNMP Windows Service Sensor 2290 (v13.x.8)
§ SNTP Sensor 2298 (v8.1.0)
§ SSH Disk Free Sensor 2305 (v8.1.0)
§ SSH INodes Free Sensor 2318 (v8.1.1)
§ SSH Load Average Sensor 2328 (v8.1.0)
§ SSH Meminfo Sensor 2337 (v8.1.0)
§ SSH Remote Ping Sensor 2346 (v12.x.1)
§ SSH SAN Enclosure Sensor 2356 (v14.x.12)
§ SSH SAN Logical Disk Sensor 2367 (v14.1.9)
§ SSH SAN Physical Disk Sensor 2378 (v14.1.9)
§ SSH SAN System Health Sensor 2389 (v14.1.9)
§ SSH Script Sensor 2399 (v12.x.1)
§ SSH Script Advanced Sensor 2412 (v12.x.6)
§ SSL Certificate Sensor 2424 (v15.x.19)
§ SSL Security Check Sensor 2434 (v14.x.12)
§ Syslog Receiver Sensor 2443 (v7)
§ System Health Sensor 2456 (v9.1.0)
§ TFTP Sensor 2462 (v8.1.0)
430 11/24/2017
§ Traceroute Hop Count Sensor 2470 (v8.3.0)

§ VMware Datastore (SOAP) Sensor 2479 (v15.x.19)
§ VMware Host Hardware (WBEM) Sensor 2490 (v8.1.0)
§ VMware Host Hardware Status (SOAP) Sensor 2499 (v12.x.1)
§ VMware Host Performance (SOAP) Sensor 2509 (v12.x.1)
§ VMware Virtual Machine (SOAP) Sensor 2519 (v7)
§ Windows CPU Load Sensor 2529 (v7)
§ Windows IIS 6.0 SMTP Received Sensor 2539 (v8.1.0)
§ Windows IIS 6.0 SMTP Sent Sensor 2548 (v8.1.0)
§ Windows IIS Application Sensor 2557 (v12.x.1)
§ Windows MSMQ Queue Length Sensor 2566 (v8.3.0)
§ Windows Network Card Sensor 2577 (v7)
§ Windows Pagefile Sensor 2588 (v12.x.4)
§ Windows Physical Disk I/O Sensor 2597 (v16.x.24)
§ Windows Print Queue Sensor 2607 (v8.3.0)
§ Windows Process Sensor 2618 (v7)
§ Windows System Uptime Sensor 2628 (v8.1.0)
§ Windows Updates Status (Powershell) Sensor 2637 (v13.x.6)
§ WMI Custom Sensor 2647 (v7)
§ WMI Custom String Sensor 2657 (v12.x.4)
§ WMI Event Log Sensor 2669 (v7)
§ WMI Exchange Server Sensor 2680 (v9)
§ WMI Exchange Transport Queue Sensor 2690 (v12.x.1)
§ WMI File Sensor 2700 (v7)
§ WMI Free Disk Space (Multi Disk) Sensor 2709 (v7)
§ WMI HDD Health Sensor 2721 (v12.x.1)
§ WMI Logical Disk I/O Sensor 2731 (v16.x.24)
§ WMI Memory Sensor 2740 (v7)
§ WMI Microsoft SQL Server 2005 Sensor 2749 (v8.1.0)
§ WMI Microsoft SQL Server 2008 Sensor 2762 (v8.1.0)
§ WMI Microsoft SQL Server 2012 Sensor 2774 (v12.x.6)
§ WMI Remote Ping Sensor 2810 (v12.x.1)
11/24/2017 431
§ WMI Security Center Sensor 2819 (v9)

§ WMI Service Sensor 2829 (v7)
§ WMI Share Sensor 2839 (v8.1.0)
§ WMI SharePoint Process Sensor 2849 (v12.x.1)
§ WMI Terminal Services (Windows 2008+) Sensor 2858 (v8.1.0)
§ WMI Terminal Services (Windows XP/Vista/2003) Sensor 2866 (v8.1.0)
§ WMI UTC Time Sensor 2874 (v9.2.0)
§ WMI Vital System Data (V2) Sensor 2882 (v7)
§ WMI Volume Sensor 2892 (v7)
§ WSUS Statistics Sensor 2901 (v9.1.0)
Script World Sensors

In addition to the built-in sensors, you can create your own sensors. Just write a script or a
program and use it with a custom sensor 434 . There are already many free, useful scripts,
plugins, and add-ons for PRTG in the PRTG Script World. You can directly open the Script
World from the Add Sensor 309 dialog in the PRTG web interface.
§ Active Fileshare Sessions

§ Active Lync Users, Inbound/Outbound Calls
§ Active Windows Users
§ AD Group Membership
§ Advanced Exchange Server Metrics
§ Age of McAfee Anti-Virus Signatures
§ AllNet UPS
§ Altaro Hyper-V Backup Monitoring
§ Amazon AWS Costs
§ APC Battery Replacement
§ Atlantis ILIO
§ Automatic Services
§ AWS Costs Sensor
§ BGP Peer Status
§ Certain HTTP Response Code
§ Citrix Environments
§ Citrix NetScaler
§ DICOM and HL7
§ Dynamic Windows Processes
432 11/24/2017
§ Exim Queue Length

§ Find Groups and Devices with Auto-Discovery Enabled
§ Google Search Appliance
§ Historic Windows Events
§ HP ProCurve Switch Version and Model
§ HTTP Return Codes
§ Hyper-V Replication
§ iDirect Modem Sensor
§ IP Addresses of Hops
§ Kemp Load Balancer
§ Linux Distributions that are Incompatible with the SSH Disk Free Sensor
§ Linux Services
§ Locked AD Users
§ Microsoft Active Cluster Nodes
§ Mounted Windows Volumes
§ MySQL Replication
§ MySQL Table Fragmentation
§ NetApp SnapMirror
§ NetApp Snapshot Age
§ Processed MailScanner Mails
§ PRTG Pester
§ PRTG Uptime SLA Sensors
§ Quota Exceeding Exchange Mailboxes
§ RabbitMQ Queues & Exchanges
§ SAP and SAP Database Monitoring
§ SCVMM - Hyper-V and Virtual Machines
§ Seatel Antenna Sensor
§ Shadow Copy Age
§ Subscriptions Monitoring with PRTG
§ TXT DNS Records Monitoring
§ Users Logged in to PRTG
§ Veeam Backup and Replication
§ VMware Horizon 7
§ WatchGiard Firewall (Cluster or Non-Cluster) – Status Multi-WAN
11/24/2017 433
§ Website Login
§ Windows DHCP Scope Status
§ Windows Registry Value
§ YUM Update Check
Go to https://www.paessler.com/script-world and follow the instructions there to use

these sensors.
More
PRTG Manual:
Knowledge Base: Why do I encounter gaps in the graphs/data of my EXE sensors?

434 11/24/2017
2 Active Directory Replication Errors Sensor
7.8.2 Active Directory Replication Errors Sensor
The Active Directory Replication Errors sensor checks a Windows Domain Controller (DC) 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.
Ac tiv e Direc tory Replic taion Errors Sensor
11/24/2017 435
Remarks
§ The device you add the sensor to must be a Domain Controller (DC).
§ Requires 436 valid Windows domain credentials in the settings of the parent device 390 .
§ Requires 436 the probe system to be part of the domain whose Active Directory you
monitor.
§ Requires 436 .NET 4.5 or later on the probe system. If the sensor shows the error PE087,
please additionally install .NET 3.5 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 one or more sensor
channels. This means that possible states are defined in a lookup file. You can change the
behavior of a channel by editing the lookup file that this channel uses. For details, see the
manual section Define Lookups 3345 .
§ This sensor type can have a high impact on the performance of your monitoring system.
Please use it with care! We recommend that you use no more than 50 sensors of this sensor
type on each probe.
You cannot add this sensor type to the Cloud Probe of a PRTG in the cloud instance. If
you want to use this sensor type, please add it to a remote probe device.
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 3359 . If the framework is missing, you cannot create
this sensor.
Required .NET version (with latest update): .NET 4.5, .NET 4.6, or .NET 4.7.
For more information, please see this Knowledge Base article: Which .NET version does
PRTG require?
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 3359 . If this requirement is
not met, the sensor will not work. You have to add the sensor to a device that represents
your Domain Controller (DC) in PRTG.
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 390 Credent ials for Windows Sy st ems settings, please
prefer using Windows domain credentials.
436 11/24/2017
If you use local credentials, please make sure that the same Windows user accounts (with
the same username and password) exist on both the system running the PRTG probe and
the target computer. Otherwise the sensor cannot connect correctly.
Add Sensor
The Add Sensor dialog appears when you manually 309 add a new sensor to a device. It only
shows the setting fields that are required for creating the sensor. Therefore, you will not see
all setting fields in this dialog. You can change (nearly) 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 choose will be valid for all
sensors that you create when you finish this dialog.
The following settings for this sensor differ in the Add Sensor dialog in comparison to the
sensor's settings page.
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 that are
available to monitor. Add check marks in front of the respective
lines to select the desired items. PRTG creates one sensor for each
selection. You can also use the check box in the table head to
select and deselect all items.
Sensor Settings
On the details page of a sensor, click the Set t ings tab to change its settings.
Usually, a sensor connects to the IP Address or DNS Name of the parent device where
you created this sensor. See the Device Set t ings 385 for details. For some sensor types,
you can define the monitoring target explicitly in the sensor settings. Please see below for
details on 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 170 , as well as in alarms 207 , logs
216 , notifications 2966 , reports 3000 , maps 3026 , libraries 2984 , and tickets
218 .
11/24/2017 437
Parent Tags Shows Tags 131 that this sensor inherits 131 from its parent device,
group, and probe 125 . This setting is shown for your information
only and cannot be changed here.
Tags Enter one or more Tags 131 , separated by spaces or commas. You
can use tags to group sensors and use tag–filtered views later on.
Tags are not case sensitive. We recommend that you use the
default value.
You can add additional tags to the sensor if you like. Other tags
are automatically inherited 131 from objects further up in the device
tree. These are visible above as Parent Tags.
Priority Select a priority for the sensor. This setting determines where the
sensor is placed in sensor lists. Top priority is at the top of a list.
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.
DEBU G OPTIONS
Sensor Result Define what PRTG will do with the sensor results. Choose
between:
§ Discard sensor result : Do not store the sensor result.
438 11/24/2017
DEBU G OPTIONS
§ 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 in the PRTG data folder on the probe
system the sensor is running on (on the Master node if in a
cluster). File names: Result of Sensor [ID].txt and Result of
Sensor [ID].Data.txt. This is for debugging purposes. PRTG
overrides these files with each scanning interval.
For more information on how to find the folder used for
storage, see section Dat a St orage 3383 .
This option is not available when the sensor runs on the
Cloud Probe of a PRTG in the cloud instance.
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 below the sensor's name. The available options depend
on what channels are available for this sensor.
You can set another primary channel later by clicking the pin
symbol of a channel in the sensor's Overview tab.
Graph 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 that visualizes the different components
of your total traffic.
This option cannot be used in combination with manual
Vertical Axis Scaling (available in the Sensor Channels
Set t ings 2915 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.
11/24/2017 439
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
440 11/24/2017
SCANNING INTER VAL

apply.


interrupted. The corresponding settings from the parent objects will always be active.
However, you can define additional settings here. They will be active at the same time as the
parent objects' settings.
Schedule Select a schedule from the list. Schedules can be used to monitor
for a certain time span (days, hours) every 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
added to existing ones, so all schedules are active at the same
time.
Maintenance Window Specify if you want to set up a one-time maintenance window.

During a "maintenance window" period, this object and all child
objects will not be monitored. They will be in a paused state
instead. Choose between:
be set and monitoring will always be active.
within a maintenance window. You can define a time span for a
monitoring pause below and change it even for a currently
running maintenance window.
defined end date, change the time entry in Maint enance Ends
field to a date in the past.
11/24/2017 441
Maintenance Begins This field is only visible if you enabled the maintenance window
above. Use the date time picker to enter the start date and time of
the maintenance window.
Maintenance Ends This field is only visible if you enabled the maintenance window
above. Use the date time picker to enter the end date and time of

can choose between:
§ Use parent : Pause the current sensor if the device, where it is
created on, is in Down status, or is paused by another
dependency.
§ Select object : Pause the current sensor if the device, where it is
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in Down status, or is paused by
another dependency. Select below.
§ Mast er object for parent : Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device, where it is created on: If the sensor is in 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 Down status,
or if it is paused by another dependency.
menu bar.
Dependency This field is only visible if the Select object option is enabled
above. Click on the reading-glasses and use the object selector 228
to choose an object on which the current sensor will depend.
Dependency Delay Define a time span in seconds for a dependency delay. After the
(Sec.) master object for this dependency goes back to Up status, PRTG
will start monitoring the depending objects after this extra
delayed. This can help to 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.
442 11/24/2017
This setting is not available if you choose this sensor to Use

parent or to be the Mast er object for parent . In this case,
please define delays in the parent Device Set t ings 385 or in the
superior Group Set t ings 358 .
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 443
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
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, see the Sensor Channels
Set t ings 2915 section.
Notifications
Click the Not ificat ions tab to change notification triggers. For detailed information, see the
Sensor Not ificat ions Set t ings 2924 section.
Others
For more general information about settings, see the Object Set t ings 205 section.
444 11/24/2017
3 ADO SQL v2 Sensor
7.8.3 ADO SQL v2 Sensor
The ADO SQL v2 sensor monitors a database using an ActiveX Data Objects (ADO) connection
and executes a Structured Query Language (SQL) query. It can monitor any data source that is
available via OLE DB (Object Linking and Embedding, Database) or ODBC (Open Database
Connectivity).
§ Execution time of the whole request (including connection buildup, query execution,
transaction handling, disconnection)
§ Execution time of the given query
§ Number of rows that were addressed by the query (including select statements if you
process data tables)
§ It can also process the data table and show defined values in individual channels.
ADO SQL v 2 Sensor
Remarks
§ Requires 1171 .NET 4.5 or later on the probe system.
§ Define credentials, custom port (if required), and timeout in settings section Credent ials for
Dat abase Management Sy st ems 396 of the parent device, or in the settings of a group or
probe above.
§ Your SQL query must be stored in a file on the system of the probe the sensor is created on.
If you use it on a remote probe, store the file on the system running the remote probe. In a
cluster setup, copy the file to every cluster node.
12/11/2017 445
3 ADO SQL v2 Sensor
§ PRTG Manual: Monit oring Dat abases 3271 (includes an example 3272 for channel value
selection)
§ Knowledge Base: How to setup the SQL v2 sensors in PRTG? Is there a guide?
§ Knowledge Base: How can I monitor strings from an SQL database and show a sensor status
depending on it?
§ Knowledge Base: How can I monitor error tables in SQL databases?
§ Knowledge Base: Why do I have to store SQL sensor queries and custom scripts in files on
the probe computer?
§ Save the SQL script with the query into the \Cust om Sensors\sql\adosql subfolder of your
PRTG installation. See manual section Dat a St orage 3383 for more information about how to
find this path.
§ If you use an ODBC connection, you have to define the ODBC connection in the Windows
ODBC Connection Manager first. If it is a 64-bit Windows, you need to define the ODBC
connection as an ODBC 32-bit connection.

this sensor.
PRTG require?
Add Sensor
later.
Sensor Settings
446 12/11/2017
3 ADO SQL v2 Sensor
218 .
default value.
DATABASE SPECIFIC
Connection String Enter the string that the sensor will use to connect to the
database. For example, a connection string can look like this:
Provider=SQLOLEDB.1;Data Source=10.0.0.200\SQLEXPRESS;User
ID=user;Password=userpass;Initial Catalog=Northwind
For ODBC connections, you need to enter MSDASQL as

provider, for example
Provider=MSDASQL;DSN=_my_odbc_sqlserver.
You can use the placeholders %dbloginuser and %

dbloginpassword here. PRTG will replace them with the
Credent ials for Dat abase Management Sy st ems 396 of the
parent device.
12/11/2017 447
3 ADO SQL v2 Sensor
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
change this value. It is shown for reference purposes only. If you
need to change this, please add the sensor anew.
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, see section
Dat a St orage 3383 . 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 ";".
Please be aware that with each request, the full result set will
be transferred,
so use filters and limits in your query.
See also this Knowledge Base article: Why do I have to store
SQL sensor queries and custom scripts in files on the probe
computer?
SQL Variables
You can use the following variables in your query file to have them
replaced by an input parameter. This is useful if you have various
SQL sensors with queries that differ in only one parameter.
§ Microsoft SQL, MySQL, PostgreSQL: @prt g
§ Oracle SQL: :prt g
§ ADO SQL: ? (question mark)
@prt g, :prt g, and ? behave like common SQL variables, so
consider the general rules for SQL variables. For example, you
cannot use a variable for a table in the FROM statement of a query.
Example for variables usage: SELECT * FROM Table WHERE @prtg
Use Input Parameter Define if you want to pass a parameter to your SQL query file. This
will replace the variables @prtg (Microsoft SQL, MySQL,
PostgreSQL), or :prtg (Oracle SQL), or ? (ADO SQL) in the SQL query,
considering the general rules for SQL variables. Choose between:
448 12/11/2017
3 ADO SQL v2 Sensor
DATA
§ Don't use input paramet er (default ): Execute the SQL query

file without using variables.
§ Use input paramet er: Execute an SQL query file that contains a
variable. Provide the parameter you want to use in the query
below.
Input Parameter This field is only visible if you choose Use input paramet er above.
Enter the parameter you want to pass to the SQL query file. This
parameter will replace the variable @prtg or :prtg or ? in the SQL
query, considering the general rules for SQL variables.
You can also use PRTG placeholders for custom sensors (command
line parameters) as input parameter, for example, %sensorid or %
deviceid. For details, see Applicat ion Programming Int erface
(API) Definit ion 3336 .
Provide strings as they are and do not surround them with
quotation marks. PRTG will correctly insert string parameters
into the query automatically.
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 file, 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 file, separate the single steps of the
Data Processing Define if you want to process data from the database. 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. 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. Affected rows are rows
that were changed somehow with the query (for example,
created, deleted, edited).
§ Count t able rows: Choose this option if you perform a SELECT
statement and want to monitor how many rows of the data table
this statement returns.
12/11/2017 449
3 ADO SQL v2 Sensor
DATA
§ Process dat a t able: Select this option to read and analyze the
queried data table. If you select this option, the sensor will count
rows with SELECT statements as well.
Handle DBNull in This setting is only visible if you select Process dat a t able above.
Channel Values as 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 select Process dat a t able above.
by Define how the desired cell in the database table will be selected.
This is necessary to configure the cells that 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.
The option you choose here also defines the method to optionally
determine a value for the sensor message. For details, see setting
Use Dat a Table Value in Sensor Message below.
Please see manual section Monit oring Dat abases 3271 for an
example 3272 for channel value selection.
Sensor Channel #x This setting is only visible if you select Process dat a t able 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.
450 12/11/2017
3 ADO SQL v2 Sensor
DATA
Once a sensor is created, you cannot change this value. It is

shown for reference purposes only. If you need to change this,
Name Enter a unique name for the channel. Please enter a string.
Channels will be generated dynamically with this name as identifier.
Sensor Channel #x This setting is only visible if you select Column number above.
Column Number Provide the number of the column that will be used to determine
the channel value in row 0. Please enter an integer value.
Column Name Provide the name of the column that will be used to determine the
channel value in row 0. Please enter a string.
Sensor Channel #x This setting is only visible if you select Row number above.
Row Number Provide the number of the row that will be used to determine the
channel value in column 0. Please enter an integer value.
Sensor Channel #x Key This setting is only visible if you select Key value pair above.
Provide the key to search for in column 0 of the data table. The
value in column 1 of the same row where the key value was found
will be used to determine the channel value. Please enter a string.
Mode Define how to display the determined value in the channel. Once a
§ Absolut e (recommended): Shows the value as the sensor
retrieves it from the data table.
§ Difference: The sensor calculates and shows the difference
between the last and the current value returned from the data
table.
Unit Define the unit of the channel value. 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. Choose
between:
§ BytesBandwidth
12/11/2017 451
3 ADO SQL v2 Sensor
DATA
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Value Lookup
For more information about the available units, please refer to
the PRTG Applicat ion Programming Int erface (API)
Definit ion 3336 for custom sensors.
To use lookups 3345 with this channel, choose Value Lookup
and select your lookup file below. Do not use Cust om for
using lookups with this sensor!
Sensor Channel #x This setting is only visible if you select Cust om above. Define a
Custom Unit unit for the channel value. Please enter a string.
Sensor Channel #x This settings is only visible if you select Value Lookup above.
Value Lookup Select a lookup 3345 file that you want to use with this channel.
Use Data Table Value in This setting is only visible if you select Process dat a t able above.
Sensor Message 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 a defined value of
the data table. Define the value selection below.
The method to determine a value for the sensor message is
defined in setting Select Channel Value by above.
452 12/11/2017
3 ADO SQL v2 Sensor
DATA
Sensor Message This setting is only visible if you select Column number and Use
Column Number Dat a Table Value in Sensor Message above. Enter the number of
a column. The sensor message will show the value in row 0 of this
column. Please enter an integer value.
Columns and rows start with index 0.
Sensor Message This setting is only visible if you select Column name and Use
Column Name Dat a Table Value in Sensor Message above. Enter the name of a
column. The sensor message will show the value in row 0 of this
column. Please enter a string.
Sensor Message Row This setting is only visible if you select Row number and Use Dat a
Number Table Value in Sensor Message above. Enter the number of a
row. The sensor message will show value in column 0 of this row.
Sensor Message Key This setting is only visible if you select Key value pair and Use
Dat a Table Value in Sensor Message above. Enter a key to
search for in column 0 of the data table. The sensor message will
show the value in column 1 of the row where the key has been
found. Please enter a string.
Sensor Message This setting is only visible if you select Use Dat a Table Value in
Sensor Message above. Define the sensor message. Please enter
a string. Use the placeholder {0} at the position where the value
will be added.
Example: The message is {0}
If Sensor Message Define what this sensor will do when the sensor value changes.
Changes You can choose between:
§ 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 2924 whenever the sensor value changes.
between:
12/11/2017 453
3 ADO SQL v2 Sensor
DATA

SENSOR DISPLAY
for each channel.
454 12/11/2017
3 ADO SQL v2 Sensor
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
12/11/2017 455
3 ADO SQL v2 Sensor
SCANNING INTER VAL

apply.


time.

456 12/11/2017
3 ADO SQL v2 Sensor

can choose between:
dependency.
menu bar.
12/11/2017 457
3 ADO SQL v2 Sensor

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
458 12/11/2017
3 ADO SQL v2 Sensor
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: How to setup the SQL v2 sensors in PRTG? Is there a guide?
Knowledge Base: How can I monitor strings from an SQL database and show a sensor status
depending on it?
Knowledge Base: How do I monitor the size of a Microsoft SQL server database?
Knowledge Base: How can I monitor error tables in SQL databases?
Knowledge Base: Why do I have to store SQL sensor queries and custom scripts in files on the
probe computer?
PRTG Manual:
§ Monit oring Dat abases 3271
12/11/2017 459
3 ADO SQL v2 Sensor

Notifications
Others
460 12/11/2017
4 Amazon CloudWatch Alarm Sensor
7.8.4 Amazon CloudWatch Alarm Sensor
The Amazon CloudWatch Alarm sensor monitors the status of an Amazon CloudWatch alarm. It
reads the data via the AWS CloudWatch Application Programming Interface (API).
§ This sensor can show the status of a configured alarm for a CloudWatch service.
Amazon CloudWatc h Alarm Sensor
Remarks
§ The data you see in the sensor message is not necessarily the current data. It merely shows
the reason for the current status 183 and why the sensor changed to it. This means for the
Up status, for example, that this data is as old as the amount of time that has passed since
the last alarm disappeared.
§ Requires 462 access rights for CloudWatch queries. For details, see the Knowledge Base: How
do I define access rights for Amazon CloudWatch queries?
§ Requires 462 .NET 4.5 or higher on the probe system.
§ Define Credent ials for Amazon CloudWat ch 398 in settings that are higher in the Object
Hierarchy 125 , for example, in the parent device settings 385 .
§ Names of configured alarms that you want to monitor must not contain double spaces.
§ Amazon will charge you (a small amount) for each "Amazon CloudWatch API Request" query
the sensor sends to the Amazon servers. For details, see the Knowledge Base: How much
does Amazon charge for using the CloudWatch API?
12/8/2017 461
§ 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.
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 this Knowledge Base article: How do I define access rights for Amazon
CloudWatch queries?

this sensor.
PRTG require?
Add Sensor
later.
PRTG looks for configured alarms on CloudWatch. This can take up to several minutes.
Select which alarm(s) you want to monitor. PRTG creates one sensor for each alarm you
choose in the Add Sensor dialog. The settings you choose will be valid for all sensors that
you create when you finish this dialog.
AMAZON CLOU DWATCH SPECIFIC
Services Select the alarms you want to add a sensor for. You see a list with
the names of all items that are available to monitor. Add check
marks in front of the respective lines to select the desired items.
PRTG creates one sensor for each selection. You can also use the
check box in the table head to select and deselect all items.
462 12/8/2017
To better find what you want to monitor, especially in large tables,

use the search function in the upper-right corner.
Sensor Settings
218 .
default value.
12/8/2017 463
Region Shows the region in which the monitored AWS instance runs. It is
one of the following regions:
§ US East (Northern Virginia)
§ US West (Oregon)
§ US West (Northern California)
§ Canada (Central)
§ EU (Ireland)
§ EU (London)
§ EU (Frankfurt)
§ Asia Pacific (Singapore)
§ Asia Pacific (Tokyo)
§ Asia Pacific (Sydney)
§ Asia Pacific (Seoul)
§ Asia Pacific (Mumbai)
§ South America (Sao Paulo)
Description Shows the description of the AWS service instance that this sensor
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
ID Shows the ID of the AWS instance that this sensor monitors. Once
a sensor is created, you cannot change this value. It is shown for
the sensor anew.
Result Handling Define what PRTG will do with the sensor results. Choose
between:
464 12/8/2017

SENSOR DISPLAY
for each channel.
12/8/2017 465
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
466 12/8/2017
SCANNING INTER VAL

apply.


time.

12/8/2017 467

can choose between:
dependency.
menu bar.
468 12/8/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
12/8/2017 469
information.
§ 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?

Notifications
Others
470 12/8/2017
5 Amazon CloudWatch EBS Sensor
7.8.5 Amazon CloudWatch EBS Sensor
The Amazon CloudWatch EBS sensor monitors the performance of the Amazon Cloud service
Elastic Block Store (EBS).
The sensor can show the following:
§ Total volume of I/O operations

§ Total disk read and write time
§ Disk read and write speed
§ Number of disk read and write operations per second
§ Idle time with no submitted operations
§ Number of read and write operations waiting to be completed
sensor setup.
Amazon CloudWatc h EBS Sensor
Remarks
§ Requires access rights for CloudWatch queries. For details, see the Knowledge Base: How
11/24/2017 471
§ Requires .NET 4.5 or higher on the probe system.

§ The minimum scanning interval for this sensor is 15 minut es.
§ Configure notification triggers 2924 with a latency of 0 seconds to receive all notifications for
this sensor ([...] for at least 0 seconds).
§ This sensor will only show those channels for which it receives data from Amazon. You can
check the availability of data in your CloudWatch Console on the AWS website. To know
which channels are possible for the various services of this Amazon CloudWatch sensor, see
the manual section Support ed Met rics. If the sensor does not receive data from Amazon
for more than 6 hours, it will go into error status.
§ To know which dimensions you can monitor, see the manual section Support ed
Dimensions.
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, see the Knowledge Base: How much does Amazon charge for using the
CloudWatch API?

CloudWatch queries?

this sensor.
PRTG require?
472 11/24/2017
Add Sensor
later.
PRTG looks for available instances.
This can take up to several minutes.
Select which service instance(s) you want to monitor. PRTG creates one sensor for each
instance you choose in the Add Sensor dialog. The settings you choose will be valid for all
Services Select the Volume you want to add a sensor for. You see a list
with the names of all items that are available to monitor. Add check
Sensor Settings
11/24/2017 473
218 .
default value.
§ US West (Oregon)
§ Canada (Central)
§ EU (Ireland)
§ EU (London)
§ EU (Frankfurt)
474 11/24/2017

the sensor anew.
between:
SENSOR DISPLAY
11/24/2017 475
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
476 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.

This sensor type has a fixed minimum scanning interval for performance reasons. You
cannot run the sensor in shorter intervals than this minimum interval. Consequently,
shorter scanning intervals as defined in Sy st em Administ rat ion—Monit oring 3096 are not
available for this sensor.
For Amazon CloudWatch sensors, the minimum scanning interval is 15 minut es.

11/24/2017 477
time.


can choose between:
dependency.
478 11/24/2017
menu bar.
11/24/2017 479
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
480 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Supported Metrics
AMAZON CLOU DWATCH METR ICS
Elastic Block Store § VolumeTotalReadTime (Sum)

(EBS)
§ VolumeTotalWriteTime (Sum)
§ VolumeReadBytes (Sum)
§ VolumeWriteOps (Sum)
§ VolumeReadOps (Sum)
§ VolumeWriteBytes (Sum)
§ VolumeConsumedReadWriteOps (Sum)
§ VolumeQueueLength (Average)
§ VolumeIdleTime (Sum)
11/24/2017 481
Supported Dimensions
AMAZON CLOU DWATCH DIMENSIONS
Elastic Block Store § Volume

(EBS)
More

Notifications
Others
482 11/24/2017
6 Amazon CloudWatch EC2 Sensor
7.8.6 Amazon CloudWatch EC2 Sensor
The Amazon CloudWatch EC2 sensor monitors the performance of the Amazon Cloud service
Elastic Cloud Computing (EC2).
§ CPU utilization
§ Network load in and out
§ Disk I/O:
· Read and write speed

· Number of disk read and write operations per second
§ CPU credit usage and balance
§ EC2 status checks
sensor setup.
Amazon CloudWatc h EC2 Sensor
11/24/2017 483
Remarks
Dimensions.
on your region).
CloudWatch API?

CloudWatch queries?

this sensor.
484 11/24/2017
PRTG require?
Add Sensor
later.
Services Select the Instances or Auto Scaling Groups you want to add a
sensor for. You see a list with the names of all items that are
Sensor Settings
11/24/2017 485
218 .
default value.
§ US West (Oregon)
§ Canada (Central)
§ EU (Ireland)
§ EU (London)
§ EU (Frankfurt)
486 11/24/2017

the sensor anew.
between:
Detailed Monitoring Choose whether you would like to import more or less detailed
monitoring data from the AWS API. Choose between
§ Enabled: You get 1 dataset per minute.
§ Disabled (default ): You get 1 dataset per 5 minutes.
To use detailed monitoring in PRTG, you must also activate it
for your monitored instance in the AWS web console.
11/24/2017 487
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
488 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 489

time.


can choose between:
dependency.
490 11/24/2017

menu bar.
11/24/2017 491
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
492 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Supported Metrics
Elastic Compute Cloud § CPUUtilization (Average)

(EC2)
§ NetworkIn (Sum)
§ NetworkOut (Sum)
§ DiskReadBytes (Sum)
§ DiskReadOps (Sum)
§ DiskWriteBytes (Sum)
§ DiskWriteOps (Sum)
§ CPUCreditUsage (Average)
§ CPUCreditBalance (Average)
§ StatusCheckFailed (Maximum)
§ StatusCheckFailed_Instance (Maximum)
§ StatusCheckFailed_System (Maximum)
11/24/2017 493
Elastic Compute Cloud § Instance

(EC2)
§ Auto Scaling Group
More

Notifications
Others
494 11/24/2017
7 Amazon CloudWatch ElastiCache Sensor
7.8.7 Amazon CloudWatch ElastiCache Sensor
The Amazon CloudWatch ElastiCache sensor monitors the performance of the Amazon Cloud
service ElastiCache.
§ CPU utilization
§ Memory
§ Cache I/O
§ Network I/O
§ Cache Statistics
See Support ed Met rics 505 for a list of data that this sensor can potentially show in dedicated
channels.
sensor setup.
Amazon CloudWatc h ElastiCac he Sensor
12/11/2017 495
Remarks
Dimensions.
on your region).
CloudWatch API?

CloudWatch queries?

this sensor.
496 12/11/2017
PRTG require?
Add Sensor
later.
Services Select the Cache Clusters or Cache Cluster Nodes you want to add
a sensor for. You see a list with the names of all items that are
Sensor Settings
12/11/2017 497
218 .
default value.
§ US West (Oregon)
§ Canada (Central)
§ EU (Ireland)
§ EU (London)
§ EU (Frankfurt)
498 12/11/2017

the sensor anew.
between:
SENSOR DISPLAY
12/11/2017 499
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
500 12/11/2017
SCANNING INTER VAL

requests.
requests.
apply.


12/11/2017 501
time.


can choose between:
dependency.
502 12/11/2017
menu bar.
12/11/2017 503
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
504 12/11/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Supported Metrics
ElastiCache § CPUUtilization (Average)

§ CurrConnections (Average)
§ CurrItems (Average)
§ NewItems (Sum)
§ NewConnections (Sum)
§ FreeableMemory (Average)
§ UnusedMemory (Average)
§ SwapUsage (Average)
§ BytesUsedForCacheItems (Average)
§ BytesReadIntoMemcached (Sum)
§ BytesWrittenOutFromMemcached (Sum)
§ NetworkBytesIn (Sum)
§ NetworkBytesOut (Sum)
§ Evictions (Sum)
§ Reclaimed (Sum)
12/11/2017 505
§ CasBadval (Sum)
§ CasHits (Sum)
§ CasMisses (Sum)
§ CmdFlush (Sum)
§ Cmdget (Sum)
§ Cmdset (Sum)
§ DecrMisses (Sum)
§ DecrHits (Sum)
§ DeleteHits (Sum)
§ DeleteMisses (Sum)
§ GetHits (Sum)
§ GetMisses (Sum)
§ IncrHits (Sum)
§ IncrMisses (Sum)
ElastiCache § Cache Cluster

§ Cache Cluster Node
More
506 12/11/2017

Notifications
Others
12/11/2017 507
8 Amazon CloudWatch ELB Sensor
7.8.8 Amazon CloudWatch ELB Sensor
The Amazon CloudWatch ELB sensor monitors the performance of the Amazon Cloud service
Elastic Load Balancing (ELB).
§ Host Count
§ HTTP Result Count (2xx, 3xx, 4xx, 5xx)
§ Latency
§ Queue
channels.
sensor setup.
Amazon CloudWatc h ELB Sensor
Remarks
508 11/24/2017
Dimensions.
on your region).
CloudWatch API?

CloudWatch queries?

this sensor.
PRTG require?
11/24/2017 509
Add Sensor
later.
Services Select the Load Balancers or Availability Zones you want to add a
Sensor Settings
510 11/24/2017
218 .
default value.
§ US West (Oregon)
§ Canada (Central)
§ EU (Ireland)
§ EU (London)
§ EU (Frankfurt)
11/24/2017 511

the sensor anew.
between:
SENSOR DISPLAY
512 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 513
SCANNING INTER VAL

requests.
requests.
apply.


514 11/24/2017
time.


can choose between:
dependency.
11/24/2017 515
menu bar.
516 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 517
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Supported Metrics
Elastic Load Balancing § RequestCount (Sum)

(ELB)
§ SpilloverCount (Sum)
§ HealthyHostCount (Minimum)
§ UnHealthyHostCount (Maximum)
§ BackendConnectionErrors (Sum)
§ HTTPCode_Backend_2XX (Sum)
§ HTTPCode_ELB_4XX (Sum)
§ HTTPCode_ELB_5XX (Sum)
§ Latency (Average)
§ SurgeQueueLength (Average)
518 11/24/2017
Elastic Load Balancing § Load Balancer

(ELB)
§ Availability Zone
More

Notifications
Others
11/24/2017 519
9 Amazon CloudWatch RDS Sensor
7.8.9 Amazon CloudWatch RDS Sensor
The Amazon CloudWatch RDS sensor monitors the performance of the Amazon Cloud service
Relational Database Service (RDS).
§ CPU Utilization
§ CPU Credit Usage and CPU Credit Balance
§ Memory Usage
§ Database I/O
§ Network I/O
§ Storage information
channels.
sensor setup.
Amazon CloudWatc h RDS Sensor
520 11/24/2017
Remarks
Dimensions.
on your region).
CloudWatch API?

CloudWatch queries?

this sensor.
11/24/2017 521
PRTG require?
Add Sensor
later.
Services Select the Engines or Database Instances you want to add a

use the search function in the upper right corner.
Sensor Settings
522 11/24/2017
218 .
default value.
§ US West (Oregon)
§ Canada (Central)
§ EU (Ireland)
§ EU (London)
§ EU (Frankfurt)
11/24/2017 523

the sensor anew.
between:
SENSOR DISPLAY
524 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 525
SCANNING INTER VAL

requests.
requests.
apply.


526 11/24/2017
time.


can choose between:
dependency.
11/24/2017 527
menu bar.
528 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 529
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Supported Metrics
Relational Database § CPUUtilization (Average)

Service (RDS)
§ CPUCreditUsage (Average)
§ CPUCreditBalance (Average)
§ DatabaseConnections (Sum)
§ FreeableMemory (Sum)
§ FreeStorageSpace (Average)
§ SwapUsage (Sum)
§ BinLogDiskUsage (Sum)
§ DiskQueueDepth (Sum)
§ ReplicLag (Average)
§ ReadIOPS (Sum)
§ WriteIOPS (Sum)
§ ReadLatency (Average)
§ WriteLatency (Average)
§ ReadThroughput (Sum)
530 11/24/2017
§ WriteThroughput (Sum)
§ NetworkReceiveThroughput (Sum)
§ NetworkTransmitThroughput (Sum)
Relational Database § Engine

Service (RDS)
§ DB Instance
More

Notifications
Others
11/24/2017 531
10 Amazon CloudWatch SNS Sensor
7.8.10 Amazon CloudWatch SNS Sensor
The Amazon CloudWatch SNS sensor monitors the performance of the Amazon Cloud service
Simple Notification Service (SNS).
§ Message Counting
§ Error Counting
channels.
sensor setup.
Amazon CloudWatc h SNS Sensor
Remarks
532 11/24/2017
Dimensions.
on your region).
CloudWatch API?

CloudWatch queries?

this sensor.
PRTG require?
Add Sensor
later.
11/24/2017 533
Services Select the Applications, Platforms or Topics you want to add a

Sensor Settings
218 .
default value.
534 11/24/2017
§ US West (Oregon)
§ Canada (Central)
§ EU (Ireland)
§ EU (London)
§ EU (Frankfurt)
11/24/2017 535
the sensor anew.
between:
SENSOR DISPLAY
for each channel.
536 11/24/2017
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
11/24/2017 537
SCANNING INTER VAL

requests.
apply.


time.
538 11/24/2017


can choose between:
dependency.
11/24/2017 539

menu bar.
540 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 541
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Supported Metrics
Simple Notification § NumberOfNotificationsDelivered (Sum)

Service (SNS)
§ NumberOfNotificationsFailed (Sum)
§ NumberOfMessagesPublished (Average)
§ PublishSize (Average)
Simple Notification § Application

Service (SNS)
§ Platform
§ Application and Platform
§ Topic
542 11/24/2017
More

Notifications
Others
11/24/2017 543
11 Amazon CloudWatch SQS Sensor
7.8.11 Amazon CloudWatch SQS Sensor
The Amazon CloudWatch SQS sensor monitors the performance of the Amazon Cloud service
Simple Queue Service (SQS).
§ Message Counting
§ Error Counting
§ Delay
channels.
sensor setup.
Amazon CloudWatc h SQS Sensor
Remarks
544 11/24/2017

Dimensions.
on your region).
CloudWatch API?

CloudWatch queries?

this sensor.
PRTG require?
Add Sensor
later.
11/24/2017 545
Services Select the Queues you want to add a sensor for. You see a list
use the search function in the upper right corner.
Sensor Settings
218 .
546 11/24/2017
default value.
§ US West (Oregon)
§ Canada (Central)
§ EU (Ireland)
§ EU (London)
§ EU (Frankfurt)
11/24/2017 547
the sensor anew.
between:
SENSOR DISPLAY
for each channel.
548 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 549
SCANNING INTER VAL

requests.
requests.
apply.


550 11/24/2017
time.


can choose between:
dependency.
11/24/2017 551
menu bar.
552 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 553
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Supported Metrics
Simple Notification § SentMessageSize (Sum)

Service (SNS)
§ NumberOfMessagesSent (Sum)
§ NumberOfMessagesReceived (Sum)
§ NumberOfMessagesDeleted (Sum)
§ NumberOfEmptyReceives (Sum)
§ ApproximateNumberOfMessagesVisible (Average)
§ ApproximateNumberOfMessagesNotVisible (Average)
§ ApproximateNumberOfMessagesDelayed (Average)
Simple Notification § Queue

Service (SNS)
554 11/24/2017
More

Notifications
Others
11/24/2017 555
12 Business Process Sensor
7.8.12 Business Process Sensor
The Business Process sensor is a powerful and very flexible sensor that allows you to give a
summary status of whole business processes while monitoring several process components.
This means that you can create your very own and individual sensor with channels based on
data from other sensors ("source sensors") that are specific to your network.
§ The summarized status of the objects contained in each channel according to the individually
defined error and warning thresholds
§ The overall and summarized status of all channels in the Global State channel
The Business Process sensor does not show values in the "Downtime" channel because
they cannot be calculated for this sensor type.
If you want to process values from other sensors and you want to perform calculations
with these values, for example, use the Sensor Fact ory Sensor 1570 instead.
sensor setup.
Business Proc ess Sensor
Remarks
§ Knowledge Base: How does the Business Process sensor calculate summarized sensor
states?
§ This sensor does not support more than 50 channels 557 officially.
556 11/24/2017
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
later.
Sensor Settings
218 .
default value.
11/24/2017 557
BU SINESS PR OCESS SPECIFIC SETTINGS
Channel Name Enter a meaningful name to identify the channel. To add a new
channel to the sensor, click the Ent er Channel Name field, enter a
name for the channel, and confirm with the enter or tab key.
Error Threshold % Set a percentage limit to define when the sensor channel displays
a Down status. Please enter an integer value. Default is 50%.
This value depends on how many objects you feed into a
business process channel.
If a channel contains less source objects in "up" condition than the

error threshold defines, this channel and the Global St at e channel
of the Business Process sensor will show a Down.
The Sensor St at es 183 that allow for the "up" condition of a

Business Process channel are the following:
§ Up
§ Warning
§ Unusual
§ Partial Down
All other sensor states will support the "down" condition (see
the table below).
For example, if you define 4 source sensors for a channel, an error
threshold of 50% means that 3 source sensors have to be in
"down" condition to set this channel to a Down status. So, 50%
means that more than half of the source sensors must not be in
"up" condition to set the sensor to Down.
For more information, an illustration of the business process
mechanisms, and some use cases of the Business Process
sensor, see the table below 560 and this Knowledge Base article:
How can I use the Business Process sensor?
558 11/24/2017
BU SINESS PR OCESS SPECIFIC SETTINGS
Warning Threshold % Set a percentage limit to define when the sensor channel displays
a Warning status. Please enter an integer value. Default is 75%.
This value depends on how many objects you feed into a
business process channel.
If a channel contains less source objects in "up" condition than the

threshold defines, this channel and the Global St at e channel of
the Business Process sensor will show a Warning status (and so
the sensor status is Warning).
The Sensor St at es 183 that allow for the "up" condition of a

Business Process channel are the following:
§ Up
§ Warning
§ Unusual
§ Partial Down
All other sensor states will support the "down" condition (see
the table below).
For example, if you define 4 source sensors for a channel, a
warning threshold of 75% means that all 4 source sensors have to
be in "down" condition to set this channel to a Warning status. So,
75% means that more than three out of four of the source sensors
must not be in "up" condition to set the sensor to Warning.
For more information, an illustration of the business process
mechanisms, and some use cases of the Business Process
sensor, see the table below 560 and this Knowledge Base article:
How can I use the Business Process sensor?
Objects Enter the objects you want to have in a channel using the + sign.
This way, you can choose the desired objects from the device tree
with the Object Select or 228 . You can also start typing the
object's ID, name, or a tag. PRTG then suggests the possible
objects to be selected.
You can add sensors, devices, groups, and probes to a channel.
Each object you add is weighted equally, no matter if it is a single
sensor or a whole device with many sensors. To give more weight
to a specific object, add it several times. For example, add it twice
to give double weight to an object, add it three times to give it
triple weight.
A probe, group, or device is as long in "up" condition as it

does not contain any sensors in "down" condition .
11/24/2017 559
Up and Down Condit ions
The Business Process Up and Down condit ions are different from the normal PRTG up
and down Sensor St at es 183 . This is necessary for the Business Process sensor to be able to
calculate summarized states and to show a calculated result for a whole business process.
This table illustrates which sensor status leads to which Business Process condition.
THE R ELATION BETWEEN OBJECT STATES AND BU SINESS PR OCESS

CONDITIONS
Channel Object Business Process Reason: Why does a given sensor st at us

St at us Condit ion correspond t o a given Business Process
condit ion?
The monitored object works, so everything is fine.

Up Up
The sensor may show a warning, but the monitored

Warning Up object still works.
This status is available in a cluster setup and is

Partial Down Up displayed if at least one cluster node reports the
sensor as up and at least one cluster node reports
it as down. With at least one up report, the
monitored object is supposed to be working and
meets the business process up condition.
The sensor may show unusual values, but the

Unusual Up monitored object works.
The sensor still waits for more monitoring data to

Collecting Up definitely decide about the sensor status, but so far
the monitored object works. This PRTG internal
status is visualized as Unknown in the PRTG web
interface.
The monitored object does not work.

Down Down
The sensor does not know if the monitored object

Unknown Down works, for example because it has not yet received
any data or because it has not received any data for
a certain amount of time.
560 11/24/2017
THE R ELATION BETWEEN OBJECT STATES AND BU SINESS PR OCESS

CONDITIONS
The sensor has not yet received any monitoring

None Down data from the monitored object. This PRTG internal
status is visualized as Unknown in the PRTG web
interface.
The monitored object does not work and

Paused Down monitoring has been paused, for example actively by
the user, by inheritance, or by executed schedules.
It might be convenient to exclude regularly or
frequently paused objects from your business
process monitoring, so you do not give more
weight than necessary to a Business Process down
status because of issues you already know about.
The monitored object does not work and someone

Down Down already knows.
Acknowledged
If you encounter issues with your Business Process sensor and want to contact our
support team 3162 , please send us your exact configuration. It helps us find the cause more
easily and quickly. Click the little clipboard icon in the upper-right of the Business Process
Specific Set t ings table to copy your configuration:
The Business Proc ess Sensor Configuration Clipboard
You find your configuration in the window that opens. Copy the marked text and paste it into
the support form 3162 to send it our support team.
11/24/2017 561
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
562 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 563

time.


can choose between:
dependency.
564 11/24/2017

menu bar.
11/24/2017 565
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: How does the Business Process sensor calculate summarized sensor states?
Knowledge Base: How can I use the Business Process sensor?

566 11/24/2017
Notifications
Others
11/24/2017 567
13 Cisco IP SLA Sensor
7.8.13 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
§ Sense code (status code of RTT entry)
sensor setup.
568 11/24/2017
Cisc o IP SLA Sensor
Remarks
§ For a general introduction to the technology behind Quality of Service monitoring, please
see manual section Monit oring Qualit y of Service 3256 .
Add Sensor
later.
Select which SLAs you want to monitor. PRTG creates one sensor for each SLA you select in
the Add Sensor dialog. The settings you choose will be valid for all sensors that you create
when you finish this dialog.
11/24/2017 569
IP SLA SPECIFIC
IP SLAs Select the IP SLAs you want to add a sensor for. You see a list with
The list options depend on the configuration of the queried device.
If you miss a type here, please check the configuration of your
target device. PRTG can support the following operations with the
given type IDs:
§ echo (1)
§ pat hEcho (2)
§ fileIO (3)
§ script (4)
§ udpEcho (5)
§ t cpConnect (6)
§ ht t p (7)
§ dns (8)
§ jit t er (9)
§ dlsw (10)
§ dhcp (11)
§ ft p (12)
§ icmp-jit t er (16)
§ pat h-jit t er (23)
The numbers above are the IDs of the SLA types as reported
by the target device. PRTG translates them into the
corresponding strings. These IDs are independent from the IDs
that you see in the first column of the list. If the target device
returns other values than given above, the sensor will show an
error message that it cannot find the type.
Packet Loss values are summarized, but have no explicit
channel for Source—Destination or Destination—Source
values.
570 11/24/2017
Sensor Settings
218 .
default value.
IP SLA SPECIFIC
ID
Type These fields show SLA specific settings that the queried SLA device
provides. Once a sensor is created, you cannot change this value.
Name (Tag) this, please add the sensor anew.
Owner
11/24/2017 571
IP SLA SPECIFIC
Frequency
SENSOR DISPLAY
for each channel.
Inherited Settings
572 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 573

time.


can choose between:
dependency.
574 11/24/2017

menu bar.
11/24/2017 575
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
576 11/24/2017
14 Citrix XenServer Host Sensor
7.8.14 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.
Citrix XenServ er Host Sensor
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.
§ Requires credentials for Xen servers to be defined for the device you want to use the
sensor on.
§ Requires .NET 4.5 or later on the probe system.
12/8/2017 577
§ This sensor type does not fully support TLS 1.2 connections and cannot be added to
XenServers with security protocol setting "TLS 1.2 only".
type on each probe.
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.
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.

this sensor.
PRTG require?
Add Sensor
later.
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 choose will be valid for all sensors that
578 12/8/2017
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 that
are available to monitor. Add check marks in front of the
respective lines to select the desired items. PRTG creates one
sensor for each selection. You can also use the check box in the
table head to select and deselect all items.
Sensor Settings
218 .
default value.
12/8/2017 579
HOST SETTINGS
UUID Shows the Universally Unique Identifier (UUID) of the host that this
sensor monitors. This value is shown for reference purposes only.
We strongly recommend that you only change it if Paessler support
explicitly asks you to do so. Wrong usage can result in incorrect
monitoring data!
Name Shows the name of the host that this sensor monitors.
DEBU G OPTIONS
between:
SENSOR DISPLAY
580 12/8/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
12/8/2017 581
SCANNING INTER VAL

requests.
requests.
apply.


582 12/8/2017

time.


can choose between:
dependency.
12/8/2017 583
menu bar.
584 12/8/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: Does PRTG impair my Citrix environment?

12/8/2017 585
Notifications
Others
586 12/8/2017
15 Citrix XenServer Virtual Machine Sensor
7.8.15 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
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.
§ Requires credentials for Xen servers to be defined for the device you want to use the
sensor on.
§ Requires .NET 4.5 or later on the probe system.
§ This sensor type does not fully support TLS 1.2 connections and cannot be added to
XenServers with security protocol setting "TLS 1.2 only".
12/8/2017 587
type on each probe.
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.
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.

this sensor.
PRTG require?
Add Sensor
later.
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.
588 12/8/2017
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 that are available to monitor. Add check marks in
front of the respective lines to select the desired items. PRTG
creates one sensor for each selection. You can also use the check
box in the table head to select and deselect all items.
Sensor Settings
218 .
default value.
12/8/2017 589
UUID Shows the Universally Unique Identifier (UUID) of the virtual

machine. This value is shown for reference purposes only. We
strongly recommend that you only change it if Paessler support
explicitly asks you to do so. Wrong usage can result in incorrect
monitoring data!
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.
DEBU G OPTIONS
between:
SENSOR DISPLAY
590 12/8/2017
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
12/8/2017 591
SCANNING INTER VAL

requests.
requests.
apply.


592 12/8/2017

time.


can choose between:
dependency.
12/8/2017 593
menu bar.
594 12/8/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

12/8/2017 595
Notifications
Others
596 12/8/2017
16 Cloud HTTP Sensor
7.8.16 Cloud HTTP Sensor
The Cloud HTTP sensor monitors the loading time of a web server via Hypertext Transfer
Protocol (HTTP) from different locations worldwide using the PRTG Cloud. The locations are
distributed over three 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: Tokyo

§ EU West: Ireland
§ US East: Northern Virginia
§ US West: Oregon
§ Global average response time
Cloud HTTP Sensor
Remarks
§ The server on which the PRTG probe 126 with this sensor runs must have access to the
internet. The probe system needs to be able to reach ht t ps://api.prt gcloud.com:443 to
communicate with the PRTG Cloud.
12/11/2017 597
§ The address you define in the parent device settings 385 must be reachable over the internet.
You cannot use this sensor to monitor localhost (127.0.0.1) or other target devices that are
only reachable within your private network.
§ This sensor type supports proxy server usage 3108 .
§ This sensor type does not support IPv6.
§ Knowledge Base: Are there any limits for using Cloud Ping and Cloud HTTP sensors?
§ Knowledge Base: What is the PRTG Cloud Bot?
§ 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, refer to the
manual section Sensor Channels Set t ings 2915 .
Add Sensor
later.
Sensor Settings
218 .
598 12/11/2017
default value.
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 that allows you to use the
parent device's IP address or DNS name setting as part of the URL.
For more information, 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.
12/11/2017 599
HTTP SETTINGS
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.
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.
SENSOR DISPLAY
for each channel.
600 12/11/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
12/11/2017 601
SCANNING INTER VAL

apply.

For Cloud HTTP sensors, the minimum scanning interval is 10 minut es.

time.

602 12/11/2017


can choose between:
dependency.
menu bar.
12/11/2017 603
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
604 12/11/2017
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 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 add an HTTP
sensor to 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/
§ 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/
Smart URL replacement does not work for sensors running on the Probe Device.
More
Knowledge Base: Are there any limits for using Cloud Ping and Cloud HTTP sensors?
Knowledge Base: What is the PRTG Cloud Bot?

Notifications
Others
12/11/2017 605
17 Cloud Ping Sensor
7.8.17 Cloud Ping Sensor
The Cloud Ping sensor monitors the Transport Control Protocol (TCP) ping times to its parent
device from different locations worldwide using the PRTG Cloud. These locations are
distributed over three continents around the globe.
The sensor can show the response t imes of the target server pinged from the following
locations:
§ Asia Pacific: Tokyo

§ EU West: Ireland
§ US East: Northern Virginia
§ US West: Oregon
§ Global average response time
Cloud Ping Sensor
Remarks
§ The server on which the PRTG probe 126 with this sensor runs must have access to the
internet. The probe system needs to be able to reach ht t ps://api.prt gcloud.com:443 to
communicate with the PRTG Cloud.
606 11/24/2017
§ The address you define in the parent device settings 385 must be reachable over the internet.
You cannot use this sensor to monitor localhost (127.0.0.1) or other target devices that are
only reachable within your private network.
§ This sensor type supports proxy server usage 3108 .
§ This sensor type does not support IPv6.
§ Knowledge Base: Are there any limits for using Cloud Ping and Cloud HTTP sensors?
§ Knowledge Base: What is the PRTG Cloud Bot?
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 607
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 that you use 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.
Port Enter the number of the port that the sensor uses for TCP ping.
The default port is 80.
SENSOR DISPLAY
for each channel.
608 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 609
SCANNING INTER VAL

requests.
requests.
apply.

For Cloud Ping sensors, the minimum scanning interval is 10 minut es.

610 11/24/2017
time.


can choose between:
dependency.
11/24/2017 611
menu bar.
612 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: Are there any limits for using Cloud Ping and Cloud HTTP sensors?
Knowledge Base: What is the PRTG Cloud Bot?

11/24/2017 613
Notifications
Others
614 11/24/2017
18 Cluster Health Sensor
7.8.18 Cluster Health Sensor
The Cluster Health sensor monitors the health of a PRTG cluster 122 and indicates the PRTG
own system health status.
It measures various internal system parameters of the cluster system:
§ Number of connects per minute

§ Cluster ingoing and outgoing messages per minute
§ Number of connected and disconnected cluster nodes.
Cluster Health Sensor
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 will show a Down status 183 by
default.
§ You can review the states of each cluster node on the sensor's Overview tab .
§ You can choose the cluster member of which you want to show data (or of all nodes) on
the monitoring data review tabs 189 .
11/24/2017 615
Sensor Settings
218 .
default value.
SENSOR DISPLAY
616 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 617
SCANNING INTER VAL

requests.
requests.
apply.

618 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
11/24/2017 619
19 Common SaaS Sensor
7.8.19 Common SaaS Sensor
The Common SaaS sensor monitors the availability of several Software as a Service (SaaS)
providers. Because your business processes depend more and more on cloud hosts, this
sensor type is an important pillar for unified monitoring. With this sensor you can get alarms if
your cloud services are not reachable anymore.
This sensor shows the following:
§ Available services in percent

§ Response times of the following SaaS providers:
· Bing
· Dropbox
· Facebook
· GitHub
· Google Apps
· Office 365
· Salesforce
· Twitter
· Youtube
620 12/8/2017
Common SaaS Sensor
Remarks
§ The server where the PRTG probe with this sensor runs must have access to the internet.
§ PRTG creates this sensor automatically on every new probe device. If the system running the
probe has no connection to the internet, please pause 232 or delete 246 this sensor manually
to avoid error messages.
§ This sensor type has a fixed scanning interval (15 minutes). You cannot change it.
§ This sensor type inherits Proxy Set t ings for HTTP Sensors 402 from the parent device.
Add Sensor
later.
12/8/2017 621
Select which SaaS providers you want to monitor. The sensor will create one channel for each
service you choose in the Add Sensor dialog.
COMMON SAAS SPECIFIC
SaaS Checklist Select the services you want to monitor with this sensor. You see
a list with the names of all items that are available to monitor.
Select the desired items by adding check marks in front of the
respective lines. The sensor creates one channel for each
selection. You can also select and deselect all items by using the
check box in the table head.
Sensor Settings
218 .
default value.
622 12/8/2017
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
12/8/2017 623
SENSOR DISPLAY

Inherited Settings

time.

624 12/8/2017


can choose between:
dependency.
menu bar.
12/8/2017 625
626 12/8/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
12/8/2017 627
20 Core Health Sensor
7.8.20 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 that have an impact on the
stability of the system:
§ Healt h: 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.
§ Age of Code: This channel shows the time that has passed since the last update of your
PRTG installation. Please update regularly to get best security and stability for PRTG, as well
as the latest features. We recommend that you use the PRTG Aut o-Updat e 3146 to get new
versions automatically.
§ CPU Load: This channel shows the current percentage CPU load. Extensive CPU load can lead
to false, incomplete, and incorrect monitoring results. This value should usually 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.
§ Commit t ed 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 Phy sical Memory : This channel shows the amount of free physical memory currently
available on the system. This is the RAM that is physically built into 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 Virt ual 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 32-bit OS (operating system) the maximum is 2 GB (3 GB with
special settings under Windows); on a 64-bit OS it is 4 GB if PRTG is running as 32-bit version,
and unlimited as 64-bit 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).
§ Maint enance Day s: This channel shows the remaining maintenance days of your PRTG on
premises license. Please renew your maintenance on time to be sure to get updates for your
PRTG on premises installation. PRTG in the cloud instances show a fixed value here for
technical reasons.
§ Threads: This channel shows the number of program parts that are currently running
simultaneously. This number can increase with heavy load. The number should not exceed
100 in normal operation.
628 11/24/2017
§ Raw Dat a 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.
Core Health Sensor
Remarks
§ PRTG creates this sensor automatically and you cannot delete it.
§ You can set up this sensor only on a Local Probe device!
§ You can find PRTG core system memory related information also in the PRTG Sy st em St at us
3138 . For details, see the Knowledge Base: What do the PRTG core system memory
parameters mean?
Sensor Settings
11/24/2017 629
218 .
default value.
SENSOR DISPLAY
for each channel.
630 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 631
SCANNING INTER VAL

requests.
requests.
apply.

632 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 633
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: What do the PRTG core system parameters mean?

Notifications
Others
634 11/24/2017
21 Dell PowerVault MDi Logical Disk Sensor
7.8.21 Dell PowerVault M Di Logical Disk Sensor
The Dell PowerVault MDi Logical Disk sensor monitors a virtual disk on a Dell PowerVault
MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or MD3820i. It might work with other models,
too.
This sensor can show the following:
§ 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
Remarks
§ Works with Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or MD3820i,
and might support other models.
§ Requires 636 Dell Modular Disk Storage Manager on the probe system. See the Knowledge
Base: Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my
MDi SAN?
11/24/2017 635
§ 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 the 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 3359 . For
details about setup, please see More section below.
Create this sensor on a device that has the SAN's IP address configured in the IP Address/
DNS Name field of the sensor settings.
Add Sensor
later.
Select which virtual disks you want to monitor. PRTG will create one sensor for each disk you
select in the Add Sensor dialog. The settings you choose will be valid for all sensors that you
create when you finish this dialog.
SENSOR SETTINGS
Virtual Disks Select the disks you want to add a sensor for. You see a list with
Sensor Settings
636 11/24/2017
218 .
default value.
SENSOR SETTINGS
Virtual Disk Shows the name of the virtual disk that this sensor monitors. Once
the sensor anew.
between:
11/24/2017 637
SENSOR SETTINGS

SENSOR DISPLAY
for each channel.
Inherited Settings
638 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 639

time.


can choose between:
dependency.
640 11/24/2017

menu bar.
11/24/2017 641
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
642 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?

Notifications
Others
11/24/2017 643
22 Dell PowerVault MDi Physical Disk Sensor
7.8.22 Dell PowerVault M Di Phy sical Disk Sensor
The Dell PowerVault MDi Physical Disk sensor monitors a physical disk on a Dell PowerVault
MD3000i, MD3420, MD3620i, MD3000f, or MD3620f. It might work with other models, too.
This sensor 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 with the status description according to the Dell documentation:
"STATU S" "MODE" CHANNEL DESCR IPTION

CHANNEL
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
644 11/24/2017
"STATU S" "MODE" CHANNEL DESCR IPTION

CHANNEL
None (status: None (status: warning) The indicated slot is empty, or the array
warning) cannot detect the physical disk.
Undefined (status:
down)
Dell PowerVault MDi Phy sic al Disk Sensor
Remarks
§ Works with Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or MD3820i,
and might support other models.
§ Requires 644 Dell Modular Disk Storage Manager on the probe system. 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.
§ This sensor supports devices with one drawer of hard-drives only. Multiple drawers are not
supported and prevent sensor creation.
11/24/2017 645
Requirement: Dell Modular Disk Storage Manager

This sensor requires the 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 3359 . For
details about setup, please see More section below.
Create this sensor on a device that has the SAN's IP address configured in the IP Address/
DNS Name field of the sensor settings.
Add Sensor
later.
Select the physical disks you want to monitor. PRTG will create 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
Sensor Settings
646 11/24/2017
218 .
default value.
SENSOR SETTINGS
Physical Disks Shows the disk 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, please add the sensor
anew.
between:
11/24/2017 647
SENSOR SETTINGS

This option is not available when the sensor runs on the Cloud
Probe of a PRTG in the cloud instance.
SENSOR DISPLAY
for each channel.
648 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 649
SCANNING INTER VAL

apply.


time.

650 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 651

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
652 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?

Notifications
Others
11/24/2017 653
23 DHCP Sensor
7.8.23 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. When creating
this sensor, choose the network card on the probe system that 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 3355 .
§ Response time (msec)
§ Lease time given by the server (in days)
DHCP Sensor
Remarks
§ You can create this sensor only on a probe device (either local probe, a remote probe, or a
cluster probe).
§ The probe device where you create a DHCP sensor must have a static IP address. It cannot
get its IP address from DHCP because this can cause a DHCP failure that will result in a severe
issue for the probe device and you risk losing monitoring data.
§ Do not use more than 2 DHCP sensors per device. Otherwise your DHCP sensors will show
a timeout error.
§ Knowledge Base: How can I monitor a DHCP server in a specific network if there are several
DHCP networks?
654 12/11/2017
23 DHCP Sensor
Add Sensor
later.
Select the desired network interfaces to monitor DHCP servers. PRTG will create one sensor
for each network interface you choose in the Add Sensor dialog. The settings you choose will
be valid for all sensors that you create when you finish this dialog.
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 that are available to monitor.
Add check marks in front of the respective lines to select the
desired items. PRTG creates one sensor for each selection. You
can also use the check box in the table head to select and
deselect all items.
Sensor Settings
218 .
12/11/2017 655
23 DHCP Sensor
default value.
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 choose 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 183 .
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. Leave empty to not
use this field.
PRTG supports PCRE regex. You cannot use regex options or

flags. For more details, see manual section Regular
Expressions 3355 .
656 12/11/2017
23 DHCP Sensor
DHCP SPECIFIC
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 the example above.
Leave empty to not use this field.

Expressions 3355 .
Server IP Specify if you want to check the returned server IP with a regular
expression. Choose between:
§ Don't check: The IP will 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. See example
above. Leave empty to not use this field.

Expressions 3355 .
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. Leave empty to not use
this field. See example above.

Expressions 3355 .
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).
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 216 . Choose between:
12/11/2017 657
23 DHCP Sensor
DHCP SPECIFIC
§ 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.
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 216 .
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.
Regardless of this setting, those entries will always be added
to the sensor log.
SENSOR DISPLAY
for each channel.
658 12/11/2017
23 DHCP Sensor
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
12/11/2017 659
23 DHCP Sensor
SCANNING INTER VAL

requests.
apply.


time.

660 12/11/2017
23 DHCP Sensor


can choose between:
dependency.
menu bar.
12/11/2017 661
23 DHCP Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
662 12/11/2017
23 DHCP Sensor
More
Knowledge Base: How can I monitor a DHCP server in a specific network if there are several
DHCP networks?

Notifications
Others
12/11/2017 663
24 DNS Sensor
7.8.24 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 will show a Down status 183 if the DNS server does not resolve a given domain name
correctly.
DNS Sensor
Add Sensor
later.
Sensor Settings
664 11/24/2017
24 DNS Sensor
218 .
default value.
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 that
The sensor connects to the IP Address or DNS Name value of
the device 385 on which you create it.
11/24/2017 665
24 DNS Sensor
DNS SPECIFIC
Domain Enter the domain name that the sensor resolves using the Domain
Name Service (DNS) server specified in the sensor's parent device
settings 385 . 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, but there might
occur an error with certain query types.
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)
§ 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:
666 11/24/2017
24 DNS Sensor
DNS SPECIFIC

SENSOR DISPLAY
for each channel.
11/24/2017 667
24 DNS Sensor
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
668 11/24/2017
24 DNS Sensor
SCANNING INTER VAL

apply.


time.

11/24/2017 669
24 DNS Sensor

can choose between:
dependency.
menu bar.
670 11/24/2017
24 DNS Sensor

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

11/24/2017 671
24 DNS Sensor
Notifications
Others
672 11/24/2017
25 Docker Container Status Sensor
7.8.25 Docker Container Status Sensor
The Docker Container Status sensor monitors the status of a Docker container. It can show
the following:
§ Overall status of the container (create, running, paused, restarting, exited)

§ Uptime
§ Exit code
§ CPU usage
§ Available memory in bytes and percent
Doc ker Container Status Sensor
Remarks
§ The parent device for this sensor must be the Docker machine on which the container runs
that you want to monitor.
§ You need to provide certificates and private keys to monitor Docker with this sensor. For
details, see the Knowledge Base: How can I create private key and certificate for the Docker
sensor?
11/24/2017 673
Add Sensor
later.
PRTG requires an authentication with certificate and private key before you can actually add
this sensor. Provide Port (usually 2375), Privat e Key , and Cert ificat e in the appearing dialog
window and click OK. PRTG can now scan Docker for existing containers.
Select which Docker containers you want to monitor. PRTG creates one sensor for each
container you choose in the Add Sensor dialog. The settings you choose will be valid for all
DOCKER SPECIFIC
Container Select the containers you want to add a sensor for. You see a list
Sensor Settings
674 11/24/2017
218 .
default value.
DOCKER CR EDENTIALS
Port Enter the number of the port to which this sensor connects. The
default port on which Docker over TLS runs is 2376.
Private Key Provide the private key for the connection to Docker. If you have
already created a key, you can use it here. Otherwise, please
create a certificate on Docker first.
Open the key with a text editor, copy everything that the file
includes, and paste it here. Usually, the key starts with -----BEGIN
RSA PRIVATE KEY----- and ends with -----END RSA PRIVATE KEY-----
See this Knowledge Base article on how to create a Docker
certificate: How can I create private key and certificate for the
Docker sensor?
Certificate Provide the certificate for the connection to Docker. If you have
already created a certificate, you can use it here. Otherwise, please
create a certificate on Docker first.
Open the certificate with a text editor, copy everything that the file
includes, and paste it here. Usually, the certificate starts with -----
BEGIN CERTIFICATE----- and ends with -----END CERTIFICATE-----
11/24/2017 675
DOCKER CR EDENTIALS
See this Knowledge Base article on how to create a Docker

certificate: How can I create private key and certificate for the
Docker sensor?
DOCKER SPECIFIC
Container ID Shows the ID of the container that this sensor monitors. Once a
the sensor anew.
Container Name Shows the name of the container that this sensor monitors. Once
the sensor anew.
Image Shows the name of the image that was used to create the
monitored Docker container. Once a sensor is created, you cannot
Container Identification Define how the sensor will identify the Docker container that it
monitors. Choose between:
§ By cont ainer ID (default ): Use the ID of the Docker container
to identify it.
§ By cont ainer name: Use the name of the Docker container to
identify it. This is a good option if the IDs of your containers
regularly change, for example, because of nightly deployments of
your Docker containers.
between:
676 11/24/2017
DOCKER SPECIFIC

SENSOR DISPLAY
for each channel.
Inherited Settings
11/24/2017 677
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

678 11/24/2017

time.


can choose between:
dependency.
11/24/2017 679

menu bar.
680 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 681
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: How can I create private key and certificate for the Docker sensor?

Notifications
Others
682 11/24/2017
26 Dropbox Sensor
7.8.26 Dropbox Sensor
The Dropbox sensor monitors a Dropbox account using the Dropbox Application
Programming Interface (API) and OAuth2. It shows the following:
§ Free storage in bytes and percent
Dropbox Sensor
Remarks
§ The minimum scanning interval for this sensor type is 30 minut es.
§ For details about OAuth2 authentication, see manual section Aut hent icat ion Using OAut h2
691 .
Add Sensor
later.
PRTG requires OAuth2 authorization before you can actually add this sensor type. Provide
the requested credentials in the appearing window.
11/24/2017 683
26 Dropbox Sensor
DR OPBOX CR EDENTIALS
This sensor type uses OAuth2 authentication to get access to your Dropbox account.
For details about the authentication approach, see section Aut hent icat ion Using
OAut h2 691 .
OAuth URL Click the button Get Access Code to connect this sensor to your
Dropbox account using OAuth2. This is necessary to allow the
sensor to query data from Dropbox. A new browser window
appears.
Follow the steps in the window and confirm the permission for
PRTG to connect to your Dropbox account. Copy the OAuth code
you get and paste it into the OAut h Code field below.
OAuth Code Paste the access code that you receive after completing the
authorization process for PRTG at your Dropbox account. Click OK
to define the sensor settings 866 .
It is mandatory to connect this sensor to your Dropbox
account to create this sensor. Complete the OAuth approach
first to get the OAuth code.
Sensor Settings
218 .
684 11/24/2017
26 Dropbox Sensor
default value.
DR OPBOX CR EDENTIALS
OAuth Code Shows the authorization code that the sensor uses to get access
to your Dropbox account. Once a sensor is created, you cannot
SENSOR DISPLAY
for each channel.
11/24/2017 685
26 Dropbox Sensor
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
686 11/24/2017
26 Dropbox Sensor
SCANNING INTER VAL

requests.
requests.
apply.


11/24/2017 687
26 Dropbox Sensor
time.


can choose between:
dependency.
688 11/24/2017
26 Dropbox Sensor
menu bar.
11/24/2017 689
26 Dropbox Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
690 11/24/2017
26 Dropbox Sensor
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Authentication Using OAuth2

This sensor type uses the OAuth2 security protocol to access the account from which you
want to retrieve and monitor data. OAuth2 enables you to grant access to the target
account without sharing your password with PRTG. The authorization approach of PRTG using
OAuth2 works as follows.
1. Aut horizat ion Request

First, you have to request authorization for this sensor to access service resources from
your account. For this purpose you are asked to get an access code for this sensor in the
Add Sensor dialog. Click the Get Access Code button to start the authorization process
using OAuth2. A new browser window will open on the authorization server of the target
service.
2. Verify ing Ident it y
This new window contains a login form for your account that you want to monitor. Log in to
your account using your credentials for this service to authenticate your identity. This is a
common login to your account on the target server so PRTG will not see your password.
The service will forward you to the authorization page and asks you to permit PRTG to
access the data in your account.
If you are already logged in to the service with a user account,
you do not have to enter credentials in this step and get directly to the access
permission page.
3. Aut horizing PRTG
Permit PRTG to access information on your account. Note that this permission holds only for
this specific sensor, not for other sensors of this type or PRTG as a whole. For each sensor
of this type you add, you have to confirm the access permission anew. You can change the
account permissions at any time in your account at the target service.
11/24/2017 691
26 Dropbox Sensor
4. Get t ing Aut horizat ion Code

Permitting PRTG to access your account data forwards you to a page where the service
provides an aut horizat ion code. Copy this code and switch back to the Add Sensor dialog
in PRTG.
The code is only valid a short period of time and expires after a few minutes.
You can use a particular code only once.
5. Providing Aut horizat ion Code
Paste the authorization code into the OAut h Code field and complete the Add Sensor
dialog. You do not have to go through further configuration steps manually. The sensor will
accomplish the following steps automatically.
6. Request ing Access Token
After receiving the authorization code, PRTG will request an access token from the API of
the target service. For this purpose, PRTG transmits the authorization code together with
several authentication details. The API checks if the authorization is valid and returns the
access token to PRTG. Access token are specific for one account and one application (here:
PRTG). The authorization process to read data from your account is now complete.
7. Ret rieving Dat a
The sensor transmits the access token with each sensor scan in the defined scanning
interval to authenticate with your account. It is not necessary to use the original account
credentials anew. The used tokens will refresh automatically from time to time.

Notifications
Others
692 11/24/2017
27 Enterprise Virtual Array Sensor
7.8.27 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.
11/24/2017 693
SNMP HP ProLiant Network Interfac e Sensor
Remarks
§ You have to explicitly specify the credentials of the EVA in the sensor settings.
§ Requires 694 the HP Command View EVA Software on the probe system, or the alternative
described in this Knowledge Base article: 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 use another option.
For details, see this Knowledge Base article: Do I really have to install the whole Command
View on the probe to use the EVA sensor?
694 11/24/2017
Add Sensor
later.
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 choose will be valid for all sensors that you create when you finish
this dialog.
EVA SETTINGS
Modules Select the modules you want to add a sensor for. You see a list
Sensor Settings
11/24/2017 695
218 .
default value.
EVA CR EDENTIALS
Username Enter the username for the EVA.
Password Enter the password for the EVA.
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.
696 11/24/2017
EVA SETTINGS
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
between:
SENSOR DISPLAY
for each channel.
11/24/2017 697
SENSOR DISPLAY
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
698 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 699

can choose between:
dependency.
menu bar.
700 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 701
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: Do I really have to install the whole Command View on the probe to use the
EVA sensor?

Notifications
Others
702 11/24/2017
28 Event Log (Windows API) Sensor
7.8.28 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
Remarks
§ Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
§ Knowledge Base: How can I configure sensors using speed limits to keep the status for
more than scanning interval?
type on each probe.
Add Sensor
later.
Sensor Settings
11/24/2017 703
218 .
default value.
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
704 11/24/2017
WINDOWS API EVENT LOG SPECIFIC
§ File Replicat ion Service
FILTER EVENT LOG ENTR IES
Event Type Specify the type of event that this sensor processes. Other event
types 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
this option, this sensor only processes 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
Source) the source that 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 Values (Event ID) This field is only visible if you enable ID filtering above. Enter an
event ID that the events must have. Only events with an ID that
matches this value are regarded.
The Event Log (Windows API) Sensor 703 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.
11/24/2017 705
The WMI Event Log Sensor 2669 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 that 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
option, this sensor only processes messages that match the
· 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) username that the events must to be assigned to. Only events
with a username 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 that 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.
706 11/24/2017
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.
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.
SENSOR DISPLAY
for each channel.
Inherited Settings
11/24/2017 707
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

708 11/24/2017

time.


can choose between:
dependency.
11/24/2017 709

menu bar.
710 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
Knowledge Base: How can I configure sensors using speed limits to keep the status for more
than one interval?

11/24/2017 711
Notifications
Others
712 11/24/2017
29 Exchange Backup (Powershell) Sensor
7.8.29 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:
§ Passed time since the last full backup

§ Passed time since the last copy backup
§ If a backup is currently running
sensor setup.
Exc hange Bac kup (Powershell) Sensor
Remarks
§ The parent device for this sensor must be the Exchange server (version 2010 or higher) that
hosts the database you want to monitor.
§ Requires credentials for Windows systems to be defined for the device you want to use the
sensor on.
§ Requires 714 Remote PowerShell and Remote Exchange Management Shell on the target
servers and PowerShell 2.0 on the probe system.
§ Requires 714 the FQDN of the Exchange server in the parent device settings 385 .
§ Requires 714 .NET 4.5 or higher on the probe system.
§ Knowledge Base: PowerShell Sensors: FAQ
12/11/2017 713
Requirement: Remote PowerShell and Remote Exchange Management Shell

This sensor type uses PowerShell commands. To monitor Exchange servers with this
sensor, you have to enable Remot e PowerShell and Remot e Exchange Management
Shell on the target servers that you want to monitor. Also ensure you have installed
PowerShell 2.0 or later on your probe machine.
In larger environments, the default memory limit for the remote shell might be insufficient.
This might result in 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 this Knowledge Base article: How do I enable and use
remote commands in Windows PowerShell?
Requirement: Fully Qualified Domain Name (FQDN)

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, see this Knowledge Base article: I have problems with the
PowerShell Exchange sensors, what can I do?

this sensor.
PRTG require?
Add Sensor
later.
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 choose will be valid for all
714 12/11/2017
SENSOR SETTINGS
Exchange Databases Select the databases you want to add a sensor for. You see a list
Sensor Settings
218 .
default value.
12/11/2017 715
SENSOR SETTINGS
Database Shows the name of the monitored database. Once a sensor is

anew.
between:
SENSOR DISPLAY
for each channel.
716 12/11/2017
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
12/11/2017 717
SCANNING INTER VAL

requests.
apply.


time.

718 12/11/2017


can choose between:
dependency.
menu bar.
12/11/2017 719
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
720 12/11/2017
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?

Notifications
Others
12/11/2017 721
30 Exchange Database (Powershell) Sensor
7.8.30 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
Remarks
sensor on.
722 11/24/2017
§ Knowledge Base: How can I monitor additional values of Exchange databases?


IP address.

this sensor.
PRTG require?
Add Sensor
later.
11/24/2017 723
SENSOR SETTINGS
Sensor Settings
218 .
default value.
724 11/24/2017
SENSOR SETTINGS

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.
11/24/2017 725
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
726 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


time.
11/24/2017 727


can choose between:
dependency.
728 11/24/2017

menu bar.
11/24/2017 729
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
730 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: How can I monitor additional values of Exchange databases?

11/24/2017 731
Notifications
Others
732 11/24/2017
31 Exchange Database DAG (Powershell) Sensor
7.8.31 Exchange Database DAG (Powershell) Sensor
The Exchange Database DAG (Powershell) sensor monitors the Database Availability Group
(DAG) status of a database on an Exchange server using Remote PowerShell.
§ Overall DAG status (for example, if it is mounted, failed, suspended)

§ Copy status (active, not active)
§ Content index status (healthy, crawling, error)
§ If activation is suspended
§ If log copy queue is increasing
§ If replay queue is increasing
§ Length of copy queue
§ Length of Replay queue
§ Number of single page restores
Exc hange Database DAG (Powershell) Sensor
12/11/2017 733
Remarks
sensor on.
§ Make sure that the Exchange database is mounted on the target device. Otherwise, you
might not be able to properly add the sensor.
§ Knowledge Base: How can I monitor additional values of Exchange databases?


IP address.
734 12/11/2017

this sensor.
PRTG require?
Add Sensor
later.
SENSOR SETTINGS
Sensor Settings
12/11/2017 735
218 .
default value.
SENSOR SETTINGS

anew.
between:
736 12/11/2017
SENSOR SETTINGS

SENSOR DISPLAY
for each channel.
Inherited Settings
12/11/2017 737
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

738 12/11/2017

time.


can choose between:
dependency.
12/11/2017 739

menu bar.
740 12/11/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
12/11/2017 741
Knowledge Base: How can I monitor additional values of Exchange databases?

Notifications
Others
742 12/11/2017
32 Exchange Mail Queue (Powershell) Sensor
7.8.32 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
sensor setup.
Exc hange Mail Queue (Powershell) Sensor
Remarks
sensor on.
11/24/2017 743

§ Knowledge Base: What types of Exchange transport queues are there?


IP address.

this sensor.
PRTG require?
Add Sensor
later.
744 11/24/2017
Select the roles you want to monitor. PRTG creates one sensor for each role you choose in
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 that are available to monitor. Add check
Sensor Settings
218 .
default value.
11/24/2017 745
SENSOR SETTINGS
between:
SENSOR DISPLAY
for each channel.
746 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 747
SCANNING INTER VAL

requests.
requests.
apply.


time.
748 11/24/2017


can choose between:
dependency.
11/24/2017 749

menu bar.
750 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
11/24/2017 751
Knowledge Base: What types of Exchange transport queues are there?

Notifications
Others
752 11/24/2017
33 Exchange Mailbox (Powershell) Sensor
7.8.33 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
Remarks
sensor on.
§ Requires elevated rights for the user of this sensor on the Exchange system. It is not
sufficient to have administrator rights. For details, see the Knowledge Base: I have problems
with the PowerShell Exchange sensors, what can I do? (solution (2) in the reply)
11/24/2017 753



IP address.

this sensor.
PRTG require?
Add Sensor
later.
754 11/24/2017
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 choose will be valid for all
SENSOR SETTINGS
Mailboxes Select the mailboxes you want to add a sensor for. You see a list
Sensor Settings
218 .
default value.
11/24/2017 755
SENSOR SETTINGS
Mailbox Name Shows the name of the monitored mailbox. Once a sensor is
anew.
between:
SENSOR DISPLAY
756 11/24/2017
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 757
SCANNING INTER VAL

requests.
requests.
apply.


758 11/24/2017

time.


can choose between:
dependency.
11/24/2017 759
menu bar.
760 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
11/24/2017 761

Notifications
Others
762 11/24/2017
34 Exchange Public Folder (Powershell) Sensor
7.8.34 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
Remarks
sensor on.
11/24/2017 763


IP address.

this sensor.
PRTG require?
Add Sensor
later.
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 choose will be valid for all
764 11/24/2017
SENSOR SETTINGS
Public Folder Select the folders you want to add a sensor for. You see a list with
Sensor Settings
218 .
default value.
11/24/2017 765
SENSOR SETTINGS
Public Folder Shows the name of the monitored folder. Once a sensor is
anew.
between:
SENSOR DISPLAY
for each channel.
766 11/24/2017
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
11/24/2017 767
SCANNING INTER VAL

requests.
apply.


time.

768 11/24/2017


can choose between:
dependency.
menu bar.
11/24/2017 769
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
770 11/24/2017
More

Notifications
Others
11/24/2017 771
35 EXE/Script Sensor
7.8.35 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 the PRTG Application Programming Interface (API).
This sensor can show the following:
§ One value returned by the executable file or script (in one channel only)
§ Execution time
For details about the return value format, see section Applicat ion Programming
Int erface (API) Definit ion 3336 .
Remarks
§ 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.
§ If you want to execute a custom Windows Management Instrumentation Query Language
(WQL) script, please use the WMI Cust om Sensor 2647 .
§ Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
§ Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?
§ Knowledge Base: How can I show special characters with EXE/Script sensors?
772 12/12/2017
the probe computer?
Add Sensor
later.
12/12/2017 773
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 3383 ). To appear in this list, store the file into this
folder ending in BAT, CMD, DLL, EXE, PS1, or VBS.
To show the expected sensor values and status, your files must
use the correct format for the returned values (in this case,
value:message to standard output). The exit code of the file
determines the sensor status 183 .
For detailed information on how to build custom sensors and

for the expected return format, please see the API
documentation in your PRTG installation. There you will find
detailed information on the Cust om Sensors tab. See also manual
section Applicat ion Programming Int erface (API) Definit ion 3336
for more information.
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 that increases. PRTG will
show the difference between the values of two sensor scans.
A counter must return an integer, float is not supported.
The sensor cannot handle string values.
Channel Name Enter a name for the channel in which the sensor shows returned
values. Please enter a string. This is for display purposes only. You
can change the name later in the sensor's channel settings 2915 .
Unit String Enter the unit for the values that this sensor returns. Please enter
a string. This unit string is used for display purposes and will be
shown in graphs, data tables, and gauges. If you want to change
the Unit after having created the sensor, you can change it in the
sensor's channel settings 2915 .
774 12/12/2017
Sensor Settings
218 .
default value.
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.
12/12/2017 775
SENSOR SETTINGS
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, see the API documentation:
Applicat ion Programming Int erface (API) Definit ion 3336 )
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 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.
§ 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, see the API
documentation in your PRTG installation. See manual section
Applicat ion Programming Int erface (API) Definit ion 3336 for more
information.
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 open the parent device settings 385
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).
776 12/12/2017
SENSOR SETTINGS
This is useful if you use a lot of sensors and want to avoid high
resource usage caused by processes running simultaneously.
Please enter a string or leave the field empty.
For more information, see this Knowledge Base article: What is
the Mutex Name in the PRTG EXE/Script Sensor settings?
Value Type Shows the expected value type that you chose on sensor
creation. Once a sensor is created, you cannot change this value. It
is shown for reference purposes only. If you need to change this,
If Value Changes Define what this sensor will do when the sensor value changes.
You can choose between:
change.
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 script result.
§ Writ e EX E result t o disk: Store the last result received from the
script to the Logs (Sensors) directory in the PRTG data folder on
the probe system the sensor is running on (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,
see section Dat a St orage 3383 .
12/12/2017 777
SENSOR SETTINGS
§ 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.
File name: Result of Sensor [ID].txt, located in the Logs
(Sensors) directory in the PRTG data folder on the probe system
the sensor is running on (on the Master node if in a cluster).
Enable this option if you do not want failures to be overwritten
by a following success of the script.
SENSOR DISPLAY
for each channel.
778 12/12/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
12/12/2017 779
SCANNING INTER VAL

apply.


time.

780 12/12/2017

can choose between:
dependency.
menu bar.
12/12/2017 781

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Information about custom scripts and executables
§ Applicat ion Programming Int erface (API) Definit ion 3336
782 12/12/2017
Knowledge Base: What is the Mutex Name in the PRTG EXE/Script Sensor settings?
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
Knowledge Base: For which sensor types do you recommend Windows Server 2012 R2 and
why?
Knowledge Base: How can I show special characters with EXE/Script sensors?
probe computer?

Notifications
Others
12/12/2017 783
36 EXE/Script Advanced Sensor
7.8.36 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 the PRTG Application Programming Interface (API). The return value of this
sensor must be valid XML or JSON.
§ The sensor can show values returned by the executable file or script in multiple channels.
EXE/Sc ript Adv anc ed Sensor
Remarks
§ 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.
§ If you want to execute a custom Windows Management Instrumentation Query Language
(WQL) script, please use the WMI Cust om Sensor 2647 .
§ Knowledge Base: How can I test if parameters are correctly transmitted to my script when
§ Knowledge Base: How can I show special characters with EXE/Script sensors?
784 12/11/2017
the probe computer?
§ Knowledge Base: How can I use meta-scans for custom EXE/Script sensors?

Add Sensor
later.
SENSOR SETTINGS
EXE/Script Select an executable file from the list. The sensor will execute it
with every scanning interval.
This list shows all files available in the corresponding \Cust om
Sensors\EX EX ML sub-directory of the probe system's PRTG
program directory (see Dat a St orage 3383 ). 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 or JSON format to standard output.
Values and message must be embedded in the XML or JSON.

for the expected return format, see the API documentation in
your PRTG installation. There, find detailed information on the
Cust om Sensors tab. See also manual section Applicat ion
Programming Int erface (API) Definit ion 3336 for more information.

12/11/2017 785
Sensor Settings
218 .
default value.
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.
786 12/11/2017
SENSOR SETTINGS
For a full list of all placeholders, see the API documentation in

your PRTG installation. See manual section Applicat ion
Programming Int erface (API) Definit ion 3336 for more
information.
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 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.
§ Set placeholders as environment values: From within your
executable or script, the values of PRTG 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, see the API
documentation: Applicat ion Programming Int erface (API)
Definit ion 3336
executable or script file. Choose between:
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 open the parent device settings 385
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. Please enter a string or leave the field empty.
For more information, see this Knowledge Base article: http://
kb.paessler.com/en/topic/6673
12/11/2017 787
SENSOR SETTINGS
EXE Result Define what the sensor will do with the results the executable file
gives back. Choose between:
§ Discard EX E result : Do not store the script result.
§ Writ e EX E result t o disk: Store the last result received from the
script to the Logs (Sensors) directory in the PRTG data folder on
scanning interval.
§ 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.
File name: Result of Sensor [ID].txt, located in the Logs
(Sensors) directory in the PRTG data folder on the probe system
the sensor is running on (on the Master node if in a cluster).
Enable this option if you do not want failures to be overwritten
by a following success of the script.
SENSOR DISPLAY
for each channel.
788 12/11/2017
SENSOR DISPLAY

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, see the
API documentation: Applicat ion Programming Int erface (API) Definit ion 3336
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
12/11/2017 789
SCANNING INTER VAL

requests.
requests.
apply.


790 12/11/2017

time.


can choose between:
dependency.
12/11/2017 791
menu bar.
792 12/11/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
12/11/2017 793
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Information about custom scripts and executables
§ Applicat ion Programming Int erface (API) Definit ion 3336
Knowledge Base: What is the Mutex Name in the PRTG EXE/Script Sensor settings?
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
why?
Knowledge Base: How can I show special characters with EXE/Script sensors?
probe computer?
Knowledge Base: How can I use meta-scans for custom EXE/Script sensors?
794 12/11/2017

Notifications
Others
12/11/2017 795
37 File Sensor
7.8.37 File Sensor
The File sensor monitors a file located on the local disk on the parent probe system, parent
device, or a file accessible via Server Message Block (SMB). You can monitor changes to the file
content and file time stamp.
§ File size
§ Passed 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 815 , you can also monitor if the actual content of a specific
file has changed.
File Sensor
Remarks
§ Requires 797 the LanmanServer ("Server") Windows service to be running on the target
computer to monitor files on a share.
§ Try using the Fully Qualified Domain Name (FQDN) of the target device if the sensor does not
get a connection with the IP address.
§ Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029
PE032
§ Knowledge Base: Can I use placeholders in file names to monitor log files?
796 11/24/2017
37 File Sensor
Requirement: LanmanServer ("Server") Windows Service

To monitor files on Windows shares, please make sure the LanmanServer ("Server")
Windows service is running on the target computer.
To enable the service, please log in to the respective computer and open the services
manager (for example, via services.msc). In the list, find the respective service and set its St art
Ty pe to Aut omat ic.
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 797
37 File Sensor
SENSOR SPECIFIC
File Name Enter the full path to the file that this sensor will monitor. For
example, enter C:\Windows\file.t xt to monitor a file on the parent
probe system.
If you use a local path, the sensor will only look for the target file
on the system on which the parent probe runs, not on the parent
device! To monitor a file on the parent device, use the dollar sign
($) like C$\User\johnqpublic\file.t xt
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.t xt . The server part \\server\ is taken from the
parent device settings 385 of this sensor. Enter a valid path and file
name.
To provide any shares, the LanmanServer "Server" Windows
service must be running on the target computer.
Sensor Behavior Specify when the sensor shows a Down status 183 . Choose
between:
§ Show 'Down' st at us if file does not exist : The sensor will
show an error if the file does not exist.
§ Show 'Down' st at us if file exist s: The sensor will show an error
if the file does exist.
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:
798 11/24/2017
37 File Sensor
SENSOR SPECIFIC
§ Ignore changes: No action will be taken on change.

§ Trigger 'change' not ificat ion: The sensor will send an internal
SENSOR DISPLAY
for each channel.
Inherited Settings
11/24/2017 799
37 File Sensor
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

800 11/24/2017
37 File Sensor

time.


can choose between:
dependency.
11/24/2017 801
37 File Sensor

menu bar.
802 11/24/2017
37 File Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 803
37 File Sensor
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029 PE032
Knowledge Base: Can I use placeholders in file names to monitor log files?

Notifications
Others
804 11/24/2017
38 File Content Sensor
7.8.38 File Content Sensor
The File Content sensor checks a text file (for example, logfiles) 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
Remarks
§ This sensor does not support UTF-16 encoded files! In this case, please try to use a custom
sensor like the EX E/Script Sensor 772 or the EX E/Script Advanced Sensor 784 .
§ This sensor does not officially support binary files! If you would still like to monitor binary
files contrary to our recommendation, then 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 to monitor files on a share.
§ To monitor files on a Linux system, the folder has to be accessible via SMB.
§ Try using the Fully Qualified Domain Name (FQDN) of the target device if the sensor does not
get a connection with the IP address.
type on each probe.
11/24/2017 805

To monitor files on Windows shares, please make sure the LanmanServer ("Server")
Add Sensor
later.
Sensor Settings
218 .
default value.
806 11/24/2017
SENSOR SPECIFIC
File Name Enter the full path to the file that this sensor will monitor. For
example, enter C:\Windows\file.t xt . to monitor a file on the
parent probe system.
If you use a local path, the sensor looks for the target file only on
the system on which the parent probe runs, not on the parent
device! To monitor a file on the parent device, use the dollar sign
($) like C$\User\johnqpublic\file.t xt .
Convention (UNC) path without the server part (only enter share
\folder\file.t xt ). The server part (\\server\) is taken from the
parent device settings 385 of this sensor. Enter a valid path and file
name.
To provide any Windows shares, the LanmanServer "Server"
Windows service must run on the target computer.
To monitor any Linux files, the folder with these files has to be
accessible via Server Message Block (SMB).
Please be aware that it might produce high network traffic if

you define PRTG to query an entire file on your network with
every scanning interval.
Search String Define the string inside the logfile you want to check for. The input
is not case-sensitive. Please enter a string.
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.
11/24/2017 807
SENSOR SPECIFIC
§ Regular Expression: Search using a regular expression.

Expressions 3355 .
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 that
were appended since the last scan. All other lines (that already
existed in the previous scan) are not sent. The sensor assumes
that they are unchanged and still counts them.
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
that you choose the new lines option.
The sensor can only transmit 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.
The sensor supports Windows and Linux line endings (CRLF or.
LF).
File Encoding Specify the encoding of the file that this sensor monitors. Choose
between:
§ Windows-1252
§ UTF-8
§ UTF-16
Warning Behavior Define under which condition the sensor will show a Warning
status 183 . Choose between:
808 11/24/2017
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.
The change notification for this sensor is triggered if the value
of the channel Last occurrence (line) changes. It is not
triggered when the number of Mat ches changes.
DEBU G OPTIONS
between:
11/24/2017 809
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
810 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 811

time.


can choose between:
dependency.
812 11/24/2017

menu bar.
11/24/2017 813
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
814 11/24/2017
39 Folder Sensor
7.8.39 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
§ Passed time since the last change to a file in the folder ("newest file")
§ Passed time since the oldest modification of a file in the folder ("oldest file")
The Folder sensor counts all files in a folder, including hidden files.
Folder Sensor
Remarks
§ This sensor counts all files in a folder, including hidden files.
computer to monitor shares.
PE032
11/24/2017 815
39 Folder Sensor

To monitor shares on Windows machines, please make sure the LanmanServer ("Server")
Add Sensor
later.
sensor's settings page. You can change the file age check later via the Limit s section in the
channel settings 2916 of Newest File and Oldest File.
FOLDER MONITOR
Check of File Ages Specify if the sensor will monitor the folder for certain file ages and
show a corresponding status 183 . 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
the age of a file in the folder that will trigger the sensor status
change if the defined age is undercut respectively exceeded.
The value will be interpreted as days, hours, or minutes, according
to your setting below.
816 11/24/2017
39 Folder Sensor
FOLDER MONITOR
File Age Limit Unit This field is only visible if you enable a file age above. Specify the
unit for the file age value that you entered above. Choose
between:
· In day s: Choose this option if you entered a number of days in
the field above.
· In hours: Choose this option if you entered a number of hours in

the field above.
· In minut es: Choose this option if you entered a number of
minutes in the field above.
Sensor Settings
218 .
default value.
11/24/2017 817
39 Folder Sensor
FOLDER MONITOR
Folder Name Enter the full path to the folder this sensor will monitor. For
example, enter C:\Windows.
Convention (UNC) path without the server part (you would only
enter share\folder). The server part (\\server\) is taken from parent
device settings 385 of this sensor. Please enter a valid path name.
To monitor shares, the LanmanServer "Server" Windows service
must be running on the target computer.
Subfolder Recursion Specify if the sensor will include subfolders in the folder
monitoring. Choose between:
§ Do not recurse subfolders: Only monitor the folder specified
above and do not monitor its subfolders.
§ Monit or t he folder and it s subfolders (use wit h caut ion!):
Monitor the folder specified above and all of its subfolders.
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. Create a change trigger 2934 on
the Not ificat ions tab of this sensor to receive a notification
whenever there is a change.
Timeout Enter a timeout in seconds for the request. If the reply takes
818 11/24/2017
39 Folder Sensor
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
11/24/2017 819
39 Folder Sensor
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
820 11/24/2017
39 Folder Sensor
SCANNING INTER VAL

requests.
apply.


time.

11/24/2017 821
39 Folder Sensor


can choose between:
dependency.
menu bar.
822 11/24/2017
39 Folder Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 823
39 Folder Sensor
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
824 11/24/2017
40 FTP Sensor
7.8.40 FTP Sensor
The FTP sensor monitors file servers using File Transfer Protocol (FTP) and FTP over SSL (FTPS).
§ Response time of the server

§ Response message of the server
FTP Sensor
Add Sensor
later.
Sensor Settings
11/24/2017 825
40 FTP Sensor
218 .
default value.
SENSOR SPECIFIC
Port Enter the number of the port the sensor tries to connect to.
Please enter an integer value. We recommend that you use the
default value.
If you cannot make 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 that you use the default value. If you cannot
make a connection, please try the passive mode.
826 11/24/2017
40 FTP Sensor
TR ANSPOR T-LEVEL SECU R ITY
FTP Specific Specify if the sensor uses encryption for the connection. Choose
between:
§ 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 will try connecting without encryption and show an
Up status if this works.
§ Enforce Transport -Level Securit y : The connection must be
established using TLS (explicit or implicit mode). Otherwise, the
sensor will show a Down status.
§ Do not use Transport -Level-Securit y : The sensor connects to
the FTP server without encryption.
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.
Default username is "anonymous". If the sensor cannot log into
the FTP server with this username (or another one that you
define), the sensor message will show that the credentials are
incorrect but the sensor will remain in Up status.
Password Enter a password for the FTP login. Please enter a string or leave
the field empty.
If the sensor cannot log onto the FTP server with this
password, the sensor message will show that the credentials
are incorrect but the sensor will remain in Up status.
DEBU G OPTIONS
between:
11/24/2017 827
40 FTP Sensor
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
828 11/24/2017
40 FTP Sensor
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 829
40 FTP Sensor
SCANNING INTER VAL

apply.


time.

830 11/24/2017
40 FTP Sensor

can choose between:
dependency.
menu bar.
11/24/2017 831
40 FTP Sensor

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

832 11/24/2017
40 FTP Sensor
Notifications
Others
11/24/2017 833
41 FTP Server File Count Sensor
7.8.41 FTP Server File Count Sensor
The FTP Server File Count sensor logs in to an File Transfer Protocol (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
Remarks
type on each probe.

this sensor.
PRTG require?
834 11/24/2017
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 835
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.
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
If you use this method, this sensor will not use the IP
Address/DNS value of the parent device.
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.
Recursing subfolders in large directories with a high number
of branches may evoke timeout errors or performance
issues.
Username Enter the username for the login to the FTP server. Please enter a
string.
Password Define the password for the login to the FTP server. Please enter a
string.
836 11/24/2017
SENSOR SETTINGS
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 839 .
With every sensor scan, any new files from the previous scan
will be regarded as old.
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.
This sensor type only supports explicit SSL.
change.
DEBU G OPTIONS
between:
11/24/2017 837
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
838 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 839
SCANNING INTER VAL

apply.


time.

840 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 841

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
842 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 843
42 GitLab Build Status Sensor
7.8.42 GitLab Build Status Sensor
The GitLab Build Status sensor monitors the status of the latest build on one specific branch.
You can monitor your builds in either your own GitLab environment or on GitLab.com.
§ Overall status of the latest build (unknown, success, pending, canceled, failed)
§ Duration of the latest build
§ Time since the last build
§ Status of the different build steps
sensor setup.
GitLab Build Status Sensor
Remarks
§ The sensor uses the IP or DNS address of the parent device to find the GitLab server. To
monitor branches in the GitLab cloud, enter gitlab.com as address in the parent device
settings 385 .
§ The sensor can only monitor builds that are using GitLab Continuous Integration (CI). Builds
using external CI tools (for example, Jenkins) are not supported.
844 11/24/2017
§ Use with care! This sensor has high impact on the performance of your GitLab server. Please
do not add too many sensors of this type to your GitLab server, only monitor the most
important branches.
§ We do not recommend to add this sensor for temporarily existing branches. This is not
useful in most cases.
Add Sensor
later.
The sensor requires an Access Token to access your projects on GitLab. Before you can
actually create the sensor, it will ask you for this token. You can create it on the GitLab web
interface in your profile under Profile Set t ings | Access Token. Copy the created token and
paste it into the Git Lab Access Token field in the Git Lab Credent ials dialog of the sensor.
GITLAB R EPOSITOR Y
Branch Select the branches you want to add a sensor for. You see a list
use the search function in the upper right corner. For example, you
can filter for a specific project to show related branches only.
The sensor scans the last 100 builds of all projects during
sensor creation (meta-scan). If you miss a branch in the
overview, start a build on the branch that is missing and add the
sensor anew.
11/24/2017 845
Sensor Settings
218 .
default value.
GITLAB CR EDENTIALS
GitLab Access Token Enter the Access Token that you have defined in your GitLab
profile. You can create the token on the GitLab web interface in
your profile under Profile Set t ings | Access Token.
By default, this field show the access token that you have provided
during sensor creation.
846 11/24/2017
GITLAB R EPOSITOR Y
Project ID These fields show various information about the project and
branch that this sensor monitors.
Project Name
Branch
SENSOR DISPLAY
for each channel.
Inherited Settings
11/24/2017 847
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

848 11/24/2017

time.


can choose between:
dependency.
11/24/2017 849

menu bar.
850 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 851
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om

Notifications
Others
852 11/24/2017
43 Google Analytics Sensor
7.8.43 Google Analy tics Sensor
The Google Analytics sensor queries and monitors several metrics from a Google Analytics
account using the Google Application Programming Interface (API) and OAuth2.
§ It can show the values for all available Google Analytics metrics in different sensor channels.
Google Analy tic s Sensor
Remarks
863 .
§ Some dimensions and metrics cannot be queried together. See the Knowledge Base: Where
do I find available Google Analytics metrics?
Add Sensor
later.
11/24/2017 853
GOOGLE CR EDENTIALS
This sensor type uses OAuth2 authentication to get access to your Google account. For
details about the authentication approach, see section Aut hent icat ion Using OAut h2 863 .
OAuth URL Click the Get Access Code button to connect this sensor to your
Google Analytics account using OAuth2. This is necessary to allow
the sensor to query data from Google Analytics. A new browser
window appears. Please follow the steps there and confirm the
permission for PRTG to connect to your Google Analytics account.
Copy the OAuth code you get and paste it into the OAut h Code
field below.
authorization process for PRTG at your Google Analytics account.
Click OK to define the sensor settings 855 .
It is mandatory to connect this sensor to your Google
Analytics account to create this sensor. Please complete the
OAuth approach first to get the OAuth code.
GOOGLE ANALYTICS SPECIFIC
Profile Choose the Google Analytics profile that you want to monitor.
Sensor Channel #2 – You can create up to 10 different sensor channels for this sensor.
#10 You have to define at least one data channel, so you will see all
available settings for Sensor Channel #1 without enabling it
manually. Additionally you can define Sensor Channel #2 up to
Sensor Channel #10. To do so, choose between:
§ Disable: The sensor will not create this channel.
§ Enable: Create an additional channel and define all its
characteristics below (name, metric, mode, and unit).
It is not possible to enable or disable sensor channels after
the creation of this sensor!
854 11/24/2017
Channel #x Mode Define how to display the retrieved value in the channel. Once a
retrieves it from Google Analytics.
between the last and the current value returned from Google
Analytics.
Sensor Settings
218 .
default value.
11/24/2017 855
GOOGLE CR EDENTIALS
to your Google Analytics account. Once a sensor is created, you
If you need to change this, please add the sensor anew.
Profile Shows the Google Analytics profile that this sensor monitors.
Time Span Define the time that the queried monitoring covers. Choose
between:
§ Last week (default )
§ Yest erday
§ Today
Sensor Channel #x Enter a name for the channel in which the sensor shows the
Name results for the metric you choose below. Please enter a string.
Sensor Channel #x Select a metric that you want to monitor. You can choose between
Metric available Google Analytics. If your desired metric is not listed,
choose Cust om Met ric and specify below.
Sensor Channel #x This field is only visible if you choose custom metric above. Enter
Custom Metric the identifier of the metric that you want to monitor. Type it
exactly as shown in Google Analytics. Metric identifiers always start
with ga:
Please enter a string.
856 11/24/2017
Sensor Channel #x Shows how the sensor displays the retrieved value in the channel.
Mode Once a sensor is created, you cannot change this value. It is
Sensor Channel #x Define the unit of the channel value. Once a sensor is created, you
Unit cannot change this value. It is shown for reference purposes only.
between:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Value Lookup
For more information about the available units, refer to the PRTG
Applicat ion Programming Int erface (API) Definit ion 3336 for
custom sensors.
To use lookups 3345 with this channel, choose the unit Value
Lookup and select your lookup file below. Do not use the
unit Cust om for using lookups with this sensor and do not use
the channel settings 2915 to define a lookup file!
Sensor Channel #x This setting is only visible if you select the Cust om unit option
Custom Unit above. Define a unit for the channel value. Please enter a string.
11/24/2017 857
Sensor Channel #x This setting is only visible if you select the Value Lookup option
Value Lookup above. Choose a lookup 3345 file that you want to use with this
channel.
Sensor Channel #x Shows if you enabled or disabled a channel. Once a sensor is

anew.
You can define up to 10 different sensor channels per sensor.
SENSOR DISPLAY
for each channel.
858 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 859
SCANNING INTER VAL

apply.


time.

860 11/24/2017


can choose between:
dependency.
menu bar.
11/24/2017 861
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
862 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om


service.
permission page.
11/24/2017 863

in PRTG.
More
Knowledge Base: Where do I find available Google Analytics metrics?

Notifications
Others
864 11/24/2017
44 Google Drive Sensor
7.8.44 Google Drive Sensor
The Google Drive sensor monitors a Google Drive account using the Google Application
Programming Interface (API) and OAuth2. It shows the following:

§ Trash size in percent
Google Driv e Sensor
Remarks
873 .
Add Sensor
later.
11/24/2017 865
GOOGLE CR EDENTIALS
This sensor type uses OAuth2 authentication to get access to your Google account. For
details about the authentication approach, see section Aut hent icat ion Using OAut h2 873 .
OAuth URL Click the Get Access Code button to connect this sensor to your
Google Drive account using OAuth2. This is necessary to allow the
sensor to query data from Google Drive. A new browser window
appears. Please follow the steps there and confirm the permission
for PRTG to connect to your Google Drive account. Copy the
OAuth code you get and paste it into the OAut h Code field below.
authorization process for PRTG at your Google Drive account.
Click OK to define the sensor settings 866 .
It is mandatory to connect this sensor to your Google Drive
account to create this sensor. Please complete the OAuth
approach first to get the OAuth code.
Sensor Settings
218 .
866 11/24/2017
default value.
GOOGLE CR EDENTIALS
to your Google Drive account. Once a sensor is created, you
SENSOR DISPLAY
for each channel.
11/24/2017 867
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
868 11/24/2017
SCANNING INTER VAL

requests.
apply.


time.
11/24/2017 869


can choose between:
dependency.
870 11/24/2017

menu bar.
11/24/2017 871
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
872 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om


service.
permission page.
11/24/2017 873

in PRTG.

Notifications
Others
874 11/24/2017
45 HTTP Sensor
7.8.45 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
Remarks
§ Knowledge Base: My HTTP sensors fail to monitor websites which use SNI. What can I do?
§ Knowledge Base: Which HTTP status code leads to which HTTP sensor status?
§ This sensor type does not support Secure Remote Password (SRP) ciphers.
Add Sensor
later.
Sensor Settings
11/24/2017 875
45 HTTP Sensor
218 .
default value.
HTTP SPECIFIC
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
parent device's IP address/DNS name setting as part of the
URL. For more information, please see section Smart URL
Replacement below.
876 11/24/2017
45 HTTP Sensor
HTTP SPECIFIC
below.
here.
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 that is needed, for example, XML, JSON, HTTP.
Server Name Indication Shows the Server Name Identification (SNI) that the sensor
automatically determined from the host address of the parent
device 385 or the target URL of the sensor. SNI has to be a Fully
Qualified Domain Name (FQDN). Please ensure it matches the
configuration of the target server.
For details, see the Knowledge Base article My HTTP sensors
fail to monitor websites which use SNI. What can I do?
SNI Inheritance Define if you want to inherit the Server Name Identification (SNI)
from the parent device. See the Server Name Indicat ion setting
above which SNI is determined. Choose between:
§ Inherit SNI from parent device: The sensor determines the SNI
from the host address of the parent device.
11/24/2017 877
45 HTTP Sensor
HTTP SPECIFIC
§ Do not inherit SNI from parent device: The sensor determines

the SNI from the target URL as defined in the settings of this
sensor.
This sensor type implicitly supports Server Name Identification (SNI), an extension to the
TLS protocol.
SENSOR DISPLAY
for each channel.
Inherited Settings
878 11/24/2017
45 HTTP Sensor
information.
proxy login.
proxy login.
SCANNING INTER VAL
information.
11/24/2017 879
45 HTTP Sensor
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

880 11/24/2017
45 HTTP Sensor

time.


can choose between:
dependency.
11/24/2017 881
45 HTTP Sensor

menu bar.
882 11/24/2017
45 HTTP Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

www.example.com/
11/24/2017 883
45 HTTP Sensor
More
Knowledge Base: My HTTP sensors fail to monitor websites which use SNI. What can I do?

Notifications
Others
884 11/24/2017
46 HTTP Advanced Sensor
7.8.46 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
Remarks
§ Supports Smart URL Replacement 899 .
§ Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?
§ Knowledge Base: My HTTP sensors fail to monitor websites which use SNI. What can I do?
§ If you need to use SRP ciphers, please choose the Alt ernat e/Compat ibilit y Mode in the
sensor settings.
§ Bandwidth monitoring of fast internet connections may be inaccurate.
12/11/2017 885
Add Sensor
later.
Sensor Settings
218 .
default value.
886 12/11/2017
HTTP SPECIFIC
Replacement below.
below.
here.
Choose between:
12/11/2017 887
HTTP SPECIFIC
sensor.
HTTP ENGINE
Monitoring Engine If you encounter unexpected errors with the standard method that
is used to monitor a 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.
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.
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.
888 12/11/2017
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.
ADVANCED SENSOR DATA
Protocol Version Define the HTTP protocol version that the sensor will use when
connecting to the target URL. Choose between:
§ HTTP 1.0
§ HTTP 1.1: This is the default setting.
User Agent Choose which user agent string the sensor will send when
§ 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 custom user agent above.
Enter a string to be used as user agent when connecting to the
URL specified above.
12/11/2017 889
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
The sensor does not support the header field names user-
agent, content-length, host.
Ensure 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:
· Ignore changes: No action will be taken on change.
· Trigger 'change' not ificat ion: The sensor will send an internal
message indicating that the web page content has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2924 whenever the web page content
changes.
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 183 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 183 if
yes.
The content check is only intended for HTML websites and
might not work with other target URLs. For example, binary
files are not supported.
890 12/11/2017
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 3355 . Specify below.
If the data does not include the search pattern, the sensor will
show the status defined above. Please enter a string.
Check Method Define the format of 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 3355 .

Expressions 3355 .
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 183 if yes.
§ 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 183 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 3355 . 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.
12/11/2017 891
§ St ring Search (default ): Search for the string as plain text. The
characters asterisk (*) and question mark (?) 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.
Expression 3355 .

Expressions 3355 .
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 data loaded at the given
· Discard HTML result : Do not store the requested data.
· St ore lat est HTML result : Store the last result of the requested
data to the Logs (Sensors) directory in the PRTG data folder on
debugging purposes, especially in combination with content
checks. The file will be overridden with each scanning interval.

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.
892 12/11/2017
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.
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.
SENSOR DISPLAY
12/11/2017 893
SENSOR DISPLAY

for each channel.
Inherited Settings
information.
894 12/11/2017
proxy login.
proxy login.
SCANNING INTER VAL
information.
Choose between:
requests.
12/11/2017 895
SCANNING INTER VAL

requests.
apply.


time.

896 12/11/2017


can choose between:
dependency.
menu bar.
12/11/2017 897
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
898 12/11/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om

www.example.com/
More
12/11/2017 899
Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?
Knowledge Base: Is it possible to test a WSDL or SOAP service with PRTG?

Notifications
Others
900 12/11/2017
47 HTTP Apache ModStatus PerfStats Sensor
7.8.47 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 worker threads
§ Number of idle worker threads
sensor setup.
HTTP Apac he ModStatus PerfStats Sensor
Remarks
11/24/2017 901
Add Sensor
later.
Sensor Settings
218 .
default value.
902 11/24/2017
HTTP SPECIFIC
URL Enter the URL to the mod_status module on your Apache server.
PRTG will append a /server_st at us?aut o 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.
Replacement below.
TLS protocol.
AU THENTICATION
Choose between:
between:
cases.
text.
11/24/2017 903
AU THENTICATION

for single sign-on.
SENSOR DISPLAY
for each channel.
Inherited Settings
904 11/24/2017
information.
proxy login.
proxy login.
SCANNING INTER VAL
information.
11/24/2017 905
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

906 11/24/2017

time.


can choose between:
dependency.
11/24/2017 907

menu bar.
908 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

www.example.com/
11/24/2017 909
More

Notifications
Others
910 11/24/2017
48 HTTP Apache ModStatus Totals Sensor
7.8.48 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 kilobytes per second
sensor setup.
HTTP Apac he ModStatus Totals Sensor
Remarks
Add Sensor
later.
11/24/2017 911
Sensor Settings
218 .
default value.
HTTP SPECIFIC
912 11/24/2017
HTTP SPECIFIC
URL Enter the URL to the mod_status module on your Apache server.
PRTG will append a /server_st at us?aut o 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.
Replacement below.
TLS protocol.
AU THENTICATION
Choose between:
between:
cases.
text.

for single sign-on.
11/24/2017 913
AU THENTICATION
SENSOR DISPLAY
for each channel.
Inherited Settings
914 11/24/2017
information.
proxy login.
proxy login.
SCANNING INTER VAL
information.
11/24/2017 915
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

916 11/24/2017

time.


can choose between:
dependency.
11/24/2017 917

menu bar.
918 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

www.example.com/
11/24/2017 919
More

Notifications
Others
920 11/24/2017
49 HTTP Content Sensor
7.8.49 HTTP Content Sensor
The HTTP Content sensor monitors a numerical value returned by an Hypertext Transfer
Protocol (HTTP) request. In the returned HTML page, each value must be placed between
square brackets [ ]. See the example 930 below.
§ It shows the returned numbers in dedicated channels, one channel for each value.
sensor setup.
HTTP Content Sensor
Remarks
§ Knowledge Base: How can I monitor internal values of a web application with PRTG?
§ See also the PRTG manual: HTTP Cont ent Sensor—Example 930

11/24/2017 921
Add Sensor
later.
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.
§ 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 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 128 . Each value must
be placed between square brackets [ ]. Enter the number of
bracket-value pairs that the defined URL will return. Please enter an
integer value.
Do not enter a number less than the number of values
returned. Otherwise you will get an error message.
Sensor Settings
922 11/24/2017
218 .
default value.
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.
parent device's IP Address/DNS Name setting as part of the
URL. For more information, see section Smart URL Replacement
below.
Value Type Shows the kind of values that the HTML file returns. Once a sensor
is created, you cannot change this value. It is shown for reference
anew.
11/24/2017 923
TLS protocol.
Content Changes Define what the sensor will do if the content of the monitored web
page changes. Choose between:
· Ignore changes: No action will be taken on change.
· Trigger 'change' not ificat ion: The sensor will send an internal
message indicating that the web page content has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2924 whenever the web page content
changes.
between:
AU THENTICATION
Choose between:
924 11/24/2017
AU THENTICATION
between:
cases.
text.

for single sign-on.
SENSOR DISPLAY
for each channel.
11/24/2017 925
SENSOR DISPLAY
Inherited Settings
information.
proxy login.
proxy login.
926 11/24/2017

SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 927
SCANNING INTER VAL

apply.


time.

928 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 929

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
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:
930 11/24/2017
<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 script URL from above,

§ 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.
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.

www.example.com/
More
11/24/2017 931
Knowledge Base: How can I monitor internal values of a web application with PRTG?

Notifications
Others
932 11/24/2017
50 HTTP Data Advanced Sensor
7.8.50 HTTP Data Advanced Sensor
The HTTP Data Advanced sensor accesses a web server and retrieves XML or JSON encoded
data.
§ The sensor can show values returned by the web server in multiple channels.
HTTP Data Adv anc ed Sensor
Remarks
§ The requested web server must return XML or JSON encoded data that matches the format
as defined in the API documentation 3336 in section Cust om Sensors—Advanced Script ,
HTTP Dat a, and REST Cust om Sensors.
§ For best sensor performance, we recommend you specify the content type on the target
server, which is application/xml or application/json.
Add Sensor
later.
11/24/2017 933
Sensor Settings
218 .
default value.
HTTP SPECIFIC
934 11/24/2017
HTTP SPECIFIC

Replacement below.
below.
here.
Choose between:
11/24/2017 935
HTTP SPECIFIC
sensor.
Result Handling Define what the sensor will do with the data loaded at the given
· Discard HTML result : Do not store the requested data.
data to the Logs (Sensors) directory in the PRTG data folder on
debugging purposes, especially in combination with content
checks. The file will be overridden with each scanning interval.

Protocol Version Define the HTTP protocol version that the sensor will use when
§ HTTP 1.0
936 11/24/2017
§ HTTP 1.1: This is the default setting.
User Agent Choose which user agent string the sensor will send when
§ Use PRTG's default st ring: Do not enter a specific user agent,
§ 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 to 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:
header1:value1

AU THENTICATION
Choose between:
11/24/2017 937
AU THENTICATION
between:
cases.
text.

for single sign-on.
SENSOR DISPLAY
for each channel.
938 11/24/2017
SENSOR DISPLAY
Inherited Settings
information.
proxy login.
proxy login.
11/24/2017 939

SCANNING INTER VAL
information.
Choose between:
requests.
requests.
940 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 941

can choose between:
dependency.
menu bar.
942 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 943
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om

www.example.com/
More
944 11/24/2017

Notifications
Others
11/24/2017 945
51 HTTP Full Web Page Sensor
7.8.51 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. 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.
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
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?
type on each probe.
946 11/24/2017
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 947
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.
parent device's IP Address/DNS Name setting as part of the URL.
For more information, please see section Smart URL Replacement
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.
For full functionality we strongly recommend you to install
Internet Explorer 11 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 3359 where the sensor is created.
For all browser engines, the same proxy settings are used that
are configured for the Windows user account that the PRTG
probe is running on (this is usually the Windows local "system" user
account, if not changed). These settings are accessible via the
Internet Explorer of this system. If you want to use a proxy for this
full web page sensor test, for example, 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:
948 11/24/2017
§ 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).
sensor is created on. Open the sensor's parent device settings
390 to change the Windows credentials.
We recommended that you use this setting when using the

Chromium browser engine.
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 HTML result (recommended): Do not store the
requested web page.
§ Render and st ore a screenshot of most recent sensor result
as JPG: 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
scanning interval. It will be named using the pattern Fullpage of
Sensor (ID).jpg.
§ Render and st ore screenshot s of all sensor result s as JPGs
(requires lot s of disk space): Render and store one new
screenshot of the web page with each sensor scan, and store
the pictures in the Screenshot s (Fullpage Sensor) directory (on
the remote system, when used on a remote probe). This option
can be used to create a visual history of the web page.
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 ion—
Core & Probes 3113 settings.
If necessary, you can change the window size of the rendered
screenshots. For details, see the Knowledge Base article How
can I change the size of PhantomJS full web page screenshots?
11/24/2017 949
Depending on the result handling method you choose, the

sensor does not only store files in the screenshot directory,
but there will also be files in an extra cache directory. If your disk
on the probe system runs full, please also check this path (you
might have to set folder options appropriately to see this
directory):
C:\Windows\System32\config\systemprofile\AppData\Local
\Microsoft\Windows\Temporary Internet Files\Content.IE5
Authentication This setting is only visible if you select the Phant omJS 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.
§ Web page needs aut hent icat ion: PRTG automatically tries to
use HTTP Basic authentication (BA) or Windows NT LAN Manager
(NTLM) to access the web page with authentication. Enter the
credentials below.
Basic access authentication forwards the credentials in plain
text!
User This setting is only visible if you select the Phant omJS engine with
authentication above. Enter the username for the web page.
Password This setting is only visible if you select the Phant omJS engine with
authentication above. Enter the password for the web page.
SENSOR DISPLAY
for each channel.
950 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 951
SCANNING INTER VAL

requests.
requests.
apply.


time.
952 11/24/2017


can choose between:
dependency.
11/24/2017 953

menu bar.
954 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

www.example.com/
11/24/2017 955
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
956 11/24/2017
52 HTTP Push Count Sensor
7.8.52 HTTP Push Count Sensor
The HTTP Push Count sensor counts received messages that are pushed via a Hypertext
Transfer Protocol (HTTP) request to PRTG. It provides a URL that you can use to push messages
to the PRTG probe system via HTTP (insecure or TLS 1.2 encrypted).
§ It shows the number of received messages per second.
HTTP Push Count Sensor
Remarks
§ For details about the usage, see manual section HTTP Push Count Sensor—How t o Use 957 .
§ 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.
§ For a general introduction to the technology behind push, please see the manual section
Monit oring via Push 3284 .
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.
The HTTP Push Count Sensor uses the following URL:
ht t p://<probe_ip>:<port_number>/<token>
11/24/2017 957
Replace the parameters <probe_ip>, <port_number>, and <token> with the corresponding
values.
§ The <probe_ip> is the IP address of the system where the PRTG probe with the sensor is
running.
§ The <port_number> is where the sensor listens for incoming HTTP calls.
§ The <token> is used to define the matching sensor.
Example:
http://192.0.2.0:5050/XYZ123
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
later.
HTTP PU SH
SSL Settings Define the security of the incoming HTTP push requests. Choose
between:
§ HTTP (unsafe): Send push messages to the PRTG probe system
via insecure HTTP.
§ HTTPS (TLS 1.2 only ): Send push messages to the PRTG probe
system via secure HTTPS. The sensor only supports TLS 1.2
connections. It will use the SSL certificate that is delivered with
PRTG or your own trusted SSL certificate 3385 that you have
imported for the PRTG web server.
Port This field is only visible if you choose HTTP above. Enter the
number of the port on which this sensor listens for incoming HTTP
requests. Default is 5050.
SSL Port This field is only visible if you choose HTTPS above. Enter the
number of the port on which this sensor listens for incoming
HTTPS requests. Default is 5051.
958 11/24/2017
Sensor Settings
218 .
default value.
HTTP PU SH
SSL Settings Shows whether the sensor accepts push messages via HTTP or
HTTPS.
11/24/2017 959
HTTP PU SH
Port This field is only visible for sensors that accept push messages via
HTTP. It shows the port number on which this sensor listens for
incoming HTTP requests.
SSL Port This field is only visible for sensors that accept push messages via
HTTPS. It shows the port number on which this sensor listens for
incoming HTTPS requests.
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 application/x-www-form-urlencoded
with the same parameters as for GET requests.
Identification Token This is the token that is used to find the matching sensor for the
incoming message. When you create the sensor, this token is
{__guid__}.
This token will be 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.
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: "Request for 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.
960 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 961
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

962 11/24/2017

time.


can choose between:
dependency.
11/24/2017 963

menu bar.
964 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
11/24/2017 965
53 HTTP Push Data Sensor
7.8.53 HTTP Push Data Sensor
The HTTP Push Data sensor displays numerical values from received messages that are pushed
via a Hypertext Transfer Protocol (HTTP) request to PRTG. It provides a URL that you can use to
push messages to the PRTG probe system via HTTP (insecure or TLS 1.2 encrypted).
§ The sensor shows the received value and an optional message in one channel.
HTTP Push Data Sensor
Remarks
§ For details about the usage, see manual section HTTP Push Dat a Sensor—How t o Use 966 .
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.
966 12/11/2017
The HTTP Push Dat a Sensor uses the following URL:
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.
If this parameter is missing, the sensor will show 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.
This text message has to be URL encoded (for example, the whitespaces in the sample
URL below); most browsers achieve this automatically.
Example:
http://192.0.2.0:5050/XYZ123?value=0&text=this%20is%20a%20message
data of push messages will be shown in each of these sensors.
Add Sensor
later.
HTTP PU SH
between:
via insecure HTTP.
12/11/2017 967
HTTP PU SH
Sensor Settings
218 .
default value.
968 12/11/2017
HTTP PU SH
HTTPS.

{__guid__}.
12/11/2017 969
HTTP PU SH

creation.
between:
970 12/11/2017
HTTP PU SH DATA
No Incoming Data Define which status 183 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.
The probe on which this sensor runs must be connected to
keep the last status. If the probe is disconnected, the
sensor will show 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 will show an
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 show a
Down status if it has not received any message within a defined
time span. Define the time threshold below.
Time Threshold This field is only visible if you select the error option above. Enter
(Minutes) the time threshold in minutes after which the sensor status will
show a Down status if it has not received a push message within
this time span.
Please enter an integer value. The maximum threshold is 1440
minutes.
Value Type Define which type the value of the received data has. If this setting
does not match, the sensor will go into an Down status. Choose
between:
§ Int eger
§ Float (with dot . as delimiter)
SENSOR DISPLAY
12/11/2017 971
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
972 12/11/2017
SCANNING INTER VAL

requests.
requests.
apply.


12/11/2017 973

time.


can choose between:
dependency.
974 12/11/2017
menu bar.
12/11/2017 975
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
976 12/11/2017
54 HTTP Push Data Advanced Sensor
7.8.54 HTTP Push Data Advanced Sensor
The HTTP Push Data Advanced sensor displays data from received messages that are pushed
via a Hypertext Transfer Protocol (HTTP) request to PRTG. It provides a URL that you can use to
push messages to the PRTG probe system via HTTP (insecure or TLS 1.2 encrypted).
§ This sensor can show received values and a message encoded in valid XML or JSON in
multiple channels.
HTTP Push Data Adv anc ed Sensor
Remarks
§ For details about the usage, see manual section HTTP Push Dat a Advanced Sensor—How
t o Use 978 .
§ If you use this sensor with multiple channels, we recommend that you simultaneously push
the data for all your channels to the PRTG server. You can push data to only one of your
sensor channels, but in this case all other channels will record the value of 0 for this push
message.
11/24/2017 977
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 that is pushed to this sensor must be valid XML or JSON.
For details about the return value format, see the Applicat ion Programming Int erface
The HTTP Push Dat a Advanced Sensor uses the following URLs depending on the type of
HTTP request.
§ GET requests: ht t p://<probe_ip>:<port_number>/<token>?cont ent =<valid XML_or_JSON>
The XML encoded value of the content parameter has to match the format as defined in the
API documentation 3336 in section Cust om Sensors—Advanced Script HTTP Dat a Sensors.
§ POST requests: ht t p://<probe_ip>:<port_number>/<token>
This HTTP request method sends the XML or JSON encoded HTTP body as POST data. The
body has to match the format as defined in the API documentation 3336 in section Cust om
Sensors—Advanced Script HTTP Dat a Sensors. We strongly recommend the HTTP content
type application/xml or application/json.
Replace the parameters <probe_ip>, <port_number>, <token> and <valid XML_or_JSON> (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 or JSON in the PRTG API format.
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
By default, values within the <value> tags in the returned XML or JSON must be integers to
be processed. If float values are returned, you have to explicitly define this value type
according to the API documentation 3336 with <float> tags, otherwise the sensor will show 0
values in affected channels. Example:
http://127.0.0.1:5050/XYZ123?content=<prtg><result><channel>MyChannel</channel><value>10.45</value><float>1
data of push messages will be shown in each of these sensors.
978 11/24/2017
Add Sensor
later.
HTTP PU SH
between:
via insecure HTTP.
Sensor Settings
11/24/2017 979
218 .
default value.
HTTP PU SH
HTTPS.
980 11/24/2017
HTTP PU SH


{__guid__}.
creation.
between:
HTTP PU SH DATA
No Incoming Data Define which status 183 the sensor will show if it has not received a
push message for at least two sensor scans. Choose between:
11/24/2017 981
HTTP PU SH DATA
§ Ignore and keep last st at us (default ): The sensor remains in

the status as defined by the last message that the sensor
received.
The probe on which this sensor runs must be connected to
keep the last status. If the probe is disconnected, the
sensor will show 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 will show an
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 show a
Down status if it has not received any message within a defined
time span. Define the time threshold below.
Time Threshold This field is only visible if you select the error option above. Enter a
(Minutes) time threshold in minutes. If this time elapses, the sensor will show
a Down status if it has not received a push message within this
time span.
Please enter an integer value. The maximum threshold is 1440
minutes.
SENSOR DISPLAY
for each channel.
982 11/24/2017
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
11/24/2017 983
SCANNING INTER VAL

requests.
apply.


time.

984 11/24/2017


can choose between:
dependency.
menu bar.
11/24/2017 985
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
986 11/24/2017

Notifications
Others
11/24/2017 987
55 HTTP Transaction Sensor
7.8.55 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
Remarks
§ Knowledge Base: Configuration Tips for HTTP Transaction Sensors
§ Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?
§ If you need to use SRP ciphers, choose the Alt ernat e/ Compat ibilit y Mode in the sensor
settings.
Add Sensor
later.
988 12/11/2017
Sensor Settings
218 .
default value.
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).
12/11/2017 989
HTTP SPECIFIC
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).
HTTP ENGINE
Monitoring Engine If you encounter unexpected errors with the standard method that
is used to monitor a 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.
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.
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 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
990 12/11/2017
§ 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.
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 a Cust om St ring: Use a custom user agent. Define below.
Custom User Agent This field is only visible if you enable the Use a Cust om St ring
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.
12/11/2017 991
web page to the Logs (Sensors) directory in the PRTG data
folder on the probe system the sensor is running on (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 overwritten with each scanning
interval.

AU THENTICATION
Choose between:
between:
cases.
text.

for single sign-on.
992 12/11/2017
AU THENTICATION

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 show an Up status 183 .
Using this mechanism you can set up an extended monitoring with multiple URLs.
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.
URL 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 that allows you to
use the parent device's IP address/DNS name setting as part of the
URL. For more information, see section Smart URL Replacement
1000 below.
Request Method The request method determines how the given URL is requested.
· GET: Request the website directly, like browsing the web. We
· POST: Send post form data to the URL. If this setting is chosen,
below.
12/11/2017 993
TR ANSACTION U R L
· HEAD: Only request the HTTP header from the server; without
Postdata This field is only active if you choose POST in the Request
Met hod setting above. Enter the data part for the post request
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 show an error
status and display this string along with the affected URL in the
sensor message. Please enter a string.
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:
§ 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 show an error
status and display this string along with the affected URL in the
sensor message. Please enter a string.
994 12/11/2017
TR ANSACTION U R L
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.
Inherited Settings
12/11/2017 995
information.
proxy login.
proxy login.
SCANNING INTER VAL
information.
996 12/11/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

12/11/2017 997

time.


can choose between:
dependency.
998 12/11/2017

menu bar.
12/11/2017 999
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

www.example.com/
1000 12/11/2017
More
Knowledge Base: Configuration Tips for HTTP Transaction Sensors needed

Notifications
Others
12/11/2017 1001
56 HTTP XML/REST Value Sensor
7.8.56 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 one defined XML node.
HTTP XML/REST Value Sensor
Remarks
§ This sensor can monitor only one single node in an XML file and shows the value in one
channel. If you need to monitor more than one node of an XML document, please add the
sensor for each target node anew.
§ Knowledge Base: HTTP XML/REST Value Sensor: FAQ
type on each probe.
1002 12/11/2017

this sensor.
PRTG require?

Add Sensor
later.
SENSOR SETTINGS
Channel Name Enter a name for the channel that will display the value at the given
URL.
Sensor Settings
12/11/2017 1003
218 .
default value.
SENSOR SETTINGS
URL Enter the URL that returns the XML file. It has to be URL encoded! If
you enter an absolute URL, the sensor uses this address
device on which you create this sensor.
parent device's IP address/DNS name setting as part of the URL.
For more information, see section Smart URL Replacement
1015 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.
You can also check values in JavaScript Object Notation (JSON)
notation.
See section Checking JSON 1013 below.
1004 12/11/2017
SENSOR SETTINGS
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, see the Knowledge
Base: How can I use XPath with PRTG's XML/Rest Value Sensor?
HTTP Username If the URL requires authentication, enter the username. Please
enter a string or leave the field empty.
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 X ML Node
(and opt ional propert y ) field including possibly existing
namespace information.
§ Remove Namespaces: Ignore namespace information in the XML
document and process the value you enter in the X ML Node
(and opt ional propert y ) field as node names only.
For more information see About Namespaces 1015 section
below.
Content Type in Define what to include in the header of the request sent to the
Header URL defined above. Choose between:
12/11/2017 1005
SENSOR SETTINGS
§ 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 Cust om option
above. Enter a custom content type like text/xml or text/html.
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
The sensor does not accept header field names that include a
dash (–) character. If you want to use such an 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
Ensure that the HTTP header statement is valid! Otherwise, the
Characters to Remove This field is only visible if you enable the Use t he value of t he
select ed X ML 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 t he value of t he
select ed X ML node option above. If the sensor value of the
selected XML node is of the type float, you can define any
character here, which is then 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
If Channel Value Define what this sensor will do when the sensor value changes.
change.
1006 12/11/2017
SENSOR SETTINGS

The change notification for this sensor can only be triggered if
the returned value is a numerical value. Strings are not
supported by this option and cannot trigger a notification.
DEBU G OPTIONS
between:
SENSOR DISPLAY
12/11/2017 1007
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1008 12/11/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

12/11/2017 1009

time.


can choose between:
dependency.
1010 12/11/2017

menu bar.
12/11/2017 1011
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1012 12/11/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
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.
12/11/2017 1013
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
The sensor converts whitespaces in JSON keys into underscores (_). So, for example, if
you look for the node some node in the JSON, you need to enter some_node into the
node field. If you count the number of nodes (for example, some_node), both some node and
some_node would be counted if they appear in the JSON.
If a key exists more than once in the JSON, the value of the first appearance is returned
(no difference between whitespace and underscore).
1014 12/11/2017
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.

www.example.com/
12/11/2017 1015
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: Why does my HTTP XML/REST Value Sensor return a 404 error?
why?

Notifications
Others
1016 12/11/2017
57 Hyper-V Cluster Shared Volume Disk Free Sensor
7.8.57 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
Remarks
§ Requires 1018 Remote PowerShell on the target device.
§ Requires 1018 WSFC PowerShell Interface on the target device.
sensor on.
§ 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?
type on each probe.
12/8/2017 1017
Requirement: Remote PowerShell

The Hyper-V Cluster Shared Volume Disk Free sensor uses PowerShell commands. To
monitor devices with this sensor Remot e PowerShell has to be enabled.
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 detailed
information, see the Knowledge Base article How can I increase memory for Remote
PowerShell?
Requirement: WSFC PowerShell Interface

This sensor type needs the WSFC (Windows Server Failover Clust ering) PowerShell
Int erface 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 Server 2008 (not officially supported) and Windows Server 2012 the interface
is part of the VMM Administrator Console, or the VMM 2012 Management Console.
The interface is available everywhere 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 10, Windows 8.1, Windows 8, Windows 7 (SP1).

this sensor.
PRTG require?
Add Sensor
later.
Select the disks you want to monitor. PRTG creates one sensor for each disk you choose in
1018 12/8/2017
DISK FR EE SETTINGS
Disk Select the disks you want to add a sensor for. You see a list with
Ensure the resource name of your disks do not contain
unsupported characters, especially avoid the hash (#) sign. In
general, UTF-8 characters are supported. We recommend that you
do not rename resource disk names once you have set up
monitoring. For detailed information, see the Knowledge Base
article Why don't my Hyper-V sensors work after changing names?
Sensor Settings
218 .
default value.
12/8/2017 1019
DISK FR EE SETTINGS
Disk Shows the name of the disk. Once a sensor is created, you cannot
between:
SENSOR DISPLAY
1020 12/8/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
12/8/2017 1021
SCANNING INTER VAL

requests.
requests.
apply.


1022 12/8/2017

time.


can choose between:
dependency.
12/8/2017 1023
menu bar.
1024 12/8/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
12/8/2017 1025
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: Why don't my Hyper-V sensors work after changing names?

1026 12/8/2017
Notifications
Others
12/8/2017 1027
58 Hyper-V Host Server Sensor
7.8.58 Hy per-V Host Server Sensor
The Hyper-V Host Server sensor monitors a Microsoft Hyper-V host server via Windows
Management Instrumentation (WMI) or Windows Performance Counters, as configured in the
"Windows Compatibility Options" of the parent device.
§ CPU usage in percent of guests, hypervisor, 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
Remarks
sensor on.
§ Requires 1029 Windows Server 2008 R2 or later on the probe system.
§ Requires 1029 the Remote Registry Windows service to be running on the target computer.
§ The parent device for this sensor must be a Windows server running Hyper-V.
§ Can use a hybrid approach 1029 with Windows Performance Counters and WMI as fallback to
query data. Please stay below 200 WMI sensors per probe!
1028 11/24/2017

Requires credentials for Windows systems to be defined for the device you want to use
the sensor on. In the parent device's 390 Credent ials for Windows Sy st ems settings,
please prefer using Windows domain credentials.
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, a connection via Performance Counters will not be possible. However,
WMI connections may still work.
Hybrid Approach: Performance Counters and WMI

By default, this sensor type uses Windows Management Instrumentation (WMI) to request
monitoring data. You can change the default behavior to a hybrid approach in the
Windows Compat ibilit y Opt ions of the parent device's settings 398 on which you create this
sensor: if you choose this option, the sensor will first try to query data via Windows
Performance Counters and use WMI as a fallback if Performance Counters are not available.
When running in fallback mode, the sensor will re-try to connect via Performance Counters
after 24 hours.
Sensors using the Windows Management Instrumentation (WMI) protocol have high impact
on the system performance! Try to stay below 200 WMI sensors per probe 117 . Above this
number, please consider using multiple Remot e Probes 3359 for load balancing.
For a general introduction to the technology behind WMI, please see Monit oring via WMI
3244 section.
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 3359 .
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.
11/24/2017 1029
Add Sensor
later.
Sensor Settings
218 .
default value.
DEBU G OPTIONS
1030 11/24/2017
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
11/24/2017 1031
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1032 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1033

can choose between:
dependency.
menu bar.
1034 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

11/24/2017 1035
Notifications
Others
1036 11/24/2017
59 Hyper-V Virtual Machine Sensor
7.8.59 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 Management Instrumentation (WMI) or Windows Performance
Counters, as configured in the "Windows Compatibility Options" of the parent device.
§ CPU usage in percent of guests, hypervisor, total

§ IDE disk read speed (bytes per second)
§ IDE disk write speed (bytes per second)
sensor setup.
Hy per-V Virtual Mac hine Sensor
Remarks
sensor on.
§ The parent device for this sensor must be a Hyper-V server.
§ The sensor does not support Live Migration.
11/24/2017 1037
§ To monitor a virtual machine with this sensor, disable User Account Control (UAC) in the
control panel of the Windows operating system that 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.


after 24 hours.
3244 section.


may still work.
1038 11/24/2017
Add Sensor
later.
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,
including the ones that are not running. You see a list with the
names of all items that are available to monitor. Add check marks in
front of the respective lines to select the desired items. PRTG
creates one sensor for each selection. You can also use the check
box in the table head to select and deselect all items.
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, see the Knowledge Base article Why don't
my Hyper-V sensors work after changing names?
Sensor Settings
11/24/2017 1039
218 .
default value.
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:
1040 11/24/2017
· Alarm when powered off: The sensor will change to a Down

status 183 if the virtual machine is powered off. While in Down
status, a sensor does not record any data in any of its channels.
· Ignore powered off st at e: The sensor will not change to a
Down status 183 if the virtual machine is powered off. It will
report zero values instead.
between:
SENSOR DISPLAY
for each channel.
11/24/2017 1041
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
1042 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


time.
11/24/2017 1043


can choose between:
dependency.
1044 11/24/2017

menu bar.
11/24/2017 1045
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: Why don't my Hyper-V sensors work after changing names?

Notifications
1046 11/24/2017
Others
11/24/2017 1047
60 Hyper-V Virtual Network Adapter Sensor
7.8.60 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 Management Instrumentation (WMI) or Windows
Performance Counters, 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.
Hy per-V Virtual Network Adapter Sensor
Remarks
sensor on.
1048 11/24/2017


after 24 hours.
3244 section.

11/24/2017 1049

may still work.
Add Sensor
later.
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 choose will be valid for all sensors
that you create when you finish this dialog.
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 that are available to
monitor. Add check marks in front of the respective lines to select
the desired items. PRTG creates one sensor for each selection.
You can also use the check box in the table head to select and
deselect all items.
We recommend you do not rename virtual machines once you
have set up monitoring. Renaming them will also change the
internal virtual network adapter names, so monitoring might be
interrupted. For detailed information about virtual machine naming,
see the Knowledge Base article Why don't my Hyper-V sensors
work after changing names?
Sensor Settings
1050 11/24/2017
218 .
default value.
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:
11/24/2017 1051
HYPER -V VIR TU AL NETWOR K ADAPTER SETTINGS

SENSOR DISPLAY
for each channel.
1052 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1053
SCANNING INTER VAL

apply.


time.

1054 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1055

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: Why don't my Hyper-V Virtual Machine sensors work after changing names?
1056 11/24/2017

Notifications
Others
11/24/2017 1057
61 Hyper-V Virtual Storage Device Sensor
7.8.61 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 Management Instrumentation (WMI) or Windows Performance
Counters, as configured in the "Windows Compatibility Options" of the parent device.
§ Read speed in bytes per second

§ Write speed in bytes per second
§ Number of errors
sensor setup.
Hy per-V Virtual Storage Dev ic e Sensor
Remarks
sensor on.
§ This sensor does not support Live Migration.
1058 11/24/2017


after 24 hours.
3244 section.


may still work.
11/24/2017 1059
Add Sensor
later.
Select the storage devices you want to monitor. PRTG creates one sensor for each storage
HYPER -V VIR TU AL STOR AGE DEVICE SETTINGS
Virtual Storage Device Select the virtual storage devices you want to add a sensor for.
You see a list with the names of all items that are available to
deselect all items.
Sensor Settings
218 .
1060 11/24/2017
default value.
HYPER -V VIR TU AL STOR AGE DEVICE SETTINGS
Virtual Storage Device Shows the unique identifier of the device that this sensor
between:
11/24/2017 1061
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1062 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1063

time.


can choose between:
dependency.
1064 11/24/2017

menu bar.
11/24/2017 1065
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
1066 11/24/2017
62 IMAP Sensor
7.8.62 IM AP Sensor
The IMAP sensor monitors an email server using Internet Message Access Protocol (IMAP).
§ Response time of the email 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 the Knowledge Base article How can I monitor my backup software to
be sure backup succeeded last night?
IMAP Sensor
Remarks
§ 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.
§ This sensor type might not work properly when monitoring subfolders 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?
§ Knowledge Base: How can I monitor my backup software to be sure backup succeeded last
night?
§ Knowledge Base: Can I analyze multipart emails using the PRTG IMAP sensor?
11/24/2017 1067
62 IMAP Sensor
§ Knowledge Base: My IMAP sensor does not find emails when I check for message date. What
can I do?
Add Sensor
later.
Sensor Settings
218 .
default value.
1068 11/24/2017
62 IMAP Sensor
CONNECTIVITY
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.
If you do not get a connection, please try another port
number.
Security 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 to connect to the server
using TLS and StartTLS. If the server does not support this, the
sensor will try to connect without encryption.
§ Use Transport -Level Securit y if available: Choose this option
to try to connect to the server using TLS. If the server does not
support this, the sensor will try to connect 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 183 .
§ Enforce Transport -Level Securit y : Choose this option to try to
connect to the server using TLS. If the server does not support
this, the sensor will show a Down status 183 .
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.
11/24/2017 1069
62 IMAP Sensor
AU THENTICATION
Username Enter a username for IMAP authentication. Please enter a string.
Password Enter a password for IMAP authentication. Please enter a string.
Mailbox Name Enter the name of the mailbox (for example, the name of the IMAP
folder) that the sensor will check. 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.
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.
SENSOR BEHAVIOR
General Behavior This sensor can additionally check the content of all incoming
emails. Choose between:
§ Check connect ivit y only , do not process emails (default ):
Only check availability of the IMAP server and check if a login is
successful. Do not process any emails in the IMAP email account.
§ Count emails in t his mailbox: Count the emails in the defined
mailbox.
§ Process emails in t his mailbox: Log in to the IMAP email
account and check the emails that it contains. Define further
options below.
between:
1070 11/24/2017
62 IMAP Sensor
FILTER EMAILS IN INBOX
This settings section is only visible if you choose to process the emails in the mailbox.
Only Include Emails Define if you want to check the "From" field of the emails. When
with Matching "From" using a search, the sensor will scan all emails from the newest to
the oldest. Choose between:
§ Do not check (default ): 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.

Expressions 3355 .
The sensor finishes the scan with the first match! This means
that after it has found a match in one email, the sensor will not
perform any further checks 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.
Only Include Emails Define if you want to check the "Subject" field of the emails. When
with Matching "Subject" using a search, the sensor will scan all emails from the newest to
the oldest. Choose between:
§ Do not check (default ): Do not process the subject of emails.
§ Check using st ring search: Process the subject of emails using
simple string search.
§ Check using regular expression: Process the subject of emails
using a regular expression. For more information about syntax,
see the Regular Expressions 3355 section.

Expressions 3355 .
Search for This field is only visible if you enable a "subject" check above. Enter
a search string using the method defined above.
11/24/2017 1071
62 IMAP Sensor
FILTER EMAILS IN INBOX
Only Include Emails Define if you want to check the email body of the emails. When
with Matching Email using a search, the sensor will scan all emails from the newest to
Body the oldest. Choose between:
§ Do not check (default ): Do not process the email body.
§ Check using st ring search: Process the email body using simple
string search.
§ Check using regular expression: Process the email body using
a regular expression. For more information about syntax, see
the Regular Expressions 3355 section.

Expressions 3355 .
Search for This field is only visible if you enable checking the email body
above. Enter a search string using the method defined above.
Only Include Recent Define if you want to check all emails in the mailbox, or only mails
Emails that were received within the last few hours. Choose between:
§ Do not check message age (default ): Always check all emails
that the mailbox contains.
§ Emails must be y ounger t han: Only check emails that were
received in the last few hours. Define below.
Maximum Age in Hours This field is only visible if you enable the message age check
above. Enter the maximum age in hours. The sensor will only
process emails that are younger. Please enter an integer value.
If No Email Matches the Define which status 183 the sensor will show if it does not find any
Above Filters email in the mailbox that matches the defined filters. Choose
between:
§ Set sensor t o "Up" st at us (default )
§ Set sensor t o "Warning" st at us
§ Set sensor t o "Down" st at us
Message This field is only visible if you define a Warning or Down status as
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.
1072 11/24/2017
62 IMAP Sensor
VALIDATE LATEST EMAIL
This settings section is only visible if you choose to process the emails in the mailbox.
The sensor will only validate the latest email that matches the filters above! If the sensor
does not find a matching email, it will not perform any email validation.
For the Latest Email Define in which cases the sensor will show a Warning status 183 .
that Matches, Set Choose between:
Sensor to "Warning"
Status § 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: Set the sensor to Warning if the subject of
the found email contains the search text you define below.
§ If subject does not cont ain: Set the sensor to Warning if the
subject of the found email does not contain the search text you
define below.
§ If email body cont ains: Set the sensor to Warning if the body
of the found email contains the search text you define below.
§ If email body does not cont ain: Set the sensor to Warning if
the body of the found email does not contain the search text
you define below.
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 email subject or body using simple
string search.
§ Regular expression: Check the email subject or body using a
regular expression. For more information about syntax, see
Regular Expressions 3355 section.

Expressions 3355 .
Search Text This setting is only visible if you select an if condition above. Enter
11/24/2017 1073
62 IMAP Sensor
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
183 .
Based on Message Define if you want to check the age of the latest matching email in
Age, Set Sensor to the mailbox. Choose between:
"Warning" Status
§ Never (default ): Do not check the age of the email.
§ If email is older t han: Set the sensor to Warning status 183 if
the found email is older than you define below.
Message Age in Hours This field is only visible if you enable the message age check
above. Enter the maximum age in hours. If the processed email is
older, the sensor will show a Warning status 183 . Please enter an
integer value.
Ensure you do not manually edit emails in this mailbox with
another email client because this can result in malfunctions of
the message age check.
For the Latest Email Define in which cases the sensor will show a Down status 183 .
that Matches, Set Choose between:
Sensor to "Down"
Status § 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: Set the sensor to Down if the subject of
§ If subject does not cont ain: Set the sensor to Down if the
subject of the found email does not contain the search text you
define below.
§ If email body cont ains: Set the sensor to Down if the body of
§ If email body does not cont ain: Set the sensor to Down if the
body of the found email does not contain the search text you
define below.
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 email subject or body using simple
string search.
1074 11/24/2017
62 IMAP Sensor
§ Regular expression: Check the email subject or body using a

regular expression. For more information about syntax, see
Regular Expressions 3355 section.

Expressions 3355 .
Search Text This setting is only visible if you enable an if condition above. Enter
Error Message This setting is only visible if you select a down condition above.
Define the message that the sensor will show for a Down status
183 .
SENSOR DISPLAY
for each channel.
11/24/2017 1075
62 IMAP Sensor
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1076 11/24/2017
62 IMAP Sensor
SCANNING INTER VAL

apply.


time.

11/24/2017 1077
62 IMAP Sensor

can choose between:
dependency.
menu bar.
1078 11/24/2017
62 IMAP Sensor

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: How can I monitor my backup software to be sure backup succeeded last
night?
11/24/2017 1079
62 IMAP Sensor
Knowledge Base: My IMAP sensor does not process HTML emails correctly using regex. What
can I do?
Knowledge Base: Can I analyze multipart emails using the PRTG IMAP sensor?
Knowledge Base: My IMAP sensor does not find emails when I check for message date. What
can I do?

Notifications
Others
1080 11/24/2017
63 IP on DNS Blacklist Sensor
7.8.63 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
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 183 . 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. You can set additional thresholds in the Sensor
Channels Set t ings 2915 .
§ Knowledge Base: Is there a list of anti spam black list servers?
type on each probe.
11/24/2017 1081

this sensor.
PRTG require?
Add Sensor
later.
Sensor Settings
218 .
default value.
1082 11/24/2017
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, see this Knowledge Base article: Is there a
list of anti spam black list servers?
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 the error message Timeout (code: PE018).
DEBU G OPTIONS
between:
11/24/2017 1083
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
1084 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 1085

time.


can choose between:
dependency.
1086 11/24/2017

menu bar.
11/24/2017 1087
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: Is there a list of anti spam black list servers?
why?
1088 11/24/2017

Notifications
Others
11/24/2017 1089
64 IPFIX Sensor
7.8.64 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.
1090 11/24/2017
64 IPFIX Sensor
IPFIX Sensor
Remarks
§ 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?
§ Knowledge Base: What is the Active Flow Timeout in Flow sensors?
§ For a general introduction to the technology behind flow monitoring, please see manual
11/24/2017 1091
64 IPFIX Sensor
Add Sensor
later.
Sensor Settings
218 .
default value.
1092 11/24/2017
64 IPFIX Sensor
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.
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 you set this one minute longer than the
respective timeout configured in your hardware router device.
For more details about this setting,
see this Knowledge Base article: What is the Active Flow
Timeout in Flow sensors?
If you set this value too low, flow information might be lost!
Sampling Mode Define if you want to use the sampling mode. This setting must
match 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 On 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 you want the probe to write a logfile of the stream and
Disk (for Debugging) packet data to the data folder (see Dat a St orage 3383 ). Choose
between:
§ None (recommended): Do not write additional logfiles.
Recommended for normal use cases.
11/24/2017 1093
64 IPFIX Sensor
§ Only for t he 'Ot her' channel: Only write logfiles of data that is
not filtered otherwise and therefore accounted to the default
Ot her channel.
§ All st ream dat a: Write logfiles for all data received.
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.
§ Remot e Cont rol: Traffic caused by remote control applications,
such as RDP, SSH, Telnet, and VNC.
§ Infrast ruct ure: Traffic caused by network services, such as
DHCP, DNS, Ident, ICMP, and 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, that is, how detailed the sensor divides the
traffic. For each group, choose between:
§ No: Do not account traffic of this group in its 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.
1094 11/24/2017
64 IPFIX Sensor
§ 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.
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.
You can change the default configuration for groups and
channels. For details, see this Knowledge Base article: How
can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
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, see section Filt er Rules 1101 below.
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.
SENSOR DISPLAY
for each channel.
11/24/2017 1095
64 IPFIX Sensor
SENSOR DISPLAY

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
SCANNING INTER VAL
information.
1096 11/24/2017
64 IPFIX Sensor
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1097
64 IPFIX Sensor

time.


can choose between:
dependency.
1098 11/24/2017
64 IPFIX Sensor

menu bar.
11/24/2017 1099
64 IPFIX Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1100 11/24/2017
64 IPFIX Sensor
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
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, see section Toplist s 2940 .
Filter Rules
The following filter rules apply to all xFlow, IPFIX, and Packet Sniffer sensors.
FIELD POSSIBLE FILTER VALU ES
IP IP address or DNS name (see Valid Data Formats 3340 )
Port Any number
SourceIP IP address or DNS name (see Valid Data Formats 3340 )
SourcePort Any number
DestinationIP IP address or DNS name (see Valid Data Formats 3340 )
DestinationPort Any number
11/24/2017 1101
64 IPFIX Sensor
Protocol TCP, UDP, ICMP, OSPFIGP, any number
TOS Type Of Service: any number
DSCP Differentiated Services Code Point: any number
The following filter rules apply to IPFIX sensors only.
Interface Any number
ASI Any number
InboundInterface Any number
OutboundInterface Any number
SenderIP IP of the sending device. This is helpful if several devices send flow
data on the same port, and you want to divide the traffic of each
device into a different sensor channel.
Possible values: IP address or DNS name (see Valid Data Formats
3340 )
SourceASI Any number
DestinationASI Any number
MAC Physical address
SourceMAC Physical address
DestinationMAC Physical address
Mask Mask values represent subnet masks in with a single number

(number of contiguous bits).
DestinationMask Mask values represent subnet masks in with a single number

1102 11/24/2017
64 IPFIX Sensor
NextHop IP address or DNS name (see Valid Data Formats 3340 )
VLAN VLAN values represent a VLAN identifier (any number)
SourceVLAN VLAN values represent a VLAN identifier (any number)
DestinationVLAN VLAN values represent a VLAN identifier (any number)
More
Paessler Website: Paessler NetFlow Testers
§ https://www.paessler.com/tools/netflowtester
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
Knowledge Base: What is the Active Flow Timeout in Flow sensors?

Notifications
Others
Related Topics
§ Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 3337
§ Channel Defint ions for xFlow, IPFIX , and Packet Sniffer Sensors 3342
11/24/2017 1103
65 IPFIX (Custom) Sensor
7.8.65 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 according to your needs.
sensor setup.
IPFIX Sensor
Remarks
§ 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).
1104 11/24/2017

Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1105
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.
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. The IP address selected here must match the one configured
in the IPFIX export options of your hardware router device.
(Minutes) received. If the timeout is reached and no new data is received, the
sensor may switch to an Unknown status 183 . Please enter an
integer value.
We recommend you set this one minute longer than the respective
timeout configured in your hardware router device.
1106 11/24/2017
below.
number that matches the sampling rate in your device that exports
the flows. If the number is different, monitoring results will be
incorrect. Please enter an integer value.
Channel Definition Enter a channel definition to divide the traffic into different
channels. Write each definition in one line. All traffic for which no
channel is defined will be accounted to the default channel named
Ot her.
For detailed information,
see section Channel Definit ions for xFlow and Packet
Sniffer Sensors 3342 .
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.
between:
Ot her channel.
purposes only.
SENSOR DISPLAY
11/24/2017 1107
SENSOR DISPLAY
for each channel.
FILTER ING
syntax.
PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
1108 11/24/2017
PR IMAR Y TOPLIST
§ Top Prot ocols

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1109
SCANNING INTER VAL

apply.


time.

1110 11/24/2017


can choose between:
dependency.
menu bar.
11/24/2017 1111
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1112 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
11/24/2017 1113
The following filter rules apply to IPFIX sensors only.
ASI Any number
3340 )

1114 11/24/2017

More
Sniffer sensors?

Notifications
Others
Related Topics
11/24/2017 1115
66 IPMI System Health Sensor
7.8.66 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
Remarks
§ You have to explicitly specify the credentials of the IPMI in the sensor settings.
1116 11/24/2017

this sensor.
PRTG require?
Add Sensor
later.
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 309 . 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
11/24/2017 1117
IPMI SPECIFIC
Group Select the measurements you want to add a sensor for. You see a
list with the names of all items that are available to monitor. Add
check marks in front of the respective lines to select the desired
items. PRTG creates one sensor for each selection. You can also
use the check box in the table head to select and deselect all
items.
Sensor Settings
218 .
default value.
1118 11/24/2017
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.
IPMI SPECIFIC
Group Shows the metric that this sensor monitors. Once a sensor is
anew.
Logfile Results Define what PRTG will do with the sensor results. Choose
between:
SENSOR DISPLAY
11/24/2017 1119
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1120 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1121

time.


can choose between:
dependency.
1122 11/24/2017

menu bar.
11/24/2017 1123
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1124 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 1125
67 jFlow V5 Sensor
7.8.67 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! There are several filter
options available to divide traffic into different channels.
§ Chat (IRC, AIM)

§ Citrix
§ NetBIOS
§ Total traffic
sensor setup.
1126 11/24/2017
67 jFlow V5 Sensor
jFlow V5 Sensor
Remarks
§ 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).
11/24/2017 1127
67 jFlow V5 Sensor
Add Sensor
later.
Sensor Settings
218 .
default value.
1128 11/24/2017
67 jFlow V5 Sensor
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.
When you configure the export, make sure you select the
appropriate jFlow version for this sensor.
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 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 you set this one minute
longer than the respective timeout configured in your hardware
router device.
For more details about this setting, see this Knowledge Base
article: What is the Active Flow Timeout in Flow sensors?
below.
11/24/2017 1129
67 jFlow V5 Sensor
JFLOW V5 SPECIFIC SETTINGS
between:
Ot her channel.
purposes only.
UDP and TCP.
Ot her.
1130 11/24/2017
67 jFlow V5 Sensor
channel.
Sniffer sensors?
FILTER ING
syntax.
SENSOR DISPLAY
11/24/2017 1131
67 jFlow V5 Sensor
SENSOR DISPLAY

for each channel.
PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
SCANNING INTER VAL
information.
1132 11/24/2017
67 jFlow V5 Sensor
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1133
67 jFlow V5 Sensor

time.


can choose between:
dependency.
1134 11/24/2017
67 jFlow V5 Sensor

menu bar.
11/24/2017 1135
67 jFlow V5 Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1136 11/24/2017
67 jFlow V5 Sensor
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
11/24/2017 1137
67 jFlow V5 Sensor
The following filter rules apply to jFlow V5 sensors only.
ASI Any number
3340 )
More
Knowledge Base: Where is the volume line in graphs?
1138 11/24/2017
67 jFlow V5 Sensor

Notifications
Others
Related Topics
11/24/2017 1139
68 jFlow V5 (Custom) Sensor
7.8.68 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! In
this custom sensor, you can define your own channel definitions to divide traffic into different
channels.
sensor setup.
jFlow V5 Sensor
Remarks
§ You have to enable jFlow export of the respective version on the monitored device for this
1140 11/24/2017

Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1141
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
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 you set this one minute
longer than the respective timeout configured in your hardware
router device.
1142 11/24/2017
JFLOW SPECIFIC SETTINGS
below.
Ot her.
see section Channel Defint ions for xFlow and Packet Sniffer
Sensors 3342 .
between:
Ot her channel.
purposes only.
11/24/2017 1143
FILTER ING
syntax.
SENSOR DISPLAY
for each channel.
1144 11/24/2017
PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 1145
SCANNING INTER VAL

requests.
requests.
apply.


time.
1146 11/24/2017


can choose between:
dependency.
11/24/2017 1147

menu bar.
1148 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1149
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
1150 11/24/2017
The following filter rules apply to jFlow V5 sensors only.
ASI Any number
3340 )
More
11/24/2017 1151

Notifications
Others
Related Topics
1152 11/24/2017
69 LDAP Sensor
7.8.69 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, it will show an error message.
§ The sensor shows the response time of the server.
LDAP Sensor
Add Sensor
later.
Sensor Settings
11/24/2017 1153
69 LDAP Sensor
218 .
default value.
LDAP SPECIFIC
Port Enter the LDAP port number, usually port 389 for unencrypted
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.
1154 11/24/2017
69 LDAP Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1155
69 LDAP Sensor
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1156 11/24/2017
69 LDAP Sensor

time.


can choose between:
dependency.
11/24/2017 1157
69 LDAP Sensor

menu bar.
1158 11/24/2017
69 LDAP Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
11/24/2017 1159
70 Microsoft OneDrive Sensor
7.8.70 M icrosoft OneDrive Sensor
The Microsoft OneDrive sensor monitors a Microsoft OneDrive Personal account using the
OneDrive Application Programming Interface (API) and OAuth2. It shows the following:
Mic rosoft OneDriv e Sensor
Remarks
1168 .
§ This sensor type only supports OneDrive Personal, it does not work with OneDrive Business.
Add Sensor
later.
1160 11/24/2017
MICR OSOFT CR EDENTIALS
This sensor type uses OAuth2 authentication to get access to your Microsoft account.
For details about the authentication approach, see section Aut hent icat ion Using
OAut h2 1168 .
OAuth URL Click the button Get Access Code to connect this sensor to your
Microsoft account using OAuth2. This is necessary to allow the
sensor to query data from OneDrive.
A new browser window appears. Please follow the steps there and
confirm the permission for PRTG to connect to your OneDrive
account. OneDrive forwards you to an empty page after
completing the authorization process. Copy the complete URL of
this empty page and paste it into the OAut h Code field below.
OAuth Code Paste the complete URL from the address bar of your browser on
the empty page to which OneDrive forwards you. The empty page
appears after completing the authorization process for PRTG at
your OneDrive account. Click OK to define the sensor settings 866 .
It is mandatory to connect this sensor to your OneDrive
account to create this sensor. Please complete the OAuth
approach first to get the OAuth code.
Sensor Settings
218 .
11/24/2017 1161
default value.
MICR OSOFT CR EDENTIALS
to your OneDrive account. Once a sensor is created, you cannot
SENSOR DISPLAY
for each channel.
1162 11/24/2017
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
11/24/2017 1163
SCANNING INTER VAL

requests.
apply.


time.
1164 11/24/2017


can choose between:
dependency.
11/24/2017 1165

menu bar.
1166 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1167
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om


service.
permission page.
1168 11/24/2017

in PRTG.

Notifications
Others
11/24/2017 1169
71 Microsoft SQL v2 Sensor
7.8.71 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 given query
Mic rosoft SQL v 2 Sensor
Remarks
probe above.
selection)
1170 11/24/2017
depending on it?
the probe computer?
§ Save the SQL script with the query into the \Cust om Sensors\sql\mssql subfolder of your
find this path.
§ This sensor type supports Microsoft SQL server 2005 or later.

this sensor.
PRTG require?
Add Sensor
later.
Sensor Settings
11/24/2017 1171
218 .
default value.
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:
1172 11/24/2017
DATABASE SPECIFIC
§ 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 prevent "man in the middle" attacks.
The sensor validates the certificate only if the database
server enforces encryption!
DATA
cluster node!
be transferred,
computer?
SQL Variables
11/24/2017 1173
DATA
below.
executed.
1174 11/24/2017
DATA

Choose between:
below.
value was found.
11/24/2017 1175
DATA
1176 11/24/2017
DATA
table.
between:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Value Lookup
11/24/2017 1177
DATA
Choose between:
1178 11/24/2017
DATA
will be added.
change.
between:
SENSOR DISPLAY
11/24/2017 1179
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
1180 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


11/24/2017 1181

time.


can choose between:
dependency.
1182 11/24/2017
menu bar.
11/24/2017 1183
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1184 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
depending on it?
probe computer?
PRTG Manual:
11/24/2017 1185

Notifications
Others
1186 11/24/2017
72 MySQL v2 Sensor
7.8.72 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
My SQL v 2 Sensor
Remarks
probe above.
selection)
11/24/2017 1187
72 MySQL v2 Sensor
depending on it?
the probe computer?
§ 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.
PRTG require?
Add Sensor
later.
Sensor Settings
1188 11/24/2017
72 MySQL v2 Sensor
218 .
default value.
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.
11/24/2017 1189
72 MySQL v2 Sensor
DATA
cluster node!
be transferred,
computer?
SQL Variables
1190 11/24/2017
72 MySQL v2 Sensor
DATA

below.
executed.
11/24/2017 1191
72 MySQL v2 Sensor
DATA
Choose between:
below.
value was found.
1192 11/24/2017
72 MySQL v2 Sensor
DATA

table.
between:
§ BytesBandwidth
11/24/2017 1193
72 MySQL v2 Sensor
DATA
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Value Lookup
Choose between:
1194 11/24/2017
72 MySQL v2 Sensor
DATA
will be added.
change.
between:
11/24/2017 1195
72 MySQL v2 Sensor
DATA

SENSOR DISPLAY
for each channel.
1196 11/24/2017
72 MySQL v2 Sensor
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1197
72 MySQL v2 Sensor
SCANNING INTER VAL

apply.


time.

1198 11/24/2017
72 MySQL v2 Sensor

can choose between:
dependency.
menu bar.
11/24/2017 1199
72 MySQL v2 Sensor

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1200 11/24/2017
72 MySQL v2 Sensor
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
depending on it?
probe computer?
PRTG Manual:
11/24/2017 1201
72 MySQL v2 Sensor

Notifications
Others
1202 11/24/2017
73 NetApp Aggregate Sensor
7.8.73 NetApp Aggregate Sensor
The NetApp Aggregate sensor monitors the status of a NetApp cDOT or ONTAP storage
aggregate accessing the Application Programming Interface (API) via Simple Object Access
Protocol (SOAP). It can show the following:
§ Number of files on the aggregate

§ Number of disks on the aggregate
§ Status of the aggregate (online, restrict, offline, other error)
§ Read and written blocks per second
§ User reads and writes per seconds
§ Free bytes in total and percent
NetApp Aggregate Sensor
Remarks
§ This sensor type supports the NetApp cDOT 8.3 and NetApp ONTAP 9.0 or later.
11/24/2017 1203
§ The ONTAPI user account that you use with this sensor needs access 1204 to ONTAPI (DATA
ONTAP API) so that the sensor can request data from it. The access is enabled by default.
§ The NetApp System Health sensor requires admin permissions for the ONTAPI user account
that you use to access ONTAPI. For other NetApp sensors, read-only user rights are
sufficient. Modify or add this user with a suitable role in the console under Clust er |
Clust erX | Configurat ion | Securit y | Users
§ As alternative to admin permissions for the NetApp System Health sensor, you can add a
specific Role At t ribut e and use read-only rights. For details, see PRTG Manual: Net App
Sy st em Healt h Sensor—Permissions: Alt ernat ive t o Admin Right s 1278
§ You can define NetApp API credentials (User and Password) in the parent device settings 390
in section Credent ials for Windows Sy st ems. This way, you will not have to individually
enter credentials for each NetApp sensor that you add to the same device.
§ Requires .NET 4.5 on the probe system.
§ This sensor type supersedes the deprecated NetApp cDOT Aggregate (SOAP) sensor.

this sensor.
PRTG require?
Requirement: Enabled ONTAPI Access

NetApp sensors require access to ONTAPI for the utilized user account, which is enabled by
default. If access is disabled, use the following command locally on the cluster console to
enable ONTAPI access for the user:
services web> modify -vserver clusterd -name ontapi -enabled true
1204 11/24/2017
Add Sensor
later.
Select the aggregates that you want to monitor. PRTG will create one sensor for each
aggregate you choose in the Add Sensor dialog. The settings you choose will be valid for all
NETAPP SPECIFIC
NetApp Aggregates Select all aggregates that you want to add a sensor to. You see a
items.
Sensor Settings
218 .
11/24/2017 1205
default value.
NETAPP CONNECTION
NetApp Credentials Specify which credentials you want to use to connect to the
NetApp API. Choose between:
§ Use explicit credent ials: Choose this option if you want to use
individual NetApp API credentials with this sensor.
§ Use Windows credent ials from parent device: If you choose
this option, the sensor will use the credentials (User and
Password) that you enter in the parent device settings 390 in
section Credent ials for Windows Sy st ems. Defining credentials
in the parent device is useful if you add several NetApp sensors
to this device because you will not have to individually enter
credentials for each NetApp sensor.
Username This field is only available if you select explicit credentials above.
Enter a username for access to the NetApp API. Read-only rights
for this ONTAP user account are sufficient. Please enter a string.
Password This field is only available if you select explicit credentials above.
Enter the password of the user that you entered above for access
to the NetApp API. Please enter a string.
Port Enter a port number on which you can access the NetApp API.
Please enter an integer value. The default port is 443.
1206 11/24/2017
NETAPP CONNECTION
Transport Type Define if the connection to the NetApp API is TLS/SSL secured.
Choose between:
§ HTTP: Use an unsecured HTTP connection.
§ HTTPS: Use a TLS/SSL secured connection to the defined port to
send the query.
NETAPP SPECIFIC
NetApp Aggregates Shows the aggregate that this sensor monitors. Once a sensor is
anew.
DEBU G OPTIONS
between:
11/24/2017 1207
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1208 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1209

time.


can choose between:
dependency.
1210 11/24/2017

menu bar.
11/24/2017 1211
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
1212 11/24/2017
Others
11/24/2017 1213
74 NetApp I/O Sensor
7.8.74 NetApp I/O Sensor
The NetApp I/O sensor monitors input and output operations of a NetApp cDOT or ONTAP
storage system accessing the Application Programming Interface (API) via Simple Object Access
§ Number of Common Internet File System (CIFS) operations per second

§ Disk read and write speed
§ Number of FCP operations per second
§ FCP read and write speed
§ HDD read and write speed
§ HTTP operations per second
§ Number of internet Small Computer System Interface (iSCSI) operations per second
§ iSCSI read and write speed
§ Number of iSCSI partner operations per second
§ iSCSI partner read and write speed
§ Network read and write speed
§ Number of Network File System (NFS) operations per second
§ SSD read and write speed
§ Tape read and write speed
1214 11/24/2017
NetApp I/O Sensor
Remarks
11/24/2017 1215

§ This sensor type supersedes the deprecated NetApp cDOT I/O (SOAP) sensor.

this sensor.
PRTG require?

Add Sensor
later.
Select the system nodes that you want to monitor. PRTG will create one sensor for each node
NETAPP SPECIFIC
NetApp System Nodes Select all nodes that you want to add a sensor to. You see a list
1216 11/24/2017
Sensor Settings
218 .
default value.
NETAPP CONNECTION
11/24/2017 1217
NETAPP CONNECTION

Choose between:
send the query.
NETAPP SPECIFIC
NetApp System Nodes Shows the ID of the system node that this sensor monitors. Once
the sensor anew.
1218 11/24/2017
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
11/24/2017 1219
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1220 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1221

can choose between:
dependency.
menu bar.
1222 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
11/24/2017 1223

Notifications
Others
1224 11/24/2017
75 NetApp LIF Sensor
7.8.75 NetApp LIF Sensor
The NetApp LIF sensor monitors logical interfaces of a NetApp cDOT or ONTAP cluster
accessing the Application Programming Interface (API) via Simple Object Access Protocol
(SOAP). It can show the following:
§ Number of sent and received packets per second

§ Amount of sent and received data per second
§ Number of sent and received errors per second
NetApp LIF Sensor
Remarks
11/24/2017 1225

this sensor.
PRTG require?

Add Sensor
later.
Select the logical interfaces that you want to monitor. PRTG will create one sensor for each LIF
1226 11/24/2017
NETAPP SPECIFIC
NetApp LIFs Select the logical interfaces you want to add a sensor to. You see
a list with the names of all items that are available to monitor. Add
items.
Sensor Settings
218 .
default value.
11/24/2017 1227
NETAPP CONNECTION
Choose between:
send the query.
NETAPP SPECIFIC
NetApp LIFs Shows the ID of the logical interface that this sensor monitors.
1228 11/24/2017
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
11/24/2017 1229
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1230 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1231

can choose between:
dependency.
menu bar.
1232 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
11/24/2017 1233

Notifications
Others
1234 11/24/2017
76 NetApp LUN Sensor
7.8.76 NetApp LUN Sensor
The NetApp LUN sensor monitors the logical unit number (LUN) of a NetApp cDOT or ONTAP
§ Status of the LUN:

· Online
· Offline due to a media error on the associated foreign LUN
· Offline due to an NVRAM failure
· Offline due to insufficient space

· Administratively offline or unknown reason
§ Free bytes in percent and total
§ Read and write operations per second
§ Read and write blocks per second
§ Other operations per second
§ Number of SCSI errors per second
§ Mapping status of the LUN (mapped: yes or no)
NetApp LUN Sensor
Remarks
12/11/2017 1235

this sensor.
PRTG require?

Add Sensor
later.
1236 12/11/2017
Select the LUNs that you want to monitor. PRTG will create one sensor for each LUN you
NETAPP SPECIFIC
NetApp LUNs Select the LUNs you want to add a sensor to. You see a list with
Sensor Settings
218 .
default value.
12/11/2017 1237
NETAPP CONNECTION
Choose between:
send the query.
1238 12/11/2017
NETAPP CONNECTION
NETAPP SPECIFIC
NetApp LUNs Shows the ID of the LUN that this sensor monitors. Once a sensor
anew.
DEBU G OPTIONS
between:
SENSOR DISPLAY
12/11/2017 1239
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1240 12/11/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

12/11/2017 1241

time.


can choose between:
dependency.
1242 12/11/2017

menu bar.
12/11/2017 1243
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
1244 12/11/2017
Others
12/11/2017 1245
77 NetApp NIC Sensor
7.8.77 NetApp NIC Sensor
The NetApp NIC sensor monitors the network interface controller (NIC) of a NetApp cDOT or
ONTAP cluster accessing the Application Programming Interface (API) via Simple Object Access
§ Sent and received bytes per second

§ Number of sent and received errors per second
§ Number of up to down links per seconds
NetApp NIC Sensor
Remarks
1246 11/24/2017

this sensor.
PRTG require?

Add Sensor
later.
Select the network interface controllers that you want to monitor. PRTG will create one sensor
for each NIC you choose in the Add Sensor dialog. The settings you choose will be valid for all
11/24/2017 1247
NETAPP SPECIFIC
NetApp NICs Select the NICs you want to add a sensor to. You see a list with
Sensor Settings
218 .
default value.
1248 11/24/2017
NETAPP CONNECTION
Choose between:
send the query.
NETAPP SPECIFIC
NetApp NICs Shows the ID of the NIC that this sensor monitors. Once a sensor
anew.
11/24/2017 1249
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
1250 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1251
SCANNING INTER VAL

apply.


time.

1252 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1253

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
1254 11/24/2017

Notifications
Others
11/24/2017 1255
78 NetApp Physical Disk Sensor
7.8.78 NetApp Phy sical Disk Sensor
The NetApp Physical Disk sensor monitors disks of a NetApp cDOT or ONTAP storage system
§ Latency of operations
§ Read and write speed of operations
§ Data read and write speed
NetApp Phy sic al Disk Sensor
Remarks
1256 11/24/2017
§ This sensor type supersedes the deprecated NetApp cDOT Physical Disk (SOAP) sensor.

this sensor.
PRTG require?

Add Sensor
later.
Select the disks you want to monitor. PRTG will create one sensor for each disk you choose in
11/24/2017 1257
NETAPP SPECIFIC
NetApp Disk Select all disks that you want to add a sensor to. You see a list
Sensor Settings
218 .
default value.
1258 11/24/2017
NETAPP CONNECTION
Choose between:
send the query.
NETAPP SPECIFIC
NetApp Disk Shows the disk that this sensor monitors. Once a sensor is
anew.
11/24/2017 1259
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
1260 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1261
SCANNING INTER VAL

apply.


time.

1262 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1263

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
1264 11/24/2017

Notifications
Others
11/24/2017 1265
79 NetApp SnapMirror Sensor
7.8.79 NetApp SnapM irror Sensor
The NetApp SnapMirror sensor monitors SnapMirror relationships of a NetApp cDOT or ONTAP
§ Health status (healthy y es or no)

§ Transfer status (relationship status returned from the API)
· Ok: idle, transferring, checking, quiescing, quiesced, queued, preparing, finalizing, aborting
· Warning: unknown, breaking
§ Lag transfer duration
§ Relationship type
· Ok: mirror, vault, mirror and vault
· Error: unknown
§ Size of last transfer
§ Duration of last transfer
§ Number of resync fails per second
§ Number of update fails per second
§ Mirror state
· Ok: snapmirrored
· Warning: uninitialized
· Error: broken-off, unknown
1266 11/24/2017
NetApp SnapMirror Sensor
Remarks
11/24/2017 1267

this sensor.
PRTG require?

Add Sensor
later.
Select the SnapMirrors you want to monitor. PRTG will create one sensor for each SnapMirror
1268 11/24/2017
NETAPP SPECIFIC
NetApp SnapMirrors Select all SnapMirrors that you want to add a sensor to. You see a
items.
Sensor Settings
218 .
default value.
11/24/2017 1269
NETAPP CONNECTION
Choose between:
send the query.
NETAPP SPECIFIC
NetApp SnapMirrors Shows the SnapMirror that this sensor monitors. Once a sensor is
anew.
1270 11/24/2017
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
11/24/2017 1271
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1272 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1273

can choose between:
dependency.
menu bar.
1274 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
11/24/2017 1275

Notifications
Others
1276 11/24/2017
80 NetApp System Health Sensor
7.8.80 NetApp Sy stem Health Sensor
The NetApp System Health sensor monitors the health of a NetApp cDOT or ONTAP storage
system accessing the Application Programming Interface (API) via Simple Object Access
§ Memory usage
§ CPU load
§ Uptime
§ Number of failed fans
§ Number of failed PSU
§ Node health (error or OK)
§ NVRAM battery status (error or OK)
§ Number of spare disks
§ Low spare disks as reported by the NetApp (yes or no)
§ Usable spare size
§ Temperature status (error or OK)
NetApp Sy stem Health Sensor
11/24/2017 1277
Remarks
§ This sensor type supersedes the deprecated NetApp cDOT System Health (SOAP) sensor.

this sensor.
PRTG require?

Permissions: Alternative to Admin Rights

If you do not want to provide admin rights for the ONTAPI user account that you use with the
NetApp System Health sensor, you can add a new command to the selected role of the user
that makes read-only rights sufficient.
1278 11/24/2017
§ Edit the Role of this user in the console under Clust er | Clust erX | Configurat ion |
Securit y | Users.
§ Add the command st orage aggregat e check_spare_low with ACL all to the Role
At t ribut es.
With this role attribute, read-only rights are sufficient for the NetApp System Health sensor.
Add Sensor
later.
Select the system nodes that you want to monitor. PRTG will create one sensor for each node
NETAPP SPECIFIC
NetApp System Nodes Select the nodes you want to add a sensor to. You see a list with
Sensor Settings
11/24/2017 1279
218 .
default value.
NETAPP CONNECTION
1280 11/24/2017
NETAPP CONNECTION
Choose between:
send the query.
NETAPP SPECIFIC
NetApp System Nodes Shows the ID of the system node that this sensor monitors. Once
the sensor anew.
DEBU G OPTIONS
between:
11/24/2017 1281
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
1282 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1283
SCANNING INTER VAL

apply.


time.

1284 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1285

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
1286 11/24/2017

Notifications
Others
11/24/2017 1287
81 NetApp Volume Sensor
7.8.81 NetApp Volume Sensor
The NetApp Volume sensor monitors volumes on a NetApp cDOT or ONTAP storage system
§ Free space for snapshots in percent and total

§ Busy snapshots in percent
§ Age of latest snapshot
§ Age of oldest snapshot
§ Total bytes of snapshots
§ Number of snapshots
§ Free physical bytes in percent and total
§ Free size in percent and total
§ Free files in percent and total
§ Compression savings in percent and total
§ Deduplication savings in percent and total
§ Total savings in percent and total
1288 12/11/2017
Remarks

this sensor.
PRTG require?

12/11/2017 1289
Add Sensor
later.
Select the volumes that you want to monitor. PRTG will create one sensor for each volume
NETAPP SPECIFIC
NetApp Volumes Select the volumes you want to add a sensor to. You see a list
Volumes that are offline will not appear in this list.
Sensor Settings
218 .
1290 12/11/2017
default value.
NETAPP CONNECTION
12/11/2017 1291
NETAPP CONNECTION
Choose between:
send the query.
NETAPP SPECIFIC
NetApp Volumes Shows the volume that this sensor monitors. Once a sensor is
anew.
DEBU G OPTIONS
between:
1292 12/11/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
12/11/2017 1293
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1294 12/11/2017

time.


can choose between:
dependency.
12/11/2017 1295

menu bar.
1296 12/11/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
12/11/2017 1297
Others
1298 12/11/2017
82 NetFlow V5 Sensor
7.8.82 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.
11/24/2017 1299
NetFlow V5 Sensor
Remarks
§ You must enable NetFlow export of the respective version on the monitored device for this
Sniffer sensors?
1300 11/24/2017
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1301
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
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 183 .
We recommend that you set the timeout one minute longer than
the respective timeout configured in your hardware router device.
The maximum timeout is 60 minutes.
If you set this value too low,
flow information might be lost!
For more details,
If the target device sends incorrect time information that
results in wrong monitoring data, please try to use 0 as active
flow timeout. This will ignore the start and stop information of a
flow as provided by the device and account all data to the current
point in time. It might result in spikes but all data will be captured.
1302 11/24/2017
below.
between:
Ot her channel.
purposes only.
UDP and TCP.
11/24/2017 1303
Ot her.
channel.
Sniffer sensors?
FILTER ING
syntax.
SENSOR DISPLAY
1304 11/24/2017
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
11/24/2017 1305
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

1306 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1307

menu bar.
1308 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1309
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
1310 11/24/2017
The following filter rules apply to NetFlow V5 sensors only.
ASI Any number
3340 )
More
Sniffer sensors?
11/24/2017 1311

Notifications
Others
Related Topics
1312 11/24/2017
83 NetFlow V5 (Custom) Sensor
7.8.83 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.
NetFlow V5 Sensor
Remarks
11/24/2017 1313

Add Sensor
later.
Sensor Settings
218 .
1314 11/24/2017
default value.

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.
When configuring export, please make sure you select the
11/24/2017 1315

For more details,
below.
Ot her.
see section Channel Definit ions for xFlow, IPFIX , and Packet
between:
Ot her channel.
1316 11/24/2017

purposes only.
FILTER ING
syntax.
SENSOR DISPLAY
for each channel.
11/24/2017 1317
SENSOR DISPLAY
PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
SCANNING INTER VAL
information.
1318 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1319

time.


can choose between:
dependency.
1320 11/24/2017

menu bar.
11/24/2017 1321
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1322 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
11/24/2017 1323
ASI Any number
3340 )
More
1324 11/24/2017

Notifications
Others
Related Topics
11/24/2017 1325
7.8.84 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.
1326 11/24/2017
NetFlow V9 Sensor
Remarks
Sniffer sensors?
11/24/2017 1327
Add Sensor
later.
Sensor Settings
218 .
default value.
1328 11/24/2017

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.
For more details,
11/24/2017 1329
below.
between:
Ot her channel.
purposes only.
UDP and TCP.
1330 11/24/2017
Ot her.
channel.
Sniffer sensors?
FILTER ING
syntax.
SENSOR DISPLAY
11/24/2017 1331
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
1332 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 1333

time.


can choose between:
dependency.
1334 11/24/2017

menu bar.
11/24/2017 1335
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1336 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
11/24/2017 1337
ASI Any number
3340 )


1338 11/24/2017
More
Sniffer sensors?

Notifications
Others
Related Topics
11/24/2017 1339
7.8.85 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
Remarks
1340 11/24/2017

Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1341

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.
When configuring export, please make sure you select the
1342 11/24/2017

For more details,
below.
Ot her.
see section Channel Definit ions for xFlow, IPFIX , and Packet
between:
Ot her channel.
11/24/2017 1343

purposes only.
FILTER ING
syntax.
SENSOR DISPLAY
for each channel.
1344 11/24/2017
SENSOR DISPLAY
PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1345
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1346 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1347

menu bar.
1348 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1349
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
1350 11/24/2017
ASI Any number
3340 )


11/24/2017 1351
More

Notifications
Others
Related Topics
1352 11/24/2017
86 Oracle SQL v2 Sensor
7.8.86 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
Remarks
probe above.
selection)
11/24/2017 1353
depending on it?
the probe computer?
§ 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.
PRTG require?
Add Sensor
later.
Sensor Settings
1354 11/24/2017
218 .
default value.
DATABASE SPECIFIC
Identifier Enter the Oracle System ID (SID) or the SERVICE_NAME of the

database the sensor will connect to. Specify below which type of
identifier you use. By default, the sensor uses the SID as
connection string.
The identifier is defined in the CONNECT_DATA part of the
TNSNames.ora file on the Oracle instance. For example, a system ID
can look like this: orcl
Identification Method Define which type of identifier you use to connect to the database.
This type depends on the configuration of your Oracle server.
Choose between:
§ Use SID as ident ifier (default ): Connect to the database
instance using a system ID as connection string. Enter the SID
above.
§ Use SERVICE_NAME as ident ifier: Connect to the database
instance using a SERVICE_NAME as connection string. Enter the
SERVICE_NAME above.
11/24/2017 1355
DATA
cluster node!
be transferred,
computer?
SQL Variables
1356 11/24/2017
DATA

below.
executed.
11/24/2017 1357
DATA
Choose between:
below.
value was found.
1358 11/24/2017
DATA

table.
between:
§ BytesBandwidth
11/24/2017 1359
DATA
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Value Lookup
Choose between:
1360 11/24/2017
DATA
will be added.
change.
between:
11/24/2017 1361
DATA

SENSOR DISPLAY
for each channel.
1362 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1363
SCANNING INTER VAL

apply.


time.

1364 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1365

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1366 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
depending on it?
probe computer?
PRTG Manual:
11/24/2017 1367

Notifications
Others
1368 11/24/2017
87 Oracle Tablespace Sensor
7.8.87 Oracle Tablespace Sensor
The Oracle Tablespace sensor monitors a tablespace on an Oracle server. It can show the
following:
§ Online status (online, system, recover, sysoff, offline, unknown)

§ Status (available, invalid, unknown)
§ Free disk space in bytes and percent
§ Number of free blocks and in percent
§ Current database size
§ Database size on disk (managed tablespace)
Orac le Tablespac e Sensor
Remarks
§ This sensor type supports Oracle database servers version 10.2 or higher.
§ Requires 1370 sufficient privileges for the account that you use for the connection. We
recommend that you use the SYSTEM account.
probe above.
11/24/2017 1369
§ PRTG Manual: Monit oring Dat abases 3271

this sensor.
PRTG require?
Requirement: Sufficient Account Privileges

Please use an account for the connection that has the privileges to see all (or specific) views.
We recommend that you use the SYSTEM account if possible, otherwise grant your DBA the
SELECT_CATALOG_ROLE to the account that you use. Without sufficient privileges you may see
the error message ORA-00942: table or view does not exist.
Add Sensor
later.
In the appearing dialog box in the Add Sensor dialog, enter an identifier 1371 to access the
tablespace selection and click OK. Select the tablespaces in the Oracle database you want to
monitor. PRTG creates one sensor for each tablespace you choose. The settings you choose
will be valid for all sensors that you create when you finish this dialog.
1370 11/24/2017
TABLESPACE SPECIFIC
Tablespace Select the tablespaces you want to add a sensor for. You see a list
Sensor Settings
218 .
default value.
11/24/2017 1371
OR ACLE SPECIFIC
Identifier Enter the Oracle System ID (SID) or the SERVICE_NAME of the

database the sensor will connect to. Specify below which type of
identifier you use. By default, the sensor uses the SID as
connection string.
The identifier is defined in the CONNECT_DATA part of the
TNSNames.ora file on the Oracle instance. For example, a system ID
can look like this: orcl
Identification Method Define which type of identifier that you use to connect to the
database. This type depends on the configuration of your Oracle
server. Choose between:
§ Use SID as ident ifier (default ): Connect to the database
instance using a system ID as connection string. Enter the SID
above.
§ Use SERVICE_NAME as ident ifier: Connect to the database
instance using a SERVICE_NAME as connection string. Enter the
SERVICE_NAME above.
Sensor Name Prefix Define if you want to use the SERVICE_NAME as prefix for the
sensor name. If you have multiple databases on your Oracle server,
this will help you to distinguish the monitored tablespaces.
Choose between:
§ Do not use a prefix for t he sensor name: The sensor name will
only show the name of the monitored tablespace.
§ Use SERVICE_NAME as prefix for t he sensor name: PRTG will
add the SERVICE_NAME to the beginning of the sensor name.
TABLESPACE SPECIFIC
Tablespace Shows the tablespace that this sensor monitors. Once a sensor is
anew.
1372 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1373
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1374 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1375

menu bar.
1376 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1377
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1378 11/24/2017
88 Packet Sniffer Sensor
7.8.88 Packet Sniffer Sensor
The Packet Sniffer sensor monitors the headers of data packets that pass a local network card
using a 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.
11/24/2017 1379
Pac ket Sniffer Sensor
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 3249 .
type on each probe.
By default, you can only monitor traffic passing the PRTG probe system where the Probe
Device with 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) that the switch sends a copy
of all traffic to. 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.
1380 11/24/2017
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1381
SNIFFER SPECIFIC
the sensor includes all traffic. To include specific traffic only, define
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.
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.
Log Stream Data to Define if the probe will write a logfile of the stream and packet data
Disk (for Debugging) to the data folder (see Dat a St orage 3383 ). Choose between:
§ None (recommended): Do not write additional logfiles. We
recommend this for normal use cases.
Ot her channel.
purposes only.
1382 11/24/2017

UDP and TCP.
Ot her.
channel.
Sniffer sensors?
SENSOR DISPLAY
for each channel.
11/24/2017 1383
SENSOR DISPLAY

PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
SCANNING INTER VAL
information.
1384 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1385

time.


can choose between:
dependency.
1386 11/24/2017

menu bar.
11/24/2017 1387
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1388 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
11/24/2017 1389
The following filter rules apply to Packet Sniffer sensors only.
MAC Physical address (see Examples 3340 )
EtherType IPV4, ARP, RARP, APPLE, AARP, IPV6, IPXold, IPX, any number
VlanPCP IEEE 802.1Q VLAN Priority Code Point
VlanID IEEE 802.1Q VLAN Identifier
TrafficClass IPv6 Traffic Class: corresponds to TOS used with IPv4
FlowLabel IPv6 Flow Label
More
Sniffer sensors?

1390 11/24/2017
Notifications
Others
Related Topics
11/24/2017 1391
89 Packet Sniffer (Custom) Sensor
7.8.89 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.
§ This sensor can show traffic by type individually to your needs.
sensor setup.
Pac ket Sniffer Sensor
Remarks
§ By default, this sensor works only on a probe device.
§ For a general introduction to the technology behind packet sniffing, please see manual
section Monit oring Bandwidt h via Packet Sniffing 3249 .
1392 12/11/2017
type on each probe.
By default, you can only monitor traffic passing the PRTG probe system where the Probe
Device with 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) that the switch sends a copy
of all traffic to. 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
later.
Sensor Settings
218 .
12/11/2017 1393
default value.
SNIFFER SPECIFIC
the sensor includes all traffic. To include specific traffic only, define
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.
channel is defined is accounted to the default channel named
Ot her.
Sensors 3342 .
1394 12/11/2017
SNIFFER SPECIFIC

filters for the data you really want to analyze. We recommend that
you do 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.
Log Stream Data to Define if the probe will write a logfile of the stream and packet data
Disk (for Debugging) to the data folder (see Dat a St orage 3383 ). Choose between:
Ot her channel.
Use with caution! Enabling this option might create huge data
files. Please use for a short time and for debugging purposes
only.
SENSOR DISPLAY
for each channel.
12/11/2017 1395
SENSOR DISPLAY

PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
SCANNING INTER VAL
information.
1396 12/11/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

12/11/2017 1397

time.


can choose between:
dependency.
1398 12/11/2017

menu bar.
12/11/2017 1399
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1400 12/11/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
12/11/2017 1401
The following filter rules apply to Packet Sniffer sensors only.
MAC Physical address (see Examples 3340 )
EtherType IPV4, ARP, RARP, APPLE, AARP, IPV6, IPXold, IPX, any number
VlanPCP IEEE 802.1Q VLAN Priority Code Point
VlanID IEEE 802.1Q VLAN Identifier
TrafficClass IPv6 Traffic Class: corresponds to TOS used with IPv4
FlowLabel IPv6 Flow Label
More

1402 12/11/2017
Notifications
Others
Related Topics
12/11/2017 1403
90 PerfCounter Custom Sensor
7.8.90 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.
§ This sensor can show Windows Performance Counters individually to your needs.
sensor setup.
To find available performance counters and their names on the target system,
see this Knowledge Base article: How can I find out the names of available Performance
Counters?
PerfCounter Custom Sensor
Remarks
§ Requires 1405 Windows credentials in the parent device settings.
§ Requires 1405 the Windows Remote Registry service to be running on the target computer.
§ 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?
§ You cannot add different performance counters with the same name to one sensor.
1404 11/24/2017
§ If a performance counter contains angle brackets (< or >), please do not edit the channel
settings because this might cause an error.

computer. If you fail to do so, a connection via Performance Counters will not be possible.
The user account has to be a member of the Performance Monitor Users user group on
the target system.

the RemoteRegistry "Remote Registry" Windows service is running on the target
Windows version 2008 R2 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
Add Sensor
later.
11/24/2017 1405
PER FOR MANCE COU NTER SETTINGS
List of Counters Enter a list of performance counters that 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(_Tot al)\% Processor Time::%
It is not possible to monitor different performance counters
with the same name in one sensor. The sensor uses the
counter as channel name, so this would create duplicate channels,
which PRTG does not support. If you want to monitor different
performance counters with the same name, please add one sensor
for each counter. You can also create a custom sensor 2911 . For
example, you can write a PowerShell query that connects to the
target device, retrieves the desired counters with the Get-Counter
cdmlet, and reports them back to PRTG as individual channels.
If your custom performance counter includes an angle bracket
(< or >), please do not edit the Sensor Channels Set t ings 2915
(for example, limits) after creating the sensor! This might lead to a
malfunctioning sensor.
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.
Make sure that all counters that you monitor are capable of
this mode if you select it.
Sensor Settings
1406 11/24/2017
218 .
default value.
PER FOR MANCE COU NTER SETTINGS
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
11/24/2017 1407
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1408 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1409

time.


can choose between:
dependency.
1410 11/24/2017

menu bar.
11/24/2017 1411
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1412 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: How can I find out the names of available Performance Counters?
Knowledge Base: Remote Monitoring of Specific Performance Counters

Notifications
Others
11/24/2017 1413
91 PerfCounter IIS Application Pool Sensor
7.8.91 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 the application pool:

· Running (sensor status 183 Up)
· Initialized or Shutdown Pending (Warning)
· Unavailable, Uninitialized, Stopping, Stopped, or Delete Pending (Down)

§ 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
1414 11/24/2017
Remarks
§ Requires 1415 Microsoft IIS version 7.5 or later on the target system.
§ Requires 1415 Windows credentials in the parent device settings.
§ Requires 1415 the Windows Remote Registry service to be running on the target computer.
Requirement: Microsoft IIS Version 7.5

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.

The user account has to be a member of the Performance Monitor Users user group on
the target system.

the RemoteRegistry "Remote Registry" Windows service is running on the target
Windows version 2008 R2 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
11/24/2017 1415
Add Sensor
later.
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 choose will be valid for all sensors that you create when you finish this dialog.
IIS APPLICATION POOL SPECIFIC
Application Pool Select the application pools you want to add a sensor for. You see
items.
Sensor Settings
218 .
1416 11/24/2017
default value.
IIS APPLICATION POOL SPECIFIC
Application Pool Shows the name of the application pool that this sensor monitors.
SENSOR DISPLAY
for each channel.
11/24/2017 1417
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
1418 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


time.
11/24/2017 1419


can choose between:
dependency.
1420 11/24/2017

menu bar.
11/24/2017 1421
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1422 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om

Notifications
Others
11/24/2017 1423
92 Ping Sensor
7.8.92 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
Remarks
§ Knowledge Base: How to create/customize statistical PING sensor?
§ Knowledge Base: Can I create an inverse Ping sensor?
Add Sensor
later.
1424 12/11/2017
92 Ping Sensor
Sensor Settings
218 .
default value.
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
show an error message. The maximum timeout value is 300
seconds (5 minutes).
12/11/2017 1425
92 Ping Sensor
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 that you use the
default value.
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.
When using multiple requests, all of them have to be lost to
show a Down status 183 . 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 Send mult iple Ping request
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 Send mult iple Ping request
above. Enter the time in milliseconds the sensor waits between
two Ping requests. Please enter an integer value. The default value
is 5.
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 208 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 show Down (Acknowledged) instead.
1426 12/11/2017
92 Ping Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
12/11/2017 1427
92 Ping Sensor
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1428 12/11/2017
92 Ping Sensor

time.


can choose between:
dependency.
12/11/2017 1429
92 Ping Sensor

menu bar.
1430 12/11/2017
92 Ping Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: How to create/customize statistical PING sensor?
Knowledge Base: Can I create an inverse Ping sensor?

12/11/2017 1431
92 Ping Sensor
Notifications
Others
1432 12/11/2017
93 Ping Jitter Sensor
7.8.93 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.
§ 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
Remarks
11/24/2017 1433

this sensor.
PRTG require?
Add Sensor
later.
Sensor Settings
218 .
default value.
1434 11/24/2017
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:
11/24/2017 1435
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1436 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1437

time.


can choose between:
dependency.
1438 11/24/2017

menu bar.
11/24/2017 1439
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
1440 11/24/2017
Others
11/24/2017 1441
94 POP3 Sensor
7.8.94 POP3 Sensor
The POP3 sensor monitors an email server using Post Office Protocol version 3 (POP3).
§ It shows the response time of the server.
POP3 Sensor
Remarks
Add Sensor
later.
Sensor Settings
1442 11/24/2017
94 POP3 Sensor
218 .
default value.
POP3 SPECIFIC
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
recommend that you use the default value.
If you do not get a connection, please try another port
number.
Sensor Specific Define the security level for the sensor connection. Choose
between:
11/24/2017 1443
94 POP3 Sensor

status 183 .
1444 11/24/2017
94 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 in to the POP3 server with
username 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
11/24/2017 1445
94 POP3 Sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
1446 11/24/2017
94 POP3 Sensor
SCANNING INTER VAL

requests.
requests.
apply.


11/24/2017 1447
94 POP3 Sensor

time.


can choose between:
dependency.
1448 11/24/2017
94 POP3 Sensor
menu bar.
11/24/2017 1449
94 POP3 Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
1450 11/24/2017
95 Port Sensor
7.8.95 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
Remarks
Sensor Settings
11/24/2017 1451
95 Port Sensor
218 .
default value.
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.
1452 11/24/2017
95 Port Sensor
§ Do not use Transport -Level Securit y : Establish the connection

without encryption.
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 183 if the port is
open, and a red Down status if the port is closed.
§ Closed: The sensor shows a green Up status 183 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.
You cannot use this option if the target machine is a web
server.
Command This field is only visible if you enable Send command above. Enter
a command that the sensor sends in a Telnet session to the
respective port. You cannot use line breaks, only a simple Telnet
command in a single line. 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 Check response code
(int eger) above. Enter a code that the target device must return. If
it does not match, the sensor will show a Down status 183 . Please
11/24/2017 1453
95 Port Sensor
Check For Existing This setting is only visible if you activated Check response t ext
Keywords (positive) above. Check if a certain keyword is part of the received value. If
there is no match, the sensor will show a Down status 183 .
§ 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.
Response Must Include This setting is only visible if you activate 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.
§ Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 3355 section.

Expressions 3355 .
Check For Existing This setting is only visible if you activated text processing above.
Keywords (negative) Check if a certain keyword is not part of the received value. If
there is a match, the sensor will show a Down status 183 .
§ 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 activate 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:
§ Plain Text : Search for a simple string.
§ Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 3355 section.

Expressions 3355 .
1454 11/24/2017
95 Port Sensor
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
11/24/2017 1455
95 Port Sensor
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1456 11/24/2017
95 Port Sensor
SCANNING INTER VAL

apply.


time.

11/24/2017 1457
95 Port Sensor

can choose between:
dependency.
menu bar.
1458 11/24/2017
95 Port Sensor

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

11/24/2017 1459
95 Port Sensor
Notifications
Others
1460 11/24/2017
96 Port Range Sensor
7.8.96 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.
It shows the following:
§ Number of closed ports

§ Number of open ports
§ Time until requests are accepted
Optionally, you can set limits in the sensor channel settings 2915 . This way you can get alerts
about open and closed ports.
Port Range Sensor
Remarks
11/24/2017 1461
Add Sensor
later.
Sensor Settings
218 .
default value.
1462 11/24/2017
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 Port range wit h st art /end
above. Enter the port number where the scan starts. Please enter
an integer value.
Range End This field is only visible if you enable Port range wit h st art /end
above. Enter the port number where the scan ends. Please enter
an integer value.
Port List This field is only visible if you enable List of port s 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
11/24/2017 1463
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1464 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1465

time.


can choose between:
dependency.
1466 11/24/2017

menu bar.
11/24/2017 1467
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
1468 11/24/2017
97 PostgreSQL Sensor
7.8.97 PostgreSQL Sensor
The PostgreSQL sensor monitors a database on a PostgreSQL server and executes a defined
query.
PostgreSQL Sensor
Remarks
probe above.
§ 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 3383 for more information about
how to find this path
11/24/2017 1469
§ This sensor type supports PostgreSQL 7.x or later.

selection)
depending on it?

this sensor.
PRTG require?
Add Sensor
later.
Sensor Settings
218 .
1470 11/24/2017
default value.
DATABASE SPECIFIC
Database Enter the name of the PostgreSQL database to which the sensor
connects (for example, MyDatabase). This is a logical entity on the
database server where database objects like tables or stored
procedures exist.
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, refer to the
PostgreSQL documentation.
11/24/2017 1471
DATA
cluster node!
be transferred,
computer?
SQL Variables
1472 11/24/2017
DATA

below.
executed.
11/24/2017 1473
DATA
Choose between:
below.
value was found.
1474 11/24/2017
DATA

table.
between:
§ BytesBandwidth
11/24/2017 1475
DATA
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Value Lookup
Choose between:
1476 11/24/2017
DATA
will be added.
change.
between:
11/24/2017 1477
DATA

SENSOR DISPLAY
for each channel.
1478 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1479
SCANNING INTER VAL

apply.


time.

1480 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1481

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1482 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
depending on it?

Notifications
Others
11/24/2017 1483
98 Probe Health Sensor
7.8.98 Probe Health Sensor
The Probe Health sensor monitors internal PRTG parameters. It shows the status of the PRTG
probe (either for the local probe, the cloud probe, a remote probe 3359 , or a cluster 122 probe).
It checks various parameters of your PRTG system that 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.
§ 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 that are not of the type SNMP or WMI. If this value is over 0%, try to increase
the scanning intervals 328 or distribute your sensors over multiple probes 3359 .
§ 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 328 or distribute the sensors over several probes 3359 .
§ 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 328 or distribute the sensors
over several probes 3359 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 3251 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 3359 .
§ Message Queue: This channel shows the number of monitoring results from the probe that
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.
§ Threads: This channel shows the number of program parts that are running simultaneously
currently. This value can increase with heavy load. The number should not exceed 100 in
normal operation.
1484 11/24/2017
§ Toplist Memory : This channel shows the amount of RAM that the Toplist s 2940 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 3359
.
§ 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
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 3359 , or
a cluster 122 probe).
§ Knowledge Base: My probe system is running out of disk space. What can I do?
Sensor Settings
11/24/2017 1485
218 .
default value.
SENSOR DISPLAY
for each channel.
1486 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 1487
SCANNING INTER VAL

requests.
requests.
apply.

1488 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1489
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: My probe system is running out of disk space. What can I do?

Notifications
Others
1490 11/24/2017
99 Python Script Advanced Sensor
7.8.99 Py thon Script Advanced Sensor
The Python Script Advanced sensor executes a Python script on the computer running the
local or remote probe. This option is provided as part of the PRTG Application Programming
Interface (API). The return value of this sensor must be valid JSON or XML.
§ The sensor can show values returned by the Python script in multiple channels.
Py thon Sc ript Adv anc ed Sensor
Remarks
§ You must store the script file on the system of the probe where you create the sensor: If
used on a remote probe, you must store the file on the system running the remote probe. In
a cluster setup, copy the file to every cluster node.
§ For best sensor usage, we recommend that the return value is JSON encoded.
§ The timeout of the sensor is its scanning interval 1496 minus 1 second. Ensure your Python
script does not run longer than this.
§ Print commands in the Python script are not supported and lead to an invalid JSON result.
§ Exceptions in the script are not supported.
§ Sensor channel values greater than 2^62 are not supported.
the probe computer?
12/11/2017 1491

Add Sensor
later.
SENSOR SETTINGS
Python Script Select a Python script from the list. The sensor will execute it with
every scanning interval 1496 .
This list shows all Python script files available in the \Cust om
Sensors\py t hon subdirectory of the probe system's PRTG
program directory (see Dat a St orage 3383 ). For the files to appear
in this list, please store the files into this folder ending in .py. To
show the expected values and sensor status, your files must
return the expected XML or JSON format to standard output.
Values and message must be embedded in the XML or JSON. We
recommend JSON encoded return values.
for the expected return format, see the API documentation
(Applicat ion Programming Int erface (API) Definit ion 3336 ). There,
find detailed information on the Cust om Sensors tab.
Sensor Settings
1492 12/11/2017
218 .
default value.
SENSOR SETTINGS
Python Script Shows the Python script file that the sensor executes with each
scan as defined at sensor creation. Once a sensor is created, you
Python interpreter. Choose between:
under the same Windows user account the probe is running on.
By default, this is the Windows system user account (if not
manually changed).
12/11/2017 1493
SENSOR SETTINGS

user account defined in the settings of the parent device on
which you create this sensor. Please navigate to the parent
device settings 385 of this sensor to change these Windows
credentials.
Device Credentials Define if you want to transmit device credentials to the Python
script. PRTG adds the device credentials to the JSON object that is
passed to the script as command line parameter. Please navigate
to parent device settings 385 of this sensor to change these
credentials. Choose between:
§ Do not t ransmit device credent ials: No device credentials are
given to the script.
§ Transmit Windows credent ials: Windows credentials 390 are
given to the script.
§ Transmit Linux credent ials: Linux credentials 391 are given to
the script.
§ Transmit SNMP credent ials: SNMP credentials 394 are given to
the script.
§ Transmit all device credent ials: Windows, Linux, and SNMP
credentials are all given to the script.
All parameters are transmitted in plain text.
Additional Parameters Define additional parameters to add to the JSON object that is
passed to the script as command line parameter.
Please enter a string or leave the field empty.
All parameters are transmitted in plain text.
Mutex Name Define any desired mutex name for the process. All 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. Please enter a string or leave the field empty.
For more details, please see this Knowledge Base article: What
is the Mutex Name in PRTG's EXE/Script Sensor's settings?
1494 12/11/2017
DEBU G OPTIONS
between:
You can use Writ e sensor result t o disk to inspect the passed JSON object that contains
all parameters (PRTG on premises only). This way you can find out which key you can
access when you script.
Transmitted passwords are masked in the logfile.
SENSOR DISPLAY
for each channel.
12/11/2017 1495
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
1496 12/11/2017
SCANNING INTER VAL

requests.
apply.


time.

12/11/2017 1497


can choose between:
dependency.
menu bar.
1498 12/11/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
12/11/2017 1499
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
probe computer?

Notifications
Others
1500 12/11/2017
100 QoS (Quality of Service) One Way Sensor
7.8.100 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/24/2017 1501
Remarks
§ You have to configure at least one remote probe 3358 in your PRTG on premises setup for this
sensor to work, and at least two remote probes in PRTG in the cloud.
§ You can create this sensor on the Probe Device of either a local or remote probe.
Add Sensor
later.
Sensor Settings
218 .
default value.
1502 11/24/2017
QU ALITY OF SER VICE MEASU R EMENT
Target Probe Define the target probe that will receive the UDP packets. The
dropdown menu shows all local and remote probes in your setup.
When running the sensor on the PRTG on premises local probe,
select a remote probe as Target Probe. If no remote probe is
available, please install and connect a remote probe 3358 first. When
running the sensor on a remote probe, select either another
remote probe or the local probe in PRTG on premises as target.
The sensor will measure values for the network track between the
probe the sensor is created on and the target probe.
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.
In PRTG in the cloud you can only select another remote probe
as target probe. QoS measurements for connections to the
cloud probe are not are not possible.
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.
11/24/2017 1503
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 that 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
SENSOR DISPLAY
for each channel.
1504 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1505
SCANNING INTER VAL

apply.


time.

1506 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1507

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

1508 11/24/2017
Notifications
Others
11/24/2017 1509
101 QoS (Quality of Service) Round Trip Sensor
7.8.101 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
QoS (Quality of Serv ic e) Round Trip Sensor
1510 11/24/2017
Remarks
§ You have to configure at least one remote probe 3358 in your PRTG on premises setup and at
least two remote probes in PRTG in the cloud, 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?
§ Knowledge Base: What connection settings are necessary for the QoS (Quality of Service)
Round Trip Sensor?
Add Sensor
later.
Sensor Settings
218 .
11/24/2017 1511
default value.
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.
For more information about the QoS Reflector, see this
Knowledge Base: How can I monitor QoS roundtrips without
using remote probes?
Target Probe This setting is only available if you select PRTG probe as QoS
target. In the dropdown menu, you see all local and remote probes
of your setup.
When running the sensor on the PRTG on premises local probe,
select a remote probe as Target Probe. If no remote probe is
available, install and connect a remote probe 3358 first or use the
PRTG QoS Reflector.
When running the sensor on a remote probe, select either another
remote probe or the local probe in PRTG on premises as target.
The sensor will measure values for the network track between the
probe the sensor is created on and the target probe.
1512 11/24/2017
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.
For details, see this Knowledge Base article: What connection
settings are necessary for the QoS (Quality of Service) Round Trip
Sensor?
In PRTG in the cloud you can only select another remote probe
as target probe. QoS measurements for connections to the
cloud probe are not are not possible.
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. Use a different
port for each QoS sensor to make sure packets can be assigned
correctly. Enter an integer value between 1024 and 65536.
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 that 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
SENSOR DISPLAY
11/24/2017 1513
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1514 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1515

time.


can choose between:
dependency.
1516 11/24/2017

menu bar.
11/24/2017 1517
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
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?
Knowledge Base: What connection settings are necessary for the QoS (Quality of Service)
Round Trip Sensor?
1518 11/24/2017

Notifications
Others
11/24/2017 1519
102 RADIUS v2 Sensor
7.8.102 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:
· Access-Accept (sensor status 183 Up)
· Access-Challenge (Warning)
· Access-Reject (Down)
§ If authentication fails, the sensor will show a Down status 183 .
RADIUS v 2 Sensor
Remarks
§ Requires 1521 .NET 4.5 on the probe system.
§ This sensor only supports plain text authentication (Password Authentication Protocol (PAP)).
1520 11/24/2017

this sensor.
PRTG require?
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1521
1522 11/24/2017
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 Enter the username that is used for authentication at the RADIUS
server. Please enter a string.
Password Enter the password that is used for authentication between the
client (this is the PRTG probe on which the sensor runs) and the
RADIUS server. Please enter a string.
Secret Enter the shared secret that is used for authentication between
the authenticator (this is the PRTG probe) and the RADIUS server.
Please enter a string.
Port Enter the port number that is used for the connection to the
RADIUS server. The default value is 1812. Please enter an integer
value.
Network Access Define how to identify the Network Access Server (NAS). Choose
Server between:
§ Use NAS IP address: Enter the IP address for identification
below.
§ Use NAS ident ifier: Enter the identifier below.
NAS IP Address This field is only visible if you select Use NAS IP address as an
identification method above. Enter a valid IP address for the
Network Access Server (NAS) that originates the access request.
NAS Identifier This field is only visible if you select Use NAS ident ifier above.
Enter an identifier for the NAS that originates the access request.
between:
11/24/2017 Cloud Probe of a PRTG in the cloud instance. 1523
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1524 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1525

time.


can choose between:
dependency.
1526 11/24/2017

menu bar.
11/24/2017 1527
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
1528 11/24/2017
Others
11/24/2017 1529
103 RDP (Remote Desktop) Sensor
7.8.103 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
Add Sensor
later.
Sensor Settings
1530 11/24/2017
218 .
default value.
SENSOR SPECIFIC
Please enter an integer value. Default value is 3389. We
SENSOR DISPLAY
11/24/2017 1531
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1532 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1533

time.


can choose between:
dependency.
1534 11/24/2017

menu bar.
11/24/2017 1535
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
1536 11/24/2017
Others
11/24/2017 1537
104 REST Custom Sensor
7.8.104 REST Custom Sensor
The REST Custom sensor queries a REST Application Programming Interface (API) endpoint and
maps the JSON or XML result to sensor values. The mapping rule has to be available as a REST
configuration file in JSON template (*.template) format according to the PRTG API definition for
custom sensors.
§ The sensor can show values returned by a REST API in multiple channels.
REST Custom Sensor
Remarks
§ The REST configuration file that contains the mapping rules 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.
§ This sensor does not support more than 50 channels 1539 . If you have more than 50 channel
mappings in your REST Configuration file, the sensor will show an error.
1538 12/11/2017

Add Sensor
later.
R EST SPECIFIC
REST Configuration Select a REST configuration from the list. The sensor will use it to
map the JSON or XML result from the REST query into sensor
values.
Default is channelDiscovery . If you choose this REST
configuration, the sensor will parse the returned JSON or XML and
automatically create channels based on available values: one
channel for each number and boolean, for strings if they are
convertible into numbers.
This list shows all available files in the \Cust om Sensors\rest sub-
directory of the probe system's PRTG program directory (see Dat a
St orage 3383 ). To appear in this list, store the files as JSON template
(*.template) into this folder.
Using custom scripts is not possible on cloud probes. To use
custom REST configurations, add this sensor to a remote
probe instead and save the file on this system.
To show the expected values and sensor status, your files must
return the expected JSON format. Channels, values, and messages
must be embedded in valid JSON using JSONPath. For details, see
section Define Sensor Channels and Select Channel Values 1549 .

for the expected return format, see the API documentation in
your PRTG installation. There, find detailed information on the
Cust om Sensors tab. See also manual section Applicat ion
Programming Int erface (API) Definit ion 3336 for more information.
12/11/2017 1539
R EST SPECIFIC
There are several REST configuration files available by default.

They are ready to use. You can also analyze them to see how
to write your own REST configuration.
Sensor Settings
218 .
default value.
1540 12/11/2017
R EST SPECIFIC
request the REST API.
§ GET (default ): Use the GET method to request the REST API.
§ POST: Use the POST method to request the REST API.
here.
Request Protocol Define the security of the HTTP request. Choose between:
§ HTTP (default ): Send the REST query via insecure HTTP.
§ HTTPS: Send the REST query via secure HTTPS.
Authentication Method Select the authentication method for access to the REST API.
Choose between:
§ No aut hent icat ion (default ): Do not use any authentication for
the request.
§ Basic aut hent icat ion: Use simple username and password
authentication.
§ Basic aut hent icat ion wit h Windows credent ials from parent
device: Use the Windows credentials from the parent device.
See section Inherit ance of Set t ings 129 for more information.
12/11/2017 1541
R EST SPECIFIC
§ Token: Use a JSON Web Token (JWT) or OAuth2 Bearer Token for
authentication.
User This field is only visible if you enable basic authentication above.
Enter a username for the REST API. Please enter a string.
Password This field is only visible if you enable basic authentication above.
Enter a password for the REST API. Please enter a string.
Token This field is only visible if you enable token authentication above.
Enter a JWT or OAuth2 Bearer Token that is required by the REST
API for authentication.
HTTP Headers Define if you want to send custom HTTP headers to the target URL.
Choose between:
header1:value1

REST Query This field shows the REST query that this sensor executes. To
change it, enter a valid query for the target REST API. The syntax
is: [:port ]/pat h[?var1=val1&...]
The first part of the address is always inherited from the parent
device's address. Only enter the path to the REST endpoint of
the parent device. You can override the port if necessary.
For example, if you add the sensor to a probe device, a query to
the REST API of your PRTG installation that returns the number of
sensors on the probe would look like this:
/api/table.json?id=1&passhash=<passhash>&username=<username>&content=sensorxref&nor
1542 12/11/2017
R EST SPECIFIC
REST Configuration Shows the REST configuration file that the sensor uses to map
returned JSON or XML into sensor values. Once a sensor is
anew.
DEBU G OPTIONS
between:
SENSOR DISPLAY
for each channel.
12/11/2017 1543
SENSOR DISPLAY

Inherited Settings
information.
1544 12/11/2017
proxy login.
proxy login.
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
12/11/2017 1545
SCANNING INTER VAL

apply.


time.

1546 12/11/2017


can choose between:
dependency.
menu bar.
12/11/2017 1547
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1548 12/11/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Define Sensor Channels and Select Channel Values

In your REST configuration file, you have to define which values of the returned JSON or XML
will be mapped to which sensor channels.
§ A sensor channel is defined by the channel key in your REST configuration. See section
JSON Ret urn Format : Minimum Example in the PRTG API documentation 3336 of your PRTG
installation.
§ A channel value is defined by an expression that retrieves and processes the value from the
JSON source. The expression can contain JSONPath 1551 , gval operators 1555 , and functions 1557 .
12/11/2017 1549
Example
For this example, we take PRTG as REST endpoint and query the sensor status statistics for
the local probe. The REST query that we enter in the sensor settings looks like this:
/api/table.json?id=1&passhash=<passhash>&username=<username>&content=sensorxref&
noraw=1&filter_basetype=probe&columns=totalsens=textraw,upsens=textraw
downsens=textraw,partialdownsens=textraw,warnsens=textraw,pausedsens=textraw,
unusualsens=textraw,undefinedsens=textraw,downacksens=textraw
This REST query will return some JSON, for example:

{
"prtg-version": "17.3.33.2517",
"treesize": 1,
"state": "ok",
"sensorxref": [
{
"totalsens": 28,
"upsens": 18,
"downsens": 0,
"partialdownsens": 0,
"warnsens": 0,
"pausedsens": 9,
"unusualsens": 1,
"undefinedsens": 0,
"downacksens": 0
}
]
}
Your REST configuration has to translate this JSON for the sensor. It has to be available as
JSON template (*template) in the \Cust om Sensors\rest sub-directory of your PRTG probe
system. See the PRTG API documentation 3336 of your PRTG installation for details about the
JSON return format.
The following example returns two channels from the JSON resource that will be added to
the sensor in PRTG, Tot al (total sensor count) and Alarms (sensors in error status), each
selected by their keys in the returned JSON.
{
"prtg": {
"result": [
{
"channel": "Total" ,
"value": $.sensorxref[0].totalsens
1550 }, 12/11/2017
{
"channel": "Alarms" ,
There are several REST configuration files available in the \Cust om Sensors\rest folder by
default. They are ready to use. You can also analyze them to see how to write your own
REST configuration.
JSONPath
The REST Custom sensor uses JSONPath to assign values from the returned JSON to sensor
channels. With JSONPath you provide the path to the value in the JSON source that you want to
monitor in a sensor channel.
The JSONPath implementation that PRTG uses for the REST Custom sensor might differ from
other JSONPath implementations. You can test and debug your definitions 1559 using the
command line. To test simple JSONPath expressions and calculations, you can also use
JSONPath Online Evaluator 1561 , for example. Please note that this tool might not work properly
with complex JSONPath expressions that PRTG supports.
12/11/2017 1551
Example
To demonstrate the practical usage of JSONPath, we use this JSON example that a REST
query might have returned as reference in this section.
{
"devices":[
{
"firmware":{
"id":"0.7",
"date":"2017-05-18T17:11:43.7049944Z",
"channel": "beta"
},
"networks": {
"a": {
"rx_bytes": 35985021,
"tx_bytes": 7229493,
"rx_errors": 0,
"rx_dropped": 476,
"tx_bytes": 7229493,
"tx_packets": 35518,
"tx_errors": 0,
"tx_dropped": 1
},
"b": {
"rx_bytes": 40085321,
"tx_bytes": 55294975
}
}
},
{
"networks": {
"a": {
"rx_bytes": 63685865,
"tx_bytes": 7229472
}
}
}
]
}
1552 12/11/2017
R EST CU STOM SENSOR : JSONPATH
Root The dollar sign ($) matches the root element of the JSON data.
Child You can match a child with .<key > or [<key >]
§ .<key > must only contain letters, numbers, and underscore (_).
§ [<key >] must only contain a number or a quoted string.
Example
This expression matches 35985021 in the example above:

$.devices.0.networks.a.rx_bytes
You get the same result with this expression:

$["devices"][0]["networks"]["a"]["rx_bytes"]
Wildcard To match multiple values, you can use the asterisk symbol (*).
§ .*
§ [*]
Example
This expression matches 35985021 and 40085321 in the example

above:
$.devices[0].networks.*.rx_bytes
Recursive You can match all sub-items of a node with two dots (..).
Descent
Example
This expression matches 7229493 and 55294975 and 7229472 in the

example above:
$..tx_bytes
Union You can match multiple children with [<key 1>,<key 2>,<...>].
Example
This expression matches 35985021 and 7229493 in the example above:

$.devices.0.networks.a["rx_bytes","tx_bytes"]
Slice You can match multiple children of an array with [<begin>:<end>] or

[<begin>:<end>:<st ep>].
§ By default, begin, end, and step are either integers or empty.
12/11/2017 1553
§ The default approach is to go step by step from the first array element
to the last element.
§ Step can also be a negative integer to go through the array in
reversed order.
Example
This expression matches 63685865 in the example above:

$.devices[-1:].networks.a.rx_bytes
Current The @ symbol matches the current element.
Example
This expression matches to 40.085321 and 55.294975 in the example

above and can be used to receive a percentage value:
$.devices[1].networks.a.["rx_bytes","tx_bytes"](@/100000000*100)
Filter You can filter matches with [?<expression>].
Example
This expression matches 35985021 in the example above because the

first device is the only one with a beta channel:
$.devices[?@.firmware.channel=="beta"].networks.a.rx_bytes
Script You can modify matches with (<expression>) and keys with
[<expression>].
Example
This expression matches t rue and false in the example above because
only the first device has a beta channel:
$.devices[*](@.firmware.channel=="beta")
Placeholder Placeholders give access to values of wildcards in a match. A

placeholder #n (where n is a natural number) represents the value of
the nth wildcard. You can use this in the keys of JSON arrays.
Example
This expression creates a JSON map from ids to the corresponding

firmware channel and matches {"0.7":"bet a"} in the example above:
{$.devices[#0].id:$.devices[*].channel}
This is an extension of the official JSONPath.
1554 12/11/2017
Constant § Numeric constants as 64-bit floating point: 12345.678

§ String constants with double quotes: "swit ch"
§ Boolean constants: t rue and false
Operator § Parentheses control the order of evaluation: (<expression>)

§ Arrays with square brackets: [<expression>, <expression>, ...]
§ Objects: {<expression>:<expression>,
<expression>:<expression>, ...}
§ Conditionals: <condit ion> ? <expression> : <expression>
Calculating Channel Values and Functions

You can perform calculations with the values of the source JSON or XML. The sensor uses the
Paessler gval package for the calculations. Please refer to the gval documentation 1561 for
details.
The following operators and functions are available to calculate channel values.
R EST CU STOM SENSOR : OPER ATOR S
Oper Descript ion Operand Ty pe Out put Ty pe

at or
Infix + plus number number

Modifiers
- minus number number
* times number number
** power of number number
% modulo number number
/ divide number number
& bitwise and number number
| bitwise or number number
12/11/2017 1555
R EST CU STOM SENSOR : OPER ATOR S
^ bitwise xor number number
<< shift left number number
>> shift right number number
Logical Infix > greater than number/string bool

Operators
>= equal or greater than number/string bool
< less than number/string bool
<= equal or less than number/string bool
== equal any bool
!= not equal any bool
=~ match regular string bool

expression
!~ mismatch regular string bool

expression
in contains element any, array bool
&& and and bool
|| or or bool
?? coalescence any any
Prefix - negative number number

Operators
~ bitwise not number number
! not bool bool
1556 12/11/2017
R EST CU STOM SENSOR : FU NCTIONS
duration § Calculates the nanoseconds between start and end.

(start,end)
§ Both parameters must be RFC3339 date time strings.
Example
duration($.devices[0].firmware.date, "017-05-18T17:11:43.7049944Z")
now() § Returns the current date time in RFC3339.
Example
duration($.devices[0].firmware.date, now())
number(string, § Converts a string to a floating point number.

[base])
§ If the base is not set, it will be detected via the prefix of the string.
· "0": base = 8
· "0X": base = 16
· otherwise: base = 10
· Decimals are only supported at base 10.
Examples
number("10.5")
number("a", 16)
len(object/ § Returns the length of an array or string and counts the number of
array/string) properties in a JSON object.
Example
len($..(number(@)))
This expression counts every number or string that can be converted

into a number. It returns 13 in the example above.
sum(array-/ § Returns the sum over an array of numbers.

object-of-
numbers) Example
sum([1,2,3])
This expression returns 6.
12/11/2017 1557
R EST CU STOM SENSOR : FU NCTIONS
mean(array-/ § Returns the average value of an array of numbers.

object-of-
numbers) Example
mean([1,2,3])
This expression returns 2.
lookup(string, § Returns the index of the given string in a string list, or -1 if the string is
string, string, ...) not found.
Example
lookup($.device[0].firmware.channel, "stable", "beta", "alpha")
This expression returns 1 because $.device[0].firmware.channel

resolves to bet a.
implode(array-/ § Returns the concatenation of each string in the array, separated by the
object-of-string, given string.
string)
Example
implode($..tx_bytes, ",")
This expression returns 7229493,7229472.
Generic Channels
You can create a template in your REST configuration that defines generic channels. Generic
channels are created based on the data that the REST endpoint returns. When the returned
value is an array or object, the sensor will create a channel for each element and concatenate
the corresponding key to the channel name.
Example
Imagine you want to have a total byte channel for each network card that is defined in the
JSON example above. You can do this by creating a dynamic channel like in the following
example.
1558 12/11/2017
{
"prtg": {
"result":[
{
"value": {
"Total bytes on device" + #0 + " in network " + #1: $.devices.*.networks[*](@.rx_bytes + @.tx_byt
},
"CustomUnit": "Bytes"
}
]
}
}
Every channel must have unique name. Channels cannot be removed once they are added
and will keep their last received value. New channels can be added.
XML Sources
If the REST source returns XML instead of JSON, the sensor will transform the XML result to
JSON before replacing the value paths with source values. Because of this, you will not know
the structure of the source JSON to correctly provide the paths.
In this case, manually execute the sensor executable rest .exe from the \Sensor Sy st em
subfolder of the PRTG probe system. Execute rest.exe with the address of the XML endpoint
and the parameter passt hrough. The rest executable will return the converted XML to JSON
result that you can use to define the desired paths..
rest.exe <xml-endpoint-url> passthrough
Usage and Debugging

To create a suitable REST configuration for the sensor, you might want to check the returned
JSON or XML and see what happens when your mapping rules apply.
The REST Custom sensor is an EXE sensor, so you can test and debug your configuration by
executing rest .exe with several parameters. The rest.exe is located in the \Sensor Sy st em
subfolder of the PRTG program directory.
Command syntax:
rest.exe url template|passthrough|channelDiscovery [flags]
R EST.EXE: PAR AMETER S
url § Address of the REST API endpoint that returns JSON or XML
12/11/2017 1559
R EST.EXE: PAR AMETER S
template § Fully qualified path and file name of your REST configuration file
used to map the JSON result to the sensor
passthrough § No mapping, only returning the queried JSON or XML

§ Useful to analyze XML that has been converted to JSON
channelDiscovery § Creates a channel for every number or boolean in the returned

JSON or XML
§ If possible, it converts string values to number or boolean
values.
R EST.EXE: FLAGS
-authtoken <string> § JWT or OAuth2 Bearer Token to send with the request in
authorization header as Bearer
-authusername § User name for basic authentication

<string>
-authuserpwd <string> § User password for basic authentication
-post <string> § {1|0}

§ Default: 0
§ 0 results in a GET request.
§ 1 results in a POST request.
-proxy <string> § Proxy server connection
-proxyusername § Proxy user name with basic authentication

<string>
-proxyuserpwd § Proxy user password with basic authentication

<string>
-tlsignore <string> § {1|0}

§ Default: 0
§ 1 will accept self-signed certificates on HTTPS connections
1560 12/11/2017
R EST.EXE: FLAGS
-customheaders § key1:val1|key2:val2|...
<string>
-template § Returns the discovered template is you use channelDiscovery .
-timeout <integer> § Sensor timeout in seconds

§ Default: 10
More
Paessler JSONPath
§ https://github.com/PaesslerAG/jsonpath
Paessler gval
§ https://github.com/PaesslerAG/gval
JSONPath Online Evaluator
§ http://jsonpath.com/

Notifications
Others
12/11/2017 1561
105 Share Disk Free Sensor
7.8.105 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
Remarks
§ Requires 1562 the LanmanServer Windows service to be running on the target device.
§ 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: LanmanServer Windows Service

To monitor shares on Windows machines, please make sure the LanmanServer "Server"
1562 11/24/2017
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1563
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.
To provide any shares under Windows, the LanmanServer
"Server" Windows service must be running on the target
computer.

SENSOR DISPLAY
for each channel.
1564 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1565
SCANNING INTER VAL

apply.


time.

1566 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1567

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1568 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 1569
106 Sensor Factory Sensor
7.8.106 Sensor Factory Sensor
The Sensor Factory sensor is a powerful tool that allows you to monitor entire business
processes that involve several components.
You can define one or more channels that combine monitoring results from other sensors or
devices. You can create your own individual sensor with channels based on data from other
sensors or devices.
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.
The Sensor Factory sensor does not show values in the Downt ime channel because they
cannot be calculated for this sensor type.
If you want to create only a cumulated sensor status based on specific source sensors,
we recommend that you use the Business Process Sensor 556 instead.
sensor setup.
Sensor Fac tory Sensor
Remarks
§ Ensure the scanning interval 1574 of this sensor is equal to or greater than the scanning
interval of the source sensor(s) to avoid incorrect sensor behavior. For example, "no data"
messages or erratic changes of the sensor status can be a result of an invalid scanning
interval.
1570 11/24/2017
§ Knowledge Base: How can I monitor the overall status of the business process "Email"?
§ The Sensor Factory sensor might not work with flow sensors 3251 . Sensor types using active
flow timeout, this is, NetFlow and jFlow sensors 413 , are not supported by the Sensor Factory
sensor.
§ Reports 192 cannot show uptime or downtime data for this sensor type.
type on each probe.

Add Sensor
later.
Sensor Settings
218 .
11/24/2017 1571
default value.
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.
For more information, see section Define Sensor Channels 1578
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 Sensor Factory sensor is Down, it will still show
data of all available sensor channels.
If a lookup definition 3345 or an error limit 2916 triggers the error
status of the source sensor, the Sensor Factory will not
show a Down status. This is because the Sensor Factory should
only show this status if it cannot calculate values.
1572 11/24/2017
SENSOR FACTOR Y SPECIFIC SETTINGS
§ 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.
If a lookup definition 3345 or an error limit 2916 triggers the error
status of the source sensor, the Sensor Factory will not
show a Warning status. This is because the Sensor Factory
should only show this status if it cannot calculate values.
§ 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 choose Use cust om 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.
For more information, see section Define Sensor St at us 1585
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.
§ 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.
If a sensor in the channel of a factory sensor has no data, the
factory sensor will always show a Warning status 183 , no
matter which of the above options you select.
SENSOR DISPLAY
11/24/2017 1573
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1574 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1575

time.


can choose between:
dependency.
1576 11/24/2017

menu bar.
11/24/2017 1577
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
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 server.
1578 11/24/2017
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 that is greater
than 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 (for example, 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() 1580 , min() 1581 , max() 1581 , avg() 1581 , or percent ()
1582 .
Define Sensor Channels—Formula 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)
11/24/2017 1579
§ 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 (for example, ping ms) or delta values (for example, traffic kbit/
s). Not all combinations are allowed in a formula.
When performing percentage calculation, please use the percent () Funct ion 1582 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 Channels—channel() 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 174 .
§ <channelId> is the ID of the sensor channel. It is displayed in the respective field of the
channel settings 2916 .
1580 11/24/2017
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 Channels—min() 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() 1580 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 Channels—avg() 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() 1580 functions.
11/24/2017 1581
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 Channels—percent() 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() 1580 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 1584 section below for a list). This can be used for gauge (for
example, Ping sensors 1424 ) or delta (for example, traffic sensors). If no unit is provided, 1 will
be used.
The sensor adds the unit string % automatically.
PRTG will calculate: <source> / <maximum> * <unit> * 100
1582 11/24/2017
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 Channels—Horizontal 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 greater than 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 (for example, 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.
11/24/2017 1583
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 Channels—Constants

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
1584 11/24/2017
§ gigabit = giga / 8
§ t erabit = tera / 8
Define Sensor Status—status() Function

You can control the status of a Sensor Factory sensor via the St at us Definit ion text field if
you enable the custom formula option in the Sensor Set t ings 1571 . 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 174 .
§ <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.
11/24/2017 1585
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.
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.
1586 11/24/2017
§ false corresponds to a value of 0, which is an Up status.
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.
You can also use the status() function in channel definitions 1578 . 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 122 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 will show 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 will only show data of the primary master node for this sensor channel.
More
Video Tutorial: How to Create a Factory Sensor for the Monitoring of Complex Processes in
PRTG
§ https://www.paessler.com/support/videos/prtg-advanced/factory-sensor
Knowledge Base: How can I monitor the overall status of the business process "Email"?
Knowledge Base: Can I add sensors to Sensor Factory sensors using tags?
Knowledge Base: What can I do with PRTG's Sensor Factory Sensors?
Paessler Blog: Monitoring Business Processes—Transformation of Technical Outages to the
Real Business Impact
§ https://www.paessler.com/blog/2014/06/26/all-about-prtg/monitoring-business-processes
11/24/2017 1587

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, see the Sensor Channels Set t ings 2915 .
Notifications
Others
1588 11/24/2017
107 sFlow Sensor
7.8.107 sFlow Sensor
The sFlow sensor receives traffic data from an 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.
11/24/2017 1589
107 sFlow Sensor
sFlow Sensor
Remarks
§ 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.
§ There are several limitations 1591 for this sensor type.
§ Paessler Website: Paessler sFlow Tester
Sniffer sensors?
§ Knowledge Base: Where is the volume line in graphs?
1590 11/24/2017
107 sFlow Sensor
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.
§ Sample packets have to be of ethernet type "IP" (with optional VLAN tag)
§ Sampled packets of type TCP and UDP are supported
We recommend that you use the sFlow tester for debugging. Please download it here:
Paessler sFlow Tester
Add Sensor
later.
Sensor Settings
218 .
11/24/2017 1591
107 sFlow Sensor
default value.
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.
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.
1592 11/24/2017
107 sFlow Sensor
between:
Ot her channel.
purposes only.
UDP and TCP.
Ot her.
channel.
11/24/2017 1593
107 sFlow Sensor
Sniffer sensors?
FILTER ING
syntax.
SENSOR DISPLAY
for each channel.
1594 11/24/2017
107 sFlow Sensor
SENSOR DISPLAY

PR IMAR Y TOPLIST
§ Top Talkers
§ Top Connect ions
§ Top Prot ocols
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1595
107 sFlow Sensor
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1596 11/24/2017
107 sFlow Sensor

time.


can choose between:
dependency.
11/24/2017 1597
107 sFlow Sensor

menu bar.
1598 11/24/2017
107 sFlow Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1599
107 sFlow Sensor
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
1600 11/24/2017
107 sFlow Sensor
The following filter rules apply to sFlow sensors only.
3340 )
More
Paessler Website: Paessler sFlow Tester
§ https://www.paessler.com/tools/sflowtester
Sniffer sensors?
11/24/2017 1601
107 sFlow Sensor

Notifications
Others
Related Topics
1602 11/24/2017
108 sFlow (Custom) Sensor
7.8.108 sFlow (Custom) Sensor
The sFlow (Custom) sensor receives traffic data from an 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.
sFlow (Custom) Sensor
Remarks
§ 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.
11/24/2017 1603
§ There are several limitations 1604 for this sensor type.

§ Paessler Website: Paessler sFlow Tester
§ Knowledge Base: Where is the volume line in graphs?
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.
§ Sample packets have to be of ethernet type "IP" (with optional VLAN tag)
§ Sampled packets of type TCP and UDP are supported
We recommend that you use the sFlow tester for debugging. Please download it here:
Paessler sFlow Tester

Add Sensor
later.
Sensor Settings
1604 11/24/2017
218 .
default value.
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
11/24/2017 1605
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.
Ot her.
Sensors 3342 .
between:
Ot her channel.
purposes only.
FILTER ING
1606 11/24/2017
FILTER ING
syntax.
SENSOR DISPLAY
for each channel.
PR IMAR Y TOPLIST
§ Top Talkers
11/24/2017 1607
PR IMAR Y TOPLIST
§ Top Connect ions

§ Top Prot ocols
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
1608 11/24/2017
SCANNING INTER VAL

requests.
apply.


time.

11/24/2017 1609


can choose between:
dependency.
menu bar.
1610 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1611
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
Toplists
detail.
Filter Rules
Port Any number
1612 11/24/2017
The following filter rules apply to sFlow sensors only.
3340 )
More
Paessler Website: Paessler sFlow Tester
§ https://www.paessler.com/tools/sflowtester
11/24/2017 1613

Notifications
Others
Related Topics
1614 11/24/2017
109 SFTP Secure File Transfer Protocol Sensor
7.8.109 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 to the server and shows the response time.
SFTP Sec ure File Transfer Protoc ol Sensor
Remarks
§ For this sensor type you must define credentials for Linux/Solaris/Mac OS (SSH/WBEM)
systems on the device you want to use the sensor on.
§ 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 3247 .
Add Sensor
later.
Sensor Settings
12/8/2017 1615
218 .
default value.
SSH SPECIFIC
Connection Timeout Define a timeout in seconds for the connection. This is the time
(Sec.) the sensor will wait to establish a connection to the host. Keep
this value as low as possible. The maximum value is 900 seconds
(15 minutes). Please enter an integer value.
Shell Timeout (Sec.) Define a timeout in seconds for the shell response. This is the time
in seconds the sensor will wait for the shell to return a response
after it has sent its specific command (for example, cat /proc/
loadavg). The maximum value is 300 seconds (5 minutes). Please
SSH Port Define which port this sensor uses for the SSH connection.
Choose between:
1616 12/8/2017
SSH SPECIFIC
§ Inherit port number from parent device (default ): Use the

port number as defined in the Credent ials for Linux/Solaris/
Mac OS (SSH/WBEM) Sy st ems 391 section of the device this
sensor is created on.
§ Ent er cust om port number: Define a custom port number
below and do not use the port number from the parent device
settings.
Use Port Number This field is only visible if you choose Ent er cust om port number
above. Enter the port number (between 1 and 65535) that this
sensor will use for the SSH connection. Please enter an integer
value.
SSH Engine Select the method you want to use to access data with this SSH
sensor 3247 . We strongly recommend that you use the default
engine! For some time you still can use the legacy mode to ensure
§ Inherit from parent device (default ): Use the SSH engine that
you have defined in the parent device settings or higher in the
object hierarchy 125 . If you did not change it, this is the
recommended default engine.
§ Default : This is the default monitoring method for SSH sensors.
It provides best performance and security. It is set by default in
objects that are higher in the hierarchy so usually you can keep
the Inherit from parent device (default ) option.
default SSH engine.
The option you select here overrides the selection of the SSH
engine in a higher object (which is a parent device, group,
probe, or root).
between:
12/8/2017 1617
SSH SPECIFIC

[ID].t xt ") in case of error: Store the last result of the sensor
only if it throws an error.
SENSOR DISPLAY
for each channel.
1618 12/8/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
12/8/2017 1619
SCANNING INTER VAL

apply.


time.

1620 12/8/2017

can choose between:
dependency.
menu bar.
12/8/2017 1621

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1622 12/8/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om

Notifications
Others
12/8/2017 1623
110 SIP Options Ping Sensor
7.8.110 SIP Options Ping Sensor
The SIP Options Ping sensor monitors the connectivity for a Session Initiation Protocol (SIP)
server using SIP options "Ping". You can use it to monitor Voice over IP (VoIP) services. The
sensor sends aut h and opt ions requests to the SIP server. It can alert in case of an error.
§ Response time of the SIP server

§ Response code: You can individually define the status for each individual response code by
editing the lookup 3345 file prt g.st andardlookups.sip.st at uscode
SIP Options Ping Sensor
Remarks
§ An SIP server might return the error 480 Service temporarily unavailable until at least one
reachable SIP client is connected to the server.
type on each probe.
1624 11/24/2017

this sensor.
PRTG require?
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1625
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.
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 (Sec.) 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 tries to connect
again. Enter the maximum number of retries. After reaching the
maximum count, the sensor will show a red Down status 183 .
DEBU G OPTIONS
between:
1626 11/24/2017
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
11/24/2017 1627
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1628 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1629

can choose between:
dependency.
menu bar.
1630 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1631
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1632 11/24/2017
111 SMTP Sensor
7.8.111 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.
§ It shows the response time of the server.
SMTP Sensor
Remarks
Add Sensor
later.
Sensor Settings
11/24/2017 1633
111 SMTP Sensor
218 .
default value.
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, for
SSL/TLS connections port 465 or 587. The actual setting depends
on the server you connect to.
If you do not get a connection, try another port number.
default value.
1634 11/24/2017
111 SMTP Sensor
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.
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 183 .
11/24/2017 1635
111 SMTP Sensor

MONITOR ING
Send Email Define the monitoring approach 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 183 .
From Specify the address that the sent emails contain in the from field.
Please enter a valid email address.
To Specify the address that PRTG sends the emails to. If you define
more than one recipient, separate the individual email addresses
with commas. Please enter a valid email address.
Topic Specify the subject that the sent emails contain. Please enter a
string or leave the field empty.
Content Specify the body that the sent emails contain. Please enter a string
or leave the field empty.
between:
1636 11/24/2017
111 SMTP Sensor
MONITOR ING

SENSOR DISPLAY
for each channel.
Inherited Settings
11/24/2017 1637
111 SMTP Sensor
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

1638 11/24/2017
111 SMTP Sensor

time.


can choose between:
dependency.
11/24/2017 1639
111 SMTP Sensor

menu bar.
1640 11/24/2017
111 SMTP Sensor
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
11/24/2017 1641
112 SMTP&IMAP Round Trip Sensor
7.8.112 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 using the parent device as SMTP server 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 runtime.
The sensor shows the following:
§ Response time of SMTP server

§ Response time of IMAP server
§ Sum of both response times
SMTP&IMAP Round Trip Sensor
Remarks
§ 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 3261 section.
1642 11/24/2017
Add Sensor
later.
We recommend that you add this sensor to an SMTP server device only, because the
settings of this sensor type are optimized for this scenario.
Sensor Settings
218 .
default value.
11/24/2017 1643
EMAIL SETTINGS
From Specify the address that the sent emails will contain in the from
field. Please enter a valid email address.
To Specify the address that PRTG sends the emails to. 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
STEP 1: SEND EMAIL WITH PAR ENT DEVICE AS SMTP SER VER
In this step, you configure how PRTG sends the emails. As SMTP server, the sensor uses
the IP Address/DNS Name of the device you add this sensor to.
via SMTP.
For non-secure connections, usually port 25 is used, for SSL/TLS
connections port 465 or 587. The actual setting depends on the
server you are connecting to.
If you do not get a connection, please try another port number.
default value.
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 authentication for the SMTP connection.
Type Choose between:
§ Username/Password: Authenticate at the SMTP server via
1644 11/24/2017
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:
status 183 .
11/24/2017 1645
STEP 2: CHECK AN IMAP MAILBOX U NTIL EMAIL AR R IVES
In this step, you configure how to receive the sent emails.
IP Address/DNS Name Specify the IMAP server. Enter a valid IP address or DNS name.
Mailbox Specify the IMAP mailbox you want to check. Enter the IMAP
mailbox or folder name.
Port Specify the port that the sensor will use for the IMAP connection.
For non-secure connections usually port 143 is used, for SSL/TLS
connections port 993. The actual setting depends on the server
you connect to.
default value.
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 continuously check the mailbox in the
interval that you specify above until the email arrives. If it does not
arrive within the maximum trip time, the sensor will show 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.
Search Method Define how to search for the roundtrip email in the mailbox.
Choose between:
§ Search email direct ly (default ): Send a SEARCH command to
find the roundtrip email directly on the IMAP server.
§ Search t hrough all available emails: Iterate over all available
message in the mailbox on the IMAP server to find the roundtrip
email.
1646 11/24/2017
between:
status 183 .
DEBU G OPTIONS
between:
11/24/2017 1647
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
1648 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 1649

time.


can choose between:
dependency.
1650 11/24/2017

menu bar.
11/24/2017 1651
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
1652 11/24/2017
113 SMTP&POP3 Round Trip Sensor
7.8.113 SM TP&POP3 Round Trip Sensor
The SMTP&POP3 Round Trip sensor monitors the time it takes for an email to reach a Post
Office Protocol version 3 (POP3) mailbox after being sent using Simple Mail Transfer Protocol
(SMTP). It sends an email using the parent device as SMTP server 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 runtime.
The sensor shows the following:
§ Response time of SMTP server

§ Response time of POP3 server
§ Sum of both response times
SMTP&POP3 Round Trip Sensor
Remarks
§ 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 3261 section.
11/24/2017 1653
Add Sensor
later.
We recommend that you add this sensor to an SMTP server device only, because the
settings of this sensor type are optimized for this scenario.
Sensor Settings
218 .
default value.
1654 11/24/2017
EMAIL SETTINGS
From Specify the address that the sent emails will contain in the from
field. Please enter a valid email address.
To Specify the address that PRTG sends the emails to. 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
In this step, you configure how PRTG sends the emails. As SMTP server, the sensor uses
the IP-Address/DNS Name of the device you add this sensor to.
via SMTP.
connections port 465 or 587. The actual setting depends on the
server you connect to.
default value.
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
11/24/2017 1655
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:
status 183 .
1656 11/24/2017
STEP 2: CHECK A POP3 MAILBOX U NTIL EMAIL AR R IVES
In this step, you configure how to receive the sent emails.
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.
connections port 995. The actual setting depends on the server
you are connecting to.
If you do not get a connection, please try another port number.
default value.
Connection Interval Enter the number of seconds the sensor will wait between two
(Sec.) connections to the IMAP server. PRTG will continuously 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 continuously check the mailbox in the
interval that you specify 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 in into the POP3 server with
username 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.
Password This field is only visible if you select an option with login above.
11/24/2017 1657
between:
status 183 .
DEBU G OPTIONS
between:
1658 11/24/2017
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
Inherited Settings
11/24/2017 1659
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

1660 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1661

menu bar.
1662 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.

Notifications
Others
11/24/2017 1663
114 SNMP APC Hardware Sensor
7.8.114 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.
SNMP APC Hardware Sensor
Remarks
§ Knowledge Base: How can I monitor additional counters with the SNMP APC Hardware
sensor?
§ Knowledge Base: How can I monitor an APC UPS that does not support SNMP?
§ For a general introduction to the technology behind SNMP, please see the manual section
Monit oring via SNMP 3227 .
1664 11/24/2017
Add Sensor
later.
Select the performance counters you want to monitor. PRTG will create one sensor for each
counter you select in the Add Sensor dialog. The settings you choose will be valid for all
APC U PS SPECIFIC
Library OIDs Select the performance counters you want to add a sensor for.
deselect all items.
Sensor Settings
218 .
11/24/2017 1665
default value.
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
value. It is shown for reference purposes only. If you need to
change this, please add the sensor anew.
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.
1666 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1667
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1668 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1669

menu bar.
1670 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: How can I monitor additional counters with the SNMP APC Hardware sensor?
Knowledge Base: How can I monitor an APC UPS that does not support SNMP?
11/24/2017 1671

Notifications
Others
1672 11/24/2017
115 SNMP Buffalo TS System Health Sensor
7.8.115 SNM P Buffalo TS Sy stem Health Sensor
The SNMP Buffalo TS System Health sensor monitors the system health of a Buffalo TeraStation
Network Attached Storage (NAS) using Simple Network Management Protocol (SNMP).
Supported TeraStation systems are the 3000, 3010, 5000, 5010, and 7000 series.
§ Number of errors
§ Number of warnings
§ Available memory in total and percent
§ CPU usage
§ Uptime
§ Failover status: idle, busy, starting main, starting backup, initializing, stopping
§ Firmware update availability: yes, no, unknown
§ RPSU status: fine, broken, unknown
The channels are created at run-time, depending on your Buffalo TeraStation NAS and firmware
version. Which channels the sensor actually shows might depend on the monitored device and
the sensor setup.
Run an Aut o-Discovery 267 with the device template Buffalo TeraSt at ion NAS to
automatically create SNMP Cust om Table sensors 1820 with additional useful information
about your Buffalo TeraStation, for example, array status, disk smart status, disk status, and
iSCSI status. This device template will also create SNMP sensors 414 for traffic, memory, and load
average on your TeraStation.
SNMP Buffalo TS Sy stem Health Sensor
11/24/2017 1673
Remarks
§ This sensor supports the TeraStation 3000, 3010, 5000, 5010, and 7000 series.
Add Sensor
later.
Sensor Settings
218 .
1674 11/24/2017
default value.
SENSOR DISPLAY
for each channel.
11/24/2017 1675
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1676 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1677

can choose between:
dependency.
menu bar.
1678 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
11/24/2017 1679

Notifications
Others
1680 11/24/2017
116 SNMP Cisco ADSL Sensor
7.8.116 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.
SNMP Cisc o ADSL Sensor
Remarks
11/24/2017 1681
Add Sensor
later.
Select the performance counters you want to monitor. PRTG will create one sensor for each
counter you select in the Add Sensor dialog. The settings you choose will be valid for all
CISCO ADSL SETTINGS
Line Index Select the performance counters you want to add a sensor for.
deselect all items.
Sensor Settings
218 .
1682 11/24/2017
default value.
SENSOR DISPLAY
for each channel.
11/24/2017 1683
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1684 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1685

can choose between:
dependency.
menu bar.
1686 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
11/24/2017 1687

Notifications
Others
1688 11/24/2017
117 SNMP Cisco ASA VPN Connections Sensor
7.8.117 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
11/24/2017 1689
Remarks
Add Sensor
later.
Sensor Settings
218 .
default value.
1690 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
information.
between:
11/24/2017 1691

SNMP.
Choose between:
device.
entirely.
1692 11/24/2017
algorithm.
algorithm.
your device.
empty.
SCANNING INTER VAL
information.
11/24/2017 1693
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1694 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1695

menu bar.
1696 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
11/24/2017 1697
Others
1698 11/24/2017
118 SNMP Cisco ASA VPN Traffic Sensor
7.8.118 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
Remarks
§ This sensor type is intended to monitor permanent connections. It will show an error if a
connection is interrupted.
§ This sensor can monitor IPsec connections only!
§ Knowledge Base: I get the error PE123 when using the SNMP Cisco ASA VPN Traffic sensor.
What can I do?
11/24/2017 1699
Add Sensor
later.
Select the connections you want to monitor. PRTG will create one sensor for each connection
you select in the Add Sensor dialog. The settings you choose will be valid for all sensors that
ASA VPN SPECIFIC
Connections Select the IPsec VPN connections you want to add a sensor for.
deselect all items.
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
218 .
1700 11/24/2017
default value.
ASA VPN SPECIFIC
Remote IP Shows the IP address of the connection this sensor monitors. This
value is shown for reference purposes only. We strongly
recommend that you only change it if Paessler support explicitly
asks you to do so. Wrong usage can result in incorrect monitoring
data!
This sensor type can only monitor VPN connections based on
IPsec.
Sensor Behavior Define the status of the sensor 183 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
11/24/2017 1701
SENSOR DISPLAY
for each channel.
Inherited Settings
information.
between:
1702 11/24/2017

SNMP.
Choose between:
device.
entirely.
11/24/2017 1703
algorithm.
algorithm.
your device.
empty.
SCANNING INTER VAL
information.
1704 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1705

time.


can choose between:
dependency.
1706 11/24/2017

menu bar.
11/24/2017 1707
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: I get the error PE123 when using the SNMP Cisco ASA VPN Traffic sensor.
What can I do?

1708 11/24/2017
Notifications
Others
11/24/2017 1709
119 SNMP Cisco ASA VPN Users Sensor
7.8.119 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
Remarks
§ Please do not use the sensor to monitor more than 50 VPN users, especially if they are all
connected simultaneously. For more information, see this Knowledge Base article: My Cisco
ASA VPN Users sensor shows a user limit error. Why? What can I do?
Add Sensor
later.
1710 11/24/2017
Sensor Settings
218 .
default value.
SENSOR DISPLAY
11/24/2017 1711
SENSOR DISPLAY
for each channel.
Inherited Settings
information.
between:
SNMP.
1712 11/24/2017

Choose between:
device.
entirely.
algorithm.
algorithm.
11/24/2017 1713

your device.
empty.
SCANNING INTER VAL
information.
1714 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1715

time.


can choose between:
dependency.
1716 11/24/2017

menu bar.
11/24/2017 1717
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: My Cisco ASA VPN Users sensor shows a user limit error. Why? What can I
do?

1718 11/24/2017
Notifications
Others
11/24/2017 1719
120 SNMP Cisco CBQoS Sensor
7.8.120 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
Remarks
1720 11/24/2017
Add Sensor
later.
Select the CBQoS entries you want to monitor. To monitor Quality of Service (QoS) via
compatible devices, PRTG will create one sensor for each CBQoS entry you choose in the Add
Sensor dialog. The settings you choose will be valid for all sensors that you create when you
finish this dialog.
CLASS BASED QOS SPECIFIC
CBQoS Entries Select the measurements you want to add a sensor for. You see a
items.
Sensor Settings
218 .
11/24/2017 1721
default value.
CLASS BASED QOS SPECIFIC
Object Type Shows further information about the parameter that this sensor
Interface
Description
BitMask
ObjectID
ConfigID
SENSOR DISPLAY
1722 11/24/2017
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 1723
SCANNING INTER VAL

requests.
requests.
apply.


1724 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1725
menu bar.
1726 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
11/24/2017 1727
Others
1728 11/24/2017
121 SNMP Cisco System Health Sensor
7.8.121 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).
Depending on what your device can deliver via SNMP, the sensor can show, for example, the
following system health components:
§ CPU load in percent

§ Available memory in absolute and percentage values
§ Values of the current
§ Status of power supplies
§ Voltage values
§ Fan states
§ Current temperature and temperature status
§ Other information, for example, transmit and receive power
PRTG creates one sensor per component. Which channels the sensor actually shows might
depend on the monitored device and the sensor setup.
SNMP Cisc o Sy stem Health Sensor
11/24/2017 1729
Remarks
Add Sensor
later.
Select the components you want to monitor. To monitor the system health of a Cisco device,
PRTG will create one sensor for each measurement you choose in the Add Sensor dialog. The
settings you choose will be valid for all sensors that you create when you finish this dialog.
CISCO SYSTEM HEALTH SPECIFIC
Measurement Select the measurements you want to add a sensor for. You see a
items.
Sensor Settings
1730 11/24/2017
218 .
default value.
CISCO SYSTEM HEALTH SPECIFIC
Measurement Shows the ID of the measurement that this sensor monitors. Once
the sensor anew.
DEBU G OPTIONS
between:
11/24/2017 1731
DEBU G OPTIONS

SENSOR DISPLAY
for each channel.
1732 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1733
SCANNING INTER VAL

apply.


time.

1734 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1735

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1736 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 1737
122 SNMP Cisco UCS Blade Sensor
7.8.122 SNM P Cisco UCS Blade Sensor
The SNMP Cisco UCS Blade sensor monitors the health status of a Cisco Unified Computing
System (UCS) blade server via Simple Network Management Protocol (SNMP).
It can show the following states:
§ Operability
§ Oper state
§ Power state
SNMP Cisc o UCS Blade Sensor
Remarks
Add Sensor
later.
1738 11/24/2017
Select the blade servers you want to monitor. PRTG will create one sensor for each blade you
SENSOR SETTINGS
Blade Server Select the blades you want to add a sensor for. You see a list with
Sensor Settings
218 .
default value.
11/24/2017 1739
SENSOR SETTINGS
Blade Server Shows information about the blade server that this sensor
Channel Mask
Model
Serial Number
SENSOR DISPLAY
for each channel.
1740 11/24/2017
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
11/24/2017 1741
SCANNING INTER VAL

requests.
apply.


time.

1742 11/24/2017


can choose between:
dependency.
menu bar.
11/24/2017 1743
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1744 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om

Notifications
Others
11/24/2017 1745
123 SNMP Cisco UCS Chassis Sensor
7.8.123 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
1746 11/24/2017
Remarks
Add Sensor
later.
Select the chassis you want to monitor. PRTG will create one sensor for each chassis you
SENSOR SETTINGS
Chassis Select the chassis you want to add a sensor for. You see a list with
Sensor Settings
11/24/2017 1747
218 .
default value.
SENSOR SETTINGS
Chassis Shows the chassis that this sensor monitors. Once a sensor is
anew.
SENSOR DISPLAY
1748 11/24/2017
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 1749
SCANNING INTER VAL

requests.
requests.
apply.


1750 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1751
menu bar.
1752 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1753
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1754 11/24/2017
124 SNMP Cisco UCS Physical Disk Sensor
7.8.124 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
SNMP Cisc o UCS Phy sic al Disk Sensor
Remarks
Add Sensor
later.
To monitor physical disks in a UCS device, PRTG will create one sensor for each disk you
11/24/2017 1755
U CS PHYSICAL DISK
Disks Select the disks you want to add a sensor for. You see a list with
This list only shows working disks with the current status Up
or Warning.
Sensor Settings
218 .
default value.
1756 11/24/2017
U CS PHYSICAL DISK
Disk Shows the disk that this sensor monitors. Once a sensor is
anew.
Display Name Shows the display name of the physical disk that this sensor
SENSOR DISPLAY
for each channel.
11/24/2017 1757
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
1758 11/24/2017
SCANNING INTER VAL

requests.
apply.


time.

11/24/2017 1759


can choose between:
dependency.
menu bar.
1760 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1761
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1762 11/24/2017
125 SNMP Cisco UCS System Health Sensor
7.8.125 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 and inoperable fans

§ Status of fan performance, fan thermal, and fan voltage
§ Number of operable and inoperable fan modules
§ Status of fan module performance, fan module thermal, and fan module voltage
§ Number of operable and inoperable power supplies
§ Status of power supply performance, power supply thermal, and power supply voltage
§ Number of minor, major, and critical faults (that are not yet acknowledged in the UCS logs)
§ Number of warnings (that are not yet acknowledged in the UCS logs)
sensor setup.
SNMP Cisc o UCS Sy stem Health Sensor
11/24/2017 1763
Remarks
Add Sensor
later.
Sensor Settings
218 .
default value.
1764 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
11/24/2017 1765
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

1766 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1767

menu bar.
1768 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1769
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1770 11/24/2017
126 SNMP CPU Load Sensor
7.8.126 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
Remarks
§ It might not work to query data from a probe device via SNMP (querying localhost, 127.0.0.1,
or ::1). Add this device to PRTG 295 with the IP address that it has in your network and create
the SNMP sensor on this device instead.
Add Sensor
later.
Sensor Settings
11/24/2017 1771
218 .
default value.
SENSOR DISPLAY
for each channel.
1772 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 1773
SCANNING INTER VAL

requests.
requests.
apply.


time.
1774 11/24/2017


can choose between:
dependency.
11/24/2017 1775

menu bar.
1776 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1777
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1778 11/24/2017
127 SNMP Custom Sensor
7.8.127 SNM P Custom Sensor
The SNMP Custom sensor monitors a single parameter that is returned by a specific Object
Identifier (OID) using Simple Network Management Protocol (SNMP).
§ This sensor shows a single numerical value (int64) for a given OID. Each OID always refers to
a specific parameter of a certain SNMP device.
SNMP Custom Sensor
Remarks
§ Knowledge Base: How do I find out what OID I need to use for a custom sensor?
Add Sensor
later.
12/11/2017 1779
OID VALU ES
Channel Name Enter a name for the channel in which the sensor shows the
results for the given OID. Please enter a string. You can change this
value later in the corresponding channel settings 2915 of this sensor.
Value Type Select the expected numeric type of the results at the given OID.
Choose between:
§ Gauge (unsigned Int eger): Integer values, without an
operational sign, such as 10 or 120.
§ Gauge (signed int eger): For integer values, including an
operational sign, 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
218 .
1780 12/11/2017
default value.
OID VALU ES
OID Value Enter the OID of the SNMP object you want to receive numerical
data from.
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.
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. Use the default value 1 to not change the
received value. Please enter an integer value.
divisor here. Use the default value 1 to not change the received
value. Please enter an integer value.
12/11/2017 1781
OID VALU ES

change.
SENSOR DISPLAY
for each channel.
Inherited Settings
1782 12/11/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

12/11/2017 1783

time.


can choose between:
dependency.
1784 12/11/2017

menu bar.
12/11/2017 1785
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Video Tutorial: How to Set Up an SNMP Custom Sensor
§ https://www.paessler.com/support/videos/prtg-advanced/snmp-custom-and-library-sensor
Knowledge Base: How do I find out what OID I need to use for a custom sensor?
1786 12/11/2017

Notifications
Others
12/11/2017 1787
128 SNMP Custom Advanced Sensor
7.8.128 SNM P Custom Advanced Sensor
The SNMP Custom Advanced sensor monitors numerical values returned for Object Identifiers
(OIDs) using Simple Network Management Protocol (SNMP).
§ The sensor displays numerical values for given OIDs that refer to this specific SNMP device.
Up to 10 OIDs and corresponding numerical values are possible.
sensor setup.
The SNMP Library sensor 2044 will automatically create SNMP Custom Advanced sensors
when the imported Management Information Base (MIB) file contains single values.
SNMP Custom Adv anc ed Sensor
Remarks
1788 11/24/2017
Add Sensor
later.
OID VALU ES
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.
§ Enable: The sensor will create this channel. Specify name, OID,
value type, and unit for this channel below.
please add the sensor anew. It is not possible to enable or disable
sensor channels after creation of this sensor!
Sensor Settings
11/24/2017 1789
218 .
default value.
OID VALU ES
Name results at the given OID. Please enter a string.
Sensor Channel #x OID Enter the OID of the SNMP object you want to receive numerical
data from.
the validation of your entry during your typing entirely, add the
string norfccheck: to the beginning of your OID, for example,
norfccheck:2.0.0.0.1.
1790 11/24/2017
OID VALU ES
Sensor Channel #x Shows the value type of the numerical data that this sensor
Value Type receives from the given OID. Once a sensor is created, you cannot
Sensor Channel #x Define the unit of the numerical data that this sensor receives from
Unit the given OID. Choose between:
§ BytesBandwidth
§ BytesMemory
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Value Lookup
For more information about the available units, see the PRTG
custom sensors.
Sensor Channel #x This setting is only available if you select the Cust om unit option
Sensor Channel #x This setting is only available if you select the Value Lookup option
Value Lookup above. Choose a lookup 3345 file that you want to use with this
channel.
11/24/2017 1791
OID VALU ES
Sensor Channel #y This field shows the option you chose for this channel in the Add
Sensor 1789 dialog, Enable or Disable. Once a sensor is created,
If you created this channel, you can define the settings of this
channel as described above.
SENSOR DISPLAY
for each channel.
Inherited Settings
1792 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 1793

time.


can choose between:
dependency.
1794 11/24/2017

menu bar.
11/24/2017 1795
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

1796 11/24/2017
Notifications
Others
11/24/2017 1797
129 SNMP Custom String Sensor
7.8.129 SNM P Custom String Sensor
The SNMP Custom String sensor monitors a string returned by a specific Object Identifier (OID)
using Simple Network Management Protocol (SNMP). It can check for keywords. If you want to
set limits to 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
§ In the sensor message, the sensor shows the string you search 1800 for and which is the
reason for a current Warning or Down status 183 .
The SNMP Library sensor 2044 will automatically create SNMP Custom String sensors when
the imported Management Information Base (MIB) file contains string values.
SNMP Custom String Sensor
Remarks
§ Example: Number Extraction with Regular Expression 1808
1798 11/24/2017
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 1799
OID VALU ES
OID Value Enter the OID of the SNMP object you want to receive a string
from.
the validation of your entry entirely, add the string norfccheck: at
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 183 . Please enter an
integer value or leave the field empty.
change.
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 3355 . If the data does not include the
search pattern, the sensor shows a Down status 183 . Please enter a
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
asterisk * and question mark ? work here as placeholder,
whereas * stands for no or any number of characters and ?
stands for exactly one character (as known from Windows
search). You cannot disable this behavior, so the literal search for
these characters is not possible with plain text search.
Expression 3355 .
1800 11/24/2017
KEYWOR D SEAR CH

Expressions 3355 .
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 3355 . If the data does include the
search pattern, the sensor shows a Down status 183 . Please enter a
Expression 3355 .

Expressions 3355 .
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 3355 . If the data does not include the
search pattern, the sensor shows a Warning status 183 . Please
Expression 3355 .
11/24/2017 1801
KEYWOR D SEAR CH

Expressions 3355 .
Response Must Not Define which string must not be part of the data that is received
Include (Warning State) form the SNMP object at the given OID. You can either enter plain
text or a Regular Expression 3355 . If the data does include the
search pattern, the sensor shows a Warning status 183 . Please
Expression 3355 .

Expressions 3355 .
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.
1802 11/24/2017
EXTENDED
PR OCESSING
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 2915 ).
§ 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
1808 below.
Regular Expression This setting is only visible if you enable number extraction above.
Enter a Regular Expression 3355 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.

Expressions 3355 .
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.
11/24/2017 1803
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1804 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1805

time.


can choose between:
dependency.
1806 11/24/2017

menu bar.
11/24/2017 1807
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
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, that is 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.
1808 11/24/2017
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.
It is not possible to match an empty string with the PRTG regex sensor search.
PRTG supports PCRE regex. You cannot use regex options or flags. For more details, see
manual section Regular Expressions 3355 .
More

Notifications
Others
11/24/2017 1809
130 SNMP Custom String Lookup Sensor
7.8.130 SNM P Custom String Lookup Sensor
The SNMP Custom String Lookup sensor monitors a string that a specific Object Identifier (OID)
returns via Simple Network Management Protocol (SNMP). It can map the string directly to a
sensor status 183 by using a defined lookup file 3345 . Basically, this sensor type does a "reverse
lookup". You have to define all potential return strings in the lookup file as text values, each in
one lookup entry. Graphs and data tables show the value to which the string is mapped,
usually an integer (lookup type 3352 SingleInt ). See manual section SNMP Cust om St ring
Lookup Sensor—Example 1817 .
§ This sensor shows a retrieved string value and its status, as defined in the corresponding
lookup file.
SNMP Custom Lookup Sensor
Remarks
§ See manual section SNMP Cust om St ring Lookup Sensor—Example 1817 for a sample lookup
definition for this sensor type.
1810 11/24/2017
Add Sensor
later.
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 2915 of this sensor.
Lookup Select a lookup file that you stored in the \lookups\cust om

subfolder of your PRTG installation. This lookup file must contain all
potential strings that the monitored OID can return.
Sensor Settings
218 .
11/24/2017 1811
default value.
OID VALU ES
OID Value Enter the OID of the SNMP object you want to receive a string
from.
the validation of your entry entirely, add the string norfccheck: at
Lookup Shows the lookup file that this sensor uses. Once a sensor is
anew.
change.
1812 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1813
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1814 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1815

menu bar.
1816 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
Example
You have to provide all possible return strings for this sensor in one lookup file. For
example, consider an OID that can return one of the three strings Good, Deficient, or Bad.
Then you have to define a lookup file 3345 for this sensor that contains all these possible string
values as text, each text value in one lookup entry:
11/24/2017 1817
<?xml version="1.0" encoding="UTF-8"?>

<ValueLookup id="mylookupfile" desiredValue="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:n
<Lookups>
<SingleInt state="Ok" value="0">
Good
</SingleInt>
<SingleInt state="Warning" value="1">
Deficient
</SingleInt>
Bad
</SingleInt>
</Lookups>
</ValueLookup>
If a retrieved string matches one of the text values, the sensor maps it into the defined integer
value ("reverse lookup") that is shown, for example, in data graphs. Depending on the integer,
the sensor shows the according status and converts the integer back to the original string to
show it as channel value. If the OID returns a string that the lookup definition does not
contain, the sensor will show a Down status 183 with a corresponding error message.
For example, you create an SNMP Custom String Lookup sensor, apply the example lookup
definition from above (store it into the \lookups\cust om subfolder of your PRTG installation),
and the given OID returns the string Good. Then the sensor maps Good into the integer value
0, shown in the live graph of the sensor, for example. According to the status definition
state="Ok", the sensor status 183 is Up in this case. The integer 0 is converted back to the
string Good, which is shown as channel value.
The string match is not case sensitive.
Use the lookup type SingleInt for this sensor. BitFields and ranges are not supported!
If you imported an SNMP library 2049 (this is an oidlib file) that contains lookups 3345 (you can
see this in section Lookup in the MIB Importer), you can define your own sensor states for
returning values. Use the lookupname of the imported SNMP library as id parameter in a
custom lookup definition. This overrides the lookups that an oidlib might contain with your
own status definitions. See section Define Lookups—Cust omizing Lookups 3350 for details
about this mechanism.
More
1818 11/24/2017

Notifications
Others
11/24/2017 1819
131 SNMP Custom Table Sensor
7.8.131 SNM P Custom Table Sensor
The SNMP Custom Table sensor monitors entries from a table that is provided via Simple
Network Management Protocol (SNMP). You can create one new sensor per table row. For
each sensor, you can define up to ten channels. Each channel shows the value of one defined
table column.
§ It can show numerical values in up to 10 channels per table row.
sensor setup.
The SNMP Library sensor 2044 will automatically create SNMP Custom Table sensors when
the imported Management Information Base (MIB) file contains tables.
SNMP Custom Table Sensor
Remarks
§ Knowledge Base: What can I monitor with the SNMP Custom Table Sensor?
1820 11/24/2017
Add Sensor
later.
PRTG will create one SNMP Table sensor for each table row that you select in the Add Sensor
dialog. The settings you choose will be valid for all sensors that you create when you finish
this dialog.
SNMP TABLE
Table OID Enter the OID of the SNMP table you want to monitor. The OID
needs to point directly to an object that represents an SNMP table.
Without entering an OID, you cannot proceed to the sensor
and sensor channel creation.
Sensor Name Enter a meaningful name to identify the sensor. You can use the
placeholders [tablename] and [rowidentifier]. They will be replaced
with the name of the table and the identifying value of the chosen
row respectively. You can choose the column that provides the
row identifier in the Ident ificat ion Column option below.
You can also enter a valid OID that is part of a different SNMP table,
for example, [1.3.6.1.2.1.2.2.1.2], to query information that is not
contained in the current table. The same index as in the original
table will be added to the OID.
11/24/2017 1821
TABLE SPECIFIC
Table Choose the relevant table rows in which you find the data that you
want to monitor. You see a list with the names of all items that are
PRTG shows you the table that the OID you entered before
returns. To better find what you want to monitor, especially in
large tables, use the search function in the upper right corner.
Identification Column Define the identification column for the SNMP Table sensor(s) you
want to create. The sensor uses this column to uniquely identify
each table row. This column should preferably be unique because it
will allow the sensor to keep track of changing indexes.
The value of the column that you choose as the identification
column will replace the [rowident ifier] in the sensor name. This
allows you to distinguish sensors that are created for the same
SNMP table.
One new sensor is created for each table row you choose.
§ Enable: Create an additional channel and define all its
characteristics below, its name, column, value type, and unit.
It is not possible to enable or disable sensor channels after the
creation of this sensor!
All sensor channels that you define while creating an SNMP
Table sensor will be the same for all sensors for each table
row.
Value Type Select the expected type of the results in this channel. 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.
1822 11/24/2017
TABLE SPECIFIC
See below 1824 for the other channel settings that can be changed
also after the sensor has been created.
This sensor monitors numerical values only. Make sure that
you do not select columns that return strings because they
lead to a Down status 183 . For example, if you monitor an ifTable,
we recommend that you do not select an ifDescr column because
this will result in an error.
Sensor Settings
218 .
default value.
11/24/2017 1823
SNMP TABLE
Table OID Shows the OID of the SNMP table that this sensor monitors. Once
the sensor anew.
TABLE SPECIFIC
Identifier This is the value of the column that you selected as the
Ident ificat ion Column during the sensor creation. It is also
displayed in the sensor name to distinguish it from other sensors
you created for the same table with other table rows. You can
change the identifier if you want to.
Identification Column Shows the table column that you chose as the identification
column. Once a sensor is created, you cannot change this value. It
Name desired result. Please enter a string.
Sensor Channel #x Select the table column that together with the table row points to
Column the value that you want to monitor in this channel. You can choose
between the available columns of the table that you monitor.
Sensor Channel #x Shows the value type of the data that this sensor receives in this
Value Type channel. Once a sensor is created, you cannot change this value. It
Sensor Channel #x Define the unit of the data that this sensor receives in this channel.
Unit Choose between:
§ BytesBandwidth
§ BytesMemory
1824 11/24/2017
TABLE SPECIFIC
§ BytesDisk
§ Temperature
§ Percent
§ TimeResponse
§ TimeSeconds
§ TimeHours
§ Count
§ CPU
§ BytesFile
§ SpeedDisk
§ SpeedNet
§ Custom
§ Value Lookup
For more information about the available units, see the PRTG
custom sensors.
Sensor Channel #x This setting is only visible if you select the Cust om unit option
Sensor Channel #x This setting is only visible if you select the Value Lookup option
Value Lookup above. Select a lookup 3345 file that you want to use with this
channel.
Sensor Channel #x+1 Shows if you enabled or disabled a channel. Once a sensor is
anew.
11/24/2017 1825
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1826 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1827

time.


can choose between:
dependency.
1828 11/24/2017

menu bar.
11/24/2017 1829
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: What can I monitor with the SNMP Custom Table Sensor?
Knowledge Base: How to monitor a no-break (UPS) device complying to the UPS-MIB (RFC
1628)
1830 11/24/2017

Notifications
Others
11/24/2017 1831
132 SNMP Dell EqualLogic Logical Disk Sensor
7.8.132 SNM P Dell EqualLogic Logical Disk Sensor
The SNMP Dell EqualLogic Logical Disk sensor monitors a volume of a Dell EqualLogic storage
system via Simple Network Management Protocol (SNMP).
The sensor provides the following information:
§ Availability
§ Average read/write latency
§ Number of connections
§ Amount of read/written data
§ Operational status
§ Number of IOPS (Input/Output operations per second)
SNMP Dell EqualLogic Logic al Disk Sensor
Remarks
1832 11/24/2017
Add Sensor
later.
Select the volume(s) from the storage system that you want to monitor. PRTG will create one
sensor for each volume you choose in the Add Sensor dialog. The settings you choose will be
valid for all sensors that you create when you finish this dialog.
DELL EQU ALLOGIC SPECIFIC
Volume Select the volume(s) you want to add a sensor for. You see a list
Sensor Settings
218 .
11/24/2017 1833
default value.
Volume Shows the volume that this sensor monitors. Once a sensor is
anew.
Member ID Shows the identifier of the array member. Once a sensor is

anew.
Volume ID Shows the ID of the volume that this sensor monitors. Once a
the sensor anew.
Volume Description Shows the description of the volume that this sensor monitors.
SENSOR DISPLAY
1834 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1835
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1836 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1837

menu bar.
1838 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1839
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1840 11/24/2017
133 SNMP Dell EqualLogic Member Health Sensor
7.8.133 SNM P Dell EqualLogic M ember Health Sensor
The SNMP Dell EqualLogic Member Health sensor monitors the health of an array member of an
EqualLogic storage system via Simple Network Management Protocol (SNMP).
§ Member status
§ Cooling power of the fan module in rpm (rotations per minute)
§ Power supply status of cooling system
§ Temperature of the backplane
§ Temperature measured by temperature control module
§ System temperature
§ Member health status
§ RAID status
§ Average read/write latency in milliseconds or as percentage of the largest value
§ Free storage capacity
§ Amount of data handled per second
§ Number of spare drives available
11/24/2017 1841
SNMP Dell EqualLogic Member Health Sensor
Remarks
§ This sensor type works with SNMP v2c and SNMP v3. It does not support SNMP v1. Ensure
you set the correct SNMP Version in the Credent ials for SNMP Devices settings of the
parent device or inherit it from objects higher in the hierarchy 125 .
1842 11/24/2017
Add Sensor
later.
Select the disk(s) on the drive you want to monitor. PRTG creates one sensor for each disk
Array Member Select the array member(s) you want to add a sensor for. You see
items.
Sensor Settings
218 .
11/24/2017 1843
default value.
Array Member Shows the name of the member this sensor monitors. Once a
the sensor anew.
Group ID Shows the group ID of the disk that this sensor monitors.. Once a
the sensor anew.
Member ID Shows the group member ID of the disk that this sensor monitors.
SENSOR DISPLAY
1844 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1845
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1846 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1847

menu bar.
1848 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1849
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1850 11/24/2017
134 SNMP Dell EqualLogic Physical Disk Sensor
7.8.134 SNM P Dell EqualLogic Phy sical Disk Sensor
The SNMP Dell EqualLogic Physical Disk sensor monitors a disk in a Dell EqualLogic storage
§ Disk status
§ Bytes read/written
§ Failed transfers
§ Health status of disk
SNMP Dell EqualLogic Phy sic al Disk Sensor
Remarks
11/24/2017 1851
Add Sensor
later.
Select the array member(s) of the Dell EqualLogic storage system you want to monitor. PRTG
will create one sensor for each disk you choose in the Add Sensor dialog. The settings you
choose will be valid for all sensors that you create when you finish this dialog.
Disk Select the disk(s) you want to add a sensor for. You see a list with
Sensor Settings
218 .
1852 11/24/2017
default value.
Disk Shows the disk that this sensor monitors. Once a sensor is
anew.
Group ID Shows the group ID of the disk that this sensor monitors.. Once a
the sensor anew.
Member ID Shows the group member ID of the disk that this sensor monitors.
Disk Slot Shows the slot number of disk that this sensor monitors. Once a
the sensor anew.
Serial Number Shows the serial number of the disk that this sensor monitors.
Manufactured Shows the production date of the disk that this sensor monitors. If
this field is empty, the disk does not provide information about the
date (this depends on the manufacturer). Once a sensor is created,
11/24/2017 1853
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1854 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1855

time.


can choose between:
dependency.
1856 11/24/2017

menu bar.
11/24/2017 1857
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1858 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 1859
135 SNMP Dell Hardware Sensor
7.8.135 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
Remarks
§ Requires 1861 the Dell OpenManage Server Administrator to be installed on the monitored Dell
device.
§ Knowledge Base: What do I need to monitor Dell servers?
1860 11/24/2017
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, see the Knowledge Base: What do I need to monitor Dell servers?
Add Sensor
later.
Select the Dell performance counters you want to monitor. PRTG will create one sensor for
each OID you choose in the Add Sensor dialog. The settings you choose will be valid for all
DELL HAR DWAR E SPECIFIC
Library OIDs Select the performance counters you want to add a sensor for.
deselect all items.
Choose the counters that you want to monitor with caution!
We recommend that you select only a few counters in this
dialog. Use the search function in the table head to filter for
specific counters. Selecting too many library OIDs might result in
thousands of sensors or in an aborted sensor creation.
Sensor Settings
11/24/2017 1861
218 .
default value.
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 given OID. Please enter a string.
the multiplier here. Please enter an integer value.
divisor here. Please enter an integer value.
change.
1862 11/24/2017

SENSOR DISPLAY
for each channel.
Inherited Settings
11/24/2017 1863
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

1864 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1865

menu bar.
1866 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: What do I need to monitor Dell servers?

11/24/2017 1867
Notifications
Others
1868 11/24/2017
136 SNMP Dell PowerEdge Physical Disk Sensor
7.8.136 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
Remarks
§ Requires 1880 iDRAC 7 or the Dell OpenManage Server Administrator to be installed on the
monitored server.
§ Knowledge Base: I can't add Dell PowerEdge sensors to PRTG. What can I do?
§ Knowledge Base: Why does my Dell PowerEdge System Health sensor show a power unit
status error after iDRAC update?
§ Knowledge Base: My Dell PowerEdge sensor fails to validate disks and I can't add it. What can
I do?
11/24/2017 1869
Requirement: Dell OpenManage Server Administrator or iDRAC 7

Dell PowerEdge server to monitor it. Please make sure that you enable SNMP in the
You can also monitor Dell PowerEdge servers with this sensor type via Integrated Dell
Remote Access Controller (iDRAC) 7.
Add Sensor
later.
Select the disks you want to monitor. PRTG will create one sensor for each disk you select in
DELL POWER EDGE PHYSICAL DISK SETTINGS
Sensor Settings
1870 11/24/2017
218 .
default value.
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 that is used to get monitoring data. This is
either Dell OpenManage Server Administrator (OMSA) or Integrated
Dell Remote Access Controller (iDRAC).
11/24/2017 1871
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
1872 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 1873

time.


can choose between:
dependency.
1874 11/24/2017

menu bar.
11/24/2017 1875
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1876 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: I can't add Dell PowerEdge sensors to PRTG. What can I do?
Knowledge Base: My Dell PowerEdge sensor fails to validate disks and I can't add it. What can I
do?

Notifications
11/24/2017 1877
Others
1878 11/24/2017
137 SNMP Dell PowerEdge System Health Sensor
7.8.137 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.
SNMP Dell PowerEdge Sy stem Health Sensor
11/24/2017 1879
Remarks
§ Requires 1880 iDRAC 7 or the Dell OpenManage Server Administrator to be installed on the
monitored server.
§ Knowledge Base: I can't add Dell PowerEdge sensors to PRTG. What can I do?
§ Knowledge Base: Why does my Dell PowerEdge System Health sensor show a power unit
Requirement: Dell OpenManage Server Administrator or iDRAC 7

Dell PowerEdge server to monitor it. Please make sure that you enable SNMP in the
You can also monitor Dell PowerEdge servers with this sensor type via Integrated Dell
Remote Access Controller (iDRAC) 7.
Add Sensor
later.
Select the Dell PowerEdge chassis you want to monitor. PRTG will create one sensor for each
chassis you choose in the Add Sensor dialog. The settings you choose will be valid for all
1880 11/24/2017
DELL POWER EDGE SYSTEM HEALTH SPECIFIC
Chassis Select the chassis you want to add a sensor for. You see a list with
Sensor Settings
218 .
default value.
11/24/2017 1881
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 that 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.
1882 11/24/2017
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
11/24/2017 1883
SCANNING INTER VAL

apply.


time.

1884 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 1885

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1886 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: I can't add Dell PowerEdge sensors to PRTG. What can I do?
Knowledge Base: Why does my Dell PowerEdge System Health sensor show a power unit

Notifications
11/24/2017 1887
Others
1888 11/24/2017
138 SNMP Disk Free Sensor
7.8.138 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
Remarks
§ This sensor uses more generic Object Identifier (OID) values compared to the SNMP Linux
Disk Free Sensor 2058 .
Add Sensor
later.
11/24/2017 1889
Select the disk(s) you want to monitor. PRTG will create one sensor for each disk you choose
in the Add Sensor dialog. The settings you choose will be valid for all sensors that you create
DISK FR EE SETTINGS
Disk Select one or more disks you want to add a sensor for. You see a
items.
Sensor Settings
218 .
default value.
1890 11/24/2017
DISK FR EE SETTINGS
Disk Shows the name of the disk that this sensor is monitoring. This
value is shown for reference purposes only. We strongly
recommend that you only change it if Paessler support explicitly
asks you to do so. Wrong usage can result in incorrect monitoring
data!
SENSOR DISPLAY
for each channel.
11/24/2017 1891
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1892 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1893

can choose between:
dependency.
menu bar.
1894 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1895
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1896 11/24/2017
139 SNMP Hardware Status Sensor
7.8.139 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
Remarks
Add Sensor
later.
11/24/2017 1897
Select the hardware components you want to monitor. PRTG will create one sensor for each
component you choose in the Add Sensor dialog. The settings you choose will be valid for all
HAR DWAR E SPECIFIC
Hardware Component Select the hardware components you want to add a sensor for.
deselect all items.
Sensor Settings
218 .
default value.
1898 11/24/2017
HAR DWAR E SPECIFIC
Hardware Component Shows further information about the hardware component. Once a
Product ID
the sensor anew.
Description
Type
SENSOR DISPLAY
for each channel.
11/24/2017 1899
SENSOR DISPLAY
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
1900 11/24/2017
SCANNING INTER VAL

requests.
apply.


time.

11/24/2017 1901


can choose between:
dependency.
menu bar.
1902 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1903
More

Notifications
Others
1904 11/24/2017
140 SNMP HP BladeSystem Blade Sensor
7.8.140 SNM P HP BladeSy stem Blade Sensor
The SNMP HP BladeSystem Blade sensor monitors the status of an HP BladeSystem via Simple
Network Management Protocol (SNMP). It can show the following:
§ Blade status (OK, degraded, unknown, failed, other)

§ Power status (OK, on, off, power stagged off, unknown, other)
HP BladeSy stem Serv er Blade Sensor
Remarks
§ Make sure you add this sensor to a device whose IP/DNS name points to the HP
BladeSystem Enclosure hosting the Onboard Administrator!
Add Sensor
later.
Select the server blades you want to monitor. PRTG will create one sensor for each blade you
12/8/2017 1905
HP BLADESYSTEM SPECIFIC
Server Blade Select the blades you want to add a sensor for. You see a list with
Sensor Settings
218 .
default value.
1906 12/8/2017
HP BLADESYSTEM SPECIFIC
Server Blade Shows the server blade that this sensor monitors. Once a sensor
anew.
SENSOR DISPLAY
for each channel.
12/8/2017 1907
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1908 12/8/2017
SCANNING INTER VAL

apply.


time.

12/8/2017 1909

can choose between:
dependency.
menu bar.
1910 12/8/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
12/8/2017 1911
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om

Notifications
Others
1912 12/8/2017
141 SNMP HP BladeSystem Enclosure System Health Sensor
7.8.141 SNM P HP BladeSy stem Enclosure Sy stem Health Sensor
The SNMP HP BladeSystem Enclosure System Health sensor monitors the system health of an
HP BladeSystem device via Simple Network Management Protocol (SNMP). It can show the
following:
§ Enclosure condition of the BladeCenter (OK, degraded, failed, unknown, other)
HP BladeSy stem Sy stem Health Sensor
Remarks
§ Make sure you add this sensor to a device whose IP/DNS name points to the HP
BladeSystem Enclosure hosting the Onboard Administrator!
Add Sensor
later.
Sensor Settings
12/11/2017 1913
218 .
default value.
SENSOR DISPLAY
for each channel.
1914 12/11/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
12/11/2017 1915
SCANNING INTER VAL

requests.
requests.
apply.


time.
1916 12/11/2017


can choose between:
dependency.
12/11/2017 1917

menu bar.
1918 12/11/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
12/11/2017 1919
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om

Notifications
Others
1920 12/11/2017
142 SNMP HP LaserJet Hardware Sensor
7.8.142 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
Remarks
Add Sensor
later.
11/24/2017 1921
Select the categories you want to monitor. PRTG will create one sensor for each category you
Library OIDs Select the categories you want to add a sensor for. You see a list
The following performance counters for your printer are available:
§ Toner/St at us
§ Paper/St at us
§ Jam/St at us
Sensor Settings
218 .
1922 11/24/2017
default value.
HP LASER JET SPECIFIC
Selected Interface Shows the name of the category (performance counter) that this
change.
SENSOR DISPLAY
11/24/2017 1923
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
1924 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


11/24/2017 1925

time.


can choose between:
dependency.
1926 11/24/2017
menu bar.
11/24/2017 1927
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
1928 11/24/2017
Others
11/24/2017 1929
143 SNMP HP ProLiant Logical Disk Sensor
7.8.143 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
Remarks
§ Requires 1931 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
1931 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 that you use iLO 4 because this version applies its own dedicated SNMP
counters while iLO 3 only forwards SNMP counters from the particular operating system.
1930 11/24/2017
Requirement: HP System Management Tools

This sensor needs a specific HP system management tool to be installed on the target device
to report data via SNMP: HP Insight Management Agents. To receive SNMP data from RAID
controllers, you additionally need HP Insight Management WBEM Providers.
For more details and download links, see the Knowledge Base: Monitor HP ProLiant via
SNMP?
Some of the HP Object Identifiers (OIDs) that 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 that points to the address of the HP
iLO interface (if available) and add the sensor to this device. We recommend that you use 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
later.
Select the disks in the HP server you want to monitor. PRTG creates one sensor for each disk
HP PR OLIANT LOGICAL DISK SETTINGS
Sensor Settings
11/24/2017 1931
218 .
default value.
HP PR OLIANT LOGICAL DISK SETTINGS
Disk Shows the name of the disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
1932 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 1933
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

1934 11/24/2017

time.


can choose between:
dependency.
11/24/2017 1935

menu bar.
1936 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1937
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: Monitor HP ProLiant via SNMP

Notifications
Others
1938 11/24/2017
144 SNMP HP ProLiant Memory Controller Sensor
7.8.144 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
Remarks
§ Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory
Controller Sensor?
§ If modules are inserted at a later point, you have to add this sensor anew.
11/24/2017 1939

SNMP?
Add Sensor
later.
Select the memory controllers in the HP server you want to monitor. PRTG will create one
sensor for each controller you choose in the Add Sensor dialog. The settings you choose will
1940 11/24/2017
HP PR OLIANT MEMOR Y CONTR OLLER SETTINGS
Controller Select the controllers you want to add a sensor for. You see a list
Sensor Settings
218 .
default value.
11/24/2017 1941
HP PR OLIANT MEMOR Y CONTR OLLER SETTINGS
Controller Shows the name of the controller that this sensor monitors. Once
the sensor anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
1942 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 1943

time.


can choose between:
dependency.
1944 11/24/2017

menu bar.
11/24/2017 1945
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1946 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory
Controller Sensor?

Notifications
Others
11/24/2017 1947
145 SNMP HP ProLiant Network Interface Sensor
7.8.145 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
SNMP HP ProLiant Network Interfac e Sensor
1948 11/24/2017
Remarks
§ 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)".

SNMP?
Add Sensor
later.
Select the network interfaces in the HP server you want to monitor. PRTG will create one
sensor for each interface you choose in the Add Sensor dialog. The settings you choose will
11/24/2017 1949
HP PR OLIANT NETWOR K INTER FACE SETTINGS
Network Interface Select the interfaces you want to add a sensor for. You see a list
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
218 .
default value.
1950 11/24/2017
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
displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
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 to show different channels for this sensor.
for each channel.
You cannot use this option in combination with manual
Set t ings 2915 ). Manual scaling is not possible if you choose this
option.
§ 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.
You cannot use this option in combination with manual

Set t ings 2915 ). Manual scaling is not possible if you choose this
option.
You cannot show a positive/negative chart for a channel if

you choose to display its data in percent of maximum
(available in the Sensor Channels Set t ings 2915 ).
11/24/2017 1951
SENSOR DISPLAY
Stack Unit This setting is only available if you choose St ack channels on t op
of each ot her 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
SCANNING INTER VAL
information.
Choose between:
requests.
1952 11/24/2017
SCANNING INTER VAL

requests.
apply.


time.

11/24/2017 1953


can choose between:
dependency.
menu bar.
1954 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1955
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
1956 11/24/2017
146 SNMP HP ProLiant Physical Disk Sensor
7.8.146 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
· Up: ok
· Warning: predictive failure, erasing, erase done, erase queued, not authenticated
· Down: failed, SSD wear out
§ 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
12/11/2017 1957
Remarks
§ The sensor will only show Disk St at us and no other channels if it runs in "Limited
Monitoring" mode. For more information, see SNMP HP ProLiant Physical Disk sensor not
showing all information.

SNMP?
Add Sensor
later.
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 choose will be valid for all
1958 12/11/2017
HP PR OLIANT PHYSICAL DISK SETTINGS
Sensor Settings
218 .
default value.
12/11/2017 1959
HP PR OLIANT PHYSICAL DISK SETTINGS
Disk Shows the identifier of the disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
Inherited Settings
1960 12/11/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

12/11/2017 1961

time.


can choose between:
dependency.
1962 12/11/2017

menu bar.
12/11/2017 1963
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1964 12/11/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: SNMP HP ProLiant Physical Disk sensor not showing all information

Notifications
Others
12/11/2017 1965
147 SNMP HP ProLiant System Health Sensor
7.8.147 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
§ Integrated Management Log (IML) status: OK, Degraded, Failed, Other. This channel can help
to determine the reason for a Down status of the sensor.
These channels are created at run-time, depending on the available measurement components.
sensor setup.
1966 11/24/2017
SNMP HP ProLiant Sy stem Health Sensor
Remarks
§ This sensor has predefined limits for temperatures and broken frames. You can change these
limits individually in the channel settings 2915 .
§ RAID controllers that have no hard disks assigned might cause a Down status 183 . In this
case, deactivate the respective controller(s) in the HP ProLiant BIOS to avoid sensor errors.
11/24/2017 1967

SNMP?
Add Sensor
later.
Sensor Settings
218 .
1968 11/24/2017
default value.
SENSOR DISPLAY
for each channel.
11/24/2017 1969
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
1970 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 1971

can choose between:
dependency.
menu bar.
1972 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1973
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: Why is my SNMP HP ProLiant System Health sensor in error status after
updating PRTG?

Notifications
Others
1974 11/24/2017
148 SNMP IBM System X Logical Disk Sensor
7.8.148 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
Remarks
§ Requires 1975 the IBM Systems Director Platform to be installed on the target device.
§ Knowledge Base: What are the requirements to monitor IBM System x?
§ Knowledge Base: IBM System X sensors could not find any disk/data on this device (PE187/
PE188/PE194)
Requirement: IBM Systems Director Platform Agent

This sensor type needs the IBM Systems Director Platform Agent to be installed on the
target IBM device to monitor it via SNMP.
For more information, see the Knowledge Base: What are the requirements to monitor IBM
System x?
11/24/2017 1975
Add Sensor
later.
Select the logical disks of the IBM device you want to monitor. PRTG will create 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
Sensor Settings
218 .
1976 11/24/2017
default value.
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.
11/24/2017 1977
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
1978 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


time.
11/24/2017 1979


can choose between:
dependency.
1980 11/24/2017

menu bar.
11/24/2017 1981
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
1982 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: What are the requirements to monitor IBM System x?
Knowledge Base: IBM System X sensors could not find any disk/data on this device (PE187/
PE188/PE194)

Notifications
Others
11/24/2017 1983
149 SNMP IBM System X Physical Disk Sensor
7.8.149 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
Remarks
PE188/PE194)

System x?
1984 11/24/2017
Add Sensor
later.
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
items.
Sensor Settings
218 .
11/24/2017 1985
default value.
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.
1986 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 1987
SCANNING INTER VAL

requests.
requests.
apply.


time.
1988 11/24/2017


can choose between:
dependency.
11/24/2017 1989

menu bar.
1990 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 1991
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
PE188/PE194)

Notifications
Others
1992 11/24/2017
150 SNMP IBM System X Physical Memory Sensor
7.8.150 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
Remarks
PE188/PE194)

11/24/2017 1993
System x?
Add Sensor
later.
Select the memory modules of the IBM server you want to monitor. PRTG will create one
sensor for each module you choose in the Add Sensor dialog. The settings you choose will
IBM SYSTEM X PHYSICAL MEMOR Y SETTINGS
Module Select the memory modules you want to add a sensor for. You see
items.
Sensor Settings
218 .
1994 11/24/2017
default value.
IBM SYSTEM X PHYSICAL MEMOR Y SETTINGS
Name Shows further information about the module. Once a sensor is

Caption
anew.
Serial Number
Size
SENSOR DISPLAY
11/24/2017 1995
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
1996 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


11/24/2017 1997

time.


can choose between:
dependency.
1998 11/24/2017
menu bar.
11/24/2017 1999
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
2000 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
PE188/PE194)

Notifications
Others
11/24/2017 2001
151 SNMP IBM System X System Health Sensor
7.8.151 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:
§ Overall health
· Sy st em level or Normal (sensor status 183 Up)
· Non Crit ical (sensor status Warning)
· Crit ical (sensor status Down)

§ Temperatures of ambient and CPUs
§ Voltages of planars
§ Status of power supplies (OK or Error)
§ Fans: RPM (revolutions per minute) or the current percentage of the possible maximum
These channels are created at run-time, depending on the available measurement components.
sensor setup.
SNMP IBM Sy stem X Sy stem Health Sensor
Remarks
§ This sensor can also run directly on an Integrated Management Module (IMM) network port
and can show the overall health on IMMs.
2002 11/24/2017
§ 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 183 for this via channel limits 2916 .
PE188/PE194)

System x?
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
later.
Select the measurements of the IBM device you want to monitor. PRTG will create one sensor
for each measurement you choose in the Add Sensor dialog. The settings you choose will be
valid for all sensors that you create when you finish this dialog.
11/24/2017 2003
IBM SYSTEM X SYSTEM HEALTH SPECIFIC
Measurement Select the measurements you want to add a sensor for. You see a
items.
Sensor Settings
218 .
default value.
2004 11/24/2017
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.
11/24/2017 2005
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
2006 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 2007

can choose between:
dependency.
menu bar.
2008 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2009
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
PE188/PE194)

Notifications
Others
2010 11/24/2017
152 SNMP interSeptor Pro Environment Sensor
7.8.152 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 show the following as measured by the Jacarta interSeptor Pro device:
§ Temperature
§ Humidity
SNMP interSeptor Pro Env ironment Sensor
Remarks
§ 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 the IP address of PRTG.
Add Sensor
later.
Select the measuring points of interSeptor Pro device you want to monitor. PRTG will create
one sensor for each measuring point you choose in the Add Sensor dialog. The settings you
choose will be valid for all sensors that you create when you finish this dialog.
11/24/2017 2011
INTER SEPTOR ENVIR ONMENT SPECIFIC
Measuring Point Select the measuring points you want to add a sensor for. You see
items.
Sensor Settings
218 .
default value.
2012 11/24/2017
INTER SEPTOR ENVIR ONMENT SPECIFIC
Name Shows information about the measurement that this sensor

Measuring Point Shows the measuring point that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
11/24/2017 2013
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
2014 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 2015

can choose between:
dependency.
menu bar.
2016 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
2018 11/24/2017
153 SNMP Juniper NS System Health Sensor
7.8.153 SNM P Juniper NS Sy stem Health Sensor
The SNMP Juniper NS System Health sensor monitors the system health of a Juniper NetScreen
device using Simple Network Management Protocol (SNMP).
§ CPU utilization
§ Fan status
§ Power supply status
§ System temperature
§ Memory usage in percent
§ Session usage in percent
These channels are created at run-time, depending on the available measurement components
of your Juniper NetScreen device. Which channels the sensor actually shows might depend on
the monitored device and the sensor setup.
SNMP Juniper NS Sy stem Health Sensor
Remarks
11/24/2017 2019
Add Sensor
later.
Sensor Settings
218 .
default value.
2020 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 2021
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

2022 11/24/2017

time.


can choose between:
dependency.
11/24/2017 2023

menu bar.
2024 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2025
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
2026 11/24/2017
154 SNMP LenovoEMC Physical Disk Sensor
7.8.154 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 183 Up),

§ Unknown (sensor status Warning)
§ Foreign (sensor status Warning)
§ Faulted (sensor status Down)
§ Missing (sensor status Down)
SNMP Lenov oEMC Phy sic al Disk Sensor
Remarks
11/24/2017 2027
Add Sensor
later.
Select the physical disks in the LenovoEMC NAS. PRTG creates one sensor for each disk you
LENOVOEMC PHYSICAL DISK SETTINGS
Sensor Settings
218 .
2028 11/24/2017
default value.
LENOVOEMC NAS 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.
SENSOR DISPLAY
11/24/2017 2029
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
2030 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


11/24/2017 2031

time.


can choose between:
dependency.
2032 11/24/2017
menu bar.
11/24/2017 2033
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
2034 11/24/2017
Others
11/24/2017 2035
155 SNMP LenovoEMC System Health Sensor
7.8.155 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 183 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.
SNMP Lenov oEMC Sy stem Health Sensor
2036 11/24/2017
Remarks
Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 2037
SENSOR DISPLAY
for each channel.
Inherited Settings
2038 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 2039

time.


can choose between:
dependency.
2040 11/24/2017

menu bar.
11/24/2017 2041
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
2042 11/24/2017
Others
11/24/2017 2043
156 SNMP Library Sensor
7.8.156 SNM P Library Sensor
The SNMP Library sensor uses a compiled Management Information Base (MIB) library file to
create sensors that monitor a device via Simple Network Management Protocol (SNMP). This
approach provides custom monitoring beyond the standard SNMP sensors of PRTG.
The content of the MIB file will determine which data types are available for monitoring. When
you create the sensor, it will provide a list of counters that came back from the target device
based on checking every Object Identifier (OID) in the MIB. From this list, you can choose what
you want to monitor.
The SNMP Library sensor will automatically create the following custom SNMP sensor types
based on the data types available in the MIB:
§ SNMP Cust om Advanced sensors 1788 for all OIDs the return single values
§ SNMP Cust om St ring sensors 1798 for all OIDs that return string values
§ SNMP Cust om Table sensors 1820 for all OIDs that return tables
The SNMP Library sensor is not actually a sensor type and will not appear as running
sensor. It is a sensor that uses the meta-scan facility of the PRTG probe to find or match
OIDs from an MIB and eases the creation of custom sensors, because you do not have to
enter the OIDs manually.
To monitor SNMP capable devices and add sensors using the SNMP Library sensor, download
the manufacturer's MIB files for the target device, convert the MIB file to the Paessler oidlib
format, and import it into PRTG. To make setting up your monitoring as convenient as
possible, PRTG comes with pre-compiled oidlib library files that already contain the OIDs of
SNMP counters for the most common devices in a network.
For more details, see the Knowledge Base: How do SNMP, MIBs and OIDs work?
2044 11/24/2017
SNMP Custom Adv anc ed Sensor Created by SNMP Library
Remarks
§ Knowledge Base: How do SNMP, MIBs and OIDs work?
§ Knowledge Base: How can I import my MIB files into PRTG?
§ Knowledge Base: Can't find a sensor for my device in PRTG but I believe it supports SNMP.
How to proceed?
Add Sensor
Manually add 309 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 server installation directory—both the
ones delivered with PRTG and your own files.
11/24/2017 2045
List of SNMP Library Files
The filenames on the list indicate the likely purpose. Select a name that appears appropriate for
your device (for example, choose an MIB file that you imported before) and confirm via OK.
Often, the 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, click Cancel and try adding the sensor with another file.
The SNMP Library sensor takes a list of OIDs that you imported from an MIB file into an oidlib
and tests the OIDs against a device to find the OIDs the device supports. This discovery
process is the meta-scan.
If counters were found for your device, the sensor settings will open with a list of available
monitoring items for you to select from. PRTG sorts the list in advance to make the related
values sequential in the list.
2046 11/24/2017
List of SNMP Single Values: Sorted by MIB, Category , Name
List of SNMP Table Values: Sorted by MIB, Category (Table Name/OID), Row, Name
The list of SNMP table values presents row values sequentially and makes it easier for you to
select the values you are interested in.
You can also use the search function to find the desired group or category. The search
matches individual strings so if your string has a space in it, enclose the search string in
quotes.
11/24/2017 2047
Select the desired counters and click Save. PRTG will now create sensors based on the
OID types of the selected entries.
§ For selected SNMP single values, PRTG will create SNMP Cust om Advanced sensors 1788 with
up to 10 channels for 10 OIDs each. For example, 22 selected single values will result in 3
sensors: 2 sensors with 10 channels and 1 sensor with 2 channels.
§ If you select OIDs that return string values, PRTG will create one SNMP Cust om St ring
sensor 1798 for each selected entry that returns a string value.
§ For selected SNMP table entries, PRTG will create SNMP Cust om Table sensors 1820 with up
to 10 channels for 10 columns per row.
Once a custom SNMP sensor is created, you can create a device template 2954 from it and
prepare it for distribution. For example, you can refine the template with better name
templates.
Default OIDLIB Files Overview

The following files are included in PRTG and allow the extension of your SNMP monitoring to
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.
§ 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.
2048 11/24/2017
§ 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.
This file may detect a very large number of interfaces. It may take a few seconds until the
selection table is shown.
§ Linux SNMP (Framework Proxy Not i v2).oidlib

§ Linux SNMP (IP Net SNMP Not i OSPF RMON SMUX ).oidlib
§ Linux SNMP (Source TCP UCD UDP).oidlib

§ 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.
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, see section Dat a St orage 3383 .
For more information about the MIB Import er and to download this tool, see the
Knowledge Base: How can I import my MIB files into PRTG?
If your imported oidlib file contains lookups 3345 (you can see this in section Lookup in the
MIB Importer), you can define your own sensor states for returning values. Add an SNMP
Library sensor using this oidlib. PRTG will then create a lookup definition file using the
lookupname of the chosen library as id parameter.
11/24/2017 2049
Important: The lookups will be added without state definitions, so the sensor will show a
Warning status 183 by default! You have to edit the corresponding lookup files to get reliable
alarms. Please override the lookup definition with your own custom lookup as described in
section Define Lookups—Cust omizing Lookups 3350 .
PRTG in the cloud does not support the import of MIB files. You can use the SNMP Library
sensor only with the default oidlib files in PRTG in the cloud.
SNMP Library Sensor—Add Sensor Settings

SNMP LIBR AR Y SPECIFIC
Library 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 parameters 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.
Choose one or more items by adding a check mark in front of the
the check box in the table head. Use the search box to narrow
down to your desired items.
Depending on the kind of the chosen entries, PRTG will create the
following sensor types:
§ SNMP Cust om Advanced sensor 1788 : one sensor for every 10
single values
§ SNMP Cust om St ring sensor 1798 : one sensor for each selected
entry that returns a string value
§ SNMP Cust om Table sensor 1820 : one sensor for each selected
table row with up to 10 channels representing values in the
columns of the same row
Sensor Settings
2050 11/24/2017
218 .
default value.
SENSOR SPECIFIC
The available sensor settings depend on the sensor type that the SNMP Library sensor
has created. For details about settings, see the manual sections of these sensor types:
§ SNMP Cust om Advanced sensor 1790
§ SNMP Cust om St ring sensor 1799
§ SNMP Cust om Table sensor 1824
SENSOR DISPLAY
11/24/2017 2051
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
2052 11/24/2017
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

11/24/2017 2053

time.


can choose between:
dependency.
2054 11/24/2017

menu bar.
11/24/2017 2055
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More
Knowledge Base: How do SNMP, MIBs and OIDs work?
Knowledge Base: How can I import my MIB files into PRTG?
Knowledge Base: Can't find a sensor for my device in PRTG but I believe it supports SNMP. How
to proceed?
Knowledge Base: How can I monitor EMC Isilon storage systems with PRTG?
2056 11/24/2017

Notifications
Others
11/24/2017 2057
157 SNMP Linux Disk Free Sensor
7.8.157 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
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, see the Knowledge Base: Why do
SSH Disk Free and SNMP Linux Disk Free show different values for my target Linux system?
SNMP Linux Disk Free Sensor
Remarks
§ Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values for
my target Linux system?
2058 11/24/2017
§ Knowledge Base: Checklist: Setting up SNMP on Linux

Add Sensor
later.
Sensor Settings
218 .
default value.
11/24/2017 2059
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 183 , depending
on the data provided by all drives that this sensor monitors. If you want to individually define
limits for separate channels, please use the limit settings in the Sensor Channels Set t ings
2915 .
All limits that you define here are valid in addition to the limits defined in the particular
Channel settings! The limits are valid simultaneously, so the first limit that is breached
applies.
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 that are valid for all
percentage channels. The sensor only uses limits that 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 that 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.
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 2915 . 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.
2060 11/24/2017
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.
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
space of one of your drives undercuts this percent value, the
sensor switches to Down. Please enter an integer value or leave
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 that are valid for all byte size
channels. The sensor only uses limits that you define in the
settings of the particular free space in bytes 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 that 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
will switch to Down. Please enter an integer value or leave the field
empty.
11/24/2017 2061
Upper Warning 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
space of one of your drives overruns this bytes 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 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
switches to Warning. Please enter an integer value or leave the
field empty.
Lower Error 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
switches to Down. Please enter an integer value or leave the field
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.
2062 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 2063
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

2064 11/24/2017

time.


can choose between:
dependency.
11/24/2017 2065

menu bar.
2066 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2067
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
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

Notifications
Others
2068 11/24/2017
158 SNMP Linux Load Average Sensor
7.8.158 SNM P Linux Load Average Sensor
The SNMP Linux 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

SNMP Linux Load Av erage Sensor
Remarks
Add Sensor
later.
Sensor Settings
11/24/2017 2069
218 .
default value.
SENSOR DISPLAY
for each channel.
2070 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 2071
SCANNING INTER VAL

requests.
requests.
apply.


time.
2072 11/24/2017


can choose between:
dependency.
11/24/2017 2073

menu bar.
2074 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

11/24/2017 2075
Notifications
Others
2076 11/24/2017
159 SNMP Linux Meminfo Sensor
7.8.159 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
Remarks
11/24/2017 2077
Add Sensor
later.
Sensor Settings
218 .
default value.
2078 11/24/2017
SENSOR DISPLAY
for each channel.
Inherited Settings
SCANNING INTER VAL
information.
11/24/2017 2079
SCANNING INTER VAL
Choose between:
requests.
requests.
apply.

2080 11/24/2017

time.


can choose between:
dependency.
11/24/2017 2081

menu bar.
2082 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2083
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
2084 11/24/2017
160 SNMP Linux Physical Disk Sensor
7.8.160 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
Remarks
11/24/2017 2085
Add Sensor
later.
Select the disks of the Linux/Unix system you want to monitor. PRTG creates one sensor for
PHYSICAL DISK SETTINGS
Sensor Settings
218 .
2086 11/24/2017
default value.
PHYSICAL DISK SETTINGS
Disk Shows further information about the disk that this sensor
Bitmask please add the sensor anew.
SENSOR DISPLAY
for each channel.
11/24/2017 2087
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
2088 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


time.
11/24/2017 2089


can choose between:
dependency.
2090 11/24/2017

menu bar.
11/24/2017 2091
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
2092 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 2093
161 SNMP Memory Sensor
7.8.161 SNM P M emory Sensor
The SNMP Memory sensor monitors the memory usage of a system via Simple Network
Management Protocol (SNMP).
§ Available memory in bytes

§ Available memory in percent
§ Total memory
This sensor uses more generic Object Identifier (OID) values compared to the SNMP Linux
Meminfo Sensor 2077 .
SNMP Memory Sensor
Remarks
2094 11/24/2017
Add Sensor
later.
Select the memory types you want to monitor. PRTG will create one sensor for each memory
type you choose in the Add Sensor dialog. The settings you choose will be valid for all
MEMOR Y SETTINGS
Memory Select one or more memory types you want to add a sensor for.
deselect all items.
Sensor Settings
218 .
11/24/2017 2095
default value.
MEMOR Y SETTINGS
Memory Shows the type of the memory that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
for each channel.
2096 11/24/2017
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 2097
SCANNING INTER VAL

requests.
requests.
apply.


time.
2098 11/24/2017


can choose between:
dependency.
11/24/2017 2099

menu bar.
2100 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2101
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
2102 11/24/2017
162 SNMP NetApp Disk Free Sensor
7.8.162 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
Remarks
§ Knowledge Base: How can I monitor capacity and used disk space on a NetApp?
11/24/2017 2103
Add Sensor
later.
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
Sensor Settings
218 .
2104 11/24/2017
default value.
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.
11/24/2017 2105
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
2106 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


time.
11/24/2017 2107


can choose between:
dependency.
2108 11/24/2017

menu bar.
11/24/2017 2109
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
2110 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More
Knowledge Base: How can I monitor capacity and used disk space on a NetApp?

Notifications
Others
11/24/2017 2111
163 SNMP NetApp Enclosure Sensor
7.8.163 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
Remarks
2112 11/24/2017
Add Sensor
later.
Select the power supply and cooling measurements of an enclosure on a NetApp you want to
monitor. PRTG will create one sensor for each enclosure/measurement combination you
NETAPP ENCLOSU R E SETTINGS
Enclosure Select the enclosures with the measurement you want to add a
Sensor Settings
218 .
11/24/2017 2113
default value.
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

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 183 if a measurement is not available. We
recommend that you use this setting to not miss any hardware
errors.
2114 11/24/2017
NETAPP SPECIFIC
§ Int erpret as valid: Choose this option to handle unavailable

measurements as valid sensor results to keep the sensor in Up
status 183 . 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 will interpret this as 0.
We recommend that you use the lookup file
prt g.st andardlookups.net app.not available.ovl for
channels with unavailable measurements if you choose this
option. This will replace 0 with the message Not Available. Open
the Sensor Channels Set t ings 2915 of the affected channel(s) and
choose this file in section Value Lookup. For details, see
section Define Lookups 3345 .
SENSOR DISPLAY
for each channel.
11/24/2017 2115
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
2116 11/24/2017
SCANNING INTER VAL

apply.


time.

11/24/2017 2117

can choose between:
dependency.
menu bar.
2118 11/24/2017

ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2119
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
2120 11/24/2017
164 SNMP NetApp I/O Sensor
7.8.164 SNM P NetApp I/O Sensor
The SNMP NetApp I/O sensor monitors input/output operations (IOPS) on a NetApp storage
§ 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
11/24/2017 2121
SNMP NetApp I/O Sensor
Remarks
Add Sensor
later.
Sensor Settings
2122 11/24/2017
218 .
default value.
SENSOR DISPLAY
for each channel.
11/24/2017 2123
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
2124 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


time.
11/24/2017 2125


can choose between:
dependency.
2126 11/24/2017

menu bar.
11/24/2017 2127
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
2128 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 2129
165 SNMP NetApp License Sensor
7.8.165 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
detect when a NetApp license is going to expire.
SNMP NetApp Lic ense Sensor
Remarks
Add Sensor
later.
Select the NetApp license you want to monitor. PRTG will create one sensor for each license
2130 11/24/2017
NETAPP LICENSE SETTINGS
License for Service Select the licenses you want to add a sensor for. You see a list
Sensor Settings
218 .
default value.
11/24/2017 2131
NETAPP LICENSE SETTINGS
License for Service Shows the name of the service whose license this sensor
SENSOR DISPLAY
for each channel.
Inherited Settings
2132 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

11/24/2017 2133

time.


can choose between:
dependency.
2134 11/24/2017

menu bar.
11/24/2017 2135
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
2136 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 2137
166 SNMP NetApp Logical Unit Sensor
7.8.166 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
2138 11/24/2017
Remarks
Add Sensor
later.
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 choose will be valid for all sensors
Logical Unit Select the logical units you want to add a sensor for. You see a list
Sensor Settings
11/24/2017 2139
218 .
default value.
NETAPP LOGICAL U NIT SETTINGS
Logical Unit Shows the name of the logical unit that this sensor monitors. Once
the sensor anew.
SENSOR DISPLAY
2140 11/24/2017
SENSOR DISPLAY

for each channel.
Inherited Settings
SCANNING INTER VAL
information.
Choose between:
11/24/2017 2141
SCANNING INTER VAL

requests.
requests.
apply.


2142 11/24/2017

time.


can choose between:
dependency.
11/24/2017 2143
menu bar.
2144 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2145
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
2146 11/24/2017
167 SNMP NetApp Network Interface Sensor
7.8.167 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
Remarks
Add Sensor
later.
Select the network interfaces on the NetApp you want to monitor. PRTG will create one
sensor for each interface you choose in the Add Sensor dialog. The settings you choose will
11/24/2017 2147
NETAPP NETWOR K INTER FACE SETTINGS
Network Interface Select the interfaces you want to add a sensor for. You see a list
Sensor Settings
218 .
default value.
2148 11/24/2017
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.
Inherited Settings
11/24/2017 2149
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.

2150 11/24/2017

time.


can choose between:
dependency.
11/24/2017 2151

menu bar.
2152 11/24/2017
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
11/24/2017 2153
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
2154 11/24/2017
168 SNMP NetApp System Health Sensor
7.8.168 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.
11/24/2017 2155
SNMP NetApp Sy stem Health Sensor
Remarks
Add Sensor
later.
Sensor Settings
2156 11/24/2017
218 .
default value.
SENSOR DISPLAY
for each channel.
11/24/2017 2157
SENSOR DISPLAY

Inherited Settings
SCANNING INTER VAL
information.
Choose between:
2158 11/24/2017
SCANNING INTER VAL

requests.
requests.
apply.


time.
11/24/2017 2159


can choose between:
dependency.
2160 11/24/2017

menu bar.
11/24/2017 2161
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
2162 11/24/2017
information.
§ Bandwidt h
§ Memory
§ Disk
§ File
§ Cust om
More

Notifications
Others
11/24/2017 2163
169 SNMP Poseidon Environment Sensor
7.8.169 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
Remarks
Add Sensor
later.
To monitor performance counters for environmental measurements on Poseidon hardware,

PRTG will create one sensor for each measuring point you choose in the Add Sensor dialog.
The settings you choose will be valid for all sensors that you create when you finish this
dialog.
2164 11/24/2017
POSEIDON ENVIR ONMENT SPECIFIC
Measuring Point Select the measurements you want to add a sensor for. You see a
items.
Sensor Settings
218 .
default value.
11/24/2017 2165
POSEIDON ENVIR ONMENT SPECIFIC
Name Shows further information about the measurement. Once a sensor

Unit
anew.
Measuring Point
SENSOR DISPLAY
for each channel.
Inherited Settings
2166 11/24/2017
SCANNING INTER VAL
information.
Choose between:
requests.
requests.
apply.
11/24/2017 2167
SCANNING INTER VAL


time.

2168 11/24/2017

can choose between:
dependency.
menu bar.
11/24/2017 2169
ACCESS R IGHTS
information.
monitoring results.
rights settings.
option.
More

Notifications
2170 11/24/2017
Others
11/24/2017 2171
170 SNMP Printer Sensor
7.8.170 SNM P Printer Sensor
The SNMP Printer sensor is a generic sensor that monitors various types of printers via Simple
§ 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
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
2172 11/24/2017
170 SNMP Printer Sensor
Add Sensor
shows the setting fields that are required for creating the

Prtgmanual PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Prtgmanual PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

PRTG Net work Monit or User Manual

Printed: December 2017 in Nuremberg

Part 1 Welcome to PRTG Network M onitor 14

Part 2 Quick Start Guide 46

Part 3 Using PRTG in the Cloud 62

Part 4 Installing the Software 76

Part 5 Understanding Basic Concepts 116

Part 6 Ajax Web Interface—Basic Procedures 156

Part 7 Ajax Web Interface—Device and Sensor Setup 266

Amazon CloudWatch SQS Sensor 544

IMAP Sensor 1067

SMTP&POP3 Round Trip Sensor 1653

SNMP NetApp I/O Sensor 2121

Windows Print Queue Sensor 2607

Part 8 Ajax Web Interface—Advanced Procedures 2938

Context Menus 2999

Part 9 Enterprise Console 3168

Part 10 PRTG Apps for M obile Network M onitoring 3222

Part 11 Sensor Technologies 3226

Part 12 PRTG Administration Tool 3296

Part 13 Advanced Topics 3332

Part 14 Appendix 3388

4 Support and Troubleshooting 3403

1 Welcome to PRTG Network Monitor

A PRTG Network Monitor Standard Installation

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 is PRTG for?

Monitoring with PRTG

§ Monitoring and alerting you to up and downtimes or slow servers

What is Included in PRTG?

1.3 New in This Version

We provide three release channels for PRTG on premises:

1.4 Available Licenses

There are three different PRTG flavors available.

§ Free for personal and commercial use.

This option is not available in PRTG in the cloud.

§ Can monitor an unlimited number of sensors.

§ Can monitor a maximum number of sensors (please consider our recommendations 28 ).

§ Supports all available sensor types.

1.5 System Requirements

System Requirements for PRTG Core Server (PRTG on Premises)

System Requirements for PRTG Remote Probes

Planning a PRTG on Premises Installation With Hundreds of Sensors or More?

For more information, see section Det ailed Sy st em Requirement s 26 .

1.5.1 Detailed Sy stem Requirements

§ Supported Operating Systems 26

§ Network Size: Recommendations 28

§ Running PRTG on Virtual Machines 30

§ Running PRTG in a Failover Cluster 30

§ Web Browser Requirements 31

§ Requirements for Monitored Devices 31

§ Requirements for the Enterprise Console 32

§ Requirements for Smartphones 32

Supported Operating Systems for PRTG Server and Remote Probes

§ Microsoft Windows Server 2012 R2* (recommended)

§ the operating system is a 64-bit Windows system, and

§ the system provides 6 GB RAM or more.

Hardware Requirements for PRTG Server and Remote Probes

Network Size: Recommendations