PRT G Manual

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

1
2
3
4
5
About this Document

Key Features
New in This Version
Available Licenses
System Requirements
Detailed System Requirements
16
17
19
20
22
23
32
Part 2 Quick Start Guide

1 ONEDownload, Installation, and First Login
2 TWOSmart Setup
34
37
48
Part 3 Installing the Software

1
2
3
4
5
6
7
8
9
Download PRTG
Update From Previous Versions
Install a PRTG Core Server
Install a PRTG Cluster
Enter a License Key
Activate the Product
Install a PRTG Remote Probe
Install the Enterprise Console
Uninstall PRTG Products
49
51
56
61
62
65
67
72
78
82
Part 4 Understanding Basic Concepts

1
2
3
4
5
6
7
8
9
10
11
Architecture and User Interfaces

Clustering
Object Hierarchy
Inheritance of Settings
Tags
Dependencies
Scheduling
Notifying
User Access Rights
Data Reporting
IPv6
83
87
89
94
96
98
99
100
101
104
105
108
Part 5 Ajax Web InterfaceBasic Procedures

1 Login
2 SSL Certificate Warning
3 Welcome Page
Customer Service
110
113
117
121
3
Contents
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
General Layout
Sensor States
Review Monitoring Data
Compare Sensors
Historic Data Reports
Similar Sensors
Recommended Sensors
Object Settings
Alarms
System Information
Logs
Tickets
Working with Table Lists
Object Selector
Priority and Favorites
Pause
Context Menus
Hover Popup
Main Menu Structure
123
135
137
143
146
151
155
159
161
164
169
171
178
181
182
185
186
199
200
218
Part 6 Ajax Web InterfaceDevice and Sensor Setup

1 Auto-Discovery
2 Create Objects Manually
Add a Group
Add a Device
Add a Sensor
3 Manage Device Tree
4 Root Group Settings
5 Probe Settings
6 Group Settings
7 Device Settings
8 Sensor Settings
List of Available Sensor Types
Active Directory Replication Errors Sensor
ADO SQL v2 Sensor
Amazon CloudWatch Alarm Sensor
Amazon CloudWatch EBS Sensor
Amazon CloudWatch EC2 Sensor
Amazon CloudWatch ElastiCache Sensor
Amazon CloudWatch ELB Sensor
Amazon CloudWatch RDS Sensor
Amazon CloudWatch SNS Sensor
Amazon CloudWatch SQS Sensor
Business Process Sensor
Cisco IP SLA Sensor
Citrix XenServer Host Sensor
Citrix XenServer Virtual Machine Sensor
Cloud HTTP Sensor
4
219
236
237
244
256
258
260
278
299
324
347
348
367
378
392
402
413
425
436
447
459
470
481
492
502
513
523
Contents
Cloud Ping Sensor

Cluster Health Sensor
Common SaaS Sensor
Core Health Sensor
Dell PowerVault MDi Logical Disk Sensor
Dell PowerVault MDi Physical Disk Sensor
DHCP Sensor
DNS Sensor
Docker Container Status Sensor
Dropbox Sensor
Enterprise Virtual Array Sensor
Event Log (Windows API) Sensor
Exchange Backup (Powershell) Sensor
Exchange Database (Powershell) Sensor
Exchange Database DAG (Powershell) Sensor
Exchange Mail Queue (Powershell) Sensor
Exchange Mailbox (Powershell) Sensor
Exchange Public Folder (Powershell) Sensor
EXE/Script Sensor
EXE/Script Advanced Sensor
File Sensor
File Content Sensor
Folder Sensor
FTP Sensor
FTP Server File Count Sensor
Google Analytics Sensor
Google Drive Sensor
HTTP Sensor
HTTP Advanced Sensor
HTTP Apache ModStatus PerfStats Sensor
HTTP Apache ModStatus Totals Sensor
HTTP Content Sensor
HTTP Data Advanced Sensor
HTTP Full Web Page Sensor
HTTP Push Count Sensor
HTTP Push Data Sensor
HTTP Push Data Advanced Sensor
HTTP Transaction Sensor
HTTP XML/REST Value Sensor
Hyper-V Cluster Shared Volume Disk Free Sensor
Hyper-V Host Server Sensor
Hyper-V Virtual Machine Sensor
Hyper-V Virtual Network Adapter Sensor
Hyper-V Virtual Storage Device Sensor
IMAP Sensor
IP on DNS Blacklist Sensor
IPFIX Sensor
IPFIX (Custom) Sensor
IPMI System Health Sensor
jFlow V5 Sensor
jFlow V5 (Custom) Sensor
533
542
547
555
562
571
581
591
599
609
619
629
639
649
659
669
679
689
699
711
722
731
741
750
758
768
780
790
800
816
826
836
848
859
870
879
890
901
915
930
940
949
960
971
980
994
1003
1015
1025
1035
1047
5
Contents
LDAP Sensor
Microsoft OneDrive Sensor
Microsoft SQL v2 Sensor
MySQL v2 Sensor
NetApp cDOT Aggregate (SOAP) Sensor
NetApp cDOT I/O (SOAP) Sensor
NetApp cDOT Physical Disk (SOAP) Sensor
NetApp cDOT System Health (SOAP) Sensor
NetFlow V5 Sensor
NetFlow V5 (Custom) Sensor
NetFlow V9 Sensor
Oracle SQL v2 Sensor
Oracle Tablespace Sensor
Packet Sniffer Sensor
Packet Sniffer (Custom) Sensor
PerfCounter Custom Sensor
PerfCounter IIS Application Pool Sensor
Ping Sensor
Ping Jitter Sensor
POP3 Sensor
Port Sensor
Port Range Sensor
PostgreSQL Sensor
Probe Health Sensor
Python Script Advanced Sensor
QoS (Quality of Service) One Way Sensor
QoS (Quality of Service) Round Trip Sensor
RADIUS v2 Sensor
RDP (Remote Desktop) Sensor
Share Disk Free Sensor
Sensor Factory Sensor
sFlow Sensor
sFlow (Custom) Sensor
SFTP Secure File Transfer Protocol Sensor
SIP Options Ping Sensor
SMTP Sensor
SMTP&IMAP Round Trip Sensor
SMTP&POP3 Round Trip Sensor
SNMP APC Hardware Sensor
SNMP Cisco ADSL Sensor
SNMP Cisco ASA VPN Connections Sensor
SNMP Cisco ASA VPN Traffic Sensor
SNMP Cisco ASA VPN Users Sensor
SNMP Cisco CBQoS Sensor
SNMP Cisco System Health Sensor
SNMP Cisco UCS Blade Sensor
SNMP Cisco UCS Chassis Sensor
SNMP Cisco UCS Physical Disk Sensor
SNMP Cisco UCS System Health Sensor
SNMP CPU Load Sensor
6
1058
1065
1075
1090
1104
1113
1123
1132
1141
1153
1164
1176
1187
1201
1211
1222
1232
1242
1252
1261
1270
1279
1289
1297
1311
1318
1329
1338
1348
1358
1366
1374
1393
1405
1416
1425
1434
1443
1455
1467
1476
1484
1494
1505
1515
1524
1533
1542
1551
1560
1569
Contents
SNMP Custom Sensor

SNMP Custom Advanced Sensor
SNMP Custom String Sensor
SNMP Custom String Lookup Sensor
SNMP Custom Table Sensor
SNMP Dell EqualLogic Logical Disk Sensor
SNMP Dell EqualLogic Member Health Sensor
SNMP Dell EqualLogic Physical Disk Sensor
SNMP Dell Hardware Sensor
SNMP Dell PowerEdge Physical Disk Sensor
SNMP Dell PowerEdge System Health Sensor
SNMP Disk Free Sensor
SNMP Hardware Status Sensor
SNMP HP BladeSystem Blade Sensor
SNMP HP BladeSystem Enclosure System Health Sensor
SNMP HP LaserJet Hardware Sensor
SNMP HP ProLiant Logical Disk Sensor
SNMP HP ProLiant Memory Controller Sensor
SNMP HP ProLiant Network Interface Sensor
SNMP HP ProLiant Physical Disk Sensor
SNMP HP ProLiant System Health Sensor
SNMP IBM System X Logical Disk Sensor
SNMP IBM System X Physical Disk Sensor
SNMP IBM System X Physical Memory Sensor
SNMP IBM System X System Health Sensor
SNMP interSeptor Pro Environment Sensor
SNMP Juniper NS System Health Sensor
SNMP LenovoEMC Physical Disk Sensor
SNMP LenovoEMC System Health Sensor
SNMP Library Sensor
SNMP Linux Disk Free Sensor
SNMP Linux Load Average Sensor
SNMP Linux Meminfo Sensor
SNMP Linux Physical Disk Sensor
SNMP Memory Sensor
SNMP NetApp Disk Free Sensor
SNMP NetApp Enclosure Sensor
SNMP NetApp I/O Sensor
SNMP NetApp License Sensor
SNMP NetApp Logical Unit Sensor
SNMP NetApp Network Interface Sensor
SNMP NetApp System Health Sensor
SNMP Poseidon Environment Sensor
SNMP Printer Sensor
SNMP QNAP Logical Disk Sensor
SNMP QNAP Physical Disk Sensor
SNMP QNAP System Health Sensor
SNMP RMON Sensor
SNMP SonicWALL System Health Sensor
SNMP SonicWALL VPN Traffic Sensor
SNMP Synology Logical Disk Sensor
1577
1586
1596
1607
1617
1629
1638
1648
1657
1666
1675
1685
1694
1703
1712
1720
1729
1738
1747
1756
1765
1775
1784
1793
1802
1811
1819
1828
1837
1845
1857
1869
1877
1885
1894
1903
1912
1922
1931
1939
1948
1957
1966
1975
1983
1992
2001
2010
2020
2028
2037
7
Contents
SNMP Synology Physical Disk Sensor

SNMP Synology System Health Sensor
SNMP System Uptime Sensor
SNMP Traffic Sensor
SNMP Trap Receiver Sensor
SNMP Windows Service Sensor
SNTP Sensor
SSH Disk Free Sensor
SSH INodes Free Sensor
SSH Load Average Sensor
SSH Meminfo Sensor
SSH Remote Ping Sensor
SSH SAN Enclosure Sensor
SSH SAN Logical Disk Sensor
SSH SAN Physical Disk Sensor
SSH SAN System Health Sensor
SSH Script Sensor
SSH Script Advanced Sensor
SSL Certificate Sensor
SSL Security Check Sensor
Syslog Receiver Sensor
System Health Sensor
TFTP Sensor
Traceroute Hop Count Sensor
VMware Datastore (SOAP) Sensor
VMware Host Hardware (WBEM) Sensor
VMware Host Hardware Status (SOAP) Sensor
VMware Host Performance (SOAP) Sensor
VMware Virtual Machine (SOAP) Sensor
Windows CPU Load Sensor
Windows IIS 6.0 SMTP Received Sensor
Windows IIS 6.0 SMTP Sent Sensor
Windows IIS Application Sensor
Windows MSMQ Queue Length Sensor
Windows Network Card Sensor
Windows Pagefile Sensor
Windows Physical Disk I/O Sensor
Windows Print Queue Sensor
Windows Process Sensor
Windows System Uptime Sensor
Windows Updates Status (Powershell) Sensor
WMI Custom Sensor
WMI Custom String Sensor
WMI Event Log Sensor
WMI Exchange Server Sensor
WMI Exchange Transport Queue Sensor
WMI File Sensor
WMI Free Disk Space (Multi Disk) Sensor
WMI HDD Health Sensor
WMI Logical Disk I/O Sensor
WMI Memory Sensor
8
2045
2054
2063
2071
2082
2094
2102
2109
2122
2132
2142
2152
2162
2172
2183
2194
2205
2217
2228
2237
2245
2257
2263
2271
2280
2290
2298
2308
2318
2329
2339
2348
2357
2367
2378
2389
2398
2408
2419
2429
2438
2448
2458
2469
2480
2490
2500
2509
2521
2533
2543
Contents
WMI Microsoft SQL Server 2005 Sensor (Deprecated)

WMI Microsoft SQL Server 2008 Sensor
WMI Remote Ping Sensor
WMI Security Center Sensor
WMI Service Sensor
WMI Share Sensor
WMI SharePoint Process Sensor
WMI Terminal Services (Windows 2008+) Sensor
WMI Terminal Services (Windows XP/Vista/2003) Sensor
WMI UTC Time Sensor
WMI Vital System Data (V2) Sensor
WMI Volume Sensor
WSUS Statistics Sensor
9 Additional Sensor Types (Custom Sensors)
10 Sensor Channels Settings
11 Sensor Notifications Settings
2552
2565
2577
2589
2601
2610
2620
2630
2640
2649
2658
2667
2676
2686
2696
2707
2711
2719
2732
Part 7 Ajax Web InterfaceAdvanced Procedures

1
2
3
4
5
6
7
8
9
10
11
12
Toplists
Arrange Objects
Clone Object
Multi-Edit
Create Device Template
Show Dependencies
Geo Maps
Notifications
Setting Up Notifications Based on Sensor Limits: Example
Libraries
Libraries Step By Step
Management
Libraries and Node Settings
Context Menus
Reports
Reports Step By Step
View and Run Reports
Report Settings
Maps
Maps Step By Step
Map Designer
Maps Settings
Setup
Account SettingsMy Account
Account SettingsNotifications
Account SettingsNotification Contacts
Account SettingsSchedules
System AdministrationUser Interface
System AdministrationMonitoring
2734
2739
2740
2742
2747
2751
2753
2759
2762
2770
2773
2777
2779
2785
2786
2790
2794
2798
2810
2814
2816
2823
2828
2830
2836
2852
2856
2860
2871
9
Contents
System AdministrationNotification Delivery

System AdministrationCore & Probes
System AdministrationUser Accounts
System AdministrationUser Groups
System AdministrationAdministrative Tools
System AdministrationCluster
PRTG StatusSystem Status
PRTG StatusAuto-Update
PRTG StatusCluster Status
PRTG StatusLicensing Status and Settings
Optional Downloads and Tools
Desktop Notifications
SupportContact Support
2877
2883
2890
2896
2900
2905
2907
2918
2923
2925
2928
2930
2932
2938
Part 8 Enterprise Console

1 First Start
2 General Layout
3 Menu Tabs and Page Content
Devices
Libraries
Sensors
Alarms
Maps
Reports
Logs
Tickets
Setup
Search Results
4 PRTG Servers
5 Options
6 Windows Menu Structure
7 Context Menus
8 Shortcuts Overview
2941
2942
2945
2946
2953
2955
2957
2959
2961
2963
2965
2967
2969
2970
2973
2979
2986
2987
2990
Part 9 Other User Interfaces

1 Mobile Web GUI
2 PRTG Apps for Mobile Network Monitoring
2991
2995
3000
Part 10 Sensor Technologies

1
2
3
4
5
6
7
8
9
10
Monitoring via SNMP

Monitoring via WMI
Monitoring via SSH
Monitoring Bandwidth via Packet Sniffing
Monitoring Bandwidth via Flows
Bandwidth Monitoring Comparison
Monitoring Quality of Service and VoIP
Monitoring Email Round Trip
Monitoring Backups
3001
3005
3008
3010
3012
3015
3017
3022
3024
Contents
10 Monitoring Virtual Environments

11 Monitoring Databases
12 Monitoring Syslogs and SNMP Traps
3025
3033
3038
3046
Part 11 PRTG Administration Tool

1 PRTG Administration Tool on Core Server System
2 PRTG Administration Tool on Remote Probe Systems
3047
3073
3082
Part 12 Advanced Topics

1
2
3
4
5
6
7
8
9
Active Directory Integration

Application Programming Interface (API) Definition
Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
Define IP Ranges
Define Lookups
Regular Expressions
Calculating Percentiles
Add Remote Probe
Remote Probes and Multiple Probes
Remote Probe Quick Setup
Remote Probe Setup Using Installer
10 Failover Cluster Configuration
Failover Cluster Step by Step
11 Data Storage
12 Using Your Own SSL Certificate with PRTG's Web Server
3083
3086
3087
3092
3094
3095
3105
3107
3108
3109
3112
3117
3122
3128
3135
3137
3140
Part 13 Appendix
1
2
3
4
Index
Glossary
List of Abbreviations
Support and Troubleshooting
Legal Notices
3141
3145
3150
3151
11
Part 1
Welcome to PRTG Network Monitor
15.04.2016
13
Part 1: Welcome to PRTG Network Monitor |
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 economical 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
15.04.2016
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. It provides system administrators
with live readings and periodical usage trends to optimize the efficiency, layout, and setup of
leased lines, routers, firewalls, servers, and other network components.
The software is easy to set up and use and monitors a network using Simple Network
Management Protocol (SNMP), Windows Management Instrumentation (WMI), packet sniffer,
Cisco NetFlow (as well as IPFIX, sFlow, and jFlow), and many other industry standard protocols.
It runs on a Windows-based machine in your network for 24-hours every day. PRTG Network
Monitor constantly records the network usage parameters and the availability of network
systems. The recorded data is stored in an internal database for later analysis.
15.04.2016
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 PRTG's Ajax web interface. In this manual you often
get some more help regarding the different options that are available.
This document does not explain monitoring protocols and file formats in-depth. Also, the use
of the Application Programming Interface (API) built into PRTG is only briefly addressed.
Whenever possible, hyperlinks to more detailed resources are provided, such as articles in the
Paessler Knowledge Base.
To start using PRTG right away, please see the Quick St art Guide 32 section. For more
detailed instructions, browse the manual content and choose the section you want to read.
16
30.03.2015
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
1.2
Key Features
PRTG Network Monitor follows and analyses your network and requires no third party
software. It's quick to download and install. PRTG will be up and running in a just a few minutes
including a first auto-configuration. Smart Set up, the built in interactive guidance dialog, will
lead you through the whole process.
What is PRTG for?

Monitoring and alerting you to up-/downtimes or slow servers,
System health monitoring of your various hardware devices,
Network device monitoring, bandwidth accounting,
Applications monitoring,
Monitor virtual servers,
Service Level Agreement (SLA) monitoring,
System usage monitoring (for example, CPU loads, free memory, free disk space),
Database performance as well as main parameter monitoring,
Email server monitoring and reviewing various backup solutions,
Monitoring the network's physical environment,
Classifying network traffic by source/destination as well as content,
Discovering unusual, suspicious, or malicious activity with devices or user,
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,
Finding unexpected relationships between your network components to detect potential
security issues and assessing the real usage of your network and hardware,
Monitoring a fail-safe using a failover cluster setup.
What is included in PRTG?

The PRTG installer contains everything necessary to run your monitoring system immediately
without any for third party modules:
High performance - PRTG's own fast and efficient database system stores the raw monitoring
results, as well as logs, toplists, and tickets (outperforms SQL servers for monitoring data),
accessible through the Application Programming Interface (API). You can distribute high loads
on multiple probes.
Low system requirements: An average PC (not older than 2 years) is sufficient and even a
netbook can monitor over thousand sensors. Fur detailed system requirements see here
15.04.2016
22
17
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
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 the page.
A mail 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.
Multiple triggers, for example, status alerts, limit alerts, threshold alerts, multiple condition
alerts, escalation alerts.
gradual dependencies to avoid alarm floods, acknowledment of 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
or Portable Document Format (PDF). Several report templates are available by default.
Graphics engines 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 dashboardsprivate and publicincluding live performance
and status information. You can design these maps as you like with many different objects,
as well as you can integrate external custom objects.
Multiple languages such as English, German, Spanish, French, Portuguese, Dutch, Czech,
Japanese, 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 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 the Paesslers reliable monitoring technology, which is being
constantly improved since 1997. We already have more than 150,000 daily users. Our
outstanding support 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) make sure every user finds the best-possible
solution.
18
15.04.2016
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 fixesfast
and with high quality.
We provide three release channels for PRTG:
St able: best tested version of PRTG for live systems; updated about once or twice a month;
for usage on live systems
Preview: offering the latest features and fixes; updated 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"; updated very often; 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.
For an overview of all recent changes
our website.
19
in the current version, visit the version history
19
on
More
Paessler Website: PRTG Network Monitor Version History
https://www.paessler.com/prtg/history
Paessler Blog: Version 12 of PRTG introduces "Continuous Rollout"
https://www.paessler.com/blog/2012/04/25/
15.04.2016
19
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 four 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.
Note: If you want to use the Freeware Edition, please first install the Trial Edit ion 20 and get a
free trial key. After the trial period has ended, your Trial Edition will automatically revert into a
Freeware Edition.
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.
Temporary license key must be requested from Paessler's website. Usually you see the
license details including the key if you click the free download button on paessler.com
Trial period limited to 30 days (automatically reverts to Freeware Edition
20
afterwards)
With each license one single failover cluster setup 87 , consisting of two nodes, is included.
Cluster installations with two and three failover nodes will require one additional trial license
key; a cluster installation with four failover nodes will require two additional trial license
keys.
After the trial period has ended, a Trial Edition will revert into a Freeware Edition, allowing you
to monitor up to 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:
Can monitor a maximum number of sensors (please consider our recommendations
25 ).
20
03.05.2016
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
With each license one single failover cluster setup 87 , consisting of two nodes, is included.
Cluster installations with two and three failover nodes will require one additional license of
the same size. A cluster installation with four failover nodes will require two additional
licenses of the same size.
For more information about available commercial licenses, please see the More
below.
21
section
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
03.05.2016
21
Part 1: Welcome to PRTG Network Monitor | 5 System Requirements
1.5
System Requirements
To install and work with PRTG Network Monitor, you need to meet the following requirements:
A current PC or server with at least a dual core CPU and minimum 2048 MB RAM memory.
We recommend that you use the operating system Microsoft Windows Server 2012 R2 for
best performance.
Web browser to access the web interface. The following browsers are supported:
Google Chrome 49 or later (recommended)
Mozilla Firefox 45 or later
Microsoft Internet Explorer 11
Planning an Installation With Hundreds of Sensors or More?

The maximum number of sensors you can monitor with one installation of PRTG mainly
depends on the monitoring technology and the monitoring intervals you use. 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, please see section Det ailed Sy st em
Requirement s 23 .
More
Updat e From Previous Versions
51
Paessler Website: System Requirements for PRTG Network MonitorRecommended Setup for
Most PRTG Users
https://www.paessler.com/prtg/requirements
Knowledge Base: Planning Large Installations of PRTG Network Monitor
http://kb.paessler.com/en/topic/26383
Knowledge Base: How can I speed up PRTGespecially for large installations?
Knowledge Base: Checklist for Running PRTG on VMware
Knowledge Base: Which ports does PRTG use on my system?
Knowledge Base: Which .NET version does PRTG require?
22
15.04.2016

1 Detailed System Requirements
1.5.1
Detailed Sy stem Requirements
This section shows different aspects of system requirements for PRTG. Please consider these
requirements to avoid issues while network monitoring.
Support ed Operat ing Sy st ems
Hardware Requirement s
23
24
Net work Size: Recommendat ions
25
Running PRTG on Virt ual Machines
27
Running PRTG in a Failover Clust er
27
Web Browser Requirement s

Screen Resolut ion
27
28
Requirement s for Monit ored Devices
28
Requirement s for t he Ent erprise Console

Requirement s for Mobile Web GUI
Requirement s for Smart phones
More
29
28
(deprecat ed)
29
29
Supported Operating Systems

The 32-bit and 64-bit versions of the following operating systems are officially supported for
PRTG Core Service and Probe Service:
Microsoft Windows Server 2012 R2* (recommended)
Microsoft Windows Server 2012*
Microsoft Windows 10**
Microsoft Windows 8.1
Microsoft Windows 8
Microsoft Windows 7
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008 (not recommended)
Microsoft Windows Vista (not recommended)
* Windows Server 2012 in Core mode and the Minimal Server Interface are not officially
supported.
** The 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
11.03.2016
23

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 3109 .
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 3109 .
Microsoft .NET Framework: We recommend that you provide Microsoft .NET Framework
versions 4.0 or 4.5 (with latest updates) on all systems running a PRTG probe. Note: The .NET
framework is imperatively needed for monitoring VMware and XenServer virtual
environments.
More details: Some sensor types need the Microsoft .NET Framework to be installed on the
computer running the PRTG probe. This is either on the local system (on every node, if on a
cluster probe), or on the system running a remote probe 3109 . Depending on the sensor type,
the required versions are 4.0 or 4.5. See the More 29 section for details about the PRTG
usage of .NET.
Hardware Requirements
Hardware requirements for PRTG Core Service and Probe Service mainly depend on the
sensor types and intervals used. The following values are provided as reference for common
usage scenarios of PRTG (based on a default sensor interval of 60 seconds).
CPU
A current PC or server 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.
24
11.03.2016

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 3108 . For clusters we recommend that you stay below 2,500 sensors per
cluster.
Note: It is crucial for a properly working PRTG server to have a certain amount of hardware
resources available. Because of this PRTG sends according warning and emergency messages
to the primary email address of the PRTG Sy st em Administ rat or user if disk space or memory
on the PRTG core server system is running out. You will get 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 in this case and free your system
resources!
Network Size: Recommendations

Rule of thumb: Typical PRTG installations almost never run into performance issues when
they stay under 2,000 sensors, under 30 remote probes, and under 30 user accounts.
PRTG can scale much higher when the installation is planned well. Please read on if you plan
to go beyond these numbers and/or if you plan elevated use of resource intensive features
like reporting, xFlow sensors, or clustering.
If you plan an installation that monitors more than 5,000 sensors from one instance of PRTG
on a physical device or more than 2,500 sensors with PRTG running on a virtual machine we
ask you to contact our pre-sales team for consultation.
For your information: To monitor 5,000 sensors in a 1-minute interval, PRTG takes 7.2 million
measurements and evaluates, notifies, and stores themthis adds 700 MB of additional data
to the database every single day.
Note: PRTG users usually monitor each device in their network with about 5-10 sensors, so
for 50 servers you need about 250-500 sensors.
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 1252 and SNMP sensors 350 create much less load than complex
sensors like xFlow sensors 3012 , VMware sensors 354 , Sensor
Factory sensors 1374 , WMI sensors 352 , or Syslog 2245 /Trap receiver 2082
sensors, for example.
Scanning Interval
We recommend that you mainly use 1-minute scanning intervals

for up to 2,000 sensors and 5-minute intervals if you have more
sensors.
11.03.2016
272
25

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

3109 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 2810 , frequent generation of huge
sensor reports 2786 , heavy usage of packet sniffing 3010 , factory
sensors 1374 , and toplists 2734 , frequent automatically scheduled autodiscoveries 219 for large network segments, constant queries of
monitoring data via the API 3086 , among others.
Network Connection
Quality
The quality of your network also plays an important role. When

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
please see More 29 section below and refer to the Knowledge Base article "Increasing
Maximum Connections for VMware sensors".
26
11.03.2016

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 3109 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 3109 . 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 2,500 sensors per virtual
machine and consider running several PRTG core server instances instead.
Important note: We cannot offer technical support regarding performance and stability
problems for PRTG installations on virtual machines that run with more than 5,000 sensors. In
this case, please migrate PRTG to one or more, preferably physical, machines.
Note: When running PRTG on a virtual machine, do not use dynamic resource allocation, but
please make sure that full resources are available to the virtual machine at any time. In our
experience, dynamic resource allocation is not working efficiently for a monitoring software
and can therefore lead to massive performance issues.
Please see also the More
29
section for information on running PRTG on VMware.
Running PRTG in a Failover Cluster

We recommend a single failover setup 87 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.
Web Browser Requirements

The following browsers are officially supported by the PRTG web interface (in order of
performance and reliability):
Google Chrome 49 or later (recommended)
Mozilla Firefox 45 or later
11.03.2016
27

Microsoft Internet Explorer 11

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

SNMP monit oring
The monitored device(s) must be equipped with SNMP Version 1, 2c, or 3 (an SNMPcompatible 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,
please see section Monit oring via SNMP 3001 .
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
are officially supported. Please do not use Windows Vista or Windows 2008 R1 for WMI
monitoring (they both have WMI performance issues). For details, please see section
Monit oring via WMI 3005 .
23
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, please see
section Monit oring Bandwidt h via Flows 3012 .
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, please see section Monit oring Bandwidt h via Packet Sniffing 3010 .
Ot her sensor t y pes
Depending on the specific sensor type, you can find requirements (for example, modules,
components, device configurations) which may have to be fulfilled in the corresponding
manual section, as well as when adding the sensor to a device.
Requirements for the Enterprise Console

The optional PRTG Ent erprise Console 2938 (EC) runs under all supported Windows versions
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.
23
The EC has a built-in webkit browser engine and requires no specific browser installed on the
system. See also Ent erprise ConsoleRequirement s for Connect ions t o PRTG Web Server
(s) 2938 .
28
11.03.2016

Requirements for Mobile Web GUI (deprecated)

The feature-limited mobile web interface is optimized for low bandwidth and mobile access. It
has been designed for and tested with iOS, Android (including BlackBerry), and Windows Phone
devices, and also with deprecated Internet Explorer versions. For details, please see section
Mobile Web GUI 2991 .
Note: This user interface is deprecated. For mobile access to your PRTG server, please use the
PRTG mobile apps.
Requirements for Smartphones and Tablets

PRTG supports optional mobile apps for iOS and Android devices, as well as for Windows
Phone. For more information and system requirements, please see section PRTG Apps for
Mobile Net work Monit oring 2995 .
More
51
Paessler Website: System Requirements for PRTG Network MonitorRecommended Setup for
Most PRTG Users
https://www.paessler.com/prtg/requirements
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?
Knowledge Base: Checklist for Running PRTG on VMware
Knowledge Base: Which ports does PRTG use on my system?
Knowledge Base: Why can't I save my PRTG password in Google Chrome?
11.03.2016
29

30
11.03.2016
Part 2
Quick Start Guide
15.04.2016
31
Part 2: Quick Start Guide |
Quick Start Guide
Welcome to the 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, run through the installation wizard, and provide some information
about your network in the Smart Setup. 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.
Please see the following quick steps.
Quick Start GuideTopics

ONEDownload, Inst allat ion, and First Login
32
34
15.04.2016
Part 2: Quick Start Guide |
TWOSmart Set up
15.04.2016
37
33
Part 2: Quick Start Guide | 1 ONEDownload, Installation, and First Login
2.1
ONEDownload, Installation, and First Login
Simply download and install the version of PRTG Network Monitor which meets your needs.
For video tutorials with PRTG basics, please see the More 36 section below.
Download
On the Paessler website, you find two different installers for PRTG, a public download for the
Freeware and Trial editions, and a login link to download a commercial edition, which is
available for paying customers only.
Download the Trial or Freeware Edition, or log in to get a Commerc ial PRTG Edition
Downloading the Freeware or Trial Edition

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.
ht t ps://www.paessler.com/prt g/download
34
15.04.2016
Note: Every Freeware installation starts as a Trial version, permitting you an unlimited number
of sensors for 30 days. After the trial period expires, your installation automatically reverts to a
Freeware edition with 100 sensors. Please understand that Commercial Edition users get
prioritized support.
Downloading the Commercial Edition

Downloads and updates are free to customers with an active maintenance contract. Please log
in to the Paessler website to get the latest PRTG version. There you can also find your license
key, which must be entered during the installation:
ht t ps://shop.paessler.com/account s/login/
If you do not have an active maintenance contract and need one, please contact
sales@paessler.com.
Note: Once installed, usually PRTG's Soft ware Aut o-Updat e 2918 will automatically provide and
install new software versions. This helps you keep PRTG up to date.
Installation
Double click the setup file on the computer 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 123 , and starts the setup assistant. Please make
sure you load the web interface with one of the supported browsers:
Google Chrome 49 or later (recommended),
Mozilla Firefox 45 or later, or
Microsoft Internet Explorer 11.
Note: 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 the PRTG in another browser.
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.
15.04.2016
35
PRTG Login Sc reen
Leave the Login Name and Password fields empty.

Choose the Use AJAX Web GUI (All feat ures, opt imized for deskt op access) option.
Click the Default Login button to login.
Please make sure you use a supported web browser when logging in to PRTG. Please use
Google Chrome 49 or later (recommended), Mozilla Firefox 45 or later, or Microsoft Internet
Explorer 11. Only with a supported browser you can log in with the Use AJAX Web GUI (All
feat ures, opt imized for deskt op access) option. If you see this option grayed out, please
change your browser and open the URL again.
Please see the next step for more information about the initial configuration of PRTG using the
Smart Set up 37 !
More
Video tutorials for PRTG Network Monitor:
https://www.paessler.com/support/videos
36
15.04.2016
Part 2: Quick Start Guide | 2 TWOSmart Setup
2.2
TWOSmart Setup
For a new installation on a computer or server, PRTG automatically shows the Smart Set up.
This setup assistant, represented by some members 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.
First Start
When logging in for the first time, PRTG will show you the device tree 123 . It already contains
several devices 91 with sensors 92 that monitor your network, ordered in different suitable
groups 90 . PRTG automatically creates the device tree during the installation process by using
its Aut o-Discovery 219 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 at your first start of
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.
Note: 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
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!
15.04.2016
37
Note: 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 go are:

Provide Credent ials
38
Ent er Locat ion Informat ion
41
Change Your PRTG Login Password

Confirm Your Email Address
Swit ch t o SSL
45
42
44
(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.
38
15.04.2016
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 to set up your network monitoring
so there is no need for you to manually add every single devices one by one.
15.04.2016
39
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 3005 .
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 3008 .
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 3025 .
To monitor your hardware (router, switches, etc.), Simple Network Management Protocol
(SNMP) is the most common protocol used. Usually, all SNMP-enabled devices use the same
settings by default: SNMP v2c, community string public, SNMP port 161). For a general
introduction to the technology behind SNMP, see the manual section Monit oring via SNMP
3001 .
40
15.04.2016
PRTG will store these credentials in the Root 260 group of your device tree. All dependent
devices automatically inherit and use them for monitoring. You can discontinue Inherit ance of
Set t ings 94 at any level if you enter other credentials instead.
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, please see the manual section Root Group Set t ings
261 .
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 2753 . Enter your location and confirm with OK, done!. Click OK,
show me! to get back to the device tree.
15.04.2016
41
Enter Your Loc ation
For details about the available options, please see the manual section Root Group Set t ings
260 .
Step 3: Change Your PRTG Login Password

Back on the device tree, the setup assistant asks you to change your password. Click OK,
show me!, 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.
42
15.04.2016
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.
15.04.2016
43
...to Change the Default Password
For details about the available options, please see the manual section Account Set t ingsMy
Account 2830 .
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.
Note: A working email address is absolutely mandatory for PRTG to reach you via email
notifications, alarms, and other important messages.
If the address is correct, click OK, done! and follow the assistant back to the device tree.
Verify Your Email Address
44
15.04.2016
For details about the available options, see the manual section Account Set t ingsMy
Account 2830 .
Step 5: Switch to SSL

If you access the PRTG web interface from another computer than from the computer on which
you installed PRTG, the assistant will appear and ask you to switch to a secure connection with
Secure Sockets Layer (SSL) 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
proceed to the login screen.
113
. Confirm it to
Switc h to a Sec ure SSL Connec tion
For more details, see the manual sections Sy st em Administ rat ionUser Int erface
SSL Cert ificat e Warning 113 .
15.04.2016
2862
and
45
You Are Done!

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! In the meantime, you can follow PRTG on Facebook, Twitter, and Google+.
Just click the Follow & Share button on the page footer and connect to your new favorite
monitoring tool!
To become familiar with the PRTG web interface, we recommend that you read on in the manual
section General Lay out 123 of the web interface.
46
15.04.2016
Part 3
Installing the Software
08.10.2015
47
Part 3: Installing the Software |
Installing the Software
This section describes how to download and install your PRTG product.
PRTG Setup
Please see the following sections for more information.
Installing the SoftwareTopics

Download PRTG
49

Inst all a PRTG Core Server
Inst all a PRTG Clust er
Ent er a License Key
56
61
62
Act ivat e t he Product
65
Inst all a PRTG Remot e Probe
67
Inst all t he Ent erprise Console

Uninst all PRTG Product s
48
51
72
78
08.10.2015
Part 3: Installing the Software | 1 Download PRTG
3.1
Download PRTG
On the Paessler website, you find two different installers for PRTG, a public download for the
Freeware and Trial editions, and a login link to download a commercial edition, which is
available for paying customers only.
Download the Trial or Freeware Edition, or log in to get a Commerc ial PRTG Edition
Downloading the Freeware or Trial Edition

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.
ht t ps://www.paessler.com/prt g/download
Note: Every Freeware installation starts as a Trial version, permitting you an unlimited number
of sensors for 30 days. After the trial period expires, your installation automatically reverts to a
Freeware edition with 100 sensors. Please understand that Commercial Edition users get
prioritized support.
24.03.2015
49
Part 3: Installing the Software | 1 Download PRTG
Downloading the Commercial Edition

Downloads and updates are free to customers with an active maintenance contract. Please log
in to the Paessler website to get the latest PRTG version. There you can also find your license
key, which must be entered during the installation:
ht t ps://shop.paessler.com/account s/login/
If you do not have an active maintenance contract and need one, please contact
sales@paessler.com.
Note: Once installed, usually PRTG's Soft ware Aut o-Updat e 2918 will automatically provide and
install new software versions. This helps you keep PRTG up to date.
50
24.03.2015
Part 3: Installing the Software | 2 Update From Previous Versions
3.2
Update From Previous Versions
If you already have installed a previous software version, there are several things you have to
consider before you update to the current PRTG version. Please see section Det ailed Sy st em
Requirement s 23 to see all requirements for the current PRTG version.
Note: We recommend 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. Please see More 54 section below.
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 56 the latest
version on top of the previous version. Your configuration will be kept. PRTG updates remote
probes 3109 automatically as well. If you have configured PRTG as a cluster 87 , 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 2918 of PRTG to install the latest version. Please
always have a proper backup of your monitoring data.
Note: As of PRTG 16.2.23, several sensor types are deprecated and will be completely removed
with PRTG version 16.x.25. Please see this article for details: https://kb.paessler.com/en/
topic/68227
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 2918 from previous versions (lower than 16.1.21.1691/1692), PRTG will
automatically install this intermediate version first. You have to perform an additional autoupdate to install the latest version. PRTG will notify you with a ticket 171 about this approach.
Your configuration will be kept.
Note: We recommend that you use the auto-update 2918 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 2932 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 do not support Windows X P and Windows Server
2003 (including SP1 and SP2) officially anymore.
As of PRTG 15, Int ernet Explorer 10 is no longer officially support ed for access to the
PRTG web interface.
15.04.2016
51
Web Interface Customizations as of PRTG Network Monitor 13.2.3

As of PRTG version 13.2.3, the website folder of the PRTG program directory is not used any
more. This means that if you update from an older PRTG version than 13.2.3 to the current
version, all existing customizations of the web interface will be disabled and 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, please see the
section More 54 .
Update from PRTG Network Monitor 9 and 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.
Note: 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, please see section Updat e
from PRTG Net work Monit or 13.1.1 t hrough 16.1.21 51 above.
We recommend that you use the Aut o-Updat e 2918 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 2932 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. In order
to continue monitoring, please add the sensors anew (for example, using the autodiscovery).
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 354 auto-discovery and monitoring, Citrix XenServer 502 autodiscovery and monitoring, SIP Options Ping Sensor 1425 , 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).
52
15.04.2016
Windows 2000 Not Support ed: Since PRTG 7 we do not officially support Windows 2000
systems any more. This means, PRTG cannot be installed on systems running Windows 2000,
and you cannot officially monitor Windows 2000 systems (for example, via WMI). However, if
you could successfully monitor your Windows 2000 systems with PRTG 9, this might actually
not be possible any more with the current PRTG version. Especially the WMI Service Sensor
2620 will show an error message when monitoring Windows 2000 systems under the current
PRTG version. For a work around, please see the More 54 section below.
Note: We recommend that you to have a look at the Det ailed Sy st em Requirement s 23
before updating to the current version! Officially supported operating systems, browsers, and
other requirements may have changed since version 9.
Update from PRTG Network Monitor 7 or 8

Note: If at all possible for you, we strongly recommend that you perform a clean install of the
latest PRTG version instead of updating from an existing PRTG 7 or 8!
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
and then to the current PRTG version.
52
12.4.7.3507 and 16.1.21.1691/1692
Please contact our technical support 3150 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 any more. Existing sensors of this type
will automatically be switched to Packet Sniffer (Header) sensors after the update. As a
benefit, you can now also sniff IPv6 traffic.
Internet Explorer 8 is no longer supported for access to the PRTG Ajax web interface or to
the mobile web GUI.
You may experience a slow Enterprise Console 2938 (former 'Windows GUI') due to different
reasons. For detailed information, please see the Knowledge Base article linked in the More
54 section below.
When installing a failover node on top of an existing stand-alone PRTG 7, 8, 9, 12, or 13+
installation, the configuration cannot be kept and is written to a backup folder. Then, the
new cluster configuration is received from the master node of the cluster. As all nodes work
with the same configuration, a failover node's old configuration and monitoring data can no
longer be used. If you want to keep a configuration of PRTG 7, please install the master node
on top of the old installation and use other servers for the failover node installations.
Since PRTG 9 the SNMP sensors use the IPv4 Out going IP set for the probe service (this
setting was formerly ignored by those sensors, using the aut o setting instead). If you
experience failing sensors, please check the setting in the probe settings 295 . For detailed
information please see the More 54 section below.
15.04.2016
53
If you have (manually) configured the PRTG probe or PRTG core service to run under a
different Windows user account (for example, for successful internet access through an ISA
server firewall), please apply the respective Windows user account for the
"PRTGProbeService" and/or "PRTGCoreService" anew after installing the current PRTG version.
For detailed information please see the More 54 section below.
System Requirements for the PRTG core server and probes: Please have a look at our latest
Det ailed Sy st em Requirement s 23 .
If you use the default data path in your PRTG setup, it will be changed automatically. Up to
version 8 all data was stored in a sub folder reflecting a PRTG version number (v7 or v8). As
of version 9 this sub folder is omitted, and data is stored directly at %ALLUSERSPROFILE%
\Application data\Paessler\PRTG Network Monitor. During setup, all data will be moved to
the new directory. If you use a custom data path it will not be changed.
Up to version 8 all data in the registry was stored in a sub key reflecting a PRTG version
number (v7 or v8). As of version 9 this sub key is omitted, and registry data is stored directly
under the key HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor (on 32-bit
systems) respectively HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG
Network Monitor (on 64-bit systems). During setup, all existing registry values will be moved
to the new key.
Note: We strongly recommend that you to have a look at the Det ailed Sy st em Requirement s
23 before updating to the current version! Officially supported operating systems, browsers,
and other requirements may have changed since version 8.
Updat ing from PRTG 7 t o Current PRTG Version
Regarding custom sensors, the interpretation of returned values is handled more strict as of
PRTG 8. If you 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 3086 .
Update from Older PRTG Products

For all other predecessor products, a direct data import into the current version is not
possible.
If you have been using IPCheck 5 or PRTG Traffic Grapher 6, please perform a clean installation
of PRTG Network Monitor and set up your configuration anew. Using PRTG's Aut o-Discovery
219 is the easiest way to quickly configure a monitoring of your entire network. Please see
Quick St art Guide 32 section for more information.
More
Knowledge Base: How do I backup all data and configuration of my PRTG installation?
Knowledge Base: What about my web interface customizations as of PRTG 13.2.3?
Knowledge Base: How and where does PRTG store its data?
54
15.04.2016
Knowledge Base: Updating from Version 7, 8, or 9? Read this important message!
Knowledge Base: Can I update from PRTG Traffic Grapher or IP Check 5 to the current PRTG
version?
Knowledge Base: How do I Import Data from PRTG Traffic Grapher 6 or IPCheck Server Monitor
5 in PRTG Network Monitor?
Knowledge Base: What does error code PE251 mean?
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?
https://kb.paessler.com/en/topic/68227
15.04.2016
55
Part 3: Installing the Software | 3 Install a PRTG Core Server
3.3
Install a PRTG Core Server
Installing PRTG is easy. It is similar to other Windows-based applications. To install the

application please run the installation setup program from the ZIP file that you have
downloaded.
Windows User Ac c ount Control Confirmation Request
Confirm the question of the Windows User Account Control with Yes to allow the program to
install. The usual software installation wizard will guide you through the installation process.
Setup Language Selec tion
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.
56
08.10.2015
Setup Wizard Start Sc reen
Click Next to start the walk through the wizard.
Setup Wizard Lic ense Agreement
Accept the license agreement and click Next .
08.10.2015
57
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.
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 Paessler. We recommend that
you use copy&paste to avoid typos. Click Next to confirm.
58
08.10.2015
Setup Wizard Destination Loc ation
Choose the folder you wish to install the software in. We recommend that you use the default
value. As soon as you click Next , PRTG will copy the necessary files to your disk.
Setup Wizard Installing
After installation, PRTG opens the Ajax Web Int erface 108 in your system's default browser.
Make sure there is Google Chrome 49 or later (recommended), Mozilla Firefox 45 or later, or
Microsoft Internet Explorer 11 available on the system, and set as default browser (see
Sy st em Requirement s 22 ).
08.10.2015
59
Enter License Information

Only if you entered incorrect license information before, PRTG will ask you to enter a correct
license name and key.
Enter Lic ense Key Dialog
Please enter both Name and Key exactly as stated in the email received from Paessler. We
recommend that you use copy&paste to avoid typing mistakes. For details, please see Ent er a
License Key 62 .
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?
60
08.10.2015
Part 3: Installing the Software | 4 Install a PRTG Cluster
3.4
Install a PRTG Cluster
PRTG offers single failover clustering in all licenseseven using the freeware edition. A single
failover cluster consists of two servers ("Current Master" Node and "Failover Node"), each of
them running one installation of PRTG. They are connected to each other and exchange
configuration and monitoring data. You can run a cluster with up to 5 nodes.
Illustration of a Single Failov er Cluster

Clic k here to enlarge: http://media-s3.paessler.c om.s3.amazonaws.c om/prtg-sc reenshots/c lustering-1_en.png
For detailed information, please see Failover Clust er Configurat ion
3122
More
Knowledge Base: What's the Clustering Feature in PRTG?
09.07.2015
61
Part 3: Installing the Software | 5 Enter a License Key
3.5
Enter a License Key
A license key for PRTG Network Monitor consists of the license name and a license key. The
key is a string consisting of approximately 60 characters.
Your Personal License Information

You have received the license name and key from Paessler via email or in a license document
on Paessler shop. This is either the information for a Trial or a Commercial Edition. When you
click the according button to download the trial or freeware version of PRTG on the Paessler
webpage, it will show a page with license details (license name and license key). Please copy
this information and insert it when PRTG asks you to about you license information.
EXAMPLE OF LICENSE INFOR MATION

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

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

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

You have two options to enter a license key. If you can log in to the PRTG web interface 108 ,
choose Set up | Ent er License Key from the main menu bar 200 and provide your license
information 2926 . Alternatively, start the PRTG Administ rat ion Tool 3059 from the Windows Start
Menu. In this program, select the License tab. For a video tutorial on the various settings you
can make in the Administration Tool, including the PRTG License settings, please see the More
64 section below.
To use a PRTG license with this installation of PRTG, please enter the license information you
have received from Paessler via email. To avoid typing errors, please copy and paste both the
License Name and the License Key from the email. Both must be transferred exactly as shown
in the email.
PRTG Administration Tool: Lic ense
21.01.2016
63
To make sure your key has been entered correctly please click on the Check Key button. A
popup box will either show success or denial of your license information. License information
is also checked if you change tabs.
In the Licensed Edit ion field you will see an accepted license key.
Click the Ok button to save and confirm to restart the core server service by clicking on the
Yes button.
PRTG Administrator: Restart Core Serv er Serv ic e
More
Paessler Website: PRTG Administration Tool (video tutorial)
https://www.paessler.com/support/videos/prtg-basics/administration-tool
64
21.01.2016
Part 3: Installing the Software | 6 Activate the Product
3.6
Activate the Product
PRTG tries to activate your license automatically via the internet on first start up. Only if PRTG
cannot connect to the internet directly, the web interface will display a Soft ware Act ivat ion
Required notice.
You have to run through the product activation process once to use PRTG continuously (only
Freeware and Trial Edition are always activated automatically and do not require a special
procedure). The activation has to be done within ten days after installation and only takes a
few minutes. If you do not activate PRTG for ten days, it temporarily reverts to the Freeware
Edition (with a maximum of 100 sensors) until you activate. Login to the PRTG web interface 110
to activate.
Activate via Internet

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

In the PRTG Web Interface, choose Set up | PRTG St at us from the main menu and open the
Act ivat ion tab.
If there is no internet connection available, you can activate PRTG via email. To do so, first click
St art Act ivat ion Now. You will then see Last message about act ivat ion: Act ivat ion failed
in the License Activation Status.
Once the activation via internet fails, the activation via email is available.
Open the St art Act ivat ion per Email tab. You see an Act ivat ion Request Code.
Copy it and send it to the email address shown.
Within two business days you will receive an email reply from Paessler, containing an
activation code.
When you receive this email, open the Finalize Act ivat ion per Email tab and copy the
activation code into the according field.
Note: Ensure you only copy the code itself and nothing else from the email. Also, please
omit the "Activation Code Start/End" markers.
Click on Confirm Act ivat ion.
A few seconds later you should see Act ivat ion OK in the License Activation Status.
11.03.2016
65
Part 3: Installing the Software | 6 Activate the Product
More
Knowledge Base: Which servers does PRTG connect to for Software Auto-Update and for
Activation?
66
11.03.2016
Part 3: Installing the Software | 7 Install a PRTG Remote Probe
3.7
Install a PRTG Remote Probe
The local probe is already included in a PRTG core server installation 56 . You can install
additional remote probes on other computers in order to take load from the system running
the core installation or to extend monitoring to distributed networks.
Note: You cannot install a remote probe on a system running already a PRTG core installation.
Download the Remote Probe Installer from the Web Interface

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

Please execute the setup program that you have just downloaded.
Confirm the question of the Windows User Account Control with Yes to allow installation. The
usual software installation wizard will guide you through the installation process.
26.01.2016
67
Remote Probe Setup Wizard Welc ome Sc reen
Click Next to walk through the wizard.
Setup Wizard Lic ense Agreement
After accepting the license agreement, you can choose the folder for the remote probe
software. We recommend that you use the default value.
68
26.01.2016
Setup Wizard Destination Loc ation
As soon as you click Next , the necessary files will be copied to your disk.
The PRTG Administ rat ion Tool 3046 starts. Please enter the correct settings to connect your
remote probe to your PRTG core installation. See the Remot e Probe Set up 3117 section for
more information. Click Ok to continue.
26.01.2016
69
Probe Settings in PRTG Administration Tool
When asked if you want to start the probe service, confirm with Yes. The installation is
complete.
After that, click Finish in the installation wizard.
70
26.01.2016
Remote Probe Setup Wizard Finish
Your remote probe is now installed on this computer as a Windows service.
More
After clicking the Finish button, the PRTG Administ rat ion Tool 3046 is shown, allowing you to
configure connections. Please see Remot e Probe Set up 3117 for more information on how to
connect the remote probe to your PRTG core server installation.
Note: You can also install a Remote Probe directly from PRTG's web interface. For details, refer
to Remot e Probe Quick Inst all 3112 .
26.01.2016
71
Part 3: Installing the Software | 8 Install the Enterprise Console
3.8
Install the Enterprise Console
The Enterprise Console is already included in a PRTG core server installation

additional Enterprise Consoles on other computers.
56
. You can install
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
web interface of PRTG.
108
2. On the login screen 110 of the web interface, enter login name and password and select
Download Client Soft ware (for Windows, iOS, Android).
3. You will see the downloads page 2928 in the Mobile Web GUI 2991 version of PRTG, so you can
also download the EC if you can only use an unsupported browser that cannot access the
fully featured web interface.
4. Click PRTG Ent erprise Console (Windows GUI) 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.
Confirm the question of the Windows User Account Control with Yes to allow the program to
install. The common software installation assistant will guide you through the installation
process.
72
31.08.2015
Enterprise Console Setup: Welc ome Sc reen
Click Next to walk through the wizard.
31.08.2015
73
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.
74
31.08.2015
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.
31.08.2015
75
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 2938 in the appearing dialog.
76
31.08.2015
Enterprise Console Setup: Finish
More
Please see the section Ent erprise Console
Graphical User Interface (GUI).
31.08.2015
2938
for more information on how to use this
77
Part 3: Installing the Software | 9 Uninstall PRTG Products
3.9
Uninstall PRTG Products
The uninstall process has six stepsregardless of if you are uninstalling an entire PRTG
Network Monitor installation, a single Enterprise Console installation, or a PRTG Remote Probe
installation. Use the Windows uninstall routines to remove the PRTG software from your
system.
Step 1
From the Windows Start Menu, select the Uninst all PRTG Net work Monit or icon, the
Uninst all PRTG Ent erprise Console icon, or the Uninst all PRTG Remot e Probe icon, or open
your Windows Control Panel and choose the respective entry in the Programs section.
Depending on the installed products, not all uninstall programs are available.
Start Menu Ic ons
Step 2
If asked, confirm the question of the Windows User Account Control with Yes to allow the
program to uninstall. The usual software uninstall wizard will guide you through the uninstall
process.
Windows User Ac c ount Control Request
Step 3
Confirm the removal of the software by clicking the Yes button.
78
19.10.2015
Uninstall PRTG Network Monitor Step 1
Step 4
Wait while the software is being removed.
Step 5
Confirm a system restart by clicking the Yes button.
19.10.2015
79
Step 6
After system restart, the software is removed. However, there are still custom data in the PRTG
program folder left. If you have uninstalled an entire PRTG Network Monitor installation or a
remote probe installation, your monitoring data is still stored on the system. To completely
remove all PRTG data, please delete the PRTG Net work Monit or program folder as well as the
Paessler\PRTG Net work Monit or folder in your data path. For more information on where the
data is stored see the Dat a St orage 3135 section.
More
Knowledge Base: Can we remotely and silently uninstall a Remote Probe?
80
19.10.2015
Part 4
Understanding Basic Concepts
15.04.2016
81
Part 4: Understanding Basic Concepts |
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-to-use as
possible. Setting it up for the first start and getting first monitoring results happens almost
automatically 37 .
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 ConceptsTopics

Archit ect ure and User Int erfaces
Clust ering
87
Object Hierarchy
89
Inherit ance of Set t ings

Tags
Scheduling
Not ify ing
98
99
100
Dat a Report ing
104
User Access Right s
82
94
96
Dependencies
IPv6
83
101
105
15.04.2016
Part 4: Understanding Basic Concepts | 1 Architecture and User Interfaces
4.1
Architecture and User Interfaces
PRTG Network Monitor consists of different parts which you can divide into three main
categories: System parts, control interfaces, and a basic administration interface.
TYPE
PAR T OF PR TG
System Parts
Core Server 84
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 Windows service which
runs permanently.
Probe(s) 84
The part of PRTG which performs the actual monitoring. There are
local probes, remote probes, and cluster probes available. All
monitoring data is forwarded to the central core server. Probes are
configured as Windows services which run permanently.
Note: 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
Ajax Web Int erface 108

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.
Ent erprise Console 2938
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 Net work Monit oring 2995
Monitor your network on the go with PRTG and apps for iOS,
Android (including BlackBerry devices), and Windows Phone.
Mobile Web GUI 2991 (deprecat ed)
A read-only interface for mobile access to your PRTG installation.
View latest states, tables, and graphs. Using jQuery Mobile, this
interface is compatible with almost all mobile devices available on
the market, as well as with older and unsupported browser
versions.
Note: This user interface is deprecated. Please use a supported
browser version or the PRTG apps for mobile access.
09.05.2016
83
TYPE
PAR T OF PR TG
System Administration
Program
PRTG Administ rat ion Tool on Core Server Sy st em 3047

Used to configure basic core server settings, such as administrator
login, web server IPs and port, probe connection settings, cluster
mode, system language, and more.
PRTG Administ rat ion Tool on Remot e Probe Sy st em 3073
Used to configure basic probe settings such as name of the probe,
IP and server connection settings, and more.
Core Server
The core server is the heart of your PRTG system and performs the following processes:
Configuration management for object monitoring
Management and configuration of the connected probes
Cluster management
Database for monitoring results
Notification management including a mail server for email delivery
Report generator and scheduler
User account management
Data purging (culling data that is older than 365 days, for example)
Web server and API server
In a cluster
87 ,
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 with a
browser and also answers PRTG Application Programming Interface (API) calls (for example, for
user scripts or the Enterprise Console).
Note: Core server and probe(s) are configured as Windows services which are permanently run
by the Windows system without the requirement for a logged-in user.
Probe(s)
On a probe, PRTG performs the actual monitoring with the sensors created on a device (for
example, computer, router, server, firewall). The probe receives its configuration from the core
server, runs the monitoring processes, and delivers monitoring results back to the core
server. On every system running a PRTG core server, there is always a local probe running with
it on the same machine.
84
09.05.2016
PRTG Core Serv er and Loc al Probe Monitoring a Loc al Area Network
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/probes.png
The actual monitoring is performed by PRTG probe processes which run on one or more
computers. During installation, the system automatically creates the Local Probe. In a singleprobe installationwhich is the default setupthe local probe performs all monitoring.
The PRTG 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).
Note: Core server and probe(s) are configured as Windows services which are permanently run
by the Windows system without the requirement for a logged-in user.
You can create additional Remot e Probes to achieve monitoring of multiple locations, or for
several other scenarios. They use SSL-secured connections to the core and allow to securely
monitor services and systems inside remote networks which are not openly accessible or
secured by firewalls. For more information, please see Remot e Probes and Mult iple Probes
3108 . For a video on this please see the More 235 section below.
In a cluster setup 87 , 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.
PRTG Mini Probes allow you to create small probes on any device (not just on Windows
systems). You can implement mini probes to gather monitoring data exactly like you need it
and create them on any platform. For more information, see the Mini Probe API definition in
the PRTG web interface.
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 555 and Probe Healt h 1311 , Sy st em Healt h 2257 , Clust er Healt h 542 , disk free 2509 , and
bandwidth 2378 sensors for all installed network cards, as well as a Common SaaS sensor 547
that checks the availability of widely used SaaS providers.
09.05.2016
85
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 137 of a
particular sensor for details.
More
Video Tutorial: There is a video available on the Paessler video tutorials page.
https://www.paessler.com/support/video_tutorials
86
09.05.2016
Part 4: Understanding Basic Concepts | 2 Clustering
4.2
Clustering
A PRTG Cluster consists of two or more installations of PRTG 56 that work together to form a
high availability monitoring system. The objective is to reach true 100% uptime for the
monitoring tool. Using clustering 3122 , the uptime will no longer be degraded by failing
connections because of an internet outage at a PRTG server's location, failing hardware, or
because of downtime due to a software update for the operating system or PRTG itself.
How a PRTG Cluster Works

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

For detailed information, please see Failover Clust er Configurat ion
3122
More
Knowledge Base: What's the Clustering Feature in PRTG?
88
15.04.2016
Part 4: Understanding Basic Concepts | 3 Object Hierarchy
4.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 same locations. The hierarchical order described is also used to
define common settings for larger groups of objects, for example, settings of the Root group
apply by default to all other objects underneath (see section Inherit ance of Set t ings 94 ).
Objec t Hierarc hy in PRTG

Clic k here to enlarge: http://media-s3.paessler.c om.s3.amazonaws.c om/prtg-sc reenshots/objec thierarc hy _en.png
The figure shows the object hierarchy in PRTG:

Root group contains all objects in your setup; all probes are directly under the root node.
A Probe contains one or more groups.
A Group contains one or more devices.
A Device represents one component in your network which is reachable via an IP address.
On a device are several sensors.
11.11.2015
89
A Sensor monitors one single aspect of a device and has at least one channel.
A Channel receives the monitoring results and is part of a sensor.
Root Group
The Root group is the topmost instance in PRTG. It contains all other objects in your setup.
Using the inheritance 94 mechanism, we recommend adjusting the default settings for the
Root group 260 . This makes configuration easier later on, because all other objects inherit
these standard settings by default and, thus, you will not have to set up the same
configuration for each object anew.
Probe
Each group (except the Root group) is part of a Probe. This is the platform on which the
monitoring takes place. All objects configured below a probe will be monitored via that probe.
Every PRTG core installation automatically installs a Local Probe service. You can add additional
probes and remote probes to your configuration to include remote devices from outside your
network into the monitoring (see section Mult iple Probes and Remot e Probes 3108 ). In a
cluster, there is an additional Clust er Probe running on all nodes. Devices on the cluster
probe are monitored by all nodes of the cluster, so data from a different perspective is
available and monitoring for these devices will always continue, even if one of the nodes fails.
Group
On each probe, there are one or more Groups, which serve merely structural purposes. Use
groups to arrange similar objects in order to inherit same settings to them. To a group, you
add the devices. You can arrange your devices in different nested groups to reflect the
structure of your network.
Find below a sample configuration: A device tree with local probe, several groups, devices and
their sensors.
90
11.11.2015
PRTG Dev ic e Tree View
Device
To each probe or group, you can add Devices that you want to monitor. Each device in your
PRTG configuration represents a real hardware or virtual device in your network. These can be,
for example:
Web or file server
Client computer (Windows, Linux, or Mac OS)
Router or network switch
Almost every device in your network that has its own IP address
Note: Sometimes you may want to add the same device in PRTG several times to get a better
overview when using many sensors for a very detailed monitoring, or to use different device
settings for different groups of sensors. In PRTG you can simply add multiple devices with the
same IP address or DNS name. The sensors on all of these PRTG devices will then query the
same real hardware device in your network.
PRTG additionally adds a so called Probe Device to the local probe. This is an internal system
device. It has access to the computer on which the probe is running on and monitors its
health parameters with several sensors running on it.
11.11.2015
91
To get a better and more detailed picture about your devices, PRTG automatically analyzes the
devices which you add and recommends appropriate sensor types 348 on the device overview
tab 137 . In the Recommended Sensors table, click on the Add Sensors button in the
corresponding table row to create recommended sensor types with one click.
Note: You can turn off the sensor recommendation in Sy st em Administ rat ionMonit oring
2874 .
Sensor
On each device you can create a number of Sensors. Every sensor monitors one single aspect
of a device. This can be, for example:
One network service like SMTP, FTP, HTTP, etc.
One network switch port's traffic
CPU load of a device
Memory load of a device
Traffic on one network card
One NetFlow device
System health of a device
Other content (for example, of databases, mails, HTTP, XML, files, etc.)
etc.
Channel
Every sensor has a number of Channels through which it receives the different data streams.
The available channels depend on the type of sensor. One sensor channel can contain, for
example:
Downt ime and upt ime of a device
Traffic in of a bandwidth device (for example, a router)
Traffic out of a bandwidth device (for example, a router)
Traffic sum of a bandwidth device (for example, a router)
WWW t raffic of a NetFlow device
Mail t raffic of a NetFlow device
Ot her t raffic of a NetFlow device
CPU load of a device
Loading t ime of a web page
Download bandwidt h of a web page
Time t o first by t e of a web page
92
11.11.2015
Response t ime of a Ping request to a device

Response t ime of a Remote Desktop service
etc.
11.11.2015
93
Part 4: Understanding Basic Concepts | 4 Inheritance of Settings
4.4
Inheritance of Settings
The hierarchical tree 89 is not only used to group sensors for organizational reasons, there is
also an important aspect involved that we call inheritance. To ensure administration is quick
and easyespecially for large monitoring setupscertain settings are inherited from the
overlying level. For example, you can change the monitoring interval for all sensors by editing
the interval setting of the topmost Root group (unless no other setting is defined below).
Settings are Inherited to Child Objects

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

For all settings (except passwords), PRTG already includes a set of default values so you can
get started with the software immediately. For example, the following settings will be inherited
by all sensors from the Root group:
Default monitoring interval of one minute
SNMP version 1 with community string set to public (default values for most devices)
Dependency type Use parent
etc.
You may need to change some of the default entries as you become used to the interface.
However, these settings will initially suffice for most situations.
Before sensor setup, please review the Root group's settings and set the default values to
suit your setup, including necessary credentials for all kinds of systems in your network you
want to monitor (Windows, Linux, virtual servers, etc.).
See section Root Group Set t ings
260
for more details.
Inheritance of Notification Triggers

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

The tags in the settings of an object are automatically inherited 94 by all other objects
underneath in the Object Hierarchy 89 . You can view inherited tags in section Parent Tags in
the settings of a sensor 92 , device 91 , or group 90 . So, for example, a device with the tag
myExampleTag automatically passes on this tag to all sensors which you create on it. These
sensors appear in lists then whenever you search for myExampleTag. This is useful, for
example, when you add sensors by tag in reports 2786 settings.
This way, to configure your setup for fetching all sensors on a device by tag, you do not have
to tag every single sensor, but it is enough to tag the device. Inheritance for tags cannot be
disabled.
Filtering with Tags

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

Tags with must not exist for an object to be shown
At least one tag of the tags without + or must exist for an object
The filter shows an object only if all three conditions are true. The order of the tags in a tag
field does not matter.
For example, if you enter windows into a tag field, all sensors/devices that do not have
"windows" as tag are shown. With +windows or windows you filter for objects which are
tagged with "windows".
You can use more than one logical operator in a tag field: For example, if you enter +netflow
bandwidth_important into a tag field, the corresponding list, library, or report includes all
sensors that are tagged with "netflow" but not with the tag "bandwidth_important". If you
enter netflow bandwidth_important, a sensor has to be tagged with "netflow" or
"bandwidth_sensor" or both to be affected.
24.03.2015
97
Part 4: Understanding Basic Concepts | 6 Dependencies
4.6
Dependencies
Using dependencies, you can pause sensor monitoring based on the status 135 of another
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.
This means, for example, you can stop monitoring remote network services when the
corresponding firewall is down due to connection problems.
When using the auto-discovery 219 function, the Ping Sensor 1252 on a device is by default set as
the master object for this device. This means that monitoring for the entire device is paused if
the Ping sensor is in a Down status. Usually, it does not make sense to monitor other aspects
of a device with other sensors while the Ping sensor indicates that the device is not even
reachable.
To view a list of all dependencies or only selected dependencies, choose Devices |
Dependencies and the corresponding dependencies path from the main menu 202 . From there
you can also access the Dependencies Graph 2751 that visualizes all dependencies within your
network.
Dependenc ies Graph
For more information about the dependency settings, please see the settings of the object
you want to set a dependency for, section Schedules, Dependencies, and Maint enance
Window 342 respectively.
98
159
24.03.2015
Part 4: Understanding Basic Concepts | 7 Scheduling
4.7
Scheduling
Using schedules, monitoring of an object can be paused 185 for a certain time, for example,
Sundays between 4 and 8 a.m. A paused sensor will not collect monitoring data, will not
change its status, and will not trigger any notifications 100 . With schedules you can limit the
monitoring time automatically. You can also pause monitoring for planned system maintenance
time spans to avoid false alarms. You can apply different schedules to every object. They are
also used for reports and notifications.
Av ailable Default Sc hedules in Dev ic e Settings
Schedules are user account specific. To change the default pre-defined schedules or to add
your own schedule, please see Account Set t ingsSchedules 2856 section.
Note: If you use failover clustering with nodes in different timezones, scheduling applies at the
local time of each node. For more information, please see section Failover Clust er
Configurat ionBefore Get t ing St art ed 3123 .
24.03.2015
99
Part 4: Understanding Basic Concepts | 8 Notifying
4.8
Notifying
PRTG Network Monitor keeps the administrator or other responsible persons informed about
the current status of the network. There are several methods how the administrator can stay
up to date.
Notifications
This is the most powerful information tool. Whenever PRTG discovers downtime, an overloaded
system, threshold breaches (for example, a disk runs full), or similar situations, it can send a
notification. Notifications use various methods by which you can be notified (for example, email
2841 , SMS 2836 , push messages 2842 , 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 2759 section for more details and Set t ing Up
Not ificat ions Based on Sensor Limit s: Example 2762 for a step-by-step guide.
Limits
In a sensor channel's settings 2711 , you can set limits to change the status of the sensor when
certain limits are breached. This way, you can set, for example, a traffic sensor (typically never
in a error status) to Down status whenever bandwidth values are measured that you consider
critical. This sensor will then show up in the alarms list.
Alarms
The alarms list shows all sensors that are currently in a Down, Down (Acknowledged),
Warning, or Unusual status. This is useful to keep track of all irregularities in your network. In
the table list, you can re-sort the items by clicking on the column's header items. See Alarms
161 section for more details.
Logs
In the logs list, the log file with all monitoring events is shown. In a typical setup, a huge
amount of data is produced here. As the activity of every single object is minuted, you can use
this data to check exactly if your setup works as expected. See Logs 169 section for more
information.
Tickets
The tickets list shows items with important system information or action steps to take for the
administrator. You should view every ticket and take appropriate actions. Per default, an email
is sent to the administrator for every new ticket that is created by the system or another user.
If a ticket is assigned to a specific user, this user will get an email by default. See Ticket s 171
section for more information.
100
24.03.2015
Part 4: Understanding Basic Concepts | 9 User Access Rights
4.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 as or can create a nearly
unlimited number of other users. Single users are organized in a nearly unlimited number of
user groups. Each user group can separately have access rights for each individual object in
your PRTG device tree 89 (except for sensor channels). Objects can also inherit 94 access
rights according to the hierarchic structure of the device tree.
In addition, every single user has specific rights: There are administrator users, read/write
users, and read only users. You can define these settings in Sy st em Administ rat ionUser
Account s 2890 . With 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 access rights of the group(s) they belong to conduct
the access rights to certain objects in the device tree. This means that group membership
particularly controls what a user is allowed to do and which objects the user will see when
logged in.
The actual access rights for each object in the device tree can be defined in an object's
settings. You can define different access rights for all sensors, devices, groups, or probes via
the corresponding Cont ext Menus 186 or in the Object Set t ings 159 .
Access Rights Overview

The following classes of access rights for objects are available in hierarchical order as they can
be given to user groups (lowest rights to highest rights):
None: The object will not be displayed to the users of the group; no logs, no tickets, no
alarms regarding this object will appear.
Read: You can see only 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.
31.08.2015
101
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.
Note: Access rights that are defined locally on an object, for example, on a device, override
inherited 94 rights. On a certain object, the highest directly set access right applies for a user
group. If there is no access right set directly on an object, the next higher object level will be
checked for access rights. This process is repeated until defined access rights are found to be
inherited or there is no higher object level.
Different Ac c ess Rights for a Firewall in the Dev ic e Tree Depending on User Groups
Please see the table below for which user rights apply when. Column headings show access
rights of user groups for objects in the device tree; line headings show the type of user.
Note: Users are either in PRTG user groups or in Active Directory Domain user groups. They
cannot be in both of them. We recommend that you use only one type of user group (either
PRTG or Active Directory) to minimize your administration effort.
102
PRTG User
Group
PRTG User
Group
PRTG User
Group
PRTG Sy st em
Administ rat or
Domain User
Group
Domain User
Group
Domain User
Group
Domain
Administ rat or
31.08.2015
R EAD ACCESS
PRTG User Read Read-only rights
Only
R EAD/WR ITE
ACCESS
FU LL ACCESS
Read-only rights
Read-only rights
Admin rights
Domain User
Read Only
PRTG User
Read/Writ e
Read-only rights
Read/write rights Full access
Admin rights
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 read rights, 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 2830 , 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 than one group, access rights of the user group with the highest right s
apply .
Administrator rights can only be given via the administrator group.
For more information about defining access rights, please see the following sections:
Sy st em Administ rat ionUser Account s
Sy st em Administ rat ionUser Groups
2890
2896
For information about connecting PRTG to an existing Active Directory, please see Act ive
Direct ory Int egrat ion 3083 .
31.08.2015
103
Part 4: Understanding Basic Concepts | 10 Data Reporting
4.10
Data Reporting
With Report s 2786 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 146 section for more information.
Generate Reports
You can use the sophisticated reports machine included in PRTG to create exhaustive reports
for all monitoring data. See the Report s 2786 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) 3086 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 101 section), or you can create public or semi-public HTML
pages with monitoring data using the Maps feature. See the Maps 2810 section for more
information.
Bill Customers
You can also create custom billing reports based on PRTG's monitoring data, using the open
source Billing Tool for PRTG. For details and download, please see the More 104 section
below.
More
Dat a St orage
3135
Paessler Website: Billing Tool

https://www.paessler.com/tools/billingtool
104
15.04.2016
Part 4: Understanding Basic Concepts | 11 IPv6
4.11
IPv6
PRTG supports the IPv6 protocol for most sensor types. You can define whether you want
PRTG to query data from your network devices via an IPv4 or IPv6 connection. Indicate your
wishes in the Device Set t ings 324 of each device. The sensors you create on them will use the
protocol you indicated.
Note: Not all sensor types are IPv6 compatible. You can see which sensors support IPv6 in the
Add Sensor 256 dialog. Incompatible sensors are not selectable on IPv6 devices.
In the Out going IP Set t ings of the PRTG Administ rat ion Tool 3076 , you can additionally
choose which IPv6 address will be used for outgoing monitoring requests. Note: The the same
option is also available for IPv4.
05.11.2015
105
Part 5
Ajax Web InterfaceBasic Procedures
24.03.2015
107
Part 5: Ajax Web InterfaceBasic Procedures |
Ajax Web InterfaceBasic Procedures
The Ajax-based web interface is your access to PRTG. Use it to configure devices and sensors,
to set up notifications, as well as to review monitoring results and to create reports. This web
interface is highly interactive, using Asynchronous Java Script and XML (AJAX) to deliver a
powerful and easy-to-use user experience. While you are logged in 110 , the PRTG web interface
permanently refreshes the data on the screen permanently (via Ajax calls) so it always shows
the current monitoring results (you can set 2890 refresh interval and method individually).
Because the web interface works as a Single Page Application (SPA), you rarely see a full page
refresh to avoid this performance impact due to redundant processing. Only single page
elements are refreshed when necessary. The AJAX web interface shows all object setting
dialogs as pop-up layers, so you never lose the current context. This speeds up the user
experience appreciably and makes the configuration of objects in PRTG comprehensible. The
responsive design of the web interface ensures that it always adjusts to the size of your
screen to see more information at a glance.
The following sections introduce the features and concepts of the Ajax Graphical User
Interface (GUI).
Ajax Web InterfaceBasic ProceduresTopics

Login
110
SSL Cert ificat e Warning

Welcome Page
117
Cust omer Service

General Lay out
Sensor St at es
113
121
123
135
Review Monit oring Dat a

Compare Sensors
143
Hist oric Dat a Report s

Similar Sensors
146
151
Recommended Sensors
Object Set t ings
Alarms
155
159
161
Sy st em Informat ion
Logs
164
169
Ticket s
171
Working wit h Table List s

Object Select or
178
181
Priorit y and Favorit es
108
137
182
24.03.2015
Part 5: Ajax Web InterfaceBasic Procedures |
Pause
185
Cont ext Menus

Hover Popup
186
199
Main Menu St ruct ure
200
Other Ajax Web Interface Sections

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

In a web browser window, please enter the IP address or URL of the system PRTG is installed
on. When using a cluster, please connect to the primary master node. You can also double
click on the PRTG Net work Monit or icon on the desktop of the system PRTG is installed on.
Note: If you run PRTG on localhost, please do not use the DNS name http://localhost to log in
to the web server, as this may considerably slow down PRTG's web interface. Please use your
local IP address or http://127.0.0.1 instead.
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 113 .
Login Screen
After loading the web interface, the login screen is shown. You can either login as default
administrator or as an other PRTG user. As Administrator user you can use all functionalities of
the web interface. Administrators can create additional users 2890 with administrator rights or
with more restricted privileges (for example, read only users).
Additionally, there are different GUI versions available.
PRTG Login Sc reen
110
16.11.2015
Login as Default Administrator (First Time Login)

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

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

Depending on the used browser, different Graphical User Interface (GUI) options are shown:
Use AJAX Web GUI (All feat ures, opt imized for deskt op access): The standard interface.
We recommend to use this option for PRTG whenever possible. It offers the full functionality
of PRTG. Use Google Chrome 49 or later (recommended) or Mozilla Firefox 45 or later for
best performance. In some browsers, the Ajax option is not shown, for example, in old
browser versions.
Note: Although you can login using Microsoft Internet Explorer 11, the Ajax web interface
might not be fully compatible with Internet Explorer! When using Microsoft Internet
Explorer 11, please set the security level at least to Default level Medium-high and make
sure you do not use the Compat ibilit y View! For detailed information, please see the
More 112 section below.
Use Mobile Web GUI (Limit ed funct ionalit y , opt imized for mobile access): The Mobile
Web GUI 2991 interface is optimized for slow network connections and old browsers. It only
offers read-only functionality and comes with less scripting. It is also a fallback solution when
using a browser that is not supported by the Ajax interface.
Note: This user interface is deprecated. For mobile access to your PRTG server, please use
the PRTG mobile apps 2995 .
Download Client Soft ware (for Windows, iOS, Android): This option calls PRTG's download
page in the Mobile Web GUI. You can optionally download the native Windows application
Ent erprise Console to the desktop (called Windows GUI in previous deprecated PRTG
versions). It has to be installed 2938 on the client computer before use. The Enterprise
Console 2938 provides full functionality. However, for some functions the Ajax Web GUI is
opened. As an additional feature, the Enterprise Console can view data of several
independent PRTG core installations in one single application.
You can also access pages on Paessler's website from here for information about the PRTG
apps 2995 PRTG for iOS, PRTG for Android and PRTG for Windows Phone. These pages also
contain the download links to the corresponding app stores. Note: Also when using this
download option, your name and password (or a Default Login) are required for login!
16.11.2015
111
Note: Only Google Chrome 49 or later (recommended) and Mozilla Firefox 45 or later are fully
compatible with the Ajax web interface. For more information about Internet Explorer support,
please see the More 112 section below.
Click on the Login button to proceed to the PRTG web interface.
More
Knowledge Base: Why are Internet Explorer IE6 and IE7 not supported by PRTG's Ajax Interface?
Knowledge Base: How can I access the AJAX web interface of PRTG with Internet Explorer 9 or
IE10?
112
16.11.2015
Part 5: Ajax Web InterfaceBasic Procedures | 2 SSL Certificate Warning
5.2
SSL Certificate Warning
If you use PRTG outside your internal LAN, especially when you use it on the internet, you
should switch the internal web server to use SSL 2862 . After doing so, your browser shows a
certificate warning because the certificate that comes with PRTG cannot be signed by a valid
authority. Anyway, the connection to your PRTG web server is secured via SSL, and you can
confirm the claimed security risk. For more information on secure browser connections, please
see the More 116 section below.
Every browser shows the certificate warning in a different layout. The steps to take are similar
for every browser, yet different in detail:
Google Chrome
Mozilla Firefox
113
114
Internet Explorer
Other
115
116
You can avoid these browser warnings by using your own trusted SSL certificate
For this purpose we provide the freeware tool PRTG Certificate Importer 3137 .
3137
with PRTG.
Google Chrome
In Google Chrome, click on Advanced and then on Proceed t o [y ourPRTGserver] (unsafe)
every time you call the PRTG web interface.
21.01.2016
113
Sec urity Warning in Google Chrome Browser
Mozilla Firefox
In Mozilla Firefox, click on I Underst and t he Risks and then on the Add Except ion... button.
In the appearing window, leave the check mark for Permanent ly st ore t his except ion and
finally click on the Confirm Securit y Except ion button.
114
21.01.2016
Sec urity Warning in Mozilla Firefox
You only have to go through this procedure once for every Firefox browser and PRTG core
server.
Internet Explorer
In Int ernet Explorer, click on Cont inue t o t his websit e (not recommended) every time you
call the web interface.
Sec urity Warning in Internet Explorer
21.01.2016
115
Other
For other browsers that are not officially supported, the procedures to confirm the certificate
are similar to the ones described above.
More
Using Your Own SSL Cert ificat e
3137
Freeware Network Tools: PRTG Certificate ImporterInstalling Trusted SSL Certificates for PRTG
Network Monitor
https://www.paessler.com/tools/certificateimporter
Knowledge Base: Why don't I get an SSL connection to the PRTG web interface?
Knowledge Base: Why can't I save my PRTG password in Google Chrome?
Knowledge Base: How can I stop Google Chrome showing me a "connection not private"
message?
116
21.01.2016
Part 5: Ajax Web InterfaceBasic Procedures | 3 Welcome Page
5.3
Welcome Page
After completing the Smart Set up 37 , you will see PRTG's welcome page as default when you
log in to the web interface. You can set another homepage in your account settings 2830 ,
section Web Int erface.
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax
interface on a master node. For other user accounts, interfaces, or nodes, not all of the
options might be visible in the way described here. When using a cluster installation, 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. You can also directly access several pages in the PRTG web
interface from the welcome page.
You have the following options on the welcome page:
View Result s: Open the device tree
21.01.2016
123
that shows your monitoring results.
117
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 2932 and contact our customer service 121 from this page.
Inst all Smart phone App: Open the download page for PRTG's mobile apps
2928
Download Ent erprise Console: Open the download page for the Enterprise Console
PRTG.
2928
in
Welc ome Page: A Good Starting Point for Your Daily Monitoring Ac tiv ities
The welcome page keeps you informed about current Alarms

View All Alarms: Open a list of alarms
161
and open Ticket s
171
in your PRTG installation.
View All Ticket s: Open a list of all open tickets

in user.
118
161
171
that are assigned to the currently logged
21.01.2016
Welc ome Page: Alarms Ov erv iew and Open Tic kets
Other sections are:

News from Paessler: 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 usSy st em St at us 2911 , section Act ivit y Hist ory .
License St at us: Shows the number of your left maintenance days for PRTG 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. Click Get More Sensors to open the Paessler
shop and upgrade your license. See also manual section PRTG St at usLicense St at us and
Set t ings 2925 .
Note: If you use a PRTG license with an unlimited number of sensors, you will see 0 Sensors
Available here for technical reasons. Of course, you can still add sensors if you run an
unlimited edition nevertheless. Please consider the system requirements 23 for a properly
working PRTG setup and click Recommended Set up for more information.
Updat e Available: Shows the version number of your PRTG 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 PRTG's Aut o-Updat e 2918 page.
If your PRTG is currently not SSL secured, the welcome page asks 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 ionUser Int erface 2862 .
If you still use the default password of the PRTG System Administrator user (prtgadmin), the
welcome page asks 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 ionUser Account s 2890 .
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.
21.01.2016
119
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 2810 feature of PRTG enables you to create dashboards exactly
like you want.
120
21.01.2016

1 Customer Service
5.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 assist you with quotes and valuable information about license and
maintenance, guide you through the purchasing process, and support you with contacting our
system engineers or partners in your region.
Note: 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
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.
21.01.2016
121

1 Customer Service
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.
Note: If you have technical questions regarding monitoring with PRTG, please contact our
technical support 2932 .
122
21.01.2016
Part 5: Ajax Web InterfaceBasic Procedures | 4 General Layout
5.4
General Layout
This manual section provides an overview about the structure of PRTG's web interface. The
main focus is on the Devices view which you can select via the main menu bar, because there
you see your monitoring results at a glance so you will widely use it.
Welcome Page
When you log in to the PRTG web interface, you will see PRTG's Welcome Page 117 as default.
You can set another homepage in your account settings 2830 , section Web Int erface.
Click View Result s to open the device tree view.
Tree View Layout

Click Review Result s on the welcome screen to display the tree-like device view which will be
a starting point for everyday use or click Devices in the main menu bar 125 .
PRTG Dev ic e Tree
From top to bottom, the main layout consists of:
21.01.2016
123
Screen
Number
Part
Descript ion
Global Header
Area 125
This element contains the main menu at the top, the global
status bar, the path to the currently selected object, and a
quick search box.
Page Header Bar
This element contains the page heading with the name of the
current object, several tabs with settings, monitoring data of
the current object, the object's status bar, quick action
buttons, and the QR code that links to the current URL.
126
Device Tree
View 129
This selection is part of the page header bar. Using the

provided options you can define how your device tree is
displayed.
Page Content
This element contains information about the current object and

all other objects underneath in the tree hierarchy.
133
Page Footer
Icons
With these icons you have quick access to the PRTG Aut oUpdat e 2918 page, to PRTG's social network accounts, and to
the contact support form 2932 . There is also a link to context
sensitive help.
When running PRTG in a cluster, you will also see a cluster
related element. It shows the name of the node you are logged
in and displays whether this is a master or a failover node. Click
the bar to show the Clust er St at us 2923 . 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.
Page Footer
Shows information about the current version of PRTG, the

logged in user, the time remaining to the next automatic page
refresh, and the current time (depending on the time zone
settings 2893 for the currently logged in user).
Simply click an object to see more details about it. In the page heading of the page header bar
126 you always see the name of the object that you have currently selected.
When you navigate through PRTG's web interface you will always use one of the following
navigational paths:
The main menu provides access to all important aspects of the software.
The quick search is often the fastest way to navigate to an object.
Using the page's tabs, you can switch between various sub-pages for an object.
Many objects offer a context menu that open when you right-click them.
124
21.01.2016
Many objects offer a quick-info menu that open when you point to an object.
You can drill down into the object hierarchy of probes, groups, devices, and sensors in the
object tree by merely clicking an sub-object of the currently displayed object (for example, a
sensor on the device page).
These six navigation paths put PRTG's complete functionality at your fingertips. Quite likely you
are already familiar with these techniques from many other websites and web-based user
interfaces.
In the following, the different areas of the web interface are described.
Global Header Area
PRTG's Global Header Area
The header area of the web interface is both base for the most important information of your
installation and starting point for all actions. You can view the global status and navigate
through the web interface using the main menu.
The global header area consists of the following parts:
21.01.2016
125
Screen
Number
Part
Descript ion
Main Menu Bar
Navigating through the web interface is performed using the

main menu. Please take a few minutes to familiarize yourself
with all menu items and sub-items. A detailed description can
be found in the Main Menu St ruct ure 200 section.
Icons Refresh,
Help Center,
Logout
With the icons on the right you can reload the current page,
open the help center or log the current user out.
White Search
Box
To search for any monitoring object, enter the name, part of

the name, an IP address, a DNS name or a tag in the search box
on the right and hit the enter key. A web page with all items
that fit the search term will be returnedeven displaying online
help articles.
Breadcrumbs
Below the main menu you see always a path which leads to the
homepage. Use it to go back to where you came from. It can
also help you to orient yourself if you get lost. If you click a
breadcrumb item, a drop-down menu opens that shows all
available objects on the same level. Enter some characters to
search for a name, or select an object directly. For example,
you can use this to directly access all other sensors or a
device, other devices within a group, another group on the
same probe, or other probes in your root group.
Buttons New
These buttons show the number of new alarms and new log
Alarms, New Log entries, as well as the number of new tickets. Click the
Entries, New
respective button to view the Alarms 161 , Logs 169 , or Ticket s
171 .
Tickets
Global Sensor
Status Symbols
This area shows the aggregated status of all sensors you have
configured for monitoring, divided into different sensor states.
Depending on the sensors' status you will see colored boxes
with numbers which symbolize the sensors. For example, you
can see how many sensors are in Up, Down, or Warning
status. Click a box to view a list of all sensors in the respective
status. For a detailed description, please see Sensor St at es 135
section.
Page Header Bar

In the page header under the global header area, you see the name of the current object and
the page content underneath. When displaying a group, aggregated sensor states are shown
in a sensor bar and there is an option to change the tree view. Furthermore, various
information about the current object is reported here.
126
21.01.2016
PRTG's Page Header Bar
The page header and tabs area consists of the following parts:
21.01.2016
127
Screen
Number
Part
Descript ion
Page Heading
This line displays the kind of the current object and the name
as page heading. In the screenshot above, it is a group which is
called Root . Here you also can add the current object to
favorites by clicking on the flag, as well as you can define the
object's priority by clicking on one of the five stars (not
available for the Root group). For details, please see section
Priorit y and Favorit es 182 .
Tabs
Using the tabs you can navigate to various sub-pages of an

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

object.
Sensor Status
Bar
This element is visible when viewing a probe, a group

(including Root ), or a device. It is not available when viewing a
sensor's details. The sensor status bar shows the aggregated
status of all sensors for the current object, divided into
different sensor states. They show the number of sensors in
the respective state. For example, you can see how many
sensors are in Up, Down, or Warning state. For a detailed
description of sensor states, please see Sensor St at es 135
section. You can hide sensors that are in a certain state by
removing the check mark symbol in front of the respective
sensor symbol. To show them again, re-add the check mark.
Tree Search
In the white search box next to the tree view selection, enter a
key word to search the device tree for matching names. The
tree will highlight matching devices and sensors by graying out
all others. This can help to gain a quick overview over sensors
monitoring a specific part of your network. For example, you
can enter the keyword "firewall" to highlight devices and
sensors which match this name.
Device Tree
View
This element is only visible when viewing a probe or a group. It

is not available when viewing a device's or sensor's details. For
a detailed description, see Switch Device Tree View 129 below.
21.01.2016
Depending on the selected object type, the page header bar shows additional information:
All objects underneath the Root group show their dependency
98
Groups and devices show the past time since the last execution of the auto-discovery
the selected object.
219
on
Devices show their respective DNS/IP address as defined in the device settings 324 and the
past time since the last execution of the sensor recommendation 155 on this device.
Sensors show additional monitoring statistics.
Switch Device Tree View

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

Buttons
Switch Device Tree ViewClassic Device Tree

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

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

The sunburst view shows your entire installation in one circle diagram. The groups are
represented as inner circles, and all devices contained within a group are shown as 'cake slices'
attached to the outside of a circle element.
130
21.01.2016
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 135 ) 135 . A more severe status is
regarded more important and wins the color battle. For example, if a device currently has
sensors in the states Up (green), Paused (blue), and Warning (yellow), the according device
tile in this view would be yellow, indicating that at least one sensor on this device is in
Warning status. If there are any red Down sensors, the according device tile will turn red.
Following, all possible states in both views are listed ordered by their hierarchy:
21.01.2016
131
Flag
Flag Color
Object St at us
Meaning
Red
Down
At least one sensor of this object shows a red

Down status. Hover over an object's name to
view the total number of alarms concerning this
object.
Bright-Red
Down
At least one sensor of this object is Down and
(Acknowledged) the status was acknowledged by a PRTG user,
applying the Acknowledge Alarm function. The
Down states of all sensors of this object have
to be acknowledgedif at least one sensor is
unacknowledged down, this object will be
displayed as Down.
Yellow
Warning
At least one sensor of this object shows a

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

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

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

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

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

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

Object Set t ings
159
Compare Sensors
Geo Maps
146
143
2753
More
Knowledge Base: How can I change the width of the devices and group "boxes" shown in the
PRTG 9 device tree?
134
21.01.2016
Part 5: Ajax Web InterfaceBasic Procedures | 5 Sensor States
5.5
Sensor States
In PRTG's device tree you usually create several sensors on each 'device 324 '. With sensors, you
can monitor different aspects of your devices. Using a simple color code, they always show
you what is going on in your network.
The color of a sensor always shows its current status. Following, you find a list of states a
sensor can show. This list also reflects the hierarchy of states whenever summarized sensor
states are shown (in the device tree 123 , or on geo maps 2753 ) : the higher a status is in the
hierarchy, the higher will be its priority in displaying sensor states. For example, if all the
sensors of a specific device are Up, but one of its sensors reached a Down status, then the
overall status of this device will be Down as well (for example, displayed red in the Tree Map
View 129 ), as this state is hierarchically higher.
Note: Down and Down (Part ial) states are hierarchically equal.
Sen Colo
sor r
Red
St at us
Name
Meaning
Down
1. PRTG is not able to reach the device or the sensor has reached
an error state. Please see Sensor Warning and Down Behavior
136 below for more information. Note: By design, a sensor does
not record any data in its channels while it shows this status.
2. Another reason for this status can be an error limit that is set in
the Sensor Channels Set t ings 2711 , or an error status due to a
sensor Lookup 3095 . Note: In this case, the sensor continues to
record data in all sensor channels although the sensor shows
an error.
Gree
n/
Red
Down
(Part ial)
Brigh
t-Red
Down
(Acknowl
edged)
The sensor is Down and the status was acknowledged by a PRTG

user, applying the Acknowledge Alarm function. This can be
helpful to mark that an alarm has already been attended to. For
acknowledged alarms no more notifications 2759 are sent. To set
this sensor status, right-click on a sensor in a Down status and
from the context menu 186 , select Acknowledge Alarm.... Then
enter a comment and click OK.
Yello
w
Warning
There was an error reading the sensor, but PRTG will try again. The
sensor may soon change to a down status. Please see Sensor
Warning and Down Behavior 136 below for more information.
Another reason for this state can be a warning limit set in a
sensor's Sensor Channels Set t ings 2711 .
05.11.2015
In a cluster, at least one node reports this sensor as Down, while

at least one other node reports the same sensor as Up.
Note: This status is not available for sensors on remote probes in
a failover cluster 87 .
135
Part 5: Ajax Web InterfaceBasic Procedures | 5 Sensor States
Sen Colo
sor r
St at us
Name
Meaning
Oran
ge
Unusual
The sensor reports unusual values for this weekday and time of
day. The unusual detection is based on the historic average data
and can be configured or disabled in the system administration 2872 .
You can also disable unusual detection for certain groups only
(see Group Set t ings 322 ).
Gree
n
Up
The last check was okay and the sensor receives data.
Blue
Paused
The sensor is currently paused (for a certain time or unlimitedly, or

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

The Down status symbolizes that something is wrong with a monitored device. There can be
various reasons for a down status, for example, an interruption in the physical connection to
the device, an internet connection outage, or a crashed server.
After a failed request, PRTG tries to reach the device again before setting a sensor to Down
status (this is true for almost all types of sensors):
1. If a request to a device fails for the first time, the sensor is set to Warning status. PRTG
repeats the request and tries to re-scan the device immediately.
2. If also the second request fails, the sensor is set to Down status by default until the device
is reachable again. You can change this behavior in the Scanning Int erval 272 settings of any
monitoring object. PRTG tries to reach the device with every scanning interval.
This procedure gives devices and services the chance to recover from a momentary overload
and prevents false alarms. Still, you are informed promptly about any failures occurring.
Note: The behavior described above does not apply to a Warning or Down status that is
activated due to a warning or error limit set in the Sensor Channels Set t ings 2711 or to
channels using lookups 3095 .
More
Knowledge Base: What to check if sensors are black (gray)?
136
05.11.2015
Part 5: Ajax Web InterfaceBasic Procedures | 6 Review Monitoring Data
5.6
Review Monitoring Data
Pages of probes, groups, devices, and sensors have an interface providing tabs. By using the
tabs you can navigate through various sub-pages of an object to show your network's status,
view monitoring results, or change settings.
Tabs Bar on Sensor Pages
Overview
The Overview tab shows an overview of the currently selected object and of its sensors. The
pages share a common layout, but include different elements, depending on the kind of object
you look at:
For probes and groups, the Overview tab shows a tree-like view with devices and sensors,
a Geo Map, as well as summary graphs for different time spans of the current probe or
group.
For devices, the Overview tab shows device details, a Geo Map, and summary graphs for
different time spans, colored gauges for high priority sensors, as well as a table list of all
sensors on this device. Additionally, you see a table list 178 with Recommended Sensors
155
Note: You can turn off the sensor recommendation (and disable this table list) in Sy st em
Administ rat ionMonit oring 2874 .
Note: To display gauges, you have to tag corresponding sensors with 4 stars (****) or 5
stars (*****) in the priority settings 182 . 5 star sensors are represented with bigger gauges
than 4 star sensors.
For sensors, the Overview tab shows sensor details, current status, colored gauges, sensor
graphs for different time spans, a table with all sensor channels, as well as similar sensors 151
which show correlations in your network.
Gauges and switches represent sensor values on Overview tabs of devices and channel
values on Overview tabs of sensors. They graphically illustrate the current values of a
sensor or a channel, so you can use them as a quick status indicator. The red and yellow
parts of gauges correspond to the error and warning limits of the respective sensor channel
settings 2711 . Device overview tabs show gauges of high priority sensors, sensor overview
tabs show gauges of all sensor channels (except the Downt ime channel), with the primary
channel having the biggest gauge. For sensor channels that measure or calculate binary
values like on/off or successful/failing using lookups, a switch shows green or red color
respectively.
Note: For sensors using lookups 3095 , we recommend staying below 120 lookup values in the
primary channel to get expressive gauges. For sensors with a priority of 4 stars, the upper limit
is around 40 lookup values.
11.03.2016
137
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 349 only. Toplist graphs are
displayed right on the sensor overview page. Please see the section Toplist s 2734 .
Live Data and Data By x Days

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

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

For sensors, the tabs show a graph and data table of the selected sensor. When viewing data
of a sensor running on a cluster probe, you can additionally select if you want to show the
data of all nodes, or of one specific node only. Please use the Select Clust er Member bar
below the tabs.
140
11.03.2016
Note: Multi-node graphs are never displayed filled here, but with single lines only. However,
historic data reports can have filled multi-node graphs.
While viewing a sensor graph you can hide single sensor channels individually. Simply remove
the check mark symbol in front of a channel name 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.
Live Data and Data By x DaysInteractive Graphs

On historic data tabs of sensors and in "zoomed graphs in new windows" (see below) of other
monitoring objects, graphs are interactive. You can zoom in and scroll along the time axis with
the corresponding buttons.
Graph Buttons
The following actions for graphs are available:

<< scrolls one graph window left and >> one 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 shown time depends on the graph you select. 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 every graph, you see three small icons:
You can do the following with them:

Zoom graph in new window: Opens a larger version of the graph in a new browser window.
Download t he graph (PNG or SVG): Shows a PNG or SVG file of the graph in a new browser
window. You can then save or copy it for later use.
In every graph, you can also choose which specific channels (only on sensor pages) or indexes
you want to see by using the corresponding check boxes or the Show all and Hide all
buttons.
Note: Warning or error limits 2712 are only shown in graphs (highlighted in yellow or red) if you
select exactly one channel with a limit.
11.03.2016
141
Historic Data
The Hist oric Dat a tab is available for sensors only. Please see the section Hist oric Dat a
Report s 146 .
Sensors Lists
Viewing lists of sensors is a great way to keep an eye on your network status because you
can select which kind of sensors you would like to see. There are many different sensor list
views available, such as a list of favorite sensors and top 10 lists, lists filtered by current
sensor status, value, availability, tag or type, sensor cross reference, and many more.
Sensor lists are available from the main menu bar. Click the Sensors entry to show a table list
of all sensors. In the table list 178 appearing, you can re-sort the items by clicking on the
column's header items (see section Working wit h Table List s 178 ). Hover over it to show
other menu options. For detailed information about the available options, please see Main
Menu St ruct ure 205 (Sensors) section.
Alarms
The Alarms tab is not available for sensors, but for probes, groups, and devices only. Please
see the Alarms 161 section.
Log
The Logs tab shows past activities and events regarding the currently selected object. Please
see the Logs 169 section.
Related Topics
Object Set t ings
159
Compare Sensors
143
More
Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time Index?
142
11.03.2016
Part 5: Ajax Web InterfaceBasic Procedures | 7 Compare Sensors
5.7
Compare Sensors
This function allows you to visually compare the graphs of two or more specific sensors. The
selected graphs are shown next to each other so you can have a look at all of them at the
same time.
To open the page to compare graphs of several sensors, from the main menu, choose Sensors
| Compare Sensors. Hover over it and select how many sensors you want to compare.
PRTG Main Menu: Compare

Sensors
Choose the number of sensors that you want to compare. This opens an assistant where you
can define your desired sensors and the time span the particular graphs cover.
15.10.2015
143
Compare Graphs of Two Sensors with 30 Day s Time Span
Compare Sensors Settings

OPTIONS
Time Span
Specify the time span for which you want to show the graphs for.
Choose between:
2 day s
30 day s
365 day s
Dat a Comparison
Select the objects you want to show a graph for. Click on Click here t o select an object ! to
open the Object Select or 181 . There appear as many selection screens as you defined before.
144
15.10.2015
Selec t the Objec ts to be Compared
PRTG shows the graphs immediately after object selection. You can now work with the
compared graphs like on the historic data tabs of sensors 140 : select the channels you want to
show and zoom and scroll in the graphs. Click Select New Sensor to choose another sensor
for comparison.
Related Topics
If you want to create a sensor that combines the data of different other sensors, please see
the following sensor type:
Sensor Fact ory Sensor
15.10.2015
1374
145
Part 5: Ajax Web InterfaceBasic Procedures | 8 Historic Data Reports
5.8
Historic Data Reports
For quick reporting of a sensor's monitoring data, use the historic data reports as an
alternative to the comprehensive Report s 2786 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
to your computer for further processing in external applications.
There are two possibilities to call the function for historic data reports: Either you click on the
Hist oric Dat a tab on a sensor's detail page, or you choose Sensors | View Hist oric Dat a
from the main menu 205 .
Historic Data (Sensor Tab)

The Hist oric Dat a tab is available for sensors only (not for probes, groups, or devices). When
you call the historic data reports via this tab, there is no sensor selection available because
you already determined which sensor you want to create a report for. If you want to select
another sensor for the report, choose Sensors | View Hist oric Dat a from the main menu in
Historic Data Tab of Ping Sensor
146
11.03.2016
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/historic _data_tab_ping_sensor.png
Historic Monitoring Data (Sensors Main Menu)

When you call historic data reports via the View Hist oric Dat a entry from the Sensors tab in
the main menu, you additionally have to choose the sensor you want to create a report for
with the Object Select or 181 .
Historic Monitoring Data Settings

SETTINGS
Sensor
This field is only visible if you call the historic data function via the
main menu. Select the sensor you want to create the report for:
Click on the reading-glass symbol to open the object selector. For
more information, see section Object Select or 181 .
Start
Specify the start date and time of the data you want to review. Use
the date time picker to enter the date and time.
End
Specify the end date and time of the data you want to review. Use
the date time picker to enter the date and time.
Quick Range
In this section you can use several buttons for a faster selection of
start and end dates. Click on any of these links to change the
St art and End values above. Choose between:
1 Day , 2 Day s, 7 Day s, or 14 Day s: Set the date range to the
respective day(s). The current time of the current day is the end
date.
Today , Yest erday , Last Week (Mo-Su), Last Week (Su-Sa), Last
Mont h, 2 Mont hs, 6 Mont hs, 12 Mont hs: Set the date range to
the last matching period. It starts at 00:00 and ends at 00:00 of
the particularly following day.
Average Interval
With this option, you can activate and set up averaging. Select an
interval for which PRTG calculates the average value. You can
choose between No Int erval (no averaging is performed and only
raw data displayed), a few seconds, minutes, hours, or a whole day
(24 Hours). A smaller interval results in a more detailed report for
this sensor.
The best settings for you vary, depending on the scanning interval
of the sensor, the selected date period and, of course, the
intended use for the report. It might be useful to try different
settings to see what the results look like. Please also see the
section Aut omat ic Averaging 149 below.
11.03.2016
147
SETTINGS
Channels
Select the channels you want to include in the report. You can
select or deselect single channels with the respective check
boxes, and select or deselect all channels with the buttons Show
all or Hide all. PRTG shows only the data of selected data in the
report.
Cluster Node
This field is only visible if the sensor is running on a cluster probe.

Select the cluster node's data that PRTG uses for the report.
Choose between:
All nodes: Include the data of all cluster nodes in the report.
[Several specific nodes]: Use a specific node's data for the
report. The nodes you see are specific to your setup.
File Format
Select the output format for the report. Choose between:

HTML web page: Display the result directly as HTML web page.
This is also a good option to check results before exporting to
another file format.
X ML file: Export the data as Extensible Markup Language (XML)
file. Usually, you browser shows a download dialog when you
use this option.
CSV file: Export the data as Comma Seperated Values (CSV) file,
for example, for import into Microsoft Excel. Usually, you
browser shows a download dialog when you use this option.
INCLU DE PER CENTILES

Percentile Results
Define if you want to include an additional percentile calculation

of your data in the report. Choose between:
3107
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,
which shows percentiles for every sensor channel.
Note: 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.
148
11.03.2016

Likewise, percentiles are not available if in a cluster setup you
choose the option All Nodes in the Cluster 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
Interval
Enter a value to define the averaging interval on which PRTG bases
the percentile calculation. The default value is 300 (seconds),
which is equivalent to 5 minutes. This means that PRTG takes 5
minute averages as basic values for the percentile calculation.
Percentile Mode
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.

Note: Data reporting is limited to 5 requests per minute.
Note: Reports cannot show uptime or downtime data for the Sensor Fact ory Sensor
1374
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
11.03.2016
149
A report for a time span of more than 500 days is not possible. If you try to set a larger time
span, it will be reduced to 365 days automatically.
Related Topics
Report s
137
2786
More
Knowledge Base: Why is there missing data in historical data reports?
150
11.03.2016
Part 5: Ajax Web InterfaceBasic Procedures | 9 Similar Sensors
5.9
Similar Sensors
With PRTG you can detect relationships between different components in your network. This
function is called similar sensors analysis, a heuristic calculation showing similar behavior of
your sensors. The analysis is completely automated and sensor type agnostic. It is based on
mathematics and fuzzy logic. This feature helps you find interconnections in your network you
were not aware of and optimizes your sensor usage by tracking redundant monitoring of
some aspects of your system.
You can adjust the depth of similar sensors analysis or turn it off in Sy st em Administ rat ion
Monit oring 2874 . You can also switch on and off the similarity analysis for specific probes,
groups, and devices and specify inheritance 94 in the corresponding object settings 159 ,
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
which show similarities to channels of the current sensor.
In addition, you can call a similar sensors overview page via Sensors | Similar Sensors
Overview from the main menu 205 .
Similar Sensors (Sensor Overview Tab)

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

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

currently selected sensor (the one in the "Channel" column in the
same row).
Note: PRTG does not show the similar sensors section when the analysis is off or you have
exceeded 1,000 sensor and selected the automatic analysis depth option 2874 . You will see a
notice in this case.
152
11.03.2016
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 178 .
Note: PRTG only shows similar sensors here when channels have at least 85% similarity.
Furthermore, the analysis saves up to 15 entries per sensor at most.
Similar Sensors Ov erv iew
You can sort the list by clicking on the column headers. The similar sensors overview page
provides the following information:
SIMILAR SENSOR S OVER VIEW

Original Channel
Shows channels to which other channels are compared. Click on

the column header to sort the list according to the order on the
device tree in ascending or descending order.
Similarity
Shows a measurement of similarity between two channels in

percent. Click on the column header to sort the list according to
the similarities in ascending or descending order.
11.03.2016
153
SIMILAR SENSOR S OVER VIEW

Similar Channel
Shows a channel compared to the original channel. Click on the

column header to sort the list according to the order on the
device tree in ascending or descending order.
Item Count
Define how many channel similarities are shown on this page.

Choose between 50, 100, or 500.
Note: PRTG does not show the similar sensors overview option in the main menu if you turned
off the analysis or if you have exceeded 1,000 sensors and selected the automatic analysis
depth option.
154
11.03.2016
Part 5: Ajax Web InterfaceBasic Procedures | 10 Recommended Sensors
5.10
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 137 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 any important monitoring data anymore!
Rec ommended Sensors on Dev ic e Ov erv iew Tab

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/rec ommended_sensors.png
Get Sensor Recommendations

You want to know which sensors can complete the monitoring of your devices? By default,
PRTG recommends sensors for any device 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 to 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 past time since the last execution of the sensor recommendation on a device
in the page header bar 126 on the Overview tab of this device.
Step 1: Choose the Device

Open the Overview
21.01.2016
137
tab of the device that you want to analyze.
155
Step 2: Recommend Now

To start the analysis of your device, click the Recommend Now button directly below the
sensor list or choose the option Recommend Now in the context menu 192 .
Note: If you do not see the Recommend Now option, make sure that the sensor
recommendation is enabled in the Sy st em Administ rat ionMonit oring 2874 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 ionMonit oring 2874 .
Note: To recommend SNMP sensors 350 for a device, the detection engine uses the SNMP
version that you defined in the Credent ials for SNMP Devices 332 section of the device
settings.
Step 3: Get the Results

After analyzing your device, PRTG suggests you a list of sensors that are useful for a more
comprehensive monitoring.
156
21.01.2016
List of Rec ommended Sensors
The list of recommended sensors provides the following information:
R ECOMMENDED SENSOR S
Priority
Shows which priority 182 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.
Note: 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 2071 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.
Note: 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 157 .
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.
Note: 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 like 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 196 or pause 185 the ones you do not need.
21.01.2016
157
Settings for the Recommended Sensors Analysis

You can also adjust the recommended sensors detection. Go to Sy st em Administ rat ion
Monit oring 2874 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 to run into performance issues.
Note: Disable the recommended sensors feature if you encounter performance issues or 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 219 ! You can activate it when adding a new device 245 to PRTG,
manually at any time 220 , or choose if you want PRTG to analyze a whole section 222 of your
network, for example, devices covered by a certain IP range.
Note: 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.
158
21.01.2016
Part 5: Ajax Web InterfaceBasic Procedures | 11 Object Settings
5.11
Object Settings
Device Tree Management

The Management tab is available when viewing probes or groups. After clicking this tab you
can move devices and sensors right within the tree view. If moving is not possible, the web
interface will start a clone process automatically.
For more information, please see the Manage Device Tree
258
section.
General Settings
In the Set t ings tab you can define all settings of the current object. The available options vary,
depending on the kind of object you're changing. Please see the following sections for
information about the respective object types:
Root Group Set t ings
Probe Set t ings
260
278
Group Set t ings
299
Device Set t ings
324
Sensor Set t ings
347
Note: The available setting options are different for each sensor, but always the same for
probes, groups, and devices. Sensor Channels Set t ings 2711 are not reachable via tab but
directly on a sensor's overview page via channel gauges and the channels table.
Notifications Settings
In the Not ificat ions tab, notification triggers can be set for every object. When using these
settings for a probe, group, or device, they will be inherited to all sensors on these objects.
Available notification trigger options are the same for all objects.
For more information, please see Sensor Not ificat ions Set t ings
2719
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.
09.07.2015
159
Part 5: Ajax Web InterfaceBasic Procedures | 11 Object Settings
Click Save to store your settings. If you change tabs or use the main menu, all changes to the
settings will be lost!
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 has conducted the change, and a message. The history log retains
the last 100 entries.
Note: On some pages, you can access the history of subordinate objects via the
corresponding context button in the page header bar 126 . This includes Sy st em
Administ rat ion 2860 and the overview pages of User Account s 2890 , User Groups
2786 , Libraries 2770 , and Maps 2810 . See the Logs (Main Menu) 169 for details.
2896
, Report s
Related Topics
General Lay out
123

Toplist s
160
137
2734
09.07.2015
Part 5: Ajax Web InterfaceBasic Procedures | 12 Alarms
5.12
Alarms
The alarms list shows all sensors that are currently in a Down, Down (Part ial), Down
(Acknowledged), Warning, or Unusual status. Sensors in other states (for example, Up,
Paused, or Unknown) do not appear here. This is useful to keep track of all irregularities in
your network.
In the table list
178
, you can re-sort the items by clicking the column's header items.
Alarms List
There are two options to call the alarms list: Either you click the Alarms tab on the detail page
of a probe, group, or device (not available for sensors), or you choose the Alarms entry in the
main menu.
Alarms (Object Tab)

Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you can
navigate through various sub-pages of an object in order to show your network's status, view
monitoring results, or change settings.
Tabs Bar on 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 main menu 208 . The tab is not available on a sensor's
detail page.
21.01.2016
161
Alarms (Main Menu)

Click the Alarms entry from the main menu 208 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. Point to the Alarms entry and
select another option to only show a subset of sensors in certain states. Choose between:
ALAR MS
All
Open a list of all sensors which are currently in Down, Down

(Part ial), Down (Acknowledged), Warning, or Unusual status
135
Show as Gauges
Open a page with the gauges of all sensors which are currently in
Down, Down (Part ial), Down (Acknowledged), Warning, or
Unusual status. The size of the sensor gauges corresponds to
their respective priority.
Errors Only

(Part ial), or Down (Acknowledged) status.
Warnings Only
Open a list of all sensors which are currently in Warning status.
Unusuals Only
Open a list of all sensors which are currently in Unusual status.
Acknowledge Alarm
An acknowledged alarm shows up in the alarms list as "acknowledged" (see Sensor St at es
and will not trigger 2719 any more notifications 2759 .
135
Note: If the alarm condition clears, the sensor usually returns into an Up status immediately
with the next sensor scan.
To acknowledge an alarm, right-click 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:
162
21.01.2016
ACKNOWLEDGE ALAR M U NTIL

Selected Objects
Shows the sensor(s) for which you want to acknowledge the

alarm. You can acknowledge alarms for more than one sensor
using multi-edit 2742 .
Message
Enter a text, for example, the reason why you acknowledge the
alarm. Please enter a string or leave the field empty.
Until
Enter the date when the acknowledge status will end. Use the date
time picker to enter the date and time.
Note: If the alarm condition still persists after the specified date,
the sensor will show a Down status again.
Only users 2890 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 2890 , section
Account Cont rol.
More
Knowledge Base: Which audible notifications are available in PRTG? Can I change the default
sound?
21.01.2016
163
Part 5: Ajax Web InterfaceBasic Procedures | 13 System Information
5.13
System Information
The Sy st em Informat ion feature can show you various information about a device such as
connected hardware, installed software, connected user accounts, running processes, and
available Windows services with their current status. This is a great possibility to see at a
glance what is currently running on the systems in your network. Together with your everyday
monitoring you will receive a really profound knowledge about your IT infrastructure from only
a single sourceyour PRTG Network Monitor!
System information is available for all devices which you add to PRTG and run with an officially
supported Windows version 23 . You can also retrieve system information from other devices
with enabled Simple Network Management Protocol (SNMP). On the overview page of a device,
click the Sy st em Informat ion tab to see available information.
Basically you do not have to configure anything special to use the system information feature.
PRTG uses the same technologies 3000 to request system information data as sensors that
receive monitoring data from a device. If you already monitor a device with WMI 352 and SNMP
sensors 350 , the main preconditions for retrieving system information for this device are already
met. The data will be displayed in the corresponding table automatically. Section
Precondit ions 165 below shows in detail what you need to get system information.
Note: System information is not supported by the Enterprise Console
web interface 108 to access the system information of a device.
2938
. Please use the PRTG
Note: System information for your devices only has information purposes. We cannot
guarantee that the display in PRTG fully corresponds to the device parameters.
Sy stem Information Tab on a Windows Dev ic e (Snippet)
164
28.04.2016
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
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 324 (or inherited 89 ): 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 automatic.
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 automatic.
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 3005 and the Knowledge Base article General
Int roduct ion t o WMI and PRTG.
SNMP on target computer: Configure Simple Network Management Protocol (SNMP) on the
target computer. For more details, see manual section Monit oring via SNMP 3001 and the
Knowledge Base article General Int roduct ion t o SNMP and PRTG.
Usually you will see data for a system information table after a few minutes, depending on the
used protocols (WMI takes longer than SNMP). A system information table will show an
according error message if PRTG cannot get data for a table because of misconfiguration. For
details about these messages, please see the Knowledge Base article How can PRTG get
dat a for Sy st em Informat ion t ables?
Note: To show information data, you need to enable Sy st em Informat ion in section
Advanced Net work Monit oring 345 in the device settings (or inherit it from an object higher
in the hierarchy 89 ). This is the default setting. If system information is disabled, the Sy st em
Informat ion tab will not be available for the device.
28.04.2016
165
No Data Av ailable: Chec k the Prec onditions
System Information (Device Tab)

Tabs Bar on Dev ic e Lev el
On the details page of a device, click the Sy st em Informat ion tab to show several tables with
information about this device. Each table contains information about one category.
SYSTEM INFOR MATION

System
Shows information about the device like BIOS serial number, IP

addresses, MAC addresses.
Hardware
Shows hardware connected to the device like disk drives, CD/

DVD, video controllers, processors, network adapters, sound
devices, printers, and memory. You can see Class and Capt ion of a
hardware device. In the Propert ies column you can get more
information about the hardware (for example, the description).
Software
Shows installed software and the Version number on the device.

In the Propert ies column you can get more information about the
software (for example, the size).
166
28.04.2016
SYSTEM INFOR MATION

Note: PRTG uses Uninstall registry keys to retrieve the list of
installed software, so the displayed software might differ from the
software which the target Windows system shows under Programs
and Features.
Users
Shows the user accounts connected to the device and their

Domain.
Services
Shows the available Windows services on the device. This table

shows the St at e of the service (running, stopped) and the start
type (St art mode automatic, manual, or disabled). In the 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 as

listed on the Processes tab of the Windows Task Manager. You can
also see the St art Time and Process ID of a process.
Click the refresh button in the upper right corner of a table to retrieve current information for
this system information category. The timestamp shows the passed time since the last table
refresh. The tables Users, Services, and Processes refresh automatically each time you open
the Sy st em Informat ion tab. The tables Sy st em, Hardware, and Soft ware perform no
automatic refresh, so you have to request new information data manually with the refresh
button. PRTG also updates all system information tables with a restart of the PRTG server.
Table Refresh
You can sort each table by clicking the column headers. Please see Working wit h Table List s
178 section for more information.
Data Storage
PRTG stores data files with the retrieved system information in the \Sy st em Informat ion
Dat abase subfolder of the PRTG data folder 3135 under the according categories. Please note
that if you delete a device in PRTG, the system information files of this device will remain here
unless you delete them manually from the folder.
The PRTG uses following subfolders for system information data.
SYSTEM INFOR MATION DATABASE: DATA FOLDER S

hardware
28.04.2016
Data for the Hardware table
167
SYSTEM INFOR MATION DATABASE: DATA FOLDER S

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
Knowledge Base: General Introduction to SNMP and PRTG
168
28.04.2016
Part 5: Ajax Web InterfaceBasic Procedures | 14 Logs
5.14
Logs
The Logs list shows all past activities and events of your PRTG monitoring setup. This is useful
to keep track of all important activities and, for example, to check whether messages were
sent. In a typical setup, a huge amount of data is produced here. As the activity of every single
object is minuted, you can use this data to check exactly if your setup works as expected.
To support you when viewing the log files, there are several filters available. Please see
Working wit h Table List s 178 section for more information.
List with Log Entries
There are two options to call 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 entry in the main menu.
Log (Object Tab)

Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you can
navigate through various sub-pages of an object in order to show your network's status, view
monitoring results, or change settings.
Tabs Bar on Group and Probe Lev el
On an object's detail view, click on the Log tab to show a table list with all log information on
this object. This is a more detailed log than the system log available via the Logs | All option in
main menu 210 .
Logs (Main Menu)

Click the Logs entry from the main menu 210 to show a table list of all system log entries in
your configuration. Hover over the Logs entry and select another option to only show a
subset of entries for certain objects for certain kind of entries. Choose between:
11.03.2016
169
Part 5: Ajax Web InterfaceBasic Procedures | 14 Logs
LOGS
All
Open a table list 178 with log information for all objects in your
configuration, newest first.
By Group
Open a list with log information for objects in a certain group only,
newest first. Hover over By Group to show other menu items.
Select All, or follow the menu path (it is specific to your setup) to
select a group you would like to show log information for.
St at us Changes
Open a list with log information for certain status changes only.
Hover 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 Set up, Not ificat ions,
Schedules, User Account s, User Groups, Report s, Libraries, or
Maps.
Note: You can open a specific tab directly with the context button
Hist ory in the page header bar 126 on the corresponding pages.
170
11.03.2016
Part 5: Ajax Web InterfaceBasic Procedures | 15 Tickets
5.15
Tickets
PRTG Network Monitor includes its own ticket system. With tickets you can manage and
maintain various issues which may appear while monitoring a network. A ticket in PRTG
contains information about recent events in your PRTG installation which need a closer look by
the administrator or another responsible person. You can see each ticket as a task for a
particular PRTG user.
Each monitoring related task has a lifecycle in the ticket system. PRTG itself can create tickets,
for example, when Aut o-Discovery 219 has finished, as well as PRTG users can create tickets
for every kind of issue. In addition, you can set up notifications which open a ticket when
something uncommon occurs in your network. The task gets alive when a ticket is created.
Responsible PRTG users then take care of this issue. Once the issue has been resolved, the
ticket can be closed and the lifecycle of the task ends.
Every ticket has a unique ID, a priority, and a status, and you can take several actions on each
ticket. You should view every ticket and conduct a corresponding action. This way, you always
keep an overview about each task and its history in your PRTG installation.
PRTG can also send an email to you whenever there is a ticket assigned to you or one of your
tickets has been changed. See section Ticket s as Emails 175 for details and how to turn off
emails about tickets.
List of Tic kets
21.01.2016
171
Note: You can turn off the tickets system for particular user groups in Sy st em Administ rat ion
User Groups 2896 except for the PRTG Administrators group. The users in the admin group will
not receive new ToDo tickets (and notifications about changes) by default but only the PRTG
System Administrator user. You cannot change this behavior. However, you can turn off ticket
emails 175 for every user account.
Types of Tickets
New tickets are created in the following cases:
New devices or sensors have been created by the auto-discovery process. Note: In the
corresponding ticket, only device templates will be listed through which PRTG created
sensors.
A new probe connects to the core and must be acknowledged.
A new cluster node connects to the cluster and must be acknowledged.
A new version of the software is available.
A new report is ready for review.
In a few other situations, such as when the system runs out of disk space, for licensing
issues, when an error occurred, etc.
A notification
2759
opened a ticket if set in the notification settings.
A user opened a ticket.

Overall, there are three types of tickets:
User Ticket s: Tickets created by PRTG users, for example, to assign monitoring related tasks
to a particular PRTG user (or user group)
ToDo Ticket s: Tickets created by PRTG to show important system information and in case of
specific system events. They are assigned to the PRTG System Administrator user and cannot
be turned off.
Note: The Relat ed Object of ToDo tickets is Sy st em.
Not ificat ion Ticket s: Tickets created via Not ificat ions
2759
in case of monitoring alerts
States of Tickets
Tickets can have three different states depending on the working process regarding the
corresponding issue:
Open: New tickets will be open as long as the corresponding issue exists as described in
the ticket.
Resolved: The issue as described in the ticket does not persist any longer. Someone took
care of it.
Closed: Usually, the ticket has been resolved before, the solution to the issue has been
checked for correctness, and the ticket does not require any other action.
172
21.01.2016
Tickets (Main Menu)

Note: This option is only shown in the main menu bar if the user group of the current user is
allowed to use the ticket system. You can turn off tickets for particular user groups in Sy st em
Administ rat ionUser Groups 2896 . Users with read-only rights are always excluded from the
ticket system and cannot see the tickets entry in the main menu bar.
You have several options to display a list of tickets which is filtered to your needs. In the main
menu bar 200 , 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 which 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 172 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
21.01.2016
173
All
Open Ticket
This will open the New Ticket dialog. In the first step, select the object on which you want
to focus in the ticket via the Object Select or 181 . Click on Cont inue. Note: You can leave
this step out when using the context menu 186 of this object in the device tree to open the
ticket.
In step 2, provide the following information and confirm by clicking on Save to create a User
Ticket:
Subject : Enter a meaningful title for the ticket which indicates the topic of the issue.
Assigned t o: Select a user (or user group) who will be responsible for this issue from the
drop down list.
Priorit y : Define a priority
182
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 178 .
Additionally, you have several search options using the inline filter directly above the table. The
following filters are available:
Ticket st at us: all, open, resolved, closed
Ticket t y pe: User, ToDo, Notification
Concerned user(s): Show only tickets which are assigned to a specific user or user group.
There are the following types:
any one: no user filter is applied so all tickets on this PRTG server are shown
me: show tickets which are assigned to you (the user who is currently logged in)
Groups: show tickets which are assigned to a specific user group only
Users: show tickets which are assigned to a specific user only
Disallowed: users or user groups which do not have access rights to the selected object
are displayed under Disallowed. This for your information only; you cannot select them!
Relat ionship to a monitoring object: Choose groups, probes, devices, sensors with the
Object Select or 181 .
Note: ToDo tickets are related to Sy st em.
Time span to view tickets by last edit of a ticket: Use the date time picker to enter the date
and time.
Click on the subject of a ticket to open the ticket's detail page. There you can find all related
information, as well as you can conduct several actions.
174
21.01.2016
An Open ToDo Tic ket with Instruc tions
Actions
For best experience with PRTG, check every ticket and select appropriate actions. Note: Only
members of user groups which have the corresponding access rights 101 can view and edit to
tickets which are related to a certain monitoring object.
The following actions are available when viewing the tickets list or a specific ticket:
Edit : Opens a dialog where you can change the subject and the priority of the ticket, as well
as you can assign the ticket to another user. Furthermore, you can add a text message to
this ticket. Confirm your changes by clicking on Save.
Assign: Opens a dialog in which you can give the ticket to another user. Select a user (or
user group) via the drop down menu. Furthermore, you can add a text message to this
ticket. Confirm your assignment by clicking on Save.
Resolve: Opens a dialog where you can resolve the ticket by clicking on Save. The status
resolved indicates that the issue as described in this ticket does not persist. Furthermore,
you can add a text message to this ticket which indicates, for example, what has been done
concerning the issue.
Close: Opens a dialog where you can close the ticket by clicking on Save. Usually, this ticket
has been resolved before and the correct solution of the issue has been checked.
Furthermore, you can add a text message to this ticket.
Reopen: Opens a dialog where you can reopen a ticket after it has been resolved or closed.
Do so, for example, if the solution of the issue turned out to be incorrect. Furthermore, you
can add a text message to this ticket which indicates, for example, why you have opened
the ticket again. Confirm reopening and assignment by clicking on Save.
Tickets as Emails
You can receive all tickets which are assigned to you or to your user group as emails. You will
be also notified each time this ticket is edited via email. This way, you will keep always
informed about new notifications (if set), important system information (if PRTG System
Administrator), or within the communication with other PRTG users. You can turn off the
setting Ticket s as Emails in Sy st em Administ rat ionUser Account s 2890 . If you disable
emails for tickets for a user account, this particular user will not receive any ticket emails
anymore.
21.01.2016
175
Note: If you have defined to get tickets as emails and you are PRTG System Administrator, you
will receive emails for ToDo tickets as well, although ToDo tickets are considered to be
opened by the PRTG System Administrator.
More
Paessler Blog: A New Feature Was Assigned to You in PRTG: Ticket System Keeps Track of
Network Monitoring Issues
https://www.paessler.com/blog/2014/02/03/prtg/ticket-system-keeps-track-of-networkmonitoring-issues
Ajax Web InterfaceBasic ProceduresTopics

Login
110
SSL Cert ificat e Warning

Welcome Page
117
Cust omer Service

General Lay out
Sensor St at es
113
121
123
135

Compare Sensors
143

Similar Sensors
146
151
Recommended Sensors
Object Set t ings
Alarms
155
159
161
Sy st em Informat ion
Logs
164
169
Ticket s
171

Object Select or
182
185
Cont ext Menus

Hover Popup
186
199
Main Menu St ruct ure
176
178
181
Priorit y and Favorit es

Pause
137
200
21.01.2016

218
2732
Related Topics
Ent erprise Console
2938
21.01.2016
2990
177
Part 5: Ajax Web InterfaceBasic Procedures | 16 Working with Table Lists
5.16
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 2770 , Maps 2810 , Report s 2786
, Not ificat ions 2759 , and Schedules 2856 , as well as in Logs 169 and Ticket s 171 . All these provide
common functionality. Depending on the type of content in the list, tables show various
information in their columns for each object.
On certain overview pages, such as for sensors 205 , tickets 173 , and similar sensors 153 , there is
also an inline filter available directly above the table. The filter options depend on the current
page.
Example of a Table List
178
21.01.2016
FE DISPLAY
AT
U
RE
WHAT IT DOES
Pa
gin
g
The content of a table

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

symbol at the
beginning or the end
of a list to open the
table in a new
window.
Da
te
Ra
ng
e
Use the date time

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

(not available in other
lists), point to the
Select Range option
at the upper right
corner of the list to
select the time span
you want to show log
entries for. Choose
between Today ,
Yest erday , and
several other time
spans. Choose
Unlimit ed to disable
this filter again.
21.01.2016
Ite
ms
Point to the It ems

option at the
beginning or end of
179
Related Topics
Mult i-Edit List s
180
2742
21.01.2016
Part 5: Ajax Web InterfaceBasic Procedures | 17 Object Selector
5.17
Object Selector
For some functions, the object selector is shown. It enables you to browse all objects in your
configuration and select an object in two steps.
Objec t Selec tor
Step 1: Navigate Device Tree

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

If you have selected a device on the left hand side, you will see the sensors on this device
here, on the right hand side. Also, the sensor type is shown. Hover over a sensor on the right
side to view its parent device and group.
You can also directly search and find sensors by entering its sensor name, group name, device
name, or tag into the Find... box above the sensor list.
Select an object and click on the Save button.
24.03.2015
181
Part 5: Ajax Web InterfaceBasic Procedures | 18 Priority and Favorites
5.18
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.
Note: Settings for priority and favorites are stored for the entire installation. They are not user
specific.
Priority for All Objects

The priority setting affects in which order your objects are displayed when you view table lists.
PRTG lists objects with a higher priority first, others underneath, depending on their own
priority. Furthermore, device overview pages display gauges 137 for sensors with a high
priority.
To change priority settings, right-click an object to open the context menu 186 and select
Priorit y . You can choose between 5 stars ***** (top priority) and one star * (lowest priority).
By default, all objects are set to medium priority (3 stars ***). In the page header bar and in
lists, you can set a priority directly by one click on a star, for example, for sensors on a device
overview page.
Context Menu: Priority
Note: Select 4 or 5 stars for particular sensors to activate their gauges on device overview
pages.
Note: Select 5 stars for a map to show it as an entry in the main menu
200
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 on it to
open the context menu 186 . Select Priorit y /Favorit e | Add t o Favorit es. A small black flag
symbol will be added next to the object's name.
182
21.01.2016
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 186 .
Context Menu:
Priority /Fav orites (Remov e)
There is also the option to add a device or sensor to favorites by one click in the device tree.
Just click on the small flag symbol right to the respective object name for this concern. If the
flag is black, the specific object is already a favorite; clicking anew on the flag will remove it
from favorites and the flag will turn gray again.
One-Clic k Adding to Fav orites in the Dev ic e Tree
21.01.2016
183
Priority and Favorites in the Page Header Bar

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

If you pause monitoring for an object in the device tree 123 , all child objects underneath will be
paused as well. For example, when pausing a group, all sensors on all devices in it will also be
paused. Once an object is paused, you can resume monitoring any time by selecting Resume
from the context menu 186 . However, you cannot resume monitoring for single child objects
that are paused by a parent object, but only for the object you originally set to pause. Note:
Also after a restart of PRTG, a pause status will be kept.
24.03.2015
185
Part 5: Ajax Web InterfaceBasic Procedures | 20 Context Menus
5.20
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 200 or the hover popup 199 window. However, using the context menus is the easier way
in most cases.
Note: To view your browser's context menu, hold down the Ctrl key (Chrome) or the Shift key
(Firefox) while right-clicking. You will then see the menu of your browser instead of the PRTG
menu. This is not possible with Internet Explorer.
The content of the PRTG context menu varies, depending on the type of object you have
selected. Please see the following sub sections for an overview of the available options.
Probe Cont ext Menu
186
Group Cont ext Menu
190
Device Cont ext Menu
192
Sensor Cont ext Menu
196
Probe Context Menu

The Probe Menu contains actions for your local probe, remote probes, or mini probes
90 .
Probe Context Menu
186
26.01.2016
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
89 .
Det ails...
Show the overview tab
Edit
Hover over Edit to show the Edit menu.
137
of the selected probe.
Edit Menu
The following actions are available:

Set t ings...
Open the Probe Set t ings
Not ificat ions...
Open the Not ificat ions
278
2759
tab of this probe.
tab of this probe.
Access Right s...

Open an assistant to edit User Access Right s
probe.
101
for this
Rename...
Open an assistant to edit the name of this probe.
Management ...
Open the Management
258
tab of this probe.
Add Group...
Open an assistant which guides you through the process of adding

a new group to the selected probe. For detailed instructions,
please see Add a Group 237 .
Add Aut o-Discovery

Group...

a new auto-discovery group to the selected probe. PRTG creates a
new group and runs an auto-discovery in your network to add
devices and sensors automatically. For more information, please
see section Using t he Aut o-Discovery 219 .
Add Device...
Open an assistant which guides you through adding a new device

to the selected probe. For detailed instructions, please see Add a
Device 244 .
26.01.2016
187
PR OBE MENU
Sort Alphabet ically
Sort direct children (groups and devices) of the selected probe in

alphabetical order.
Note: The ordering is stored in the monitoring configuration and
cannot be revoked.
Delet e...
Delete the selected probe. PRTG will ask for confirmation before
anything is actually deleted.
Move
Hover 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
258
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
Pause Menu
188
26.01.2016
PR OBE MENU
You can pause and resume monitoring on the selected probe. The
monitoring for all sensors in the object hierarchy 89 underneath
will be paused resp. resumed.
You can choose between: Pause Indefinit ely ..., pause For 5
Minut es..., For 15 Minut es..., For 1 Hour..., For 3 Hours..., For 1
Day ..., or Pause Unt il.... If you choose Pause Unt il..., an assistant
appears where you can define a date. Use the date time picker to
enter the date and time. PRTG will resume monitoring after this
date.
You can directly add a One-t ime maint enance window to pause
monitoring during a planned downtime. In the appearing assistant,
define the start and end date of the maintenance window for this
probe. Use the date time picker to enter the date and time.
Priorit y
Hover over Priorit y to open the Priorit y menu.
Context Menu Priority
Define the priority of the selected probe. For details, please see
Hist oric Dat a
Hover over Hist oric Dat a to open the Hist oric Dat a menu.
Context Menu Historic

Data

Open the historic data report tabs for the specified interval
Last 2 day s..., Last 30 day s..., or Last 365 day s...
139
Creat e Report ...: Open an assistant to add a new report to

PRTG. For details, please see Report s St ep by St ep 2790 .
26.01.2016
189
PR OBE MENU
Send Link by Email
Send the link to the selected probe by email. Click to create a new
email using your system's standard email client. It contains a direct
link to the overview tab 137 of the selected probe.
Open Ticket
Open the New Ticket dialog. For details, please see the section
Ticket s 174 .
Group Context Menu

The Group Menu contains actions for your groups
90 .
Note: The context menu of the Root group is special and differs from the other groups' menu.
GR OU P MENU
Check Now
Perform an immediate scan for the selected group. This queries the
data for all devices and sensors underneath in the object hierarchy
89 .
Det ails...
Edit
Hover over Edit to show the Edit menu. The following actions are
available:
137
of the selected group.
Set t ings...
Open the Group Set t ings
Not ificat ions...
2759
299
tab of this group.
tab of this group.
Access Right s...

group.
101
for this
Rename...
Open an assistant to edit the name of this group.
Management ...
Open the Management
Add Group...
190
258
tab of this group.

a new group to the selected group. For detailed instructions,
please see Add a Group 237 .
26.01.2016
GR OU P MENU
Add Aut o-Discovery
Group...

a new auto-discovery group to the selected group. PRTG creates a
new group and runs an auto-discovery in your network to add
devices and sensors automatically. For more information, please
see section Using t he Aut o-Discovery 219 .
Add Device...
Open an assistant which guides you through adding a new device

to the selected group. For detailed instructions, please see Add a
Device 244 .
Aut o Discovery
This option is only available for auto-discovery groups. These are

groups with automatic device identification or sensor creation
enabled 300 . Point on 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 is running in the background. If found, you see new
devices with sensors after a few minutes (if found). For more
information, please see Aut o-Discovery 220 (Run Aut oDiscovery Now).
Run Aut o-Discovery wit h Templat e: Open an assistant 222 to
start an automatic search with a desired device template.
Sort direct children (groups and devices) of the selected group in

alphabetical order.
cannot be revoked.
Delet e...
Delete the selected group. PRTG will ask for confirmation before
Clone...
Open an assistant which guides you through cloning the selected

group. For detailed instructions, please see Clone Object 2740 .
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.
26.01.2016
191
GR OU P MENU
To Ot her Group...: Move the group to another group to
become a sub-group.
Management ...: Open the Management
258
tab of the group.
Pause
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 89 underneath
will be paused resp. resumed.
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. For details, please see Priorit y and
Favorit es 182 .
Hist oric Dat a
Hover over Hist oric Dat a to open the Hist oric Dat a menu. The
139

Send Link by Email
Send the link to the selected group by email. Click to create a new
link to the overview tab 137 of the selected group.
Open Ticket
Open the New Ticket dialog. For details, please see section
Ticket s 174 .
Device Context Menu

The Device Menu contains actions for your devices
192
91 .
26.01.2016
DEVICE MENU
Check Now
Perform an immediate scan for the selected device. This queries

the data for all sensors underneath in the object hierarchy 89 .
Det ails...
Edit
available:
137
of the selected device.
Set t ings...
Open the Device Set t ings
324
Not ificat ions...

tab of this device.
2759
tab of this device.
Access Right s...

device.
101
for this
Rename...
Open an assistant to edit the name of this device. You can also
select another device icon.
Add Sensor...
Open an assistant which guides you through adding a new sensor

to the selected device. For detailed instructions, please see Add a
Sensor 256 .
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 is running in the background. If found, you see new
sensors on this device after a few minutes. For more information,
please see Aut o-Discovery 220 (Run Aut o-Discovery Now).
Run Aut o-Discovery wit h Templat e: Open an assistant 221 to
start an automatic search with a desired device template.
Creat e Device
Templat e...
Open an assistant which guides you through creating a new device

template. The template is then available in auto-discovery 219 . For
detailed instructions, please see Creat e Device Templat e 2747 .
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
137 where you can add the according sensor types directly.
Note: This option is only available if the recommendation engine is
enabled 2874 .
26.01.2016
193
DEVICE MENU
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
Clone...

device. For detailed instructions, please see Clone Object 2740 .
Move
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.
Pause
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 resp.
resumed.
date.
device. Use the date time picker to enter the date and time.
Priorit y /Favorit e
194
Hover over Priorit y /Favorit e to open the Priorit y /Favorit e

menu. Define the priority of the selected device or add to resp.
remove it from the favorite devices list. For details, please see
26.01.2016
DEVICE MENU
Hist oric Dat a
139

Device Tools
Hover over Device Tools to open the Device Tools menu.
Context Menu Dev ic e Tools

Go To Service URL...
Open the service page that you have defined in the Device
Set t ings 324 . If there is no service URL available for this device,
you can enter an address in the appearing assistant.
New window wit h HTTP...
Open a new browser window with Hypertext Transfer Protocol
(HTTP) and the IP address / DNS name of the device.
New window wit h HTTPS...
Open a new browser window with Hypertext Transfer Protocol
Secure (HTTPS) and the IP address / DNS name of the device.
New window wit h FTP...
Open a new browser window with File Transfer Protocol (FTP)
and the IP address / DNS name of the device.
Remot e Deskt op...
Download an .rdp file. When you execute this file, a remote
desktop will start with the IP address / DNS name of the
device.
Note: In Firefox you have to use mstsc.exe (Microsoft Terminal
Service) to open the file.
26.01.2016
195
DEVICE MENU
Tracerout e...
Start a traceroute on the selected device. PRTG will display the
route and measure transit delays of packets across the IP
network.
Inst all Remot e Probe...
Open an assistant to install a Remot e Probe of PRTG on this
device. For more details, please see Remot e Probe Quick
Inst all 3112 .
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 137 of the selected device.
Open Ticket
Ticket s 174 .
Sensor Context Menu

The Sensor Menu contains actions for your sensors
92
SENSOR MENU
Check Now
Perform an immediate scan for the selected sensor.
Det ails...
Edit
available:
137
of the selected sensor.
Set t ings...
Open the Sensor Set t ings
347
Not ificat ions...

tab of this sensor.
2759
tab of this sensor.
Access Right s...

sensor.
196
101
for this
26.01.2016
SENSOR MENU
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 135 .
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 135 ) and will not trigger
more notifications 2759 .
2719
any
You can choose between: Acknowledge Indefinit ely ...,

acknowledge For 5 Minut es..., For 15 Minut es..., For 1 Hour...,
For 3 Hours..., For 1 Day ..., or Unt il.... If you choose Unt il... an
assistant appears where you can define a date. Use the date time
picker to enter the date and time. If the alarm condition still exists
after this date, the sensor will show a Down status again.
Note: If the alarm condition clears, the sensor usually returns into
an Up status immediately with the next sensor scan. For details
about acknowledging an alarm, please see Alarms 162 section.
Delet e...
Delete the selected sensor. PRTG will ask for confirmation before
Clone...

sensor. For detailed instructions, please see Clone Object 2740 .
Move
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.
Pause
or
If the sensor is already in paused status 135 or in Simulat e Error

St at us, Resume appears. Click Resume to restart monitoring on
this sensor.
Resume
You can pause and resume monitoring of the selected sensor.

Choose between: Pause Indefinit ely ..., pause For 5 Minut es...,
For 15 Minut es..., For 1 Hour..., For 3 Hours..., For 1 Day ..., or
Pause Unt il.... If you choose Pause Unt il..., an assistant appears
where you can define a date. Use the date time picker to enter the
date and time. PRTG will resume monitoring after this date.
26.01.2016
197
SENSOR MENU
sensor. Use the date time picker to enter the date and time.
Simulat e Error St at us Set the selected sensor to a Down status 135 . Like for the paused
status, Resume will appear in the context menu if a the selected
sensor is already in a simulated error status.
Note: "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 to resp.
remove it from the favorite devices list. For details, please see
Hist oric Dat a
Open the historic data tab for the specified interval 140 : Live
Dat a..., Last 2 day s..., Last 30 day s..., or Last 365 day s...
Compare...: Open the Compare Sensors
currently selected sensor.
143
assistant with the
View Hist oric Dat a: Open the Hist oric Dat a

sensor.
146
tab of this

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 137 of the selected sensor.
Open Ticket
Ticket s 174 .
198
26.01.2016
Part 5: Ajax Web InterfaceBasic Procedures | 21 Hover Popup
5.21
Hover Popup
Whenever you rest the mouse pointer for a second over an object's icon in the device tree 123 ,
a hover popup window will appear, showing details about this object. It contains information
from the object's overview tab 137 , as well as several graphs. The exact information provided
depends on the kind of object you are hovering over.
Hov er Menu Example: VMware Virtual Mac hine Sensor
Note: The hover popup does only appear if your browser is the currently focused window on
your desktop. It disappears with every (automatic) page refresh.
Menu Icons
At the top of the hover popup window, several icons are shown which enable you to view or
edit the current object. These are the most important options from this object's context menu
186 which is shown when right-clicking it.
24.03.2015
199
Part 5: Ajax Web InterfaceBasic Procedures | 22 Main Menu Structure
5.22
Main Menu Structure
You can access all functions of PRTG using the main menu. In this section, you find descriptions
about the most important menu items. Often, you can either click on an item directly, or hover
over it to show more items.
PRTG Main Menu Bar
The following menu items are available:
Home
200
Devices
202
Libraries
204
Sensors
205
Alarms
Maps
208
209
Reports
Logs
209
210
Tickets
Setup
211
212
Refresh (Arrows Symbol)

Help Center (? Symbol)
Logout (Off Symbol)
Search Box
214
214
215
215
Home
Click to open the user's homepage. The default setting is the PRTG welcome page 123 . You can
change the homepage in the user account settings 2830 . Point to Home to show other menu
items.
200
11.03.2016
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 2810 that PRTG creates automatically with a new
installation.
Note: The Home menu shows maps that have a 5***** priority
You can include up to 10 map entries in this menu.
182
Note: You can change the appearance of the default dashboard

with the Map Designer 2816 . To not show the sample dashboard in
the menu, define a priority 182 lower than 5***** for this map.
Dashboard 1
Dashboard 3
Choose a preconfigured dashboard to view monitoring data in

another layout. Dashboards provide different preset overviews
with the status of your sensors.
Note: These dashboards are not customizable. You can create
your own overview pages using the Maps 2810 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 87 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.
Sit emap
11.03.2016
Open the sitemap which contains a flat text view of all menu items.
You can easily search for key words using the search function in
your browser (usually shortcut CTRL-F).
201
HOME
Go t o Mobile Web GUI Switch to the Mobile Web GUI 2991 which is optimized for low
bandwidth and mobile devices. This interface uses less scripting for
more compatibility.
Note: This is a read-only interface for most parts of PRTG.
Note: This user interface is deprecated. We will completely remove
it from PRTG soon.
Welcome t o PRTG
Open the Welcome Page 117 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.
Note: This is the default homepage of the PRTG web interface.
Make This My
Homepage
Change the page that is loaded when you click on the Home
button in the main menu. Select this command on any page to set
its URL as the current user's homepage. This setting is user
sensitive. The default homepage is /welcome.htm.
You can change this setting any time by clicking on this command
again, or by changing the Homepage URL in the My Account 2830
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
202
11.03.2016
DEVICES
All
Open the Overview tab of the Root 90 group that shows a group
view of all your devices (the device tree).
Group View
Open a tree view of all probes and groups in your setup. Click to
show a group view of all your devices, starting with the Root 90
group which contains all other groups of your setup. Hover over
Group View to show other menu items. Follow the menu path (it is
specific to your setup) to view the devices in a specific probe or
group only.
Device List
Open a list view of all devices in your setup. Click to show a table
list of all devices in your setup. Hover over Device List to show
other menu items. Choose Favorit e Devices to show a list of all
devices marked as Favorit e 182 . Follow the menu path (it is specific
to your setup) to view a table list of the devices in a specific probe
or group only.
Note: In the table list 178 appearing, you can re-sort the items by
clicking on the column's header items.
Note: On device lists, you can use the Print QR-Codes button to
show the QR codes of all devices in this list in a printable layout.
You can change the size of these QR codes by changing the values
of the according parameters width, height, and margin in the URL.
Favorit e Devices
Open a table list of all devices marked as Favorit e 182 . Click on the
Print QR-Codes button to show a printable list of the QR codes of
all your favorite devices.
Note: To mark any device as a favorite device, select Priorit y /
Favorit e | Add t o Favorit es from its context menu or click on the
small flag on a device's details page.
Dependencies
Open an overview list of the Dependencies 98 configured for the

objects in your setup. Hover over the menu item to show other
menu items. Choose between Select ed Dependencies and
Mast er Dependencies to view a list of all dependencies or explicit
ones. You can select dependencies and define master
dependencies in the Schedules, Dependencies, and
Maint enance Windows settings of a monitoring object 159 (not
available for the Root group).
Click on Dependencies Graph 2751 to visualize the dependencies
between objects in your configuration. Follow the menu path (it is
specific to your setup) to view dependencies of the objects in a
specific probe or group only.
11.03.2016
203
DEVICES
Add Group
Start an assistant which guides you through the process of adding

a new group to your setup. For more information, please see
section Creat e Object s Manually 236 .
Note: You can create new groups much faster by choosing Add
Group... from a probe's or group's context menu.
Add Aut o-Discovery

Group

a new auto-discovery group to your setup. PRTG will create a new
group and run an auto-discovery in your network to add devices
and sensors for these devices automatically. For more information,
please see section Using t he Aut o-Discovery 219
Note: You can create new groups much faster by choosing Add
Aut o-Discovery Group... from a probe's or group's context menu.
Add Device

a new device to an existing group. During the process, you can
choose if PRTG will run an auto-discover for the new device to add
sensors automatically. For more information, please see section
Creat e Object s Manually 236 .
Note: You can create new devices much faster by choosing Add
Device... from a group's context menu.
Libraries
Click to open the Libraries overview list where you can view or add custom views of your
network status and monitoring data. For more information, please see Libraries 2770 section.
Hover over Libraries to show other menu items.
PRTG Main Menu: Libraries
LIBR AR IES
All
204
Open the Libraries overview list where you can view or add custom
device tree views of your network status and monitoring data.
11.03.2016
LIBR AR IES
Add Library
Open an assistant to directly create
Select Library
Open an existing library. Hover over Select Library to show other

menu items. Follow the menu path (it is specific to your setup) to
select a library and open it.
2773
a new library.
Sensors
Click to show a table list of all sensors 92 . In the table list 178 appearing, you can re-sort the
items by clicking on the column's header items, as well as you can filter the list by related
object and tag with the inline filter directly above the table. Hover over Sensors in the main
menu bar to show other menu items.
Note: The column Last Value shows only the last value of the sensor's primary channel.
Note: For most sensor lists, you can use Mult i-Edit
one sensor at once.
2742
to change the settings of more than
PRTG Main Menu: Sensors
11.03.2016
205
SENSOR S
All
Open a table list 178 of all sensors 92 . In the table list appearing,
you can re-sort the items by clicking on the column's header
items.
Note: The column Last Value shows only the last value of the
sensor's primary channel.
Add Sensor

a new sensor to an existing device. For more information, please
see section Add a Sensor 256 . During the process, you can also
choose to create a new device via the Add a Device 244 assistant
(that you can also open from the "Devices" menu 202 directly).
Favorit e Sensors
Open a table list of all sensors which you marked as Favorit e
182
Note: To mark any sensor as a favorite sensor, select Priorit y /

Favorit e | Add t o Favorit es from its context menu or click on the
small flag on a device's details page.
Top 10 List s
Open a dashboard view with different top 10 lists which show

best/worst uptime, Ping, bandwidth usage, website response
times, CPU usage, disk usage, memory usage, and system uptime.
Click to show top 10 lists for all sensors. Hover 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.
Note: 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 178 of Fast est or Slowest sensors for
Ping
Port
Webpages
IMAP/POP3/SMTP
FTP
as well as a list of sensors with Most Used or Least Used
Bandwidt h
CPU
Disk
Memory
Note: The shown sensors are selected by default tags.
206
11.03.2016
SENSOR S
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 178 of all sensors in a certain status. For more information
about sensor states, please see Sensor St at es 135 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 178 of all sensors sorted by
Best Upt ime (%)
Highest Upt ime (Time)
Worst Downt ime (%)
Highest Downt ime (Time)
By Group
Open a list of sensors filtered by their parent group. Hover over By

Group to show other menu items. Follow the menu path (it is
specific to your setup) to view a sensor table list 178 of a specific
probe or group only.
By Ty pe
Open a list of sensors filtered by sensor type 348 . 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 178
containing only sensors of one specific sensor type.
By Tag
Open a list of sensors filtered by tag 96 . 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 view a
table list 178 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 182 , scanning interval
272 , access rights 101 , notification trigger settings 159 , schedule 99 ,
and dependency 98 . 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 in a specific probe or group only,
or to view them by type or tag.
Compare Sensors
Compare the data graphs of two or more sensors. Hover over

Compare Sensors to show other menu items. Follow the menu
path to open an assistant for comparing several monitoring
objects. For more information, please see Compare Sensors 143
section.
11.03.2016
207
SENSOR S
View Hist oric Dat a
Open an assistant for a quick generation of sensor data reports.

For more information, please see Hist oric Dat a Report s 146
section.
Similar Sensors
Overview
Open an overview page with a list of "similar sensors". For more

information, please see Similar Sensors 151 section.
Alarms
Click to show a all sensors that currently show a Down, Down (Part ial), Warning, or Unusual
status. In the table list 178 appearing, you can re-sort the items by clicking on the column's
header items. If you select Show as Gauges, this command displays the sensor gauges 137 in a
size corresponding to their priority. Hover over Alarms to show other menu items.
PRTG Main Menu: Alarms
ALAR MS
All

(Part ial), Down (Acknowledged), Warning, or Unusual status
135
Show as Gauges
Open a page with the gauges of all sensors which are currently in
Down, Down (Part ial), Down (Acknowledged), Warning, or
Unusual status. The size of the sensor gauges corresponds to
their respective priority.
Errors Only

(Part ial), or Down (Acknowledged) status.
Warnings Only
Open a list of all sensors which are currently in Warning status.
Unusuals Only
Open a list of all sensors which are currently in Unusual status.
208
11.03.2016
Maps
Click to open the Maps overview page where you can view or add custom views of your
network status and monitoring data. For more information, please see Maps 2810 section. Hover
over Maps to show other menu items.
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
Select Map
Open an existing map. Hover over Select Map to show other

select a map.
2814
a new map.
Reports
Click to open the Reports overview page where you can view or add reports of your
monitoring data. For more information, please see Report s 2786 section. Hover over Report s to
show other menu items.
PRTG Main Menu: Reports
R EPOR TS
All
11.03.2016
Open the Reports overview page where you can view or add
reports of your monitoring data.
209
R EPOR TS
Add Report
Select Report
Open an existing report. Point on Select Report to show other

select a report.
Configurat ion
Report s
Create reports for maps, reports, users & user groups, and system
configuration to document changes to the configuration. Point on
Report s | Configurat ion Report s to see the available
configuration reports 2789 .
2790
a new report.
Logs
Click to show log information for all objects in your configuration, newest first. In the table list
178 appearing, you can filter the items by using the respective options 178 . Hover over Logs to
show other menu items. For more information, please see Logs 169 section.
Note: Logs for monitoring objects (for example, sensors) are available as long as you define
for Logfile Records in the Hist oric Dat a Purging settings under Sy st em Administ rat ion
Core & Probes 2887 .
PRTG Main Menu: Logs
LOGS
All
Open a table list 178 with log information for all objects in your
configuration, newest first.
By Group
Open a list with log information for objects in a certain group only,
newest first. Hover over By Group to show other menu items.
Select All, or follow the menu path (it is specific to your setup) to
select a group you would like to show log information for.
210
11.03.2016
LOGS
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 Set up, Not ificat ions,
Schedules, User Account s, User Groups, Report s, Libraries, or
Maps.
Note: You can open a specific tab directly with the context button
Hist ory in the page header bar 126 on the corresponding pages.
Tickets
Click to show all tickets which are assigned to the current user. In the table list 178 appearing,
you can re-sort the items by clicking on the column's header items, as well as you can filter the
list with the inline filter directly above the table. Hover over Ticket s to show other menu
items.
Tickets show important system information or action steps to take for the administrator. For
best experience with PRTG, check every ticket and conduct appropriate actions. For more
information, please see section Ticket s 171 .
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.
11.03.2016
211
TICKETS
All
Open a list of all open tickets which are assigned to the current
user.
My Ticket s
Open a list of all open tickets which are assigned to the current
user. Hover 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 on Save to create a User Ticket . For more
information about available options, please refer to section
Ticket s 171 .
Setup
Click to show the setup page. Hover over Set up to show other menu items. For more
information, please see Set up 2828 section.
PRTG Main Menu: Setup
SETU P
Overview
212
Open the setup page
2828
11.03.2016
SETU P
Account Set t ings
Open the My Account 2830 settings. Hover over Account Set t ings
to show and open the tabs of account settings directly. Choose
from:
My Account
2830
Not ificat ions
2836
Not ificat ion Cont act s

Schedules
Sy st em
Administ rat ion
2856
Open the Sy st em Administ rat ion 2860 settings. Hover over

Sy st em Administ rat ion to show and open the tabs of the system
administration settings directly. Choose from:
User Int erface
Monit oring
2860
2871
Not ificat ion Delivery

Core & Probes
Clust er
User Groups
2883
2890
2896
Administ rat ive Tools
License
2877
2905
User Account s
PRTG St at us
2852
2900
Open the PRTG St at usSy st em St at us 2907 page. When running a

cluster, hover over PRTG St at us to show other menu items.
Choose from:
Sy st em St at us
2907
Clust er St at us
2923
Open the license act ivat ion st at us 2925 page. Hover over License
to show other menu items. Choose from:
St at us
2925
to view information about your license.
Ent er License Key 2926 to enter your license name and key and
to show your licensed PRTG edition.
Aut o-Updat e
11.03.2016
Open information about the Soft ware Aut o-Updat e 2918 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:
213
SETU P
St at us 2918 to view the update status and to manually check for
the latest update.
Set t ings
Downloads
2920
to define your update settings.
Open the downloads page

Choose from:
2928
of PRTG for additional downloads.
Client App for Windows (Ent erprise Console)

Client Apps for Mobile Devices
Remot e Probe Inst aller
PRTG Tools
2928
2928
2928
2928
Deskt op Not ificat ions
2930
PRTG API
Open the documentation of the Applicat ion Programming

Int erface (API) Definit ion 3086 for your installation.
Cont act Support
Open the Cont act Paessler Support / Send Your Feedback t o

Paessler 2932 form.
Refresh (Arrows Symbol)
PRTG Main Menu: Refresh Button
Click this symbol to refresh all elements on the current page to display current data. Unlike the
reload function of your browser, this merely refreshes the single page elements, not the whole
page.
Help Center (? Symbol)
PRTG Main Menu: Help Button
Open the Help and Support Cent er to get help if you have any questions regarding your
PRTG setup.
214
11.03.2016
Logout (Off Symbol)
PRTG Main Menu: Logout Button
Log out the current user and return to the login screen
110
Search Box
Use the search box to find objects and reports, and other items by name or tag, or to search
for help. Click into the field to enlarge it.
Context Menu
Additionally, there are Cont ext Menus
open it.
11.03.2016
186
available for all objects. Right-click on an object to
215
Part 6
Ajax Web InterfaceDevice and Sensor Setup
24.03.2015
217
Part 6: Ajax Web InterfaceDevice and Sensor Setup |
Ajax Web InterfaceDevice and Sensor

Setup
The following sections introduce device and sensor setup in the Ajax Graphical User Interface
(GUI).
Ajax Web InterfaceDevice and Sensor SetupTopics

Aut o-Discovery
219
Creat e Object s Manually

Manage Device Tree
258
Root Group Set t ings

Probe Set t ings
236
260
278
Group Set t ings
299
Device Set t ings
324
Sensor Set t ings
347
List of Available Sensor Ty pes
Addit ional Sensor Ty pes (Cust om Sensors)

Sensor Channels Set t ings
348
2707
2711
Sensor Not ificat ions Set t ings
2719

Ajax Web Int erfaceBasic Procedures
108
2732
Related Topics
Ent erprise Console
2938
218
2990
24.03.2015
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 1 Auto-Discovery
6.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. For video instructions, please see the More 235 section below.
Note: PRTG already runs a quick initial auto-discovery as soon as you finished the install 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 2747 section).
You can use the auto-discovery on group level for a range of IP addresses, or for individual
devices which 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 autodiscovery daily or weekly on group level automatically creates new devices when they are
connected to the network and adds according sensors. As soon as PRTG discovers new
devices or sensors, it will create notifying Ticket s 171 (which are mailed to the PRTG system
administrator user by default).
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 260 .
If a device has more than one IP address, it may show up more than once in the discovery
results, even though PRTG tries to identify these situations.
If a device already exists on the same probe, the auto-discovery will skip this device and not
create a duplicate.
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.
25.04.2016
219
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 the More 235 section below.
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.
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. PRTG immediately
starts searching for new objects which can be added to the device tree. If you use it for an
auto-discovery group, 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 126 when PRTG run the last auto-discovery on a selected group or device.
Note: The auto-discovery will also re-add devices or sensors you have manually deleted. If you
do not want this, please create objects manually 236 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. 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 186 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.
220
25.04.2016
Add Auto-Disc ov ery Group Dialog
St ep 1
Please choose a probe or group you want to add the new group to. Click Cont inue.
St ep 2
Add auto-discovery settings as described below.
Add Auto-Discovery Group Settings

GR OU P NAME AND TAGS
Group Name
Enter a meaningful name to identify the group. The name will be

shown by default in the devices tree and in all alarms.
Tags
Enter one or more tags. Confirm each tag by hitting the space,
comma, or enter key. You can use tags to group objects and use
tag-filtered views later on. Tags are not case sensitive. Tags are
automatically inherited 96 .
25.04.2016
221
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 autodiscovery. 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 autodiscovery. 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
Cisco ASA VPN
Cisco Device (Generic)
Dell MDI Disk
DNS Server
Environment Jacart a
Environment Poseidon
Frit zbox
FTP Server
Generic Device (PING only )
Generic Device (SNMP-enabled)
Generic Device (SNMP-enabled, Det ailed)
HTTP Web Server
Hy per V Host Server
222
25.04.2016
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)
Sever Cisco UCS
Server IBM
SonicWALL
SSL Securit y Check
Swit ch (Cisco Cat aly st )
Swit ch (Cisco IOS Based)
Swit ch (HP Procurve)
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
VMware ESX / vCent er Server
Webserver
Windows (Det ailed via WMI)
Windows (via Remot e Powershell)
Windows (via WMI)
Windows IIS (via SNMP)
X EN Host s
25.04.2016
223
X EN Virt ual Machines

Once the auto-discovery is finished, PRTG will create a new ticket
171 and list the device templates which it used to create new
sensors. The ticket will not show templates which 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. You can run auto-discovery manually
any time using an object's context menu 186 .
Hourly : Perform auto-discovery for new devices and sensors
every 60 minutes.
Note: Please use this option with caution! Frequently executed
auto-discoveries might cause performance issues, especially
when large network segments are scanned every hour.
Daily : Perform auto-discovery for new devices and sensors
every 24 hours. The first auto-discovery will run immediately, all
other discoveries will start on the time defined in the Aut oDiscovery Set t ings section of the Sy st em Administ rat ion
Monit oring 2875 settings.
Weekly : Perform auto-discovery for new devices and sensors
every 7 days. The first auto-discovery will run immediately, all
IP Selection Method
Define how you want to define the IP range for auto-discovery.

Choose between:
Class C base IP wit h st art /end (IPv4): Define an IPv4 class C
address range.
List of individual IPs and DNS names (IPv4): Enter a list of
individual IPv4 addresses or DNS names.
IP and Subnet (IPv4): Enter an IPv4 address and subnet mask.
IP wit h oct et range (IPv4): Enter an IPv4 address range for every
IP octet individually. With this, you can define very customizable
IP ranges.
Use comput ers from t he act ive direct ory (maximum 1000
comput ers): Search in the active directory for computers to
perform auto-discovery.
Note: Define your active directory domain in advance in the
system administration. See Sy st em Administ rat ionCore &
Probes 2887 .
224
25.04.2016
Note: Only subnets with up to 65,536 IP addresses can be

discovered! If you define a range with a higher number of
addresses, discovery will stop before it is completed.
IPv4 Base
This field is only visible if 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

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

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

IPv6/DNS Name List
This field is only visible if you select the IP list option above. Enter a
list of IP addresses or DNS names which the auto-discovery will
scan. Enter each address in a separate line.
IPv4 and Subnet (IPv4)
This field is only visible if 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 which 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.
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:
25.04.2016
225
Assuming that the organizational unit 'Y' is part of the OU named

'X'. Then the syntax would be Y,OU=X
For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would
be Z,OU=Y,OU=X
Note: The order is important, sub-OUs have to be listed left of their
particular parents!
Name Resolution
Define how 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 324 shows the DNS name or IP
address which 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.
Note: This setting does not affect how PRTG shows the devices in
the device tree.
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, but 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, for example, in other
groups also to this group and runs the auto-discovery on the
newly added devices.
Note: The auto-discovery will not run on devices that already
exist. 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 260
group's settings. To change a setting only for this object, disable inheritance by clicking on
the check mark before the corresponding setting name. You will then see the options
described below.
226
25.04.2016
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

Domain or Computer
Name
Define the authority for Windows access. This is used for Windows
Management Instrumentation (WMI) and other Windows sensors. If
you want to use a Windows local user account on the target
device, please enter the computer name here. If you want to use a
Windows domain user account (recommended), please enter the
(Active Directory) domain name here. If not explicitly defined, PRTG
will automatically add a prefix in order to use the NT LAN Manager
(NTLM) protocol. Please do not leave this field empty.
User
Enter the username for Windows access. Usually, you will use
credentials with administrator privileges.
Password
Enter the password for Windows access. Usually, you will use
CR EDENTIALS FOR LINU X/SOLAR IS/MAC OS (SSH/WBEM) SYSTEMS

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.
Note: PRTG can only handle keys in OpenSSH format which 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, please see
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.
25.04.2016
227

Note: If you do not insert a private key for the first time, but
change the private key, you need to restart your PRTG core server
service 2901 in order for the private key change to take effect! For
details, please see Monit oring via SSH 3008 .
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:
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.

Note: By default, PRTG uses this setting automatically for all SSH
sensors 353 , unless you define a different port number in the
sensor settings.
SSH Rights Elevation
Define the rights with which you want 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.
Run t he command as anot her user using 'sudo': Use the rights
of another user, for example, the administrator.
Run t he command as anot her user using 'su': Use the rights of
another target user.
Target User
This field is only visible if you choose sudo or su above. Enter a

username to run the specified command as another user than root.
If you leave this field empty, you will run the command as root.
Ensure that you set the Linux password even if you use a public/
private key for authentication. This is not necessary if the user is
allowed to execute the command without a password.
Password Target User
This field is only visible if you choose su above. Enter the

password for the specified target user.
228
25.04.2016

SSH Engine
Select the method you want to use to access data with SSH
sensors 3008 . We strongly recommend that you keep the default
engine! For some time you still can use the legacy mode to ensure
compatibility with your target systems. Choose between:
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.
Note: You can also individually select the SSH engine for each SSH
sensor in the sensor settings.
CR EDENTIALS FOR VMWAR E/XENSER VER

User
Enter a login name for access to VMware and XEN servers.

Usually, you will use credentials with administrator privileges.
Password
Enter a password for access to VMware and XEN servers. Usually,

Note: Single Sign-On (SSO) passwords for vSphere do not
support special characters. Please 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
25.04.2016
Define if you want to use session pooling for VMware sensors.

Choose between:
229

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

The settings you define in this section apply to the following sensors:
My SQL v2 Sensor
1090

Post greSQL Sensor
For Databases Use
Port
1075
1187
1297
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
230
25.04.2016

Port
Enter the number of the port that PRTG will use for database
connections. Please enter an integer value.
Note: All your database sensors will use this port to connect!
Authentication
Select the authentication method for the connection to the SQL

database. Choose between:
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 329 for the database connection.
Note: The user whose credentials are used needs to have
permissions to log on to the system on which the PRTG probe
with a database sensor runs. This is required for the
impersonation.
SQL server aut hent icat ion: Choose this option if you want to
use explicit credentials for database connections.
User
This field is only visible if you select SQL server authentication

above. Enter the username for the database connection.
Password
This field is only visible if you selected SQL server authentication

above. Enter the password for the database connection.
Timeout (Sec.)
Enter a timeout in seconds for the request. Please enter an integer

value. If the reply takes longer than this value defines, the sensor
cancels the request and triggers an error message. The maximum
timeout value is 300 seconds (5 minutes).
CR EDENTIALS FOR AMAZON CLOU DWATCH

Access Key
Enter your Amazon Web Services (AWS) Access Key. Please see the
corresponding Amazon CloudWatch sensor 354 documentation to
know 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.
25.04.2016
231
CR EDENTIALS FOR SNMP DEVICES

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.
Note: SNMP v1 does not support 64-bit counters which 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.
Note for SNMP v3: Due to internal limitations you can only monitor
a limited number of sensors per second using SNMP v3. The limit is
somewhere between 1 and 50 sensors per second (depending on
the SNMP latency of your network). This means that using an
interval of 60 seconds you are limited to between 60 and 3000
SNMP v3 sensors for each probe. If you experience an increased
"Interval Delay" or "Open Requests" with the Probe Healt h Sensor
1311 , you need to distribute the load over multiple probes. SNMP v1
and v2 do not have this limitation.
Community String
This setting is only visible if 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.
Note: If you do not want to use authentication, but you need SNMP
v3, for example, because your device requires context, you can
leave the field password empty. In this case,
SNMP_SEC_LEVEL_NOAUTH is used and authentication deactivated
entirely.
User
232

Enter a username for secure authentication. This value must match
the username of your device.
25.04.2016

Password

Enter a password for secure authentication. This value must match
the password of your device.
Encryption Type

Select an encryption type. Choose between:
DES: Use Data Encryption Standard (DES) as encryption
algorithm.
AES: Use Advanced Encryption Standard (AES) as encryption
algorithm. Note: AES 192 and AES 256 are not supported by NetSNMP because they lack RFC specification.
The type you choose must match the encryption type of your
device.
Data Encryption Key

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.
Note: 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

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.
25.04.2016
233
PR OXY SETTINGS FOR HTTP SENSOR S

HTTP Proxy Settings
The proxy settings determine how a sensor connects to a given

URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS. Note: This setting is valid for the
monitoring only and determines the behavior of sensors. In order
to change proxy settings for the core server, please see Sy st em
Administ rat ionCore & Probes 2883 .
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. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the

ACCESS R IGHTS
User Group Access
Define which user group(s) will have access to the object that you
are editing. A table with user groups and right is shown; it contains
all user groups from your setup. For each user group you can
choose from the following access rights:
Inherit ed: Use the settings of the parent object.
None: Users in this group cannot see or edit the object. The
object does not show up in lists.
Read: Users in this group can see the object and review its
settings.
Writ e: Users in this group can see the object, as well as review
and edit its settings. However, they cannot edit access rights
settings.
Full: Users in this group can see the object, as well as review
and edit its settings as well as edit access rights.
You can create new user groups in the Sy st em Administ rat ion
User Groups 2896 settings.
Click the Cont inue button to save your settings. If you change tabs or use the main menu, all
changes to the settings will be lost!
234
25.04.2016
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
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 186 . PRTG will pause 185 monitoring for 5 minutes and
stops auto-discovery tasks.
Related Topics
Creat e Device Templat e
2747
More
https://www.paessler.com/support/video_tutorials
Knowledge Base: Why can automatic auto-discoveries evoke performance issues?
25.04.2016
235
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
6.2
Create Objects Manually
We recommend using the auto-discovery 219 function to create a basic monitoring setup for
your network. Afterwards, you can manually create devices that could not be discovered, or
arrange 2739 detected devices in groups.
The procedure depends on the kind of object you want to add. Choose between:
Add a Group
237
Add a Device
244
Add a Sensor
256
Add a Remote Probe

Please see Mult iple Probes and Remot e Probes
236
3108
section for more information.
24.03.2015
1 Add a Group
6.2.1
Add a Group
In order to add a group manually, select Devices | Add Group from the main menu. An
assistant will appear, leading you through two steps. For faster setup, you can select Add
Group... in the context menu 186 of a probe or group to which you want to add the new
group. This will skip step 1 and lead you directly to step 2.
St ep 1
Please choose a probe or group you want to add the new group to. Click on Cont inue.
Add Group Assistant Step 2
St ep 2
Add group settings as described below.
Add Group Settings

GR OU P NAME AND TAGS
Group Name

Tags
Enter one or more tags. Confirm each tag by hitting the space,
tag-filtered views later on. Tags are not case sensitive. Tags are
24.03.2015
237
1 Add a Group

Domain or Computer
Name
User
Password

User
Login

between:
Password
Private Key
238
24.03.2015
1 Add a Group

For WBEM Use Port
WBEM Port

SSH Port

sensor settings.
Target User


SSH Engine
24.03.2015
239
1 Add a Group

default SSH engine.

User

Password

VMware Protocol

XenServers.
Session Pool

Choose between:
240
24.03.2015
1 Add a Group


SNMP Version

between:
Community String

Authentication Type

Choose between:
device.
24.03.2015
241
1 Add a Group

entirely.
User

Password

Encryption Type

algorithm.
device.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (Sec.)

242
24.03.2015
1 Add a Group
ACCESS R IGHTS
User Group Access
settings.
settings.
24.03.2015
243
2 Add a Device
6.2.2
Add a Device
To manually add a device, select Devices | Add Device from the main menu. An assistant will
appear, leading you through two steps. For faster setup, you can select Add Device... in the
context menu 186 of a group to which you want to add the new device. This will skip step 1
and lead you directly to step 2.
St ep 1
Please choose a group you want to add the new device to. Click on Cont inue.
Add Dev ic e Assistant Step 2
St ep 2
Add device settings as described below.
Add Device Settings

DEVICE NAME AND ADDR ESS
Device Name
Enter a meaningful name to identify the device. The name will be

shown by default in the device tree and in all alarms.
IP Version
Define which IP protocol PRTG will use to connect to this device.

The setting is valid for all sensors created on this device. Choose
between:
Connect using IPv4: Use IP version 4 for all requests to this
device.
244
31.08.2015
2 Add a Device
DEVICE NAME AND ADDR ESS

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. Note: There are some sensor types that
still have their own setting for IP address/DNS name. Those
sensors will use their own settings.
Tags
Enter one or more tags; confirm each tag by hitting space, comma,
or enter key. You can use tags to group sensors and use tagfiltered views later on. Tags are not case sensitive. Tags are
Device Icon
Choose a device icon from the list. It will be shown in the device
tree.
DEVICE TYPE
Sensor Management
Select which type of auto-discovery you would like to perform for

this device. Choose between:
Manual (no aut o-discovery ): Do not auto-discover any sensors,
but only add sensors manually.
Use a small set of auto-discovery templates. This will scan your
LAN and usually create a view standard sensors on your device.
sensors): Use an extended set of auto-discovery templates. This
will scan your LAN and usually create many sensors on your
device.
Aut omat ic sensor creat ion using specific device t emplat es:
Use specific auto-discovery templates only. Please select
templates below. This will scan your LAN and add sensors
defined in the template.
Discovery Schedule
This option is only visible if one of the auto-discovery options is

selected above. Define when the auto-discovery will be run.
Choose between:
Once: Perform auto-discovery only once. For existing devices,
this will initiate a one-time sensor update for the current device.
31.08.2015
245
2 Add a Device
DEVICE TYPE
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. Please choose one or more templates by
adding a check mark in front of the respective template name. You
can also select and deselect all items by using the check box in the
table head. These will be used for auto-discovery on the current
device. Choose from:
ADSL
Amazon Cloudwat ch
Cisco ASA VPN
Dell MDI Disk
DNS Server
Frit zbox
FTP Server
HTTP Web Server
NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
246
31.08.2015
2 Add a Device
DEVICE TYPE
NTP Server
Print er (HP)
Print er (Generic)
RDP Server
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
SSL Securit y Check
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
Webserver
Windows (via WMI)
X EN Host s
171 and list the device templates which were actually used to
create new sensors. Templates which were not applied will not be
shown in the ticket.
31.08.2015
247
2 Add a Device

Domain or Computer
Name
User
Password

User
Login

between:
Password
Private Key
248
31.08.2015
2 Add a Device

For WBEM Use Port
WBEM Port

SSH Port

sensor settings.
Target User


SSH Engine
31.08.2015
249
2 Add a Device

default SSH engine.

User

Password

VMware Protocol

XenServers.
Session Pool

Choose between:
250
31.08.2015
2 Add a Device


SNMP Version

between:
Community String

Authentication Type

Choose between:
device.
31.08.2015
251
2 Add a Device

entirely.
User

Password

Encryption Type

algorithm.
device.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (Sec.)

252
31.08.2015
2 Add a Device

My SQL v2 Sensor
1090

Post greSQL Sensor
For Databases Use
Port
1075
1187
1297
Microsoft SQL: 1433
MySQL: 3306
Oracle SQL: 1521
PostgreSQL: 5432
Port
Authentication

impersonation.
31.08.2015
253
2 Add a Device

User

Password

Timeout (Sec.)


Access Key
CloudWatch metrics.
Secret Key
CloudWatch metrics.
254
31.08.2015
2 Add a Device
ACCESS R IGHTS
User Group Access
Define which user group(s) will have access to the object you're
editing. A table with user groups and 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 2896 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, please see the section User
Access Right s 101 .
31.08.2015
255
3 Add a Sensor
6.2.3
Add a Sensor
In order to add a sensor manually, select Sensors | Add Sensor from the main menu. An
assistant will appear, leading you through two steps. For faster setup, you can select Add
Sensor... in the context menu 186 of a device to which you want to add the new sensor. This
will skip step 1 and lead you directly to step 2.
St ep 1
Please select Add sensor t o an exist ing device and choose a device you want to add the
new sensor to. Click on Cont inue.
Add Sensor Assistant
256
24.03.2015
3 Add a Sensor
St ep 2
The Add Sensor assistant is shown (see screenshot above). Select a sensor you want to
add and enter the needed settings. You can filter the listed sensors by type, by target
system, and by the used technology. You can choose one aspect per filter. Alternatively or
additionally, you can use the live search by typing in a key term (or a substring) in the Search
box. PRTG also suggests sensor types to create on the selected device; this
recommendation is automatically calculated based on the current user's sensor usage and
shows the ten commonest sensor types by default (if enough sensor types are already in
use). The chosen filter also applies to the recommendation. See section More if you want to
adjust the number of most used sensor types which are shown here or to hide this option
completely.
For more information about a sensor type, please see the manual section of the respective
sensor. See List of Available Sensor Ty pes 348 section to find detailed information about
every sensor type.
More
Knowledge Base: How can I change the number of entries in most used sensor types?
24.03.2015
257
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 3 Manage Device Tree
6.3
Manage Device Tree
While viewing the device tree (or parts of it), click on the Management tab to enter a different
tree view which shows your devices and sensors in a less colorful way. While in this view, you
can move monitoring objects using drag&drop in your browser window. You can also view and
edit object settings by selecting it. Changes take effect immediately. When done, leave the
Management tab.
In order to arrange objects in the tree, you have the following options:
Drag&Drop a Sensor
You can either move a sensor within the same device, or clone a sensor to another device.
Within the same device, drag any sensor and drop it to the place where you want to have it.
A shade will show the future position. When dropping, the sensor will be moved to this
position and existing sensors will be lined up after it. This is a very easy way to reposition
your sensors.
Drag any sensor from one device and drop it on another to clone a sensor. This will create
the same sensor type, with the same settings, on the new device, while maintaining the
original sensor. A shade will show the future position. Note: Cloned sensors are put to
Pause status initially to give you the chance to change any settings before monitoring
begins. Please check the settings 159 and resume 185 monitoring.
Note: You cannot clone 'fixed' objects, such as the root group or a probe device.
Note: In order to clone entire groups or devices, please use the Clone Object
accessible via the objects' Context Menu 186 .
2740
functionality
Drag&Drop a Group or Device

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

You can use Multi-Edit for object settings:
Hold down the Ctrl key and select multiple groups, devices, or sensors (one of a kind).
In the appearing dialog, select the settings you want to edit, change the according values,
and click Save. The changes will be applied to all selected objects.
The dialog is the same as described in the Mult i-Edit
2744
(Edit Settings) section.
Related Topics
For other ways to arrange objects, please see
Arrange Object s
2739

Clone Object
24.03.2015
2747
2740
259
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 4 Root Group Settings
6.4
Root Group Settings
On the Root group's overview page, click on the Set t ings tab to change settings.
The Root Group is Special

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

The following settings are available in the Set t ings tab. As you may not need all of these, just
regard those settings you really need and ignore the others. All settings you define here can
easily be inherited to all other objects in your setup.
BASIC GR OU P
SETTINGS
Group Name

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.
260
21.04.2016
LOCATION
Location (for geo
maps)
When you want to use Geo Maps 2753 , enter a location in the first
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 135 (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.

Domain or Computer
Name
User
Password

User
21.04.2016
261

Login

between:
Password
Private Key
For WBEM Use Port
WBEM Port

SSH Port

sensor settings.
262
21.04.2016

Target User


SSH Engine
default SSH engine.

User

Password

21.04.2016
263

VMware Protocol

XenServers.
Session Pool

Choose between:

SNMP Version

between:
264
21.04.2016

Community String

Authentication Type

Choose between:
device.
entirely.
User

Password

Encryption Type

algorithm.
device.
21.04.2016
265

Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (Sec.)


My SQL v2 Sensor
1090

Post greSQL Sensor
For Databases Use
Port
1075
1187
1297
266
21.04.2016

Microsoft SQL: 1433
MySQL: 3306
Oracle SQL: 1521
PostgreSQL: 5432
Port
Authentication

impersonation.
User

Password

Timeout (Sec.)

21.04.2016
267

Access Key
CloudWatch metrics.
Secret Key
CloudWatch metrics.
WINDOWS COMPATIBILITY OPTIONS

When experiencing problems while monitoring via Windows sensors, you can set some
compatibility options for trouble shooting.
Preferred Data Source
Define the method Windows sensors will use to query data. This
setting is valid only for hybrid sensors offering performance
counter and Windows Management Instrumentation (WMI)
technology. The setting will be ignored for all other sensors!
Choose between:
Performance Count ers and fallback t o WMI (recommended):
Try to query data via performance counters. If this is not
possible, establish a connection via WMI. This is the
recommended setting to best balance resource usage and
functionality.
Performance Count ers only : Query data via performance
counters only. If this is not possible, a sensor will return no data.
WMI only : Query data via WMI only. If this is not possible, a
sensor will return no data.
Timeout Method
Specify the time the sensor will wait for the return of its WMI query
before aborting it with an error message. Choose between:
Use 1.5x scanning int erval (recommended): Use a default of
one and a half times the scanning interval set for the sensor (see
below in this settings).
Set manually : Enter a timeout value manually.
We recommend that you use the default value. Only if you
experience ongoing timeout errors, try increasing the timeout
value.
268
21.04.2016

Timeout Value (Sec.)
This field is only visible if the manual timeout method is selected

above. Specify the time the sensor will wait for the return of its
WMI query before aborting with an error message. Please enter an
integer value.
SNMP COMPATIBILITY OPTIONS

When experiencing problems while monitoring via Simple Network Management Protocol
(SNMP) sensors, you can set some compatibility options for trouble shooting.
SNMP Delay (ms)
Add a time in milliseconds that will be waited between two SNMP

requests. This can help increase device compatibility. Please enter
an integer value. We recommend 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 (recommended): Ignore overflow
values and do not include them in the monitoring data.
Handle overflow values as valid result s: Regard all overflow
values as regular data and include them in the monitoring data.
We recommend that you use the default value. If you experience
problems, change this option.
Zero Values
Define how PRTG will handle zero values. Some devices send
incorrect zero values. This can cause false peaks.
Ignore zero values for delt a sensors (recommended): Ignore
zero values and do not include them in the monitoring data.
21.04.2016
269

Handle zero values as valid result s for delt a sensors: Regard
all zero values as regular data and include them in the monitoring
data.
32-bit/64-bit Counters
Define which kind of traffic counters PRTG will search for on a

device.
Use 64-bit count ers if available (recommended): The interface
scan will use 64-bit traffic counters, if available. This can avoid
buffer overflows in the devices.
Use 32-bit count ers only : The interface scan will always use 32bit 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.
Note: 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/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.
270
21.04.2016

[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.
[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
2071 and SNMP RMON 2010 sensors.
Combine them as you like to obtain suitable sensor names. See
the More section below for more information about SNMP sensor
names.
Port Name Update
Define how PRTG will react if you change port names in your
physical device (e.g. a switch or router). Choose between:
Keep port names (use t his if y ou edit t he names in PRTG): Do
not automatically adjust sensor names. This is the best option if
you want to change names in PRTG manually.
Aut omat ic sensor name updat e if name changes in device: If
PRTG detects changes of port names in your physical device, it
will try to automatically adjust sensor names accordingly. For
detailed information please see More section below.
Port Identification
Define which field will be used for SNMP interface identification.

Choose between:
Aut omat ic (recommended): Tries the ifAlias field first to identify
an SNMP interface and then ifDescr. Note: ifName will not be tried
automatically.
Use ifAlias: For most devices ifAlias is the best field to get
unique interface names.
Use ifDescr: Use this option if the port order of your device
changes after a reboot, and there is no ifAlias field available. For
example, this is the best option for Cisco ASA devices. Note:
When using this option it is important that your device returns
unique interface names in the ifDescr field.
Use ifName: You can also use this option if there is no unique
ifAlias available. Note: When using this option it is important that
your device returns unique interface names in the ifName field.
No Port Updat e: Use this option to disable automatic port
identification.
21.04.2016
271

Start Interface Index
For SNMP Traffic sensors 2071 , 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 2071 , define at which index PRTG will stop
SNMP Debug Log
Define if you want to create an SNMP log file for debugging

purposes. We recommend this only for debugging low level SNMP
issues. Choose between:
No log (recommended): No SNMP debug log file will be created.
Enable debug log: An SNMP log file is written to the Logs
(Debug) directory (on the Master node, if in a cluster). This is for
debugging purposes. The file will be overridden with each
scanning interval. For information on how to find the folder used
for storage, please see Dat a St orage 3135 section.

HTTP Proxy Settings

Name

Port
User

Password

272
21.04.2016
SCANNING INTER VAL

Scanning Interval
Select a scanning interval (seconds, minutes, or hours) from the

list. The scanning interval determines the time the sensor waits
between two scans. You can change the available intervals in the
system administration 2871 .
When a Sensor
Reports an Error
Define the number of scanning intervals that a sensor has time to

report an error before the sensor will be set to a Down status 135 .
The sensor can try to reach a device several times, depending on
the setup you can specify here, to help avoid false alarms if the
monitored device has only temporary issues. For previous
scanning intervals with failed requests, the sensor will show a
Warning status. Choose between:
Set sensor t o "down" immediat ely : The sensor will show an
error 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.
Note: Sensors that monitor via Windows Management
Instrumentation (WMI) always wait at least one scanning interval
until they show an error. It is not possible to set a WMI sensor
"down" immediately, so the first option will not apply to these
sensor types (all other options can apply).
Note: If a sensor has defined error limits for channels, this sensor
will always be set to a Down status immediately, so no "wait"
option will apply.
Note: If a channel uses lookup 3095 values, the sensor will always be
set to a Down status immediately, so no "wait" options will apply.
21.04.2016
273
SCHEDU LES, DEPENDENCIES, AND MAINTENANCE WINDOW

Schedule
Select a schedule from the list. Schedules can be used to pause

monitoring for a certain time span (days, hours) throughout the
week. You can create new schedules and edit existing ones in the
account settings 2836 . Note: Schedules are generally inherited. New
schedules will be added to existing ones, so all schedules are
active.
Maintenance Window
Specify if you want to set-up a one-time maintenance window.

During a maintenance window this object and all child objects will
not be monitored. They will enter a paused state then. Choose
between:
Not set (monit or cont inuously ): No maintenance window will
be set.
Set up a one-t ime maint enance window: Pause monitoring
within a maintenance window.
Maintenance Begins At
This field is only visible if maintenance window is enabled above.

Use the date time picker to enter the start date and time of the
maintenance window.
Maintenance End At

Use the date time picker to enter the end date and time of the
maintenance window.
Dependency settings are available only in Probe Settings

Settings 324 , and Sensor Settings 347 .
274
278
, Group Settings
299
, Device
21.04.2016
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
CHANNEL U NIT CONFIGU R ATION

Channel Unit Types
For each type of sensor channel, define the unit in which data is
displayed. If defined on probe, group, or device level, these
settings can be inherited to all sensors underneath. You can set
units for the following channel types (if available):
Bandwidt h
Memory
Disk
File
Cust om
Note: Custom channel types can be set on sensor level only.
21.04.2016
275
ADVANCED NETWOR K ANALYSIS

Unusual Detection
Define if you want to benefit from unusual detection 2872 for

sensors. You can configure the behavior of unusual detection (or
disable it completely) in the system settings 2872 . Choose between:
Enabled: Activate unusual detection for this object and, by
default, for all objects underneath in the hierarchy 89 of the
device tree. Sensors affected by this setting will turn to orange
color (unusual sensor status 135 ) 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
Detection
Define if you want to activate Similar Sensors 151 analysis. You can
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 89 of the
device tree. PRTG considers all sensors affected by this setting
during similarity analysis.
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

for your devices. Choose between:
164
Enabled: Activate the system information feature for this object

and, by default, for all objects underneath in the hierarchy 89 of
the device tree.
Disabled: Do not activate system information.
Notifications
The status or the data of a sensor can trigger notifications. Using this mechanism, you can
configure external alerting tailored to you needs. In an object's detail page, click on the
Not ificat ions tab to change sensor notification triggers. The defined triggers will be inherited
down to sensor level. For detailed information, please see Sensor Not ificat ions Set t ings 2719
section.
276
21.04.2016
Others
For more general information about settings, please see Object Set t ings
159
section.
More
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
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
21.04.2016
277
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 5 Probe Settings
6.5
Probe Settings
On a probe's overview page, click on the Set t ings tab to change settings.
Add Remote Probe

You can add additional remote probes to your setup to extend you monitoring to networks
that are not directly reachable by your PRTG core installation or cluster.
See Add Remot e Probe
3108
for more details.
Probe Settings
The following settings are available in the Set t ings tab of every probe. As you may not need
all of these for every probe, just regard those settings you really need, ignoring the others.
We recommend that you define as many settings as possible in the Root 260 group, so you can
inherit them to all other objects further down in the device tree hierarchy 89 .
BASIC PR OBE SETTINGS

Probe Name
Enter a meaningful name to identify the probe. The name will be

Tags
Enter one or more Tags 96 . Confirm each tag by hitting space,

tagfiltered 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
278
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).
21.04.2016
Inherited Settings
described below.
LOCATION
Location (for geo
maps)
49.452778 any 11.077778 text
following.

Domain or Computer
Name
User
Password
21.04.2016
279

User
Login

between:
Password
Private Key
For WBEM Use Port
WBEM Port

SSH Port
280
21.04.2016

sensor settings.
Target User


SSH Engine
default SSH engine.
21.04.2016
281

User

Password

VMware Protocol

XenServers.
Session Pool

Choose between:

SNMP Version

between:
282
21.04.2016

Community String

Authentication Type

Choose between:
device.
entirely.
User

Password

Encryption Type

algorithm.
21.04.2016
283

device.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (Sec.)


My SQL v2 Sensor
1090

Post greSQL Sensor
For Databases Use
Port
284
1075
1187
1297
21.04.2016

Microsoft SQL: 1433
MySQL: 3306
Oracle SQL: 1521
PostgreSQL: 5432
Port
Authentication

impersonation.
User

Password

Timeout (Sec.)

21.04.2016
285

Access Key
CloudWatch metrics.
Secret Key
CloudWatch metrics.

Choose between:
functionality.
Timeout Method
value.
286
21.04.2016


integer value.

SNMP Delay (ms)

Failed Requests

failures.
earlier.
Overflow Values
peaks.
Zero Values
21.04.2016
287

data.

device.
Request Mode
into one request.
Port Name Template

among which are:
288
21.04.2016

bandwidth (KBit/s).
names.
Port Name Update
Port Identification

Choose between:
automatically.
identification.
21.04.2016
289

End Interface Index
SNMP Debug Log


HTTP Proxy Settings

Name

Port
User

Password

290
21.04.2016
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.04.2016
291
CLU STER U SAGE

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 94 to
all objects underneath.

Note: Inheritance for schedules, dependencies, and maintenance windows cannot be
interrupted; the according settings from the parent objects will always be active. However,
you can define additional settings here. They will be active in parallel to the parent objects'
settings.
Schedule

active.
Maintenance Window

between:
be set.

maintenance window.
Maintenance Ends At

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:
292
21.04.2016

Use parent : Pause the current object if its parent object is in a
Down status, or if it is paused by another dependency.
Select object : Pause the current object if its parent object is in
a Down status, or if it is paused by another dependency.
Additionally, pause the current object if a specific other object in
the device tree is in a Down status, or if it is paused by another
dependency. Select below.
Note: Testing your dependencies is easy! Simply choose Simulat e
Error St at us from the context menu of an object that other
objects depend on. A few seconds later all dependent objects
should be paused. You can check all dependencies 2751 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 181
to choose an object on which the current object will be
dependent on.
Dependency Delay
(Sec.)
This field is only visible if you select another object than the parent
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.
21.04.2016
293
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
294
21.04.2016

Unusual Detection

Similar Sensors
Detection
analysis.
System Information

164

the device tree.
ADMINISTR ATIVE PR OBE SETTINGS / PR OBE SETTINGS FOR MONITOR ING

Define the IP address used for outgoing monitoring requests.
If there is more than one IP on the current system available, you can specify the IP address
that will be used for outgoing monitoring requests of certain sensor types.
The setting is valid for all monitoring requests sent from this PRTG probe.
This setting will be used for sensors using the following connection types: HTTP, DNS, FTP,
IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. Note: This feature does not support
all sensor types for technical reasons.
21.04.2016
295
ADMINISTR ATIVE PR OBE SETTINGS / PR OBE SETTINGS FOR MONITOR ING

This is useful for devices that expect a certain IP address when queried.
Default setting is aut o. PRTG will select an IP address automatically.
Note: If you change this setting, some sensors might stop working. For example, sensors
might show a Down status if the selected IP address is blocked on the way to or directly on
the monitored device.
Outgoing IPv4
Define the IP address for outgoing requests using the IPv4

protocol. The list shows all IP addresses available on the current
system. Choose a specific IP address or select aut o.
Outgoing IPv6
Define the IP address for outgoing requests using the IPv6

protocol. The list shows all IP addresses available on the current
system. Choose a specific IP address or select aut o. For details
about the basic concept of IPv6 in PRTG, please see IPv6 105
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.
Note: 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).
296
21.04.2016
SCHEDU LED R ESTAR T SETTINGS

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:
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 2900 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): This is the
recommended setting, although not set by default. Enter a
schedule below. We recommend restarting Windows servers
once a month for best performance.
Restart Schedule
This setting is only visible if you selected a schedule option above.

Choose how often you want to restart PRTG services or the
Windows server:
Once per week: Select a weekday and time below.
Once per mont h (recommended): Select a day of month and
time below.
Specify Day

Select a specific day of a week (Monday to Sunday) resp. month
(1st to 30th resp. Last). If you select Last , the restart will always be
executed on the last day of the month, regardless of how many
days the month has.
Note: If you select a date that does not exist in every month (for
example, the 30th day in February), PRTG will automatically initiate
the restart on the last day of this month.
Specify Hour

Select the time of day when PRTG will perform the restart.
Note: A Windows warning message will be displayed 10 minutes
before restart to inform a logged in user. The actual restart time
can differ up to 30 minutes from the settings you enter below!
21.04.2016
297
Notifications
section.
Others
159
section.
More
SNMP sensors?
298
21.04.2016
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 6 Group Settings
6.6
Group Settings
On a group's overview page, click on the Set t ings tab to change settings.
Add Group
The Add Group dialog appears when adding a new group to a parent group. It only shows the
setting fields that are imperative for creating the group. Therefore, you will not see all setting
fields in this dialog. For example, the Group St at us option is not available in this step.
You can change all settings in the group's Set t ings tab later.
Group Settings
The following settings are available in the Set t ings tab of every group. As you may not need
all of these for every group, just regard those settings you really need, ignoring the others.
Note: This documentation does not refer to the setting of the special Root group. The
settings available there differ from those described here.
BASIC GR OU P SETTINGS
Group Name

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
21.04.2016
Shows Tags 96 that this group inherits 96 from its parent probe
. This setting is shown for your information only and cannot be
changed here.
89
299
BASIC GR OU P SETTINGS
Tags
Enter one or more Tags 96 . Confirm each tag by hitting space,

tagfiltered 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
Sensor Management

this group. Choose between:
sensors: Use an extended set of auto-discovery templates. This
device.
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
head. PRTG will use the selected templates for auto-discovery on
the current device. Choose from:
ADSL
Amazon Cloudwat ch
Cisco ASA VPN
Dell MDI Disk
300
21.04.2016
DNS Server
Frit zbox
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)
Sever Cisco UCS
Server IBM
SonicWALL
SSL Securit y Check
UNIX /Linux Device
21.04.2016
301
UPS (APC)
Virt uozzo Server
Webserver
Windows (via WMI)
X EN Host s
171 and list the device templates which it used to create new
sensors. The ticket will not show templates which 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. You can run auto-discovery manually
any time using an object's context menu 186 .
Hourly : Perform auto-discovery for new devices and sensors
every 60 minutes.
Note: Please use this option with caution! Frequently executed
auto-discoveries might cause performance issues, especially
when large network segments are scanned every hour.
Daily : Perform auto-discovery for new devices and sensors
every 24 hours. The first auto-discovery will run immediately, all
Weekly : Perform auto-discovery for new devices and sensors
every 7 days. The first auto-discovery will run immediately, all
IP Selection Method
Define how you want to define the IP range for auto-discovery.

Choose between:
Class C base IP wit h st art /end (IPv4): Define an IPv4 class C
address range.
302
21.04.2016
IP and Subnet (IPv4): Enter an IPv4 address and subnet mask.

IP wit h oct et range (IPv4): Enter an IPv4 address range for every
IP octet individually. With this, you can define very customizable
IP ranges.
Use comput ers from t he act ive direct ory (maximum 1000
comput ers): Search in the active directory for computers to
perform auto-discovery.
Note: Define your active directory domain in advance in the
system administration. See Sy st em Administ rat ionCore &
Probes 2887 .
Note: Only subnets with up to 65,536 IP addresses can be
discovered! If you define a range with a higher number of
addresses, discovery will stop before it is completed.
IPv4 Base

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

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

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

IPv6/DNS Name List
This field is only visible if you select the IP list option above. Enter a
list of IP addresses or DNS names which the auto-discovery will
scan. Enter each address in a separate line.
IPv4 and Subnet (IPv4)
This field is only visible if 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.
21.04.2016
303
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 which 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.
If you have sub-OUs, consider the correct syntax in the format
Y,OU=X : OUs that are part of another OU have to be listed
together with their parent(s). Enter the sub-OU followed by ,OU=
and the name of the parent OU.
Examples:
Assuming that the organizational unit 'Y' is part of the OU named
'X'. Then the syntax would be Y,OU=X
For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would
be Z,OU=Y,OU=X
Note: The order is important, sub-OUs have to be listed left of their
particular parents!
Name Resolution
Define how 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 324 shows the DNS name or IP
address which 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.
Note: This setting does not affect how PRTG shows the devices in
the device tree.
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, but 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.
304
21.04.2016
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, for example, in other
groups also to this group and runs the auto-discovery on the
newly added devices.
Note: The auto-discovery will not run on devices that already
exist. If you want to run the auto-discovery for an existing
device, you have to start the auto-discovery on this device.
Inherited Settings
described below.
LOCATION
Location (for geo
maps)
49.452778 any 11.077778 text
following.
21.04.2016
305

Domain or Computer
Name
User
Password

User
Login

between:
Password
Private Key
306
21.04.2016

For WBEM Use Port
WBEM Port

SSH Port

sensor settings.
Target User


SSH Engine
21.04.2016
307

default SSH engine.

User

Password

VMware Protocol

XenServers.
Session Pool

Choose between:
308
21.04.2016


SNMP Version

between:
Community String

Authentication Type

Choose between:
device.
21.04.2016
309

entirely.
User

Password

Encryption Type

algorithm.
device.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (Sec.)

310
21.04.2016

My SQL v2 Sensor
1090

Post greSQL Sensor
For Databases Use
Port
1075
1187
1297
Microsoft SQL: 1433
MySQL: 3306
Oracle SQL: 1521
PostgreSQL: 5432
Port
Authentication

impersonation.
21.04.2016
311

User

Password

Timeout (Sec.)


Access Key
CloudWatch metrics.
Secret Key
CloudWatch metrics.

312
Choose between:
21.04.2016

functionality.
Timeout Method
value.

integer value.

SNMP Delay (ms)

Failed Requests

failures.
21.04.2016
313

earlier.
Overflow Values
peaks.
Zero Values
data.

device.
Request Mode
into one request.
314
21.04.2016

Port Name Template

among which are:
bandwidth (KBit/s).
names.
Port Name Update
21.04.2016
315

Port Identification

Choose between:
automatically.
identification.
End Interface Index
SNMP Debug Log

316
21.04.2016

HTTP Proxy Settings

Name

Port
User

Password

21.04.2016
317
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
318
21.04.2016
CLU STER U SAGE


settings.
Schedule

active.
Maintenance Window

between:
be set.

maintenance window.
Maintenance Ends At

maintenance window.
Dependency Type

can choose between:
21.04.2016
319

menu bar.
Dependency
dependent on.
Dependency Delay
(Sec.)
integer value.
320
21.04.2016
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.04.2016
321

Unusual Detection

Similar Sensors
Detection
analysis.
System Information

164

the device tree.
NU MBER OF SENSOR S LIMITATION

Sensor Limit
This setting allows the administrator to set a limit for the maximum
number of sensors in this group. Subgroups are also included. If
sensors exceed this limitation, they will be paused. This is of
special interest for a Managed Service Provider (MSP). Choose
between:
Allow unlimit ed number of sensors: Disable a limitation of the
number of sensors for this group. Any number of sensors can be
added to this group.
322
21.04.2016
NU MBER OF SENSOR S LIMITATION

Limit number of sensors in t his group: Enables a limitation of
the number of sensors for this group. Only a limited number of
sensors can be added to this group.
Maximum Number of
Sensors
This field is only visible if limitation is enabled above. Define how

many sensors can be added to this group. Please enter an integer
value.
Notifications
section.
Others
159
section.
More
SNMP sensors?
21.04.2016
323
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 7 Device Settings
6.7
Device Settings
On the details page of a device, click on 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 properties of
many devices at a time. For more details, please see Mult i-Edit List s 2742 section.
BASIC DEVICE SETTINGS

Device Name
Enter a meaningful name to identify the device. PRTG shows this

name by default in the device tree 123 and in all Alarms 161 and
Not ificat ions 2759 .
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 135 Paused until you change this setting again.
IP Version
324
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:
31.08.2015
BASIC DEVICE SETTINGS

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.
Note: Some sensor types have their own setting for IP address/
DNS name to which they connect.
Parent Tags
Shows Tags 96 that this device inherits 96 from its parent group
and probe 89 . This setting is shown for your information only and
cannot be changed here.
Tags
Enter one or more Tags 96 . Confirm each tag by with space,

comma, or enter key. Sensors on this device inherit these tags.
You can use tags to group sensors and tagfiltered views, for
example, in Libraries 2770 . 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 182 for the device. This setting determines in which
order 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, please see
the link in the More 346 section below.
Service URL
Specify a URL you would like to open directly when you select
Device Tools | Go To Service URL from the context menu 192 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.
31.08.2015
325
DEVICE TYPE
Sensor Management

this device. Choose between:
sensors): Use an extended set of auto-discovery templates. This
device.
Discovery Schedule
This option is only visible if one of the auto-discovery options is

selected above. Define when the auto-discovery will be run.
Choose between:
Once: Perform auto-discovery only once. For existing devices,
this will initiate a one-time sensor update for the current device.
Hourly : Perform auto-discovery for new sensors every hour.
Daily : Perform auto-discovery for new sensors every day.
Weekly : Perform auto-discovery for new sensors every week.
Device Template(s)
This option is only visible if using specific device templates (last

option) is enabled above. Please choose one or more templates by
adding a check mark in front of the respective template name. You
table head. These will be used for auto-discovery on the current
device. Choose from:
ADSL
Amazon Cloudwat ch
Cisco ASA VPN
Dell MDI Disk
DNS Server
326
31.08.2015
DEVICE TYPE
Frit zbox
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)
Sever Cisco UCS
Server IBM
SonicWALL
SSL Securit y Check
UNIX /Linux Device
UPS (APC)
31.08.2015
327
DEVICE TYPE
Virt uozzo Server
Webserver
Windows (via WMI)
X EN Host s
171 and list the device templates which were actually used to
create new sensors. Templates which were not applied will not be
shown in the ticket.
Inherited Settings
described below.
LOCATION
Location (for geo
maps)
49.452778 any 11.077778 text
following.
328
31.08.2015
LOCATION

Domain or Computer
Name
User
Password

User
Login

between:
31.08.2015
329

Password
Private Key
For WBEM Use Port
WBEM Port

SSH Port

sensor settings.
330
31.08.2015

Target User


SSH Engine
default SSH engine.

User

Password

VMware Protocol

31.08.2015
331

XenServers.
Session Pool

Choose between:

SNMP Version

between:
332
31.08.2015

Community String

Authentication Type

Choose between:
device.
entirely.
User

Password

Encryption Type

algorithm.
device.
Data Encryption Key

31.08.2015
333

Context Name

SNMP Port

SNMP Timeout (Sec.)


My SQL v2 Sensor
1090

Post greSQL Sensor
For Databases Use
Port
1075
1187
1297
Microsoft SQL: 1433
MySQL: 3306
Oracle SQL: 1521
PostgreSQL: 5432
334
31.08.2015

Port
Authentication

impersonation.
User

Password

Timeout (Sec.)


Access Key
CloudWatch metrics.
Secret Key
CloudWatch metrics.
31.08.2015
335

Choose between:
functionality.
Timeout Method
value.

integer value.

336
31.08.2015

SNMP Delay (ms)

Failed Requests

failures.
earlier.
Overflow Values
peaks.
Zero Values
data.

device.
31.08.2015
337

Request Mode
into one request.
Port Name Template

among which are:
bandwidth (KBit/s).
338
31.08.2015

names.
Port Name Update
Port Identification

Choose between:
automatically.
identification.
End Interface Index
SNMP Debug Log

31.08.2015
339


HTTP Proxy Settings

Name

Port
User

Password

340
31.08.2015
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
341
CLU STER U SAGE


settings.
Schedule

active.
Maintenance Window

between:
be set.

maintenance window.
Maintenance Ends At

maintenance window.
Dependency Type

can choose between:
342
31.08.2015

menu bar.
Dependency
dependent on.
Dependency Delay
(Sec.)
integer value.
31.08.2015
343
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
344
31.08.2015

Unusual Detection

Similar Sensors
Detection
analysis.
System Information

164

the device tree.
Notifications
section.
31.08.2015
345
Others
159
section.
More
SNMP sensors?
346
31.08.2015
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 8 Sensor Settings
6.8
Sensor Settings
There are more than 200 different sensor types available. In the Add Sensor dialog, all sensors
are categorized into groups to help you quickly find what you need. Once you are familiar with
the interface, you will probably enter the first letters of a sensor type's name into the Search
field in the upper left corner and get to a sensor even faster.
Available Sensor Types

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

For information about sensor settings, please see the following sections:
Sensor Set t ings
347

2707
2711
09.07.2015
348
2719
347

1 List of Available Sensor Types
6.8.1
This chapter lists all available sensors, arranged both by different categories and in alphabetical
order. Note: In the Add a Sensor 256 assistant, PRTG offers you various options to filter for
fitting sensor types easily.
Common Sensors
348
Bandwidth Monitoring Sensors

Web Servers (HTTP) Sensors
SNMP Sensors
349
349
350
Windows WMI/Performance Counters Sensors

Linux/Unix/OS X Sensors
Virtual Servers Sensors
Mail Servers Sensors
353
354
354
Database Servers Sensors

File Servers Sensors
355
355
Various Servers Sensors

VoIP and QoS Sensors
356
356
Hardware Parameters Sensors

Custom Sensors
357
358
PRTG Internal Sensors
359
All Sensors in Alphabetical Order

More
352
359
366
Common Sensors
Cloud HTTP Sensor
Cloud Ping Sensor
HTTP Sensor
523
533
790
Ping Sensor
1252
Port Sensor
1279
Port Range Sensor

SNMP Traffic Sensor
1289
2071
2228
2237
348
2378
27.04.2016

Bandwidth Monitoring Sensors

IPFIX Sensor
1003

jFlow V5 Sensor
1015
1035

NetFlow V5 Sensor
1047
1141

NetFlow V9 Sensor
1153
1164

1176
1211

sFlow Sensor
1222
1393
1405
1476

SNMP Library Sensor
1494
1845

SNMP RMON Sensor
SNMP Traffic Sensor
1948
2010
2071
2378
Web Servers (HTTP) Sensors

Cloud HTTP Sensor
523
Common SaaS Sensor

HTTP Sensor
547
790
800

HTTP Content Sensor
826
836

848
859
870
879

27.04.2016
816
890
349

901

915
2228
2237
2357
SNMP Sensors
1467
1476

1494
1505
1515

1524
1533
1542
1551

SNMP Custom Sensor
1484
1560
1569
1577

1586
1596

1607
1617
1629

1648
1657
1666

1675
1685
1694
SNMP HP BladeSystem Server Blade Sensor
1703
SNMP HP BladeSystem System Health Sensor
350
1638
1712
27.04.2016

1720
1729

1738
1747
1756
1765
1775
1784

1802
1811
SNMP Juniper System Health Sensor
1819
1828

SNMP Library Sensor
1857

SNMP Memory Sensor
1869
1877
1885
1894
1903
1912
1922
1931
1939

1957
1966
1983
1992
2001
2010

27.04.2016
1948
1975
SNMP RMON Sensor
1837
1845
SNMP Printer Sensor
1793
2020
351

2028
2037
2045

SNMP Traffic Sensor
2054
2063
2071
2082
2094
Windows WMI/Performance Counters Sensors

629
1232
1242
2339
2348
Windows IIS Application Pool Sensor

1242
2329

367
2367
2378
2389

2408
2419
2429

WMI Custom Sensor
2448

2458
2469
2480

WMI File Sensor
2490
2500

352
2438
2509
2521
27.04.2016


WMI Memory Sensor
2533
2543
2552
2565
2577
2589
2601

WMI Service Sensor
WMI Share Sensor
2610
2620
2630
2640
2649

WMI UTC Time Sensor
2667

WMI Volume Sensor
2658
2676
2686
2696
Linux/Unix/OS X Sensors
1318
1857

1877

2122
2132
2142

SSH Script Sensor
2152
2205

2217
2162

27.04.2016
1885
2109
SSH Meminfo Sensor
1869
2172
2183
353

2194
Virtual Servers Sensors

392
402
413

436
447
459
470
502

Common SaaS Sensor
513
547

Dropbox Sensor
425
599
609

Google Drive Sensor
619
780

940
949

930
960
971
1065
Virtuozzo Container Disk Sensor

Virtuozzo Container Network Sensor
2280
2290

2298
2308
2318
Mail Servers Sensors

639

354
649
27.04.2016


669
679

IMAP Sensor
659
689
980

POP3 Sensor
1270
SMTP Sensor
1434
994
1443

1455
2237
2480

2490
2339
2348
Database Servers Sensors

ADO SQL v2 Sensor
378

MySQL v2 Sensor
1075
1090
1187

PostgreSQL Sensor
1201
1297
2552
2565
2577
2589
File Servers Sensors

File Sensor
Folder Sensor
27.04.2016
571
722
File Content Sensor
FTP Sensor
562
731
741
750
355

758

1366
1903
1912
1922
1931

TFTP Sensor
1416
1948
1957
2263
WMI File Sensor
2500
WMI Free Disk Space (Multi Drive) Sensor

WMI Volume Sensor
2509
2686
Various Servers Sensors

DHCP Sensor
DNS Sensor
581
591

LDAP Sensor
Ping Sensor
1058
1252
Ping Jitter Sensor

Port Sensor
1025
1261
1279
Port Range Sensor

RADIUS v2 Sensor
1289
1348

SNTP Sensor
1358
2082
2102
2245
2237
2271
VoIP and QoS Sensors

Cisco IP SLA Sensor
492
1425

356
1329
27.04.2016


1338
1515
Hardware Parameter Sensors

562

571
619

1104
1113
1123

1467

1524
1533
1542
1551

1132
1560
1569
1629

1648
1657
1666

1638
1675
1685
1694
1703

1720

1738
1747
1756

27.04.2016
1712
1765
1784
357


1819
1828

SNMP Library Sensor
1793
1802
1837
1845
SNMP Memory Sensor
1894
1922
1912
1939

1957
1992
2001

2045
2054
2162
2172
2183

2020
2028

1948
2194
2521
Custom Sensors
EXE/Script Sensor
699

711
1015
1047
1153
1176

358
1222
1318
1374
27.04.2016


SNMP Custom Sensor
1405
1577

SNMP Custom Lookup Sensor
SSH Script Sensor
1586
1607
1596
1617
2205
WMI Custom Sensor
2448
2458
PRTG Internal Sensors

ClusterState Sensor
Core Health Sensor
542
555
Probe Health Sensor
1311
2257
All Sensors in Alphabetical Order

The version numbers show when the respective sensor type was originally introduced to
PRTG.
ADO SQL v2 Sensor
378
367
(v8.3.0)
(v16.x.24)
392
(v16.x.22)
402
(v15.x.19)
413
(v15.x.19)

436
425
(v15.x.19)
(v15.x.19)
447
459
(v15.x.19)
470
(v15.x.19)
Business Process Sensor

Cisco IP SLA Sensor
492
481
(v15.x.19)
(v15.x.20)
(v7)
502
(v12.x.1)

Cloud HTTP Sensor
Cloud Ping Sensor
27.04.2016
523
533
513
(v8.1.0)
(v14.x.14)
(v14.x.14)
359

ClusterState Sensor
Common SaaS Sensor

Core Health Sensor
(v9.1.0)
542
(v15.x.19)
547
555
(v9.1.0)

DHCP Sensor
DNS Sensor
(v12.x.1)
562
(v14.x.13)
571
(v8.2.0)
581
(v7)
591

Dropbox Sensor
609
599
(v16.x.22)
(v15.x.19)
619
(v13.x.6)
629
(v7)
(v13.x.5)
639
649
(v13.x.5)

679
669
722
Folder Sensor
741
FTP Sensor
(v7)
711
731
(v13.x.5)
(v7)
(v7)
(v7)

Google Analytics Sensor
Google Drive Sensor
HTTP Sensor
689
(v7)
File Content Sensor
750
(v13.x.5)
(v7)
699

File Sensor
(v15.x.18)
(v13.x.5)

EXE/Script Sensor
659
790
758
(v8.3.0)
(v15.x19)
768
(v15.x.19)
780
(v7)
800
(v7)
816
(v12.x.3)
HTTP Content Sensor
836
(v7)

360
826
(v12.x.3)
870
848
859
(v15.x.16)
(v7)
(v13.4.8)
27.04.2016

879
(v14.1.9)

890
(14.1.10)
(v7)
901
915
(v8.3.0)

940
(v7)
949

980
1003
(v12.4.4)
(v8.3.0)
994
1015
(v13.x.7)

jFlow V5 Sensor
1035
(v14.x.11)
1025
(v8.2.0)

1058
971
(v13.x.7)
LDAP Sensor
(v9.1.0)
960
(v7)

IPFIX Sensor
1047
(v8.2.0)
(v8.1.0)

MySQL v2 Sensor
1090
1065
1075
(v15.x.19)
(v14.x.12)
(v14.x.12)

1113
1104
(v15.4.21)
(v15.4.21)
1123

NetFlow V5 Sensor
1141
NetFlow V9 Sensor
1164
1187
(v15.4.21)
1153
(v7)
1176
(v7)
(v14.x.13)

1132
(v7)

(v15.4.21)
(v7)
1211
1201
(v15.x.18)
(v7)
1222
(v12.x.3)
1232
(v7)

27.04.2016
(v12.3.4)
(v7)
IMAP Sensor
930
1242
(v12.x.6)
361

Ping Sensor
1252
(v7)
Ping Jitter Sensor

POP3 Sensor
Port Sensor
(v7)
1270
1279
(v8.3.0)
1261
(v7)
Port Range Sensor
(v12.x.4)
1289
PostgreSQL Sensor
(v14.x.12)
1297
Probe Health Sensor
1311
(v9.1.0)
(v15.x.19)
1318

RADIUS v2 Sensor
1348

1393
(v7)
1358
(v7)
1374
(v7)
1405

1434
(v9.1.0)
(v7)
SMTP Sensor
1338
(v14.x.13)
sFlow Sensor
(v7)
1329
1416
(v12.x.6)
(v7)
1366
1425
(v12.x.1)
(v7)

1467
1476
(v7)
1443
(v7)
1455
(v9.1.0)
(v12.x.1)
1484
(v12.x.1)
1494
(v12.x.1)
1505
(v12.x.5)
1515
(v13.x.5)

1533
1524
(v12.x.4)
(v14.x.14)
1542
(v13.x.8)
1551

SNMP Custom Sensor
362
1577
1569
(v14.1.10)
1560
(v13.x.8)
(v12.x.4)
(v7)
27.04.2016


1586
(v15.x.18)
(v9.1.0)
1596

(v14.x.14)
1607
(v15x.18)
1617
(v16.x.24)
1629

1657
1638
(v7)
(v12.x.4)
1666

1685
(v16.x.24)
1648
(v16.x.24)
1675
(v12.x.4)
(v12.x.4)
1694
(v13.x.5)
(v15.x.18)
1703

1720
(v12.x.6)
1729

1738
1747
(v12.x.6)
(v12.x.4)
(v12.x.6)
1756
1765
(v12.x.4)
1775
(v13.x.4)
(v13.x.4)
1784
1793
(v13.x.4)
1802
(v13.x.4)
1811
(v14.1.10)
1819
(v15.2.16)
1828
(v13.x.8)

1845
(v13.x.8)
(v8.1.0)
1857

1877
1894
1869
(v8.1.0)
(v8.1.0)
27.04.2016
1837
(v7)
SNMP Memory Sensor
(v15.x.18)
(v9.1.0)
SNMP Library Sensor
1712
1885
(v13.x.5)
(v12.x.4)
363

1903
1912
(v12.x.3)
(v12.x.4)
(v12.x.3)
1922
(v12.x.4)
1931
(v13.x.7)
1939
1948
(v12.x.3)
1957
(v12.x.3)
1966
(v13.x.5)
SNMP Printer Sensor
(v14.x.11)
1975

1992

SNMP RMON Sensor
(v13.x.4)
1983
(v13.x.4)
2001
(v13.x.4)
(v12.x.1)
2010
2020
(v13.x.5)
2028
(v13.x.6)
2037
(v13.x.4)
2045

SNMP Traffic Sensor
2071
(v7)
2082
(v13.x.8)
2094
(v8.1.0)
(v8.1.0)
2109
2122

SSH Meminfo Sensor
2142
(v8.1.1)
(v8.1.0)
2132
(v8.1.0)
(v12.x.1)
2152
(v14.x.12)
2162
2183

SSH Script Sensor
2205
(v14.1.9)
2172
(v14.1.9)
2194
(v14.1.9)
(v12.x.1)

364
(v13.x.4)
(v7)
2063

2102
2054
(v7)
SNTP Sensor
(v13.x.4)
2217
(v12.x.6)
27.04.2016

2228
(v15.x.19)

TFTP Sensor
2263
2245
(v14.x.12)
2237
(v7)
(v9.1.0)
2257
(v8.1.0)
(v8.3.0)
2271
2280
(v15.x.19)
2290
(v8.1.0)
2298
(v12.x.1)
2308
2318
(v7)
2339
(v8.1.0)
2329
(v7)

2357
2348
(v8.1.0)
(v12.x.1)

2389
(v12.x.1)
2378
2367
(v8.3.0)
(v7)
(v12.x.4)
Windows Physical Disk Sensor (v9.1.0)

Windows Physical Disk I/O Sensor
2419
2408
2398
(v16.x.24)
(v8.3.0)
(v7)
2429
(v8.1.0)

WMI Custom Sensor
2448
2469
2458
(v12.x.4)
(v7)
2480
(v9)

WMI File Sensor
2500
(v13.x.6)
(v7)

2438
2490
(v12.x.1)
(v7)

2521
2509
(v7)
(v12.x.1)
2533
(v16.x.24)
WMI Logical Disk Sensor

27.04.2016
365

WMI Memory Sensor
2543
(v7)
2552
(v8.1.0)
2565
(v8.1.0)
2577
(v12.x.6)
2589
(v14.x.13)
2601

WMI Service Sensor
WMI Share Sensor
(v12.x.1)
2610
(v9)
(v7)
2620
(v8.1.0)
2630
2640
(v12.x.1)
2649
(v8.1.0)

WMI UTC Time Sensor
2667
2686
(v8.1.0)
(v9.2.0)

WMI Volume Sensor
2658
2676
(v7)
(v7)
2696
(v9.1.0)
More
Did not find what you were looking for? Have a look at the Additional Sensor Types (Custom
Sensors) 2707 section.
366
27.04.2016

2 Active Directory Replication Errors Sensor
6.8.2
The Active Directory Replication Errors sensor uses the Windows credentials of its parent
device to check domain controllers for replication errors.
It can show the following:
Number of consecutive sync failures
If the source is deleted
If the scheduled sync is disabled
Time of the last sync attempt
Result of the last sync
Time of the last sync success
Number of modified consecutive sync failures
Number of pending replication operations
Which channels the sensor actually shows might depend on the monitored device and the
sensor setup.
21.01.2016
367

Ac tiv e Direc tory Replic taion Errors Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ac tiv e_direc tory _replic ation_errors.png
Remarks
Requires
369
valid Windows domain credentials in the settings of the parent device
Requires
369
the probe system to be part of the domain whose AD you monitor.
329
Requires 369 .NET 4.0 or higher on the probe system. Note: 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, please see
the manual section Define Lookups 3095 .
Note: 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 not more than 50 sensors of
this sensor type on each probe.
368
21.01.2016

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 3109 . If the framework is missing, you cannot create
this sensor.
Required .NET version (with latest updates): .NET 4.0 (Client Profile is sufficient), .NET 4.5, or
.NET 4.6. For more information, please see the Knowledge Base article http://kb.paessler.com/
en/topic/60543 (see also section More below).
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 3109 . If this requirement is
not met, the sensor will not work.
Requirement: Windows Credentials

Requires credentials for Windows systems to be defined for the device you want to use the
sensor on. In the parent device's 329 Credent ials for Windows Sy st ems settings, please
prefer using Windows domain credentials.
Note: 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.
Note: Your Windows credentials may not contain any double quotation marks ("). If they do,
this sensor will not work!
Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 256 . It only
shows the setting fields that are imperative for creating the sensor. Therefore, you will not see
all setting fields in this dialog. You can change (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 in this dialog are
valid for all of the sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
21.01.2016
369

SENSOR SETTINGS
Replication Neighbor
Select the replication neighbor whose replication you want to add

a sensor for. You see a list with the names of all items which are
available to monitor. Select the desired items by adding check
marks in front of the respective lines. PRTG creates one sensor for
each selection. You can also select and deselect all items by using
the check box in the table head.
Sensor Settings
On the details page of a sensor, click on the Set t ings tab to change its settings.
Note: Usually, a sensor connects to the IP Address or DNS Name of the parent device on
which you created this sensor. See the Device Set t ings 324 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 123 , as well as in alarms 161 , logs
169 , notifications 2759 , reports 2786 , maps 2810 , libraries 2770 , and tickets
171 .
Parent Tags
Shows Tags 96 that this sensor inherits 96 from its parent device,
group, and probe 89 . This setting is shown for your information
only and cannot be changed here.
Tags
Enter one or more Tags 96 , separated by space or comma. You

can use tags to group sensors and use tagfiltered views later on.
Tags are not case sensitive. We recommend that you use the
default value.
You can add additional tags to it, if you like. Other tags are
automatically inherited 96 from objects further up in the device
tree. These are visible above as Parent Tags.
Priority
370
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).
21.01.2016

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.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (on the Master node, if in a cluster). File
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, please see the Dat a
St orage 3135 section.
SENSOR DISPLAY
Primary Channel
Select a channel from the list to define it as the primary channel. In

the device tree, the last value of the primary channel will always be
displayed below the sensor's name. The available options depend
on what channels are available for this sensor. Note: You can set
another primary channel later by clicking on the pin symbol of a
channel in the sensor's Overview tab.
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 which visualizes the different components
of your total traffic. Note: This option cannot be used in
combination with manual Vertical Axis Scaling (available in the
Sensor Channels Set t ings 2711 settings).
21.01.2016
371

SENSOR DISPLAY
Stack Unit
This setting is only available if stacked graphs are selected above.

Choose a unit from the list. All channels with this unit will be
stacked on top of each other. By default, you cannot exclude
single channels from stacking, if they use the selected unit.
However, there is an advanced procedure to do so.
Inherited Settings
described below.
372
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
373


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) throughout the week. With the
period list option it is also possible to pause monitoring for a
specific time span. You can create new schedules and edit existing
ones in the account settings 2836 .
Note: Schedules are generally inherited. New schedules will be
added to existing ones, so all schedules are active at the same
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.
Note: To terminate a current maintenance window before the
defined end date, you can change the time in Maint enance End At
field to a date in the past.
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 End At

above. Use the date time picker to enter the end date and time of
Dependency Type

can choose between:
Use parent : Pause the current sensor if the device, where it is
created on, is in a Down status, or if the sensor is paused by
another dependency.
374
21.01.2016


Select object : Pause the current sensor if the device, where it is
created on, is in an Down status, or if the sensor is paused by
another dependency. Additionally, pause the current sensor if a
specific other object in the device tree is in a Down status, or if
it is paused by another dependency. Select below.
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 a Down
status, the device will be paused. For example, it is a good idea
to make a Ping sensor the master object for its parent device to
pause monitoring for all other sensors on the device in case the
device cannot even be pinged. Additionally, the sensor will be
paused if the parent group of its parent device is in a Down
status, or if it is paused by another dependency.
menu bar.
Dependency
Dependency Delay
(Sec.)
This field is only visible if the Select object option is enabled

above. Click on the reading-glasses and use the object selector
to choose an object on which the current sensor will depend.
181
Define a time span in seconds for dependency delay. After the

master object for this dependency comes back to an Up status,
the beginning of the monitoring of the depending objects will be
additionally delayed by the time span you define here. This can help
to avoid false alarms, for example, after a server restart, by giving
integer value.
Note: 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 324 or in the
superior Group Set t ings 299 .
21.01.2016
375

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
376
21.01.2016

More
Edit Sensor Channels

To change display settings, spike filter, and limits, switch to the sensor's Overview tab and
click the gear icon of a specific channel. For detailed information, please see the Sensor
Channels Set t ings 2711 section.
Notifications
Click the Not ificat ions tab to change notification triggers. For detailed information, please see
the Sensor Not ificat ions Set t ings 2719 section.
Others
For more general information about settings, please see the Object Set t ings
21.01.2016
159
section.
377

3 ADO SQL v2 Sensor
6.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 which 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ado-sql-v 2.png
Remarks
Requires
379
.NET 4.0 on the probe system.
Define Credent ials for Dat abase Management Sy st ems 334 in settings that are higher in
the Object Hierarchy 89 , for example, in the parent device settings 324 .
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.
378
27.04.2016

3 ADO SQL v2 Sensor
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 3135 for more information about how to
find this path.
If you use an ODCB connection, you have to define the ODCB connection in the Windows
ODCB Connection Manager first. If it is a 64-bit Windows, you need to define the ODCB
connection as an ODCB 32-bit connection.
This sensor type supersedes the outdated ADO SQL sensor.
PRTG Manual: Monit oring Dat abases
selection)
3033
(includes an example
3034
for channel value
Knowledge Base: How can I monitor strings from an SQL database and show a sensor status
depending on it?

this sensor.
Add Sensor
later.
Sensor Settings
27.04.2016
379

3 ADO SQL v2 Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
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 more information on how to build connection strings, please
see More 391 section below.
Note: For ODBC connections, you need to enter MSDASQL as
provider, for example
Provider=MSDASQL;DSN=_my_odbc_sqlserver.
Note: You can use the placeholders %dbloginuser and %
dbloginpassword here. PRTG will replace them with the
Credent ials for Dat abase Management Sy st ems 334 of the
parent device.
380
27.04.2016

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, please see Dat a
St orage 3135 section. By default, there is the demo script Demo
Serverupt ime.sql available that you can use to monitor the uptime
of the target server.
For example, a correct expression in the file could be: SELECT AVG
(UnitPrice) FROM Products. If you want to use transactions,
separate the individual steps with semicolons ";".
Note: Please be aware that with each request the full result set will
be transferred, so use filters and limits in your query.
Use Transaction
Define if you want to use transactions and if they will affect the
database content. Choose between:
Don't use t ransact ion (default ): No transactions will be
executed.
Use t ransact ion and alway s rollback: Choose this option to
ensure that no data in the database will be changed by the
query. In the SQL Query field above, separate the single steps of
the transaction with semicolons.
Use t ransact ion and commit on success: Choose this option
to perform changes on the database with the query. The
changes will only apply if all execution steps succeed without
any errors. In the SQL Query field above, separate the single
steps of the transaction with semicolons.
Data Processing
Define if you want to process data from the database. Once a

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 only
rows which were changed somehow with the query (for
example, created, deleted, edited).
27.04.2016
381

3 ADO SQL v2 Sensor
DATA
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.
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
Channel Values as
This setting is only visible if you selected the process data table
option above. Define the sensor behavior if DBNull is returned by
the query. Choose between:
Error: The sensor will show a Down status if DBNull is reported.
Number 0: The sensor will recognize the result DBNull as a valid
value and interpret it as the number 0.
Select Channel Value

by
option above. Define how the desired cell in the database table will
be selected. This is necessary to configure the cells which will be
used in the sensor channels. Choose between:
Column number: The channel value will be determined by using
the value in row 0 of the column whose number you specify
below.
Column name: The channel value will be determined by using the
value in row 0 of the column whose name you specify below.
Row number: The channel value will be determined by using the
value in column 0 of the row whose number you specify below.
Key value pair: The channel value will be determined by
searching in column 0 for the key you specify below and
returning the value in column 1 of the same row where the key
value was found.
Please see manual section Monit oring Dat abases
example 3034 for channel value selection.
Sensor Channel #x
3033
for an
option above. You can define up to 10 different channels for the
data processing of this sensor. You have to define at least one
data channel if you process the data table, so you will see all
available settings for Channel #1 without enabling it manually. For
all other possible channels, choose between:
Disable: This channel will not be added to the sensor.
Enable: This channel will be added to the sensor. Define the
settings as described above.
382
27.04.2016

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,
Sensor Channel #x
Name
option above. Enter a unique name for the channel. Please enter a
string. Channels will be generated dynamically with this name as
identifier. Once a sensor is created, you cannot change this value.
It is shown for reference purposes only. If you need to change
this, please add the sensor anew.
Sensor Channel #x
Column Number
This setting is only visible if you selected the column number

option above. Provide the number of the column which will be
used to determine the channel value in row 0. Please enter an
integer value.
Sensor Channel #x
Column Name
This setting is only visible if you selected the column name option
above. Provide the name of the column which will be used to
determine the channel value in row 0. Please enter a string.
Sensor Channel #x
Row Number
This setting is only visible if you selected the row number option
above. Provide the number of the row which 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 selected the key value pair option
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.
Sensor Channel #x
Mode
option above. Define how to display the determined value in the
channel. 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:
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.
Sensor Channel #x
Unit
27.04.2016
This setting is only visible if you have selected the process data
table option above. Define the unit of the channel value. Once a
383

3 ADO SQL v2 Sensor
DATA
BytesBandwidth
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 3086 for
custom sensors.
Note: To use lookups 3095 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!
Sensor Channel #x
Custom Unit
This setting is only visible if you selected the Cust om unit option
above. Define a unit for the channel value. Please enter a string.
Sensor Channel #x
Value Lookup
This settings is only visible if you select the Value Lookup option
above. Select a lookup 3095 file that you want to use with this
channel.
Use Data Table Value in This setting is only visible if you selected the process data table
Sensor Message
option above. Define if the sensor message will show a value from
the data table. Choose between:
Disable: Do not use a custom sensor message.
Enable: Define a custom sensor message with the value of a
defined channel.
384
27.04.2016

3 ADO SQL v2 Sensor
DATA
Sensor Message
Column Number
This setting is only visible if you selected the column number and
sensor message options above. Specify the number of the column
whose value will be shown in the sensor message. Please enter an
integer value.
Sensor Message
Column Name
This setting is only visible if you selected the column name and
sensor message options above. Specify the name of the column
whose value will be shown in the sensor message. Please enter a
string.
Sensor Message Row

Number
This setting is only visible if you selected the row number and
sensor message options above. Specify the number of the row
integer value.
Sensor Message Key
This setting is only visible if you selected the key value pair and
sensor message options above. Specify the key for the value
which will be shown in the sensor message. Please enter a string.
Sensor Message
This setting is only visible if you selected the sensor message

option above. Define the sensor message. Please enter a string.
Use the placeholder {0} at the position where the value will be
added.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel
27.04.2016

385

3 ADO SQL v2 Sensor
SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
386
27.04.2016

3 ADO SQL v2 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
27.04.2016
387

3 ADO SQL v2 Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
388
27.04.2016

3 ADO SQL v2 Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
27.04.2016
389

3 ADO SQL v2 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
390
27.04.2016

3 ADO SQL v2 Sensor
More
Knowledge Base: How can I monitor other SQL Servers through ADO with PRTG?
depending on it?

Notifications
Others
27.04.2016
159
section.
391

4 Amazon CloudWatch Alarm Sensor
6.8.4
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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/amazon_c loudwatc h_alarm.png
Remarks
The data you see in the sensor message is not necessarily the current data. It merely shows
the reason for the current status 135 and why the sensor changed to it. This means for the
Up status, for example, that this data is as old as time has past since the last alarm
disappeared.
Requires 393 access rights for CloudWatch queries. For details, please see the Knowledge
Base: How do I define access rights for Amazon CloudWatch queries?
Requires
393
.NET 4.0 or higher on the probe system.
Define Credent ials for Amazon CloudWat ch 335 in settings that are higher in the Object
Hierarchy 89 , for example, in the parent device settings 324 .
Note: Names of configured alarms that you want to monitor must not contain double spaces.
Note: Amazon will charge you (a small amount) for each "Amazon CloudWatch API Request"
query the sensor sends to the Amazon servers. For details, please see the Knowledge
Base: How much does Amazon charge for using the CloudWatch API?
392
21.01.2016

Important notice: Currently, this sensor type is in beta status. The methods of operating can
change at any time, as well as the available settings. Do not expect that all functions will
work properly, or that this sensor works as expected at all. Be aware that this type of
sensor can be removed again from PRTG at any time.
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 the Knowledge
Base article http://kb.paessler.com/en/topic/38083

this sensor.
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 in this dialog are valid for all of the
sensors that are created.
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 which are available to monitor. Select the
desired items by adding check marks in front of the respective
lines. PRTG creates one sensor for each selection. You can also
head.
To better find what you want to monitor, especially in large tables,
use the search function in the upper right corner.
21.01.2016
393

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

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)
394
21.01.2016


EU (Ireland)
EU (Frankfurt)
Asia Pacific (Singapore)
Asia Pacific (Tokyo)
Asia Pacific (Sydney)
Asia Pacific (Seoul)
South America (Sao Paulo)
Description
Shows the description of the AWS service instance that this sensor
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.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
21.01.2016
395

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
396
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
397


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
398
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
399

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
400
21.01.2016

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
21.01.2016
159
section.
401

5 Amazon CloudWatch EBS Sensor
6.8.5
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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/amazon_c loudwatc h_ebs_sensor.png
402
21.01.2016

Remarks
Requires
403
The minimum scanning interval for this sensor is 15 minut es.
query the sensor sends to the Amazon servers. Depending on the service, each Amazon
CloudWatch sensor sends about 10 to 30 requests with each scanning interval. Last time we
checked the Amazon price list, they charged max. US$ 0.014 per 1,000 requests (depending
on your region).
For details, please see the Knowledge Base: How much does Amazon charge for using the
CloudWatch API?
Note: 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 411 . 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 411

CloudWatch sensor needs specific rights to query any metrics. For details, see section More
411 .

this sensor.
21.01.2016
403

Add Sensor
later.
PRTG looks for available instances. Note: 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 in this dialog are valid
for all of the sensors that are created.

Services
Select the Volume you want to add a sensor for. You see a list
with the names of all items which are available to monitor. Select
the desired items by adding check marks in front of the respective
head.
Sensor Settings

Sensor Name
404

171 .
21.01.2016


Parent Tags
Tags

default value.
Priority

Region

US West (Oregon)
EU (Ireland)
EU (Frankfurt)
21.01.2016
405


Description
ID
the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
406
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
407

Note: 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 ionMonit oring 2871 are not available for
this sensor.
For Amazon CloudWatch sensors, the minimum scanning interval is 15 minut es.

Schedule

time.
Maintenance Window


Maintenance End At

408
21.01.2016


Dependency Type

can choose between:
another dependency.
menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
409

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
410
21.01.2016

Supported Metrics
AMAZON CLOU DWATCH METR ICS
Elastic Block Store
(EBS)
VolumeTotalReadTime (Sum)
VolumeTotalWriteTime (Sum)
VolumeReadBytes (Sum)
VolumeWriteOps (Sum)
VolumeReadOps (Sum)
VolumeWriteBytes (Sum)
VolumeConsumedReadWriteOps (Sum)
VolumeQueueLength (Average)
VolumeIdleTime (Sum)
Supported Dimensions
AMAZON CLOU DWATCH DIMENSIONS
Elastic Block Store
(EBS)
Volume
More

21.01.2016
411

Notifications
Others
412
159
section.
21.01.2016

6 Amazon CloudWatch EC2 Sensor
6.8.6
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
21.01.2016
413

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/amazon_c loudwatc h_ec 2_sensor.png
Remarks
Requires
414
Dimensions 423 .
on your region).
CloudWatch API?

423 .

this sensor.
414
21.01.2016

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 which are
Sensor Settings

Sensor Name
21.01.2016

171 .
415


Parent Tags
Tags

default value.
Priority

Region

US West (Oregon)
EU (Ireland)
EU (Frankfurt)
416
21.01.2016


Description
ID
the sensor anew.
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.
Note: To use detailed monitoring in PRTG, you must also activate it
for your monitored instance in the AWS web console.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
21.01.2016
417

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
418
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
21.01.2016
419


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
420
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
421

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
422
21.01.2016

Supported Metrics
Elastic Compute Cloud
(EC2)
CPUUtilization (Average)
NetworkIn (Sum)
NetworkOut (Sum)
DiskReadBytes (Sum)
DiskReadOps (Sum)
DiskWriteBytes (Sum)
DiskWriteOps (Sum)
CPUCreditUsage (Average)
CPUCreditBalance (Average)
StatusCheckFailed (Maximum)
StatusCheckFailed_Instance (Maximum)
StatusCheckFailed_System (Maximum)

Elastic Compute Cloud
(EC2)
Instance
Auto Scaling Group
More
21.01.2016
423


Notifications
Others
424
159
section.
21.01.2016

7 Amazon CloudWatch ElastiCache Sensor
6.8.7
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
channels.
434
for a list of data that this sensor potentially can show in dedicated
sensor setup.
Amazon CloudWatc h ElastiCac he Sensor
21.01.2016
425

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/

amazon_c loudwatc h_elastic ac he_sensor.png
Remarks
Requires
426
Dimensions 435 .
on your region).
CloudWatch API?

435 .

this sensor.
426
21.01.2016

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 which are
Sensor Settings

Sensor Name
21.01.2016

171 .
427


Parent Tags
Tags

default value.
Priority

Region

US West (Oregon)
EU (Ireland)
EU (Frankfurt)
428
21.01.2016


Description
ID
the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
429

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
430
21.01.2016

this sensor.

Schedule

time.
Maintenance Window


Maintenance End At

21.01.2016
431


Dependency Type

can choose between:
another dependency.
menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
432
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
433

Supported Metrics
ElastiCache
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)
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)
434
21.01.2016


ElastiCache
Cache Cluster
Cache Cluster Node
More

Notifications
Others
21.01.2016
159
section.
435

8 Amazon CloudWatch ELB Sensor
6.8.8
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.
445
sensor setup.
Amazon CloudWatc h ELB Sensor
436
21.01.2016

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/amazon_c loudwatc h_elb_sensor.png
Remarks
Requires
437
Dimensions 445 .
on your region).
CloudWatch API?

445 .

this sensor.
21.01.2016
437

Add Sensor
later.

Services
Select the Load Balancers or Availability Zones you want to add a

Sensor Settings

Sensor Name
438

171 .
21.01.2016


Parent Tags
Tags

default value.
Priority

Region

US West (Oregon)
EU (Ireland)
EU (Frankfurt)
21.01.2016
439


Description
ID
the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
440
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
441

this sensor.

Schedule

time.
Maintenance Window


Maintenance End At

442
21.01.2016


Dependency Type

can choose between:
another dependency.
menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
443

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
444
21.01.2016

Supported Metrics
Elastic Load Balancing
(ELB)
RequestCount (Sum)
SpilloverCount (Sum)
HealthyHostCount (Minimum)
UnHealthyHostCount (Maximum)
BackendConnectionErrors (Sum)
HTTPCode_Backend_2XX (Sum)
HTTPCode_ELB_4XX (Sum)
HTTPCode_ELB_5XX (Sum)
Latency (Average)
SurgeQueueLength (Average)

Elastic Load Balancing
(ELB)
Load Balancer
Availability Zone
More
21.01.2016
445


Notifications
Others
446
159
section.
21.01.2016

9 Amazon CloudWatch RDS Sensor
6.8.9
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.
457
sensor setup.
21.01.2016
447

Amazon CloudWatc h RDS Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/amazon_c loudwatc h_rds_sensor.png
Remarks
Requires
449
448
21.01.2016

Dimensions 457 .
on your region).
CloudWatch API?

457 .

this sensor.
Add Sensor
later.
21.01.2016
449


Services
Select the Engines or Database Instances you want to add a

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
450
21.01.2016


Region

US West (Oregon)
EU (Ireland)
EU (Frankfurt)
Description
ID
the sensor anew.
SENSOR DISPLAY
Primary Channel
21.01.2016

451

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
452
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
21.01.2016
453


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
454
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
455

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
456
21.01.2016

Supported Metrics
Relational Database
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)
WriteThroughput (Sum)
NetworkReceiveThroughput (Sum)
NetworkTransmitThroughput (Sum)

Relational Database
Service (RDS)
Engine
DB Instance
More
21.01.2016
457


Notifications
Others
458
159
section.
21.01.2016

10 Amazon CloudWatch SNS Sensor
6.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.
468
sensor setup.
Amazon CloudWatc h SNS Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/amazon_c loudwatc h_sns_sensor.png
Remarks
Requires
460
21.01.2016
459

Dimensions 468 .
on your region).
CloudWatch API?

468 .

this sensor.
Add Sensor
later.
460
21.01.2016


Services
Select the Applications, Platforms or Topics you want to add a

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
21.01.2016
461


Priority

Region

US West (Oregon)
EU (Ireland)
EU (Frankfurt)
Description
ID
the sensor anew.
462
21.01.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
463

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
464
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
465


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
466
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
467

Supported Metrics
Simple Notification
Service (SNS)
NumberOfNotificationsDelivered (Sum)
NumberOfNotificationsFailed (Sum)
NumberOfMessagesPublished (Average)
PublishSize (Average)

Simple Notification
Service (SNS)
Application
Platform
Application and Platform
Topic
More

Notifications
468
21.01.2016

Others
21.01.2016
159
section.
469

11 Amazon CloudWatch SQS Sensor
6.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.
479
sensor setup.
Amazon CloudWatc h SQS Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/amazon_c loudwatc h_sqs_sensor.png
Remarks
470
21.01.2016

Requires
471
Dimensions 479 .
on your region).
CloudWatch API?

479 .

this sensor.
Add Sensor
later.
21.01.2016
471


Services
Select the Queues you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
472
21.01.2016


Priority

Region

US West (Oregon)
EU (Ireland)
EU (Frankfurt)
Description
ID
the sensor anew.
21.01.2016
473

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
474
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
21.01.2016
475


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
476
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
477

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
478
21.01.2016

Supported Metrics
Simple Notification
Service (SNS)
SentMessageSize (Sum)
NumberOfMessagesSent (Sum)
NumberOfMessagesReceived (Sum)
NumberOfMessagesDeleted (Sum)
NumberOfEmptyReceives (Sum)
ApproximateNumberOfMessagesVisible (Average)
ApproximateNumberOfMessagesNotVisible (Average)
ApproximateNumberOfMessagesDelayed (Average)

Simple Notification
Service (SNS)
Queue
More

21.01.2016
479

Notifications
Others
480
159
section.
21.01.2016

12 Business Process Sensor
6.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
Note: The Business Process sensor does not show values in the "Downtime" channel because
they cannot be calculated for this sensor type.
Note: If you want to process values from other sensors and you want to perform calculations
with these values, for example, please use the Sensor Fact ory Sensor 1374 instead.
sensor setup.
Business Proc ess Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/business_proc ess_sensor.png
21.01.2016
481

Remarks
Knowledge Base: How does the Business Process sensor calculate summarized sensor
states?
This sensor does not support more than 50 channels
482
officially.
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

Sensor Name
482

171 .
21.01.2016


Parent Tags
Tags

default value.
Priority
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%. Note:
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 status (and so
the sensor status is Down).
The Sensor St at es 135 which 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.
21.01.2016
483


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.
To get more information, an illustration of the business process
mechanisms and some use cases of the Business Process sensor,
Warning Threshold %
Set a percentage limit to define when the sensor channel displays

a Warning status. Please enter an integer value. Default is 75%.
Note: 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 135 which 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.
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.
To get more information, an illustration of the business process
mechanisms and some use cases of the Business Process sensor,
Objects
484
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 181 . You can also start typing the
object's ID, name, or a tag. PRTG then suggests the possible
objects to be selected.
21.01.2016


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 triple
weight to it.
Note: A probe, group, or device is as long in "up" condition as it
does not contain any sensors in "down" condition.
Note: If you encounter issues with your Business Process sensor and want to contact our
support team 2932 , 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/business_proc ess_sensor_c lipboard-m.png
You find your configuration in the window that opens. Copy the marked text and paste it into
the support form 2932 to send it our support team.
SENSOR DISPLAY
Primary Channel
21.01.2016

485

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
486
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
487


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
488
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
489

ACCESS R IGHTS
User Group Access
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?

Notifications
490
21.01.2016

Others
21.01.2016
159
section.
491

13 Cisco IP SLA Sensor
6.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
492
13.11.2015

Cisc o IP SLA Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c isc o_ip_sla.png
Remarks
For a general introduction to the technology behind Quality of Service monitoring, please
see manual section Monit oring Qualit y of Service 3017 .
13.11.2015
493

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 in this dialog are valid for all of the sensors
that are created.
IP SLA SPECIFIC
IP SLAs
Select the IP SLAs you want to add a sensor for. You see a list with
head.
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)
494
13.11.2015

IP SLA SPECIFIC
pat h-jit t er (23)
Note: 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 which 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.
Note: Packet Loss values are summarized, but have no explicit
channel for SourceDestination or DestinationSource values
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
13.11.2015
495


Priority
IP SLA SPECIFIC
ID
Type
Name (Tag)
These fields show SLA specific settings which the queried SLA
device provides. 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.
Owner
Frequency
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
496
13.11.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
13.11.2015
497

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
498
13.11.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
13.11.2015
499


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
500
13.11.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
13.11.2015
159
section.
501

14 Citrix XenServer Host Sensor
6.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.
502
09.07.2015

Citrix XenServ er Host Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c itrix_xenserv er_host.png
Remarks
The parent device must be a Citrix XenServer version 5.0 or later.
The parent device has to represent one host server of your XenServer pool
504
Requires credentials for Xen servers to be defined for the device you want to use the
sensor on.
09.07.2015
503

Requires
504
Knowledge Base: Does PRTG impair my Citrix environment?

Monitoring a XenServer Pool

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

this sensor.
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 in this dialog are valid for all of
the sensors that are created.
504
09.07.2015

HOST SETTINGS
Host
Select the hosts you want to add a sensor for, including the ones
that are not running. You see a list with the names of all items
which are available to monitor. Select the desired items by adding
check marks in front of the respective lines. PRTG creates one
sensor for each selection. You can also select and deselect all
items by using the check box in the table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
09.07.2015
505

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 for debugging. Wrong usage can result
in incorrect monitoring data!
Name
Shows the name of the host that this sensor monitors.

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
506

09.07.2015

Inherited Settings
described below.
09.07.2015
507

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
508
09.07.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
09.07.2015
509


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
510
09.07.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

09.07.2015
511

Notifications
Others
512
159
section.
09.07.2015

15 Citrix XenServer Virtual Machine Sensor
6.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
09.07.2015
513

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c itrix_xenserv er_v irtual_mac hine.png
Remarks
The parent device must be a Citrix XenServer (version 5.0 or later).
The parent device has to represent one host server of your XenServer pool
514
Requires credentials for Xen servers to be defined for the device you want to use the
sensor on.
Requires
514

Monitoring a XenServer Pool

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

this sensor.
Add Sensor
later.
Note: PRTG requests a full list of all virtual machines configured on the Xen server. Therefore, it
may take a few seconds before the dialog is loaded.
514
09.07.2015

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:
VIR TU AL MACHINE SETTINGS

Virtual Machine
Select the Virtual Machines (VM) you want to add a sensor for,
including the ones that are not running. You see a list with the
names of all items which are available to monitor. Select the
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
09.07.2015
515


Priority

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 for debugging. 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.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
516
09.07.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
09.07.2015
517

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
518
09.07.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
09.07.2015
519


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
520
09.07.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

09.07.2015
521

Notifications
Others
522
159
section.
09.07.2015

16 Cloud HTTP Sensor
6.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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c loud_http.png
15.04.2016
523

Remarks
The server on which the PRTG probe 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.
The URL you monitor 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
2883
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, please refer
to the manual section Sensor Channels Set t ings 2711 .
Add Sensor
later.
Sensor Settings

Sensor Name
524

171 .
15.04.2016


Parent Tags
Tags

default value.
Priority
HTTP SETTINGS
URL
Enter the URL the sensor connects to. It has to be URL encoded! If
you enter an absolute URL, the sensor uses this address
independently from the IP address/DNS name setting of the
device on which you create this sensor. You can enter an URL
leading to a webpage (to measure the page source code's loading
time), or enter the URL of an image or of another page asset to
measure this element's availability and loading time.
PRTG uses a smart URL replacement which allows you to use the
parent device's IP address/DNS name setting as part of the URL.
For more information, please see section Smart URL Replacement
below.
Request Method
Choose an HTTP request method to determine how the sensor will

request the given URL.
GET: Request the website directly, like browsing the web. We
recommend using this setting for a simple check of a web page.
POST: Send post form data to the URL. If this setting is chosen,
you must enter the data that will be sent in the Post dat a field
below.
15.04.2016
525

HTTP SETTINGS
HEAD: Only request the HTTP header from the server; without
the actual web page. Although this saves bandwidth since less
data is transferred, it is not recommended because the measured
request time is not the one experienced by your users and you
might not be notified for slow results or timeouts.
Postdata
This field is only visible when you select the POST Request
Met hod setting above. Enter the data part for the POST request
here. Note: No XML is allowed here!
Timeout (Sec.)
Enter a timeout in seconds for the server request. If the reply

takes longer than this value defines, the PRTG will cancel the
request and shows an error message. The maximum timeout value
is 5 seconds.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
526

15.04.2016

Inherited Settings
described below.
15.04.2016
527

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
528
15.04.2016

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

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
15.04.2016
529


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
530
15.04.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Smart URL Replacement

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

Note: Smart URL replacement does not work for sensors running on the "Probe Device".
More

Notifications
Others
532
159
section.
15.04.2016

17 Cloud Ping Sensor
6.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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c loud_ping.png
Remarks
The server on which the PRTG probe 90 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.
15.04.2016
533

The address you define in the parent device settings 324 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.
2883
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
534
15.04.2016


Priority
PING SETTINGS
Packet Size (Bytes)
Enter the packet size in bytes for the Ping. You can choose any
value between 1 and 10000. We recommend 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
Primary Channel

Graph Type

for each channel.
15.04.2016
535

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
536
15.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
15.04.2016
537

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

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
538
15.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.04.2016
539

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
540
15.04.2016

Others
15.04.2016
159
section.
541

18 Cluster Health Sensor
6.8.18 Cluster Health Sensor

The Cluster Health sensor monitors the health of a PRTG cluster
system health status.
87
and indicates PRTG's own
It measures various internal system parameters of the cluster system:

Number of connects per minute
Cluster in- and outgoing messages per minute
Number of connected and disconnected cluster nodes.
ClusterState Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c lusterstate.png
Remarks
PRTG creates this sensor automatically with a cluster installation. You cannot delete or add it
manually.
If at least one cluster node is disconnected, this sensor shows a Down status by default.
On the sensor's Overview tab you can review the states of each cluster node.
On the monitoring data review tabs 140 you can choose the cluster member of which you
want to show data (or of all nodes).
542
09.07.2015

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type
09.07.2015
543

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
544
09.07.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
09.07.2015
545

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
546
159
section.
09.07.2015

19 Common SaaS Sensor
6.8.19 Common SaaS Sensor

The Common SaaS Sensor monitors the availability of several Software as a Service (SaaS)
providers. Because your business processes more and more depend 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
31.08.2015
547

Common SaaS Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c ommon_saas.png
Remarks
The server on which 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 185 or delete 196 this sensor manually
to avoid error messages.
2883
548
31.08.2015

Add Sensor
later.
Select which SaaS providers you want to monitor. The sensor creates 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 which are available to monitor.
Select the desired items by adding check marks in front of the
respective lines. The sensor creates on channel for each selection.
You can also select and deselect all items by using the check box
in the table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
31.08.2015
549


Tags

default value.
Priority
COMMON SAAS SPECIFIC

Period (Interval)
Define the scanning interval of this sensor. The period you choose
here specifies how often the sensor requests the target services.
Choose between:
15 minut es
30 minut es
1 hour
4 hours
6 hours
12 hours
24 hours
Note: This sensor cannot inherit scanning intervals nor use other
intervals than given here.
DEBU G OPTIONS
Sensor Result

between:
550
31.08.2015

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
31.08.2015
551


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
552
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
553

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
554
159
section.
31.08.2015

20 Core Health Sensor
6.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 which have an impact on the
stability of the system:
Health: This index value sums up the core state into a value between 100% (healthy) and 0%
(failing). Frequent or repeated health values below 100% should be investigated.
Age of Code: This channel shows the passed time 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 2918 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 usually should stay below
50%.
Handles: This is a counter for the data structures of the operating system. It is responsible
for internal resource management. Repeated obviously increasing values should be
investigated.
Committed Memory: This channel shows the amount of memory committed to the PRTG core
server as reported by the memory manager.
Free Page File Memory: This channel shows the amount of free page file memory currently
available on the system. Page file memory is aggregated RAM and the size of page file. It is
the maximum amount of memory that is available on the system to be used for all currently
running processes. If it gets too low the system can crash, at least some applications will
throw "Out of memory" errors.
Free Physical Memory: This channel shows the amount of free physical memory currently
available on the system. This is the RAM that is physically built-in in the computer. If it gets
too low the system will become very slow and PRTG is not usable in a reasonable way
anymore. It can happen that some sensors will not be displayed correctly in that case, they
will appear disabled (grayed out).
Free Virtual Memory: This channel shows the accessible address space on the system for
PRTG. PRTG cannot use more memory than reported here, independently from free page file
and physical memory. On a 32bit OS (operating system) the maximum is 2 GB (3 GB with
special settings under Windows); on a 64bit OS it is 4 GB if PRTG is running as 32bit version,
and unlimited as 64bit version (only Core). If free virtual memory gets too low, PRTG will
throw "Out of memory" errors or the message "not enough storage to process this
command" (visible in the Core log).
Maintenance Days: This channel shows the remaining maintenance days of your PRTG
license. Please renew your maintenance on time to be sure to get your PRTG updates.
Threads: This channel shows the number of program parts which are currently running
simultaneously. This number can increase with heavy load. The number should not exceed
100 in normal operation.
Raw Data Buffer: This channel shows how much raw data is temporarily stored on the
physical memory while I/O operations on the disk. Usually, this value should be 0 (or very
low). Investigate increasing values.
11.03.2016
555

Core Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/c ore_health.png
Remarks
PRTG creates this sensor automatically and you cannot delete it.
You can set up this sensor only on a Local Probe device!
Sensor Settings
556
11.03.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
11.03.2016
557

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
558
11.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
11.03.2016
559

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
560
11.03.2016


Notifications
Others
11.03.2016
159
section.
561

21 Dell PowerVault MDi Logical Disk Sensor
6.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.
Total number of I/O operations
Number of current and maximum I/O operations per second
Current and maximum disk speed
Read and cache hit percentages
sensor setup.
Dell PowerVault MDi Logic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dell_powerv ault_mdi_logic al_disk.png
Remarks
Works with Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or MD3820i,
and might support other models.
562
21.01.2016

Requires 563 Dell Modular Disk Storage Manager on the probe system. Please see the
Knowledge Base: Where do I find the Dell PowerVault Modular Disk Storage Manager for use
with my MDi SAN?
Needs the IP address of the Storage Area Network (SAN) defined in the parent device
settings.
Requirement: Dell Modular Disk Storage Manager

This sensor requires an installation of the Dell "Modular Disk Storage Manager" program. You
have to install it on the computer running the PRTG probe: Either on the local system (on every
node, if on a cluster probe), or on the system running the remote probe 3109 . For details about
setup, please see More section below.
Note: Please create this sensor on a device which has the SAN's IP address configured in the
"IP address/DNS name" field.
Add Sensor
later.
Select which virtual disks you want to monitor. PRTG creates one sensor for each disk you
select in the Add Sensor dialog. The settings you choose in this dialog are valid for all of the
SENSOR SETTINGS
Virtual Disks
Select the disks you want to add a sensor for. You see a list with
head.
Sensor Settings
21.01.2016
563


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
Virtual Disk
Shows the name of the virtual disk that this sensor monitors. Once
the sensor anew.
Sensor Result

between:
564
21.01.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
565

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
566
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
567


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
568
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
569

More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?

Notifications
Others
570
159
section.
21.01.2016

22 Dell PowerVault MDi Physical Disk Sensor
6.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.
It can show following:
Mode of the physical disk
Status of the physical disk
The sensor shows these channels as reported in the Modular Disk Storage Manager. Status
and mode combined indicate the particular status of a RAID controller physical disk. The table
below provides you the status description according to the Dell documentation:
"St at us" Channel
"Mode" Channel
Descript ion
Optimal (status: up)
Unassigned (status:
up)
The physical disk in the indicated slot is

unused and available to be configured.
Assigned (status: up)

configured as part of a disk group.
Hot Spare Standby

(status: up)

configured as a hot spare.
Hot Spare In Use

(status: up)
The physical disk in the indicated slot is in

use as a hot spare within a disk group.
Assigned
The physical disk in the indicated slot has

been failed because of an unrecoverable
error, an incorrect drive type or drive size,
or by its operational state being set to
failed.
Failed (status: down)
Unassigned
Hot Spare In Use
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
(status: down)
Assigned
A SMART error has been detected on the

physical disk in the indicated slot.
Unassigned
Hot Spare In Use
Hot Spare Standby
None (status:
warning)
11.03.2016
None (status: warning)
The indicated slot is empty, or the array

cannot detect the physical disk.
571

"St at us" Channel
"Mode" Channel
Descript ion
Undefined (status:
down)
Dell PowerVault MDi Phy sic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dell_powerv ault_mdi_phy sic al_disk.png
Remarks
Works with Dell PowerVault MD3000i, MD3420, MD3620i, MD3000f, MD3620f, or MD3820i,
and might support other models.
Requires 571 Dell Modular Disk Storage Manager on the probe system. Please see the
Knowledge Base: Where do I find the Dell PowerVault Modular Disk Storage Manager for use
with my MDi SAN?
Needs the IP address of the Storage Area Network (SAN) defined in the parent device
settings.
This sensor supports devices with one drawer of hard-drives only. Multiple drawers are not
supported and prevent sensor creation.
572
11.03.2016

Requirement: Dell Modular Disk Storage Manager

This sensor requires an installation of the Dell "Modular Disk Storage Manager" program. You
have to install it on the computer running the PRTG probe: Either on the local system (on every
node, if on a cluster probe), or on the system running the remote probe 3109 . For details about
setup, please see More section below.
Note: Please create this sensor on a device which has the SAN's IP address configured in the
"IP address/DNS name" field.
Add Sensor
later.
Select the physical disks you want to monitor. PRTG creates one sensor for each disk you
SENSOR SETTINGS
Physical Disks
head.
Sensor Settings
11.03.2016
573


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
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.
Sensor Result

between:
574
11.03.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
11.03.2016
575

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
576
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
577


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
578
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
11.03.2016
579

More
Where do I find the Dell PowerVault Modular Disk Storage Manager for use with my MDi SAN?

Notifications
Others
580
159
section.
11.03.2016

23 DHCP Sensor
6.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. On sensor
creation, choose the network card on the probe system which will be used to send the
broadcast message.
If a server responds, the sensor shows the following:
Address of the server and the offered IP in the sensor message. You can check the server's
response using Regular Expressions 3105 .
Response time (msec)
Lease time given by the server (in days)
DHCP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dhc p.png
Remarks
You can create this sensor only on a probe device (either local probe, a remote probe, or a
cluster probe).
Note: The probe device on which you create a DHCP sensor must have a static IP address. It
must not get its IP address from DHCP because this can cause a DHCP failure which will result
in a severe issue for the probe device and you risk losing monitoring data.
Note: 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?
15.04.2016
581

23 DHCP Sensor
Add Sensor
later.
Select the desired network interfaces to monitor DHCP servers. PRTG creates one sensor for
each network interface you choose in the Add Sensor dialog. The settings you choose in this
dialog are valid for all of the sensors that are created.
DHCP SPECIFIC
Specify Network
Interface
Select the network adapters you want to add a sensor for. You
see a list with the names of all items which are available to monitor.
respective lines. PRTG creates one sensor for each selection. You
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
582
15.04.2016

23 DHCP Sensor

Tags

default value.
Priority
DHCP SPECIFIC
MAC
Shows the MAC address of the network adapter that is used to

send the broadcast message to the network. Once a sensor is
anew.
Client IP
Specify if you want to check the returned client IP with a regular

expression. Choose between:
Don't check: The IP will only appear in the sensor message
without further processes.
Check: Enter the regular expression you want to use below.
Client IP Must Include
This field is only visible if you chose to check the client IP above. In
the response of the DHCP server, search using a regular
expression. If the answer for the client IP does not contain the
defined string, the sensor shows a Down status 135 .
For example, enter 10\.0\.5\..* to make sure any answering DHCP
server returns an client IP address starting with "10.0.5.". If it does
not, the sensor will show an error. For more details, see Regular
Expressions 3105 section. Leave empty to not use this field.
Client IP Must Not

Include
15.04.2016
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 contains the defined
string, the sensor shows a Down status.
583

23 DHCP Sensor
DHCP SPECIFIC
See example above. For more details, see Regular Expressions
section. Leave empty to not use this field.
Server IP
3105
Specify if you want to check the returned server IP with a regular

expression. Choose between:
Don't check: The IP only appears in the sensor message without
further processes.
Check: Enter the regular expression you want to use below.
Server IP Must Include
This field is only visible if you choose to check the server IP above.
expression. If the answer for the server IP does not contain the
defined string, the sensor shows a Down status.
Server IP Must Not

Include
3105
This field is only visible if you choose to check the server IP above.
expression. If the answer for the server IP contains the defined
string, the sensor shows a Down status.
3105
Timeout (Sec.)

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 169 . Choose between:
Ignore: Do not write a log entry if the DHCP server changes.
Writ e log ent ry : Write an entry to the system Logs whenever
the DHCP server changes between two sensor scans.
Note: Regardless of this setting, those entries will always be added
to the sensor Log.
Offered IP Change
584
If the IP address offered by the DHCP server changes between two

sensor scans, PRTG can write an entry to the system Logs 169 .
Choose between:
15.04.2016

23 DHCP Sensor
DHCP SPECIFIC
Ignore: Do not write a log entry if the offered IP address
changes.
Writ e log ent ry : Write an entry to the system Logs whenever
the DHCP server offers a different IP address compared to the
last sensor scan.
Note: Regardless of this setting, those entries will always be added
to the sensor Log.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
15.04.2016
585

23 DHCP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
586
15.04.2016

23 DHCP Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
15.04.2016
587

23 DHCP Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
588
15.04.2016

23 DHCP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: How can I monitor a DHCP server in a specific network if there are several
DHCP networks?

Notifications
15.04.2016
589

23 DHCP Sensor
Others
590
159
section.
15.04.2016

24 DNS Sensor
6.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 turns to a Down status if the DNS server does not resolve a given domain name correctly.
DNS Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dns.png
Add Sensor
later.
Sensor Settings
27.10.2015
591

24 DNS Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
DNS SPECIFIC
Timeout (Sec.)

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
Note: The sensor connects to the IP Address or DNS Name value
of the device 324 on which you create it.
592
27.10.2015

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 324 . 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.
Sensor Result

between:
27.10.2015
593

24 DNS Sensor
DNS SPECIFIC
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
594
27.10.2015

24 DNS Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
27.10.2015
595

24 DNS Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
596
27.10.2015

24 DNS Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
27.10.2015
597

24 DNS Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
598
159
section.
27.10.2015

25 Docker Container Status Sensor
6.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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/doc ker_c ontainer_status.png
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?
21.01.2016
599

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 in this dialog are
DOCKER SPECIFIC
Container
Select the containers you want to add a sensor for. You see a list
head.
Sensor Settings
600
21.01.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
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. See section More 608 for a link
to the Knowledge Base article about how to create a Docker
certificate.
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-----
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. See section More 608 for a link
to the Knowledge Base article about how to create a Docker
certificate.
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-----
21.01.2016
601

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
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
602
21.01.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
21.01.2016
603

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
604
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
605


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
606
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
607

More
Knowledge Base: How can I create private key and certificate for the Docker sensor?

Notifications
Others
608
159
section.
21.01.2016

26 Dropbox Sensor
6.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
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/dropbox.png
Remarks
The minimum scanning interval for this sensor type is 30 minut es.
For details about OAuth2 authentication, please see manual section Aut hent icat ion Using
OAut h2 617 .
Add Sensor
later.
PRTG requires OAuth2 authorization before you can actually add this sensor type. Provide the
requested credentials in the appearing window. The following settings for this sensor differ in
08.10.2015
609

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, please see section Aut hent icat ion Using
OAut h2 617 .
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. Please follow the steps there 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 781 .
Note: It is mandatory to connect this sensor to your Dropbox
account to create this sensor. Please complete the OAuth
approach first to get the OAuth code.
Sensor Settings

Sensor Name

171 .
Parent Tags
610
08.10.2015

26 Dropbox Sensor

Tags

default value.
Priority
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
Primary Channel

Graph Type

for each channel.
08.10.2015
611

26 Dropbox Sensor
SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
612
08.10.2015

26 Dropbox Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
08.10.2015
613

26 Dropbox Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
614
08.10.2015

26 Dropbox Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
08.10.2015
615

26 Dropbox Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
616
08.10.2015

26 Dropbox Sensor
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. In general, the authorization approach of PRTG
using OAuth2 works like this:
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. This opens a new browser window 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.
Note: 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 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.
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.
Note: The code is valid only 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 getting the authorization code, PRTG requests 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 at your account. It is not necessary to use the original account
credentials anew. The used tokens are refreshed automatically from time to time.
08.10.2015
617

26 Dropbox Sensor

Notifications
Others
618
159
section.
08.10.2015

27 Enterprise Virtual Array Sensor
6.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.
Remarks
You have to explicitly specify the credentials of the EVA in the sensor settings.
24.03.2015
619

Requires
below).
620
the HP Command View EVA Software on the probe system (or the alternative
Knowledge Base: Do I really have to install the whole Command View on the probe to use
the EVA sensor?
Requirement: Command View

The EVA sensor needs the HP Command View EVA Software to be installed on the probe
system. If you do not want to install the whole command view tool, you can alternatively use
another approach. For details, please see section More 628 .
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 in this dialog are valid for all of the sensors that are created.
620
24.03.2015

EVA SETTINGS
Modules
Select the modules you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
621

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.
System
Shows further information about the monitored module. Once a

the sensor anew.
Module Type
Description
Sensor Result
Define what will be done with the results the sensor receives.
Choose between:
Discard sensor result : Do not store the results.
[ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
SENSOR DISPLAY
Primary Channel

Graph Type
622
24.03.2015

SENSOR DISPLAY
for each channel.
Stack Unit
24.03.2015

623

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
624
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
625


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
626
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
627

More
Knowledge Base: Do I really have to install the whole Command View on the probe to use the
EVA sensor?

Notifications
Others
628
159
section.
24.03.2015

28 Event Log (Windows API) Sensor
6.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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ev ent_log_windows_api.png
Remarks
Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
Add Sensor
later.
Sensor Settings
24.03.2015
629


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
WINDOWS API EVENT LOG SPECIFIC

Log File
Specify the log file that this sensor monitors. The Windows event
log provides several different log files which PRTG shows here.
Choose between:
Applicat ion
Sy st em
Securit y
Direct ory Service
DNS Server
630
24.03.2015

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
type cannot be processed. Choose between the following event
types:
Any
Error
Warning
Informat ion
Securit y Audit Success
Securit y Audit Failure
Filter by Source
Filter all received events for a certain event source. If you enable
this option, this sensor processes only messages that match the
defined value. Choose between:
Off: Do not filter by event source.
On: Enable filtering by event source.
Match String (Event

Source)
This field is only visible if you enable source filtering above. Enter a
source from which the events come from. Only events from a
source matching this string are regarded, other events are ignored.
Please enter a string.
Filter by ID
Filter all received events for a certain event ID. If you enable this
option, this sensor processes only messages that match the
defined value(s). Choose between:
Off: Do not filter by event ID.
On: Enable filtering by event ID.
Match Value (Event ID)
This field is only visible if you enable ID filtering above. Enter an

event ID which the events must have. Only events with an ID that
matches this value are regarded.
Note: The Event Log (Windows API) Sensor 629 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.
24.03.2015
631


Note: The WMI Event Log Sensor
one ID.
Filter by Category
2469
supports filtering for only
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

Category)
This field is only visible if you enable category filtering above. Enter
a category which the events must have. Only events with a
category that matches this string are regarded. Please enter a
string.
Filter by User
Filter all received events for a certain event user. If you enable this
Off: Do not filter by event user.
On: Enable filtering by event user.
Match String (Event

User)
This field is only visible if you enable user filtering above. Enter a
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

Computer)
This field is only visible if you enable computer filtering above.

Enter a computer name which the events must be assigned to.
Only events with a computer name that matches this string are
regarded. Please enter a string.
Filter by Message
Filter all received events for a certain event message. If you enable
Off: Do not filter by event message.
On: Enable filtering by event message.
632
24.03.2015


Match String (Event
Message)
This field is only visible if you enable message filtering above. Enter
a message that the event must contain. Only events with a
message matching this string are regarded. Please enter a string.
Note: The Event Log (Windows API) Sensor always performs a substring match. Please do not
use any placeholder character. For example, enter RAS for any event source containing this
string in partial or whole form.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
633

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
634
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
635


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
636
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
637

Others
638
159
section.
24.03.2015

29 Exchange Backup (Powershell) Sensor
6.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:
Past time since the last full backup
Past time since the last copy backup
If a backup is currently running
sensor setup.
Exc hange Bac kup (Powershell) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_bac kup.png
Remarks
The parent device for this sensor must be the Exchange server (version 2010 or higher) that
hosts the database you want to monitor.
sensor on.
21.01.2016
639

Requires 640 Remote PowerShell and Remote Exchange Management Shell on the target
servers and PowerShell 2.0 on the probe system.
Requires
640
the FQDN of the Exchange server in the parent device settings
Requires
640
324
Knowledge Base: PowerShell Sensors: FAQ
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 which you want to monitor. Also ensure you have installed PowerShell 2.0 or
later on your probe machine.
Note: In larger environments, the default memory limit for the remote shell might be insufficient
and you might see the error message "The WSMan provider host process did not return a
proper response". In this case, increase the memory limit for Remote PowerShell.
For more information, please see the Knowledge Base article http://kb.paessler.com/en/
topic/44453 (see also section More below).
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, please see the Knowledge Base article http://kb.paessler.com/

this sensor.
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 in this dialog are
640
21.01.2016

SENSOR SETTINGS
Exchange Databases
Select the databases you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
21.01.2016
641

SENSOR SETTINGS
Database
Shows the name of the monitored database. Once a sensor is

anew.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
642
21.01.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
21.01.2016
643

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
644
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
645


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
646
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
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?
21.01.2016
647


Notifications
Others
648
159
section.
21.01.2016

30 Exchange Database (Powershell) Sensor
6.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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_database.png
Remarks
sensor on.
Requires
650
Requires
650
324

Knowledge Base: How can I monitor additional values of Exchange databases?
11.03.2016
649




this sensor.
Add Sensor
later.
650
11.03.2016

SENSOR SETTINGS
Exchange Databases
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
11.03.2016
651

SENSOR SETTINGS
Database

anew.
AutoRemount
Database
Define if you want the sensor to try to remount the database

automatically if it is unmounted. Choose between:
Try t o remount
Just report t he current reading and keep unmount ed
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
652
11.03.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
11.03.2016
653

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
654
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
655


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
656
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
11.03.2016
657

More

Notifications
Others
658
159
section.
11.03.2016

31 Exchange Database DAG (Powershell) Sensor
6.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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_database_dag.png
21.01.2016
659

Remarks
sensor on.
Requires
660
Requires
660
324




this sensor.
660
21.01.2016

Add Sensor
later.
SENSOR SETTINGS
Exchange Databases
head.
Sensor Settings

Sensor Name
21.01.2016

171 .
661


Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
Database

anew.
Sensor Result

between:
662
21.01.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
663

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
664
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
665


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
666
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
21.01.2016
667


Notifications
Others
668
159
section.
21.01.2016

32 Exchange Mail Queue (Powershell) Sensor
6.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
See section More 677 below for a link to an explanation of the transport queue types. Which
channels the sensor actually shows might depend on the monitored device and the sensor
setup.
Exc hange Mail Queue (Powershell) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_mail_queue.png
Remarks
sensor on.
21.01.2016
669

Requires
670
Requires
670
324



this sensor.
Add Sensor
later.
Select the roles you want to monitor. PRTG creates one sensor for each role you choose in
that are created.
670
21.01.2016

SENSOR SETTINGS
Hub-Transport or Edge- Select the roles you want to add a sensor for. You see a list with
Server
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
21.01.2016
671

SENSOR SETTINGS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
672

21.01.2016

Inherited Settings
described below.
21.01.2016
673

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
674
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
675


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
676
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: Types of Transport Queues in Microsoft Exchange
21.01.2016
677


Notifications
Others
678
159
section.
21.01.2016

33 Exchange Mailbox (Powershell) Sensor
6.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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_mailbox.png
Remarks
sensor on.
21.01.2016
679

Requires
680
324
Requires elevated rights for the user of this sensor on the Exchange system. It is not
sufficient to have administrator rights. For details, please see the Knowledge Base: I have
problems with the PowerShell Exchange sensors, what can I do? (solution (2) in the reply)
Requires
680



this sensor.
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 in this dialog are valid
680
21.01.2016

SENSOR SETTINGS
Mailboxes
Select the mailboxes you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
21.01.2016
681

SENSOR SETTINGS
Mailbox Name
Shows the name of the monitored mailbox. Once a sensor is

anew.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
682
21.01.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
21.01.2016
683

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
684
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
685


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
686
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
21.01.2016
687


Notifications
Others
688
159
section.
21.01.2016

34 Exchange Public Folder (Powershell) Sensor
6.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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exc hange_public _folder.png
Remarks
sensor on.
Requires
21.01.2016
690
324
689

Requires
690



this sensor.
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 in this dialog are valid
690
21.01.2016

SENSOR SETTINGS
Public Folder
Select the folders you want to add a sensor for. You see a list with
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
21.01.2016
691

SENSOR SETTINGS
Public Folder
Shows the name of the monitored folder. Once a sensor is

anew.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
692

21.01.2016

Inherited Settings
described below.
21.01.2016
693

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
694
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
695


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
696
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
21.01.2016
697


Notifications
Others
698
159
section.
21.01.2016

35 EXE/Script Sensor
6.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 PRTG's Application Programming Interface (API). For details about the return value format
please see the Applicat ion Programming Int erface (API) Definit ion 3086 .
One value returned by the executable file or script (in one channel only)
Execution time
EXE/Sc ript Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exe_sc ript.png
Remarks
Note: The executable or script file must be stored on the system of the probe the sensor is
created on: If used on a remote probe, the file must be stored on the system running the
remote probe. In a cluster setup, please copy the file to every cluster node.
Note: If you want to execute a custom Windows Management Instrumentation Query
Language (WQL) script, please use the WMI Cust om Sensor 2448 .
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
09.07.2015
699

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?
Add Sensor
later.
700
09.07.2015

SENSOR SETTINGS
Script
Select an executable file from the list. The sensor will execute it
with every scanning interval.
In this list, files in the corresponding \Cust om Sensors\EX E subdirectory of the probe system's PRTG program directory are shown
(see Dat a St orage 3135 ). In order for the files to appear in this list,
store them into this folder ending in BAT, CMD, DLL, EXE, PS1, or
VBS. To show the expected values and sensor status, your files
must use the right format for the returned values (in this case,
value:message to standard output). The exit code of the file
determines the sensor status 135 .
For detailed information on how to build custom sensors and for
the expected return format, please see the API documentation
(Applicat ion Programming Int erface (API) Definit ion 3086 ). There,
find detailed information the the "Custom Sensors" tab.
Note: Please do not use the folder \Custom Sensors\Powershell
Scripts to store your files. This remnant from previous software
versions is not used any more and may usually be deleted.
Note: When using custom sensors on the Clust er Probe, please
copy your files to every cluster node installation.
Value Type
Define what kind of values your executable or script file gives

back. Choose between:
Int eger: An integer is expected as return value. If the script
gives back a float, PRTG will display the value 0.
Float : A float is expected as return value, with a dot (.) between
pre-decimal position and decimal places. In this setting, the
sensor will also display integer values unless they produce a
buffer overflow.
Count er: Your script returns an integer which increases. PRTG
will show the difference between the values of two sensor
scans.
Note: A counter must return an integer, float is not supported
here!
Channel Name
Enter a name for the channel in which the sensor shows returned
values. This is for display purposes only. Please enter a string.
Unit String
Enter a string that describes the unit of the returned values. This is
for display purposes only. Please enter a string.
Sensor Settings
09.07.2015
701


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
EXE/Script
Shows the executable or script file that the sensor executes with
each sensor scan as defined on sensor creation. Once a sensor is
anew.
Parameters
If your executable or script file catches command line parameters,

you can define them here. You can use placeholders as well. For a
full list of all placeholders please see the API documentation
(Applicat ion Programming Int erface (API) Definit ion 3086 ).
702
09.07.2015

SENSOR SETTINGS
Note: Please make sure you write the placeholders in quotes to
ensure that they are working properly if their values contain
blanks. Use single quotation marks ' ' with PowerShell scripts, and
double quotes " " with all others. Please enter a string or leave the
field empty.
Environment
Choose if PRTG's command line parameters will also be available as

environment parameters.
Default Environment : Do not provide PRTG placeholders' values
in the environment. Choose this secure option if you are not
sure.
Set placeholders as environment values: From within your
executable or script, the values of PRTG's command line
parameters will be available via environment variables. For
example, you can then read and use the current host value of
the PRTG device this EXE/script sensor is created on from within
your script. This option can mean a security risk, because also
credentials are provided in several variables. For a full list of all
available variables please see the API documentation
Security Context
Define the Windows user account that the sensor uses to run the
executable or script file. Choose between:
Use securit y cont ext of probe service: Run the selected file
under the same Windows user account the probe runs on. By
default, this is the Windows system user account (if not manually
changed).
Use Windows credent ials of parent device: Use the Windows
user account defined in the settings of the parent device this
sensor is created on. Please go to parent device settings 324 of
this sensor to change these Windows credentials.
Mutex Name
Define any desired mutex name for the process. All EXE/Script
sensors having the same mutex name will be executed serially (not
simultaneously). This is useful if you use a lot of sensors and want
to avoid high resource usage caused by processes running
simultaneously. For links to more information, please see the More
709 section below. Please enter a string or leave the field empty.
Timeout (Sec.)

09.07.2015
703

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
Note: The sensor cannot handle string values.
If Value Changes
Define what this sensor will do when the sensor value changes.
You can choose between:
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 2719 whenever the sensor value changes.
EXE Result
Define what this sensor will do with the result that the executable
file gives back. Choose between:
Discard EX E result : Do not store the requested web page.
Writ e EX E result t o disk: Store the last result received from the
script with the file name "Result of Sensor [ID].txt" to the "Logs
(Sensors)" directory (on the Master node, if in a cluster). This is
for debugging purposes. The file will be overridden with each
Writ e EX E result t o disk in case of error: Store the last result
received from the script only if the sensor is in a down status.
The file name is "Result of Sensor [ID].txt" in the "Logs (Sensors)"
directory. Enable this option if you do not want failures to be
overwritten by a following success of the script.
SENSOR DISPLAY
Primary Channel

Graph Type
704
09.07.2015

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
09.07.2015
705

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
706
09.07.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
09.07.2015
707


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
708
09.07.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Information about custom scripts and executables
Applicat ion Programming Int erface (API) Definit ion
3086
2707
Knowledge Base: How and Where Does PRTG Store its Data?
Knowledge Base: For which sensor types do you recommend Windows Server 2012 R2 and
why?
09.07.2015
709


Notifications
Others
710
159
section.
09.07.2015

36 EXE/Script Advanced Sensor
6.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. For details about the return value format please see the
Applicat ion Programming Int erface (API) Definit ion 3086 .
The sensor can show values returned by the executable file or script in multiple channels.
EXE/Sc ript Adv anc ed Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/exe_sc ript_adv anc ed.png
Remarks
712
officially.
Note: The executable or script file must be stored on the system of the probe the sensor is
created on: If used on a remote probe, the file must be stored on the system running the
remote probe. In a cluster setup, please copy the file to every cluster node.
Note: If you want to execute a custom Windows Management Instrumentation Query
Language (WQL) script, please use the WMI Cust om Sensor 2448 .
27.01.2016
711

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 3135 ). 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.
find detailed information on the Cust om Sensors tab.
Note: Please do not use the folder \Custom Sensors\Powershell
Scripts to store your files. This remnant from previous software
versions is not used any more and may usually be deleted.
712
27.01.2016

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
EXE/Script
27.01.2016
Shows the executable or script file that the sensor executes with
each scan as defined on sensor creation. Once a sensor is created,
713

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 please see the API documentation
field empty.
Environment
Choose if PRTG's command line parameters will also be available as

environment parameters.
Default Environment : Do not provide PRTG placeholders' values
in the environment. Choose this secure option if you are not
sure.
Set placeholders as environment values: From within your
executable or script, the values of PRTG's command line
parameters will be available via environment variables. For
example, you can then read and use the current host value of
the PRTG device this EXE/Script sensor is created on from within
your script. This option can mean a security risk, because also
credentials are provided in several variables. For a full list of all
available variables please see the API documentation
Security Context
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 navigate to parent device settings
324 of this sensor to change these Windows credentials.
Mutex Name
714
27.01.2016

SENSOR SETTINGS
Timeout (Sec.)

EXE Result
Define what the sensor will do with the results the executable file
gives back. Choose between:
Writ e EX E result t o disk: Store the last result received from the
script with the file name "Result of Sensor [ID].txt" to the "Logs
(Sensors)" directory (on the Master node, if in a cluster). This is
for debugging purposes. The file will be overridden with each
Writ e EX E result t o disk in case of error: Store the last result
received from the script only if the sensor is in a down status.
The file name is "Result of Sensor [ID].txt" in the "Logs (Sensors)"
directory. Enable this option if you do not want failures to be
overwritten by a following success of the script.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
27.01.2016
715

SENSOR DISPLAY
Stack Unit

Note: The St ack Unit option for stacking graphs will only work if you explicitly define the
same <unit> for at least two channels. For detailed information about sensor settings please
see the API documentation (Applicat ion Programming Int erface (API) Definit ion 3086 ).
Inherited Settings
described below.
716
27.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
27.01.2016
717


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
718
27.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
27.01.2016
719

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
720
27.01.2016

More
3086
2707
why?
Knowledge Base: How can I use meta-scans for custom EXE/Script sensors?

Notifications
Others
27.01.2016
159
section.
721

37 File Sensor
6.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
Past time since the file was modified the last time (in days, hours, and minutes, depending on
the elapsed time)
In contrast to the Folder sensor
file has changed.
741
, you can also monitor if the actual content of a specific
File Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/file.png
Remarks
To monitor files on a share, the "LanmanServer" Windows service must run on the target
computer.
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
722
27.04.2016

37 File Sensor
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
27.04.2016
723

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.txt 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.txt.
If the file is located on a network device, use the Uniform Naming
Convention (UNC) path without the server part (only enter share
\folder\file.txt). The server part (\\server\) is taken from the parent
device settings 324 of this sensor. Enter a valid path and file name.
Note: To provide any shares, the LanmanServer "Server" Windows
service must be running on the target computer.
Sensor Behavior
Specify when the sensor shows a Down status

between:
135
. Choose
Show 'Down' st at us if file does not exist : The sensor switches

into an error status if the file does not exist.
Show 'Down' st at us if file exist s: The sensor switches into an
error status 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

Stamp

content of the file's time stamp changes. Choose between:
724
27.04.2016

37 File Sensor
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
27.04.2016
725

37 File Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
726
27.04.2016

37 File Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
27.04.2016
727

37 File Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
728
27.04.2016

37 File Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
27.04.2016
729

37 File Sensor
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
730
159
section.
27.04.2016

38 File Content Sensor
6.8.38 File Content Sensor

The File Content sensor checks a text file (for example, log files) for certain strings and returns
the following:
Line number of the last match
Number of total matches.
Additionally, the sensor quotes matching lines in the sensor message field.
File Content Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/file_c ontent.png
Remarks
This sensor does not support UTF-16 encoded files! In this case, please try use a custom
sensor like the EX E/Script Sensor 699 or the EX E/Script Advanced Sensor 711 .
This sensor does not support binary files officially! 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.
To monitor files on a Windows share, the "LanmanServer" Windows service must run on the
target computer.
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.
27.04.2016
731

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
732
27.04.2016

SENSOR SPECIFIC
File Name
Enter the full path to the file that this sensor will monitor. For
example, enter C:\Windows\file.txt. 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.txt.
If the file is located on a network device, use the Uniform Naming
Convention (UNC) path without the server part (only enter share
\folder\file.txt). The server part (\\server\) is taken from the parent
device settings 324 of this sensor. Enter a valid path and file name.
Note: To provide any Windows shares, the LanmanServer "Server"
Windows service must run on the target computer.
Note: To monitor any Linux files, the folder with these files has to
be accessible via Server Message Block (SMB).
Note: If you define a file on your network here, please be aware
that this might produce high network traffic if you define PRTG to
query the entire file with every scanning interval below.
Search String
Define the string inside the log file you want to check for. The
input is not case-sensitive. Please enter a string.
Network Usage
Define in which way the sensor will transmit the target file to PRTG.
Choose between:
Only t ransmit t o PRTG new lines at t he end of t he file
(default ): This option improves the performance of the sensor. It
sends the whole file only with the first scan to PRTG. With the
following sensor scans, the sensor will only transmit lines which
were appended since the last scan. All other lines (which already
existed in the previous scan) are not sent. The sensor assumes
that they are unchanged and still counts them.
Note: This option is currently in beta status. Please do not
expect that it will work as expected in every usage scenario!
Alway s t ransmit t o PRTG t he ent ire file: The sensor sends the
whole file with every sensor scanning interval to PRTG. If this
results in too much traffic on the target system, we recommend
that you choose the new lines option.
Note: The sensor can transmit only newly added lines in the
following cases:
The file is bigger than at the previous scan, and
the last line in the file at the previous scan still has to be at the
same place in the file.
27.04.2016
733

SENSOR SPECIFIC
Note: The sensor supports Windows and Linux line endings (CRLF
resp. LF).
Search Method
Define the method you want to provide the search string with. The
pattern must be in one line and only the last matching line will be
given back. Choose between:
Simple st ring search: Search for a simple plain text expression.
Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 3105 section.
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. Choose between:
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.
If Value Changes
change.
Note: 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.
734
27.04.2016

DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
27.04.2016

735

Inherited Settings
described below.
736
27.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
27.04.2016
737


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
738
27.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
27.04.2016
739

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
740
159
section.
27.04.2016

39 Folder Sensor
6.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
Past time since the last change to a file in the folder ("newest file")
Past time since the oldest modification of a file in the folder ("oldest file")
Note: The Folder sensor counts all files in a folder, including hidden files.
Folder Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/folder.png
Remarks
This sensor counts all files in a folder, including hidden files.
To monitor files on a share, the "LanmanServer" Windows service must run on the target
computer.
PE032
09.07.2015
741

39 Folder Sensor
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
742
09.07.2015

39 Folder Sensor
FOLDER MONITOR
Folder Name
Enter the full path to the folder this sensor will monitor. For
example, enter C:\Windows. If the file is located on a network
device, use the Uniform Naming Convention (UNC) path without the
server part (you would only enter share\folder). The server part (\
\server\) is taken from parent device settings 324 of this sensor.
Please enter a valid path name.
Note: To monitor shares, the LanmanServer "Server" Windows
service must be running on the target computer.
Sub-Folder Recursion
Specify if the sensor will include subfolders in the folder

monitoring. Choose between:
Do not recurse sub-folders: Only monitor the folder specified
above and do not monitor its subfolders.
Monit or t he folder and it s sub-folders (use wit h caut ion!):
Monitor the folder specified above and all of its subfolders.
Note: Recursing subfolders in large directories with a high
number of branches may evoke timeout errors or performance
issues.
Monitor Folder
Changes

content of the folder changes. Choose between:
Ignore changes: Changes to the folder will not trigger a change
notification.
Trigger 'On Change' not ificat ion: The sensor will trigger a
change notification if a file changes its timestamp or filename, or
if there are new or deleted files.
Check of File Ages
Specify if the sensor will monitor the folder for certain file ages and
show a corresponding status 135 . 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

09.07.2015
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's status
change if the defined age is undercut respectively exceeded.
The value will be interpreted as days, hours, or minutes, according
743

39 Folder Sensor
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
744
09.07.2015

39 Folder Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
09.07.2015
745

39 Folder Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
746
09.07.2015

39 Folder Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
09.07.2015
747

39 Folder Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
748
09.07.2015

39 Folder Sensor
More

Notifications
Others
09.07.2015
159
section.
749

40 FTP Sensor
6.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
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ftp.png
Add Sensor
later.
Sensor Settings
750
20.04.2016

40 FTP Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SPECIFIC
Timeout (Sec.)

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 do not get a connection, please try another port number.
FTP Mode
Specify which FTP mode the sensor uses for the connection.
Choose between:
Use act ive mode
Use passive mode
We recommend that you use the default value. If you do not get a
connection, please try the passive mode.
20.04.2016
751

40 FTP Sensor
TR ANSPOR T-LEVEL SECU R ITY

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

between:
20.04.2016

40 FTP Sensor
DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
20.04.2016
753

40 FTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
754
20.04.2016

40 FTP Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
20.04.2016
755

40 FTP Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
756
20.04.2016

40 FTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
20.04.2016
159
section.
757

41 FTP Server File Count Sensor
6.8.41 FTP Server File Count Sensor

The FTP Server File Count sensor logs on to an FTP server and can monitor changes to files.
It can show the number of files available in the directory listing.
FTP Serv er File Count Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ftp_serv er_file_c ount.png
Remarks

this sensor.
758
09.07.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
09.07.2015
759

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
Note: When you use this method, this sensor does not use the IP
Address/DNS value of the parent device.
Note: You can add a port number to the URL by using a colon, for
example, ftp://10.0.0.1/upload:21
FTP Port
This field is only visible if you select the parent device method
above. Enter the number of the port to which this sensor
connects. Default port is 21.
FTP Folder
This field is only visible if you select the parent device method
above. Enter the name of the folder on the parent device that this
sensor monitors, for example, upload
Subfolder Recursion
This field is only visible if your select the parent device method
above. Define if the sensor additionally monitors the subfolders of
the FTP folder you specify above. Choose between:
Do not recurse subfolders: The sensor monitors only the
folder that you define above and ignores its subfolders.
Monit or t he folder and it s subfolders (use wit h caut ion!): The
sensor recursively checks all subfolders in addition to the folder
that you define above.
Note: Recursing subfolders in large directories with a high
number of branches may evoke timeout errors or performance
issues.
Username
Enter the username for the logon to the FTP server. Please enter a
string.
Password
Define the password for the logon to the FTP server. Please enter
a string.
File Count
Define which file the sensor counts. Choose between:
760
09.07.2015

SENSOR SETTINGS
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 762 .
Note: With the 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.
Note: This sensor type supports only explicit SSL.
If Value Changes
change.
DEBU G OPTIONS
Sensor Result

between:
09.07.2015
761

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
762
09.07.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
09.07.2015
763


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
764
09.07.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
09.07.2015
765

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
766
09.07.2015

More

Notifications
Others
09.07.2015
159
section.
767

42 Google Analytics Sensor
6.8.42 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/google_analy tic s_v 2.png
Remarks
OAut h2 778 .
Knowledge Base: Where do I find available Google Analytics metrics?
Add Sensor
later.
768
21.01.2016

GOOGLE CR EDENTIALS
This sensor type uses OAuth2 authentication to get access to your Google account. For
OAut h2 778 .
OAuth URL
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.
OAuth Code
authorization process for PRTG at your Google Analytics account.
Click OK to define the sensor settings 770 .
Note: 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
#10
You can create up to 10 different sensor channels for this sensor.

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).
please add the sensor anew. It is not possible to enable or disable
sensor channels after the creation of this sensor!
21.01.2016
769


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

Sensor Name

171 .
Parent Tags
Tags

default value.
770
21.01.2016


Priority
GOOGLE CR EDENTIALS
OAuth Code
to your Google Analytics account. 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.

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
Name
Enter a name for the channel in which the sensor shows the
results for the metric you choose below. Please enter a string.
Sensor Channel #x
Metric
Select a metric that you want to monitor. You can choose between
available Google Analytics. If your desired metric is not listed,
choose Cust om Met ric and specify below.
Sensor Channel #x
Custom Metric
This field is only visible if you choose custom metric above. Enter
the identifier of the metric that you want to monitor. Type it
exactly as shown in Google Analytics. Metric identifiers always start
with ga:
21.01.2016
771


Sensor Channel #x
Mode
Shows how the sensor displays the retrieved value in the channel.
Sensor Channel #x
Unit
Define the unit of the channel value. Once a sensor is created, you
If you need to change this, please add the sensor anew. Choose
between:
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
Value Lookup
custom sensors.
Sensor Channel #x
Custom Unit
This setting is only visible if you select the Cust om unit option
Sensor Channel #x
Value Lookup
This setting is only visible if you select the Value Lookup option
above. Choose a lookup 3095 file that you want to use with this
channel.
772
21.01.2016


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
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
773

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
774
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
775


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
776
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
777


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


Notifications
Others
21.01.2016
159
section.
779

43 Google Drive Sensor
6.8.43 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/google_driv e.png
Remarks
OAut h2 788 .
Add Sensor
later.
780
31.08.2015

GOOGLE CR EDENTIALS
This sensor type uses OAuth2 authentication to get access to your Google account. For
OAut h2 788 .
OAuth URL
Google Drive account using OAuth2. This is necessary to allow the
sensor to query data from Google Drive. A new browser window
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.
OAuth Code
authorization process for PRTG at your Google Drive account.
Click OK to define the sensor settings 781 .
Note: It is mandatory to connect this sensor to your Google Drive
Sensor Settings

Sensor Name

171 .
Parent Tags
31.08.2015
781


Tags

default value.
Priority
GOOGLE CR EDENTIALS
OAuth Code
to your Google Drive account. Once a sensor is created, you
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
782
31.08.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
31.08.2015
783

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
784
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
785


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
786
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
31.08.2015
787


service.
in PRTG.
788
31.08.2015


Notifications
Others
31.08.2015
159
section.
789

44 HTTP Sensor
6.8.44 HTTP Sensor

The HTTP sensor monitors a web server using Hypertext Transfer Protocol (HTTP). This is the
easiest way to monitor if a website (or a specific website element) is reachable.
It shows the loading time of a web page or element.
HTTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http.png
Remarks
Knowledge Base: My HTTP sensors fail to monitor websites which use SNI. What can I do?
Note: You do not have to define the sensor behavior for HTTP result codes. For details, see
this Knowledge Base article: Which HTTP status code leads to which HTTP sensor status?
Note: This sensor type does not support Secure Remote Password (SRP) ciphers.
Add Sensor
later.
790
21.01.2016

44 HTTP Sensor
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
HTTP SPECIFIC
Timeout (Sec.)
21.01.2016

791

44 HTTP Sensor
HTTP SPECIFIC
URL
below.
Request Method

below.
Postdata
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
792
This field is only visible when you select Cust om above. Define the
content type which is needed, for example, XML, JSON, HTTP.
21.01.2016

44 HTTP Sensor
HTTP SPECIFIC
Server Name Indication
Shows the Server Name Identification (SNI) that the sensor

automatically determined from the host address of the parent
device 324 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, please see section More for a link to the Knowledge
Base article My HTTP sensors fail t o monit or websit es 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.
Do not inherit SNI from parent device: The sensor determines
the SNI from the target URL as defined in the settings of this
sensor.
Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the
TLS protocol.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
21.01.2016
793

44 HTTP Sensor
SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.

HTTP Proxy Settings

Name

Port
User

Password

794
21.01.2016

44 HTTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
795

44 HTTP Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
796
21.01.2016

44 HTTP Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
797

44 HTTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

798
21.01.2016

44 HTTP Sensor
More
Knowledge Base: Which HTTP status code leads to which HTTP sensor status?

Notifications
Others
21.01.2016
159
section.
799

45 HTTP Advanced Sensor
6.8.45 HTTP Advanced Sensor

The HTTP Advanced sensor monitors the source code of a web page using Hypertext Transfer
Protocol (HTTP). It supports authentication, content checks, and other advanced parameters.
Loading time
Bytes received
Download bandwidth (speed)
Time to first byte
HTTP Adv anc ed Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_adv anc ed.png
Remarks
Supports Smart URL Replacement
814
Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?
800
11.03.2016

If you need to use SRP ciphers, please choose the "compatibility mode" in the sensor settings
below.
Note: Bandwidth monitoring of fast internet connections may be inaccurate.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
11.03.2016
801

HTTP SPECIFIC
Timeout (Sec.)

URL
below.
Request Method

below.
Postdata
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
802
This field is only visible when you select Cust om above. Define the
content type which is needed, for example, XML, JSON, HTTP.
11.03.2016

HTTP SPECIFIC

SNI Inheritance

sensor.
HTTP ENGINE
Monitoring Engine
If you encounter unexpected errors with the standard method that

is used to monitor an URL, try to use the compatibility mode which
is based on .NET. Choose between:
Default /High Performance (recommended): This is the default
monitoring method for this sensor type.
Alt ernat e/Compat ibilit y Mode: Try this method as an
alternative for websites that do not work with the default
approach. Using the compatibility mode, this sensor executes an
external exe. Because of this, this method needs more
resources, but it can be helpful in particular cases.
Note: If you select the compatibility mode, the options for the
SSL method will be slightly different. You can also check for
trusted certificates. Please see below.
Note: When using the Compatibility Mode, Smart URL
Replacement will not work, so this sensor will not use the IP
Address/DNS value of the parent device automatically then.
11.03.2016
803

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 uses when
connecting to the URL. Choose between:
HTTP 1.0
HTTP 1.1: This is the default setting.
User Agent
Choose which user agent string will be sent by this sensor when
connecting to the URL defined above. Choose between:
Use PRTG's default st ring: Do not enter a specific user agent,
use default setting. Usually, this is: Mozilla/5.0 (compatible; PRTG
Network Monitor (www.paessler.com); Windows)
Use a cust om st ring: Use a custom user agent. Define below.
Custom User Agent
804
This field is only visible if you enable custom user agent above.
Enter a string which will be used as user agent when connecting to
the URL specified above.
11.03.2016


Use Custom HTTP
Headers
Define if you want to send custom HTTP headers to the target URL.
Choose between:
Do not use cust om HTTP headers
Use cust om HTTP headers
Custom HTTP Headers
This field is only available if you select using custom headers

above. Enter a list of custom HTTP headers with theirs respective
values that you want to transmit to the URL you define above,
each pair in one line. The syntax of a header-value pair is
header1:value1
Note: The sensor does not accept the header field names useragent, content-length, host.
Note: Ensure that the HTTP header statement is valid! Otherwise,
the sensor request will not be successful.
Content Changes
Define what the sensor will do if the content of the monitored web
page (element) changes. You can choose between:
message indicating that the web page content has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2719 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 135 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 135 if
yes.
Note: The content check is only intended for html websites and
might not work with other target URLs. For example, binary files
are not supported.
11.03.2016
805


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 3105 . Specify below. If the data does not include the
search pattern, the sensor will show the status defined above.
Check Method
Define in which format you have entered the search expression in

the field above.
St ring search (default ): Search for the string as plain text. The
characters * and ? work here as placeholder, whereas * stands
for no or any number of characters and ? stands for exactly one
character (as known from Windows search). This behavior cannot
be disabled, so the literal search for these characters is not
possible with plain text search. You can also search for HTML
tags.
Regular Expression: Use the search pattern as a Regular
Expression 3105 .
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 135 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 135 if
yes.
Note: The content check is only intended for html websites and
might not work with other target URLs. For example, binary files
are not supported.
Response Must Not

include
This field is only visible if you enable keyword checking (exclude)

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 3105 . If the data does include this string, the sensor will
show the status defined above. Please enter a string.
Check Method

the field above.
806
11.03.2016


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 3105 .
Limit Download (kb)
Enter a maximum amount of data that the sensor can transfer per
every single request. If you set content checks, please be aware
that only the content downloaded up to this limit can be checked
for search expressions.
Result Handling
Define what the sensor will do with the web page loaded at the
given URL. Choose between:
Discard HTML result : Do not store the requested web page.
St ore lat est HTML result : Store the last result of the requested
web page to the "Logs (Sensors)" directory (on the Master node,
if in a cluster). File name: Result of Sensor [ID].txt. This is for
debugging purposes, especially in combination with content
checks. The file will be overridden with each scanning interval.
For information on how to find the folder used for storage,
please see Dat a St orage 3135 section.
Note: This sensor loads the source code at the given URL. If you set up a content check, only
this source code is checked for the keywords. The code is not necessarily identical to the one
used to display the page when opening the same URL in a web browser, as there may be a
reload configured or certain information may be inserted after loading, for example, via
Javascript. PRTG does not follow links to embedded objects nor does it execute scripts. Only
the first page at the given URL is loaded and checked against the expressions configured. For
debugging, please use the Result Handling option to write the source code file to disk and
look up what exactly PRTG gets when calling the URL. If the URL configured does not point to
a web page, but to a binary file, for example, to an image, you usually will not check for
content.
AU THENTICATION
Authentication
Define if the web page at the configured URL needs authentication.

Choose between:
No aut hent icat ion needed
11.03.2016
807

AU THENTICATION
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

password. Please enter a string.
Authentication Method
This field is only visible if enable authentication above. Select the

authentication method the given URL is protected with. Choose
between:
Basic access aut hent icat ion (HTTP): Use simple HTTP
authentication. This is the default setting and suitable for most
cases.
Note: This authentication method transmits credentials as plain
text.
Windows NT LAN Manager (NTLM): Use the Microsoft NTLM
protocol for authentication. This is sometimes used in intranets
for single sign-on.
Digest Access Aut hent icat ion: Use digest access
authentication that applies a hash function to the password
which is safer than basic access authentication.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
808
11.03.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.

HTTP Proxy Settings

Name

Port
User

Password

11.03.2016
809

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
810
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
811


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
812
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
11.03.2016
813


More
Knowledge Base: Is it possible to test a WSDL or SOAP service with PRTG?

Notifications
814
11.03.2016

Others
11.03.2016
159
section.
815

46 HTTP Apache ModStatus PerfStats Sensor
6.8.46 HTTP Apache M odStatus PerfStats Sensor

The HTTP Apache ModStatus PerfStats sensor monitors performance statistics of an Apache
web server using mod_status over Hypertext Transfer Protocol (HTTP).
It can show the following about the Apache at scan time:
CPU load
Server uptime
Requests per second
Bytes per request
Number of current busy workers threads
Number of idle worker threads
sensor setup.
HTTP Apac he ModStatus PerfStats Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_apac he_modstatus_perfstats.png
Remarks
816
824
.
31.08.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
31.08.2015
817

HTTP SPECIFIC
Timeout (Sec.)

URL
Enter the URL to the mod_status module on your Apache server.

PRTG will append a "/server_status?auto" part automatically. If you
enter an absolute URL, this address will be independent from the IP
address/DNS name setting of the device this sensor is created
on.
below.
TLS protocol.
AU THENTICATION
Authentication

Choose between:
User

Password


between:
cases.
text.
818
31.08.2015

AU THENTICATION
for single sign-on.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
31.08.2015
819


HTTP Proxy Settings

Name

Port
User

Password

820
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
821


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
822
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
823

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

824
31.08.2015

More

Notifications
Others
31.08.2015
159
section.
825

47 HTTP Apache ModStatus Totals Sensor
6.8.47 HTTP Apache M odStatus Totals Sensor

The HTTP Apache ModStatus Totals sensor monitors the activity of an Apache web server
using mod_status over Hypertext Transfer Protocol (HTTP).
Number of accesses
Transferred data in kBytes per second
sensor setup.
HTTP Apac he ModStatus Totals Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_apac he_modstatus_totals.png
Remarks
834
826
31.08.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
31.08.2015
827

HTTP SPECIFIC
Timeout (Sec.)

URL
Enter the URL to the mod_status module on your Apache server.

PRTG will append a "/server_status?auto" part automatically. If you
enter an absolute URL, this address will be independent from the IP
address/DNS name setting of the device this sensor is created
on.
below.
TLS protocol.
AU THENTICATION
Authentication

Choose between:
User

Password


between:
cases.
text.
828
31.08.2015

AU THENTICATION
for single sign-on.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
31.08.2015
829


HTTP Proxy Settings

Name

Port
User

Password

830
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
831


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
832
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
833

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

834
31.08.2015

More

Notifications
Others
31.08.2015
159
section.
835

48 HTTP Content Sensor
6.8.48 HTTP Content Sensor

The HTTP Content sensor monitors a numerical value returned by a Hypertext Transfer Protocol
(HTTP) request. In the returned HTML page, each value must be placed between square
brackets [ ]. See the example 845 below.
It shows the returned numbers in dedicated channels, one channel for each value.
sensor setup.
HTTP Content Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_c ontent.png
Remarks
846
837
officially.
Knowledge Base: How can I monitor internal values of a web application with PRTG
See also the PRTG manual: HTTP Cont ent SensorExample
845
836
31.08.2015


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.
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 92 . Each value must
be placed between square brackets [ ]. Enter the number of
bracket-value pairs that the defined URL will return.
Note: Do not enter a number less than the number of values
returned. Otherwise you will get an error message.
Sensor Settings
31.08.2015
837


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
HTTP SPECIFIC
Timeout (Sec.)

Script URL
you enter an absolute URL, this address will be independent from
the IP address/DNS name setting of the device this sensor is
created on.
below.
Value Type
838
Shows the kind of values the HTML file gives back. Once a sensor
is created, you cannot change this value. It is shown for reference
anew.
31.08.2015

TLS protocol.

Content Changes
Define what the sensor will do if the content of the monitored web
page changes. Choose between:
message indicating that the web page content has changed. In
to trigger a notification 2719 whenever the web page content
changes.
Sensor Result
Define what the sensor will do with the results the sensor
receives. Choose between:
Discard sensor result : Do not store the results.
(ID].t xt "): Store the last result received to the "Logs (Sensors)"
directory (on the Master node, if in a cluster). This is for
AU THENTICATION
Authentication

Choose between:
User

Password


between:
31.08.2015
839

AU THENTICATION
cases.
text.
for single sign-on.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
840

31.08.2015

Inherited Settings
described below.

HTTP Proxy Settings

Name

Port
User

Password

31.08.2015
841

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
842
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
843


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
844
31.08.2015

ACCESS R IGHTS
User Group Access
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:
<html>
<body>
Description: Script gives back current status of disk free (%) and CPU usage (%).
[85.5][12.0]
</body>
</html>
You would configure the HTTP Content sensor using the mentioned script URL, value type
Float , and number of channels 2. The sensor calls the URL with every scanning interval and
only regard the two values in square brackets [ ], handling each of them in one sensor channel.
The additional description text and HTML tags are not necessary; in this example they are
added in case a human calls the URL.
31.08.2015
845

Note: If you define the number of channels as 1, the sensor will read only the first value. The
second value will be ignored. Using 3 as number of channels will result in a sensor error
message.

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

Notifications
846
31.08.2015

Others
31.08.2015
159
section.
847

49 HTTP Data Advanced Sensor
6.8.49 HTTP Data Advanced Sensor

The HTTP Data Advanced sensor accesses a web server and retrieves XML or JSON encoded
data. For details about the return value format, please see the Applicat ion Programming
Int erface (API) Definit ion 3086 .
The sensor can show values returned by the web server in multiple channels.
HTTP Data Adv anc ed Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_data_adv anc ed.png
Remarks
The requested web server must return XML or JSON encoded data that matches the format
as defined in the API documentation 3086 in section Cust om SensorsAdvanced EX E/Script
Sensor, Advanced SSH Script Sensor, and Advanced HTTP Push Dat a Sensor.
For best sensor performance, we recommend that you specify the content type on the
target server, which is application/xml or application/json.
848
11.03.2016

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
11.03.2016
849

HTTP SPECIFIC
Timeout (Sec.)

URL
device on which you create this sensor.
parent device's IP Address/DNS Name setting as part of the URL.
below.
Request Method

GET: Request the target URL with the GET method.
POST: Send post form data to the URL. If you choose this
setting, you must enter the data that will be sent in the
Post dat a field below.
HEAD: Only request the HTTP header from the target server.
Postdata
This field is only visible if you select the POST method above. Enter
the data part for the POST request here.
Note: No XML is allowed here!

SNI Inheritance

sensor.
850
11.03.2016

HTTP SPECIFIC
Result Handling
Define what the sensor will do with the data loaded at the given
Discard HTML result : Do not store the requested data.
dta to the "Logs (Sensors)" directory (on the Master node, if in a
cluster). File name: Result of Sensor [ID].txt. This is for
AU THENTICATION
Authentication

Choose between:
User

Password


between:
cases.
text.
for single sign-on.
11.03.2016
851

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
852
11.03.2016


HTTP Proxy Settings

Name

Port
User

Password

11.03.2016
853

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
854
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
855


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
856
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
11.03.2016
857


More

Notifications
Others
858
159
section.
11.03.2016

50 HTTP Full Web Page Sensor
6.8.50 HTTP Full Web Page Sensor

The HTTP Full Web Page sensor monitors the full download time of a web page including assets
such as images etc. In the background, it opens the web page in a browser instance to
perform the measurement. Links are not followed.
This sensor shows the loading time of the full web page.
Note: Be careful with this sensor, because it can generate considerable internet traffic if you
use it with a low scanning interval!

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_full_web_page.png
Remarks
868
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?
04.11.2015
859

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
860
04.11.2015

FU LL PAGE DOWNLOAD SETTINGS

Timeout (Sec.)

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.
below.
Browser Engine
Define which browser the sensor uses to load the web page.
Choose between:
Chromium (recommended): Use the "WebKit" engine that is
delivered with PRTG to perform the loading test. With each
scanning interval, PRTG will load the URL defined above in an
instance of "Chromium" and measure the time until the page is
fully loaded. This is the recommended setting.
Phant omJS (Headless Webkit ): Use the "PhantomJS" engine. This
engine can have a high impact on your probe system's CPU and
memory load, but there are additional options for result handling
available (see below).
Int ernet Explorer: With each scanning interval, the URL defined
above is loaded in the background in an instance of Internet
Explorer. PRTG uses the Internet Explorer of the system running
the PRTG probe.
Note: For full functionality we strongly recommend that you
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 3109 on which the sensor is created on.
Note: For all browser engines, the same proxy settings are used
that are configured for the Windows user account the PRTG probe
is running on (this is usually the Windows local "system" user
account, if not changed). Those settings are accessible via the
Internet Explorer of this system. If you want to e.g. use a proxy for
this full web page sensor test, please adjust the Internet Explorer's
settings accordingly (on the computer running the probe; on all
nodes, if in a cluster).
Security Context
04.11.2015
browser engine. Choose between:
861


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. Please go to the sensor's parent device's
settings to change the Windows credentials.
Note: When using the Chromium browser engine above, we
recommended this setting here.
Result Handling
This setting is only visible if you select the PhantomJS engine

above. This browser engine can render and store screenshots of
the loaded web page. Choose between:
Discard loaded web page (recommended): Do not store the
requested web page.
St ore lat est screenshot of t he web page: Render and store
the last result of the web page to the "Logs (Sensors)" directory
(on the remote system, when used on a remote probe; on the
Master node, if in a cluster). This is for debugging purposes. The
file will be overridden with each scanning interval. It will be
named after the pattern "Fullpage of Sensor (ID).jpg". For
information on how to find the folder used for storage, please
see Dat a St orage 3135 section.
St ore ongoing screenshot s of t he web page (use wit h
caut ion!): Render and store one new screenshot of the web
page with each sensor scan, and store the pictures in the
Screenshot s (Fullpage Sensor) directory (on the remote
system, when used on a remote probe). For information on how
to find the folder used for storage, please see Dat a St orage 3135
section. This option can be used to create a visual history of the
web page.
Note: Depending on the monitored website and the scanning
interval of the sensor, this option can create a very high amount
of data! Use with care and make sure you set appropriate data
purging limits in the Sy st em Administ rat ionCore & Probes 2887
settings.
Note: If necessary, you can change the window size of the
rendered screenshots. See section More 869 for details.
Note: 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):
862
04.11.2015


C:\Windows\System32\config\systemprofile\AppData\Local
\Microsoft\Windows\Temporary Internet Files\Content.IE5
Authentication
This setting is only visible if you select the PhantomJS engine

above. Define if the monitored web page needs authentication for
access. Choose between:
No aut hent icat ion needed: Access to the web page is granted
without authentication.
Web page needs aut hent icat ion: PRTG automatically tries using
HTTP Basic authentication (BA) or Windows NT LAN Manager
(NTLM) to access the web page with authentication. Enter the
credentials below.
Note: Basic access authentication forwards the credentials in
plain text!
User
This setting is only visible if you select the PhantomJS engine with
authentication above. Enter the username for the web page.
Password
This setting is only visible if you select the PhantomJS engine with
authentication above. Enter the password for the web page.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
04.11.2015
863

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
864
04.11.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
04.11.2015
865


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
866
04.11.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
04.11.2015
867

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

868
04.11.2015

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
04.11.2015
159
section.
869

51 HTTP Push Count Sensor
6.8.51 HTTP Push Count Sensor

The HTTP Push Count sensor counts received messages which are pushed via a Hypertext
Transfer Protocol (HTTP) request to the PRTG server. It provides a URL that can be used to
push messages to the PRTG server using HTTP.
It shows the number of received messages per second.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_push_c ount.png
Remarks
For details about the usage, please see manual section HTTP Push Count SensorHow t o
Use 870 .
Note: This sensor type cannot be used in cluster mode. You can set it up on a local probe or
remote probe only, not on a cluster probe.
How to Use
This function is known as webhook. Basically, a webhook works like a push notification:
Webhooks are usually triggered by some event (for example, a new comment to a blog post)
and send according information to a specified URL. The HTTP Push Count sensor then displays
the number of pushed and received messages.
Use the following URL to receive the HTTP requests of the webhook:
870
31.08.2015

ht t p://<probe_ip>:<port_number>/<token>
Replace the parameters <probe_ip>, <port_number>, and <token> with the corresponding
values. You can define port number and identification token in the sensor settings. The "probe
IP" is the IP address of the system your PRTG probe with the sensor is running on.
Example: http://127.0.0.1:5050/XYZ123
Note: You can use several sensors with the same port and identification token. In this case,
the number of push messages will be shown in each of these sensors.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
31.08.2015
871


Priority
HTTP PU SH
Request Method
Select the request method of your webhook:

ANY: Do not use any filter for the request method.
GET: Choose this method if your webhook uses GET.
POST: Choose this method if your webhook sends post form
data. Postdata has to be applicat ion/x-www-form-urlencoded
with the same parameters as for GET requests.
Port
Enter the port number on which this sensor listens for incoming
HTTP requests. Default is 5050.
Identification Token
This is the token that is used to find the matching sensor for the
incoming message. While you create the sensor, this token is
{__guid__}. It is replaced with an automatically generated token after
you have completed the sensor creation. If you want to use
another identification token, you can edit it while or after sensor
creation.
Note: The token will not be replaced automatically if you change it
already during sensor creation.
Incoming Request
Define what PRTG will do with the incoming messages. Choose

between:
Discard request : Do not store the pushed messages.
Writ e request t o disk (Filename: "Result of Sensor [ID].t xt "):
Store the last message received from the sensor to the "Logs
(Sensor)" directory (on the Master node, if in a cluster). File
name: Request for Sensor [ID].txt. This is for debugging
purposes. The file will be overridden with each scanning interval.
872
31.08.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
31.08.2015
873

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
874
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
875


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
876
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
31.08.2015
877

Others
878
159
section.
31.08.2015

52 HTTP Push Data Sensor
6.8.52 HTTP Push Data Sensor

The HTTP Push Data sensor displays numerical values from received messages which are
pushed via a Hypertext Transfer Protocol (HTTP) request to the PRTG server. It provides a URL
that can be used to push messages to the PRTG server using HTTP.
The sensor shows the received value and an optional message in one channel.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_push_data.png
Remarks
For details about the usage, please see manual section HTTP Push Dat a SensorHow t o
Use 880 .
31.08.2015
879

How to Use
and send according information to a specified URL. The HTTP Push Data sensor then displays
the data of pushed and received messages.
Use the following URL to receive the HTTP requests of the webhook:
ht t p://<probe_ip>:<port_number>/<token>?value=<integer_or_float>&t ext =<text message>
Replace the parameters <probe_ip>, <port_number>, <token>, and <integer_or_float> with the
corresponding values. The &t ext parameter is optional: You can omit it.
You can define port number and ident ificat ion t oken in the sensor settings.
The probe IP is the IP address of the system on which your PRTG probe with this sensor is
running on.
The value can be an integer or a float value, depending on the data of your application; you
have to set the value type accordingly in the sensor settings. This parameter will be the
sensor value.
Note: If this parameter is missing, the sensor status will be set into a down status.
You can opt ionally add a custom text message by replacing the parameter <text message>
with it. The text will be shown as sensor message. If there is no value but only a text, the
text will be shown as error message.
Note: This text message has to be URL encoded (for example, the whitespaces in the sample
URL below); most browsers achieve this automatically.
Example:
http://127.0.0.1:5050/XYZ123?value=0&text=this%20is%20a%20message
the data of push messages will be shown in each of these sensors.
Add Sensor
later.
Sensor Settings
880
31.08.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
31.08.2015
881

HTTP PU SH
Request Method

Port
creation.
Incoming Request

between:
882
31.08.2015

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

Graph Type

for each channel.
31.08.2015
883

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
884
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
885


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
886
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
887

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
888
31.08.2015

Others
31.08.2015
159
section.
889

53 HTTP Push Data Advanced Sensor
6.8.53 HTTP Push Data Advanced Sensor

The HTTP Push Data Advanced sensor displays data from received messages which are pushed
via a Hypertext Transfer Protocol (HTTP) request to the PRTG server. It provides a URL that can
be used to push messages to the PRTG server using HTTP.
This sensor can show received values and a message encoded in valid XML or JSON in
multiple channels.
HTTP Push Data Adv anc ed Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_push_data_adv anc ed.png
Remarks
For details about the usage, please see manual section HTTP Push Dat a Advanced Sensor
How t o Use 891 .
890
31.08.2015

How to Use
and send according information to a specified URL. The HTTP Push Data Advanced sensor then
displays the data of pushed and received messages.
The data which is pushed to this sensor must be valid XML or JSON. For details about the
return value format please see the Applicat ion Programming Int erface (API) Definit ion
3086
Use the following URLs to receive the HTTP requests of the webhook:
GET requests: ht t p://<probe_ip>:<port_number>/<token>?cont ent =<valid XML_or_JSON>
The XML encoded value of the content parameter has to match the format as defined in the
API documentation 3086 in section Cust om SensorsAdvanced EX E/Script Sensor,
Advanced SSH Script Sensor, and Advanced HTTP Push Dat a Sensor.
POST requests: ht t p://<probe_ip>:<port_number>/<token>
This HTTP request method sends the XML or JSON encoded HTTP body as POST data. The
body has to match the format as defined in the API documentation 3086 in section Cust om
SensorsAdvanced EX E/Script Sensor, Advanced SSH Script Sensor, and Advanced
HTTP Push Dat a Sensor. 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.
Note: The content has to be URL encoded (for example, the whitespaces in the sample URL
below); most browsers achieve this automatically.
Minimum example for t he GET met hod which returns one static channel value:
http://127.0.0.1:5050/XYZ123?content=<prtg><result><channel>MyChannel</channel><value>10</value></result><t
the data of push messages will be shown in each of these sensors.
31.08.2015
891

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
892
31.08.2015

HTTP PU SH
Request Method

Port
creation.
Incoming Request

between:
31.08.2015
893

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

Graph Type

for each channel.
894
31.08.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
31.08.2015
895

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
896
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
897


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
898
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
31.08.2015
899

Others
900
159
section.
31.08.2015

54 HTTP Transaction Sensor
6.8.54 HTTP Transaction Sensor

The HTTP Transaction sensor monitors an interactive website, such as a web shop, by
performing a transaction using a set of Hypertext Transfer Protocol (HTTP) URLs. The sensor
monitors whether logins or shopping carts work properly.
It shows the loading time of single URLs and of the complete transaction.
HTTP Transac tion Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_transac tion.png
Remarks
913
Knowledge Base: Configuration Tips for HTTP Transaction Sensors

If you need to use SRP ciphers, please choose the "compatibility mode" in the sensor settings
below.
21.01.2016
901

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
902
21.01.2016

HTTP SPECIFIC
Timeout (Sec.)
Enter a timeout in seconds for all HTTP requests. If the complete

transaction takes longer than this value defines, the sensor
cancels the request and shows an according error message. Please
enter an integer value. The maximum value is 900 seconds (15
minutes).
Single URL Timeout

(Sec.)
Enter a timeout in seconds for one single HTTP request. If the reply
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 an URL, try to use the compatibility mode which
is based on .NET. Choose between:
Default /High Performance (recommended): This is the default
monitoring method for this sensor type.
Alt ernat e/Compat ibilit y Mode: Try this method as an
alternative for websites that do not work with the default
approach. Using the compatibility mode, this sensor executes an
external exe. Because of this, this method needs more
resources, but it can be helpful in particular cases.
Note: If you select the compatibility mode, the options for the
SSL method will be slightly different. You can also check for
trusted certificates. Please see below.
Note: When using the Compatibility Mode, Smart URL
Replacement will not work, so this sensor will not use the IP
Address/DNS value of the parent device automatically then.

SSL 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
21.01.2016
903


SSL V3 or TLS V1: This is the default setting.
Check SSL Certificates
Specify if the sensor will check the certificate of the monitored

Do not check used cert ificat es: Do not consider the
certificates of the monitored web pages. This the default setting.
Check if t he used cert ificat es are t rust ed: Inspect the
certificates. If the certificate of the server is not trusted, the
sensor shows a Down status and displays a corresponding
message.
TLS protocol.

Limit Download (kb)
Enter a maximum amount of data that is transferred per every

single request. If you set content checks below, please be aware
that the sensor can only check the content downloaded within
this limit for certain search expressions.
Cookie Management
Select if cookies are used for the transaction. Choose between:

Use cookies (recommended): Allow cookies to be set and read
during the transaction cycle.
Ignore cookies: Do not allow cookies. Use this option if you
want to test the transaction without the use of cookies.
User Agent
Choose which user agent string the sensor sends when

connecting to the defined URLs. Choose between:
Use PRTG's Default St ring: Do not enter a specific user agent,
use the default setting. Usually, this is: Mozilla/5.0 (compatible;
PRTG Network Monitor (www.paessler.com); Windows)
Use a Cust om St ring: Use a custom user agent. Define below.
Custom User Agent
904
This field is only visible if you enable the custom user agent option
above. Enter a string that the sensor uses as user agent when
connecting to the URL specified above.
21.01.2016


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.
web page to the "Logs (Sensors)" directory (on the Master node,
if in a cluster). File name: Result of Sensor [ID].txt. This is for
AU THENTICATION
Authentication

Choose between:
User

Password


between:
cases.
text.
for single sign-on.
21.01.2016
905

TR ANSACTION U R L
You can define up to 10 different transaction URLs which will all be called in a row. Only if
the complete transaction can be completed, the sensor will be in an Up status 135 . Using this
mechanism you can set up an extended monitoring with multiple URLs. Please enter settings
for at least one transaction URL. You can use as many steps as needed and disable the
other steps.
Transaction Step #x
This setting is available for URL #2 through #10. Define if you want
to use this step for your transaction check. Choose between:
Disable st ep #x: Do not use this step. Choose this option if you
do not need all 10 steps for your transaction check.
Enable st ep #x: Enable this step. Further options will be viewed,
as described below.
URL
Please enter the URL the sensor will connect to. It has to be URL
encoded! If you enter an absolute URL, this address will be
independent from the IP address/DNS name setting of the device
this sensor is created on. PRTG uses a smart URL replacement
which allows you to use the parent device's IP address/DNS name
setting as part of the URL. For more information, please see
section Smart URL Replacement below.
Request Method
The request method determines how the given URL is requested.

below.
Postdata
This field is only active when POST is selected in the Request

Met hod setting above. Please enter the data part for the post
request here.
Note: No XML is allowed here!
Check For Existing Key

Words (Positive)
Define whether the result at the configured URL will be checked

for keywords. Choose between:
Disable: Do not search for keywords.
906
21.01.2016

TR ANSACTION U R L
Enable key word check (posit ive): In the result returned at the
URL, check if a key word exists.
Note: The content check is only intended for HTML websites and
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.
Note: Only simple text search is available here. The characters *
and ? work here as placeholder, whereas * stands for no or any
number of characters and ? stands for exactly one character (as
known from Windows search). This behavior cannot be disabled, so
the literal search for these characters is not possible.
Check For Existing Key
Words (Negative)
Define whether the the result at the configured URL will be

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.
Note: The content check is only intended for HTML websites and
might not work with other target URLs.
Response Must Not

Include
Define which string must not be part of the web at the given URL.
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.
Note: Only simple text search is available here. The characters *
known from Windows search). This behavior cannot be disabled, so
the literal search for these characters is not possible.
SENSOR DISPLAY
Primary Channel
21.01.2016

907

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
908
21.01.2016


HTTP Proxy Settings

Name

Port
User

Password

21.01.2016
909

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
910
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
911


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
912
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

21.01.2016
913

More
Knowledge Base: Configuration Tips for HTTP Transaction Sensors needed

Notifications
Others
914
159
section.
21.01.2016

55 HTTP XML/REST Value Sensor
6.8.55 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.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/http_xmlrest_v alue.png
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.
927
Knowledge Base: HTTP XML/REST Value Sensor: FAQ
15.04.2016
915


this sensor.

Add Sensor
later.
SENSOR SETTINGS
Channel Name
Enter a name for the channel which will display the value at the
given URL. You can change the name later in the Sensor Channels
Set t ings 2711 .
Sensor Settings
916
15.04.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
URL
Enter the URL that returns the XML file. It has to be URL encoded! If
independently from the IP Address/DNS Name setting of the
device on which you create this sensor.
927 below.
XML Node (and

optional property)
Enter the name of the node that this sensor checks, or enter a
node name and a property name to check a property value. To
obtain a value from nested tags, enter the tag names separated by
a slash symbol, for example, use myTag/myTagInside as XML node
value.
Note: You can also check values in JavaScript Object Notation
(JSON) notation. Please see Checking JSON 926 section below.
15.04.2016
917

SENSOR SETTINGS
Note: You can try using XPath syntax here but it does not work in
all cases and we do not provide any technical support for XPath
issues. For further documentation about XPath, please see More
915 section below.
HTTP Username
If the URL requires authentication, enter the username. Please

HTTP Password
If the URL requires authentication, enter the password. Please

Sensor Value
Define what value this sensor shows. Choose between:

Use t he value of t he select ed X ML node: Return the value that
the sensor finds at the specified XML node. If this is non-numeric,
the sensor shows 0.
Use t he number of occurrences of t he select ed X ML node or
it s children/siblings: Return the number of occurrences found.
Define further below.
Count XML Nodes
This setting is only visible if you enable the return number option
above. Define which count the sensor shows. Choose between:
Occurrences of t he select ed X ML node: Return how often the
defined XML node occurs at the defined URL.
Child nodes of t he select ed X ML node: Return the number of
child nodes that exist below the node at the defined URL.
Sibling nodes of t he select ed X ML node: Return the number
of sibling nodes that exist next to the node at the defined URL.
Namespaces
Define whether namespaces in the XML document are used or not.

Choose between:
Use Namespaces: Process the value you enter in the "XML Node
(and optional property)" field including possibly existing
namespace information.
Remove Namespaces: Ignore namespace information in the XML
document and process the value you enter in the "XML Node
(and optional property)" field as node names only.
For more information see About Namespaces
Content Type in
Header
927
section below.
Define what to include in the header of the request sent to the

URL defined above. Choose between:
Enable (recommended): This works for most web servers and is
the recommended setting.
918
15.04.2016

SENSOR SETTINGS
Disable: Only very few web servers cannot handle this contenttype and need this setting. Try this if you get an error message
with the enabled option.
Cust om: You can use a custom content type.
Custom Content Type
This field is only visible when you enable the custom option above.
Enter a custom content type like text/xml or text/html.
HTTP Headers
Optionally enter a list of custom HTTP headers with theirs

respective values that you want to transmit to the URL you define
above. The syntax of a list with header-value pairs is
header1:value1|header2:value2|...|headerx:valuex
Note: The sensor does not accept header field names that include
a dash (-) character. If you want to use such a HTTP header, please
leave out the dash of the name. For example, enter
ContentType:value instead of Content-Type:value.
Example: From:johnqpublic@example.com|AcceptLanguage:en-us
Note: Ensure that the HTTP header statement is valid! Otherwise,
the sensor request will not be successful.
Characters to Remove
This field is only visible if you enable the "use value of XML node"
option above. Optionally enter a string that the sensor removes
from the returned XML value. Use this to remove any unwanted
characters from the result, for example, a thousands separator
from numeric values. Please enter a string or leave the field empty.
Decimal Delimiter
This setting is only visible if you enable the "use value" option
above. If the sensor value of the selected XML node is of the type
float, you can define any character here which is handled as the
decimal delimiter. Enter one character or leave the field empty.
Custom Message
Optionally enter a custom sensor message. Use %1 as a

placeholder to automatically fill in the returned XML value. Please
SSLv3 Connection
Define if you want to allow SSLv3 only for connections to the URL
configured above. Choose between:
Use SSLv3 if available
Force usage of SSLv3
Note: The force method does not work when the requested URL
uses forward secrecy. See section More 928 .
15.04.2016
919

SENSOR SETTINGS
If Value Changes
change.
Unit String
Enter a string that the sensor will add to the retrieved values as a
unit description. This is for display purposes only.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type
920
15.04.2016

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
15.04.2016
921

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
922
15.04.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
15.04.2016
923


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
924
15.04.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
15.04.2016
925

Checking JSON
With the X ML Node (and opt ional propert y ) field you can also check values that are returned
in JavaScript Object Notation (JSON) notation under the defined URL.
Example
A JSON notated section may look like the following:
{
"test": "Hello World",
"object": {
"value": "content",
"AnotherValue": "AnotherContent"
},
"arraytest": [
"one",
"two"
]
}
Depending on your entries in the X ML Node field, the sensor will process the respective
values:
Ent ry in Sensor's "X ML Node" Field (from

Example Above)
Processed Value (from Example Above)
test
Hello World
object/value
content
object/AnotherValue
AnotherContent
object
contentAnotherContent
arraytest[1]
one
arraytest[2]
two
926
15.04.2016

Note: 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.
Note: 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.
Note: If a key exists more than once in the JSON, the value of the first appearance is returned
(no difference between whitespace and underscore).
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.

15.04.2016
927

More
Knowledge Base: Is there a tool available that can help me building queries for the XML/Rest
Sensor?
Knowledge Base: How do I extract values from XML nodes (with nested tags) using PRTG's
XML/Rest Value Sensor?
Knowledge Base: How can I use XPath with PRTG's XML/Rest Value Sensor?
Knowledge Base: HTTP XML/REST Value Sensor shows protocol violation. What can I do?
Knowledge Base: Why does my HTTP XML/REST Value Sensor return a 404 error?
Knowledge Base: My HTTP sensors could not create an SSL secure channel and are down.
What can I do?
why?
928
15.04.2016


Notifications
Others
15.04.2016
159
section.
929

56 Hyper-V Cluster Shared Volume Disk Free Sensor
6.8.56 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

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

Requirement: Remote PowerShell

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

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

this sensor.
Add Sensor
later.
Select the disks you want to monitor. PRTG creates one sensor for each disk you choose in
that are created.
24.03.2015
931

DISK FR EE SETTINGS
Disk
head.
Note: Ensure the resource name of your disks do not contain
unsupported characters, especially avoid the hash ('#') sign. We
recommend to not rename resource disk name once you have set
up monitoring. For detailed information, please see More 958
section below.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
932
24.03.2015


Priority
DISK FR EE SETTINGS
Disk
Shows the name of the disk. Once a sensor is created, you cannot
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type
24.03.2015
933

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
934
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
935


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
936
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
937

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
938
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
939

57 Hyper-V Host Server Sensor
6.8.57 Hy per-V Host Server Sensor

The Hyper-V Host Server sensor monitors a Microsoft Hyper-V host server via Windows
Performance Counters or Windows Management Instrumentation (WMI), as configured in the
"Windows Compatibility Options" of the parent device.
CPU usage in percent of guests, hypervisor, and total
Number of host health critical values
Number of deposited pages
Network traffic: Sums up the total bytes per second (received and sent) on all ports of your
virtual switch.
Hy per-V Host Serv er Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hy per_v _host_serv er.png
Remarks
sensor on.
Requires
941
Windows Server 2008 or later on the probe system.
Requires
941
the Remote Registry Windows service to be running on the target computer.
940
24.03.2015

Uses a hybrid approach 941 with Windows Performance Counters and WMI as fallback to query
data. Please stay below 200 WMI sensors per probe!
Note: The parent device for this sensor must be a Windows server running Hyper-V.
Hybrid Approach: Performance Counters and WMI

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

Note: If you use local credentials, please make sure the same Windows user accounts (with
same username and password) exist on both the system running the PRTG probe and the
target computer. If you fail to do so, a connection via Performance Counters will not be
possible. However, WMI connections may still work.
Requirement: Windows Version

In order for this sensor to work with Windows Performance Counters, please make sure a
Windows version 2008 or later is installed on the computer running the PRTG probe: This is
remote probe 3109 .
Requirement: Remote Registry Service

In order for this sensor to work with Windows Performance Counters, please make sure the
Remote Registry Windows service is running on the target computer. If you fail to do so, a
connection via Performance Counters will not be possible. However, WMI connections may still
work.
To enable the service, please log in to the respective computer and open the services
manager (for example, via services.msc). In the list, find the respective service and set its Start
Type to Automatic.
24.03.2015
941

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
DEBU G OPTIONS
Sensor Result
942
24.03.2015

DEBU G OPTIONS
between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
24.03.2015

943

Inherited Settings
described below.
944
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
945


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
946
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
947

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
948
159
section.
24.03.2015

58 Hyper-V Virtual Machine Sensor
6.8.58 Hy per-V Virtual M achine Sensor

The Hyper-V Virtual Machine sensor monitors a virtual machine running on a Microsoft Hyper-V
host server via Windows Performance Counters or Windows Management Instrumentation
(WMI), as configured in the "Windows Compatibility Options" of the parent device.
CPU usage in percent of guests, hypervisor, and total
IDE disk read speed (bytes per second)
IDE disk write speed (bytes per second)
sensor setup.
Hy per-V Virtual Mac hine Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hy per_v _v irtual_mac hine.png
Remarks
sensor on.
Requires
950
Requires
951
24.03.2015
949

Note: The parent device for this sensor must be a Hyper-V server or a System Center Virtual
Machine Manager (SCVMM).
Note: We recommend using System Center Virtual Machine Manager (SCVMM) as parent
device, because this way PRTG will continue to monitor your virtual machines also when they
change the physical host using Live Migration.
Note: To monitor a virtual machine with this sensor, disable User Account Control (UAC) in
the control panel of the Windows operating system which is running on this virtual machine.
Otherwise, the sensor might switch into a Down status with the error message "The virtual
machine is not running or is powered off".

section.
3005


remote probe 3109 .
950
24.03.2015


work.
Type to Automatic.
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 which are available to monitor. Select the
head.
Note: Ensure the name of your VMs do not contain unsupported
characters, especially avoid the hash ('#') sign. We recommend to
not rename virtual machines once you have set up monitoring. For
detailed information, please see More 958 section below.
Sensor Settings
24.03.2015
951


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

GUID
Shows the Globally Unique Identifier (GUID) of the virtual machine

that this sensor monitors. Once a sensor is created, you cannot
Name
Shows the name of the virtual machine that this sensor monitors.
Description
Shows information about the virtual machine. Once a sensor is

anew.
952
24.03.2015


Powered Off VMs
Define how to react to a virtual machine that is powered off.

Choose between:
Alarm when powered off: The sensor will change to a Down 135
status if the virtual machine is powered off. Note: While in Down
status, a sensor does not record any data in all of its channels.
Ignore powered off st at e: The sensor will not change to a
Down status if the virtual machine is powered off. It will report
zero values instead.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
953

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
954
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
955


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
956
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
957

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
958
24.03.2015

Others
24.03.2015
159
section.
959

59 Hyper-V Virtual Network Adapter Sensor
6.8.59 Hy per-V Virtual Network Adapter Sensor

The Hyper-V Network Adapter sensor monitors virtual network adapters running on a
Microsoft Hyper-V host server via Windows Performance Counters or Windows Management
Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent
device.
Sent, received, and totally transferred bytes
Sent and received packets per second
Sent and received broadcast packets per second
Sent and received directed packets per second
Sent and received multicast packets per second
sensor setup.
960
02.11.2015

Hy per-V Virtual Network Adapter Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hy per_v _v irtual_network_adapter.png
Remarks
sensor on.
Requires
962
Requires
962
Note: The parent device for this sensor must be a Hyper-V server.
02.11.2015
961


section.
3005


remote probe 3109 .

work.
Type to Automatic.
962
02.11.2015

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 in this dialog are valid for all of

Hyper-V Virtual
Network Adapter
Select the virtual network adapters you want to add a sensor for.
You see a list with the names of all items which are available to
monitor. Select the desired items by adding check marks in front of
the respective lines. PRTG creates one sensor for each selection.
in the table head.
Note: We recommend that you do not rename virtual machines
once you have set up monitoring. Renaming them will also change
the internal virtual network adapter names, causing the monitoring
to be interrupted. For detailed information about virtual machine
naming, please see More 958 section below.
Sensor Settings

Sensor Name
02.11.2015

171 .
963


Parent Tags
Tags

default value.
Priority
HYPER -V VIR TU AL NETWOR K ADAPTER SETTINGS

Virtual Network
Adapter
Shows the name of the virtual network adapter monitored by this

sensor. Once a sensor is created, you cannot change this value. It
Sensor Result

between:
964
02.11.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
02.11.2015
965

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
966
02.11.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
02.11.2015
967


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
968
02.11.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: Why don't my Hyper-V Virtual Machine sensors work after changing names?

Notifications
02.11.2015
969

Others
970
159
section.
02.11.2015

60 Hyper-V Virtual Storage Device Sensor
6.8.60 Hy per-V Virtual Storage Device Sensor

The Hyper-V Virtual Storage sensor monitors a virtual storage device running on a Microsoft
Hyper-V host server via Windows Performance Counters or Windows Management
device.
Read speed in bytes per seconds
Write speed in bytes per second
Number of errors
sensor setup.
Hy per-V Virtual Storage Dev ic e Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hy per_v _v irtual_storage_dev ic e.png
Remarks
sensor on.
Requires
972
Requires
972
24.03.2015
971

Note: The parent device for this sensor must be a Hyper-V server.
Note: This sensor does not support Live Migration.

section.
3005


remote probe 3109 .

work.
972
24.03.2015

Type to Automatic.
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

Hyper-V Virtual Storage Select the virtual storage devices you want to add a sensor for.
Device
in the table head.
Sensor Settings

Sensor Name
24.03.2015

171 .
973


Parent Tags
Tags

default value.
Priority
HYPER -V VIR TU AL STOR AGE DEVICE SETTINGS

Virtual Storage Device
Shows the unique identifier of the device that this sensor

Sensor Result

between:
974
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
975

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
976
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
977


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
978
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
24.03.2015
159
section.
979

61 IMAP Sensor
6.8.61 IM AP Sensor
The IMAP sensor monitors a mail server using Internet Message Access Protocol (IMAP).
Response time of the mail server
Number of emails in the defined mailbox
It can also check the content of emails for certain key words. This way, you can use this
sensor to monitor backup solutions via emails that are sent out by these solutions. For
more information, see section More 992 .
IMAP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/imap.png
Remarks
Note: If you use content checks, we recommend using a dedicated IMAP account that is only
checked by PRTG. Editing existing mails in the mailbox of the monitored IMAP account can
lead to false alarms or malfunctions of this sensor type.
Note: This sensor type might not work properly when monitoring sub-folders of mailboxes. If
it has to check subsequent emails with identical subjects, later on incoming emails might not
be recognized.
Knowledge Base: My IMAP sensor does not process HTML emails correctly using regex. What
can I do?
980
19.10.2015

61 IMAP Sensor
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?
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
19.10.2015
981

61 IMAP Sensor
IMAP SPECIFIC
Timeout (Sec.)

Port
Enter the number of the port that the sensor uses to connect via
IMAP. For non-secure connections, usually port 143 is used. For
SSL connections it is usually port 993. The actual setting depends
on the server you are connecting to. Please enter an integer value.
AU THENTICATION
Username
Enter a username for IMAP authentication. Please enter a string.
Password
Enter a password for IMAP authentication. Please enter a string.

Sensor Specific
Define the security level for the sensor connection. Choose

between:
Use Transport -Level Securit y if available using St art TLS
(default ): Choose this option to try connecting to the server
using TLS and StartTLS. If the server does not support this, the
sensor will try connecting without encryption.
Use Transport -Level Securit y if available: Choose this option
to try connecting to the server using TLS. If the server does not
support this, the sensor will try connecting without encryption.
Enforce Transport -Level Securit y using St art TLS: Choose this
option to try connecting to the server using TLS and StartTLS. If
the server does not support this, the sensor will show a Down
status 135 .
Enforce Transport -Level Securit y : Choose this option to try
connecting to the server using TLS. If the server does not
support this, the sensor will show a Down status 135 .
982
19.10.2015

61 IMAP Sensor

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.
IDENTIFY EMAIL
Process Email Content
This sensor can additionally check the content of all incoming

emails. Choose between:
Do not check email cont ent : Only check availability of the IMAP
server and check if a login is successful (if defined). Do not
process any emails in the IMAP email account.
Read email count : Count the emails in the defined mailbox.
Process emails in t his mailbox: Log in to the IMAP email
account and check the emails which it contains. Define further
options below.
Mailbox Name
This field is only visible if you enable email counting or content

processing above. Enter the name of the mailbox (for example, the
name of the IMAP folder) that the sensor checks. Default value is
Inbox. Unless you set a last message date check below, the
sensor will always look at all emails contained in the mailbox.
Note: Ensure you do not manually edit emails in this mailbox with
another email client because this can result in malfunctions of this
sensor's email identification.
Identify by "From" Field
This option is only visible if you enable email content processing

above. Define if you want to check the "From" field of the emails.
Choose between:
Don't check: Do not process this field in emails.
Check using st ring search: Process this field in emails using
simple string search.
Check using regular expression: Process this field in emails
using a regular expression. For more information about syntax,
please see the Regular Expressions 3105 section.
19.10.2015
983

61 IMAP Sensor
IDENTIFY EMAIL
When using a search, the sensor will scan all emails from the
newest to the oldest.
Note: The sensor finishes the scan with the first match! This means
that after it finds a match in one email, there will be no further
checks performed in older emails.
Search For
This field is only visible if you enable a "from" check above. Enter a
search string using the method defined above.
Identify by "Subject"
Field
This option is only visible if you enable content processing above.

Define if you want to check the "Subject" field of the emails.
Choose between:
Don't check: Do not check this field in emails.
Check using st ring search: Check this field in emails using
simple string search.
Check using regular expression: Check this field in emails using
a regular expression. For more information about syntax, please
see the Regular Expressions 3105 section.
Search For
This field is only visible if you enable a "subject" check above. Enter
a search string using the method defined above.
Identify by Mail Body

Define if you want to check the mail body of the emails. Choose
between:
Don't check: Do not check the mail body.
Check using st ring search: Check the mail body using simple
string search.
Check using regular expression: Check the mail body using a
regular expression. For more information about syntax, please
see the Regular Expressions 3105 section.
984
19.10.2015

61 IMAP Sensor
IDENTIFY EMAIL
Search For
This field is only visible if you enable checking the mail body above.
Enter a search string using the method defined above.
Check Last Message

Date

Define if you want to check all emails in the mailbox, or only mails
that were received within the last x hours. Choose between:
Don't check message age: Always check all emails contained in
the mailbox.
Check for new messages received wit hin t he last x hours:
Only regard emails that were received in the last hours. Define
below.
Error Threshold (Hours) Enter the maximum age in hours. The sensor processes only emails
that are younger. If there is no matching email in the defined time
span, the sensor will show a Down status 135 .
Warning Threshold
(Hours)
Enter the maximum age in hours. The sensor processes only emails
that are younger. If there is no matching email in the defined time
span, the sensor will show a Warning status 135 .
SENSOR BEHAVIOR
Set to Error
This setting is only visible if you enable email content check above.
Define in which cases the sensor will show a Down status 135 .
Choose between:
Never (default ): Never set this sensor to a Down status based
on email content.
Alway s: Always set this sensor to a Down status in case any
emails could be identified.
If subject cont ains
If subject does not cont ain
If mail body cont ains
If mail body does not cont ain
Check Method
This setting is only visible if you select an if-condition above.

Define how you want to check for the above condition. Choose
between:
St ring search: Check the mail body using simple string search.
19.10.2015
985

61 IMAP Sensor
SENSOR BEHAVIOR
Regular expression: Check the mail body using a regular
expression. For more information about syntax, please see
Regular Expressions 3105 section.
Note: The sensor finished the scan with the first match! This means
Search Text
This setting is only visible if you select an if-condition above. Enter

Error Message
This setting is only visible if you select an alarm condition above.

Define the message that the sensor will show for a Down status
135 .
Set to Warning
This setting is only visible if you enable content check above.

Define in which cases the sensor will show a Warning status 135 .
Choose between:
Never (default ): Never set this sensor to a Warning status
based on email content.
Alway s: Always set this sensor to a Warning status in case any
emails could be identified.
If subject cont ains
If subject does not cont ain
If mail body cont ains
If mail body does not cont ain
Check Method
This setting is only visible if you select an if-condition above.

Define how you want to check for the above condition. Choose
between:
St ring search: Check the mail body using simple string search.
Regular expression: Check the mail body using a regular
expression. For more information about syntax, please see
Regular Expressions 3105 section.
986
19.10.2015

61 IMAP Sensor
SENSOR BEHAVIOR
Search Text
This setting is only visible if you enable an if-condition above. Enter

Warning Message
This setting is only visible if you select a warning condition above.

Define the message that the sensor will show for a Warning status
135 .
No Matching Mail
Behavior
This setting is only visible if you enable content check above.

Define how the sensor will react if it does not find matching emails
in the mailbox that it scans. Choose between:
Set sensor t o "Down" st at us
Set sensor t o "Warning" st at us
None: Do not do anything in this case.
Message
This field is only visible if you enable a no matching behavior above.

Define the message that the sensor will show if it did not find any
matching emails together with a Warning or Down status as you
define above.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type
19.10.2015
987

61 IMAP Sensor
SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
988
19.10.2015

61 IMAP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
19.10.2015
989

61 IMAP Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
990
19.10.2015

61 IMAP Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
19.10.2015
991

61 IMAP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: How can I monitor my backup software to be sure backup succeeded last
night?
Knowledge Base: My IMAP sensor does not process HTML emails correctly using regex. What
can I do?
Knowledge Base: Can I analyze multipart emails using the PRTG IMAP sensor?
992
19.10.2015

61 IMAP Sensor

Notifications
Others
19.10.2015
159
section.
993

62 IP on DNS Blacklist Sensor
6.8.62 IP on DNS Blacklist Sensor

The IP on DNS Blacklist sensor checks if the IP address of its parent device is listed on specific
blacklist servers.
The sensor shows the number of blacklist hits it can find.
IP on DNS Blac klist Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ip_on_dns_blac klist.png
Remarks
If a DNS name is used as hostname of the parent device, PRTG will resolve it to an IP address
before querying blacklist servers.
During normal operation, there should be 0 hits and the sensor should show a green Up
status 135 . If the sensor can find the IP address on at least one of the blacklist servers, it will
show a yellow Warning status by default. Note: You can set additional thresholds in the
Sensor Channels Settings 2711 .
Knowledge Base: Is there a list of anti spam black list servers?
994
02.11.2015


this sensor.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
02.11.2015
995


Priority
SENSOR SETTINGS
Blacklist Servers
Define the blacklist servers that the sensor uses for the check.
You can enter a comma separated list. Default is bl.spamcop.net.
For a list of servers, please see More 1001 section below.
Note: With each scanning interval, PRTG will query all servers in the
list! We recommend that you do not enter more than 10 servers to
make sure the check can be completed within the scanning interval
of this sensor. If you use too many blacklist servers, the sensor
will show a "Timeout (code: PE018)" error message.
DEBU G OPTIONS
Sensor Result

between:
996
02.11.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
02.11.2015
997

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
998
02.11.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
02.11.2015
999


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1000
02.11.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: Is there a list of anti spam black list servers?
why?

02.11.2015
1001

Notifications
Others
1002
159
section.
02.11.2015

63 IPFIX Sensor
6.8.63 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.
21.01.2016
1003

63 IPFIX Sensor
IPFIX Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ipfix.png
Remarks
Note: You have to enable IPFIX export on the device for this sensor to work. The device
must send the flow data stream to the IP address of the PRTG probe system on which the
sensor is set up (either a local or remote probe).
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?
Knowledge Base: What is the Active Flow Timeout in Flow sensors?
For a general introduction to the technology behind flow monitoring, please see manual
1004
21.01.2016

63 IPFIX Sensor
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
21.01.2016
1005

63 IPFIX Sensor
IPFIX SPECIFIC SETTINGS

Receive IPFIX Packets
on UDP Port
Enter the UDP port number on which the flow packets are
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.

on IP
Select the IP address(es) on which PRTG listens to IPFIX packets.

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

(Minutes)
Enter a time span in minutes after which new flow data must be
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 that you set this one minute longer than the
respective timeout configured in your hardware router device.
Please see section More for more details about this setting.
Note: If you set this value too low, flow information might get lost!
Sampling Mode
Define if you want to use the sampling mode. This setting must
accord to the setting in the flow exporter. Choose between:
Off: The standard flow will be used.
On: Switch into sampling mode and specify the sampling rate
below.
Sampling Rate
This field is only visible when sampling mode is enabled above.

Enter a number that matches the sampling rate in your exporter
device. If the number is different, monitoring results will be
incorrect. Please enter an integer value.
Log Stream Data to

Disk (for Debugging)
Define if the probe will write a log file of the stream and packet
data to the data folder (see Dat a St orage 3135 ). Choose between:
None (recommended): Do not write additional log files.
Recommended for normal use cases.
Only for t he 'Ot her' channel: Only write log files of data that is
not filtered otherwise and therefore accounted to the default
Ot her channel.
All st ream dat a: Write log files for all data received.
1006
21.01.2016

63 IPFIX Sensor

Note: Use with caution! When enabled, huge data files can be
created. Please use for a short time and for debugging purposes
only.
CHANNEL CONFIGU R ATION

Channel Selection
Define the categories the sensor accounts the traffic to. There are
different groups of traffic available. Choose between:
Web: Internet web traffic.
File Transfer: Traffic caused by FTP.
Mail: Internet mail traffic.
Chat : Traffic caused by chat and instant messaging.
Remot e Cont rol: Traffic caused by remote control applications,
such as RDP, SSH, Telnet, VNC.
Infrast ruct ure: Traffic caused by network services, such as
DHCP, DNS, Ident, ICMP, SNMP.
Net BIOS: Traffic caused by NetBIOS communication.
Cit rix: Traffic caused by Citrix applications.
Ot her Prot ocols: Traffic caused by various other protocols via
UDP and TCP.
For each traffic group, you can select how many channels will be
used for each group, i.e., how detailed the sensor divides the
traffic. For each group, choose between:
No: Do not account traffic of this group in an own channel. All
traffic of this group is accounted to the default channel named
Ot her.
Yes: Count all traffic of this group and summarize it into one
channel.
Det ail: Count all traffic of this group and further divide it into
different channels. The traffic appears in several channels as
shown in the Cont ent column. Note: Extensive use of this
option can cause load problems on your probe system. We
recommend setting specific, well-chosen filters for the data you
really want to analyze.
Note: You can change the default configuration for groups and
channels. For details, please see section More.
21.01.2016
1007

63 IPFIX Sensor
FILTER ING
Include Filter
Define if you want to filter any traffic. If you leave this field empty,
all traffic will be included. To include specific traffic only, define
filters using a special syntax. For detailed information, please see
Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors 3087
section.
Exclude Filter
First, the filters defined in the Include Filt er field are considered.
From this subset, you can explicitly exclude traffic, using the same
syntax. For detailed information, please see Filt er Rules for xFlow,
IPFIX , and Packet Sniffer Sensors 3087 section.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
1008

21.01.2016

63 IPFIX Sensor
PR IMAR Y TOPLIST
Primary Toplist
Define which will be your primary toplist. It will be shown in maps

when adding a toplist object. Choose from:
Top Talkers
Top Connect ions
Top Prot ocols
[Any custom toplists you have added]
Inherited Settings
described below.
21.01.2016
1009

63 IPFIX Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1010
21.01.2016

63 IPFIX Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
1011

63 IPFIX Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1012
21.01.2016

63 IPFIX Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
1013

63 IPFIX Sensor
Toplists
For all flow and packet sniffer sensors there are Toplist s available on the Overview tab of a
sensor's detail page. Using toplists, you can review traffic data of small time periods in great
detail. For more information, please see Toplist s 2734 section.
More
Paessler Website: Paessler NetFlow Testers
https://www.paessler.com/tools/netflowtester
Sniffer sensors?

Notifications
Others
159
section.
Related Topics
Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors
3087
Channel Defint ions for xFlow, IPFIX , and Packet Sniffer Sensors
1014
3092
21.01.2016

64 IPFIX (Custom) Sensor
6.8.64 IPFIX (Custom) Sensor

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

1016
officially.

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
1016
21.01.2016


Priority

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.
Sender IP
IPFIX data from. Enter an IP address to receive data from a specific

on IP
Select the IP address(es) on which PRTG listens to IPFIX packets.

line. The IP address selected here must match the one configured
in the IPFIX export options of your hardware router device.
Active Flow Timeout

(Minutes)
value. We recommend that you set this one minute longer than the
respective timeout configured in your hardware router device.
Sampling Mode
below.
Sampling Rate
21.01.2016

Enter a number that matches the sampling rate in your device. If
the number is different, monitoring results will be incorrect. Please
enter an integer value.
1017


Channel Definition
Please enter a channel definition to divide the traffic into different

channels. Write each definition in one line. For detailed information,
please see Channel Definit ions for xFlow and Packet Sniffer
Sensors 3092 section. All traffic for which no channel is defined will
be accounted to the default channel named Ot her.
Note: Extensive use of many filters can cause load problems on
your probe system. We recommend defining specific, well-chosen
filters for the data you really want to analyze.
Log Stream Data to

Ot her channel.
only.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1018
21.01.2016

SENSOR DISPLAY
Stack Unit

FILTER ING
Include Filter
section.
Exclude Filter
PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
21.01.2016
1019

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1020
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
1021


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1022
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
1023

Toplists
More
Sniffer sensors?

Notifications
Others
159
section.
Related Topics
3087
1024
3092
21.01.2016

65 IPMI System Health Sensor
6.8.65 IPM I Sy stem Health Sensor

The IPMI System Health sensor monitors the status of a system via the Intelligent Platform
Management Interface (IPMI).
Temperatures of, for example, the system or the peripheral temperature.
Fan rotation per minute
Voltages
Status of a power supply
sensor setup.
IPMI Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ipmi_sy stem_health.png
Remarks
Note: You have to explicitly specify the credentials of the IPMI in the sensor settings.
Requires
31.08.2015
1026
1025


this sensor.
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 256 . 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
1026
31.08.2015

IPMI SPECIFIC
Group
Select the measurements you want to add a sensor for. You see a
list with the names of all items which are available to monitor.
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
31.08.2015
1027

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

between:
SENSOR DISPLAY
Primary Channel

Graph Type
1028
31.08.2015

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
31.08.2015
1029

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1030
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
1031


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1032
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
31.08.2015
1033

More

Notifications
Others
1034
159
section.
31.08.2015

66 jFlow V5 Sensor
6.8.66 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.
15.10.2015
1035

66 jFlow V5 Sensor
jFlow V5 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/jflow_v 5.png
Remarks
Note: You have to enable jFlow export of the respective version on the monitored device
for this sensor to work. The device must send the flow data stream to the IP address of the
PRTG probe system on which the sensor is set up (either a local or remote probe).
1036
15.10.2015

66 jFlow V5 Sensor
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
15.10.2015
1037

66 jFlow V5 Sensor
JFLOW V5 SPECIFIC SETTINGS

Receive jFlow Packets
on UDP Port
Enter the UDP port number on which PRTG receives the flow
packets. It must match the one you have configured in the jFlow
integer value.
Note: When you configure the export, please make sure you select
the appropriate jFlow version for this sensor.
Sender IP
jFlow from. Enter an IP address to receive data from a specific

on IP
Select the IP address(es) on which PRTG listens to jFlow packets.

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

(Minutes)
Enter a time span in minutes after which the sensor must have
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 that you set this one
minute longer than the respective timeout configured in your
Sampling Mode
below.
Sampling Rate

Log Stream Data to

1038
15.10.2015

66 jFlow V5 Sensor
JFLOW V5 SPECIFIC SETTINGS

Ot her channel.
only.

Channel Selection
UDP and TCP.
Ot her.
channel.
15.10.2015
1039

66 jFlow V5 Sensor

FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1040
15.10.2015

66 jFlow V5 Sensor
SENSOR DISPLAY
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
15.10.2015
1041

66 jFlow V5 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1042
15.10.2015

66 jFlow V5 Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
15.10.2015
1043

66 jFlow V5 Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1044
15.10.2015

66 jFlow V5 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
15.10.2015
1045

66 jFlow V5 Sensor
Toplists
More
Knowledge Base: Where is the volume line in graphs?

Notifications
Others
159
section.
Related Topics
3087
1046
3092
15.10.2015

67 jFlow V5 (Custom) Sensor
6.8.67 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
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/jflow_v 5.png
15.10.2015
1047

Remarks
Note: You have to enable jFlow export of the respective version on the monitored device
1048
officially.

Add Sensor
later.
Sensor Settings

Sensor Name
1048

171 .
15.10.2015


Parent Tags
Tags

default value.
Priority
JFLOW SPECIFIC SETTINGS

on UDP Port
Enter the UDP port number on which PRTG receives the flow
packets. It must match the one you have configured in the jFlow
integer value.
Sender IP
jFlow from. Enter an IP address to receive data from a specific

on IP
Select the IP address(es) on which PRTG listens to jFlow packets.

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
15.10.2015
1049

JFLOW SPECIFIC SETTINGS

Active Flow Timeout
(Minutes)
Enter a time span in minutes after which the sensor must have
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 that you set this one
minute longer than the respective timeout configured in your
Sampling Mode
below.
Sampling Rate

Channel Definition

please see Channel Defint ions for xFlow and Packet Sniffer
Sensors 3092 section. All traffic for which no channel is defined will
be accounted to the default channel named Ot her.
filters for the data you really want to analyse.
Log Stream Data to

Ot her channel.
only.
1050
15.10.2015

FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
15.10.2015

1051

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1052
15.10.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.10.2015
1053


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1054
15.10.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.10.2015
1055

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1056
15.10.2015

Toplists
More

Notifications
Others
159
section.
Related Topics
3087
15.10.2015
3092
1057

68 LDAP Sensor
6.8.68 LDAP Sensor

The LDAP sensor monitors directory services using Lightweight Directory Access Protocol
(LDAP), connecting to the server trying a "bind". If the server does not respond or
authentication fails, an it will show an error message.
The sensor shows the response time of the server.
LDAP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ldap.png
Add Sensor
later.
Sensor Settings
1058
24.03.2015

68 LDAP Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
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.
24.03.2015
1059

68 LDAP Sensor
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1060
24.03.2015

68 LDAP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1061

68 LDAP Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1062
24.03.2015

68 LDAP Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1063

68 LDAP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1064
159
section.
24.03.2015

69 Microsoft OneDrive Sensor
6.8.69 M icrosoft OneDrive Sensor

The Microsoft OneDrive sensor monitors a Microsoft OneDrive account using the OneDrive
Application Programming Interface (API) and OAuth2. It shows the following:
Mic rosoft OneDriv e Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/mic rosoft_onedriv e.png
Remarks
OAut h2 1073 .
Add Sensor
later.
31.08.2015
1065

MICR OSOFT CR EDENTIALS

This sensor type uses OAuth2 authentication to get access to your Microsoft account. For
OAut h2 1073 .
OAuth URL
Microsoft account using OAuth2. This is necessary to allow the
sensor to query data from OneDrive. A new browser window
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 781 .
Note: It is mandatory to connect this sensor to your OneDrive
Sensor Settings

Sensor Name

171 .
Parent Tags
1066
31.08.2015


Tags

default value.
Priority
MICR OSOFT CR EDENTIALS

OAuth Code
to your OneDrive account. Once a sensor is created, you cannot
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
31.08.2015
1067

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1068
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
31.08.2015
1069


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1070
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
1071

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1072
31.08.2015


service.
in PRTG.
31.08.2015
1073


Notifications
Others
1074
159
section.
31.08.2015

70 Microsoft SQL v2 Sensor
6.8.70 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/mic rosoft_sql_v 2.png
Remarks
Requires
1076
27.04.2016
1075

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 type supersedes the outdated Microsoft SQL sensor. We recommend that you
use this new sensor to monitor Microsoft SQL databases.
selection)
3033
3034
for channel value
depending on it?

this sensor.
Add Sensor
later.
Sensor Settings

Sensor Name
1076

171 .
27.04.2016


Parent Tags
Tags

default value.
Priority
DATABASE SPECIFIC
Database
Enter the name of the SQL database to which the sensor connects.
For example, such a database's name could be MyDatabase. This is
a logical entity on the database server where database objects like
tables or stored procedures exist.
SQL Server Instance
Define if you want to use an instance name for the database

connection. Choose between:
No inst ance name required (default ): Use the default instance
for the connection.
Use inst ance name: Use a named instance that you can specify
below.
Instance Name
This field is only visible if you enable instance name usage above.
Enter the named instance you want to monitor.
Encryption
Define encryption usage for the database connection. Choose

between:
Use server default s (default ): The database connection is only
encrypted if enforced by the database server.
27.04.2016
1077

DATABASE SPECIFIC
Enforce encry pt ion but do not validat e server cert ificat e:
Choose this option to make sure the database connection is
encrypted.
Enforce encry pt ion and validat e server cert ificat e: Choose
this option to force encryption and to validate the database
server certificate. This approach provides highest security, for
example, it helps preventing "man in the middle" attacks.
Note: The sensor validates the certificate only if the database
server enforces encryption!
DATA
SQL Query File

cluster node!
Use Transaction
executed.
1078
27.04.2016

DATA
Data Processing

Handle DBNull in
Channel Values as

by
below.
27.04.2016
1079

DATA
value was found.
Sensor Channel #x
3033
for an
Sensor Channel #x
Name
Sensor Channel #x
Column Number

integer value.
Sensor Channel #x
Column Name
Sensor Channel #x
Row Number
value.
1080
27.04.2016

DATA
string.
Sensor Channel #x
Mode
table.
Sensor Channel #x
Unit
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
Value Lookup
27.04.2016
1081

DATA
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Channel #x
Value Lookup
channel.
Sensor Message
defined channel.
Sensor Message
Column Number
integer value.
Sensor Message
Column Name
string.
Sensor Message Row

Number
integer value.
Sensor Message Key
Sensor Message

added.
1082
27.04.2016

DATA
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
27.04.2016

1083

Inherited Settings
described below.
1084
27.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
27.04.2016
1085


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1086
27.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
27.04.2016
1087

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1088
27.04.2016

More
depending on it?

Notifications
Others
27.04.2016
159
section.
1089

71 MySQL v2 Sensor
6.8.71 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
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/my sql.png
Remarks
Requires
1091
Save the SQL script with the query into the \Cust om Sensors\sql\my sql subfolder of your
find this path.
1090
27.04.2016

71 MySQL v2 Sensor
This sensor type supports MySQL server version 5.0 or later and might also work with
previous versions.
This sensor type supersedes the outdated MySQL sensor. We recommend that you to use
this new sensor to monitor MySQL databases.
selection)
3033
3034
for channel value
depending on it?

this sensor.
Add Sensor
later.
Sensor Settings

Sensor Name
27.04.2016

171 .
1091

71 MySQL v2 Sensor

Parent Tags
Tags

default value.
Priority
DATABASE SPECIFIC
Database
Enter the name of the MySQL database to which the sensor

connects. For example, such a database's name could be
MyDatabase. This is a logical entity on the database server where
database objects like tables or stored procedures exist.
The database name of a MySQL server also reflects a physical
directory structure where your database objects are stored. Enter
the appropriate string which is the same as you would supply
when invoking the mysql.exe admin tool (with the command line
switch -p) or after the login with mysql.exe with the command use.
DATA
SQL Query File
1092

27.04.2016

71 MySQL v2 Sensor
DATA
cluster node!
Use Transaction
executed.
Data Processing

27.04.2016
1093

71 MySQL v2 Sensor
DATA
Handle DBNull in
Channel Values as

by
below.
value was found.
Sensor Channel #x
3033
for an
1094
27.04.2016

71 MySQL v2 Sensor
DATA
Sensor Channel #x
Name
Sensor Channel #x
Column Number

integer value.
Sensor Channel #x
Column Name
Sensor Channel #x
Row Number
value.
string.
Sensor Channel #x
Mode
table.
Sensor Channel #x
Unit
BytesBandwidth
BytesMemory
27.04.2016
1095

71 MySQL v2 Sensor
DATA
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
Value Lookup
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Channel #x
Value Lookup
channel.
Sensor Message
defined channel.
Sensor Message
Column Number
1096
integer value.
27.04.2016

71 MySQL v2 Sensor
DATA
Sensor Message
Column Name
string.
Sensor Message Row

Number
integer value.
Sensor Message Key
Sensor Message

added.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
27.04.2016
1097

71 MySQL v2 Sensor
SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1098
27.04.2016

71 MySQL v2 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
27.04.2016
1099

71 MySQL v2 Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1100
27.04.2016

71 MySQL v2 Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
27.04.2016
1101

71 MySQL v2 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1102
27.04.2016

71 MySQL v2 Sensor
More
depending on it?

Notifications
Others
27.04.2016
159
section.
1103

72 NetApp cDOT Aggregate (SOAP) Sensor
6.8.72 NetApp cDOT Aggregate (SOAP) Sensor

The NetApp cDOT Aggregate (SOAP) sensor monitors a NetApp clustered Data ONTAP (cDOT)
storage aggregate accessing the cDOT web Application Programming Interface (API) via Simple
Object Access Protocol (SOAP). It can show the following:
Number of files on the aggregate
Status of the aggregate (online, restrict, offline)
Read and written blocks per second
User reads and writes per seconds
Free bytes in total and percent
NetApp c DOT Aggregate (SOAP) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/netapp_c dot_aggregate_soap.png
Remarks
The cDOT user account that you use with this sensor needs access to ONTAPI (DATA ONTAP
API) so that the sensor can request data from it. The access is enabled by default.
If API access is disabled, use the following command locally on the cluster console to enable
it: services web> modify -vserver clusterd -name ontapi -enabled true
Read-only user rights are sufficient for the cDOT user account that you use with this sensor
for access to ONTAPI. Modify or add this user with the role readonly in the console under
Clust er | Clust erX | Configurat ion | Securit y | Users
This sensor type supports ONTAPI version 1.21 (included in Ontap version 8.2.x) and ONTAPI
version 1.30 (included in Ontap version 8.3.x).
1104
11.03.2016

Add Sensor
later.
Select the aggregates you want to monitor. PRTG creates one sensor for each aggregate you
NETAPP CDOT SPECIFIC

NetApp cDOT
Aggregates
Select all aggregates for which you want to add a sensor. You see
table head.
Sensor Settings
11.03.2016
1105


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
NETAPP CDOT CR EDENTIALS

Username
Enter a username for access to the NetApp cDOT API. Read only
rights for this cDOT user account are sufficient. Please enter a
string.
Password
Enter the password of the user that you enter above for access to
the NetApp cDOT API. Please enter a string.
Port
Enter a port number on which you can access the NetApp cDOT
API. Please enter an integer value. The default port is 443.
Timeout (Sec.)

1106
11.03.2016


NetApp cDOT
Aggregates
Shows the aggregate that this sensor monitors. Once a sensor is

anew.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
11.03.2016
1107

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1108
11.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
11.03.2016
1109


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1110
11.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
11.03.2016
1111

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1112
159
section.
11.03.2016

73 NetApp cDOT I/O (SOAP) Sensor
6.8.73 NetApp cDOT I/O (SOAP) Sensor

The NetApp cDOT I/O (SOAP) sensor monitors input and output operations of a NetApp
clustered Data ONTAP (cDOT) storage system accessing the cDOT web Application
Programming Interface (API) via Simple Object Access Protocol (SOAP). It can show the
following:
Number of Common Internet File System (CIFS) operations per second
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
11.03.2016
1113

NetApp c DOT I/O (SOAP) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/netapp_c dot_io_soap.png
Remarks
1114
11.03.2016

Add Sensor
later.
Select the cDOT system nodes which you want to monitor. PRTG creates one sensor for each
node you choose in the Add Sensor dialog. The settings you choose in this dialog are valid

NetApp cDOT System
Nodes
Select all nodes for which you want to add a sensor. You see a list
head.
Sensor Settings
11.03.2016
1115


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

Username
string.
Password
Port
Timeout (Sec.)

1116
11.03.2016


NetApp cDOT System
Nodes
Shows the ID of the system node that this sensor monitors. Once
the sensor anew.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
11.03.2016
1117

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1118
11.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
11.03.2016
1119


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1120
11.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
11.03.2016
1121

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1122
159
section.
11.03.2016

74 NetApp cDOT Physical Disk (SOAP) Sensor
6.8.74 NetApp cDOT Phy sical Disk (SOAP) Sensor

The NetApp cDOT Physical Disk (SOAP) sensor monitors disks of a NetApp clustered Data
ONTAP (cDOT) storage system accessing the cDOT web Application Programming Interface
(API) via Simple Object Access Protocol (SOAP). It can show the following:
Latency of operations
Data read and write speed
NetApp c DOT Phy sic al Disk (SOAP) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/netapp_c dot_phy sic al_disk_soap.png
Remarks
11.03.2016
1123

Add Sensor
later.
Select the disks you want to monitor. PRTG creates one sensor for each aggregate you

NetApp cDOT Disks
Select all disks for which you want to add a sensor. You see a list
head.
Sensor Settings

Sensor Name
1124

171 .
11.03.2016


Parent Tags
Tags

default value.
Priority

Username
string.
Password
Port
Timeout (Sec.)


NetApp cDOT Disk
11.03.2016

1125


anew.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1126
11.03.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
11.03.2016
1127

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1128
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
1129


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1130
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
11.03.2016
159
section.
1131

75 NetApp cDOT System Health (SOAP) Sensor
6.8.75 NetApp cDOT Sy stem Health (SOAP) Sensor

The NetApp cDOT System Health (SOAP) sensor monitors the health of a NetApp clustered
Data ONTAP (cDOT) storage system accessing the cDOT web Application Programming
Interface (API) via Simple Object Access Protocol (SOAP). It can show the following:
Memory usage
CPU load
Uptime
NetApp c DOT Sy stem Health (SOAP) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/netapp_c dot_sy stem_health_soap.png
Remarks
1132
11.03.2016

Add Sensor
later.
Select the cDOT system nodes which you want to monitor. PRTG creates one sensor for each
node you choose in the Add Sensor dialog. The settings you choose in this dialog are valid

NetApp cDOT System
Nodes
Select the nodes for which you want to add a sensor. You see a
table head.
Sensor Settings

Sensor Name
11.03.2016

171 .
1133


Parent Tags
Tags

default value.
Priority

Username
string.
Password
Port
Timeout (Sec.)


NetApp cDOT System
Nodes
1134
Shows the ID of the system node that this sensor monitors. Once
11.03.2016


the sensor anew.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
11.03.2016
1135

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1136
11.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
11.03.2016
1137


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1138
11.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
11.03.2016
1139

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1140
159
section.
11.03.2016

76 NetFlow V5 Sensor
6.8.76 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.
15.10.2015
1141

NetFlow V5 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/netflow_v 5.png
Remarks
Note: You must enable NetFlow export of the respective version on the monitored device
1142
15.10.2015

Sniffer sensors?
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
15.10.2015
1143

NETFLOW SPECIFIC SETTINGS

Receive NetFlow
Packets on UDP Port
received. It must match the one you have configured in the
NetFlow export options of your hardware router device. Please
Note: When configuring export, make sure you select the
appropriate NetFlow version for this sensor.
Sender IP
NetFlow from. Enter an IP address to receive data from a specific
Receive NetFlow
Packets on IP
Select the IP address(es) on which PRTG listens to NetFlow

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.
Active Flow Timeout

(Minutes)
received. If the timeout is reached and no new data was received
during this time, the sensor switches to an Unknown status. Please
enter an integer value. We recommend that you set the timeout
one minute longer than the respective timeout configured in your
hardware router device. The maximum timeout is 60 minutes.
Sampling Mode
below.
Sampling Rate
1144

15.10.2015


Log Stream Data to
Ot her channel.
only.

Channel Selection
UDP and TCP.
Ot her.
channel.
15.10.2015
1145


FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1146
15.10.2015

SENSOR DISPLAY
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
15.10.2015
1147

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1148
15.10.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
15.10.2015
1149


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1150
15.10.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
15.10.2015
1151

Toplists
More
Sniffer sensors?

Notifications
Others
159
section.
Related Topics
3087
1152
3092
15.10.2015

77 NetFlow V5 (Custom) Sensor
6.8.77 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.
15.10.2015
1153

NetFlow V5 Sensor
Remarks
1154
15.10.2015

1155
officially.

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
15.10.2015
1155


Priority

Receive NetFlow
Packets on UDP Port
Sender IP
Receive NetFlow
Packets on IP

the check box in the table head. The IP address you select here
must match the one you have configured in the NetFlow export
options of your hardware router device.
Note: When configuring export, please make sure you select the
Active Flow Timeout

(Minutes)
value. We recommend that you set the timeout one minute longer
than the respective timeout configured in your hardware router
device.
Sampling Mode
1156
15.10.2015


below.
Sampling Rate

Channel Definition

please see Channel Definit ions for xFlow, IPFIX , and Packet
Sniffer Sensors 3092 section. All traffic for which no channel is
defined will be accounted to the default channel named Ot her.
Log Stream Data to

Ot her channel.
only.
FILTER ING
Include Filter
section.
Exclude Filter
15.10.2015
1157

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1158
15.10.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.10.2015
1159


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1160
15.10.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.10.2015
1161

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1162
15.10.2015

Toplists
More

Notifications
Others
159
section.
Related Topics
3087
15.10.2015
3092
1163

6.8.78 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.
1164
15.10.2015

NetFlow V9 Sensor
Remarks
Sniffer sensors?
15.10.2015
1165

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1166
15.10.2015


Receive NetFlow
Packets on UDP Port
Sender IP
Receive NetFlow
Packets on IP

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.
Active Flow Timeout

(Minutes)
received. If the timeout is reached and no new data was received
during this time, the sensor switches to an Unknown status. Please
enter an integer value. We recommend that you set the timeout
one minute longer than the respective timeout configured in your
hardware router device. The maximum timeout is 60 minutes.
Sampling Mode
below.
Sampling Rate

Log Stream Data to

15.10.2015
1167


Ot her channel.
only.

Channel Selection
UDP and TCP.
Ot her.
channel.
1168
15.10.2015


FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
15.10.2015
1169

SENSOR DISPLAY
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1170
15.10.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.10.2015
1171


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1172
15.10.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.10.2015
1173

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1174
15.10.2015

Toplists
More
Sniffer sensors?

Notifications
Others
159
section.
Related Topics
3087
15.10.2015
3092
1175

6.8.79 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
1176
15.10.2015

Remarks
1177
officially.

Add Sensor
later.
Sensor Settings

Sensor Name
15.10.2015

171 .
1177


Parent Tags
Tags

default value.
Priority

Receive NetFlow
Packets on UDP Port
Sender IP
Receive NetFlow
Packets on IP

the check box in the table head. The IP address you select here
must match the one you have configured in the NetFlow export
options of your hardware router device.
Note: When configuring export, please make sure you select the
1178
15.10.2015


Active Flow Timeout
(Minutes)
value. We recommend that you set the timeout one minute longer
than the respective timeout configured in your hardware router
device.
Sampling Mode
below.
Sampling Rate

Channel Definition

please see Channel Definit ions for xFlow, IPFIX , and Packet
Sniffer Sensors 3092 section. All traffic for which no channel is
defined will be accounted to the default channel named Ot her.
Log Stream Data to

Ot her channel.
only.
15.10.2015
1179

FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist
1180

15.10.2015

PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
15.10.2015
1181

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1182
15.10.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
15.10.2015
1183


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1184
15.10.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
15.10.2015
1185

Toplists
More

Notifications
Others
159
section.
Related Topics
3087
1186
3092
15.10.2015

80 Oracle SQL v2 Sensor
6.8.80 Oracle SQL v2 Sensor

The Oracle SQL v2 sensor monitors a database on an Oracle server and executes a defined
query.
Orac le SQL v 2 Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/orac le_sql_v 2.png
Remarks
Requires
1188
27.04.2016
1187

Save the SQL script with the query into the \Cust om Sensors\sql\oracle subfolder of your
find this path.
This sensor type supports Oracle database servers version 10.2 or higher.
This sensor type supersedes the outdated Oracle SQL sensor. We recommend that you use
this new sensor to monitor Oracle SQL databases.
selection)
3033
3034
for channel value
depending on it?

this sensor.
Add Sensor
later.
Sensor Settings

Sensor Name
1188

171 .
27.04.2016


Parent Tags
Tags

default value.
Priority
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.
27.04.2016
1189

DATA
SQL Query File

cluster node!
Use Transaction
executed.
Data Processing

1190
27.04.2016

DATA
Handle DBNull in
Channel Values as

by
below.
value was found.
Sensor Channel #x
3033
for an
27.04.2016
1191

DATA
Sensor Channel #x
Name
Sensor Channel #x
Column Number

integer value.
Sensor Channel #x
Column Name
Sensor Channel #x
Row Number
value.
string.
Sensor Channel #x
Mode
table.
Sensor Channel #x
Unit
1192
27.04.2016

DATA
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
Value Lookup
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Channel #x
Value Lookup
channel.
Sensor Message
defined channel.
27.04.2016
1193

DATA
Sensor Message
Column Number
integer value.
Sensor Message
Column Name
string.
Sensor Message Row

Number
integer value.
Sensor Message Key
Sensor Message

added.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel
1194

27.04.2016

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
27.04.2016
1195

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1196
27.04.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
27.04.2016
1197


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1198
27.04.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
27.04.2016
1199

More
depending on it?

Notifications
Others
1200
159
section.
27.04.2016

81 Oracle Tablespace Sensor
6.8.81 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
Orac le Tablespac e Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/orac le_tablespac e.png
Remarks
This sensor type supports Oracle database servers version 10.2 or higher.
Requires
1202
Requires 1202 sufficient privileges for the account that you use for the connection. We
recommend that you use the SYSTEM account.
11.03.2016
3033
1201


this sensor.
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 the Oracle System ID 1203 to access
the tablespace selection. Select the tablespaces in the Oracle database you want to monitor.
PRTG creates one sensor for each tablespace you choose. The settings you choose in this
1202
11.03.2016

TABLESPACE SPECIFIC
Tablespace
Select the tablespaces you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
11.03.2016
1203

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
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.
TABLESPACE SPECIFIC
Tablespace
Shows the tablespace that this sensor monitors. Once a sensor is

anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1204
11.03.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
11.03.2016
1205

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1206
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
1207


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1208
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
11.03.2016
1209

Others
1210
159
section.
11.03.2016

82 Packet Sniffer Sensor
6.8.82 Packet Sniffer Sensor

The Packet Sniffer sensor monitors the headers of data packets that pass a local network card
using built-in packet sniffer. You can choose from predefined channels. The sensor analyzes
only header traffic.
Chat (IRC, AIM)
Citrix
NetBIOS
Total traffic
sensor setup.
22.10.2015
1211

Pac ket Sniffer Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/pac ket_sniffer.png
Remarks
By default, this sensor works only on a probe device.
Sniffer sensors?
For a general introduction to the technology behind packet sniffing, please see manual
section Monit oring Bandwidt h via Packet Sniffing 3010 .
1212
22.10.2015

Note: By default, you can only monitor traffic passing the PRTG probe system on which's Probe
Device the sensor is set up (either a local or remote probe). To monitor other traffic in your
network, you can configure a monitoring port (if available) to which the switch sends a copy of
all traffic. You can then physically connect this port to a network card of the computer the
PRTG probe (either local or remote probe) is running on. This way, PRTG can analyze the
complete traffic that passes through the switch. This feature of your hardware may be called
Switched Port Analyzer (SPAN), port mirroring, or port monitoring.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
22.10.2015
1213


Priority
SNIFFER SPECIFIC
Include Filter
the sensor includes all traffic. To include specific traffic only, define
section.
Exclude Filter
First, the filters you define in the Include Filt er field are
considered. From this subset, you can explicitly exclude traffic,
using the same syntax. For detailed information, please see Filt er
Rules for xFlow, IPFIX , and Packet Sniffer Sensors 3087 section.
Network Adapters
Define the network adapters that this sensor monitors. You see a
list of names with all adapters available on the probe system. To
select an adapter, set a check mark symbol in front of the
respective name. You can also select and deselect all items by
using the check box in the table head.
Log Stream Data to

None (recommended): Do not write additional log files. We
recommend this for normal use cases.
Ot her channel.
only.
1214
22.10.2015


Channel Selection
UDP and TCP.
Ot her.
channel.
22.10.2015
1215

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1216
22.10.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
22.10.2015
1217


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1218
22.10.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
22.10.2015
1219

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1220
22.10.2015

Toplists
More
Sniffer sensors?

Notifications
Others
159
section.
Related Topics
3087
22.10.2015
3092
1221

83 Packet Sniffer (Custom) Sensor
6.8.83 Packet Sniffer (Custom) Sensor

The Packet Sniffer (Custom) sensor monitors the headers of data packets that pass a local
network card using built-in packet sniffer. You can define your own channels. There are no
predefined channels for this sensor type. This sensor analyzes only header traffic.
sensor setup.
Pac ket Sniffer Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/pac ket_sniffer.png
1222
02.11.2015

Remarks
By default, this sensor works only on a probe device.
1223
officially.
For a general introduction to the technology behind packet sniffing, please see manual
section Monit oring Bandwidt h via Packet Sniffing 3010 .
Note: By default, you can only monitor traffic passing the PRTG probe system on which's Probe
Device the sensor is set up (either a local or remote probe). To monitor other traffic in your
network, you can configure a monitoring port (if available) to which the switch sends a copy of
all traffic. You can then physically connect this port to a network card of the computer the
PRTG probe (either local or remote probe) is running on. This way, PRTG will be able to analyze
the complete traffic that passes through the switch. This feature of your hardware may be
called Switched Port Analyzer (SPAN), port mirroring, or port monitoring.

Add Sensor
later.
Sensor Settings
02.11.2015
1223


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SNIFFER SPECIFIC
Include Filter
the sensor includes all traffic. To include specific traffic only, define
Filt er Rules for xFlow and Packet Sniffer Sensors 3087 section.
Exclude Filter
First, the filters you define in the Include Filt er field are
considered. From this subset, you can explicitly exclude traffic,
using the same syntax. For detailed information, please see Filt er
Rules for xFlow and Packet Sniffer Sensors 3087 section.
Channel Definition

Sensors 3092 section. All traffic for which no channel is defined is
accounted to the default channel named Ot her.
1224
02.11.2015

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

Ot her channel.
only.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
02.11.2015
1225

SENSOR DISPLAY
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1226
02.11.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
02.11.2015
1227


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1228
02.11.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
02.11.2015
1229

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1230
02.11.2015

Toplists
More

Notifications
Others
159
section.
Related Topics
3087
02.11.2015
3092
1231

84 PerfCounter Custom Sensor
6.8.84 PerfCounter Custom Sensor

The PerfCounter Custom sensor monitors a configured set of Windows Performance Counters.
You can define your own channels. There are no predefined channels available for this sensor
type. To find out which performance counters are available on the target system and what
their names are, please see section More 1241 .
This sensor can show Windows performance counters individually to your needs.
sensor setup.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/perfc ounter_c ustom.png
Remarks
Requires
1233
Windows credentials in the parent device settings.
Requires
1233
the Windows Remote Registry service to be running on the target computer.
Requires
1233
Windows Server 2008 R2 or later on the probe system.
Knowledge Base: How can I find out the names of available Performance Counters?
Knowledge Base: My Performance Counter sensor does not work. What can I do?
Note: You cannot add different performance counters with the same name to one sensor.
Note: If a performance counter contains angle brackets (< or >), please do not edit the
channel settings because this might cause an error.
1232
21.01.2016


possible.
Note: The user account has to be a member of the Performance Monitor Users user group on
the target system.

RemoteRegistry "Remote Registry" Windows service is running on the target computer. If you
fail to do so, a connection via Performance Counters will not be possible.
Type to Automatic.

Windows version 2008 R2 or later is installed on the computer running the PRTG probe: This is
remote probe 3109 .
Add Sensor
later.
21.01.2016
1233

PER FOR MANCE COU NTER SETTINGS

List of Counters
Enter a list of performance counters which will be queried. Define

one counter per row. PRTG will create one channel for each
counter. Use the following syntax: the name of the counter,
followed by two colons (::) and the unit.
Example: \Processor(_Total)\% Processor Time::%
Note: 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 2707 . 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.
Note: If your custom performance counter includes an angle
bracket (< or >), please do not edit the Sensor Channels Set t ings
2711 (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. Note: Please make sure that all counters which are
monitored are capable of this mode if you select it.
Sensor Settings
1234
21.01.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
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
Primary Channel
21.01.2016

1235

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1236
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
1237


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1238
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
1239

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1240
21.01.2016

More
Knowledge Base: How can I find out the names of available Performance Counters?
Knowledge Base: Remote Monitoring of Specific Performance Counters
Notifications
Others
21.01.2016
159
section.
1241

85 PerfCounter IIS Application Pool Sensor
6.8.85 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 135 Up), Initialized or Shutdown
Pending (Warning), or 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/PerfCounter_IIS_Applic ation_Pool.png
1242
28.04.2015

Remarks
Requires
1243
Microsoft IIS version 7.5 or later on the target system.
Requires
1243
Windows credentials in the parent device settings.
Requires
1243
Requires
1243
Windows Server 2008 R2 or later on the probe system.
Requirement: Microsoft IIS Version 7.5

In order to monitor Microsoft Internet Information Services (IIS) application pools, this sensor
needs IIS version 7.5 or later to be installed on the target system.

possible.
Note: The user account has to be a member of the Performance Monitor Users user group on
the target system.

RemoteRegistry "Remote Registry" Windows service is running on the target computer. If you
fail to do so, a connection via Performance Counters will not be possible.
Type to Automatic.

Windows version 2008 R2 or later is installed on the computer running the PRTG probe: This is
remote probe 3109 .
28.04.2015
1243

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 in this dialog are valid for all of the sensors that are created.
IIS APPLICATION POOL SPECIFIC

Application Pool
Select the application pools you want to add a sensor for. You see
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
1244
28.04.2015


Tags

default value.
Priority
IIS APPLICATION POOL SPECIFIC

Application Pool
Shows the name of the application pool that this sensor monitors.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
28.04.2015
1245

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1246
28.04.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
28.04.2015
1247


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1248
28.04.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
28.04.2015
1249

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1250
28.04.2015


Notifications
Others
28.04.2015
159
section.
1251

86 Ping Sensor
6.8.86 Ping Sensor

The Ping sensor sends an Internet Control Message Protocol (ICMP) echo request ("Ping") from
the computer running the probe to the device it is created on to monitor the availability of a
device. Default is 5 pings per scanning interval.
Ping time
Minimum ping time when using more than one ping per interval
Maximum ping time when using more than one ping per interval
Packet loss in percent when using more than one ping per interval
Ping Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ping.png
Remarks
Knowledge Base: How to create/customize statistical PING sensor?
Knowledge Base: Can I create an inverse Ping sensor?
1252
09.05.2016

86 Ping Sensor
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
09.05.2016
1253

86 Ping Sensor
PING SETTINGS
Timeout (Sec.)
than this value defines, the sensor will cancel the request and
shows an error message. The maximum timeout value is 300
seconds (5 minutes).
Packet Size (Bytes)
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.
Note: When using multiple request, all of them have to get lost to
show a Down status 135 . For example, if there is only one Ping
request answered in a series of five, the sensor will still show a
green Up status.
Ping Count
This field is only visible if you enable sending multiple Pings above.
Enter the number of Pings that the sensor sends in a row for one
interval. Please enter an integer value. The default value is 5.
Ping Delay (in ms)
This field is only visible if you enable sending multiple Pings above.
Enter the time in milliseconds the sensor waits between two Ping
requests. Please enter an integer value. The default value is 5.
Note: Increase the value if the target device drops Ping packets
due to denial-of-service (DOS) suspicion.
Auto Acknowledge
You can define that a Down status of this sensor will be

acknowledged 162 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.
1254
09.05.2016

86 Ping Sensor
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
09.05.2016
1255

86 Ping Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1256
09.05.2016

86 Ping Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
09.05.2016
1257

86 Ping Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1258
09.05.2016

86 Ping Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: How to create/customize statistical PING sensor?
Knowledge Base: Can I create an inverse Ping sensor?


09.05.2016
1259

86 Ping Sensor
Notifications
Others
1260
159
section.
09.05.2016

87 Ping Jitter Sensor
6.8.87 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ping_jitter.png
Remarks
Requires 1262 .NET 4.0 or 4.5 on the probe system. Note: If the sensor shows the error PE087,
please additionally install .NET 3.5 on the probe system.
09.07.2015
1261


this sensor.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
1262
09.07.2015


Priority
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
Sensor Result

between:
09.07.2015
1263

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1264
09.07.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
09.07.2015
1265


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1266
09.07.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
09.07.2015
1267

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1268
09.07.2015

Others
09.07.2015
159
section.
1269

88 POP3 Sensor
6.8.88 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
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/pop3.png
Remarks
Add Sensor
later.
Sensor Settings
1270
04.11.2015

88 POP3 Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
POP3 SPECIFIC
Timeout (Sec.)

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.
04.11.2015
1271

88 POP3 Sensor

Sensor Specific

between:
status 135 .
SSL/TLS protocol.
1272
04.11.2015

88 POP3 Sensor
POP3
AU THENTICATION
Type
Select the kind of authentication for the POP3 connection.

Choose between:
Wit hout login: Monitor the connection to the POP3 server only.
Username and password: Log on to the POP3 server with
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
Enter a password for POP3 authentication. Please enter a string.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
04.11.2015
1273

88 POP3 Sensor
SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1274
04.11.2015

88 POP3 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
04.11.2015
1275

88 POP3 Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1276
04.11.2015

88 POP3 Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
04.11.2015
1277

88 POP3 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1278
159
section.
04.11.2015

89 Port Sensor
6.8.89 Port Sensor

The Port sensor monitors a network service by connecting to its port. It tries to connect to
the specified TCP/IP port number of a device and waits for the request to be accepted.
Depending on your settings, it can alert you either when the monitored port is open, or when
it is closed.
The sensor shows the time until a request to a port is accepted.
Port Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/port.png
Remarks
Add Sensor
later.
Sensor Settings
07.05.2015
1279

89 Port Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
POR T SPECIFIC
Timeout (Sec.)

Port
Enter the number of the port to which this sensor connects.

1280
07.05.2015

89 Port Sensor

Security

between:
Use Transport -Level Securit y (default ): Establish the
connection with the strongest TLS method that the target device
provides.
Do not use Transport -Level Securit y : Establish the connection
without encryption.
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 135 if the port is
open, and a red Down status if the port is closed.
Closed: The sensor shows a green Up status if the port is
closed, and a red Down status if the port is open.
Command
Define whether the sensor will send a command after opening the
port. Choose between:
Don't send command: Only check if a connection to the port is
possible.
Send command: Open a Telnet session to the respective port
and send the command.
Note: You cannot use this option if the target machine is a web
server.
Command
This field is only visible if you enable sending a command above.

Enter a command that the sensor sends in a Telnet session to the
respective port. You cannot use line breaks, but a simple Telnet
command in a single line only. Please enter a string.
Response
Define if the sensor will process the received response further.

Choose between:
Ignore response: Do not check the response.
Check response code (int eger): Check if the response matches
a defined response code. Define below.
07.05.2015
1281

89 Port Sensor
ADVANCED SENSOR SETTINGS

Check response t ext : Check if the response matches a defined
response text. Define below.
Allowed Code
This field is only visible if you enable response code check above.
Enter a code that the target device must return. If it does not
match, the sensor will show a Down status. Please enter an integer
value.
Check For Existing

Keywords (Positive)
This setting is only visible if you activated text processing above.

Check if a certain keyword is part of the received value. If there is
no match, the sensor shows a "Down" status.
Disable: Do not check for positive keywords.
Enable key word check (posit ive): Check if a certain keyword
exists in the received value. Define below.
Text Must Include
This setting is only visible if you activated keyword check above.

Enter a search string that the returned value must contain.
For Keyword Search

Use
Define the method that you want to use for the search string.
Choose between:
Plain Text : Search for a simple string.
Check For Existing

Keywords (Negative)
This setting is only visible if you activated text processing above.

Check if a certain keyword is not part of the received value. If
there is a match, the sensor shows a "Down" status.
Disable: Do not check for negative keywords.
Enable key word check (negat ive): Check if a certain keyword
does not exist in the received value. Define below.
Text Must Not Include
This setting is only visible if you activated keyword check above.

Enter a search string that the returned value must not contain.
For Keyword Search

Use
Define the method you want to use for the search string. Choose
between:
Plain Text : Search for a simple string.
1282
07.05.2015

89 Port Sensor
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
07.05.2015

1283

89 Port Sensor
Inherited Settings
described below.
1284
07.05.2015

89 Port Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
07.05.2015
1285

89 Port Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1286
07.05.2015

89 Port Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
07.05.2015
1287

89 Port Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1288
159
section.
07.05.2015

90 Port Range Sensor
6.8.90 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
about open/closed ports.
2711
. This way you can get alerts
Port Range Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/port_range.png
Remarks
Add Sensor
later.
07.05.2015
1289

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
POR T R ANGE SPECIFIC

Timeout (Sec.)

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.
1290
07.05.2015

POR T R ANGE SPECIFIC

Port Range Selection
Method
Define whether you want to monitor all ports within a range or if

you want to monitor several individual ports. Choose between:
Port range wit h st art /end: Monitor ports within a range.
List of port s: Monitor several individual ports.
Range Start
This field is only visible if you enable the port range method above.
Enter the port number where the scan starts. Please enter an
integer value.
Range End
This field is only visible if you enable the port range method above.
Enter the port number where the scan ends. Please enter an
integer value.
Port List
This field is only visible if you enable the list of ports method
above. Enter the numbers of the ports the sensor will try to
connect to. Enter one or more individual integer values, each port
in one line.
If Value Changes
Define what the sensor will do if the number of closed ports or

open ports changes. Choose between:
Ignore changes: No action is taken on change.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
07.05.2015
1291

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1292
07.05.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
07.05.2015
1293


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1294
07.05.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
07.05.2015
1295

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1296
159
section.
07.05.2015

91 PostgreSQL Sensor
6.8.91 PostgreSQL Sensor

The PostgreSQL sensor monitors a database on a PostgreSQL server and executes a defined
query.
PostgreSQL Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/postgresql.png
Remarks
Requires
1298
27.04.2016
1297

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 3135 for more information about
how to find this path
This sensor type supports PostgreSQL 7.x or later.
selection)
3033
3034
for channel value
depending on it?

this sensor.
Add Sensor
later.
Sensor Settings

Sensor Name
1298

171 .
27.04.2016


Parent Tags
Tags

default value.
Priority
DATABASE SPECIFIC
Database
Enter the name of the PostgreSQL database to which the sensor

connects. For example, such a database's name could be
MyDatabase. This is a logical entity on the database server where
database objects like tables or stored procedures exist.
SSL Mode
Select the PostgreSQL SSL mode for the sensor connection.

PostgreSQL SSL connections require OpenSSL to be installed on
both the target server and on the PRTG probe system with this
sensor. The SSL mode options you can choose here are the same
as the values of the PostgreSQL sslmode parameter. PRTG sends it
with the sensor requests.
Choose between these SSL modes:
Disable
Allow
Prefer
Require
For details about the PostgreSQL SSL modes, please refer to the
PostgreSQL documentation.
27.04.2016
1299

DATA
SQL Query File

cluster node!
Use Transaction
executed.
Data Processing

1300
27.04.2016

DATA
Handle DBNull in
Channel Values as

by
below.
value was found.
Sensor Channel #x
3033
for an
27.04.2016
1301

DATA
Sensor Channel #x
Name
Sensor Channel #x
Column Number

integer value.
Sensor Channel #x
Column Name
Sensor Channel #x
Row Number
value.
string.
Sensor Channel #x
Mode
table.
Sensor Channel #x
Unit
1302
27.04.2016

DATA
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
Value Lookup
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Channel #x
Value Lookup
channel.
Sensor Message
defined channel.
27.04.2016
1303

DATA
Sensor Message
Column Number
integer value.
Sensor Message
Column Name
string.
Sensor Message Row

Number
integer value.
Sensor Message Key
Sensor Message

added.
Sensor Result

between:
SENSOR DISPLAY
Primary Channel
1304

27.04.2016

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
27.04.2016
1305

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1306
27.04.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
27.04.2016
1307


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1308
27.04.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
27.04.2016
1309

More
depending on it?

Notifications
Others
1310
159
section.
27.04.2016

92 Probe Health Sensor
6.8.92 Probe Health Sensor

The Probe Health sensor monitors internal PRTG parameters. It shows the status of the PRTG
probe (either for the local probe, a remote probe 3109 , or a cluster 87 probe).
It checks various parameters of your PRTG system which can affect the quality of the
monitoring results:
Healt h: This index value sums up the probe state into a value between 100% (healthy) and
0% (failing). Frequent or repeated health values below 100% should be investigated.
Probe Process CPU Load: This channel shows the current percentage CPU load that the
probe process causes. Extensive CPU load can lead to false, incomplete, and incorrect
monitoring results. This value usually should stay below 50%.
Dat a St orage Free: This channel shows the free disk space on the probe system.
Approximately you need 200 KB disk space per sensor per day (with a 60 seconds scanning
interval 272 ).
Handles: This is a counter for the data structures of the operating system. It is responsible
for internal resource management. Repeated obviously increasing values should be
investigated.
Int erval Delay non-WMI&SNMP: This channel shows the percentage interval delay for all
sensor types which are not from the type SNMP or WMI. If this value is over 0%, try to
increase the scanning intervals 272 or distribute your sensors over multiple probes 3109 .
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 272 or distribute the sensors over several probes 3109 .
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 272 or distribute the sensors
over several probes 3109 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 3012 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 3109 .
Message Queue: This channel shows the number of monitoring results from the probe
which have not been processed yet by the core. This value usually should stay below 1/10
of the sensor count.
Open Request s: This channel shows the number of currently active monitoring requests.
This value should stay below the maximum of 500 open requests.
Sy slog Buffer: This channel shows the number of buffered syslog packages. Usually, this
value should be 0 (or very low). Investigate increasing values.
08.10.2015
1311

Threads: This channel shows the number of program parts which are running simultaneously
currently. This value can increase with heavy load. The number should not exceed 100 in
normal operation.
Toplist Memory : This channel shows the amount of RAM that the Toplist s 2734 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 3109
.
Trap Buffer: This channel shows the number of buffered SNMP traps. Usually, this value
should be 0 (or very low). Investigate increasing values.
Probe Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/probe_health.png
1312
08.10.2015

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
a cluster 87 probe).
3109
, or
Knowledge Base: My probe system is running out of disk space. What can I do?
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
08.10.2015
1313

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1314
08.10.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
08.10.2015
1315

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1316
08.10.2015

More
Knowledge Base: My probe system is running out of disk space. What can I do?

Notifications
Others
08.10.2015
159
section.
1317

93 Python Script Advanced Sensor
6.8.93 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. For details about the
return value format please see the Applicat ion Programming Int erface (API) Definit ion 3086 .
PRTG includes a CPython 3.4.2 interpreter to execute Python scripts for this sensor type.
Because of this you do not have to install anything manually to use the Python Script
Advanced sensor. Your Python scripts must be compatible to Python 3 to run with this
interpreter. It is located in the the \Py t hon34 subfolder of your PRTG program directory. You
can find the paepy package to easily create PRTG API conforming JSON output in the
\Py t hon34\Lib\sit e-packages folder.
The sensor can show values returned by the Python script in multiple channels.
Py thon Sc ript Adv anc ed Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/py thon_sc ript_adv anc ed.png
Remarks
You must store the script file on the system of the probe on which 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
script does not run longer than this.
1323
minus 1 second. Ensure your Python
Print commands in the Python script are not supported and lead to an invalid JSON result.
Exceptions in the script are not supported.
1318
31.08.2015

Sensor channel values greater than 2^62 are not supported.

1319
officially.

Add Sensor
later.
SENSOR SETTINGS
Python Script
Select a Python script from the list. The sensor will execute it with
every scanning interval 1323 .
This list shows all Python script files available in the \Cust om
Sensors\py t hon sub-directory of the probe system's PRTG
program directory (see Dat a St orage 3135 ). 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.
find detailed information on the Cust om Sensors tab.
Sensor Settings
31.08.2015
1319


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
Python Script
Shows the Python script file that the sensor executes with each
scan as defined on sensor creation. Once a sensor is created, you
Security Context
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).
1320
31.08.2015

SENSOR SETTINGS
user account defined in the settings of the parent device on
which you create this sensor. Please navigate to parent device
settings 324 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 324 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
given to the script.
Transmit Linux credent ials: Linux credentials
the script.
Transmit SNMP credent ials: SNMP credentials
the script.
329
332
329
are
are given to
are given to
Transmit all device credent ials: Windows, Linux, and SNMP

credentials are all given to the script.
Note: 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.
Note: 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
DEBU G OPTIONS
Sensor Result
31.08.2015

between:
1321

DEBU G OPTIONS
Note: You can use Writ e sensor result t o disk to inspect the passed JSON object that
contains all parameters. This way you can find out which key you can access when you script.
Note: Transmitted passwords are masked in the log file.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
1322

31.08.2015

Inherited Settings
described below.
31.08.2015
1323

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1324
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
1325


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1326
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
31.08.2015
1327

More

Notifications
Others
1328
159
section.
31.08.2015

94 QoS (Quality of Service) One Way Sensor
6.8.94 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
24.03.2015
1329

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/qos.png
Remarks
Note: You have to configure at least one remote probe
work.
3108
in your setup for this sensor to
You can create this sensor on the Probe Device of either a local or remote probe.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
1330
24.03.2015


Priority
24.03.2015
1331

QU ALITY OF SER VICE MEASU R EMENT

Timeout (Sec.)

Target Probe
Define the target probe that will receive the UDP packets. The drop
down menu shows all local and remote probes of your setup.
When running the sensor on the local probe, select a remote
probe as Target Probe. If no remote probe is available, please
install and connect a remote probe 3108 first. When running the
sensor on a remote probe, select either another remote probe or
the local probe as target. The sensor will measure values for the
network track between the probe the sensor is created on and
the target probe.
Note: You must ensure that firewalls, NAT rules, etc. allow UDP
packets to reach the target probe. The Windows firewall on the
target system will be opened automatically by the probe.
Target Host/IP
Define the IP address of the target probe to which the probe the
sensor is created on connects. If you do not use NAT rules, this is
usually the address shown above next to the target probe's name.
Port
Define the source and t arget port for the UDP packets. This port
is used on both the source and target probe. Use a different port
for each QoS sensor to make sure packets can be assigned
correctly. Enter an integer value between 1024 and 65536.
Note: This port must be available on both the source and target
system.
Number of Packets
Define how many packets the sensor sends with each scanning
interval. Please enter an integer value. Default value is 1000. We
Size of Packets (Bytes)
Define the size in bytes of the packets which the sensor sends.
Please enter an integer value. Default value is 172. We recommend
Time between Packets

(ms)
Define the time in milliseconds that the sensor waits between two
packets. Please enter an integer value. Default value is 20. We
1332
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1333

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1334
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1335


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1336
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
24.03.2015
159
section.
1337

95 QoS (Quality of Service) Round Trip Sensor
6.8.95 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
1338
31.08.2015

QoS (Quality of Serv ic e) Round Trip Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/qos_round_trip.png
Remarks
Note: You have to configure at least one remote probe 3108 in your setup, or you need to set
up the PRTG QoS Reflector tool on the target machine at the endpoint of the monitored
connection.
Knowledge Base: How can I monitor QoS roundtrips without using remote probes?
Knowledge Base: How does PRTG calculate the MOS score for QoS sensors?
31.08.2015
1339

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1340
31.08.2015

QU ALITY OF SER VICE MEASU R EMENT

Timeout (Sec.)

QoS Target
Define the type of target that will receive the UDP packets. Choose
between:
PRTG Probe (recommended): The connection endpoint is a
PRTG probe.
Cust om Target : Choose this option if you want to use the PRTG
QoS Reflector as connection endpoint. See section More 1346 for
information about this tool.
Target Probe
This setting is only available if you select PRTG probe as QoS

target. In the drop down menu, you see all local and remote
probes of your setup.
When running the sensor on the local probe, select a remote
probe as Target Probe. If no remote probe is available, install and
connect a remote probe 3108 first or use the QoS Reflector. When
running the sensor on a remote probe, select either another
remote probe or the local probe as target. The sensor will measure
values for the network track between the probe the sensor is
created on and the target probe.
Note: You must ensure that firewalls, NAT rules, etc. will allow the
UDP packets to reach the target probe. The Windows firewall on
the target system will be automatically opened by the probe. For
further information, see the More 1346 section below.
Target Host/IP
Define the IP address of the QoS target. If you use the QoS
Reflector, enter the address of the machine on which the reflector
script runs. If you use a probe, enter the address of the probe to
which the probe the sensor is created on connects. If you do not
use NAT rules, this is usually the address shown above next to the
target probe's name.
Port
Define the source and t arget port for the UDP packets. This port
will be used on both the source and target probe resp. machine.
Use a different port for each QoS sensor to make sure packets can
be assigned correctly. Enter an integer value between 1024 and
65536.
Note: This port must be available on both the source and target
system.
Number of Packets
Size of Packets (Bytes)

31.08.2015
Define how many packets the sensor sends for each scanning
interval. Please enter an integer value. Default value is 1000. We
Define the size in bytes of the packets which the sensor sends.
Please enter an integer value. Default value is 172. We recommend
1341

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1342
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
1343


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1344
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
1345

ACCESS R IGHTS
User Group Access
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?

1346
31.08.2015

Notifications
Others
31.08.2015
159
section.
1347

96 RADIUS v2 Sensor
6.8.96 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 135 Up), Access-Challenge (sensor status
Warning), Access-Reject (sensor status Down)
If authentication fails, the sensor shows a Down status
135
RADIUS v 2 Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/radius_v 2.png
Remarks
Note: This sensor type supersedes the outdated RADIUS sensor. We recommend that you
use this new sensor to monitor RADIUS servers.
Requires
1349
1348
04.11.2015

96 RADIUS v2 Sensor

this sensor.
Required .NET version (with latest update): .NET 4.5 or .NET 4.6. Please see the section More
below for details.
Add Sensor
later.

Sensor Name

171 .
Parent Tags
Tags

default value.
04.11.2015
1349

96 RADIUS v2 Sensor

Priority
1350
04.11.2015

96 RADIUS v2 Sensor
R ADIU S SPECIFIC
Timeout (Sec.)

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

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 server. Please
enter a string.
Port
Enter the port number that is used for the connection to the
server. The default value is 1812. Please enter an integer value.
Network Access
Server
Define how to identify the Network Access Server (NAS). Choose

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.
Sensor Result

between:
04.11.2015
1351

96 RADIUS v2 Sensor
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1352
04.11.2015

96 RADIUS v2 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
04.11.2015
1353

96 RADIUS v2 Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1354
04.11.2015

96 RADIUS v2 Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
04.11.2015
1355

96 RADIUS v2 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1356
04.11.2015

96 RADIUS v2 Sensor
Others
04.11.2015
159
section.
1357

97 RDP (Remote Desktop) Sensor
6.8.97 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.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/rdp_remote_desktop.png
Add Sensor
later.
Sensor Settings
1358
24.03.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SPECIFIC
Timeout (Sec.)

Port

Please enter an integer value. Default value is 3389. We
24.03.2015
1359

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1360
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1361


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1362
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1363

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1364
24.03.2015

Others
24.03.2015
159
section.
1365

98 Share Disk Free Sensor
6.8.98 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.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/share_disk_free.png
Remarks
Requires
1366
the LanmanServer Windows service to be running on the target device.
Note: This sensor only works if no quotas are enabled on the target share. If there are
quotas enabled for the user account this sensor uses to connect to the share, the absolute
value will be okay, but the percentage variable will show wrong values.
PE032
Requirement: Server Service

In order to monitor shares on Windows machines, please make sure the LanmanServer "Server"
Windows service is running on the target computer.
Type to Automatic.
1366
24.03.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
1367

SHAR E CONFIGU R ATION

Share
Enter the name of the share this sensor will monitor. Only a share
name is allowed here (for example, enter C$). Please do not enter a
complete UNC name here. The server name (\\server\) is taken
from the parent device of this sensor.
Note: To provide any shares under Windows, the LanmanServer
"Server" Windows service must be running on the target computer.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1368
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1369


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1370
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1371

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1372
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
1373

99 Sensor Factory Sensor
6.8.99 Sensor Factory Sensor

The Sensor Factory sensor is a powerful tool that allows you to monitor whole 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.
Note: The Sensor Factory sensor does not show values in the "Downtime" channel because
they cannot be calculated for this sensor type.
Note: If you want to create only a cumulated sensor status based on specific source sensors,
we recommend that you use the Business Process Sensor 481 instead.
sensor setup.
Sensor Fac tory Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sensor_fac tory .png
1374
05.11.2015

Remarks
1375
officially.
Ensure the scanning interval 1378 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.
Knowledge Base: How can I monitor the overall status of the business process "Email"?
Note: The Sensor Factory sensor might not work with flow sensors 3012 . Sensor types using
active flow timeout, this is, NetFlow and jFlow sensors 349 , are not supported by the Sensor
Factory sensor.
Note: Reports
146
cannot show uptime or downtime data for this sensor type.

Add Sensor
later.
Sensor Settings
05.11.2015
1375


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR FACTOR Y SPECIFIC SETTINGS

Channel Definition
Enter a channel definition for the sensor. Using a specific syntax,

you can refer to data from channels of other sensors here. You
can also calculate values. Enter one channel definition for each
new channel you want to add to this sensor. Please see section
Define Sensor Channels 1382 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:
1376
05.11.2015

SENSOR FACTOR Y SPECIFIC SETTINGS

Fact ory sensor shows error st at us when one or more source
sensors are in error st at us: If at least one sensor that you use
in a channel definition is in a Down status, the Factory sensor
shows a Down status as well until all referred sensors leave this
status. While the Factory sensor is Down, it will still show data of
all available sensor channels.
Note: If a lookup definition 3095 or an error limit 2712 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.
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.
Note: If a lookup definition 3095 or an error limit 2712 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 enable custom formula above. Define
when the sensor will switch to a Down status. You can use the
status() function in combination with Boolean operations. For
advanced users it is also possible to calculate a status value.
Please see section Define Sensor St at us 1389 below.
If a Sensor Has No
Data
Choose how this Sensor Factory sensor reacts if a sensor referred

to in the channel definition does not provide any data (for example,
because it is paused or does not exist). Choose between:
Do not calculat e fact ory channels t hat use t he sensor: For
defined channels that use one or more sensor(s) that deliver no
data, no data is shown. Additionally, the factory sensor shows a
Warning status.
Calculat e t he fact ory channels and use zero as source value:
If a sensor that you use in a channel definition does not deliver
any data, zero values will be filled in instead. The sensor factory
calculates the channel value and shows it using these zero
values.
05.11.2015
1377

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1378
05.11.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
05.11.2015
1379


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1380
05.11.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
05.11.2015
1381

ACCESS R IGHTS
User Group Access
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 core server.
1382
05.11.2015

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

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

Compare: = (equal), <> (not equal), > (greater), < (less), >= (greater or equal), <= (less or
equal)
If the comparison resolves to true, the value is 10,000; if false, the value is 0. For delta
sensors the speed is compared.
Example
You see a Sensor Factory channel definition with calculation.
#1:Traffic Total x Minus Traffic Out y
( channel(2001,-1) - channel(1004,1) ) * 2
This full channel definition results in a factory sensor that shows a calculation with values
from two channels (channel IDs -1 and 1) of two traffic sensors (sensor IDs 2001 and 1004).
The returned values are subtracted and then multiplied by two.
Channels can be gauge values (e.g., ping ms) or delta values (e.g., traffic kbit/s). Not all
combinations are allowed in a formula. Note: When performing percentage calculation, please
use the percent () Funct ion 1386 to make sure you obtain the expected values!
There are calculations you cannot do:
You cannot add/subtract a delta from a gauge channel (and vice-versa).
You cannot multiply two delta channels.
You cannot compare a delta with a gauge channel.
You cannot use a channel of (another) Sensor Factory sensor channel in the formula.
Define Sensor Channelschannel() Function

The channel() function allows to read the data from a channel of a different sensor. The syntax
is:
channel(<sensorId>,<channelId>)
The parameters are:

<sensorId> is the ID of the sensor. It is displayed on the sensor details page in the page
header bar 126 .
<channelId> is the ID of the sensor channel. It is displayed in the respective field of the
channel settings 2712 .
1384
05.11.2015

Example
channel(2001,2)
This function reads the data from channel ID 2 of the sensor with the ID 2001.
#1:Sample
channel(2001,2)
This full channel definition reads the data from channel ID 2 of the sensor with the ID 2001
and displays it in the first factory sensor channel (#1), without any additional calculations.
Define Sensor Channelsmin() and max() Functions

The min() and max() functions return the minimum or maximum of two values. The syntax is:
min(<a>,)
max(<a>,)
Values for <a> and are either numbers or channel()
1384
functions.
Examples
min(10,5)
This function in the first line returns 5, because this is the smaller value out of 10 and 5.
min( channel(2001,1),channel(2002,1) )
This function returns the minimum of the values of channel 1 of the sensor with ID 2001 and
channel 1 of the sensor with ID 2002.
Define Sensor Channelsavg() Function

The avg() function returns the average of the two values. This equals: (a+b) / 2. The syntax is:
avg(<a>,)
Values for <a> and are either numbers or channel()
05.11.2015
1384
functions.
1385

Examples
avg(20,10)
This function returns 15: (20+10) / 2 = 15.

avg( channel(2001,1),channel(2002,1) )
This function returns the average of channel 1 of the sensor with ID 2001 and channel 1 of
the sensor with ID 2002.
Define Sensor Channelspercent() Function

The percent () function calculates the percent value of two given values, for example, a channel
and a fixed value. The syntax is:
percent(<source>,<maximum>[,<unit>])
The parameters are:

<source> is the value the percent is calculated for. This is usually a channel()
1384
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 1388 section below for a list). This can be used for gauge (e.g., Ping
sensors) or delta (e.g., traffic sensors). If no unit is provided 1 will be used. Note: The sensor
adds the unit string % automatically.
PRTG will calculate: <source> / <maximum> * <unit> * 100
1386
05.11.2015

Examples
#1:Usage Traffic In
percent(channel(2001,0),100,kilobit)
#2:Usage Traffic Out
percent(channel(2001,1),100,kilobit)
This full channel definition results in a factory sensor that shows two channels of a traffic
sensor (sensor ID 2001): Traffic in (channel ID 0) and traffic out (channel ID 1). The sensor
displays the values % of maximum bandwidth (100 kilobit/second).
#1:Ping %
percent(channel(2002,0),200)
This full channel definition results in a factory sensor that shows the Ping Time channel
(channel ID 0) of a Ping sensor (sensor ID 2002). The sensor displays the values as a
percentage of 200 ms.
Define Sensor ChannelsHorizontal Lines

You can add lines to the graph using a formula without channel() function. Use a fixed value
instead. The syntax is:
#<id>:<name>[<unit>]
<value>
The parameters are:

<id> is the ID of the factory sensor's channel and must be a unique number > 1. Although
the sensor does not show a horizontal line as a channel, the ID has to be unique.
<name> is the name of the factory sensor's channel. PRTG does not display this name in
graphs and tables, but you can use it as a comment to describe the nature of the line.
[<unit >] is an optional unit description (e.g., kbit/s). If you do not provide a unit, PRTG
applies the line automatically to the scale of the first factory sensor channel. If your factory
sensor uses different units, provide a unit to make sure the line is added for the right scale.
Enter the unit exactly as shown in your graph's legend. If you enter a unit that does not yet
exist in your graph, a new scale will be added automatically.
<value> contains a number defining where the line will be shown in the graph.
05.11.2015
1387

Examples
#5:Line at 100ms [ms]
100
This channel definition results in a graph that shows a horizontal line at the value of 100 on
the ms scale.
#6:Line at 2 Mbit/s [kbit/s]
2000
This channel definition results in a graph that shows a horizontal line at the value of 2000 on
the kbit /s scale.
#1:Ping Time
channel(2002,0)
#2:Line at 120ms [ms]
120
This full channel definition results in a factory sensor that shows the Ping Time channel
(channel ID 0) of a Ping sensor (sensor ID 2002). Additionally, the sensor graphs will show a
horizontal line at 120 ms.
Define Sensor ChannelsConstants

The following constants are defined and can be used in calculations:
one = 1
kilo = 1000
mega = 1000 * kilo
giga = 1000 * mega
t era = 1000 * giga
by t e = 1
kiloby t e = 1024
megaby t e = 1024 * kilobyte
gigaby t e = 1024 * megabyte
t eraby t e = 1024 * gigabyte
bit = 1/8
kilobit = kilo / 8
megabit = mega / 8
1388
05.11.2015

gigabit = giga / 8
t erabit = tera / 8
Define Sensor Statusstatus() Function

The status of a Sensor Factory sensor can be controlled by the St at us Definit ion text field, if
you enable the custom formula option in the Sensor Set t ings 1375 . 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 126 .
<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.
05.11.2015
1389

Examples
status(2031) AND status(2044)
This changes the factory sensor to a Down status if both sensors, with IDs 2031 and 2044,
are Down. Otherwise the factory sensor shows an Up status.
status(2031) OR status(2044)
This changes the factory sensor to a Down status if at least one of the sensors with ID
2031 or ID 2044 is Down. Otherwise the factory sensor shows an Up status.
status(2031) AND NOT status(2044)
This changes the factory sensor to a Down status if the sensor with ID 2031 is Down, but
the sensor with ID 2044 is not in a Down status. Otherwise the factory sensor shows an Up
status.
Note: A status() function with NOT has to be connected with AND or OR if it is combined
with other status() functions:
status(sensorID) AND NOT status(sensorID)
status(sensorID) OR NOT status(sensorID)
( status(2031) AND status(2044) ) OR status(2051)
This changes the factory sensor to a Down status if both the sensor with ID 2031 and the
sensor with ID 2044 is Down, or if the sensor with ID 2051 is Down. Otherwise the factory
sensor shows an Up status.
Additionally, the following elements are allowed to perform calculations and comparisons with
the values that are returned by the status functions:
Basic operations: + (add), - (substract), * (multiply), / (divide)
Example: 3 + 5 * 2
Brackets: ( )
Example: 3 * (2 + 6)
Compare: = (equal), <> (not equal), > (greater), < (less), >= (greater or equal), <= (less or
equal)
If the comparison resolves to true, the value is 10,000; if false, the value is 0. For delta
sensors the speed is compared.
Internally, the status() function returns the downtime channel of the sensor in hundreds of
percent (10,000 = 100%).
true corresponds to a value of 10,000 which is a Down status.
false corresponds to a value of 0 which is an Up status.
1390
05.11.2015

If you understand this, you are able to use more complex formulas.
Example
( status(1031) + status(1032) + status(1033) + status(1034) ) >= 20000
This changes the factory sensor to a Down status if at least any two of the sensors with
IDs 1031, 1032, 1033, or 1034 are Down. Otherwise the factory sensor shows an Up status.
Note: You can also use the status() function in channel definitions 1382 . 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
87
mode, please note these additional facts:
If you add a Sensor Factory sensor underneath the Clust er Probe, and in the Sensor Factory
formula you refer to a channel of a sensor running on the Clust er Probe as well, the Sensor
Factory sensor shows the data of all cluster nodes for this sensor channel.
If you add a Sensor Factory sensor underneath the Local Probe, and in the Sensor Factory
formula you refer to a channel of a sensor running on the Clust er Probe, the Sensor Factory
sensor only shows data of the primary master node for this sensor channel.
More
Knowledge Base: 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 ProcessesTransformation of Technical Outages to the
Real Business Impact
https://www.paessler.com/blog/2014/06/26/all-about-prtg/monitoring-business-processes

To change display settings and limits, switch to the sensor's Overview tab and click the gear
icon of a specific channel. For detailed information, please see the Sensor Channels Set t ings
2711 .
05.11.2015
1391

Notifications
Others
1392
159
section.
05.11.2015

100 sFlow Sensor
6.8.100 sFlow Sensor

The sFlow sensor receives traffic data from a sFlow V5 compatible device and shows the traffic
by type. Only header traffic will be analyzed. Ensure the device matches the sFlow version V5!
There are several filter options available to divide traffic into different channels.
Chat (IRC, AIM)
Citrix
NetBIOS
Total traffic
sensor setup.
21.01.2016
1393

100 sFlow Sensor
sFlow Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sflow.png
Remarks
Note: You must enable sFlow V5 export on the monitored device for this sensor to work.
The device must send the flow data stream to the IP address of the PRTG probe system on
which the sensor is set up (either a local or remote probe).
The sensor accepts RAW data only. The stream must be sent via IPv4.
1394
21.01.2016

100 sFlow Sensor
There are several limitations
1395
for this sensor type.
Paessler Website: Paessler sFlow Tester

Sniffer sensors?
Limitations of This Sensor Type

There are some limitations that you want to consider before using this sensor type:
Only sFlow version 5 datagrams are supported
Only IPv4 flows are supported
Only the "raw packet header" format is supported
Only the "Flow sample" format is supported. "Extended flow" and "Counter" formats cannot be
processed
PRTG processes only samples where the source ID matches the ifIndex of the input interface
(avoiding double counted traffic) and ascending sequence numbers.
Sample packets have to be of ethernet type "IP" (with optional VLAN tag)
Sampled packets of type TCP and UDP are supported
We recommend using sFlow tester for debugging (see More section below).
Add Sensor
later.
Sensor Settings
21.01.2016
1395

100 sFlow Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SFLOW SPECIFIC SETTINGS

Receive sFlow Packets
on UDP Port
received. It must match the one you have configured in the sFlow
export options of your hardware router device. Default value is
6343. Please enter an integer value.
Note: When configuring export, ensure you select the appropriate
sFlow version 5.
Sender IP
sFlow from. Enter an IP address to receive data from a specific

on IP
Select the IP address(es) on which PRTG listens to sFlow packets.

in the sFlow export options of your hardware router device.
1396
21.01.2016

100 sFlow Sensor

sFlow version 5.

Channel Selection
UDP and TCP.
Ot her.
channel.
21.01.2016
1397

100 sFlow Sensor
FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
1398

21.01.2016

100 sFlow Sensor
PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
21.01.2016
1399

100 sFlow Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1400
21.01.2016

100 sFlow Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
1401

100 sFlow Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1402
21.01.2016

100 sFlow Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
1403

100 sFlow Sensor
Toplists
More
https://www.paessler.com/tools/sflowtester
Sniffer sensors?

Notifications
Others
159
section.
Related Topics
3087
1404
3092
21.01.2016

101 sFlow (Custom) Sensor
6.8.101 sFlow (Custom) Sensor

The sFlow (Custom) sensor receives traffic data from a sFlow V5 compatible device and shows
the traffic by type. Please make sure the device matches the sFlow version V5! There are
several filter options available to divide traffic into different channels.
sensor setup.
21.01.2016
1405


Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sflow.png
Remarks
Note: You must enable sFlow V5 export on the monitored device for this sensor to work.
The device must send the flow data stream to the IP address of the PRTG probe system on
which the sensor is set up (either a local or remote probe).
The sensor accepts RAW data.
1406
21.01.2016

There are several limitations
1407
for this sensor type.

Limitations of This Sensor Type

There are some limitations that you want to consider before using this sensor type:
Only sFlow version 5 datagrams are supported
Only IPv4 flows are supported
Only the "raw packet header" format is supported
Only the "Flow sample" format is supported. "Extended flow" and "Counter" formats cannot be
processed
PRTG processes only samples where the source ID matches the ifIndex of the input interface
(avoiding double counted traffic) and ascending sequence numbers.
Sample packets have to be of ethernet type "IP" (with optional VLAN tag)
Sampled packets of type TCP and UDP are supported
We recommend using sFlow tester for debugging (see More section below).

Add Sensor
later.
Sensor Settings
21.01.2016
1407


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

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.
Sender IP
1408
sFlow from. Enter an IP address to receive data from a specific
21.01.2016


on IP
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.
Channel Definition
Enter a channel definition to divide the traffic into different

Sensors 3092 section.
All traffic for which no channel is defined will be accounted to the
default channel named Ot her.
FILTER ING
Include Filter
section.
Exclude Filter
21.01.2016
1409

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1410
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
1411


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1412
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
1413

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1414
21.01.2016

Toplists
More
https://www.paessler.com/tools/sflowtester

Notifications
Others
159
section.
Related Topics
3087
21.01.2016
3092
1415

102 SFTP Secure File Transfer Protocol Sensor
6.8.102 SFTP Secure File Transfer Protocol Sensor

The sFTP Secure File Transfer Protocol sensor monitors FTP servers of a Linux/Unix system
using SSH File Transfer Protocol (FTP over SSH).
It tries to connect and shows the response time of the server.
SFTP Sec ure File Transfer Protoc ol Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sftp_sec ure_file_transfer_protoc ol.png
Remarks
For this sensor type you must define credentials for Linux/Solaris/Mac OS (SSH/WBEM)
systems on the device you want to use the sensor on.
Note: This sensor type cannot support all Linux/Unix and Mac OS distributions.
For a general introduction to SSH monitoring, please see manual section Monit oring via
SSH 3008 .
Add Sensor
later.
Sensor Settings
1416
09.11.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SSH SPECIFIC
Connection Timeout
(Sec.)

This timeout value determines the time the sensor waits to
establish a connection to the host. Keep this value as low as
possible.
Shell Timeout (Sec.)
09.11.2015
Define a timeout for the shell response. This is the time in seconds
the sensor waits for the shell to return a response after it has sent
its specific command (for example, cat /proc/loadavg).
1417

SSH SPECIFIC
SSH Port
Define which port this sensor uses for the SSH connection.
Choose between:
Inherit port number from parent device (default ): Use the
SSH port number as defined in the xx/Solaris/Mac OS (SSH/
WBEM) Systems section of the device on which you create this
sensor.
Ent er cust om port number: Do not use the port number from
the parent device settings but define a different port number
below.
Use Port Number
This field is only visible if you enable the custom port number
setting above. Enter the port number this sensor uses for the SSH
connection. Please enter an integer value.
Result Handling

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1418
09.11.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
09.11.2015
1419

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1420
09.11.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
09.11.2015
1421


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1422
09.11.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
09.11.2015
1423


Notifications
Others
1424
159
section.
09.11.2015

103 SIP Options Ping Sensor
6.8.103 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 "auth" and "options" 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 3095 file prt g.st andardlookups.sip.st at uscode

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sip_options_ping.png
Remarks
Requires
1426
Note: An SIP server might return a "480 Service temporarily unavailable" error until at least
one reachable SIP client is connected to the server.
21.01.2016
1425


this sensor.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
1426
21.01.2016


Priority
SIP SPECIFIC
Port

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 (Seconds)
Enter the timeout for the connection to the SIP server. Please
enter an integer value. The maximum value is 300.
Retry Count
If the connection to the SIP server fails, the sensor can re-try to
connect. Enter the maximum number of retries. After reaching the
maximum count, the sensor will show a red Down status 135 .
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
21.01.2016
1427

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1428
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
1429


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1430
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
1431

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1432
21.01.2016

More

Notifications
Others
21.01.2016
159
section.
1433

104 SMTP Sensor
6.8.104 SM TP Sensor
The SMTP sensor monitors a mail server using Simple Mail Transfer Protocol (SMTP) and can
optionally send a test email with every check.
SMTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/smtp.png
Remarks
Add Sensor
later.
Sensor Settings
1434
07.05.2015

104 SMTP Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SMTP SPECIFIC
Timeout (Sec.)

Port
Enter the number of the port that the sensor uses to send an email
via SMTP. For non-secure connections usually port 25 is used and
port 465 or 587 for SSL/TLS connections. The actual setting
depends on the server you connect to.
default value. If you do not get a connection, please try another
port number.
07.05.2015
1435

104 SMTP Sensor
AU THENTICATION
Type
Select whether to use an authentication method for the SMTP

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

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.

Sensor Specific

between:
status 135 .
SSL/TLS protocol.
1436
07.05.2015

104 SMTP Sensor

MONITOR ING
Send Email
Define if PRTG sends an email when connecting to the SMTP server.

Choose between:
None: Do not send an email, just connect to the SMTP server.
Send Email: Send an email through the SMTP server. If there is
an error when sending the email, an error message will be
triggered and the sensor will change to a Down status.
From
Specify which address the sent emails contain in the from field.
Please enter a valid email address.
To
Specify to which address PRTG sends the emails to. If you define
more than one recipient, separate the individual email addresses by
comma. Please enter a valid email address.
Topic
Specify which subject the sent emails contain. Please enter a string
Content
Specify which body the sent emails contain. Please enter a string
Sensor Result

between:
07.05.2015
1437

104 SMTP Sensor
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1438
07.05.2015

104 SMTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
07.05.2015
1439

104 SMTP Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1440
07.05.2015

104 SMTP Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
07.05.2015
1441

104 SMTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1442
159
section.
07.05.2015

105 SMTP&IMAP Round Trip Sensor
6.8.105 SM TP&IM AP Round Trip Sensor

The SMTP&IMAP Round Trip sensor monitors the time it takes for an email to reach an Internet
Message Access Protocol (IMAP) mailbox after being sent using Simple Mail Transfer Protocol
(SMTP). It sends an email to the parent device via SMTP and then scans a dedicated IMAP
mailbox until this email comes in. The SMTP&IMAP Round Trip sensor will delete these emails
automatically from the mailbox as soon as PRTG retrieves them. Emails will only remain in the
mailbox particularly if a timeout or a restart of the PRTG server occurred during sensor runtime.
The sensor shows the following:
Response time of SMTP server
Response time of IMAP server
Sum of both response times

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/smtp_imap_round_trip.png
Remarks
Note: Please use dedicated email accounts with this sensor type. If you use more sensors of
this type, please make sure that each sensor uses its own email accounts.
For a general introduction to the technology behind round trip monitoring, please see
Monit oring Email Round Trip 3022 section.
07.05.2015
1443

Add Sensor
later.
We recommend adding this sensor to an SMTP server device only, because the settings of this
sensor type are optimized for this scenario.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1444
07.05.2015

EMAIL SETTINGS
From
Specify which address the sent emails contain in the from field.
To
Specify to which address PRTG sends the emails. Please enter a

valid email address.
HELO Ident
Enter a server name for the HELO part of the mail protocol. For
some mail servers the HELO identifier must be the valid principal
07.05.2015
1445

STEP 1: SEND EMAIL TO PAR ENT DEVICE U SING SMTP

In this step, you configure how PRTG sends the emails. As SMTP server, the sensor uses the
IP-Address/DNS Name property's value of the device on which you add this sensor.
Port
via SMTP. Please enter an integer value. For non-secure
connections usually port 25 is used and port 465 or 587 for SSL/
TLS connections. The actual setting depends on the server you are
connecting to.
port number.
Timeout for SMTP

Connection (Sec.)

SMTP Authentication
Type
Define if you want to use an authentication for the SMTP

Username/Password: Authenticate at the SMTP server via
Username

Password

Additional Text for

Email Subject
The subject part of the round trip email is created automatically by

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-9B2A55630165D276}). Use this field to place your custom text before
the automatically created text.

Sensor Specific
1446

between:
07.05.2015


status 135 .
SSL/TLS protocol.
07.05.2015
1447

STEP 2: CHECK AN IMAP MAILBOX U NTIL EMAIL AR R IVES

In this step, you configure how the sent emails will be received.
IP-Address/DNS Name
Specify the IMAP server. Enter a valid IP address or DNS name.
Mailbox
Specify the IMAP Mailbox (resp. "IMAP folder") you want to check.
Enter the IMAP mailbox/folder name.
Port
Specify the port that the sensor uses for the IMAP connection. For
non-secure connections usually port 143 is used and port 993 for
SSL/TLS connections. The actual setting depends on the server
you connect to.
port number.
Connection Interval
(Sec.)
Enter the number of seconds the sensor will wait between two
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

(Sec.)
Enter the number of seconds an email may take to arrive in the

IMAP mailbox. PRTG will repeatedly check the mailbox in the
interval specified above until the email arrives. If it does not arrive
within the maximum trip time, the sensor will trigger an error
message. Please enter an integer value.
Username
Enter a username for IMAP authentication. Please enter a string.
Password
Enter a password for IMAP authentication. Please enter a string.
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.

Sensor Specific
1448

between:
07.05.2015


status 135 .
SSL/TLS protocol.
DEBU G OPTIONS
Sensor Result

between:
07.05.2015
1449

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1450
07.05.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
07.05.2015
1451


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1452
07.05.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
07.05.2015
1453

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1454
159
section.
07.05.2015

106 SMTP&POP3 Round Trip Sensor
6.8.106 SM TP&POP3 Round Trip Sensor

The SMTP&POP3 Round Trip sensor monitors the time it takes for an email to reach an Post
Office Protocol version 3 (POP3) mailbox after being sent using Simple Mail Transfer Protocol
(SMTP). It sends an email to the parent device via SMTP and then scans a dedicated POP3
mailbox until the email comes in. The SMTP&POP3 Round Trip sensor will delete these emails
automatically from the mailbox as soon as PRTG retrieves them. Emails will only remain in the
mailbox particularly if a timeout or a restart of the PRTG server occurred during sensor runtime.
Response time of SMTP server
Response time of POP3 server
Sum of both response times.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/smtp_pop3_round_trip.png
Remarks
Note: Please use dedicated email accounts with this sensor type. If you use more sensors of
this type, please make sure that each sensor uses its own email accounts.
For a general introduction to the technology behind round trip monitoring, please see
Monit oring Email Round Trip 3022 section.
04.11.2015
1455

Add Sensor
later.
We recommend adding this sensor on an SMTP server device only, as this sensor type's
settings are optimized for this scenario.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1456
04.11.2015

EMAIL SETTINGS
From
Specify which address the sent emails will contain in the from field.
To
Specify to which address PRTG sends the emails. Please enter a

valid email address.
HELO Ident
Enter a server name for the HELO part of the mail protocol. For
some mail servers the HELO identifier must be the valid principal
04.11.2015
1457

STEP 1: SEND EMAIL TO THE PAR ENT DEVICE U SING SMTP

In this step, you configure how PRTG sends the emails. As SMTP server, the sensor uses the
IP-Address/DNS Name property's value of the device on which you add this sensor.
Port
via SMTP. Please enter an integer value. For non-secure
connections usually port 25 is used and port 465 or 587 for SSL/
TLS connections. The actual setting depends on the server you
connect to.
port number.
Timeout for SMTP

Connection (Sec.)

SMTP Authentication
Type
Define if you want to use an authentication for the SMTP

Username/Password: Authenticate at the SMTP server via
Username

Password

Additional Text for

Email Subject
The subject part of the round trip email is created automatically by

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-9B2A55630165D276}). Use this field to place your custom text before
the automatically created text.

Sensor Specific
1458

between:
04.11.2015


status 135 .
SSL/TLS protocol.
04.11.2015
1459

STEP 2: CHECK A POP3 MAILBOX U NTIL EMAIL AR R IVES

In this step, you configure how the sent emails will be received.
IP-Address/DNS Name
Specify the POP3 server. Enter a valid IP address or DNS name.
Port
Specify the port that the sensor uses for the POP3 connection. For
non-secure connections usually port 110 is used and port 995 for
SSL/TLS connections. The actual setting depends on the server
you are connecting to.
port number.
Connection Interval
(Sec.)
Enter the number of seconds the sensor will wait between two
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

(Sec.)
Enter the number of seconds an email may take to arrive in the

IMAP mailbox. PRTG will repeatedly check the mailbox in the
interval specified above until the email arrives. If it does not arrive
within the maximum trip time, the sensor will trigger an error
message. Please enter an integer value.
POP3 Authentication
Type
Select the kind of authentication for the POP3 connection.

Choose between:
Wit hout Login: Monitor the connection to the POP3 server only.
Username and Password: Log on to the POP3 server with
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're connecting to.
Username
Password

Sensor Specific
1460
04.11.2015


between:
status 135 .
SSL/TLS protocol.
DEBU G OPTIONS
Sensor Result

between:
04.11.2015
1461

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1462
04.11.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
04.11.2015
1463


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1464
04.11.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
04.11.2015
1465

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
1466
159
section.
04.11.2015

107 SNMP APC Hardware Sensor
6.8.107 SNM P APC Hardware Sensor

The SNMP APC Hardware sensor monitors performance counters on an APC UPS device using
Simple Network Management Protocol (SNMP).
Actual voltage of battery
Capacity of battery
Temperature of battery
Remaining runtime of battery
Input and output frequency
Input and output voltage
Output load
sensor setup. For additional counters, please see section More 1474 .

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_apc _hardware.png
Remarks
Knowledge Base: How can I monitor additional counters with the SNMP APC Hardware
sensor?
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 3001 .
21.01.2016
1467

Add Sensor
later.
Select the performance counters you want to monitor. PRTG creates one sensor for each
counter you select in the Add Sensor dialog. The settings you choose in this dialog are valid
APC U PS SPECIFIC
Library OIDs
Select the performance counters you want to add a sensor for.

in the table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
1468
21.01.2016


Tags

default value.
Priority
APC U PS SPECIFIC
Selected Interface
Shows the name of the interface (performance counter) that this

sensor monitors. Once a sensor is created, you cannot change this
Unit String
Define the unit of the numerical data that the sensor monitors at
the given OID. Please enter a string.
Multiplication
If you want to multiply the received data with a certain value, enter
the quotient here. Please enter an integer value.
Division
If you want to divide the received data by a certain value, enter the
divisor here. Please enter an integer value.
If Value Changes
change.
21.01.2016
1469

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1470
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
1471


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1472
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
1473

ACCESS R IGHTS
User Group Access
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?

1474
21.01.2016

Notifications
Others
21.01.2016
159
section.
1475

108 SNMP Cisco ADSL Sensor
6.8.108 SNM P Cisco ADSL Sensor

The SNMP Cisco ADSL sensor monitors Asymmetric Digital Subscriber Line (ADSL) statistics of a
Cisco router using Simple Network Management Protocol (SNMP).
Speed of downlink
Speed of uplink
Remote and local attenuation
Remote and local SNR (signal-to-noise ratio)
Remote and local power output
sensor setup.
Remarks
Add Sensor
later.
For devices with multiple performance counters, multiple sensors are created at once in the
Add Sensor dialog. The settings you choose in this dialog are valid for all of the sensors that
are created.
CISCO ADSL SETTINGS

Line Index
1476

in the table head.
24.03.2015

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type
24.03.2015
1477

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
1478
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1479


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1480
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1481

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1482
24.03.2015

Others
24.03.2015
159
section.
1483

109 SNMP Cisco ASA VPN Connections Sensor
6.8.109 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
1484
15.04.2016

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_asa_v pn_c onnec tions.png
Remarks
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
15.04.2016
1485

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.

SNMP Version

between:
1486
15.04.2016


Community String

Authentication Type

Choose between:
device.
entirely.
User

Password

Encryption Type

algorithm.
15.04.2016
1487


device.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (Sec.)

1488
15.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.04.2016
1489


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1490
15.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.04.2016
1491

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1492
15.04.2016

Others
15.04.2016
159
section.
1493

110 SNMP Cisco ASA VPN Traffic Sensor
6.8.110 SNM P Cisco ASA VPN Traffic Sensor

The SNMP Cisco ASA VPN Traffic sensor monitors the traffic of an Internet Protocol Security
(IPsec) Virtual Private Network (VPN) connection on a Cisco Adaptive Security Appliance using
Incoming traffic
Outgoing traffic
SNMP Cisc o ASA VPN Traffic Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_asa_v pn_traffic .png
Remarks
This sensor type is indented to monitor permanent connections. It will show an error if a
connection is interrupted.
This sensor can monitor IPsec connections only!
Knowledge Base: I get the error PE123 when using the SNMP Cisco ASA VPN Traffic sensor.
What can I do?
1494
09.07.2015

Add Sensor
later.
Select the connections you want to monitor. PRTG creates one sensor for each connection
ASA VPN SPECIFIC

Connections
Select the IPsec VPN connections you want to add a sensor for.
in the table head.
Note: This sensor type can only monitor VPN connections based
on IPsec. This means, for example, that connections using "Cisco
AnyConnect" are not listed here.
Sensor Settings

Sensor Name
09.07.2015

171 .
1495


Parent Tags
Tags

default value.
Priority
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 for debugging. Wrong usage can result in
incorrect monitoring data!
Note: This sensor type can only monitor VPN connections based
on IPsec.
Sensor Behavior
Define the status of the sensor

available. Choose between:
135
if there is no active connection
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
1496
09.07.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.

SNMP Version

between:
09.07.2015
1497


Community String

Authentication Type

Choose between:
device.
entirely.
User

Password

Encryption Type

algorithm.
1498
09.07.2015


device.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (Sec.)

09.07.2015
1499

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1500
09.07.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
09.07.2015
1501


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1502
09.07.2015

ACCESS R IGHTS
User Group Access
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?

09.07.2015
1503

Notifications
Others
1504
159
section.
09.07.2015

111 SNMP Cisco ASA VPN Users Sensor
6.8.111 SNM P Cisco ASA VPN Users Sensor

The SNMP Cisco ASA VPN Users sensor monitors account connections to a Virtual Private
Network (VPN) on a Cisco Adaptive Security Appliance via Simple Network Management
Protocol (SNMP).
Number of currently connected accounts
If a specific user account is currently offline or online
SNMP Cisc o ASA VPN Users Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_asa_v pn_users.png
Remarks
28.04.2015
1505

Note: Please do not use the sensor to monitor more than 50 VPN users, especially if they are
all connected simultaneously. For more information, see the More 1513 section below.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1506
28.04.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.

SNMP Version

between:
28.04.2015
1507


Community String

Authentication Type

Choose between:
device.
entirely.
User

Password

Encryption Type

algorithm.
1508
28.04.2015


device.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (Sec.)

28.04.2015
1509

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1510
28.04.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
28.04.2015
1511


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1512
28.04.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: My Cisco ASA VPN Users sensor shows a user limit error. Why? What can I
do?

28.04.2015
1513

Notifications
Others
1514
159
section.
28.04.2015

112 SNMP Cisco CBQoS Sensor
6.8.112 SNM P Cisco CBQoS Sensor

The SNMP Cisco CBQoS sensor monitors network parameters using Cisco's Class Based Quality
of Service (CBQoS) via Simple Network Management Protocol (SNMP). It supports the classes
Class Map, Match Statement, and Queueing.
The sensor can show the following depending on the particular class type:
Current and maximum queue depth
Pre policy packets
Pre and post policy size
Drop packets and size
Drop packets without buffer
Fragment packets and size.
sensor setup.
SNMP Cisc o CBQoS Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_c bqos.png
24.03.2015
1515

Remarks
Add Sensor
later.
Select the CBQoS entries you want to monitor. To monitor Quality of Service (QoS) via
compatible devices, PRTG creates one sensor for each CBQoS entry you choose in the Add
Sensor dialog. The settings you choose in this dialog are valid for all of the sensors that are
created.
CLASS BASED QOS SPECIFIC

CBQoS Entries
table head.
Sensor Settings
1516
24.03.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
CLASS BASED QOS SPECIFIC

Object Type
Interface
Shows further information about the parameter that this sensor

Description
BitMask
ObjectID
ConfigID
24.03.2015
1517

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1518
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1519


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1520
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1521

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1522
24.03.2015

Others
24.03.2015
159
section.
1523

113 SNMP Cisco System Health Sensor
6.8.113 SNM P Cisco Sy stem Health Sensor

The SNMP Cisco System Health sensor monitors the system health of a Cisco device via Simple
Network Management Protocol (SNMP).
It can show the following depending on the available components of your device:
CPU load in percent
Available memory in absolute and percentage values
Status of power supplies
Current temperature and temperature status
sensor setup.
SNMP Cisc o Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_sy stem_health.png
Remarks
1524
11.03.2016

Add Sensor
later.
Select the components you want to monitor. To monitor the system health of a Cisco device,
PRTG creates one sensor for each measurement you choose in the Add Sensor dialog. The
settings you choose in this dialog are valid for all of the sensors that are created.
CISCO SYSTEM HEALTH SPECIFIC

Measurement
table head.
Sensor Settings
11.03.2016
1525


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
CISCO SYSTEM HEALTH SPECIFIC

Measurement
Shows the ID of the measurement that this sensor monitors. Once

the sensor anew.
DEBU G OPTIONS
Sensor Result

between:
1526
11.03.2016

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
11.03.2016
1527

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1528
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
1529


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1530
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
11.03.2016
1531

More

Notifications
Others
1532
159
section.
11.03.2016

114 SNMP Cisco UCS Blade Sensor
6.8.114 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_uc s_blade.png
Remarks
31.08.2015
1533

Add Sensor
later.
Select the blade servers you want to monitor. PRTG creates 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
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
1534
31.08.2015


Tags

default value.
Priority
SENSOR SETTINGS
Blade Server
Channel Mask
Shows information about the blade server that this sensor

Model
Serial Number
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
31.08.2015
1535

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1536
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
1537


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1538
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
1539

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1540
31.08.2015


Notifications
Others
31.08.2015
159
section.
1541

115 SNMP Cisco UCS Chassis Sensor
6.8.115 SNM P Cisco UCS Chassis Sensor

The SNMP Cisco UCS Chassis sensor monitors the health status of the chassis of a Cisco
Unified Computing System (UCS) device via Simple Network Management Protocol (SNMP).
It can show the states of the following properties:
Configuration
License
Oper
Operability
Power
Thermal
Serial electronic erasable programmable read-only memory (SEEPROM)
sensor setup.
SNMP Cisc o UCS Chassis Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_uc s_c hassis.png
1542
24.03.2015

Remarks
Add Sensor
later.
Select the chassis you want to monitor. PRTG creates one sensor for each chassis you choose
in the Add Sensor dialog. The settings you choose in this dialog are valid for all of the sensors
that are created.
SENSOR SETTINGS
Chassis
Select the chassis you want to add a sensor for. You see a list with
head.
Sensor Settings
24.03.2015
1543


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
Chassis
Shows the chassis that this sensor monitors. Once a sensor is

anew.
SENSOR DISPLAY
Primary Channel

Graph Type
1544
24.03.2015

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1545

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1546
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1547


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1548
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
1549

More

Notifications
Others
1550
159
section.
24.03.2015

116 SNMP Cisco UCS Physical Disk Sensor
6.8.116 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_uc s_phy sic al_disk.png
Remarks
18.03.2016
1551

Add Sensor
later.
In order to monitor physical disks in a UCS device, PRTG will create one sensor for each disk
you choose. The settings you choose in this dialog are valid for all of the sensors that are
created.
U CS PHYSICAL DISK
Disks
head.
Note: Only working disks (with the current status Up or Warning)
will be shown here.
Sensor Settings

Sensor Name
1552

171 .
18.03.2016


Parent Tags
Tags

default value.
Priority
U CS PHYSICAL DISK
Disk
Shows the disk which this sensor monitors. Once a sensor is

anew.
Display Name
Shows the display name of the physical disk which this sensor
SENSOR DISPLAY
Primary Channel

Graph Type
18.03.2016
1553

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
1554
18.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
18.03.2016
1555


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1556
18.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
18.03.2016
1557

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1558
18.03.2016

More

Notifications
Others
18.03.2016
159
section.
1559

117 SNMP Cisco UCS System Health Sensor
6.8.117 SNM P Cisco UCS Sy stem Health Sensor

The SNMP Cisco UCS System Health sensor monitors the system health of a Cisco Unified
Computing System (UCS) device via Simple Network Management Protocol (SNMP).
Number of operable resp. inoperable fans
Status of fan performance, fan thermal, and fan voltage
If a fan failure is predicted
Number of operable resp. inoperable fan modules
Status of fan module performance, fan module thermal, and fan module voltage
If a fan module failure is predicted
Number of operable resp. inoperable power supplies
Status of power supply performance, power supply thermal, and power supply voltage
If a power supply failure is predicted
Number of minor, major, and critical faults (which are not acknowledged yet in the UCS logs)
Number of warnings (which are not acknowledged yet in the UCS logs)
sensor setup.
1560
24.03.2015

SNMP Cisc o UCS Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c isc o_uc s_sy stem_health.png
Remarks
24.03.2015
1561

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1562
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1563

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1564
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1565


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1566
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
1567

More

Notifications
Others
1568
159
section.
24.03.2015

118 SNMP CPU Load Sensor
6.8.118 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.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c pu_load.png
Remarks
Note: 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 244 with the IP address that it has in your network
and create the SNMP sensor on this device instead.
31.08.2015
1569

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1570
31.08.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
31.08.2015
1571

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1572
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
1573


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1574
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
31.08.2015
1575

More

Notifications
Others
1576
159
section.
31.08.2015

119 SNMP Custom Sensor
6.8.119 SNM P Custom Sensor

The SNMP Custom sensor monitors a numerical value returned by a specific Object Identifier
(OID) using Simple Network Management Protocol (SNMP).
It shows the numerical value at a given OID of an SNMP device.
SNMP Custom Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c ustom.png
Remarks
Knowledge Base: How do I find out what OID I need to use for a custom sensor?
Add Sensor
later.
21.01.2016
1577

OID VALU ES
Channel Name
results at the given OID. Please enter a string. You can change this
value later in the respective channel settings 2711 of this sensor.
Value Type
Select the expected numeric type of the results at the given OID.
Choose between:
Gauge (unsigned Int eger): For integer values, such as 10 or
120.
Gauge (signed int eger): For integer values, such as -12 or 120.
Gauge (float ): For float values, such as -5.80 or 8.23.
Delt a (Count er): For counter values. PRTG will calculate the
difference between the last and the current value.
Sensor Settings

Sensor Name

171 .
Parent Tags
1578
21.01.2016


Tags

default value.
Priority
OID VALU ES
OID Value
Enter the OID of the SNMP object you want to receive numerical
data from.
Note: Most OIDs begin with 1.3.6.1. However, entering OIDs
starting with 1.0, or 1.1, or 1.2 is also allowed. If you want to
disable the validation of your entry entirely, add the string
norfccheck: to the beginning of your OID, for example,
norfccheck:2.0.0.0.1.
Unit String
Define the unit of the numerical data that this sensor receives from
Value Type
Shows the value type of the numerical data that this sensor
receives from the given OID. Once a sensor is created, you cannot
Multiplication
the multiplier here. Please enter an integer value. Otherwise, use
the default value 1 to not change the received value.
Division
divisor here. Please enter an integer value. Otherwise, use the
default value 1 to not change the received value.
If Value Changes
21.01.2016
1579

OID VALU ES
change.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1580
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
1581


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1582
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
1583

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1584
21.01.2016

Others
21.01.2016
159
section.
1585

120 SNMP Custom Advanced Sensor
6.8.120 SNM P Custom Advanced Sensor

The SNMP Custom Advanced sensor monitors numerical values returned by one or more
specific Object Identifiers (OIDs) using Simple Network Management Protocol (SNMP).
It can show numerical values at given OIDs on an SNMP device in up to 10 different channels.
sensor setup.
SNMP Custom Adv anc ed Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c ustom_adv anc ed.png
Remarks
1586
21.01.2016

Add Sensor
later.
OID VALU ES
Value Type
Select the expected numeric type of the results at the given OID.
Choose between:
120.
Sensor Channel #2
#10

Enable: The sensor will create this channel. Specify name, OID,
value type, and unit for this channel below.
sensor channels after creation of this sensor!
Sensor Settings
21.01.2016
1587


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
OID VALU ES
Sensor Channel #x
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.
disable the validation of your entry during your typing entirely, add
the string norfccheck: to the beginning of your OID, for example,
1588
21.01.2016

OID VALU ES
Sensor Channel #x
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
Sensor Channel #x
Unit
Define the unit of the numerical data that this sensor receives from
the given OID. Choose between:
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
Value Lookup
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Channel #x
Value Lookup
above. Choose a lookup 3095 file that you want to use with this
channel.
21.01.2016
1589

OID VALU ES
Sensor Channel #y
This field shows the option you chose for this channel in the Add
Sensor 1587 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
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1590
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
1591


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1592
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
1593

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1594
21.01.2016

Others
21.01.2016
159
section.
1595

121 SNMP Custom String Sensor
6.8.121 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
use limits for the sensor channel value, you can also extract a numeric value contained in the
string.
Response time of the monitored device
Optionally a value extracted from the string
In the sensor message, the sensor shows the string you search
reason for a current Warning or Down status.
1598
for and which is the

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c ustom_string.png
Remarks
Example: Number Extraction with Regular Expression
1605
1596
11.03.2016

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
OID VALU ES
11.03.2016
1597

OID Value
Enter the OID of the SNMP object you want to receive a string
from.
norfccheck: at the beginning of your OID, for example,
Maximum Length of
String
Define the maximum allowed length of the string to be received

from the SNMP object at the given OID. If the string is longer than
this value, the sensor shows a Down status 135 . Please enter an
integer value or leave the field empty.
If Value Changes
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 3105 . If the data does not include the
search pattern, the sensor shows a Down status 135 . Please enter a
string or leave the field empty.
For Keyword Search
Use

the field above.
Plain Text : Search for the string as plain text. The characters *
known from Windows search). This behavior cannot be disabled,
so the literal search for these characters is not possible with
plain text search.
Regular Expression: Treat the search pattern as a Regular
Expression 3105 .
1598
11.03.2016

Response Must Not

Include (Error State)
Define which string must not be part of the data that is received
form the SNMP object at the given OID. You can either enter plain
text or a Regular Expression 3105 . If the data does include the
search pattern, the sensor shows a Down status 135 . Please enter a
string or leave the field empty.
For Keyword Search

Use

the field above.
plain text search.
Expression 3105 .
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 3105 . If the data does not include the
search pattern, the sensor shows a Warning status 135 . Please
For Keyword Search
Use

the field above.
plain text search.
Expression 3105 .
Response Must Not

Include (Warning State)
form the SNMP object at the given OID. You can either enter plain
text or a Regular Expression 3105 . If the data does include the
search pattern, the sensor shows a Warning status 135 . Please
For Keyword Search

Use

the field above.
plain text search.
11.03.2016
1599


Expression 3105 .
EXTENDED
PR OCESSING
Interpret Result as
Define the type of the received string. Choose between:

St ring (default ): Handle the result as common string.
Hexadecimal by t es (as in MAC addresses): Handle the result
as hexadecimal bytes. For example, choose this option when
monitoring MAC addresses.
Decimal by t es (as in IP addresses): Handle the result as
decimal bytes. For example, choose this option when monitoring
IP addresses.
Extract Number Using

Regular Expression
Define if you want to filter out a numeric value from the string
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 2711 ).
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
1605 below.
Regular Expression
This setting is only visible if you enable number extraction above.

Enter a Regular Expression 3105 to identify the numeric value you
want to extract from the string returned by the SNMP object at the
given OID. You can use capturing groups here. Make sure the
expression returns numbers only (including decimal and thousands
separators). The result will be further refined by the settings
below.
Index of Capturing
Group
This setting is only visible if you enable number extraction above. If

your regular expression uses capturing groups, please specify
which one will be used to capture the number. Please enter an
Decimal Separator

Define which character is used as decimal separator for the
number extracted above. Please enter a string or leave the field
empty.
1600
11.03.2016

Thousands Separator

Define which character is used as thousands separator for the
empty.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
11.03.2016
1601

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1602
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
1603


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1604
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

If you want to extract a number in the response string using a regular expression, please note
that the index for captures in this sensor is based on 1 (not on 0). Furthermore, capturing
groups are not created automatically. The example below will illustrate this issue.
Consider the following string as returned by a request for CPU usage:
5 Sec (3.49%), 1 Min (3.555%), 5 Min (3.90%)
Assuming you would like to filter for the number 3.555, i.e., the percentage in the second
parentheses. Then enter the following regex in the Regular Expression field:
(\d+\.\d+).*?(\d+\.\d+).*?(\d+\.\d+)
As Index of Capt uring Group enter 3. This will extract the desired number 3.555.
11.03.2016
1605

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.
Note: It is not possible to match an empty string using PRTG's regex search with sensors.
More

Notifications
Others
1606
159
section.
11.03.2016

122 SNMP Custom String Lookup Sensor
6.8.122 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 135 by using a defined lookup file 3095 . 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 3103 SingleInt ). See section Example 1614 below.
This sensor shows a retrieved string value with a defined status.
SNMP Custom Lookup Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c ustom_lookup.png
Remarks
See manual section SNMP Cust om St ring Lookup SensorExample
definition for this sensor type.
1614
for a sample lookup
16.03.2016
1607

Add Sensor
later.
OID VALU ES
Channel Name
results at the given OID. Please enter a string. You can change this
value later in the respective channel settings 2711 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

Sensor Name

171 .
Parent Tags
1608
16.03.2016


Tags

default value.
Priority
OID VALU ES
OID Value
Enter the OID of the SNMP object you want to receive a string
from.
norfccheck: at the beginning of your OID, for example,
Lookup
Shows the lookup file that this sensor uses. Once a sensor is
anew.
If Value Changes
change.
16.03.2016
1609

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1610
16.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
16.03.2016
1611


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1612
16.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
16.03.2016
1613

ACCESS R IGHTS
User Group Access
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 3095 for this sensor that contains all these possible string values as
text, each text value in one lookup entry:
1614
16.03.2016

<?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>
<SingleInt state="Error" value="2">
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 shows a Down status 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 is Up in this case. The integer 0 is converted back to the string
Good which is shown as channel value.
Note: The string match is not case sensitive.
Note: Please use the lookup type SingleInt for this sensor. BitFields and ranges are not
supported!
Note: If you imported an SNMP library 1848 (this is an oidlib file) that contains lookups 3095 (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 which an oidlib might contain with your
own status definitions. See section Define LookupsCust omizing Lookups 3101 for details
about this mechanism.
More
16.03.2016
1615


Notifications
Others
1616
159
section.
16.03.2016

123 SNMP Custom Table Sensor
6.8.123 SNM P Custom Table Sensor

The SNMP Custom Table Sensor monitors entries from a table which 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.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_c ustom_table.png
Remarks
Knowledge Base: What can I monitor with the SNMP Custom Tale Sensor?
16.03.2016
1617

Add Sensor
later.
PRTG creates one SNMP Table sensor for each table row that you select in the Add Sensor
dialog. The settings you choose in this dialog are valid for all of the sensors that are created.
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.
Note: 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 which is part of a different SNMP
table, for example, [1.3.6.1.2.1.2.2.1.2], to query information which
is not contained in the current table. The same index as in the
original table will be added to the OID.
1618
16.03.2016

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 which
are available to monitor. Select the desired items by adding check
the check box in the table head. PRTG shows you the table that
the OID you entered before returns.
Identification Column
Define the identification column for the SNMP Table sensor(s) you
want to create. The sensor uses this column to identify the correct
table row for each object that you want to monitor. The value of
the column that you choose as the identification column will
appear in the sensor's name, so you can identify and distinguish all
sensors that are created from the same SNMP table.
Note: One new sensor is created for each table row you choose.
Sensor Channel #2
#10

Enable: Create an additional channel and define all its
characteristics below, its name, column, value type, and unit.
sensor channels after the creation of this sensor!
Note: 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:
120.
16.03.2016
1619

TABLE SPECIFIC
Please see below 1621 for the other channel settings that can be
changed also after the sensor has been created.
Note: This sensor monitors numerical values only. Make sure that
you do not select columns that return strings because they lead to
a Down status 135 . 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

Sensor Name

171 .
Parent Tags
Tags

default value.
1620
16.03.2016


Priority
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's creation. It is also
displayed in the sensor's name to distiguish it from other sensors
you created from the same table, i.e. from 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
Sensor Channel #x
Name
desired result. Please enter a string.
Sensor Channel #x
Column
Select the table column that together with the table row points to
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
Value Type
Shows the value type of the data that this sensor receives in this
Sensor Channel #x
Unit
Define the unit of the data that this sensor receives in this channel.
Choose between:
By t esBandwidt h
By t esMemory
16.03.2016
1621

TABLE SPECIFIC
By t esDisk
Temperat ure
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
By t esFile
SpeedDisk
SpeedNet
Cust om
Value Lookup
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Channel #x
Value Lookup
channel.
Sensor Channel #x+1
Shows if you enabled or disabled a channel.

Note: Once a sensor is created, you cannot change this value. It is
You can define up to 10 different sensor channels per sensor.
1622
16.03.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
16.03.2016
1623

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1624
16.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
16.03.2016
1625


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1626
16.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: What can I monitor with the SNMP Custom Table Sensor?

16.03.2016
1627

Notifications
Others
1628
159
section.
16.03.2016

124 SNMP Dell EqualLogic Logical Disk Sensor
6.8.124 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)
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/SNMP_DELL_EqualLogic _Logic al_Disk.png
28.04.2016
1629

Remarks
Add Sensor
later.
Select the volume(s) from the storage system that you want to monitor. PRTG creates one
sensor for each volume you choose in the Add Sensor dialog. The settings you choose in this
DELL EQU ALLOGIC SPECIFIC

Volume
Select the volume(s) you want to add a sensor for. You see a list
head.
Sensor Settings
1630
28.04.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

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.
28.04.2016
1631

Volume Description
Shows the description of the volume that this sensor monitors.

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1632
28.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
28.04.2016
1633


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1634
28.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
28.04.2016
1635

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1636
28.04.2016

More

Notifications
Others
28.04.2016
159
section.
1637

125 SNMP Dell EqualLogic Member Health Sensor
6.8.125 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
1638
09.05.2016


SNMP_DELL_EqualLogic _Member_Health_Sensor.png
Remarks
This sensor type works with SNMP v2c and SNMP v3. It does not support SNMP v1. Please
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 89 .
09.05.2016
1639

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
table head.
Sensor Settings
1640
09.05.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

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.
09.05.2016
1641

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1642
09.05.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
09.05.2016
1643


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1644
09.05.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
09.05.2016
1645

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1646
09.05.2016

More

Notifications
Others
09.05.2016
159
section.
1647

126 SNMP Dell EqualLogic Physical Disk Sensor
6.8.126 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
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/SNMP_DELL_EqualLogic _Phy sic al_Disk.png
Remarks
1648
28.04.2016

Add Sensor
later.
Select the array member(s) of the Dell EqualLogic storage system you want to monitor. PRTG
creates one sensor for each disk you choose in the Add Sensor dialog. The settings you
choose in this dialog are valid for all of the sensors that are created.

Disk
Select the disk(s) you want to add a sensor for. You see a list with
head.
Sensor Settings

Sensor Name
28.04.2016

171 .
1649


Parent Tags
Tags

default value.
Priority

Disk

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.
1650
28.04.2016

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,
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
28.04.2016
1651

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1652
28.04.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
28.04.2016
1653


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1654
28.04.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
28.04.2016
1655

More

Notifications
Others
1656
159
section.
28.04.2016

127 SNMP Dell Hardware Sensor
6.8.127 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.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_dell_hardware.png
Remarks
Requires
device.
1658
the Dell OpenManage Server Administrator to be installed on the monitored Dell
Knowledge Base: What do I need to monitor Dell servers?

15.04.2016
1657

Requirement: Dell OpenManage Server Administrator

This sensor needs the Dell OpenManage Server Administrator tool to be installed on the Dell
hardware device to monitor it. Please make sure that you enable SNMP in the OpenManage
Server Administrator. For details, please see section More 1664 below.
Add Sensor
later.
Select the Dell performance counter you want to monitor. PRTG creates one sensor for each
OID you choose in the Add Sensor dialog. The settings you choose in this dialog are valid for
all of the sensors that are created.
DELL HAR DWAR E SPECIFIC

Library OIDs

in the table head.
Note: 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
1658
15.04.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

Selected Interface
Shows the name of the interface (performance counter) that this

Unit String
Define the unit of the numerical data that the sensor receives at
Multiplication
the multiplier here. Please enter an integer value.
Division
divisor here. Please enter an integer value.
If Value Changes
change.
15.04.2016
1659


SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1660
15.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.04.2016
1661


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1662
15.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.04.2016
1663

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

1664
15.04.2016

Notifications
Others
15.04.2016
159
section.
1665

128 SNMP Dell PowerEdge Physical Disk Sensor
6.8.128 SNM P Dell PowerEdge Phy sical Disk Sensor

The SNMP Dell PowerEdge Physical Disk sensor monitors a physical disk in a Dell PowerEdge
server using Simple Network Management Protocol (SNMP).
Disk status
Roll up status
Component status
If there is currently a warning regarding the Self-Monitoring, Analysis and Reporting
Technology (S.M.A.R.T.) status
SNMP Dell PowerEdge Phy sic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_dell_poweredge_phy sic al_disk.png
Remarks
Requires 1677 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: My Dell PowerEdge sensor fails to validate disks and I can't add it. What can
I do?
1666
15.04.2016

Requirement: Dell OpenManage Server Administrator or iDRAC 7

PowerEdge server to monitor it. Please make sure that you enable SNMP in the OpenManage
Server Administrator. For details, please see section More below. Note: You can also monitor
Dell PowerEdge servers with this sensor type via Integrated Dell Remote Access Controller
(iDRAC) 7.
Add Sensor
later.
Select the disks you want to monitor. PRTG creates one sensor for each disk you select in
that are created.
DELL POWER EDGE PHYSICAL DISK SETTINGS

Disk
head.
Sensor Settings
15.04.2016
1667


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
DELL POWER EDGE PHYSICAL DISK SETTINGS

Disk
Shows the name of the disk that this sensor is monitoring. Once a
the sensor anew.
Data Source
Shows the interface which is used to get monitoring data. This is

either Dell OpenManage Server Administrator (OMSA) or Integrated
Dell Remote Access Controller (iDRAC).
1668
15.04.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
15.04.2016
1669

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1670
15.04.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
15.04.2016
1671


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1672
15.04.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
15.04.2016
1673

More
Knowledge Base: My Dell PowerEdge sensor fails to validate disks and I can't add it. What can I
do?

Notifications
Others
1674
159
section.
15.04.2016

129 SNMP Dell PowerEdge System Health Sensor
6.8.129 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.
25.01.2016
1675

SNMP Dell PowerEdge Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_dell_poweredge_sy stem_health.png
Remarks
Requires 1677 iDRAC 7 or the Dell OpenManage Server Administrator to be installed on the
monitored server.
1676
25.01.2016

Requirement: Dell OpenManage Server Administrator or iDRAC 7

PowerEdge server to monitor it. Please make sure that you enable SNMP in the OpenManage
Server Administrator. For details, please see section More below. Note: You can also monitor
Dell PowerEdge servers with this sensor type via Integrated Dell Remote Access Controller
(iDRAC) 7.
Add Sensor
later.
Select the Dell PowerEdge chassis you want to monitor. PRTG creates one sensor for each
chassis you choose in the Add Sensor dialog. The settings you choose in this dialog are valid
DELL POWER EDGE SYSTEM HEALTH SPECIFIC

Chassis
Select the chassis you want to add a sensor for. You see a list with
head.
Sensor Settings
25.01.2016
1677


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
DELL POWER EDGE SYSTEM HEALTH SPECIFIC

Chassis
Shows the chassis that this sensor monitors. Once a sensor is

anew.
Channel Mask
Shows the channel mask that describes which sensors are

available. Once a sensor is created, you cannot change this value.
Data Source
Shows the interface which is used to get monitoring data. This is

either Dell OpenManage Server Administrator (OMSA) or Integrated
Dell Remote Access Controller (iDRAC).
1678
25.01.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
25.01.2016
1679

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1680
25.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
25.01.2016
1681


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1682
25.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
25.01.2016
1683

More

Notifications
Others
1684
159
section.
25.01.2016

130 SNMP Disk Free Sensor
6.8.130 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_disk_free.png
Remarks
This sensor uses more generic Object Identifier (OID) values compared to the SNMP Linux
Disk Free Sensor 1857 .
31.08.2015
1685

Add Sensor
later.
Select the disk(s) you want to monitor. PRTG creates one sensor for each disk you choose in
that are created.
DISK FR EE SETTINGS
Disk
Select one or more disks you want to add a sensor for. You see a
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
1686
31.08.2015


Tags

default value.
Priority
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 for debugging. Wrong usage can result in
incorrect monitoring data!
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
31.08.2015
1687

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1688
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
1689


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1690
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
1691

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1692
31.08.2015

More

Notifications
Others
31.08.2015
159
section.
1693

131 SNMP Hardware Status Sensor
6.8.131 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hardware_status.png
Remarks
1694
31.08.2015

Add Sensor
later.
Select the hardware components you want to monitor. PRTG creates one sensor for each
component you choose in the Add Sensor dialog. The settings you choose in this dialog are
HAR DWAR E SPECIFIC

Hardware Component
Select the hardware components you want to add a sensor for.

in the table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
31.08.2015
1695


Tags

default value.
Priority
HAR DWAR E SPECIFIC

Hardware Component
Product ID
Description
Shows further information about the hardware component. Once a

the sensor anew.
Type
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1696
31.08.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
31.08.2015
1697

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1698
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
1699


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1700
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
31.08.2015
1701

Others
1702
159
section.
31.08.2015

132 SNMP HP BladeSystem Blade Sensor
6.8.132 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hp_bladesy stem_serv er_blade.png
Remarks
Note: 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 creates one sensor for each blade you
21.01.2016
1703

HP BLADESYSTEM SPECIFIC
Server Blade
Select the blades you want to add a sensor for. You see a list with
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
1704
21.01.2016


Priority
HP BLADESYSTEM SPECIFIC
Server Blade
Shows the server blade that this sensor monitors. Once a sensor
anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
21.01.2016

1705

Inherited Settings
described below.
1706
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
1707


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1708
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
1709

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1710
21.01.2016


Notifications
Others
21.01.2016
159
section.
1711

133 SNMP HP BladeSystem Enclosure System Health Sensor
6.8.133 SNM P HP BladeSy stem Enclosure Sy stem Health Sensor

The SNMP HP BladeSystem Enclosure System Health sensors 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/hp_bladesy stem_sy stem_health.png
Remarks
Note: 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
1712
21.01.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
21.01.2016
1713

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1714
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
1715


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1716
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
1717

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1718
21.01.2016


Notifications
Others
21.01.2016
159
section.
1719

134 SNMP HP LaserJet Hardware Sensor
6.8.134 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_laserjet_hardware.png
Remarks
Add Sensor
later.
1720
24.03.2015

Select the categories you want to monitor. PRTG creates one sensor for each category you

Library OIDs
Select the categories you want to add a sensor for. You see a list
head.
The following performance counters for your printer are available:
Toner/St at us
Paper/St at us
Jam/St at us
Sensor Settings

Sensor Name

171 .
Parent Tags
24.03.2015
1721


Tags

default value.
Priority
HP LASER JET SPECIFIC

Selected Interface
Shows the name of the category (performance counter) that this

If Value Changes
change.
SENSOR DISPLAY
Primary Channel
1722

24.03.2015

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1723

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1724
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1725


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1726
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
1727

Others
1728
159
section.
24.03.2015

135 SNMP HP ProLiant Logical Disk Sensor
6.8.135 SNM P HP ProLiant Logical Disk Sensor

The SNMP HP ProLiant Logical Disk sensor monitors a logical disk in an HP server via Simple
Disk status
Completion in percent: This is only important when the disk status is "Reconstructing" or
"Expanding" and illustrates the progress of this task.
SNMP HP ProLiant Logic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_proliant_logic al_disk.png
Remarks
Requires 1730 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
1730 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.
24.03.2015
1729

Requirement: HP System Management Tools

This sensor needs a specific HP system management tool to be installed on the target device,
so it reports data via SNMP: HP Insight Management Agents for Windows Server 2003/2008. To
receive SNMP data from RAID controllers, you additionally need HP Insight Management WBEM
Providers. For more details and download links please refer to the subsection More below.
Note: Some of the HP Object Identifiers (OIDs) which this sensor type uses are only accessible
via the HP Integrated Lights-Out (iLO) interface. If this sensor throws an error that it cannot
find "such device types", please create a device in PRTG which points to the address of the HP
iLO interface (if available) and add the sensor to this device. We recommend using the
Agentless Management feature with configured SNMP. You can set this up in the iLO
configuration interface under Administ rat ion | Management | SNMP Set t ings.
Add Sensor
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

Disk
head.
Sensor Settings
1730
24.03.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
HP PR OLIANT LOGICAL DISK SETTINGS

Disk
Shows the name of the disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
Primary Channel
24.03.2015

1731

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1732
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1733


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1734
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1735

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1736
24.03.2015

More
Knowledge Base: Monitor HP ProLiant via SNMP

Notifications
Others
24.03.2015
159
section.
1737

136 SNMP HP ProLiant Memory Controller Sensor
6.8.136 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.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_proliant_memory _c ontroller.png
1738
19.10.2015

Remarks
Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory
Controller Sensor?
Note: If modules are inserted at a later point, you have to add this sensor anew.

Add Sensor
later.
Select the memory controllers in the HP server you want to monitor. PRTG creates one sensor
for each controller you choose in the Add Sensor dialog. The settings you choose in this
19.10.2015
1739

HP PR OLIANT MEMOR Y CONTR OLLER SETTINGS

Controller
Select the controllers you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1740
19.10.2015

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
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.10.2015
1741

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1742
19.10.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
19.10.2015
1743


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1744
19.10.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.10.2015
1745

More
Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory
Controller Sensor?

Notifications
Others
1746
159
section.
19.10.2015

137 SNMP HP ProLiant Network Interface Sensor
6.8.137 SNM P HP ProLiant Network Interface Sensor

The SNMP HP ProLiant Network Interface sensor monitors a network interface in an HP server
Traffic in
Traffic out
Number of transmitted and received good frames
Number of transmitted and received bad frames
Alignment errors
FCS (Frame Check Sequence) errors
Late and excessive collisions
Carrier sense errors
If frames are too long
Remarks
Note: When adding the sensor, the status of each available network interface is shown. If
this status is Link Failure, it is still possible to add a sensor for the respective interface.
Though, most likely the sensor for this interface will not work correctly. The error message
in this case will be "No Such Name (SNMP error # 2)".

18.03.2016
1747

Add Sensor
later.
Select the network interfaces in the HP server you want to monitor. PRTG creates one sensor
for each interface you choose in the Add Sensor dialog. The settings you choose in this
HP PR OLIANT NETWOR K INTER FACE SETTINGS

Network Interface
Select the interfaces you want to add a sensor for. You see a list
head.
Note: If this status is Link Failure, it is still possible to add a sensor
for the respective interface. Though, most likely the sensor for this
interface will not work correctly. The error message in this case
will be "No Such Name (SNMP error # 2)".
Sensor Settings
1748
18.03.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
HP PR OLIANT NETWOR K INTER FACE SETTINGS

Network Interface
Shows the name of the interface that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
Primary Channel

displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor.
Note: You can set another primary channel later by clicking on the
pin symbol of a channel in the sensor's overview tab.
Chart Type
18.03.2016
Define how to show different channels for this sensor.
1749

SENSOR DISPLAY
for each channel.
of your total traffic.
Note: You cannot use this option in combination with manual
Vertical Axis Scaling (available in the Sensor Channels Set t ings
2711 ). 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.
Note: 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 2711 ).
Stack Unit
This setting is only available if you choose stacked graphs above.

Inherited Settings
described below.
1750
18.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
18.03.2016
1751


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1752
18.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
18.03.2016
1753

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1754
18.03.2016

More

Notifications
Others
18.03.2016
159
section.
1755

138 SNMP HP ProLiant Physical Disk Sensor
6.8.138 SNM P HP ProLiant Phy sical Disk Sensor

The SNMP HP ProLiant Physical Disk sensor monitors a physical disk in an HP server via Simple
Read and written sectors
Hard and corrected read errors
Hard and corrected write errors
Disk status
Drive condition
Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status
If the threshold is passed
SNMP HP ProLiant Phy sic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_proliant_phy sic al_disk.png
1756
30.04.2015

Remarks

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 in this dialog are
30.04.2015
1757

HP PR OLIANT PHYSICAL DISK SETTINGS

Disk
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1758
30.04.2015

HP PR OLIANT PHYSICAL DISK SETTINGS

Disk
Shows the identifier of the disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
30.04.2015
1759

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1760
30.04.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
30.04.2015
1761


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1762
30.04.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
30.04.2015
1763

More

Notifications
Others
1764
159
section.
30.04.2015

139 SNMP HP ProLiant System Health Sensor
6.8.139 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.
30.04.2015
1765

SNMP HP ProLiant Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_hp_proliant_sy stem_health.png
Remarks
This sensor has predefined limits for temperatures and broken frames. You can change these
limits individually in the channel settings 2711 .
1766
30.04.2015

Note: RAID controllers which have no hard disks assigned might cause a Down status 135 . In
this case, deactivate the respective controller(s) in the HP ProLiant BIOS to avoid sensor
errors.

Add Sensor
later.
Sensor Settings
30.04.2015
1767


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1768
30.04.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
30.04.2015
1769

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1770
30.04.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
30.04.2015
1771


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1772
30.04.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
30.04.2015
1773

More
Knowledge Base: Why is my SNMP HP ProLiant System Health sensor in error status after
updating PRTG?

Notifications
Others
1774
159
section.
30.04.2015

140 SNMP IBM System X Logical Disk Sensor
6.8.140 SNM P IBM Sy stem X Logical Disk Sensor

The SNMP IBM System X Logical Disk sensor monitors a logical disk in an IBM server via Simple
It shows the status of a logical disk in an IBM server.
SNMP IBM Sy stem X Logic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_ibm_sy stemx_logic al_disk.png
Remarks
Requires
1775
the IBM Systems Director Platform to be installed on the target device.
Knowledge Base: What are the requirements to monitor IBM System x?

Requirement: IBM Systems Director Platform Agent

This sensor type needs the IBM Systems Director Platform Agent to be installed on the target
IBM device in order to monitor it through SNMP. For more information, please see section
More below.
24.03.2015
1775

Add Sensor
later.
Select the logical disks of the IBM device you want to monitor. PRTG creates one sensor for
IBM SYSTEM X LOGICAL DISK SETTINGS

Disk
Select the logical disks you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
1776
24.03.2015


Tags

default value.
Priority
IBM SYSTEM X LOGICAL DISK SETTINGS

Disk
Shows the ID of the logical disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
1777

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1778
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1779


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1780
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1781

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1782
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
1783

141 SNMP IBM System X Physical Disk Sensor
6.8.141 SNM P IBM Sy stem X Phy sical Disk Sensor

The SNMP IBM System X Physical Disk sensor monitors a physical disk in an IBM server via
It shows the status of a physical disk.
SNMP IBM Sy stem X Phy sic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_ibm_sy stemx_phy sic al_disk.png
Remarks
Requires
1784


More below.
1784
24.03.2015

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
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
24.03.2015
1785


Tags

default value.
Priority
IBM SYSTEM X PHYSICAL DISK SETTINGS

Disk
Shows the ID of the physical disk that this sensor monitors. Once
the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1786
24.03.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
24.03.2015
1787

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1788
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1789


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1790
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
1791

More

Notifications
Others
1792
159
section.
24.03.2015

142 SNMP IBM System X Physical Memory Sensor
6.8.142 SNM P IBM Sy stem X Phy sical M emory Sensor

The SNMP IBM System X Physical Memory sensor monitors the memory modules in an IBM
server via Simple Network Management Protocol (SNMP).
Condition of memory controller
Power status (on or off)
SNMP IBM Sy stem X Phy sic al Memory Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_ibm_sy stemx_phy sic al_memory .png
Remarks
Requires
1794

24.03.2015
1793


More below.
Add Sensor
later.
Select the memory modules of the IBM server you want to monitor. PRTG creates one sensor
for each module you choose in the Add Sensor dialog. The settings you choose in this dialog
are valid for all of the sensors that are created.
IBM SYSTEM X PHYSICAL MEMOR Y SETTINGS

Module
Select the memory modules you want to add a sensor for. You see
table head.
Sensor Settings
1794
24.03.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
IBM SYSTEM X PHYSICAL MEMOR Y SETTINGS

Name
Caption
Serial Number
Shows further information about the module. Once a sensor is

anew.
Size
24.03.2015
1795

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1796
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1797


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1798
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1799

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1800
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
1801

143 SNMP IBM System X System Health Sensor
6.8.143 SNM P IBM Sy stem X Sy stem Health Sensor

The SNMP IBM System X System Health sensor monitors the system health of an IBM device via
It can show the following, depending on what measurement you select:
Revolutions per minute of fans (or the current percentage of the possible maximum)
Temperature of ambient and CPUs
Voltage of planars
Status of power supplies
These channels are created at run-time, depending on the available measurement components.
sensor setup..
SNMP IBM Sy stem X Sy stem Health Sensor
1802
28.04.2015

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_ibm_sy stemx_sy stem_health.png
Remarks
Requires
1803
Note: This sensor can also run directly on an Integrated Management Module (IMM) network
port and can show the overall health on IMMs.
Note: If the IBM device returns a string in an unexpected format for the percentage of fan
revolutions (for example, "offline"), this sensor will show -1% in the corresponding channel.
You can define a Down status 135 for this via channel limits 2712 .

More below.
Note: The SNMP IBM System X System Health sensor can also run directly on an Integrated
Management Module (IMM) network port and can show the overall health on IMMs.
Add Sensor
later.
Select the measurements of the IBM device you want to monitor. PRTG creates one sensor for
each measurement you choose in the Add Sensor dialog. The settings you choose in this
28.04.2015
1803

IBM SYSTEM X SYSTEM HEALTH SPECIFIC

Measurement
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1804
28.04.2015

IBM SYSTEM X SYSTEM HEALTH SPECIFIC

Source
Shows the source of the measurement that this sensor monitors.

Measurement
Shows the measurement that this sensor monitors. Once a sensor

anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
28.04.2015
1805

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1806
28.04.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
28.04.2015
1807


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1808
28.04.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
28.04.2015
1809

More

Notifications
Others
1810
159
section.
28.04.2015

144 SNMP interSeptor Pro Environment Sensor
6.8.144 SNM P interSeptor Pro Environment Sensor

The SNMP interSeptor Pro Environment sensor queries data from a Jacarta interSeptor Pro
environmental monitoring system via Simple Network Management Protocol (SNMP).
It can shows the following as measured by the Jacarta interSeptor Pro device:
Temperature
Humidity
Remarks
Note: To monitor data of an interSeptor Pro device with this sensor, you have to add the IP
address of your PRTG installation to Access Cont rol in the interSeptor Pro control panel.
Open the interSeptor Pro web interface, select Int erSept or Pro Menu | Sy st em
Configurat ion | Access Cont rol, and allow access for PRTG's IP address.
Add Sensor
later.
Select the measuring points of interSeptor Pro device you want to monitor. PRTG creates one
sensor for each measuring point you choose in the Add Sensor dialog. The settings you
INTER SEPTOR ENVIR ONMENT SPECIFIC

Measuring Point
Select the measuring points you want to add a sensor for. You see
table head.
Sensor Settings
18.03.2016
1811


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
INTER SEPTOR ENVIR ONMENT SPECIFIC

Name
Shows information about the measurement which this sensor

Measuring Point
Shows the measuring point which this sensor monitors. Once a

the sensor anew.
1812
18.03.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.03.2016
1813

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1814
18.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
18.03.2016
1815


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1816
18.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.03.2016
1817

More

Notifications
Others
1818
159
section.
18.03.2016

145 SNMP Juniper NS System Health Sensor
6.8.145 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
Status of memory usage in percent
Status of 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

Clic k here to enlarge: http://media-s3.paessler.c om.s3.amazonaws.c om/prtg-sc reenshots/
SNMP_Juniper_Sy stem_Health.png
31.08.2015
1819

Remarks
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
1820
31.08.2015


Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
31.08.2015

1821

Inherited Settings
described below.
1822
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
1823


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1824
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
1825

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
1826
31.08.2015


Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
More

Notifications
Others
31.08.2015
159
section.
1827

146 SNMP LenovoEMC Physical Disk Sensor
6.8.146 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
135
Up),
Unknown (sensor status Warning)

Foreign (sensor status Warning)
Faulted (sensor status Down)
Missing (sensor status Down)
Remarks
Add Sensor
later.
Select the physical disks in the LenovoEMC NAS. PRTG creates one sensor for each disk you
LENOVOEMC PHYSICAL DISK SETTINGS

Disk
1828
head.
18.03.2016

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
18.03.2016
1829

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
Primary Channel

Graph Type

for each channel.
Stack Unit
1830

18.03.2016

Inherited Settings
described below.
18.03.2016
1831

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1832
18.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
18.03.2016
1833


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1834
18.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
18.03.2016
1835

Others
1836
159
section.
18.03.2016

147 SNMP LenovoEMC System Health Sensor
6.8.147 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
135
can be:
Normal (sensor status Up)

Unknown (sensor status Warning)
Rebuilding (sensor status Warning)
Degraded (sensor status Warning)
RebuildFS (sensor status Warning)
Faulted (sensor status Down)
Furthermore, this sensor can show, for example, states of several fans, voltages, and
temperatures. These channels are created at run-time depending on the available measurement
components in the LenovoEMC NAS. Which channels the sensor actually shows might depend
on the monitored device and the sensor setup.
Remarks
Add Sensor
later.
Sensor Settings
18.03.2016
1837


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1838
18.03.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
18.03.2016
1839

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1840
18.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
18.03.2016
1841


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1842
18.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
18.03.2016
1843

Others
1844
159
section.
18.03.2016

148 SNMP Library Sensor
6.8.148 SNM P Library Sensor

The SNMP Library sensor monitors a device using Simple Network Management Protocol
(SNMP) in combination with a compiled Management Information Base (MIB) library file. This
provides extended monitoring beyond the standard SNMP sensors of PRTG.
To monitor any SNMP capable device, you can download the manufacturer's MIB files for these
devices, convert them to the Paessler oidlib format, and import them into PRTG. To make your
monitoring setup as convenient as possible, PRTG is delivered with pre-compiled oidlib library
files that already contain the Object Identifier (OID) of SNMP counters for the most common
devices in a network. See section More 1855 for details.
SNMP Library Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_library .png
Remarks
Knowledge Base: How do SNMP, MIBs and OIDs work?
Knowledge Base: How can I import my MIB files into PRTG?
Add Sensor
Manually add 256 a new sensor to an SNMP device. From the Add Sensor dialog, select SNMP
Library sensor. PRTG will show a list of oidlib files available on the system. This contains all
library files stored at the \snmplibs folder of your PRTG installation directoryboth the ones
delivered with PRTG and your own files. For details about directory paths, please see section
Dat a St orage 3135 .
15.04.2016
1845

List of SNMP Library Files
The file names in the list indicate the potential purpose. Select a name that appears appropriate
for your device (for example, choose an MIB file that you imported before) and confirm with
the OK button. Often, Paessler common oid library .oidlib is a good start. If the file does not
fit to your device, this will result in the error message the scan for available monitoring items
has failed on this device: No such object (SNMP error # 222). If you see this message, please
hit the Cancel button and try adding the sensor with another file. If counters were found for
your device, you will see the sensor's settings.
Default OIDLIB Files Overview

The following files are delivered with PRTG and allow to extend your SNMP monitoring for many
devices. Please be aware that not all devices and/or parameters may be supported by the
libraries.
APC UPS.oidlib
Can be used to monitor uninterruptible power supplies (UPS) from APC American Power
Conversion Corp.
APCSensorst at ionlib.oidlib
Can be used to monitor alarm status, communication status, humidity, and temperature as
shown by an APC sensor station.
Basic Linux Library (UCD-SNMP-MIB).oidlib
Can be used to monitor basic system parameters on Linux systems, such as memory, disk
and swap, CPU, etc.
1846
15.04.2016

cisco-int erfaces.oidlib
Can be used to monitor Cisco specific parameters, for example, the number of present
network interfaces on a system, several states of an interface (admin, oper, speed, type,
errors, discards, etc.), and more.
cisco-queue.oidlib
Can be used to monitor queues on a Cisco interface, for example, queue depth and its
maximum, discarded messages from the queue, the number of the queue within the queue
set, etc.
Dell St orage Management .oidlib
Can be used to monitor Dell storage devices. Possible parameters include disk arrays,
battery and power supply, fan and temperature, virtual disk, etc.
Dell Sy st ems Management Inst rument at ion.oidlib
Can be used to monitor the hardware of Dell systems. Possible parameters include ACPower
and battery, alerts, base board, Bios, BMC, chassis, COO, cooling, event log, firmware, IDE,
keyboard, memory, port, network, processor, SCSI, system, temperature, USB, UUID, etc.
HP LaserJet St at us.oidlib
Can be used to monitor toner, paper, and jam status of an HP LaserJet printer.
Linux SNMP (AX BGP DisMan Et herLike Host ).oidlib
Can be used to monitor different aspects of Linux systems. Note: This file can find a very
large number of possible interfaces. It may take a few seconds until the selection table is
shown.
Linux SNMP (Framework Proxy Not i v2).oidlib
shown.
Linux SNMP (IP Net SNMP Not i OSPF RMON SMUX ).oidlib
shown.
Linux SNMP (Source TCP UCD UDP).oidlib
shown.
Paessler Common OID Library .oidlib
Can be used to monitor many common hardware devices. It is used for several sensors and
is encrypted.
SNMP Informant st d.oidlib
Can be used to monitor logical disks, processor, memory, and network interface on
Windows systems.
15.04.2016
1847

Import MIB Files

Additionally you can create your own oidlib files by importing your device manufacturers' MIB
files with the free tool Paessler MIB Import er. Simply convert your mib files and save the
resulting oidlib files to the \snmplibs subfolder of your PRTG program directory. For details
about directory paths, please see Dat a St orage 3135 . For more information and download of
MIB Import er, please see the link in the More 1855 section below.
Note: If your imported oidlib file contains lookups 3095 (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 creates then a lookup definition file using the
lookupname of the chosen library as id parameter. Override this lookup definition with your
own custom lookup as described in section Define LookupsCust omizing Lookups 3101 .
SNMP Library SensorAdd Sensor Settings

SNMP LIBR AR Y SPECIFIC

Library
This shows the path to the oidlib file selected before. This setting
is shown for your information only and cannot be changed here.
Library-OIDs
Select the aspects of the device you want to monitor. A list

specific to your setup is shown. It contains all counters found in
the chosen library that match your device. Select one or more
items by adding a check mark in front of the respective line. You
table head. For each selection, PRTG will create one sensor when
you click the Cont inue button.
Sensor Settings
1848
15.04.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
15.04.2016
1849

SNMP LIBR AR Y SPECIFIC

Selected Interface
Shows the counter that this sensor monitors. Once a sensor is

anew.
Unit String
Enter a string that represents the unit of the returned values. This
is for display purposes for the sensor data only. Please enter a
string.
Multiplication
Enter the multiplier if you want to multiply the received data with a
certain value. Please enter an integer value.
Division
Enter the divisor if you want to divide the received data by a

certain value. Please enter an integer value.
If Value Changes
change.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1850
15.04.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
15.04.2016
1851

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1852
15.04.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
15.04.2016
1853


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1854
15.04.2016

ACCESS R IGHTS
User Group Access
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?

15.04.2016
1855

Notifications
Others
1856
159
section.
15.04.2016

149 SNMP Linux Disk Free Sensor
6.8.149 SNM P Linux Disk Free Sensor

The SNMP Linux Disk Free sensor monitors free space on disks of a Linux/Unix system using
Free total disk space in bytes
Free space in bytes for every mounted partition
Free space in percent for every mounted partition
Free inodes in percent for every mounted partition
Note: The free space returned by this sensor type shows the disk space that is not yet used.
Not all of this space may be available for use, as a part of this space can be reserved by the
system, for example, for redundancy purposes. For details, please see the article linked in the
24.03.2015
1857


Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_linux_disk_free.png
Remarks
Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values for
my target Linux system?
Knowledge Base: Checklist: Setting up SNMP on Linux
1858
24.03.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
1859

SET LIMITS CHECKED AGAINST ALL DISKS

In this section you can set limits that are valid for all channels and all drives. By entering
limits, you can define when the sensor will enter a Warning or Down status, depending on
the data provided by all drives that this sensor monitors. If you want to define limits for
separate channels individually please use the limit settings in the sensor Channel settings.
Note: All limits that you define here are valid additionally to the limits defined in the
particular Channels settings! The limits are valid simultaneously, so the first limit that is
breached applies.
Percentage Limit Check Enable or disable a limit check for the free space in percentage
channels of all drives. By default, percentage limits are enabled with
lower warning and lower error limit. Choose between:
Only use t he limit s in t he set t ings of t he percent age
channels: Do not define sensor limits which are valid for all
percentage channels. The sensor only uses limits which you
define in the settings of the particular "free space in percent"
channels to determine the status.
Use t he limit s of bot h t he sensor and t he channel set t ings:
Define limits for the sensor which are valid for all drives
(percentage channels). Additional fields appear below. The
sensor enters a Warning or Down status when free space limits
are undercut or overrun.
Upper Error Limit
This field is only visible if you enable percentage limit check above.
Specify an upper limit in percent for a Down status. If the free disk
space of one of your drives overruns this percent value, the
sensor switches to Down. Please enter an integer value or leave
the field empty.
Note: The limits set here are valid for all channels of this sensor.
You can additionally set individual limits for each sensor channel in
the Sensor Channels Set t ings 2711 . The limits set here and in the
channel settings are valid simultaneously!
Upper Warning Limit
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.
1860
24.03.2015


Lower Warning Limit
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
Specify a lower limit in percent for a Down status. If the free disk
the field empty.
Size Limit Check
Enable or disable a limit check for the free bytes channels of all
drives. By default, byte size limits are not enabled for drives.
Choose between:
Only use t he limit s in t he set t ings of t he by t e size channels:
Do not define sensor limits which are valid for all byte size
channels. The sensor only uses limits which you define in the
settings of the particular free space in bytes channels to
determine the status.
Define limits for the sensor which are valid for all drives (byte
size channels). Additional fields appear below. The sensor enters
a Warning or Down status when free space limits are undercut
or overrun.
Upper Error Limit
This field is only visible if you enable byte limit check above. Specify
an upper limit. Use the same unit as shown by the free bytes
channels of this sensor (by default this is MByte). If the free disk
space of one of your drives overruns this bytes value, the sensor
switches to Down. Please enter an integer value or leave the field
empty.
24.03.2015
1861


Upper Warning Limit
switches to Warning. Please enter an integer value or leave the
field empty.
Lower Warning Limit
a lower limit. Use the same unit as shown by the free bytes
space of one of your drives undercuts this bytes value, the sensor
field empty.
Lower Error Limit
empty.
Alarm on Missing/
Removed Disk
If a monitored disk is removed or not found, values are set to

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.
1862
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1863

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1864
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1865


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1866
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
1867

More

Notifications
Others
1868
159
section.
24.03.2015

150 SNMP Linux Load Average Sensor
6.8.150 SNM P Linux Load Average Sensor

The SNMP Load Average sensor monitors the system load average of a Linux/Unix system
using Simple Network Management Protocol (SNMP).
Average system load within a 1 minute interval
Average system load within a 5 minutes interval
SNMP Linux Load Av erage Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_linux_load_av erage.png
Remarks
Add Sensor
later.
24.03.2015
1869

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type
1870
24.03.2015

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1871

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1872
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1873


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1874
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

24.03.2015
1875

Notifications
Others
1876
159
section.
24.03.2015

151 SNMP Linux Meminfo Sensor
6.8.151 SNM P Linux M eminfo Sensor

The SNMP Linux Meminfo sensor monitors the memory usage of a Linux/Unix system using
It shows the following :
Available memory in absolute and percentage values
Used physical memory (free memory plus buffer plus cache) in percent
Free physical memory (free memory plus buffer plus cache) in bytes
Used swap memory in percent
Free swap memory in bytes
Used memory on the whole system (physical memory plus swap) in percent
Free memory on the whole system (physical memory plus swap) in bytes
SNMP LInux Meminfo Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_linux_meminfo.png
24.03.2015
1877

Remarks
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1878
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1879

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1880
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1881


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1882
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
1883

More

Notifications
Others
1884
159
section.
24.03.2015

152 SNMP Linux Physical Disk Sensor
6.8.152 SNM P Linux Phy sical Disk Sensor

The SNMP Linux Physical Disk sensor monitors input/output (I/O) on disks of a Linux/Unix
system using Simple Network Management Protocol (SNMP).
Read bytes per second
Written bytes per second
Number of read accesses per second
Number of write accesses per second
SNMP Linux Phy sic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_linux_phy sic al_disk.png
Remarks
24.03.2015
1885

Add Sensor
later.
Select the disks of the Linux/Unix system you want to monitor. PRTG creates one sensor for
PHYSICAL DISK SETTINGS

Disk
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
1886
24.03.2015


Tags

default value.
Priority
PHYSICAL DISK SETTINGS

Disk
Bitmask
Shows further information about the disk that this sensor

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
1887

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1888
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1889


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1890
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1891

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1892
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
1893

153 SNMP Memory Sensor
6.8.153 SNM P M emory Sensor

The SNMP Memory sensor monitors the memory usage of a system via Simple Network
Available memory in bytes
Available memory in percent
Total memory
Note: This sensor uses more generic Object Identifier (OID) values compared to the SNMP
Linux Meminfo Sensor 1877 .
SNMP Memory Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_memory .png
Remarks
1894
31.08.2015

Add Sensor
later.
Select the memory types you want to monitor. PRTG creates one sensor for each memory
type you choose in the Add Sensor dialog. The settings you choose in this dialog are valid for
MEMOR Y SETTINGS
Memory
Select one or more memory types you want to add a sensor for.
in the table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
31.08.2015
1895


Tags

default value.
Priority
MEMOR Y SETTINGS
Memory
Shows the type of the memory that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
1896
31.08.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
31.08.2015
1897

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1898
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
1899


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1900
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
31.08.2015
1901

More

Notifications
Others
1902
159
section.
31.08.2015

154 SNMP NetApp Disk Free Sensor
6.8.154 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

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_disk_free.png
15.04.2016
1903

Remarks
Knowledge Base: How can I monitor capacity and used disk space on a NetApp?
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
head.
Sensor Settings
1904
15.04.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

File System
Shows the name of the disk that this sensor is monitoring. Once a
the sensor anew.
Virtual Disk
Shows the name of the virtual disk that this sensor is monitoring (if
applicable). Once a sensor is created, you cannot change this
15.04.2016
1905

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1906
15.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.04.2016
1907


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1908
15.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.04.2016
1909

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1910
15.04.2016

More
Knowledge Base: How can I monitor capacity and used disk space on a NetApp?

Notifications
Others
15.04.2016
159
section.
1911

155 SNMP NetApp Enclosure Sensor
6.8.155 SNM P NetApp Enclosure Sensor

The SNMP NetApp Enclosure sensor monitors the power supply and cooling of an enclosure
that is part of a NetApp storage system via Simple Network Management Protocol (SNMP).
It can show the following, depending on the measurements you choose:
Temperatures
Rotations per minute (RPM) of fans and the number of failed fans
Voltages in mV, the number of broken electronic parts, and the number of broken power
supplies
Currents in mA
SNMP NetApp Enc losure Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_enc losure.png
1912
15.04.2016

Remarks
Add Sensor
later.
Select the power supply and cooling measurements of an enclosure on a NetApp you want to
monitor. PRTG creates one sensor for each enclosure/measurement combination you choose
that are created.
NETAPP ENCLOSU R E SETTINGS

Enclosure
Select the enclosures with the desired measurement you want to

add a sensor for. You see a list with the names of all items which
are available to monitor. Select the desired items by adding check
Sensor Settings
15.04.2016
1913


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
NETAPP ENCLOSU R E SETTINGS

Enclosure
Shows the identifier of the enclosure that this sensor is

monitoring. Once a sensor is created, you cannot change this
Measurement
Shows the monitored measurement. Once a sensor is created, you

1914
15.04.2016

NETAPP SPECIFIC
N/A Measurements
Define the sensor behavior if the requested NetApp value is not

available ("N/A" values). Choose between:
Int erpret as error (default ): Choose this option to set the
sensor to a Down status if a measurement is not available. We
recommend that you use this setting to not miss any hardware
errors.
Int erpret as valid: Choose this option to handle unavailable
measurements as valid sensor results to keep the sensor in Up
status. This might be useful, for example, if a hardware sensor on
the NetApp is disabled for some reason but actually there is no
hardware error. If the NetApp returns an "N/A" measurement, the
sensor interprets this as "0".
We recommend 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
replaces "0" with the message "Not Available". Open the Sensor
Channels Set t ings 2711 of the affected channel(s) and choose this
file in section Value Lookup. For details, please see section
Define Lookups 3095 .
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
15.04.2016
1915

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1916
15.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.04.2016
1917


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1918
15.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.04.2016
1919

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1920
15.04.2016

More

Notifications
Others
15.04.2016
159
section.
1921

156 SNMP NetApp I/O Sensor
6.8.156 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
1922
24.03.2015


Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_io.png
Remarks
24.03.2015
1923

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1924
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1925

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1926
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1927


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1928
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
1929

More

Notifications
Others
1930
159
section.
24.03.2015

157 SNMP NetApp License Sensor
6.8.157 SNM P NetApp License Sensor

The SNMP NetApp License sensor monitors the licenses for the services of a NetApp storage
It shows how much time is left until the license for a service expires. This can help you to
detect when a timely limited NetApp license is going to expire.
SNMP NetApp Lic ense Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_lic ense.png
Remarks
Add Sensor
later.
Select the NetApp license you want to monitor. PRTG creates one sensor for each license you
24.03.2015
1931

NETAPP LICENSE SETTINGS

License for Service
Select the licenses you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
1932
24.03.2015

NETAPP LICENSE SETTINGS

License for Service
Shows the name of the service whose license this sensor

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1933

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1934
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1935


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1936
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
1937

More

Notifications
Others
1938
159
section.
24.03.2015

158 SNMP NetApp Logical Unit Sensor
6.8.158 SNM P NetApp Logical Unit Sensor

The SNMP NetApp Logical Unit sensor monitors the input/output operations (IOPS) on a logical
unit of a NetApp storage system via Simple Network Management Protocol (SNMP).
Total number of operations per second
Data read speed
Data write speed
Number of errors per second
Number of read operations per second
Number of write operations per second
Number of other operations per second
Status of the logical unit (online or offline)
SNMP NetApp Logic al Unit Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_logic al_unit.png
24.03.2015
1939

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 in this dialog are valid for

Logical Unit
Select the logical units you want to add a sensor for. You see a list
head.
Sensor Settings
1940
24.03.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
NETAPP LOGICAL U NIT SETTINGS

Logical Unit
Shows the name of the logical unit that this sensor monitors. Once
the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type
24.03.2015
1941

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
1942
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1943


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1944
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1945

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1946
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
1947

159 SNMP NetApp Network Interface Sensor
6.8.159 SNM P NetApp Network Interface Sensor

The SNMP NetApp Network Interface sensor monitors a network card of a NetApp storage
Traffic in
Traffic out
Number of errors per second (in and out).
SNMP NetApp Network Interfac e Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_network_interfac e.png
Remarks
Add Sensor
later.
1948
24.03.2015

Select the network interfaces on the NetApp you want to monitor. PRTG creates one sensor
for each interface you choose in the Add Sensor dialog. The settings you choose in this
NETAPP NETWOR K INTER FACE SETTINGS

Network Interface
Select the interfaces you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
24.03.2015
1949


Priority
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
Primary Channel

Graph Type

for each channel.
Stack Unit
1950

24.03.2015

Inherited Settings
described below.
24.03.2015
1951

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1952
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1953


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1954
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
1955

More

Notifications
Others
1956
159
section.
24.03.2015

160 SNMP NetApp System Health Sensor
6.8.160 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.
24.03.2015
1957

SNMP NetApp Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_netapp_sy stem_health.png
Remarks
1958
24.03.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
1959

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
1960
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1961


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1962
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1963

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1964
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
1965

161 SNMP Poseidon Environment Sensor
6.8.161 SNM P Poseidon Environment Sensor

The SNMP Poseidon Environment sensor monitors performance counters for environmental
measurements on Poseidon hardware via Simple Network Management Protocol (SNMP).
It can show, depending on available measurement components on the hardware device and
what measurement you choose:
Humidity
Temperature
sensor setup.
SNMP Poseidon Env ironment Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_poseidon_env ironment.png
Remarks
Add Sensor
later.
1966
24.03.2015

In order to monitor performance counters for environmental measurements on Poseidon

hardware, PRTG will create one sensor for each measuring point you choose. The settings you
POSEIDON ENVIR ONMENT SPECIFIC

Measuring Point
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
24.03.2015
1967


Priority
POSEIDON ENVIR ONMENT SPECIFIC

Name
Unit
Measuring Point
Shows further information about the measurement. Once a sensor

anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
1968

24.03.2015

Inherited Settings
described below.
24.03.2015
1969

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1970
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1971


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1972
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
1973

Others
1974
159
section.
24.03.2015

162 SNMP Printer Sensor
6.8.162 SNM P Printer Sensor

The SNMP Printer sensor is a generic sensor which monitors various types of printers via
Total number of printed pages
Fill level of cartridges and toners
Status of the printer cover
Additionally, the sensor shows the printer status as sensor message.
SNMP Printer Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_printer.png
Remarks
This sensor type supports the following printers, among others: HP OfficeJet printers, HP
LaserJet printers, RICOH SP 5200, SP 3410, SP C242DN, MP C3003, MP C2503
21.01.2016
1975

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
1976
21.01.2016


Priority
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
1977

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1978
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
1979


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1980
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
21.01.2016
1981

Others
1982
159
section.
21.01.2016

163 SNMP QNAP Logical Disk Sensor
6.8.163 SNM P QNAP Logical Disk Sensor

The SNMP QNAP Logical Disk sensor monitors a logical disk in a QNAP Network Attached
Storage (NAS) via Simple Network Management Protocol (SNMP).
Free disk space in percent
Free disk space in bytes
Status of the volume
SNMP QNAP Logic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_qnap_logic al_disk.png
Remarks
24.03.2015
1983

Add Sensor
later.
Select the logical disks in the QNAP NAS you want to monitor. PRTG creates one sensor for
QNAP NAS SETTINGS

Disk
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
1984
24.03.2015


Tags

default value.
Priority
QNAP NAS SETTINGS

Disk
Description
File System

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
1985

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1986
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
1987


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
1988
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
1989

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
1990
24.03.2015

Others
24.03.2015
159
section.
1991

164 SNMP QNAP Physical Disk Sensor
6.8.164 SNM P QNAP Phy sical Disk Sensor

The SNMP QNAP Physical Disk sensor monitors a physical disk in a QNAP Network Attached
Temperature
Disk status
Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status of the disk.
SNMP QNAP Phy sic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_qnap_phy sic al_disk.png
Remarks
1992
24.03.2015

Add Sensor
later.
Select the physical disks in the QNAP NAS you want to monitor. PRTG creates one sensor for
each disk you choose in the Add Sensor dialog. You can also define the unit of the
temperature measurement. The settings you choose in this dialog are valid for all of the
QNAP NAS SETTINGS

Disk
table head.
Unit
Select the unit of the temperature measurement. Choose

between Celsius and Fahrenheit .
Sensor Settings

Sensor Name
24.03.2015

171 .
1993


Parent Tags
Tags

default value.
Priority
QNAP NAS SETTINGS

Disk
Description
Model
Capacity
Shows further information about the disk. Once a sensor is

anew.
Unit
SENSOR DISPLAY
Primary Channel
1994

24.03.2015

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
1995

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
1996
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
1997


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
1998
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
1999

Others
2000
159
section.
24.03.2015

165 SNMP QNAP System Health Sensor
6.8.165 SNM P QNAP Sy stem Health Sensor

The SNMP QNAP System Health sensor monitors the system health of a QNAP Network
It can show the following, depending on the available measurement components:
CPU usage in percent
Temperature of CPU
Temperature of system
Revolutions of fans per minute (RPM)
sensor setup.
SNMP QNAP Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_qnap_sy stem_health.png
Remarks
24.03.2015
2001

Add Sensor
later.
To monitor the system health of a QNAP NAS, specify the unit of the temperature
measurement.
QNAP NAS SETTINGS

Unit

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
2002
24.03.2015


Priority
QNAP NAS SETTINGS

Unit
Shows the unit of temperatures as monitored with this sensor.

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
2003

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2004
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2005


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2006
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2007

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2008
24.03.2015

Others
24.03.2015
159
section.
2009

166 SNMP RMON Sensor
6.8.166 SNM P RM ON Sensor

The SNMP RMON sensor monitors traffic on a device using the Remote Monitoring (RMON)
standard via Simple Network Management Protocol (SNMP). You can create it on an SNMP
compatible device that provides traffic data via RMON. Depending on the data returned by your
device, traffic data for each port can be displayed in different channels, allowing detailed
analysis. If available, the sensor queries 64-bit counters.
For each port, the sensor can show, for example:
Transmitted kbit/s
Packets (#/s)
Broadcast Packets (#/s)
Multicast Packets (#/s)
CRC Errors (#/s)
Undersize Packets (#/s)
Oversize Packets (#/s)
Fragments (#/s)
Jabbers (#/s)
Collisions (#/s)
Packets <= 64 Byte (#/s)
Packets 65 - 127 Bytes (#/s)
Drop Events (#/s)
sensor setup.
2010
31.08.2015

SNMP RMON Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_rmon.png
Remarks
Note: You can define the displayed sensor name with port name templates in the SNMP
Compat ibilit y Opt ions 336 of the parent device.
31.08.2015
2011

Knowledge Base: What value does the "Transmitted" channel of an RMON sensor show?
Knowledge Base: How do PRTG's automatic port name and number updates work for SNMP
traffic sensors?
Add Sensor
later.
Select the ports you want to monitor. PRTG creates one sensor for each port you choose in
that are created.
R MON SPECIFIC
Ports
Select the ports you want to add a sensor for. You see a list with
head.
Sensor Settings
2012
31.08.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
R MON SPECIFIC
Port
Shows the number of the interface port in your physical device

that this sensor monitors. Once a sensor is created, you cannot
Channel Mask
Describes which channels are available and might be useful for

technical support. This setting is shown for your information only
and cannot be changed here.
SENSOR DISPLAY
Primary Channel
31.08.2015

2013

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2014
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2016
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
2017

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2018
31.08.2015

More
Knowledge Base: What value does the "Transmitted" channel of an RMON sensor show?
traffic sensors?

Notifications
Others
31.08.2015
159
section.
2019

167 SNMP SonicWALL System Health Sensor
6.8.167 SNM P SonicWALL Sy stem Health Sensor

The SNMP SonicWALL System Health sensor monitors health values of a Dell SonicWALL
Network Security Appliance (NSA) via Simple Network Management Protocol (SNMP).
Memory usage in percent
Connection cache usage in percent
SNMP Sonic WALL Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sonic wall_sy stem_health.png
Remarks
Knowledge Base: Why does PRTG write error messages into my SonicWALL log?
Add Sensor
later.
2020
24.03.2015

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type
24.03.2015
2021

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
2022
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2023


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2024
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2025

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2026
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
2027

168 SNMP SonicWALL VPN Traffic Sensor
6.8.168 SNM P SonicWALL VPN Traffic Sensor

The SNMP SonicWALL VPN Traffic sensor monitors the traffic of an Internet Protocol Security
(IPsec) Virtual Private Network (VPN) on a Dell SonicWALL Network Security Appliance (NSA) via
Number of encrypted and decrypted packets per second
Bytes of encrypted and decrypted transmissions per second
Number of in- and outgoing fragmented packets per second
SNMP Sonic WALL VPN Traffic Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sonic wall_v pn_traffic .png
Remarks
2028
24.03.2015

Add Sensor
later.
Select the connections of the SonicWALL VPN you want to monitor. PRTG creates one sensor
for each connection you choose in the Add Sensor dialog. The settings you choose in this
SONICWALL VPN SPECIFIC

Connections
Select the connections you want to add a sensor for. You see a
table head.
Select the criteria to use for connection identification. PRTG always

uses the first connection found that matches all criteria. Choose
between:
By Index: Every connection has a unique index. This is the safest
method to identify your connection. Though, if the connection is
lost and reconnected, a new index will be assigned.
By Remot e IP: If the target of the VPN has always the same IP,
you can use this IP to identify the connection.
By Securit y Policy Name: If you use a different Security Policy
for every VPN, you can use its name to identify the connection.
By Remot e IP and Securit y Policy Name: You can also combine
both identification methods.
Sensor Settings
24.03.2015
2029


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SONICWALL VPN SPECIFIC

Security Policy
Remote IP
Shows further information about the monitored connection. Once

the sensor anew.
Index
2030
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2031

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2032
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2033


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2034
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
2035

More

Notifications
Others
2036
159
section.
24.03.2015

169 SNMP Synology Logical Disk Sensor
6.8.169 SNM P Sy nology Logical Disk Sensor

The SNMP Synology Logical Disk sensor monitors a logical disk in a Synology Network
It can show the status of a volume.
SNMP Sy nology Logic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sy nology _logic al_disk.png
Remarks
Add Sensor
later.
Select the logical disks in the Synology NAS. PRTG creates one sensor for each disk you
24.03.2015
2037

SYNOLOGY NAS SETTINGS

Disk
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
2038
24.03.2015


Disk
Name

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2039

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2040
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2041


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2042
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
2043

Others
2044
159
section.
24.03.2015

170 SNMP Synology Physical Disk Sensor
6.8.170 SNM P Sy nology Phy sical Disk Sensor

The SNMP Physical Disk sensor monitors a physical disk in a Synology Network Attached
Temperature
Disk status
SNMP Sy nology Phy sic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sy nology _phy sic al_disk.png
Remarks
Add Sensor
later.
24.03.2015
2045

Select the physical disks in the Synology NAS you want to monitor. PRTG creates one sensor
for each disk you choose in the Add Sensor dialog. The settings you choose in this dialog are

Disk
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
2046
24.03.2015


Priority

Disk
Name
Model

Type
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
2047

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2048
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2049


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2050
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2051

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2052
24.03.2015

Others
24.03.2015
159
section.
2053

171 SNMP Synology System Health Sensor
6.8.171 SNM P Sy nology Sy stem Health Sensor

The SNMP Synology System Health sensor monitors the system health of a Synology Network
It can show the following, depending on the available measurement components:
Temperature
System status
Power status
Fan status
Memory usage in percent
CPU load in percent
sensor setup. For more information about the shown memory and CPU load values, please see
section More 2061 .
SNMP Sy nology Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sy nology _sy stem_health.png
2054
24.03.2015

Remarks
Knowledge Base: Why does my Synology System Health sensor show incorrect CPU and
memory values?
Add Sensor
later.
To monitor the system health of a Synology NAS, please specify the unit of the temperature
measurement.

Unit

Sensor Settings
24.03.2015
2055


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

Unit
Shows the unit of temperatures which this sensor monitors. Once

the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type
2056
24.03.2015

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2057

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2058
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2059


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2060
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: Why does my Synology System Health sensor show incorrect CPU and
memory values?

24.03.2015
2061

Notifications
Others
2062
159
section.
24.03.2015

172 SNMP System Uptime Sensor
6.8.172 SNM P Sy stem Uptime Sensor

The SNMP System Uptime sensor monitors the time a device is running via Simple Network
It reads the system uptime value of the monitored device and shows it.
SNMP Sy stem Uptime Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_sy stem_uptime.png
Remarks
Knowledge Base: Why does the SNMP System Uptime sensor report wrong values?
Add Sensor
later.
Sensor Settings
31.08.2015
2063


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2064
31.08.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
31.08.2015
2065

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2066
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
2067


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2068
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: Why does the SNMP System Uptime sensor report wrong values?

31.08.2015
2069

Notifications
Others
2070
159
section.
31.08.2015

173 SNMP Traffic Sensor
6.8.173 SNM P Traffic Sensor

The SNMP Traffic sensor monitors traffic on a device using Simple Network Management
Protocol (SNMP). You can create it on a device that provides traffic data, one traffic sensor for
each individual port.
Traffic in
Traffic out
Traffic total
You can also add additional channels:
Errors in and out
Discards in and out
Unicast packets in and out
Non unicast packets in and out
Multicast packets in and out
Broadcast packets in and out
Unknown protocols
sensor setup.
11.03.2016
2071

SNMP Traffic Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_traffic .png
Remarks
You can define the displayed sensor name with port name templates in the SNMP
Compat ibilit y Opt ions 336 of the parent device.
Note: We recommend that you choose SNMP v2c (most common) or SNMP v3 in the
Credent ials for SNMP Devices 332 of the parent device (if supported by the device that you
monitor). SNMP v1 does not support 64-bit counters which may result in invalid data. For
details, please the Knowledge Base: Querying 64-bit Counters with SNMP Traffic Sensors
2072
11.03.2016

traffic sensors?
Add Sensor
later.
Select the ports on SNMP devices with multiple interfaces you want to monitor. PRTG creates
one sensor for each port you choose in the Add Sensor dialog. The settings you choose in
this dialog are valid for all of the sensors that are created.
TR AFFIC SPECIFIC
Interface Number
in the table head. You can see the connection status of an
interface in the respective table column.
Note: You can group-select and -unselect interfaces by using the
buttons Select all connect ed int erfaces, Select all
disconnect ed int erfaces, and Deselect all int erfaces.
Description "IN"
Channel
For the standard channel "Traffic In", enter the channel name here.
The sensor shows it in graphs and tables. You can change this
description and the description of all other channels in the sensor
channel settings 2711 later.
Description "OUT"
Channel
For the standard channel "Traffic Out", enter the channel name
here. The sensor shows it in graphs and tables. You can change
this description and the description of all other channels in the
sensor channel settings 2711 later.
Description "TOTAL"
Channel
For the standard channel "Traffic Total" enter the channel name
here. The sensor shows it in graphs and tables. You can change
this description and the description of all other channels in the
sensor channel settings 2711 later.
11.03.2016
2073

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
2074
11.03.2016

TR AFFIC SPECIFIC
Interface Number
Shows the number and name of the interface in your physical

device 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 for debugging. Wrong
usage can result in incorrect monitoring data!
Additional Channels
By default, the channels "Traffic In", "Traffic Out", and "Traffic Total"
are created for each SNMP Traffic sensor. Choose additional
channels for all selected interfaces. Click on the respective channel
name(s) to mark them and monitor their data.
You can choose from the following additional channels:
Errors In & Out : The number of in-/outbound packets that could
not be delivered because of errors.
Discards In & Out : The number of discarded in-/outbound
packets even though no errors had been detected.
Unicast Packet s In & Out : The number of unicast packets that
were delivered.
Non Unicast Packet s In & Out (32-bit only ): The number of
non-unicast packets that were delivered.
Mult icast Packet s In & Out (64-bit only ): The number of
delivered packets which were addressed to a multicast address.
Broadcast Packet s In & Out (64-bit only ): The number of
delivered packets which were addressed to a broadcast address
Unknown Prot ocols: The number of received packets which
were discarded because of an unknown or unsupported
protocol.
Channels that are once created cannot be deleted later. You can
disable them only.
Connection Status
Handling
Define how PRTG will react when an interface is operational. A

interface which is not operational is, for example, an ethernet port
on a switch with no cable plugged in. This setting is valid for all
interfaces selected above. You can choose between:
Show alarm for all "disconnect ed" st at es: The sensor for the
interface will always turn into a red error status for a
disconnected interface. This applies if the ifOperStatus of the
interface is not "up".
Show alarm when disconnect ed, but ignore when
deact ivat ed: The sensor will go into an error status for a
disconnected interface only if it is not deliberately deactivated in
the configuration. This applies if the ifOperStatus of the interface
is not "up" and the ifAdminStatus is "up". So the sensor will keep
the Up status when the interface has been deactivated.
11.03.2016
Ignore all "disconnect ed" st at es: The sensor will not show an
alarm and its status remains green. Monitoring will be
discontinued without notice.
2075

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2076
11.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
11.03.2016
2077


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2078
11.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
11.03.2016
2079

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2080
11.03.2016

More
traffic sensors?
Knowledge Base: Querying 64-bit Counters with SNMP Traffic Sensors

Notifications
Others
11.03.2016
159
section.
2081

174 SNMP Trap Receiver Sensor
6.8.174 SNM P Trap Receiver Sensor

The SNMP Trap Receiver sensor receives and analyzes Simple Network Management Protocol
(SNMP) traps.
Overall number of received traps per second
Trap messages categorized as "warning" per second
Trap messages categorized as "error" per second
Number of dropped packets per second
The actual trap messages
SNMP Trap Rec eiv er Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_trap_rec eiv er.png
Remarks
With the available filter options, you can define individually which types of messages the
sensor will consider for monitoring, and which messages it will categorize as warning or
error messages. Depending on the filters, received messages are counted in the respective
channels.
Add the sensor to the probe device to receive all messages of the system running the
probe.
2082
21.01.2016

Add the sensor to a specific device to receive all messages from this device directly. This
makes this sensor type faster than just using source filters.
You can use trap specific placeholders in email notification templates 2840 to see the
messages when you receive an email notification. See the Knowledge Base: What
placeholders can I use with PRTG?
You can copy the Management Information Base (MIB) file for your traps into the \MIB
subfolder of your PRTG installation 3135 to translate the OIDs for the traps into readable
messages.
Note: This sensor type does not support SNMP v3 traps! Please use SNMP v1 or v2c instead.
Note: If you do not add the sensor to a probe device but to another device in PRTG, be
careful with the configuration: Ensure the IP address or DNS name of the parent device
matches the proper trap sender. For example, if you want to receive traps from a Storage
Area Network (SAN), you might have to add a device to PRTG using the IP address of a
specific array member that sends the messages. Providing a DNS name that points to the IP
address of a whole group might not work for SANs.
Knowledge Base: How do I test an SNMP Trap Receiver Sensor?
For a general introduction to the SNMP trap receiver's configuration, please see manual
section Monit oring Sy slogs and SNMP Traps 3038 .
Add Sensor
later.
Sensor Settings
21.01.2016
2083


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SNMP TR AP SPECIFIC
Listen on Port
Enter the number of the port on which the sensor waits for SNMP
traps. The default port is 162. Please enter an integer value. We
Purge Messages After
Define how long PRTG stores received trap messages for analysis.
Choose a period of time from the drop down list.
FILTER
Include Filter
2084
Define if you want to filter traps. If you leave this field empty or use
the keyword "any", the sensor will process all data. This is the
default setting. To include specific types of traps only, define filters
using a special syntax. For more information, see section Filt er
Rules 2091 .
21.01.2016

FILTER
Exclude Filter
Define which types of traps the sensor will discard and not
process. To exclude specific types of traps, define filters using a
special syntax. For more information, see section Filt er Rules 2091 .
Warning Filter
Define which types of traps count for the Warnings channel. To

categorize received traps as warning messages, define filters using
a special syntax. For more information, see section Filt er Rules 2091 .
Note: Messages are collected until a scanning interval ends. As
long as the scanning interval is running, no status change will
happen. By default, the sensor will turn into a Warning status after
a scanning interval has finished and there was at least one warning
message (and no error message) during this interval. The status will
remain Warning at least until the succeeding scanning interval has
finished. If the sensor did not receive any warning or error
message in this scanning interval, its status will turn Up again after
the interval.
Error Filter
Define which types of traps count for the Errors channel. To

categorize received traps as error messages, define filters using a
happen. By default, the sensor will turn into a Down status after a
scanning interval has finished and there was at least one error
message during this interval. The status will remain Down at least
until the succeeding scanning interval has finished. If the sensor
did not receive any warning or error message in this scanning
interval, its status will turn Up again after the interval.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
21.01.2016
2085

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2086
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2087


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2088
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2089

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2090
21.01.2016

DEBU GGING
Log Data to Disk
Define if the probe will write a log file of the received data to the
data folder (see Dat a St orage 3135 ) to the disk for debugging
purposes. Choose between:
Off (recommended): Do not write additional log files.
On: Write log files for all data received.
only.
Filter Rules for Traps

Filter rules are used for the include, exclude, warning, and error definition fields of the Trap
Receiver sensor. They are based on the following format:
field[filter]
You can use various filters suitable to your needs. Include and exclude filters define which
traps to monitored. Warning and error filters define how to categorize received traps. Provide
these filters in the sensor settings as formulas. Formulas are fields which you can combine
with boolean operators (AND, OR, NOT) and brackets.
Field
Paramet er
Examples
source[ip]
Enter an IP address where the UDPs come from; IP

masks and ranges 3094 are also possible.
source[10.0.23.50],
source[10.0.23.10-50],
source[10.0.23.10/255]
agent [ip]
Enter an IP address which specifies the object that

creates the SNMP trap. Only v1 is supported.
agent[10.0.0.1]
ent erprise
[oid]
Enter an OID which specifies the object that

originates the trap. Only v1 is supported.
enterprise
[1.3.6.1.4.1.2.6.182.1.2.3
1.1.0]
bindings
[text]
Enter a substring to match all OIDs and values in the bindings[ERROR],

bindings.
bindings
[1.3.6.1.4.1.2.6.182.1.2.3
1.1.0]
bindings
[oid,value]
Enter an OID and a substring to match a value in the

given OID. Separate OID and value with a comma.
bindings
[1.3.6.1.4.1.2.6.182.1.2.3
1.1.0,error]
gent rap
[number]
Enter a number which specifies the generic trap

type. Ranges are also possible.
gentrap[3], gentrap[2-6]
21.01.2016
2091

spect rap
[number]
Enter a number which defines the specific trap

code. Ranges are also possible.
spectrap[4], spectrap[0-3]
version
[number]
Enter a number (1 or 2) which specifies the SNMP

version.
version[1], version[2]
communit y
[text]
Enter a community string for exact, case sensitive

match.
community[public],
community[private]
Messages Tab: Review and Analyze Traps

PRTG stores received traps as common files in the data folder (see section Dat a St orage 3135 ).
To review and analyze all received messages, you can access the most recent data directly in
a table list 178 in the PRTG web interface. You can access this list via the Overview tab of the
sensors.
Note: Received traps are only shown after an (automatic) page refresh following to a sensor
scan in the table on the Overview tab (default for auto refresh 2830 is 30 seconds).
For more details and further filter options, click the Messages tab of the SNMP Trap Receiver
sensor. You will see all received messages in a table list 178 . On the top, you have display filter
options to drill down into the data for specific events of your interest. The filters are the same
as available in the sensor settings, but you can define them without using formulas. Provide
the desired parameters and PRTG loads the filtered list automatically.
Note: You can automatically add a filter by clicking the content of a column.
Advanced Filt er Set t ings
You can open advanced filter settings with by clicking the gear icon in the Filt er row. The
Advanced Filt er will appear in a popup window. In the text field, you can define a filter using
the syntax as given in section Filt er Rules for Traps 2091 . If you have provided filter parameters
on the Messages tab, the advanced filter will already include them as a corresponding formula
with the correct syntax. You can adjust this filter to your needs. You can also copy the
automatically created and manually adjusted formula for usage in the filter fields of the sensor
settings.
More
Blog Article: Introducing the New High Performance Syslog and SNMP Trap Receiver Sensors
https://www.paessler.com/blog/2013/10/11/prtg/introducing-the-new-high-performancesyslog-and-snmp-trap-receiver-sensors
Knowledge Base: How do I test an SNMP Trap Receiver Sensor?
Knowledge Base: What placeholders can I use with PRTG?
2092
21.01.2016


Notifications
Others
21.01.2016
159
section.
2093

175 SNMP Windows Service Sensor
6.8.175 SNM P Windows Service Sensor

The SNMP Windows Service sensor monitors a Windows service via Simple Network
It shows the operating status of the monitored service.
Operating states can be:
Active (sensor status
135
Up)
Continue-Pending
Pause-Pending
Paused (all with sensor status Down)
SNMP Windows Serv ic e

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/snmp_windows_serv ic e.png
Remarks
This sensor type cannot distinguish the status "not installed" from "not running".
2094
31.08.2015

Add Sensor
later.
Select the Windows services you want to monitor. PRTG creates one sensor for each service
SNMP WINDOWS SER VICE MONITOR

Service
Select the services you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name
31.08.2015

171 .
2095


Parent Tags
Tags

default value.
Priority
SNMP WINDOWS SER VICE MONITOR

Service
Shows the Windows service that this sensor monitors. Once a

the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2096
31.08.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
31.08.2015
2097

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2098
31.08.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
31.08.2015
2099


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2100
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
31.08.2015
159
section.
2101

176 SNTP Sensor
6.8.176 SNTP Sensor

The SNTP Sensor monitors a Simple Network Time Protocol (SNTP) server.
Response time of the server
Time difference in comparison to the local system time
The sensor tries to get a valid timestamp from the server up to three times per scan until it
reports an error.
SNTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sntp.png
Add Sensor
later.
Sensor Settings
2102
24.03.2015

176 SNTP Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SPECIFC
Timeout (Sec.)
24.03.2015

2103

176 SNTP Sensor
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2104
24.03.2015

176 SNTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2105

176 SNTP Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2106
24.03.2015

176 SNTP Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2107

176 SNTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
2108
159
section.
24.03.2015

177 SSH Disk Free Sensor
6.8.177 SSH Disk Free Sensor

The SSH Disk Free sensor monitors free space on disks of a Linux/Unix system using Secure
Shell (SSH).
Free disk space in bytes for every mounted partition
Free disk space in percent for every mounted partition
Total disk space
Note: The free space returned by this sensor type shows the available disk space of the
volume, minus a reserve defined for this volume (for example, for redundancy purposes). So,
this sensor shows the disk space that is actually available for use. The size of the reserved
disk space can be defined with tune2fs. For details, please see the More 2121 section below.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_disk_free.png
21.01.2016
2109

Remarks
SSH 3008 .
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
2110
21.01.2016


Priority
SSH SPECIFIC
Connection Timeout
(Sec.)
Define a timeout for the connection. This is the the time the
sensor waits to establish a connection to the host. You should
keep this value as low as possible. The maximum value is 900
seconds (15 minutes). Please enter an integer value.
its specific command (e.g. cat /proc/loadavg). The maximum value
is 60 seconds (1 minute). Please enter an integer value.
SSH Port
Choose between:
port number as defined in the Credentials for Linux/Solaris/Mac
OS (SSH/WBEM) Systems section of the device this sensor is
created on.
the parent device settings, but define a different port number
below.
Use Port Number
This field is only visible if you enabled the custom port number
setting above. Enter the port number (between 1 and 65535) that
this sensor uses for the SSH connection. Please enter an integer
value.
SSH Engine
Select the method you want to use to access data with this SSH
sensor 3008 . We strongly recommend that you use the default
Inherit from parent device (default ): Use the SSH engine that
you have defined in the parent device settings or higher in the
object hierarchy 89 . If you did not change it, this is the
recommended default engine.
21.01.2016
2111

SSH SPECIFIC
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.
Note: 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).
Result Handling

between:
[ID].t xt ") in case of error: Store the last result of the sensor
only if it throws an error.

breached applies.
2112
21.01.2016


Upper Error Limit
the field empty.
Upper Warning Limit
the field empty.
Lower Warning Limit
the field empty.
21.01.2016
2113


Lower Error Limit
the field empty.
Size Limit Check
Choose between:
or overrun.
Upper Error Limit
empty.
Upper Warning Limit
field empty.
2114
21.01.2016


Lower Warning Limit
field empty.
Lower Error Limit
empty.
Alarm on Missing/
Removed Disk

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
21.01.2016
2115

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2116
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2117


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2118
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2119

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2120
21.01.2016

More

Notifications
Others
21.01.2016
159
section.
2121

178 SSH INodes Free Sensor
6.8.178 SSH INodes Free Sensor

The SSH INodes Free sensor monitors the free index nodes on disks of Linux/Unix and Mac OS
systems via Secure Shell (SSH).
It shows free index nodes in percent, for each mount in an own sensor channel.
UNIX file systems only allow a limited number of index nodes. If the limit is exceeded, no more
data can be stored, although there might be still free space available. This sensor can help you
to notice early on if one of your drives is running out of INodes.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_inodes_free.png
Remarks
SSH 3008 .
2122
24.03.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
2123

SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
SSH Engine
default SSH engine.
2124
24.03.2015

SSH SPECIFIC
probe, or root).
Result Handling

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
2125

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2126
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2127


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2128
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2129

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2130
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
2131

179 SSH Load Average Sensor
6.8.179 SSH Load Average Sensor

The SSH Load Average sensor monitors the load average of a Linux/Unix system using Secure
Shell (SSH).
Average system load within a 1 minute interval
SSH Load Av erage Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_load_av erage.png
Remarks
SSH 3008 .
2132
24.03.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
2133

SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
SSH Engine
default SSH engine.
2134
24.03.2015

SSH SPECIFIC
probe, or root).
Result Handling

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
2135

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2136
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2137


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2138
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2139

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2140
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
2141

180 SSH Meminfo Sensor
6.8.180 SSH M eminfo Sensor

The SSH Meminfo sensor monitors the memory usage of a Linux/Unix system using Secure
Shell (SSH).
Available memory in percent
SSH Meminfo Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_meminfo.png
Remarks
SSH 3008 .
Note: This sensor type is not compatible with Mac OS systems.
2142
24.03.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
2143

SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
SSH Engine
default SSH engine.
2144
24.03.2015

SSH SPECIFIC
probe, or root).
Result Handling

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
24.03.2015
2145

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2146
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2147


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2148
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2149

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2150
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
2151

181 SSH Remote Ping Sensor
6.8.181 SSH Remote Ping Sensor

The SSH Remote Ping sensor remotely monitors the connectivity between a system running
Linux/OS X and another device, using Internet Control Message Protocol (ICMP) echo requests
("Ping") and Secure Shell (SSH).
Packet loss in percent
Minimum, maximum, and average response times measured from the remote device you
connect to

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_remote_ping.png
Remarks
SSH 3008 .
2152
24.03.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
2153

SSH R EMOTE PING CONFIGU R ATION

Target
Enter the DNS name or IP address of the target device the Ping is
sent to. The sensor will remotely connect to the parent device it is
created on via SSH, then perform a ping request from this remote
device to the target device/server. Please enter a string.
Packet Size (Bytes)
Enter the packet size in bytes for the ping. You can choose any
value between 1 and 10000. Please enter an integer value. We
Packet Count
Enter the number of packets that is sent with each scanning

interval.
Custom Parameter
Optionally enter additional parameters that will be added at the end

of the ping command. Please do not use parameters that change
the output format of the result to make sure it can still be parsed.
You cannot enter another command here. Please enter a string or
leave the field empty.
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
2154
24.03.2015

SSH SPECIFIC
Use Port Number
value.
SSH Engine
default SSH engine.
probe, or root).
Result Handling

between:
24.03.2015
2155

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2156
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2157


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2158
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2159

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2160
24.03.2015

Others
24.03.2015
159
section.
2161

182 SSH SAN Enclosure Sensor
6.8.182 SSH SAN Enclosure Sensor

The SSH SAN Enclosure sensor monitors a Storage Area Network (SAN) enclosure via Secure
Shell (SSH). The SAN has to provide a command-line interface (CLI) for this purpose.
Overall status of the enclosure
Health status of the power supplies
Health status of the controllers
Remarks
This sensor type does not support every SAN, even if it provides a CLI. The sensor only
works with specific devices, for example, with the HP P2000.
Note: It may happen that the controller of your target device breaks down. The experience
shows that this issue strongly depends on the hardware model you monitor. Please increase
the scanning interval to discharge the controller and try again.
Note: Sometimes the devices you monitor with this SSH SAN sensor return status values
which are not officially documented so that the shown sensor status in PRTG differs from the
"real" device status. For more information regarding this issue, please see the Knowledge
Base: Knowledge Base: Why does my SSH SAN sensor show a wrong status?
Note: After a firmware update of the target device, this sensor might show incorrect channel
values. Please add this sensor type anew in this case.
For this sensor type, you must define corresponding credentials in section Credent ials for
Linux/Solaris/Mac OS (SSH/WBEM) Sy st em in the settings of the device 324 you want to
use the sensor on.
For a general introduction to SSH monitoring, please see the Monit oring via SSH
section.
3008
Add Sensor
later.
Select the SAN enclosures you want to monitor. PRTG creates one sensor for each enclosure
2162
18.03.2016

SSH SAN ENCLOSU R E SETTINGS

Enclosure
Select the enclosures you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
18.03.2016
2163

SSH SAN ENCLOSU R E SETTINGS

Enclosure
Shows the identifier of the enclosure that this sensor monitors.

Durable ID
Shows the durable identifier of the enclosure that this sensor

Name
Shows the name of the enclosure that this sensor monitors. Once
the sensor anew.
WWN
Shows the WWN (World Wide Name) of the enclosure that this
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
2164
18.03.2016

SSH SPECIFIC
Use Port Number
value.
SSH Engine
default SSH engine.
probe, or root).
Result Handling

between:
18.03.2016
2165

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2166
18.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
18.03.2016
2167


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2168
18.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
18.03.2016
2169

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: Why does my SSH SAN sensor show a wrong status?

Notifications
2170
18.03.2016

Others
18.03.2016
159
section.
2171

183 SSH SAN Logical Disk Sensor
6.8.183 SSH SAN Logical Disk Sensor

The SSH SAN Logical Disk sensor monitors a logical disk on a Storage Area Network (SAN) via
Secure Shell (SSH). The SAN has to provide a command-line interface (CLI) for this purpose.
Health status of the disk
Number of I/O operations per second
Transferred data per second
sensor setup.
SSH SAN Logic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_san_logic al_disk.png
Remarks
2172
18.03.2016

use the sensor on.
section.
3008
Add Sensor
later.
Select the volumes on the SAN device you want to monitor. PRTG creates one sensor for each
volume you choose. The settings you choose in this dialog are valid for all of the sensors that
are created.
SSH SAN LOGICAL DISK SETTINGS

Volume
Select the volumes you want to add a sensor for. You see a list
head.
Sensor Settings
18.03.2016
2173


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
2174
18.03.2016

SSH SPECIFIC
Use Port Number
value.
SSH Engine
default SSH engine.
probe, or root).
Result Handling

between:
18.03.2016
2175

SSH SAN LOGICAL DISK SETTINGS

Volume
Shows the volume that this sensor monitors. Once a sensor is

anew.
Size
Shows the size of the volume that this sensor monitors. Once a
the sensor anew.
Command Mode
Define the command set to use on the monitored device to get

monitoring data. Choose between:
Basic (recommended): We recommend that you use the basic
command set for best sensor performance. This setting is
appropriate for most scenarios.
Advanced: This command set enables you to monitor additional
data on the target device like IOs and bandwidth. Because this
setting results in higher usage of system resources and so might
cause sensor instabilities, we strongly recommend that you
choose this option only if this data is crucial for your monitored
volume.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2176
18.03.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
18.03.2016
2177

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2178
18.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
18.03.2016
2179


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2180
18.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.03.2016
2181

More

Notifications
Others
2182
159
section.
18.03.2016

184 SSH SAN Physical Disk Sensor
6.8.184 SSH SAN Phy sical Disk Sensor

The SSH SAN Physical Disk sensor monitors a physical disk on a Storage Area Network (SAN)
via Secure Shell (SSH). The SAN has to provide a command-line interface (CLI) for this purpose.
Health status of the disk
Number of I/O operations per second
Transferred data per second
sensor setup.
SSH SAN Phy sic al Disk Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_san_phy sic al_disk.png
Remarks
28.04.2015
2183

use the sensor on.
section.
3008
Add Sensor
later.
Select the disks on the SAN device you want to monitor. PRTG creates one sensor for each
disk you choose in the Add Sensor dialog. The settings you choose in this dialog are valid for
SSH SAN PHYSICAL DISK SETTINGS

Disk
head.
Sensor Settings
2184
28.04.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
28.04.2015
2185

SSH SPECIFIC
below.
Use Port Number
value.
SSH Engine
default SSH engine.
probe, or root).
Result Handling

between:
2186
28.04.2015

SSH SAN PHYSICAL DISK SETTINGS

Disk

anew.
Disk Name
Shows the label of disk that this sensor monitors. Once a sensor is
anew.
Size
Shows the size of the disk that this sensor monitors. Once a
the sensor anew.
Command Mode
Define the command set to use on the monitored device to get

monitoring data. Choose between:
Basic (recommended): We recommend that you use the basic
command set for best sensor performance. This setting is
appropriate for most scenarios.
Advanced: This command set enables you to monitor additional
data on the target device like IOs and bandwidth. Because this
setting results in higher usage of system resources and so might
cause sensor instabilities, we strongly recommend that you
choose this option only if this data is crucial for your monitored
volume.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
28.04.2015
2187

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2188
28.04.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
28.04.2015
2189


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2190
28.04.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
28.04.2015
2191

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2192
28.04.2015

More

Notifications
Others
28.04.2015
159
section.
2193

185 SSH SAN System Health Sensor
6.8.185 SSH SAN Sy stem Health Sensor

The SSH SAN System Health sensor monitors the system health of a Storage Area Network
(SAN) via Secure Shell (SSH). The SAN has to provide a command-line interface (CLI) for this
purpose.
The sensor can show several metrics of an SAN, depending on the available measurement
components on the SAN:
Overall unit status
Temperature and temperature states
Voltage and voltage states
Capacitor charge and status
sensor setup.
SSH SAN Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_san_sy stem_health.png
Remarks
2194
21.01.2016

use the sensor on.
section.
3008
Add Sensor
later.
Select the metrics you want to monitor. PRTG creates one sensor for each metric you choose
that are created.
SSH SAN SPECIFIC

Metric
Select the metrics you want to add a sensor for. You see a list with
head.
Sensor Settings
21.01.2016
2195


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SSH SAN SPECIFIC

Metric
2196
Shows the metric this sensor monitors. Once a sensor is created,

21.01.2016

SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
SSH Engine
default SSH engine.
21.01.2016
2197

SSH SPECIFIC
probe, or root).
Result Handling

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2198
21.01.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
21.01.2016
2199

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2200
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2201


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2202
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
2203

More

Notifications
Others
2204
159
section.
21.01.2016

186 SSH Script Sensor
6.8.186 SSH Script Sensor

The SSH Script sensor connects to a Linux/Unix system via Secure Shell (SSH) and executes a
script file located on the target system.
Execution time
One value returned by the executable file or script (in one channel only).
SSH Sc ript Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_sc ript.png
Remarks
For details about the return value format please see the Applicat ion Programming
Note: For security reasons, you must store your script file on the target system. The file
must be located in the directory /var/prt g/script s. Ensure the script has executable rights.
If the script is not available or it was deleted from the script folder, you get the error
message "Script not found (237)".
Note: 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 not more than 50 sensors of this sensor
type on each probe.
28.04.2015
2205

SSH 3008 .
Add Sensor
later.
SENSOR SETTINGS
Script
Select a script file from the list. The drop down menu will list all
script files available in the /var/prtg/scripts directory on the target
Linux/Unix system. In order for the files to appear in this list, store
them into this directory. Ensure the script has executable rights.
In order for the sensor to show the expected values and sensor
status, your files must use the right format for the returned values
(in this case, exitcode:value:message to stdout). The exit code
determines the sensor status.
For detailed information on the expected return format and on
how to build custom sensors, please see the API documentation
find detailed information the the "Custom Sensors" tab. For an
example script, please see More 2216 section below.
Value Type
Define what kind of values your script file gives back. Choose
between:
Int eger: An integer is expected as return value. If the script
gives back a float, PRTG will display the value 0.
sensor will also display integer values unless they don't produce
a buffer overflow.
Count er: Your script returns an integer which increases. PRTG
will show the difference between the values of two sensor
scans. Note: A counter must return an integer; float is not
supported here!
2206
28.04.2015

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
Script
28.04.2015
Shows the script that is executed with each sensor scan, as

defined on sensor creation. Once a sensor is created, you cannot
2207

SENSOR SETTINGS
Parameters
If your script file catches command line parameters, you can define
them here. Placeholders can be used as well. For a full list of all
placeholders please see the API documentation (Applicat ion
Programming Int erface (API) Definit ion 3086 ).
field empty.
Mutex Name
simultaneously.
For links to more information, please see the More 709 section
below. Please enter a string or leave the field empty.
Value Type
Shows the expected value type, chosen on sensor creation. Once

the sensor anew.
If Value Changes
change.
SSH SPECIFIC
Connection Timeout
(Sec.)
2208
28.04.2015

SSH SPECIFIC
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
SSH Engine
default SSH engine.
probe, or root).
Result Handling
28.04.2015

between:
2209

SSH SPECIFIC
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
2210

28.04.2015

Inherited Settings
described below.
28.04.2015
2211

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2212
28.04.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
28.04.2015
2213


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2214
28.04.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
28.04.2015
2215

More
Knowledge Base: Is there a shell script example for PRTG's SSH Script Sensor?
3086
2707
why?

Notifications
Others
2216
159
section.
28.04.2015

187 SSH Script Advanced Sensor
6.8.187 SSH Script Advanced Sensor

The SSH Script Advanced sensor connects to a Linux/Unix system via Secure Shell (SSH) and
executes a script file located on the target system.
Execution time
Values returned by the script in multiple channels. The return value of this sensor must be
valid XML or JSON.
SSH Sc ript Adv anc ed Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssh_sc ript_adv anc ed.png
Remarks
For details about the return value format please see the Applicat ion Programming
Note: For security reasons, the script file must be stored on the target system. Please make
sure the script has executable rights.
21.01.2016
2217

SSH 3008 .

Add Sensor
later.
SENSOR SETTINGS
Script
Select a script file from the list. The drop down menu will list all
script files available in the /var/prtg/scriptsxml directory on the
target Linux/Unix system. In order for the files to appear in this list,
please store them into this directory. Please make sure the script
has executable rights. In order for the sensor to show the
expected values and sensor status, your files must return the
expected XML or JSON format to standard output. Values and
message must be embedded in the XML or JSON. For detailed
information on the expected return format and on how to build
custom sensors, please see the API documentation (Applicat ion
Programming Int erface (API) Definit ion 3086 ). There, find detailed
information the the "Custom Sensors" tab.
Sensor Settings
2218
21.01.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
Script
Shows the script that is executed with each sensor scan, as

defined on sensor creation. Once a sensor is created, you cannot
Parameters
If your script file catches command line parameters, you can define
them here. Placeholders can be used as well. For a full list of all
placeholders please see the API documentation (Applicat ion
Programming Int erface (API) Definit ion 3086 ). 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.
21.01.2016
2219

SENSOR SETTINGS
Mutex Name
EXE Result
Define what to do with the results the executable file gives back.
Choose between:
Writ e EX E result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the script to the
"Logs (Sensors)" directory (on the Master node, if in a cluster).
This is for debugging purposes. The file will be overridden with
each scanning interval. For information on how to find the folder
used for storage, please see Dat a St orage 3135 section.
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
2220
21.01.2016

SSH SPECIFIC
Use Port Number
value.
SSH Engine
default SSH engine.
probe, or root).
Result Handling

between:
21.01.2016
2221

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2222
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2223


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2224
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2225

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2226
21.01.2016

More
3086
2707
why?

Notifications
Others
21.01.2016
159
section.
2227

188 SSL Certificate Sensor
6.8.188 SSL Certificate Sensor

The SSL Certificate sensor monitors the certificate of a secure Secure Sockets Layer (SSL)/
Transport Layer Security (TLS) connection. It can show the following:
Days to expiration (with predefined lower warning and error limits)
Public key length
If the common name check is enabled and successful or not
If the certificate has been revoked (failing to query the certificate revocation list results in a
warning status)
If the certificate is trusted as root authority
If the certificate is self-signed
SSL Certific ate Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssl_c ertific ate_sensor.png
Remarks
Enter the DNS name in the parent device settings 324 exactly as written in your certificate.
For example, enter "www.paessler.com" instead of "paessler.com". The short version might
prevent the sensor from working properly.
2228
15.04.2016

To check the revocation status of a certificate, the sensor uses the same proxy settings as
configured for the Windows user account on which the PRTG probe runs. This is usually the
Windows local "system" user account. If you use a proxy, for example, please edit these
settings in the Internet Explorer on this system accordingly (on the computer running the
probe; on all nodes if in a cluster).
This sensor supersedes the HTTP Certificate Expiry sensor which is outdated. We
recommend that you use this current SSL Cert ificat e sensor 2228 to monitor SSL certificates.
Add Sensor
later.
Settings

Sensor Name

171 .
Parent Tags
15.04.2016
2229


Tags

default value.
Priority
SSL CER TIFICATE SPECIFIC

Port

Please enter an integer value. The default port is 443.
Virtual Host (SNI

Domain)
Choose which host name the sensor tries to query if your server
presents multiple certificates on the same IP address and port
combination. Please enter a string.
If in the case of virtual hosting you need to identify the specific
certificate for a specific domain while all domains use the same IP
address, you can use Server Name Identification (SNI), which is an
extension of Transport Layer Security (TLS).
Certificate Name
Validation
Define if you want the sensor to validate the certificate name using
the address of the parent device. Choose between:
Do not compare common name wit h address of parent
device (default ): The sensor does not check if the certificate
name is valid using the address of the parent device.
Compare and show 'down' st at us if common name and
address do not mat ch: The sensor compares the certificate and
the DNS name of the parent device. If they do not match, the
sensor shows a Down status 135 .
2230
15.04.2016

DEBU G OPTIONS
Sensor Result

between:
Note: You can use the debug option to get a log file with information about the the certificate
chain. Additionally certificates in the certificate chain are stored in the log folder (.cer files). This
can help you, for example, if you have issues with the Root Authority Trusted channel of this
sensor.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
15.04.2016

2231

Inherited Settings
described below.
2232
15.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.04.2016
2233


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2234
15.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.04.2016
2235

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
2236
159
section.
15.04.2016

189 SSL Security Check Sensor
6.8.189 SSL Security Check Sensor

The SSL Security Check sensor monitors the Secure Sockets Layer (SSL) connectivity to the
port of a device. It tries connecting to the specified TCP/IP port number of a device with
various SSL/TLS protocol versions and shows if a particular protocol is supported.
The sensor checks connectivity with the following protocols in particular channels 92 with the
possible values Accept ed (sensor can connect with this protocol) or Denied (sensor cannot
connect with this protocol):
SSL 2.0: weak security (warning if accepted, up if denied)
SSL 3.0: weak security (warning if accepted, up if denied)
TLS 1.0: strong security (up if accepted, otherwise gray)
TLS 1.1: strong security (up if accepted, otherwise gray)
TLS 1.2: perfect security (up if accepted, otherwise gray)
The default primary channel Securit y Rat ing shows the connection security to the defined
port with one of the following states 135 :
Down: There is no secure protocol available. The sensor cannot connect with one of the
given protocols.
Warning (weak): The sensor can connect with at least one of the weak protocols SSL 2.0 or
3.0.
Up (strong): The sensor can connect with a strong protocol only (TLS 1.0, TLS 1.1, TLS 1.2).
Connecting with a weak protocol is not possible.
15.03.2016
2237

SSL Sec urity Chec k Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/ssl_sec urity _c hec k.png
Remarks
Add Sensor
later.
Settings
2238
15.03.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SSL SECU R ITY

SPECIFIC
Timeout (Sec.)

Port
Enter the number of the port to which this sensor connects. Please
enter an integer value. The default port is 443.
15.03.2016
2239

Virtual Host (SNI

Domain)
Enter a host name that the sensor will query. The sensor uses this
host to connect if the target server presents multiple certificates
on the same IP address and IP port when using Server Name
Identification (SNI).
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2240
15.03.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
15.03.2016
2241


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2242
15.03.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
15.03.2016
2243

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
2244
159
section.
15.03.2016

190 Syslog Receiver Sensor
6.8.190 Sy slog Receiver Sensor

The Syslog Receiver sensor receives and analyzes syslog messages.
Number of received syslog messages per second
Number of messages categorized as "warning" per second
Number of messages categorized as "error" per second
Number of dropped packets per second
Sy slog Rec eiv er Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sy slog_rec eiv er.png
Remarks
With the available filter options, you can define individually which types of messages the
sensor will consider for monitoring, and which messages it will categorize as warning or
error messages. Depending on the filters, received messages are counted in the respective
channels.
Add the sensor to the probe device to receive all messages of the system running the
probe.
Add the sensor to a specific device to receive all messages from this device directly. This
makes this sensor type faster than just using source filters.
21.01.2016
2245

You can use syslog specific placeholders in email notification templates 2840 to see the
messages when you receive an email notification. See the Knowledge Base: What
placeholders can I use with PRTG?
Note: If you do not add the sensor to a probe device but to another device in PRTG, be
careful with the configuration: Ensure that the IP address or DNS name of the parent device
matches the proper syslog sender. For example, if you want to receive syslogs from a
Storage Area Network (SAN), you might have to add a device to PRTG using the IP address of
a specific array member that sends the messages. Providing a DNS name that points to the IP
address of a whole group might not work for SANs.
For a general introduction to the syslog receiver's configuration, please see manual section
Monit oring Sy slogs and SNMP Traps 3038 .
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
2246
21.01.2016


Tags

default value.
Priority
SYSLOG SPECIFIC
Listen on Port
Enter the number of the port on which the sensor waits for Syslog
messages. The default port is 514. Please enter an integer value.
Purge Messages After
Define how long PRTG stores received Syslog messages for

analysis. Choose a period of time from the drop down list.
FILTER
Include Filter
Define if you want to filter Syslog messages. If you leave this field
empty or use the keyword "any", the sensor will process all data.
To include specific types of messages only, define filters using a
Exclude Filter
Define which types of Syslog messages the sensor will discard and
not process. To exclude specific types of messages, define filters
using a special syntax. For more information, see section Filt er
Rules 2254 .
Warning Filter
Define which types of Syslog messages count for the Warnings

channel. To categorize received messages as warning messages,
define filters using a special syntax. For more information, see
section Filt er Rules 2254 .
21.01.2016
2247

FILTER
Note: Messages are collected until a scanning interval ends. as
happen. By default, the sensor will turn into a Warning status after
a scanning interval has finished and there was at least one warning
message (and no error message) during this interval. The status will
remain Warning at least until the succeeding scanning interval has
finished. If in this scanning interval no warning or error message
occurred, the status of the sensor will turn Up again after the
interval.
Error Filter
Define which types of syslog messages will count for the Errors
channel. To categorize received messages as error messages,
define filters using a special syntax. For more information, see
section Filt er Rules 2254 .
happen. By default, the sensor will turn into a Down status after a
scanning interval has finished and there was at least one error
message during this interval. The status will remain Down at least
until the succeeding scanning interval has finished. If the sensor
did not receive any warning or error message in this scanning
interval, the status of the sensor will turn Up again after the
interval.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2248
21.01.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
21.01.2016
2249

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2250
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2251


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2252
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
2253

DEBU GGING
Log Data to Disk
Define if the probe will write a log file of the received data to the
data folder (see Dat a St orage 3135 ) to the disk for debugging
purposes. Choose between:
Off (recommended): Do not write additional log files.
On: Write log files for all data received.
only.
Filter Rules for Syslog Messages

Filter rules are used for the include, exclude, warning, and error definition fields of the Syslog
Receiver sensor. They are based on the following format:
field[filter]
You can use various filters suitable to your needs. Include and exclude filters define which
messages to monitor. Warning and error filters define how to categorize received messages.
Provide these filters in the sensor settings as formulas. Formulas are fields which you can
combine with boolean operators (AND, OR, NOT) and brackets.
Field
Paramet er
Example
source[ip]
the IP address where the messages will be

received from; masks and ranges are also
possible
source[10.0.23.50]
source[10.0.23.10-50]
source[10.0.23.10/255]
facilit y
[number]
any number or range from 0 to 23 specifying

the type of program sending the message
facility[2]
facility[5-7]
facility[5] OR facility[6]
severit y
[number]
any number or range from 0 (emergency) to 7

(debug) specifying the type of message
severity[4]
severity[1-3]
severity[1] AND severity
[2]
2254
21.01.2016

host name
[text]
any string specifying the hostname of a device

in the message
hostname
[www.example.com]
t ag[text]
any string specifying the tag of a program or

process in the message
tag[su]
appname
[text]
any string specifying the appname part of the

message
appname[myproc]
procid
[text]
any string specifying the process identifier part

of the message
procid[1860]
msgid[text] any string specifying the message identifier part

of the message
message
[parttext]
any string specifying the message part of the

message (substring will match; case insensitive!)
appname[demo] AND
msgid[m42]
msgid[ID47]
message[Error]
dat a
checks the SD-ID block of the message's
[id
structured data for a parameter matching the
,param,value] given value
data
[exampleSDID@12345,ev
entSource,Application]
dat a
[parttext]
checks if the given substring matches on

structured data as displayed in the
corresponding table
data
[exampleSDID@1234]
dat a
[id,param]
checks if the parameter exists in the given ID

element
data
[exampleSDID@1234,eve
ntSource]
Note: String parameters (except the substring in message) have to match exactly the particular
parts of the message. They are case sensitive!
Messages Tab: Review and Analyze Syslog Messages

PRTG stores received Syslog messages as common files in the data folder (see section Dat a
St orage 3135 ). To review and analyze all received messages, you can access the most recent
data directly in a table list 178 in the PRTG web interface. You can access this list via the
Overview tab of the sensors.
Note: Received syslogs are only shown after an (automatic) page refresh following to a sensor
scan in the table on the Overview tab (default for auto refresh 2830 is 30 seconds).
For more details and further filter options, click the Messages tab of the Syslog Receiver
sensor. You will see all received messages in a table list 178 . On the top, you have display filter
options to drill down into the data for specific events of your interest. The filters are the same
as available in the sensor settings, but you can define them without using formulas. Provide
the desired parameters and PRTG loads the filtered list automatically.
Note: You can automatically add a filter by clicking the content of a column.
21.01.2016
2255

Advanced Filt er Set t ings

You can open advanced filter settings by clicking the gear icon in the Filt er row. The
Advanced Filt er will appear in a popup window. In the text field, you can define a filter using
the syntax as given in section Filt er Rules for Sy slog Messages 2254 . If you have provided filter
parameters on the Messages tab, the advanced filter will already include them as a
corresponding formula with the correct syntax. You can adjust this filter to your needs. You
can also copy the automatically created and manually adjusted formula for usage in the filter
fields of the sensor settings.
More
Blog Article: Introducing the New High Performance Syslog and SNMP Trap Receiver Sensors
https://www.paessler.com/blog/2013/10/11/prtg/introducing-the-new-high-performancesyslog-and-snmp-trap-receiver-sensors

Notifications
Others
2256
159
section.
21.01.2016

191 System Health Sensor
6.8.191 Sy stem Health Sensor

The System Health sensor monitors internal PRTG parameters. It shows the status of the
system on which a probe runs. PRTG creates this sensor type automatically and cannot be
deleted.
It checks various parameters of your PRTG system which can affect the quality of the
monitoring results:
Healt h: This index value sums up the probe state into a value between 100% (healthy) and
0% (failing). Frequent or repeated health values below 100% should be investigated.
Available Memory : This channel shows the amount of free memory available on the system.
This value should not fall below 500 MB. This way PRTG still can request resources during
report generation, auto-discoveries, and other issues.
Available Memory Percent : This channel shows the free memory available on the system in
percent.
Sy st em CPU Load: This channel shows the current percentage CPU load on the system with
the probe. Extensive CPU load can lead to false, incomplete, and incorrect monitoring
results. This value usually should stay below 50%.
Sy stem Health Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/sy stem_health.png
Sensor Settings
24.03.2015
2257


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2258
24.03.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
24.03.2015
2259

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2260
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
2261


Notifications
Others
2262
159
section.
24.03.2015

192 TFTP Sensor
6.8.192 TFTP Sensor

The TFTP sensor monitors a Trivial File Transfer Protocol (TFTP) server and checks if a certain file
is available for download.
TFTP Sensor
Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/tftp.png
Add Sensor
later.
Sensor Settings
24.03.2015
2263

192 TFTP Sensor

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SPECIFIC
Timeout (Sec.)

Port
Enter the number of the port the TFTP service is running on. The
sensor connects to this port. Please enter an integer value.
Filename
Enter the name of the file that this sensor checks. If this file name
is not available on the server, the sensor shows a Down status 135 .
2264
24.03.2015

192 TFTP Sensor
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2265

192 TFTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2266
24.03.2015

192 TFTP Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2267

192 TFTP Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2268
24.03.2015

192 TFTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
2269

192 TFTP Sensor

Notifications
Others
2270
159
section.
24.03.2015

193 Traceroute Hop Count Sensor
6.8.193 Traceroute Hop Count Sensor

The Traceroute Hop Count sensor traces the number of hops needed from the probe system
the sensor is running on to the IP Address/DNS Name defined in the sensor's parent device.
Execution time
Number of hops.
If the number of hops (the route) changes, you can additionally define another sensor status
135 .
Trac eroute Hop Count Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/trac eroute_hop_c ount.png
Remarks
Requires 2272 .NET 4.0 or 4.5 to be installed on the probe system. Note: If the sensor shows
the error PE087, please additionally install .NET 3.5 on the probe system.
09.07.2015
2271


this sensor.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
2272
09.07.2015


Priority
SENSOR SETTINGS
If Route Changes
Define what to do if the route has changed since the last check.
Choose between:
Ignore: Do not perform any action.
Set sensor t o "Warning": Set the sensor to Warning status.
Set sensor t o "Error": Set the sensor to Down status.
DEBU G OPTIONS
Sensor Result

between:
09.07.2015
2273

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2274
09.07.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
09.07.2015
2275


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2276
09.07.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
09.07.2015
2277

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2278
09.07.2015

Others
09.07.2015
159
section.
2279

194 VMware Datastore (SOAP) Sensor
6.8.194 VM ware Datastore (SOAP) Sensor

The VMware Datastore (SOAP) sensor monitors the disk usage of a VMware data store using
Simple Object Access Protocol (SOAP). It can show the following:
Available capacity in bytes: This is the physically or virtually available size of the data store.
Free space in bytes and percent: This is the disk space that is not used by virtual machines.
Used disk space can be either thick-provisioned or used from thin-provisioned virtual disks.
Uncommitted bytes: This is the disk space that is provisioned for thin-provisioned virtual
machines but not used yet.
Total provisioned disk space in percent: This is the sum of all potentially used disk space of
thin- and thick-provisioned VM hard drives (uncommitted bytes plus used bytes).
Accessibility of the data store

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_datastore_soap.png
Remarks
Requires
2281
.NET 4.0 or higher to be installed on the probe system.
For this sensor type you must define credentials for VMware servers on the device you want
to use the sensor on. Ensure you enter a user with sufficient access rights to obtain
statistics (read-only usually works).
The parent device must be a VMware ESXi server version 5.0, 5.1, 5.5, or 6.0 or vCenter.
2280
09.05.2016

Note: This sensor type supersedes the outdated SSH VMWare ESX(i) Disk sensor. We
recommend that you use this new sensor to monitor VMware data stores.
Knowledge Base: I cannot add VMware sensors because of "wrong" password although it is
correct. What can I do?

this sensor.
Settings on VMware Host System

If you set up this sensor on different probes (for example, when using remote probes 3109 or
when running a cluster 87 setup), you might need to change the settings of your VMware
host, so it accepts more incoming connections. Otherwise you might get connection timeouts
when running plenty of VMware sensors with a short scanning interval.
For details about this setting, please see More section below.
Add Sensor
later.
Select the data stores you want to monitor. PRTG creates one sensor for each data store you
09.05.2016
2281

DATASTOR E SETTINGS
Datastore
Select all data stores for which you want to add a sensor. You see
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
2282
09.05.2016

DATASTOR E SETTINGS
MoID
Shows the Managed Object ID (MoID) of the data store that this
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
09.05.2016
2283

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2284
09.05.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
09.05.2016
2285


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2286
09.05.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
09.05.2016
2287

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2288
09.05.2016

More
Knowledge Base: How can I increase the connection limit on VMware systems?
Knowledge Base: Monitoring ESXi 5.1 and higher: Handshake Failure on Windows XP/Server
2003
why?

Notifications
Others
09.05.2016
159
section.
2289

195 VMware Host Hardware (WBEM) Sensor
6.8.195 VM ware Host Hardware (WBEM ) Sensor

The VMware Host Hardware sensor monitors hardware information of a ESX/ESXi server using
Web-Based Enterprise Management (WBEM).
It can show the following, depending on the selected ESX component:
Health status
Temperature
Power
Fan rotations per minute (RPM)
Battery voltage
sensor setup.
VMWare Host Hardware (WBEM) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_host_hardware_wbem.png
Remarks
The parent device must be a VMware ESXi server version 5.0, 5.1, 5.5, or 6.0.
2290
29.10.2015

Add Sensor
later.
Select the ESX components you want to monitor. PRTG creates one sensor for each hardware
element you choose in the Add Sensor dialog. The settings you choose in this dialog are valid
ESX SER VER ELEMENTS

ESX Element
Select the hardware elements you want to add a sensor for. You
see a list with the names of all items which are available to monitor.
table head.
Sensor Settings

Sensor Name
29.10.2015

171 .
2291


Parent Tags
Tags

default value.
Priority

Element
Shows the ESX element that this sensor monitors. Once a sensor
anew.
Automatic Sensor
State
Define if the sensor will change its status dependent on the health
state reading. Choose between:
Set sensor st at e aut omat ically t o 'Warning' or 'Down': Set
the sensor to a Warning or Down status when the server
returns respective values. The sensor will additionally change to
a Down status if the connection to the server fails.
Just report t he current reading, ignore Server Healt h Value:
Never change the sensor's status dependent on the values
returned by the server. The sensor will only change to a Down
status if the connection to the server fails.
Sensor Result

between:
2292
29.10.2015


SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
29.10.2015
2293

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2294
29.10.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
29.10.2015
2295


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2296
29.10.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Notifications
Others
29.10.2015
159
section.
2297

196 VMware Host Hardware Status (SOAP) Sensor
6.8.196 VM ware Host Hardware Status (SOAP) Sensor

The VMware Host Hardware Status (SOAP) sensor monitors the hardware status of a VMware
host server using Simple Object Access Protocol (SOAP).
It shows the total number of items in "Normal", "Warning," and "Alert" status, just as the
vSphere client reports.
This sensor is intended to give you a general status overview for your host. Any states other
than "Normal" will be reported in the sensor message.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_host_hardware_status_soap.png
Remarks
Requires
2299
This sensor only shows items that report an actual status, so you might see more "sensors"
in your vSphere client than the number of states available in the channels of this PRTG
sensor.
The parent device must be a VMware ESXi server version 5.0, 5.1, 5.5, or 6.0. We recommend
that you do not use this sensor type on your vCenter. Reliable hardware information can
only be provided when this sensor is created on your physical host server as parent device.
2298
29.10.2015


this sensor.

Add Sensor
later.
Select the VMware hosts you want to monitor. PRTG creates on sensor for each host server
VMWAR E HOST SETTINGS

Host Server
29.10.2015
Select the host server you want to add a sensor for. You see a list
head.
2299

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

MoID
2300
Shows the Managed Object ID (MoID) of the host that this sensor
29.10.2015


Known Warnings
Enter one or more semicolon (;) separated warning messages from

the VMware host that you want to ignore. Messages that you
enter here will not affect the sensor status. Please enter a string or
Note: We strongly recommend that you use this filter only for
known issues. For example, various systems (mainly HP and IBM
systems) return unknown states because of errors in the the
vendors' CIM extensions. Because of this you might not get an Up
status 135 for this sensor at all although your vSphere client does
not show warnings. In this case, use this filter option and enter the
known warning message(s), for example, Power Supply 7;Power
Supply 8
Known Errors
Enter one or more semicolon (;) separated error messages from

the VMware host that you want to ignore. Messages that you
enter here will not affect the sensor status. Please enter a string or
Note: We strongly recommend that you use this filter only for
known issues. For example, various systems (mainly HP and IBM
systems) return unknown states because of errors in the the
vendors' CIM extensions. Because of this you might not get an Up
status 135 for this sensor at all although your vSphere client does
not show errors. In this case, use this filter option and enter the
known error message(s), for example, Power Supply 7;Power
Supply 8
DEBU G OPTIONS
Sensor Result

between:
29.10.2015
2301

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2302
29.10.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
29.10.2015
2303


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2304
29.10.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
29.10.2015
2305

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
2003
why?
2306
29.10.2015


Notifications
Others
29.10.2015
159
section.
2307

197 VMware Host Performance (SOAP) Sensor
6.8.197 VM ware Host Performance (SOAP) Sensor

The VMware Host Performance (SOAP) sensor monitors a VMware host server using Simple
Object Access Protocol (SOAP).
CPU ready in percent
Network usage
Disk usage
Active memory in bytes
Consumed memory in bytes and percent
Used memory swap
Disk and data store latency (read and write)
Network received and transmitted speed
Power status
sensor setup.
2308
29.10.2015

VMware Host Performanc e (SOAP) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_host_performanc e_soap.png
Remarks
Requires
2310
29.10.2015
2309

The parent device must be a VMware ESXi server version 5.0, 5.1, 5.5, or 6.0. We recommend
that you do not use this sensor type on your vCenter. Reliable hardware information can
only be provided when this sensor is created on your physical host server as parent device.

this sensor.

Add Sensor
later.
Sensor Settings
2310
29.10.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

MoID
Shows the Managed Object ID (MoID) of the host that this sensor
DEBU G OPTIONS
Sensor Result

between:
29.10.2015
2311

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2312
29.10.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
29.10.2015
2313


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2314
29.10.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
29.10.2015
2315

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
2003
why?
2316
29.10.2015


Notifications
Others
29.10.2015
159
section.
2317

198 VMware Virtual Machine (SOAP) Sensor
6.8.198 VM ware Virtual M achine (SOAP) Sensor

The VMware Virtual Machine (SOAP) sensor monitors a virtual machine on a VMware host
server using Simple Object Access Protocol (SOAP).
CPU ready in percent
Active memory in bytes
Consumed memory in bytes and percent
Read and write latency
Network usage (total, received, and transmitted bytes per second)
sensor setup.
2318
21.01.2016

VMware Virtual Mac hine (SOAP) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/v mware_v irtual_mac hine_soap.png
Remarks
Requires
2320
We recommend that you use vCenter as parent device. When the monitored VM changes the
host server via vMotion, PRTG can continue monitoring in this case. The sensor can monitor
VMware ESXi server version 5.0, 5.1, 5.5, or 6.0.
21.01.2016
2319

Note: For VMware virtual machines, disk usage channels are only available as of virtual
hardware version 8.

this sensor.

Add Sensor
later.
Note: PRTG requests a full list of all virtual machines configured on the device. Because of this,
it may take a few seconds before the dialog is loaded.
Select the VMware virtual machines you want to monitor. PRTG creates one sensor for each
virtual machine you choose in the Add Sensor dialog. The settings you choose in this dialog
are valid for all of the sensors that are created.
2320
21.01.2016


Virtual Machine
You see a list of all virtual machines (VMs) available on the host
server on this device, including the ones that are not running. All
VMs are listed with name and the OS it is running on. Select the
lines. One sensor will be created for each selection. You can also
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
21.01.2016
2321

VMWAR E VIR TU AL MACHINE SETTINGS

MoID
Shows the Managed Object ID (MoID) of the virtual machine that

this sensor monitors. Once a sensor is created, you cannot change
this value. It is shown for reference purposes only. If you need to
Handling of "Powered
off" VM
Define how the sensor will react to a virtual machine that is

powered off. Choose between:
Ignore "powered off" st at e (default ): The sensor will not
change to a Down status 135 if the virtual machine is powered off.
It will report zero values instead.
Alarm when VM is "powered off": The sensor will change to a
Down 135 status if the virtual machine is powered off. Note: While
in Down status, a sensor does not record any data in all of its
channels.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel
2322

21.01.2016

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
2323

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2324
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2325


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2326
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
2003
why?
21.01.2016
2327


Notifications
Others
2328
159
section.
21.01.2016

199 Windows CPU Load Sensor
6.8.199 Windows CPU Load Sensor

The Windows CPU Load sensor monitors the CPU load on a computer via Windows
It shows the CPU usage of all processors and the total load in percent.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_c pu_load.png
Remarks
Requires
2330
Windows credentials in the parent device settings
Requires
2330
Windows 2008 or later on the probe system.
Requires
2330
324
Uses a hybrid approach 2330 to query monitoring data: Performance counters as standard
approach and WMI as fallback.
21.01.2016
2329


section.
3005


remote probe 3109 .

work.
Type to Automatic.
2330
21.01.2016

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
21.01.2016
2331

DEBU G OPTIONS
Sensor Result

between:
WMI ALTER NATIVE QU ER Y

Errors and Invalid Data
This is an extended help field only. PRTG's WMI sensors are

equipped with the most efficient and accurate WMI queries.
However, Microsoft has changed (and will continue to do that in
the future) some WMI classes over the various Windows/
ServicePack/patchlevel versions, resulting in errors like "class not
valid" or "invalid data". Wherever possible, PRTG features an
alternative query that might work in your specific configuration.
When you keep getting errors for this sensor, please try enabling
the alternative query method below.
Alternative Query
Choose the method PRTG uses to query via WMI. For compatibility
reasons, you can enable an alternative query method. We
recommend that you use the default value. You can choose
between:
Use default (recommended): Use PRTG's standard method to
query WMI. This is the best setting in most cases.
Use alt ernat ive (if default does not work): Use an alternative
method to query WMI. If you keep getting errors with the default
setting, please try this setting.
2332
21.01.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
2333

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2334
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2335


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2336
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
2337

More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?

Notifications
Others
2338
159
section.
21.01.2016

200 Windows IIS 6.0 SMTP Received Sensor
6.8.200 Windows IIS 6.0 SM TP Received Sensor

The Windows IIS 6.0 SMTP Receiver Sensor monitors Microsoft's Internet Information Services
regarding the number of received emails for an IIS 6.0 SMTP service (Exchange 2003) using
Windows Performance Counters or Windows Management Instrumentation (WMI), as configured
in the "Windows Compatibility Options" of the parent device.
It shows the number and bytes of received messages.
Remarks
Requires
2339
Requires
2340
Requires
2340
324
This service is not used by Exchange Server 2007 and higher. Exchange Server 2007 uses its
own SMTP stack implemented in the Microsoft Exchange Transport service.

section.
3005

24.03.2015
2339


remote probe 3109 .

work.
Type to Automatic.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
2340
24.03.2015


Tags

default value.
Priority
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type
24.03.2015
2341

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
2342
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2343


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2344
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2345

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2346
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
2347

201 Windows IIS 6.0 SMTP Sent Sensor
6.8.201 Windows IIS 6.0 SM TP Sent Sensor

The Windows IIS 6.0 SMTP Sent Sensor monitors Microsoft's Internet Information Services
regarding the number of sent emails for an IIS 6.0 SMTP service (Exchange 2003) using
Windows Performance Counters or Windows Management Instrumentation (WMI), as configured
in the "Windows Compatibility Options" of the parent device.
Number and bytes of sent messages
Number of retries per second for sent messages
Remarks
Requires
2348
Requires
2349
Requires
2349
324
This service is not used by Exchange Server 2007 and higher. Exchange Server 2007 uses its
own SMTP stack implemented in the Microsoft Exchange Transport service.

section.
3005

2348
24.03.2015


remote probe 3109 .

work.
Type to Automatic.
Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
24.03.2015
2349


Tags

default value.
Priority
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type
2350
24.03.2015

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2351

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2352
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2353


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2354
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
24.03.2015
2355

More

Notifications
Others
2356
159
section.
24.03.2015

202 Windows IIS Application Sensor
6.8.202 Windows IIS Application Sensor

The Windows IIS Application sensor monitors a Microsoft Internet Information Services server
using Windows Performance Counters or Windows Management Instrumentation (WMI), as
configured in the "Windows Compatibility Options" of the parent device. It can also monitor
applications that use IIS, such as Microsoft SharePoint or Microsoft Reporting Services (SSRS).
Sent and received bytes per second
Number of sent and received files per second
Number of anonymous and known users per second
Number of Common Gateway Interface (CGI) requests per second
Number of GET and POST requests per second
Number of not found errors per second
Windows IIS Applic ation Sensor
21.01.2016
2357

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_iis_applic ation.png
Remarks
Requires
2358
Requires
2358
Requires
2359
324

section.
3005


remote probe 3109 .
2358
21.01.2016


work.
Type to Automatic.
Add Sensor
later.
Select the web service instances you want to monitor. PRTG creates one sensor for each
WMI INTER NET INFOR MATION SER VICES

Specify Instance
in the table head.
Sensor Settings
21.01.2016
2359


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
WMI INTER NET INFOR MATION SER VICES

Instance
Shows the name of the web service instance that this sensor
DEBU G OPTIONS
Sensor Result

between:
2360
21.01.2016

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
2361

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2362
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2363


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2364
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
2365

More

Notifications
Others
2366
159
section.
21.01.2016

203 Windows MSMQ Queue Length Sensor
6.8.203 Windows M SM Q Queue Length Sensor

The Windows MSMQ Queue Length sensor reads the number of messages in a Microsoft
Message Queue of the parent device.
Total number of messages in the queue
Execution time

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_msmq_queue_length.png
Remarks
Requires 2368 .NET 4.0 or 4.5 to be installed on the probe system. Note: If the sensor shows
the error PE087, please additionally install .NET 3.5 on the probe system.
Requires
2368
Requires
2368
the MSMQ service to be running on both the probe and the target system.
324
Knowledge Base: How do I activate Message Queuing in my Windows installation?
09.07.2015
2367


this sensor.

Requirement: Message Queuing Service

In order for this sensor to work, the MSMQ "Message Queuing" service must be started both
on the target system and on the computer running the PRTG probe: Either on the local system
(on every node, if on a cluster probe), or on the system running the remote probe 3109 .
Additionally, the MSMQ "Message Queuing" service must also be started on the target
computer.
Type to Automatic.
Depending on your Windows version you may first need to install the Microsoft Message
Queue (MSMQ) Server.
Note: When installing Microsoft Message Queue (MSMQ) Server, make sure you install it
including the Directory Service. Depending on your Windows installation this might have
different names, such as
MSMQ Active Directory Domain Service Integration
Directory Service Integration
Active Directory Integration
For details, please see More
2368
2376
section below.
09.07.2015

Add Sensor
later.
Select the message queues you want to monitor. PRTG creates one sensor for each queue
SENSOR SETTINGS
Message Queue
in the table head. If there are no message queues available, you will
see a corresponding message.
Note: This sensor cannot monitor sub-queues.
Sensor Settings

Sensor Name

171 .
Parent Tags
09.07.2015
2369


Tags

default value.
Priority
SENSOR SETTINGS
Message Queue
Shows the name of the queue that this sensor monitors. Once a
the sensor anew.
Message Queue Type
Shows the type of the queue that this sensor monitors. Once a
the sensor anew.
Min. Message Age
Optionally define an age in minutes the message has to be old to

be counted. If set, messages younger than this age are not
regarded. If you leave this field blank, the sensor will not check for
the message age. Please enter an integer value or leave the field
empty.
If Value Changes
change.
2370
09.07.2015

DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
09.07.2015

2371

Inherited Settings
described below.
2372
09.07.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
09.07.2015
2373


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2374
09.07.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
09.07.2015
2375

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: How do I activate Message Queuing in my Windows installation?

2376
09.07.2015

Notifications
Others
09.07.2015
159
section.
2377

204 Windows Network Card Sensor
6.8.204 Windows Network Card Sensor

The Windows Network Card sensor monitors bandwidth usage and traffic of a network
interface using Windows Performance Counters or Windows Management Instrumentation
(WMI), as configured in the "Windows Compatibility Options" of the parent device.
Total traffic on the network card
Traffic in and traffic out
Number of packets per second.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_network_c ard.png
Remarks
This sensor type supports teamed network adapters ("NIC teaming") on Windows Server
2012.
Requires
2379
Requires
2379
Requires
2379
324
2378
21.01.2016


section.
3005


remote probe 3109 .

work.
Type to Automatic.
21.01.2016
2379

Add Sensor
later.
Select the network cards you want to monitor PRTG creates one sensor for each interface you
SENSOR SPECIFIC
Network Interface
Select the network card(s) you want to add a sensor for. You see a
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
2380
21.01.2016


Tags

default value.
Priority
SENSOR SPECIFIC
Selected Interface
Shows the name of the network card that this sensor monitors.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
21.01.2016
2381

SENSOR DISPLAY
Stack Unit

DEBU G OPTIONS
Sensor Result

between:
2382
21.01.2016

Inherited Settings
described below.
21.01.2016
2383

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2384
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2385


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2386
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
2387

More

Notifications
Others
2388
159
section.
21.01.2016

205 Windows Pagefile Sensor
6.8.205 Windows Pagefile Sensor

The Windows Pagefile sensor monitors the Windows pagefile usage via Windows Performance
Counters or Windows Management Instrumentation (WMI), as configured in the "Windows
Compatibility Options" of the parent device.
It shows the pagefile usage in percent.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_pagefile.png
Remarks
Note: This sensor does not work with Windows 2000, because the respective WMI class
does not exist on this operating system!
Requires
2390
Requires
2390
Requires
2390
324

21.01.2016
2389

section.
3005


remote probe 3109 .

work.
Type to Automatic.
Add Sensor
later.
Sensor Settings
2390
21.01.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
DEBU G OPTIONS
Sensor Result

between:
21.01.2016
2391

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2392
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2393


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2394
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2395

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2396
21.01.2016

Others
21.01.2016
159
section.
2397

206 Windows Physical Disk I/O Sensor
6.8.206 Windows Phy sical Disk I/O Sensor

The Windows Physical Disk I/O sensor monitors the input/output parameters of a hard disk in a
windows environment via Windows Performance Counters or Windows Management
device.
Disk Latency
Disk Bandwidth
Disk Queue data
DIsk IOs
sensor setup.
2398
27.04.2016

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/Windows_Phy sic al_Disk_IO_Sensor.png
Remarks
Requires
2399
Requires
2399
Requires
2400
324

section.
3005


remote probe 3109 .
27.04.2016
2399


work.
Type to Automatic.
Add Sensor
later.
Select the physical disk(s) you want to monitor. PRTG creates one sensor for each disk you
WINDOWS PHYSICAL DISK SPECIFIC

Physical Disk(s)
Select the disk(s) you want to monitor.

in the table head.
Sensor Settings
2400
27.04.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
WINDOWS PHYSICAL DISK SPECIFIC

Physical Disk(s)
Shows the disk this sensor monitors.

DEBU G OPTIONS
Sensor Result

between:
27.04.2016
2401

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2402
27.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
27.04.2016
2403


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2404
27.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
27.04.2016
2405

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2406
27.04.2016

More

Notifications
Others
27.04.2016
159
section.
2407

207 Windows Print Queue Sensor
6.8.207 Windows Print Queue Sensor

The Windows Print Queue sensor reads the print queue on its parent device and returns the
number of jobs in the print queue. It can monitor queues for all printers that are installed
locally. For example, you can use this sensor to monitor all print queues on your Windows
print server and retrieve information about all available jobs which are longer in the queue than
defined.
Number of jobs in the queue
Execution time
Additionally, this sensor can change to a defined status if there is a printer problem. See
section Sensor Set t ings 2410 for available parameters.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_print_queue.png
Remarks
Requires 2409 .NET 4.0 or higher to be installed on the probe system. Note: If the sensor
shows the error PE087, please additionally install .NET 3.5 on the probe system.
Requires
2409
Requires
2409
the Print Spooler Windows service to be running on the target device.
324
You can add a 'change' trigger
jobs in the queue changes.
2408
2840
to this sensor to get a notification when the number of
21.01.2016


this sensor.

Requirement: Print Spooler Service

In order for this sensor to work, the Spooler "Print Spooler" service must be started on the
target computer.
Type to Automatic.
Add Sensor
later.
Select the print queues you want to monitor. PRTG creates one sensor for each task you
21.01.2016
2409

SENSOR SETTINGS
Print Queue
in the table head. If there are no print queues available, you see a
corresponding message.
Note: If a printer name changes after you created a sensor for its
queue, please add the sensor anew.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
2410
21.01.2016

SENSOR SETTINGS
Print Queue
Shows the name of the task that this sensor monitors. Once a
the sensor anew.
Advanced Status
Option
You can optionally define specific Sensor St at es 135 for several

return messages of the monitored printer. Choose between:
Hide: Do not define sensor states for specific return messages.
Show: If you choose this option, you can define sensor states
for various messages which the monitored printer reports.
Door Open
Manual Feed Required
These settings are only available if you select the advanced status
option above. For each reported problem of the monitored printer,
you can define the status which the sensor shows. Choose
between:
Needs User
Intervention
Ignore: The sensor remains in the current status if this message

is reported by the printer.
Offline
Warning: The sensor shows the Warning status if this message

is reported by the printer.
Out of Memory
Error: The sensor shows a Down status if this message is

reported by the printer.
Out of Paper
Paper Jammed
Paper Problem
Paused
Printer Error
Printer Not Available
Toner Low
Toner Out
21.01.2016
2411

SENSOR SETTINGS
Min. Print Job Age
(Sec.)
Optionally define the age of the print job in seconds. If set, jobs
younger than this value are not regarded. If you leave this field
blank, the sensor will not check for the print job age. Please enter
an integer value or leave the field empty.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2412
21.01.2016

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
21.01.2016
2413

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2414
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2415


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2416
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
21.01.2016
2417

Others
2418
159
section.
21.01.2016

208 Windows Process Sensor
6.8.208 Windows Process Sensor

The Windows Process sensor monitors a Windows process using Windows Performance
Counters or Windows Management Instrumentation (WMI), as configured in the "Windows
Compatibility Options" of the parent device.
It shows the following parameters about the process:
Absolute working set in bytes
Private bytes
Number of threads
Number of handles
Number of instances
Average CPU usage (if there are multiple instances running)
Total CPU usage
For the "total CPU usage" value of a process, all CPU usage values are summed up. The total is
divided by the number of all CPUs and the maximum value is 100%. This corresponds to the CPU
usage of all instances of this specific process. Regarding the "per instance" value, the summed
up CPU usage value is divided by the number of all instances. It shows the average CPU usage
of a single instance of the process on one CPU.
Windows Proc ess Sensor
21.01.2016
2419

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_proc ess.png
Remarks
Requires
2421
Requires
2421
Requires
2421
324
Does not support 64-bit processes 2420 on devices with the address "localhost", "127.0.0.1",
"::1". Use the IP address in the network instead.
Note: This sensor cannot show values above 4 GB for 64-bit processes if you run the probe
on a 64-bit Windows system. Please add this sensor to a probe running on a 32-bit Windows
to monitor 64-bit processes.
Monitoring 64-bit Processes

This sensor type does not support 64-bit processes on devices with the address localhost ,
127.0.0.1 (IPv4 address), or ::1 (IPv6 address) in PRTG. This is the case for probe devices, for
example. The sensor works on all other target devices in your network. So if you want to
monitor 64-bit processes on your local machine, add this device 244 to PRTG with one of the IP
addresses under which it is reachable in the local network (for example, 10.0.10.20 instead of
127.0.0.1) and create the sensor on this device.
Note: This sensor type cannot show values above 4 GB for 64-bit processes if you run the
PRTG probe with this sensor on a 64-bit Windows system. The WoW64 (Windows 32-bit on
Windows 64-bit) emulation layer for 32-bit applications like PRTG limits monitoring values from
64-bit systems or processes to 4 GB and caps off greater values. To avoid this issue that is
caused by Windows and to correctly monitor 64-bit processes, please add this sensor to a
probe that runs on a 32-bit Windows system.

section.
2420
3005
21.01.2016



remote probe 3109 .

work.
Type to Automatic.
Add Sensor
later.
Sensor Settings
21.01.2016
2421


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
WINDOWS PR OCESS MONITOR

Executable
Enter the name of the process that you want to monitor. Provide
the name of an executable file without the .exe extension (for
example, enter firefox to monitor firefox.exe). The sensor goes
into a Down status if the process is not active on the device.
DEBU G OPTIONS
Sensor Result

between:
2422
21.01.2016

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
2423

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2424
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2425


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2426
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
2427

More

Notifications
Others
2428
159
section.
21.01.2016

209 Windows System Uptime Sensor
6.8.209 Windows Sy stem Uptime Sensor

The Windows System Uptime sensor monitors uptime of a Windows system using Windows
It shows the total uptime of the system in days, hours, minutes.
Windows Sy stem Uptime Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_sy stem_uptime.png
Remarks
Requires
2430
Requires
2430
Requires
2430
324

21.01.2016
2429

section.
3005


remote probe 3109 .

work.
Type to Automatic.
Add Sensor
later.
Sensor Settings
2430
21.01.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
DEBU G OPTIONS
Sensor Result

between:
21.01.2016
2431

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2432
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2433


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2434
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2435

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2436
21.01.2016

Others
21.01.2016
159
section.
2437

210 Windows Updates Status (Powershell) Sensor
6.8.210 Windows Updates Status (Powershell) Sensor

The Windows Updates Status (Powershell) sensor monitors the status of Windows updates on
a computer and counts the available and installed Windows updateseither from Microsoft or
from the local Windows Server Update Services (WSUS) server.
Elapsed time since the last update
Installed Windows updates
Missing Windows updates
Installed security updates with low, moderate, important, and critical priority
Missing security updates with low, moderate, important, and critical priority
You can find the considered updates in Server Manager (WSUS) under Roles | Windows Server
Updat e Services | Updat e Services | Comput ers | Report s.
2438
22.01.2016

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/windows_updates_status_powershell.png
Remarks
Requires
2439
Requires 2439 Remote PowerShell to be enabled on the target system and PowerShell 2.0 on
the probe system.
sensor on.
The minimum scanning interval for this sensor is 1 hour.
Note: If the sensor cannot determine the "Time since last update" (for example, because the
list of updates is empty), it will show the value -1s and turn into a Warning status 135 .
Note: We recommend that you set the scanning interval
hours to limit the load on the server being monitored.
2442
of this sensor to at least 12

this sensor.
Requirement: Remote PowerShell

The Windows Updates Status (Powershell) sensor uses PowerShell commands. To monitor
devices with this sensor, Remot e PowerShell access has to be enabled on the target
computer. Also ensure that you have installed PowerShell 2.0 or later on your probe machine.
For detailed information, please see More
22.01.2016
939
section below.
2439

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SPECIFIC
2440
22.01.2016

Port
Enter the number of the port to which this sensor connects. Please
enter an integer value. The default port is 5985.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
22.01.2016
2441

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2442
22.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
this sensor.
22.01.2016
2443


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2444
22.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
22.01.2016
2445

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
2446
22.01.2016


Notifications
Others
22.01.2016
159
section.
2447

211 WMI Custom Sensor
6.8.211 WM I Custom Sensor

The WMI Custom Sensor performs a custom query via Windows Management Instrumentation
(WMI).
It shows the retrieved value.
Note: Your Windows Management Instrumentation Query Language (WQL) query code must be
stored in a file on the system of the probe the sensor is created on: If used on a remote
probe, the file must be stored on the system running the remote probe. In a cluster setup,
please copy the file to every cluster node.
Save the file with the query into the \Cust om Sensors\WMI WQL script s subfolder of your
PRTG installation. See the section Dat a St orage 3135 for more information about how to find
this path.
WMI Custom Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_c ustom.png
Remarks
sensor on.
Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high
impact on the system performance! Try to stay below 200 WMI sensors per probe 83 . Above
this number, please consider using multiple Remot e Probes 3109 for load balancing.
For a general introduction to the technology behind WMI, please see manual section
2448
21.01.2016

Add Sensor
later.
CU STOM QU ER Y SPECIFIC
Channel Name
Enter a name for the channel in which PRTG shows the received
data. This name will be displayed in graphs and tables. Please enter
a string. You can change the name later in the sensor's channel
settings 2711 .
WQL File
Select a file that this sensor will use from the list. The sensor
executes it with every scanning interval. The menu contains WQL
scripts from the \Cust om Sensors\WMI WQL script s subfolder of
your PRTG installation. Please store your script there.
If used on a remote probe, you must store the file on the system
running the remote probe. If used on a cluster probe, you must
store the file on all servers running a cluster node. For more
information on how to find this path, please see Dat a St orage 3135
section.
Note: Your query must return an integer or float value. Strings are
not supported!
Sensor Settings
21.01.2016
2449


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
Namespace
Enter the namespace for the query.
WQL File
Shows the WQL file that this sensor executes with every scanning
interval. Once a sensor is created, you cannot change this value. It
Placeholder <#PH1>
In your WQL script, you can use up to three placeholders that you
can assign a value to using this field. Please enter a string for
variable <#PH1> or leave the field empty.
Placeholder <#PH2>
Placeholder <#PH3>
2450
21.01.2016

If Value Changes
change.
Unit String
Enter a unit for the data that the sensor receives from your script.
This is for displaying purposes only. The unit will be displayed in
graphs and tables. Please enter a string.
Multiplication
Define a multiplier for the received values. By default, this is set to

1 in order to not change received values. Please enter an integer
value.
Division
Define a divisor for the received values. By default, this is set to 1

in order to not change received values. Please enter an integer
value.
DEBU G OPTIONS
Sensor Result

between:
21.01.2016
2451

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2452
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2453


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2454
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2455

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
2707
Knowledge Base: How do I properly configure a WMI Custom Sensor?

Knowledge Base: How do I create a WMI Custom Sensor?
Knowledge Base: Which WQL queries are used by PRTG's WMI sensors?
Knowledge Base: How can I monitor a Windows service on Windows 2000?
My WMI sensors don't work. What can I do?
2456
21.01.2016


Notifications
Others
21.01.2016
159
section.
2457

212 WMI Custom String Sensor
6.8.212 WM I Custom String Sensor

The WMI Custom String sensor performs a custom string query via Windows Management
Instrumentation (WMI).
It shows the retrieved string value in the sensor message.
It shows also the response time.
Note: Your Windows Management Instrumentation Query Language (WQL) query code must be
stored in a file on the system of the probe the sensor is created on: If used on a remote
probe, the file must be stored on the system running the remote probe. In a cluster setup,
please copy the file to every cluster node.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_c ustom_string.png
Remarks
sensor on.
2458
24.03.2015

Add Sensor
later.
Channel Name
Enter a name for the channel in which the received data will be
presented. The name will be displayed in graphs and tables. Please
enter a string. You can change the name later in the sensor's
channel settings 2711 .
WQL File
Select a file that will be used for this sensor from the drop down
menu. It will be executed with every scanning interval. The menu
contains WQL scripts from the \Cust om Sensors\WMI WQL
script s sub folder of your PRTG installation. Please store your
script there. If used on a remote probe, the file must be stored on
the system running the remote probe. If used on a cluster probe,
you must store the file on all servers running a cluster node! For
more information on how to find this path, please see Dat a
Sensor Settings

Sensor Name
24.03.2015

171 .
2459


Parent Tags
Tags

default value.
Priority
Namespace
Enter the namespace for the query.
WQL File
Shows the name of the file that this sensor uses. Once a sensor is
anew.
Placeholder <#PH1>
Placeholder <#PH2>
Placeholder <#PH3>
Unit String
Enter a unit for the data that will be received by your script. This is
for displaying purposes only. The unit will be displayed in graphs
and tables. Please enter a string.
2460
24.03.2015

If Value Changes
change.
Response Must Include Define which string must be part of the data that is received form
the WMI object. You can either enter plain text or a Regular
Expression 3105 . If the data does not include the search pattern, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
Response Must Not
Include
form the WMI object. You can either enter plain text or a Regular
Expression 3105 . If the data does include the search pattern, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
For Keyword Search

Use

the field above.
plain text search.
Expression 3105 .
Maximum Length of
String
Define the maximum allowed length of the string that will be

received from the WMI object. If it is longer than this value, the
sensor will be set to an error status. Please enter an integer value
Extract Number Using

Regular Expression
Define if you want to filter out a numeric value from the string
received from the WMI object. You can convert this into a float
value, in order to use it with channel limits (see Sensor Channels
Set t ings 2711 ).
No ext ract ion: Do not extract a float value. Use the result as a
string value.
24.03.2015
2461

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
2467 below.
Regular Expression
This setting is only visible if number extraction is enabled above.

Enter a Regular Expression 3105 to identify the numeric value you
want to extract from the string returned by the WMI object. You
can use capturing groups here. Make sure the expression returns
numbers only (including decimal and thousands separators). The
result will be further refined by the settings below.
Index of Capturing
Group
This setting is only visible if number extraction is enabled above. If

your regular expression uses capturing groups, specify which one
will be used to capture the number. Please enter an integer value
Decimal Separator

Define which character to use as decimal separator for the number
extracted above. Please enter a string or leave the field empty.
Thousands Separator

Define which character to use as thousands separator for the
empty.
Sensor Result

between:
2462
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2463

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2464
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2465


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2466
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

If you want to extract a number in the response string using a regular expression, please note
that the index for captures in this sensor is based on 1 (not on 0). Furthermore, capturing
groups are not created automatically. The example below will illustrate this issue.
Consider the following string as returned by a request for CPU usage:
5 Sec (3.49%), 1 Min (3.555%), 5 Min (3.90%)
Assuming you would like to filter for the number 3.555, i.e., the percentage in the second
parentheses. Then enter the following regex in the Regular Expression field:
(\d+\.\d+).*?(\d+\.\d+).*?(\d+\.\d+)
As Index of Capt uring Group enter 3. This will extract the desired number 3.555.
24.03.2015
2467

The index has to be 3 in this case because the capturing groups here are the following:
Group 1 contains "3.49%), 1 Min (3.555), 5 Min (3.90"
Please keep in mind this note about index and capturing groups when using number
extraction.
Note: It is not possible to match an empty string using PRTG's regex search with sensors.
More

Notifications
Others
2468
159
section.
24.03.2015

213 WMI Event Log Sensor
6.8.213 WM I Event Log Sensor

The WMI Event Log sensor monitors a specific Windows log file using Windows Management
It shows the number of new records per second.
You can set the sensor to a desired status individually according to a new event log entry. For
details and how to find out the correct filter, see section More 2478 .
WMI Ev ent Log Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_ev ent_log.png
Remarks
sensor on.
24.03.2015
2469

Add Sensor
later.
Select the log files you want to monitor. PRTG creates one sensor for each log you choose in
that are created.
WMI EVENT LOG MONITOR

Log File
The Windows event log provides several different log files. You see
table head.
Sensor Settings

Sensor Name

171 .
Parent Tags
2470
24.03.2015


Tags

default value.
Priority
WMI EVENT LOG MONITOR

Log File
Shows the Windows log file that this sensor monitors. Once a
the sensor anew.
Sensor Result

between:

Event Type
Specify the type of event that this sensor processes. Other event
type cannot be processed. Choose between the following event
types:
Any
24.03.2015
2471


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
Off: Do not filter by event source.
On: Enable filtering by event source.
Match String (Event

Source)
This field is only visible if you enable source filtering above. Enter a
source from which the events come from. Only events from a
source matching this string are regarded, other events are ignored.
Filter by ID
Filter all received events for a certain event ID. If you enable this
defined value(s). Choose between:
Off: Do not filter by event ID.
On: Enable filtering by event ID.
Match Value (Event ID)
This field is only visible if you enable ID filtering above. Enter an

event ID which the events must have. Only events with an ID that
matches this value are regarded.
Note: The Event Log (Windows API) Sensor 629 supports more
than one event ID. Using this sensor type, you can enter a comma
separated list of event IDs to filter for more than one ID.
Note: The WMI Event Log Sensor
one ID.
Filter by Category
2469
supports filtering for only
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.
2472
24.03.2015


Match String (Event
Category)
This field is only visible if you enable category filtering above. Enter
a category which the events must have. Only events with a
category that matches this string are regarded. Please enter a
string.
Filter by User
Filter all received events for a certain event user. If you enable this
Off: Do not filter by event user.
On: Enable filtering by event user.
Match String (Event

User)
This field is only visible if you enable user filtering above. Enter a
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

Computer)
This field is only visible if you enable computer filtering above.

Enter a computer name which the events must be assigned to.
Only events with a computer name that matches this string are
regarded. Please enter a string.
Filter by Message
Filter all received events for a certain event message. If you enable
Off: Do not filter by event message.
On: Enable filtering by event message.
Match String (Event

Message)
This field is only visible if you enable message filtering above. Enter
a message that the event must contain. Only events with a
message matching this string are regarded. Please enter a string.
Note: For the WMI Event Log Sensor, you can use the percent sign (%) as placeholder for any
or no character (as known from the asterisk sign (*) in Windows search) in combination with a
substring. For example, you can enter %RAS% for any event source containing the string RAS.
24.03.2015
2473

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2474
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2475


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2476
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2477

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

2478
24.03.2015

Notifications
Others
24.03.2015
159
section.
2479

214 WMI Exchange Server Sensor
6.8.214 WM I Exchange Server Sensor

The WMI Exchange Server sensor monitors a Microsoft Exchange Server 2003, 2007, 2010, or
2013 using Windows Management Instrumentation (WMI).
Queue size
Average delivery time
Logon operations per second
Sent, delivered, and submitted messages per second
Messages queued for submission
Remote Procedure Call (RPC) packets operations per second
RPC latency, requests, and slow packets
RPC sent, slow, outstanding, and failed requests (store interface)
Read and write bytes RPC clients per second
Number of active and anonymous users
Database page faults per second
Log record stalls per second
Log threads waiting
Database cache size in bytes and miss in percent
Current unique users (OWA)
Average response time (OWA)
sensor setup.
2480
24.03.2015

WMI Exc hange Serv er Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_exc hange_serv er.png
Remarks
sensor on.
Note: Existing former "WMI Exchange Server 2003/2007 Sensors" from previous PRTG versions
will continue to monitor your Exchange server in PRTG 9, but newly added Exchange server
sensors will be of the "WMI Exchange Server Sensor" type which is able to monitor Exchange
servers regardless of their version.
Add Sensor
later.
Select the performance counters of the Exchange server you want to monitor. PRTG creates
one sensor for each performance counter you choose in the Add Sensor dialog. The settings
you choose in this dialog are valid for all of the sensors that are created.
24.03.2015
2481

EXCHANGE SER VER DATA R EADINGS ACCESSIBLE U SING WMI

Performance Counter
in the table head.
The available options depend on your Exchange server
configuration. PRTG shows all possible performance counters with
name and instance description (if available).
You might be able to select aspects regarding:
SMTP Server: Queue Lengths
MSExchangeIS Mailbox: Queue Sizes, Delivery Times,
Operations, Messages
MSExchangeIS Public: Queue Sizes, Delivery Times, Operations,
Messages
MSExchangeIS: Packets, Operations, Clients, Latency, Requests,
Users
MS Exchange RPC Client Access: Active User Count, User
Count, Connection Count
MS Exchange OWA: Current Unique Users, Average Response
Time
Note: Depending on your Exchange server version, not all
counters might be available.
Sensor Settings
2482
24.03.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
R EADINGS ACCESSIBLE U SING WMI

Display Name
Instance
These fields show the parameters that are used to query data for
this sensor from the target device.Once a sensor is created, you
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
24.03.2015

between:
2483


SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2484
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2485


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2486
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2487

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2488
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
2489

215 WMI Exchange Transport Queue Sensor
6.8.215 WM I Exchange Transport Queue Sensor

The WMI Exchange Server sensor monitors the length of transport queues of a Microsoft
Exchange Server 2003, 2007, 2010, or 2013 using Windows Management Instrumentation
(WMI). It shows the same information as shown in Windows System Monitor ('perfmon'). See
section More 2499 below for an explanation of the transport queue types.
This sensor can show the following:
Active Mailbox Delivery Queue Length
Active Non-Smtp Delivery Queue Length
Active Remote Delivery Queue Length
Aggregate Delivery Queue Length (All Queues)
Aggregate Shadow Queue Length
Categorizer Job Availability
Items Completed Delivery Per Second
Items Completed Delivery Total
Items Deleted By Admin Total
Items Queued For Delivery Expired Total
Items Queued for Delivery Per Second
Items Queued For Delivery Total
Items Resubmitted Total
Largest Delivery Queue Length
Messages Completed Delivery Per Second
Messages Completed Delivery Total
Messages Completing Categorization
Messages Deferred Due To Local Loop
Messages Deferred during Categorization
Messages Queued For Delivery
Messages Queued for Delivery Per Second
Messages Queued For Delivery Total
Messages Submitted Per Second
Messages Submitted Total
Poison Queue Length
Retry Mailbox Delivery Queue Length
Retry Non-Smtp Delivery Queue Length
Retry Remote Delivery Queue Length
2490
21.01.2016

Shadow Queue Auto Discards Total

Submission Queue Items Expired Total
Submission Queue Length
Unreachable Queue Length
sensor setup.
WMI Exc hange Transport Queue Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_exc hange_transport_queue.png
Remarks
sensor on.
Add Sensor
later.
21.01.2016
2491

Select the transport queues you want to monitor. PRTG creates on sensor for each queue you
WMI EXCHANGE TR ANSPOR T QU EU E SPECIFIC

MSExchangeTransport
Queues
in the table head.
The available options depend on your Exchange server
configuration. PRTG shows all possible queues with name and
instance description (if available).
Note: For performance reasons, we recommend to only select
necessary items!
Sensor Settings

Sensor Name

171 .
Parent Tags
2492
21.01.2016


Tags

default value.
Priority

Display Name
Instance
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result

between:
21.01.2016
2493

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2494
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2495


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2496
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2497

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2498
21.01.2016

More

Notifications
Others
21.01.2016
159
section.
2499

216 WMI File Sensor
6.8.216 WM I File Sensor

The WMI File sensor monitors a file using Windows Management Instrumentation (WMI).
File size
Elapsed time since its last modification
WMI File Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_file.png
Remarks
sensor on.
Add Sensor
later.
2500
21.01.2016

216 WMI File Sensor
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
WMI FILE MONITOR

File Name
21.01.2016
Enter the name of the file that this sensor checks. Enter the full
local path. The file must exist on the computer your local or
remote probe is running on. UNC paths are not allowed here. For
example, when you create this sensor on a device under the local
probe, the file has to be accessible on the local system.
2501

216 WMI File Sensor
WMI FILE MONITOR

If Timestamp Changes
Define what to do when the timestamp of the file changes. You can
choose between:
change.
message indicating that the timestamp has changed. In
to trigger a notification 2719 whenever the timestamp changes.
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2502
21.01.2016

216 WMI File Sensor
SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
21.01.2016
2503

216 WMI File Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2504
21.01.2016

216 WMI File Sensor

Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2505

216 WMI File Sensor

menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2506
21.01.2016

216 WMI File Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
2507

216 WMI File Sensor
More

Notifications
Others
2508
159
section.
21.01.2016

217 WMI Free Disk Space (Multi Disk) Sensor
6.8.217 WM I Free Disk Space (M ulti Disk) Sensor

The WMI Free Disk Space (Multi Disk) sensor monitors the free disk space of one or multiple
drive(s) using Windows Management Instrumentation (WMI).
Free disk space in percent and bytes for each disk
Disk space of a system in total
This sensor monitors logical partitions of a hard or fixed disk drive. PRTG identifies logical disks
by their drive letter, such as C.
WMI Free Disk Spac e (Multi Disk) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_free_disk_spac e_multi_disk.png
Remarks
sensor on.
11.03.2016
2509

Add Sensor
later.
WMI DISK FR EE CONFIGU R ATION

Drive
From the drop down menu, select the drive(s) you want to
monitor. We recommend that you use the default value.
You can choose All to monitor all available drives, or you can
choose one specific drive letter to monitor this single drive only.
The data in the drop down menu may also contain drive letters that
do not exist on your device. The drive setting cannot be changed
once the sensor is created.
Sensor Settings

Sensor Name

171 .
Parent Tags
2510
11.03.2016


Tags

default value.
Priority
WMI DISK FR EE CONFIGU R ATION

Drive
Shows the drive(s) that this sensor monitors. This is either All or a
specific drive letter. Once a sensor is created, you cannot change
this value. It is shown for reference purposes only. If you need to

breached applies.
11.03.2016
2511


Upper Error Limit
the field empty.
Upper Warning Limit
the field empty.
Lower Warning Limit
the field empty.
Lower Error Limit
2512
the field empty.
11.03.2016


Size Limit Check
Choose between:
or overrun.
Upper Error Limit
empty.
Upper Warning Limit
field empty.
11.03.2016
2513


Lower Warning Limit
field empty.
Lower Error Limit
empty.
Alarm on Missing/
Removed Disk

DEBU G OPTIONS
Sensor Result

between:
2514
11.03.2016

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
11.03.2016
2515

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2516
11.03.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
11.03.2016
2517


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2518
11.03.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
11.03.2016
2519

More

Notifications
Others
2520
159
section.
11.03.2016

218 WMI HDD Health Sensor
6.8.218 WM I HDD Health Sensor

The WMI HDD Health sensor connects to the parent device via Windows Management
Instrumentation (WMI) and monitors the health of IDE disk drives on the target system, using
Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.). This is built into most modern
IDE hard disk drives.
It can show the following, among others:
Read Error Rate
Spin-Up Time
Start/Stop Count
Reallocated Sectors Count
Seek Error Rate
Power-On Hours
Spin Retry Count
Calibration Retry Count
Power Cycle Count
Power-off Retract Count
Load Cycle Count
Temperature Celsius
Reallocation Event Count
Current Pending Sector Count
Uncorrectable Sector Count
UltraDMA CRC Error Count
Write Error Rate
Transfer Error Rate
Total LBAs Written
Total LBAs Read
sensor setup. The channel names indicate the ID of the S.M.A.R.T. attribute, followed by a
colon, and the typical meaning of the channel. The sensor can also show other attributes that
the target device returns, but some channels will have the name Unknown Channel. This
happens if PRTG cannot match the ID of a found attribute with an internally defined channel
name.
Note: Some vendors do not agree on attribute definitions and define meanings other than the
common one.
21.01.2016
2521

Every attribute of a disk assumes a value. PRTG shows these attributes as channels with their
last, minimum, and maximum value. These channel values change over time and indicate the
disk healthhigher values correspond to a better health. The disk's attributes come with a
threshold, defined by the manufacturer of the drive. If a channel value is lower than this
threshold, the sensor is automatically set to a Warning status. This indicates that the SelfMonitoring, Analysis and Reporting Technology (S.M.A.R.T.) status of the HDD might break
soon.
Note: For some attributes are no thresholds defined and thus cannot be judged for a status
other than Up. You can Define Lookups 3095 and use them with affected channels to get the
desired status for a return value.
2522
21.01.2016


Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_hdd_health.png
Remarks
Note: This sensor officially requires Windows Vista or later running on the target machine
which holds the hard disk drives you want to monitor. The sensor may not work reliably
when the target machine runs on Windows 2003 or Windows XP. Due to a known bug in
those systems, the sensor may not be able to detect available hard disk drives.
21.01.2016
2523

sensor on.
Add Sensor
later.
Select the IDE disks you want to monitor. PRTG creates one sensor for each IDE device you
SMAR T SPECIFIC
IDE Devices
in the table head. . The items shown in the list are specific to the
parent device you create the sensor on.
Sensor Settings
2524
21.01.2016


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SMAR T SPECIFIC
Serial No.
Shows the serial number of the monitored disk. Once a sensor is

anew.
Size (GB)
Shows the size in Gigabyte of the monitored disk. Once a sensor

anew.
Name
Shows the name of the monitored disk. Once a sensor is created,

Timeout (Sec.)

21.01.2016
2525

DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
2526

21.01.2016

Inherited Settings
described below.
21.01.2016
2527

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2528
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2529


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2530
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
21.01.2016
2531

Others
2532
159
section.
21.01.2016

219 WMI Logical Disk I/O Sensor
6.8.219 WM I Logical Disk I/O Sensor

The WMI Logical Disk I/O sensor monitors the parameters of a logical disk belonging to a
windows device using Windows Management Instrumentation (WMI).
Free space
Disk latency
Disk bandwidth
Disk Queue data
Disk IOs
This sensor shows performance data from counters that monitor logical partitions of a hard
drive. The system monitor identifies logical disk instances by their identifier, such as C. The
sensor reads the logical disk object in the system monitor and returns the values.
sensor setup.
27.04.2016
2533

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/WMI_Logic al_Disk_IO_Sensor.png
Remarks
sensor on.
2534
27.04.2016

Add Sensor
later.
Select the logical disk(s) you want to monitor. PRTG creates one sensor for each counter you
WMI LOGICAL DISK I/O

SPECIFIC
Logical Disk(s)
Select the disk(s) you want to monitor.

You see a list with the names of all items which are
available to monitor. Select the desired items by adding
check marks in front of the respective lines. PRTG creates
one sensor for each selection. You can also select and
deselect all items by using the check box in the table
head.
Sensor Settings

Sensor Name
27.04.2016

171 .
2535


Parent Tags
Tags

default value.
Priority
WMI LOGICAL DISK I/O SPECIFIC

Logical Disk(s)
Shows the disk 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

between:
2536
27.04.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
27.04.2016
2537

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2538
27.04.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
27.04.2016
2539


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2540
27.04.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
27.04.2016
2541

More

Notifications
Others
2542
159
section.
27.04.2016

220 WMI Memory Sensor
6.8.220 WM I M emory Sensor

The WMI Memory sensor monitors available (free) system memory on Windows systems using
Windows Management Instrumentation (WMI).
It shows the available memory in percent and bytes.
WMI Memory Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_memory .png
Remarks
sensor on.
Add Sensor
later.
21.01.2016
2543

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
DEBU G OPTIONS
Sensor Result

between:
2544
21.01.2016

DEBU G OPTIONS
WMI ALTER NATIVE QU ER Y

Errors and Invalid Data
This is an extended help field only. PRTG's WMI sensors are

equipped with the most efficient and accurate WMI queries.
However, Microsoft has changed (and will continue to do that in
the future) some WMI classes over the various Windows/
ServicePack/patchlevel versions, resulting in errors like "class not
valid" or "invalid data". Wherever possible, PRTG features an
alternative query that might work in your specific configuration.
When you keep getting errors for this sensor, please try enabling
the alternative query method below.
Alternative Query
Choose the method PRTG uses to query via WMI. For compatibility
reasons, you can enable an alternative query method. We
recommend that you use the default value. You can choose
between:
Use default (recommended): Use PRTG's standard method to
query WMI. This is the best setting in most cases.
Use alt ernat ive (if default does not work): Use an alternative
method to query WMI. If you keep getting errors with the default
setting, please try this setting.
SENSOR DISPLAY
Primary Channel
21.01.2016

2545

SENSOR DISPLAY
Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2546
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2547


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2548
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2549

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2550
21.01.2016

More

Notifications
Others
21.01.2016
159
section.
2551

221 WMI Microsoft SQL Server 2005 Sensor (Deprecated)
6.8.221 WM I M icrosoft SQL Server 2005 Sensor (Deprecated)
IMPOR TANT NOTICE

This sensor type is deprecated.
Monitoring of Microsoft SQL Server 2005 using PRTG is discontinued. It cannot be
monitored with PRTG any more with the latest updates of SQL Server 2005. The reason for
this is a software update delivered by Microsoft in August 2012. The following updates
cause this issue:
Securit y Updat e for SQL Server 2005 Service Pack 4 (KB2716429)
Securit y Updat e for SQL Server 2005 Service Pack 4 (KB2716427)
We have made reasonable effort to fix this from our side but we were unable to. We do not
have instructions to circumvent this issue at this time. Please ask the vendor to fix this.
More
Knowledge Base: Why does my WMI Microsoft SQL Server 2005 Sensor not work anymore?
The WMI Microsoft SQL Server sensor monitors the performance of a Microsoft SQL server via
Windows Management Instrumentation (WMI). This sensor can monitor SQL General
St at ist ics, Access Met hods, the Buffer Manager, the Memory Manager, the Locks
Manager, and SQL St at ist ics. The channels that are actually available for a sensor depend on
which performance counters you choose during setup.
CHANNEL OVER VIEW

User Connections
Number of user connections. Because each user connection

consumes some memory, configuring overly high numbers of user
connections could affect throughput. Set user connections to the
maximum expected number of concurrent users.
Logins
Total number of logins started per second.
Logouts
Total number of logout operations started per second.
Full Scans
Number of unrestricted full scans per second. These can be either

base-table or full-index scans.
2552
24.03.2015

CHANNEL OVER VIEW

Page Splits
Number of page splits per second that occur as the result of

overflowing index pages.
Table Lock Escalations
Number of times locks on a table were escalated.
Buffer Cache Hit Ratio
Percentage of pages found in the buffer cache without having to

read from disk. The ratio is the total number of cache hits divided
by the total number of cache lookups since an instance of SQL
Server was started. After a long period of time, the ratio moves
very little. Because reading from the cache is much less expensive
than reading from disk, you want this ratio to be high. Generally,
you can increase the buffer cache hit ratio by increasing the
amount of memory available to SQL Server.
Database Pages
Number of pages in the buffer pool with database content.
Stolen Pages
Number of pages used for miscellaneous server purposes

(including procedure cache).
Page Life Expectancy
Number of seconds a page will stay in the buffer pool without

references.
Connection Memory
(KB)
Total amount of dynamic memory the server is using for

maintaining connections.
Optimizer Memory (KB)
Total amount of dynamic memory the server is using for query

optimization.
Total Server Memory

(KB)
Total amount of dynamic memory (in kilobytes) that the server is

using currently.
Target Server Memory

(KB)
Total amount of dynamic memory the server can consume.
SQL Cache Memory

(KB)
Total amount of dynamic memory the server is using for the

dynamic SQL cache.
Lock Requests
Number of new locks and lock conversions per second requested

from the lock manager.
Deadlocks
Number of lock requests per second that resulted in a deadlock.
Average Wait Time
Average amount of wait time (in milliseconds) for each lock request
that resulted in a wait.
24.03.2015
2553

CHANNEL OVER VIEW

Batch Requests
Number of Transact-SQL command batches received per second.

This statistic is affected by all constraints (such as I/O, number of
users, cache size, complexity of requests, and so on). High batch
requests mean good throughput.
SQL Compilations
Number of SQL compilations per second. Indicates the number of

times the compile code path is entered. Includes compiles due to
recompiles. After SQL Server user activity is stable, this value
reaches a steady state.
SQL Re-Compilations
Number of SQL recompiles per second. Counts the number of

times recompiles are triggered. In general, you want the recompiles
to be low.
WMI Mic rosoft SQL Serv er Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_mic rosoft_sql_serv er.png
Remarks
This sensor can only be added to a device (computer) running a Microsoft SQL database.
sensor on.
2554
24.03.2015

Add Sensor
later.
Select the instances of the Microsoft SQL server you want to monitor. PRTG creates one
sensor for each instance you choose in the Add Sensor dialog. The settings you choose in
SQL SER VER SETTINGS

MS SQL Server
Instance
in the table head.
Note: Display name and service name are provided as returned by
the SQL server.
SQL Server Version
Enter the version of the SQL server. Usually, you can keep the
default value.
SQL COU NTER SPECIFIC

SQL Performance
Counters
You see a list of different performance counters that the sensor

can monitor for the instance(s) which you selected above. Every
sensor that PRTG creates for the server instances monitors the
performance counter you select here. Choose from:
General St at ist ics: Read general performance counters. This
shows the number of user connections, and the number of
logins and logouts per second.
24.03.2015
2555


Access Met hods: Read access method counters. This shows
the number of full scans, page splits, and table lock escalations
(per second).
Buffer Manager: Read buffer manager counters. This shows the
buffer cache hit ratio in percent, and the number of database
pages and stolen pages.
Memory Manager: Read memory manager counters. This shows
the connection memory, optimizer memory, total server memory,
target server memory, and SQL cache memory (in kb).
Locks: Read locks counters. This shows the number of lock
requests and deadlocks (per second), and the average wait time.
SQL St at ist ics: Read SQL statistics. This shows the number of
batch requests, SQL compilations, and SQL re-compilations (per
second).
Depending on your selection, PRTG creates a sensor with the
specified channels.
Note: To monitor several performance counters for an instance,
please add the sensor several times.
Sensor Settings

Sensor Name

171 .
Parent Tags
2556
24.03.2015


Tags

default value.
Priority

Service
Shows the service that this sensor monitors. Once a sensor is

anew.
Name
Shows the name of the server instance that this sensor monitors.
WMI Class Name
Select whether PRTG selects the name of the WMI class used for
monitoring automatically. Choose between:
Aut omat ic: Choose WMI class automatically. We recommend this
setting.
Manual: Manually enter a WMI class name. Use this if your server
instance returns an error code in automatic mode.
WMI Class
This field is only shown if you enable manual WMI class selection
above. This setting is intended for experienced users only. Enter
the WMI class name that the sensor uses for monitoring your
server instance.
Sensor Result

between:
24.03.2015
2557



SQL Performance
Counters
Shows the performance counter that this sensor monitors. Once a

the sensor anew.
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2558
24.03.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
24.03.2015
2559

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2560
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2561


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2562
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
2563

Others
2564
159
section.
24.03.2015

222 WMI Microsoft SQL Server 2008 Sensor
6.8.222 WM I M icrosoft SQL Server 2008 Sensor

CHANNEL OVER VIEW

User Connections

Logins
Logouts
Full Scans

Page Splits


Database Pages
Stolen Pages


references.
Connection Memory
(KB)

24.03.2015
2565

CHANNEL OVER VIEW


optimization.
Total Server Memory

(KB)

using currently.

(KB)
SQL Cache Memory

(KB)

dynamic SQL cache.
Lock Requests

Deadlocks
Average Wait Time
Batch Requests

SQL Compilations

SQL Re-Compilations

to be low.
2566
24.03.2015


Remarks
sensor on.
Add Sensor
later.
24.03.2015
2567


MS SQL Server
Instance
in the table head.
the SQL server.
SQL Server Version
default value.

SQL Performance
Counters

(per second).
second).
specified channels.
2568
24.03.2015

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

Service
24.03.2015

anew.
2569


Name
WMI Class Name
setting.
WMI Class
server instance.
Sensor Result

between:

SQL Performance
Counters
2570

the sensor anew.
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2571

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2572
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2573


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2574
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
2575

Others
2576
159
section.
24.03.2015


CHANNEL OVER VIEW

User Connections

Logins
Logouts
Full Scans

Page Splits


Database Pages
Stolen Pages


references.
Connection Memory
(KB)

24.03.2015
2577

CHANNEL OVER VIEW


optimization.
Total Server Memory

(KB)

using currently.

(KB)
SQL Cache Memory

(KB)

dynamic SQL cache.
Lock Requests

Deadlocks
Average Wait Time
Batch Requests

SQL Compilations

SQL Re-Compilations

to be low.
2578
24.03.2015


Remarks
sensor on.
Add Sensor
later.
24.03.2015
2579


MS SQL Server
Instance
in the table head.
the SQL server.
SQL Server Version
default value.

SQL Performance
Counters

(per second).
second).
specified channels.
2580
24.03.2015

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

Service
24.03.2015

anew.
2581


Name
WMI Class Name
setting.
WMI Class
server instance.
Sensor Result

between:

SQL Performance
Counters
2582

the sensor anew.
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2583

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2584
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2585


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2586
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
2587

Others
2588
159
section.
24.03.2015


CHANNEL OVER VIEW

User Connections

Logins
Logouts
Full Scans

Page Splits


Database Pages
Stolen Pages


references.
Connection Memory
(KB)

24.03.2015
2589

CHANNEL OVER VIEW


optimization.
Total Server Memory

(KB)

using currently.

(KB)
SQL Cache Memory

(KB)

dynamic SQL cache.
Lock Requests

Deadlocks
Average Wait Time
Batch Requests

SQL Compilations

SQL Re-Compilations

to be low.
2590
24.03.2015


Remarks
sensor on.
Add Sensor
later.
24.03.2015
2591


MS SQL Server
Instance
in the table head.
the SQL server.
SQL Server Version
default value.

SQL Performance
Counters

(per second).
second).
specified channels.
2592
24.03.2015

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

Service
24.03.2015

anew.
2593


Name
WMI Class Name
setting.
WMI Class
server instance.
Sensor Result

between:

SQL Performance
Counters
2594

the sensor anew.
24.03.2015

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
24.03.2015
2595

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2596
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2597


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2598
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
2599

Others
2600
159
section.
24.03.2015

225 WMI Remote Ping Sensor
6.8.225 WM I Remote Ping Sensor

The WMI Remote Ping sensor connects remotely to a Windows system using Windows
Management Instrumentation (WMI), then performs an Internet Control Message Protocol
(ICMP) echo request ("Ping") from this device to a specified target.
The sensor shows the Ping time from the remote device to the target device that is being
pinged.

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_remote_ping.png
Remarks
sensor on.
Add Sensor
later.
21.01.2016
2601

Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
WMI R EMOTE PING CONFIGU R ATION

Target
2602
Enter the DNS name or IP address of the target device the Ping is
sent to. The sensor remotely connects to its parent device via
WMI. Then it performs a Ping request from this remote device to
the target device/server. Please enter a string.
21.01.2016

WMI R EMOTE PING CONFIGU R ATION

Timeout (Sec.)
than this value defines, the sensor cancels the request and triggers
an error message. Please enter an integer value. The maximum
timeout value is 300.
Packet Size (Bytes)
value between 1 and 10000. Please enter an integer value. We
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
21.01.2016
2603

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2604
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2605


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2606
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2607

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2608
21.01.2016

Others
21.01.2016
159
section.
2609

226 WMI Security Center Sensor
6.8.226 WM I Security Center Sensor

The WMI Security Center sensor monitors the security status of a Windows computer using
Windows Management Instrumentation (WMI). It can monitor all security products that are
controlled by Windows Security Center / Windows Action Center.
It shows the status code of the monitored product and sets the sensor status accordingly.
A sensor status showing Up indicates that the product is up to date and the access scan is
running.
Possible return values for status codes are:
St at us Code
Meaning: St at us of Monit ored

Securit y Product Is ...
Will Result in Sensor St at us
Unknown
Down
Not running, Out of date
Down
Running, Out of date
Warning
Not running, Up to date
Down
Running, Up to date
OK
WMI Sec urity Center Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_sec urity _c enter.png
2610
21.01.2016

Remarks
This sensor requires Windows Vista or later on the target computer. The Windows Security
Center / Windows Action Center is only available on client Windows versions. Because of
this, this sensor type does not run on Windows Server operating systems (Windows Server
2003, 2008, 2012)!
sensor on.
Add Sensor
later.
Select the security center products you want to monitor. PRTG creates one sensor for each
product you select in the Add Sensor dialog. The settings you choose in this dialog are valid
WMI SECU R ITY CENTER SPECIFIC

Security Center
Products
You see a list showing the Name and Ty pe of all security products
found in the Windows Security Center on the target device. If there
are no products, you see a corresponding message. Select the
lines. One sensor will be created for each selection. You can also
head.
Sensor Settings
21.01.2016
2611


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
WMI SECU R ITY CENTER SPECIFIC

Display Name
Shows the name of the product monitored by this sensor. Once a

the sensor anew.
Type
Shows the type of the product monitored by this sensor. Once a

the sensor anew.
2612
21.01.2016

DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
21.01.2016

2613

Inherited Settings
described below.
2614
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2615


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2616
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2617

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2618
21.01.2016

Others
21.01.2016
159
section.
2619

227 WMI Service Sensor
6.8.227 WM I Service Sensor

The WMI Service sensor monitors a Windows service using Windows Management
Execution time of the monitoring request.
Additionally, if you enable Monit or ext ended values in the sensor settings, it can show these
parameters:
Pagefile usage in bytes
Number of handles
Number of threads
Working set in bytes
Note: The "Running (msec)" channel of this sensor shows the execution time of the monitoring
request. It does not refer to the time the Windows service has been running! As of PRTG
version 13, the name of this sensor channel is Sensor Execut ion Time.
WMI Serv ic e Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_serv ic e.png
2620
28.04.2016

Remarks
sensor on.
Add Sensor
later.
Select the Windows services you want to monitor. PRTG creates one sensor for each service
WMI SER VICE MONITOR

Service
in the table head. Name and description are provided in the
language of the device's Windows installation. Later on the sensor
shows a Down status 135 if the service is not running.
Sensor Settings
28.04.2016
2621


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority

If Service is Not
Running
Select whether the service will be (re-)started if it is stopped or

paused. Choose between:
St art /Rest art service: PRTG tries to start the service if it is not
running when scanning the device. In combination with a Change
Trigger, you can use this mechanism to trigger a notification 2719
whenever PRTG (re)starts the service.
Do not hing: PRTG does not start any service on the device
automatically.
Note: If you select the start/restart option and the sensor detects
that the monitored service does not run, PRTG will try to restart
the service during this scan and postpones the next sensor scan
for one interval. With this following scan, the sensor checks if the
service runs now: if starting the service was not successful or the
service failed again, the sensor will show a Down status 135 and not
try to start the service again. If the service runs after a (re-)start
attempt, the sensor will continue monitoring as usual.
2622
28.04.2016


If Service is Restarted
This setting is only visible if you select the restart option above.
Define what to do if PRTG restarts the service. Choose between:
Ignore changes: No action is taken on change.
Monitoring
Select whether you want to monitor CPU usage and other useful
performance counters. Choose between:
Just check if service is running: PRTG only monitors the
channel "Sensor Execution Time".
Monit or ext ended values: PRTG monitors also other useful
performance counters.
Note: Extended monitoring might cause a "Class not found" error
on some Windows systems.
Service
Shows the Windows service this sensor monitors. Once a sensor

anew.
Description
Shows the description for the service. Once a sensor is created,

Sensor Result

between:
28.04.2016
2623

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2624
28.04.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
28.04.2016
2625


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2626
28.04.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
28.04.2016
2627

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More
Knowledge Base: How can I monitor a Windows service on Windows 2000?

Notifications
2628
28.04.2016

Others
28.04.2016
159
section.
2629

228 WMI Share Sensor
6.8.228 WM I Share Sensor

The WMI Share sensor monitors a shared resource on a Windows system using Windows
Management Instrumentation (WMI).
It shows the availability of the share.
You can define the sensor to show a Down status
135
for different share status messages.
WMI Share Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_share.png
Remarks
sensor on.
Add Sensor
later.
2630
21.01.2016

Select the shares you want to monitor. PRTG creates one sensor for each share you choose in
that are created.
WMI SHAR ED R ESOU R CE

Share
Select the shares you want to add a sensor for. You see a list with
head.
Note: To provide any shares, the LanmanServer "Server" Windows
service must be running on the target computer. If it is not, there
are no shares and you see a No Share available message here.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
21.01.2016
2631


Priority
WMI SHAR ED R ECOU R CE

Shared Recource
Description
Type
Shows information about the shared resource that this sensor

TypeID
TR IGGER ER R OR STATE ON FOLLOWING CONDITIONS

Select under which conditions the sensor shows a Down status 135 from the list below. As
long as the share returns OK, the sensor status is Up. Choose a Down condition by adding
a check mark symbol in front of the according line. Choose none, one, or several from the
following conditions.
Note: While in Down status, a sensor does not record any data in all of its channels.
Error
Set sensor to Down status if the share returns an error status. A

share in this status is not operational. This condition is selected by
default.
Degraded
Set sensor to Down status if the share returns a degraded status.

A share in this status is still operational. This condition is selected
by default.
Unknown
Set sensor to Down status if the share returns an unknown status.
2632
21.01.2016

TR IGGER ER R OR STATE ON FOLLOWING CONDITIONS

Pred Fail
Set sensor to Down status if the share returns a "predicted fail"

status. This indicates that an element works properly but predicts a
failure (for example, a SMART-enabled hard drive). A share in this
status is still operational. This condition is selected by default.
Starting
Set sensor to Down status if the share returns a starting status. A

share in this status is not operational.
Stopping
Set sensor to Down status if the share returns a stopping status.

A share in this status is not operational.
Service
Set sensor to Down status if the share returns a service status.

This can apply during disk mirror-resilvering, reloading a user
permissions list, or other administrative work on the monitored
device. Not all such work is online, but the managed element is
neither OK nor in one of the other states. A share in this status is
not operational.
Stressed
Set sensor to Down status if the share returns a stressed status.
Nonrecover
Set sensor to Down status if the share returns a "non recover"

status. This condition is selected by default.
NoContact
Set sensor to Down status if the share returns a "no contact"

status. This condition is selected by default.
LostComm
Set sensor to Down status if the share returns "lost

communication" status. This condition is selected by default.
DEBU G OPTIONS
Sensor Result

between:
21.01.2016
2633

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2634
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2635


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2636
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2637

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2638
21.01.2016

Others
21.01.2016
159
section.
2639

229 WMI SharePoint Process Sensor
6.8.229 WM I SharePoint Process Sensor

The WMI SharePoint Process sensor monitors a Microsoft SharePoint server using Windows
Management Instrumentation (WMI).
Number of current page requests
Number of active threads
Number of currently executed SQL queries
Global heap size
Object cache always live size
Template cache size
CPU utilization in percent
WMI SharePoint Proc ess Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_sharepoint_proc ess.png
Remarks
sensor on.
2640
21.01.2016

Add Sensor
later.
Select the SharePoint processes you want to monitor. PRTG creates one sensor for each
process you choose in the Add Sensor dialog. The settings you choose in this dialog are valid
WMI PR OCESS MONITOR

SharePoint Processes
in the table head.
Sensor Settings

Sensor Name
21.01.2016

171 .
2641


Parent Tags
Tags

default value.
Priority
WMI PR OCESS MONITOR

SharePoint Process
The name of the SharePoint process that is monitored by this

sensor. Once a sensor is created, you cannot change this value. It
DEBU G OPTIONS
Sensor Result

between:
2642
21.01.2016

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
21.01.2016
2643

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2644
21.01.2016


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
21.01.2016
2645


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2646
21.01.2016

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
21.01.2016
2647

More

Notifications
Others
2648
159
section.
21.01.2016

230 WMI Terminal Services (Windows 2008+) Sensor
6.8.230 WM I Terminal Services (Windows 2008+) Sensor

The WMI Terminal Services sensor monitors the number of sessions on a Windows Terminal
Services (Remote Desktop Services) server using Windows Management Instrumentation
(WMI).
Number of active sessions: sessions with a currently logged in user, including used
published applications
Number total sessions (including inactive sessions): inactive sessions can be sessions with a
disconnected user that has not logged out, or system services using a session
WMI Terminal Serv ic es Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_terminal_serv ic es.png
Remarks
Note: For "Total Sessions", this sensor type returns the number of active and inactive
sessions, plus two additional sessions: one for the console, and another for the services.
So, the number of total sessions may actually be higher than expected.
Depending on the OS that you want to monitor, select either the sensor for Windows XP/
Vista/2003 or the one for Windows 2008 and later.
sensor on.
31.08.2015
2649

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
2650
31.08.2015

DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
31.08.2015

2651

Inherited Settings
described below.
2652
31.08.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
31.08.2015
2653


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2654
31.08.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
31.08.2015
2655

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2656
31.08.2015

Others
31.08.2015
159
section.
2657

231 WMI Terminal Services (Windows XP/Vista/2003) Sensor
6.8.231 WM I Terminal Services (Windows XP/Vista/2003) Sensor

The WMI Terminal Services sensor monitors the number of sessions on a Windows Terminal
Services (Remote Desktop Services) server using Windows Management Instrumentation
(WMI).
Number of active sessions: sessions with a currently logged in user, including used
published applications
Number total sessions (including inactive sessions): inactive sessions can be sessions with a
disconnected user that has not logged out, or system services using a session
WMI Terminal Serv ic es Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_terminal_serv ic es.png
Remarks
Note: For "Total Sessions", this sensor type returns the number of active and inactive
sessions, plus two additional sessions: one for the console, and another for the services.
So, the number of total sessions may actually be higher than expected.
Depending on the OS that you want to monitor, select either the sensor for Windows XP/
Vista/2003 or the one for Windows 2008 and later.
sensor on.
2658
24.03.2015

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
24.03.2015
2659

DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
2660

24.03.2015

Inherited Settings
described below.
24.03.2015
2661

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2662
24.03.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
24.03.2015
2663


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2664
24.03.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
24.03.2015
2665

Others
2666
159
section.
24.03.2015

232 WMI UTC Time Sensor
6.8.232 WM I UTC Time Sensor

The WMI UTC Time sensor monitors the UTC (Coordinated Universal Time) time of a target
device using Windows Management Instrumentation (WMI).
UTC time of the target device
Time difference between the PRTG system time and the target device in seconds
WMI UTC Time Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_utc _time.png
Remarks
sensor on.
21.01.2016
2667

Add Sensor
later.
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
2668
21.01.2016

DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
21.01.2016

2669

Inherited Settings
described below.
2670
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2671


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2672
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2673

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
More

Notifications
2674
21.01.2016

Others
21.01.2016
159
section.
2675

233 WMI Vital System Data (V2) Sensor
6.8.233 WM I Vital Sy stem Data (V2) Sensor

The WMI Vital System Data sensor monitors vital system parameters (CPU, thread, memory,
network, pagefile) using Windows Management Instrumentation (WMI).
CPU usage: Processor, privileged, and user time
CPU queue length
Thread context switches
Free physical memory
Total visible memory
Memory page faults, reads, and writes per second
Memory pool paged and nonpaged bytes
Memory committed bytes
Network sent, received, and total bytes per second
Network packets outbound errors
Pagefile usage in percent
Physical disk time in percent
Current physical disk queue length
Physical disk reads and writes per second
Server bytes received, transmitted, and total
CLR memory time in GC in percent
CLR memory bytes in all heaps
Thrown CLR exceptions per second
sensor setup.
2676
24.03.2015

WMI Vital Sy stem Data (V2) Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_v ital_sy stem_data.png
Remarks
sensor on.
Add Sensor
later.
Select the performance counters you want to monitor. PRTG creates one sensor for each
counter you select in the Add Sensor dialog. The settings you choose in this dialog are valid
24.03.2015
2677

VITAL SYSTEM DATA R EADINGS ACCESSIBLE U SING WMI

Performance Counter
You see a list of available vital system data values the sensor can
monitor on the target device. The available options depend on
your configuration. PRTG shows all possible performance counters
with name and instance description (if available). Select the desired
items by adding check marks in front of the respective lines. One
sensor will be created for each selection. You can also select and
deselect all items by using the check box in the table head.
You can choose between the following counters:
CPU
Thread
Memory
Net work
Pagefile
Sensor Settings

Sensor Name

171 .
Parent Tags
Tags

default value.
2678
24.03.2015


Priority

Display Name
Instance
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result

between:
24.03.2015
2679

SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit

Inherited Settings
described below.
2680
24.03.2015

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
24.03.2015
2681


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2682
24.03.2015


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
24.03.2015
2683

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2684
24.03.2015

More

Notifications
Others
24.03.2015
159
section.
2685

234 WMI Volume Sensor
6.8.234 WM I Volume Sensor

The WMI Volume sensor monitors the free disk space on one drive or one logical volume using
Windows Management Instrumentation (WMI). For each drive or logical volume, PRTG uses one
sensor.
It shows free space in percent and total.
This sensor monitors an area of storage on a hard disk. It can monitor local volumes that are
formatted, unformatted, mounted, or offline. A volume is formatted by using a file system, such
as File Allocation Table (FAT) or New Technology File System (NFTS), and might have a drive
letter assigned to it. One hard disk can have multiple volumes, and volumes can span multiple
physical disks. The sensor does not support disk drive management.
WMI Volume Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wmi_v olume.png
Remarks
This sensor is not supported on Windows XP and earlier.
sensor on.
2686
21.01.2016

Add Sensor
later.
Select the volumes you want to monitor. PRTG creates one sensor for each volume you
WMI VOLU ME SPECIFIC

Volumes
Select the volumes you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

171 .
Parent Tags
21.01.2016
2687


Tags

default value.
Priority
WMI VOLU ME SPECIFIC

DeviceID
Shows the unique identifier of the volume that this sensor

Drive Type
Shows the type of the disk drive that this sensor monitors. Once a
the sensor anew.
ID Selection
Specify the way how sensor identifies the volume. Choose

between:
Use sy st em device ID (recommended): This is usually the best
option for this sensor type, because the device ID will not
change when the volume is renamed.
Use drive let t er: In a Microsoft cluster environment, the device
ID will change when the cluster is switched to another node. In
this case, use the drive letter option to avoid issues regarding
this.
Drive Letter
2688
This field is only visible if you select the drive letter option above.
Enter the letter of the drive you want to monitor followed by a
double dot, for example, C:
21.01.2016

DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
Stack Unit
21.01.2016

2689

Inherited Settings
described below.
2690
21.01.2016

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
21.01.2016
2691


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
2692
21.01.2016


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
21.01.2016
2693

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2694
21.01.2016

More

Notifications
Others
21.01.2016
159
section.
2695

235 WSUS Statistics Sensor
6.8.235 WSUS Statistics Sensor

The WSUS Statistics sensor monitors various statistics on a Windows Server Update Services
(WSUS) server using Windows Management Instrumentation (WMI).
It can show the numbers of the following:
Approved updates
Computers having update errors
Computers needing updates
Computers not synchronized for 7 days
Computers registered
Computers up to date
Declined updates
Expired updates
Not approved critical or security updates
Not approved updates
Total updates
Unapproved needed updates
Updates needed by computers
Updates needing files
Updates up to date
Updates with client errors
Updates with server errors
Updates with stale update approvals
Number of WSUS infrastructure updates not approved for installation
sensor setup.
2696
09.07.2015

WSUS Statistic s Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/wsus_statistic s.png
Remarks
Requires
09.07.2015
2698
WSUS 3.0 Administration Console on the probe system.
2697

Requires
2698
324

this sensor.

Requirement: WSUS 3.0 Administration Console

In order for this sensor to work, Microsoft's WSUS 3.0 Administration Console must 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.
Add Sensor
later.
Sensor Settings
2698
09.07.2015


Sensor Name

171 .
Parent Tags
Tags

default value.
Priority
SENSOR SETTINGS
WSUS Server Port
Define the port where the WSUS server service runs on. The
default value is 8530. Please enter an integer value.
Connection Security
Define if you want to use SSL encryption for the connection to the
WSUS server or if you prefer unencrypted connections. Choose
between:
Use SSL
Do not use any encry pt ion
09.07.2015
2699

SENSOR SETTINGS
Note: If you want to use SSL encryption, you have to configure
your Windows Server Update Services (WSUS) accordingly (see also
the More 2706 section below).
DEBU G OPTIONS
Sensor Result

between:
SENSOR DISPLAY
Primary Channel

Graph Type

for each channel.
2700
09.07.2015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
09.07.2015
2701

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error

requests.
requests.
option will apply.
2702
09.07.2015


Schedule

time.
Maintenance Window


Maintenance End At

Dependency Type

can choose between:
another dependency.
09.07.2015
2703


menu bar.
Dependency
Dependency Delay
(Sec.)

181

integer value.
2704
09.07.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
09.07.2015
2705

More
Knowledge Base: Can I encrypt connections to my WSUS server?

Notifications
Others
2706
159
section.
09.07.2015
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 9 Additional Sensor Types (Custom Sensors)
6.9
Additional Sensor Types (Custom Sensors)
Users can create and use their own, self-written custom sensors in PRTG Network Monitor to
go far beyond PRTG's standard sensor set. You can create your own sensors using Windows
Management Instrumentation Query Language (WQL), visual basic scripting, PowerShell, batch
scripting, SQL queries, by compiling an EXE or DLL file (using any Windows software
development tool), and by running Python scripts.
Basics
For a general introduction, please see the sections about EXE/Script sensors and the API
documentation 3086 which contains details about the necessary return format for these sensors.
WMI Custom sensors allow executing WQL requests.
EX E/Script Sensor
699
EX E/Script Advanced Sensor
711
Py t hon Script Advanced Sensor

SSH Script Sensor
1318
2205
2217

WMI Cust om Sensor
3086
2448
Additionally, some types of SQL sensors execute script files with SQL queries:
My SQL v2 Sensor
1075
1090

Post greSQL Sensor
1187
1297
Custom Sensors Included in PRTG

After installing PRTG Network Monitor, you will already find a selection of custom EXE/Script,
Python, and WMI WQL script sensors in the PRTG program directory 3135 , as well as scripts with
SQL queries for specific database sensors 2707 . Many of these are sample projects that you can
edit and improve for your needs.
Custom Sensors Included in PRTGFolder: \Custom Sensors\EXE

Demo Batchfile - Returns 200.bat
Demo Batchfile - Set sensorstate to error.bat
Demo Batchfile - Set sensorstate to warning.bat
Demo Cmd - Returns 200.cmd
Demo Dll - Returns a random integer.dll
Demo EXE - Returns a random integer.exe
18.03.2016
2707
Demo EXE - Returns number of files in folder (parameter).exe

Demo EXE - Returns user of process.exe
Demo Powershell Script - Available MB via WMI.ps1
Demo Powershell Script - InterruptsPerSec via WMI.ps1
Demo Powershell Script - Returns a fixed integer value.ps1
Demo Powershell Script - Returns a random integer value.ps1
Demo Powershell Script - Returns Random Integer and Warnings.ps1
Demo VBScript - InterruptsPerSec via WMI.vbs
Demo VBScript - Multiplies two integers(2 parameters).vbs
Demo VBScript - Returns a fixed float value.vbs
Demo VBScript - Returns a fixed integer value.vbs
Demo VBScript - Returns a random value.vbs
Demo VBScript - Returns number of svchost processes.vbs
Demo VBScript - Returns user of process.vbs
Demo VBScript - Returns warning depending on number of svchost processes.vbs
Demo VBScript - Timezone via WMI.vbs
Demo VBScript - UTCTime via WMI.vbs
Load_Test_CPU_1_Mio_Primes.exe
Load_Test_CPU_10_Mio_Primes.exe
Load_Test_Disk_Write_Read_1000_files.exe
Load_Test_Disk_Write_Read_10000_files.exe
Load_Test_Memory_Allocate_And_Free_400MB.exe
To create a new sensor based on one of these files, create a new EX E/Script Sensor
choose the respective file from the EX E/Script list in the sensor settings.
699
and
Custom Sensors Included in PRTGFolder: \Custom Sensors\EXEXML

Demo Batchfile - Returns static values in four channels.bat
To create a new sensor based on one of these files, create a new EX E/Script Advanced
Sensor 711 and choose the respective file from the EX E/Script list in the sensor settings.
Custom Sensors Included in PRTGFolder: \Custom Sensors\python

sensor_example.py
This Python example script just returns fixed values in two channels to demonstrate the
usage. To create a new sensor based on this file, create a new Py t hon Script Advanced
Sensor 1318 and choose the file from the Py t hon Script list in the sensor settings.
2708
18.03.2016
SQL Query Files Included in PRTGFolder: \Custom Sensors\sql\<dbms>

Demo Serveruptime.sql
You can find this demo SQL query script in each subfolder for each supported database
management system (dbms): \mssql, \my sql, \oracle, \post gresql
To create a new sensor that uses one of the scripts in the dbms folders, create the according
sensor type (see above for supported sensors 2707 ) and choose the respective file from the
SQL Query File list in the sensor settings.
Custom Sensors Included in PRTGFolder: \Custom Sensors\WMI WQL scripts

Demo WQL Script - Get Win32LogicalDiscFreeMB.wql
Demo WQL Script - Get Win32OsBuildnumber.wql
Demo WQL Script - Get Win32PercentProcessorIdleTime.wql
Demo WQL Script - Get Win32PercentProcessorTime.wql
To create a new sensor based on one of these files, create a new WMI Cust om Sensor
choose the respective file from the WQL File list in the sensor settings.
2448
and
Downloading Pre-Built Custom Sensors

A good resource to find custom sensors that PRTG users share is our Knowledge Base. Search
for the tag cust om-script -exe to find a lot of custom sensors.
More
For the other sensor types that work out-of-the-box, please see
348
Knowledge Base: Custom sensors

http://kb.paessler.com/en/tags/custom-script-exe/
Knowledge Base: How can I share my self-written PRTG script/program with other PRTG users?

Sensor Set t ings
347
18.03.2016
348
2707
2709
2711
2710
2719
18.03.2016
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 10 Sensor Channels Settings
6.10
Sensor Channels Settings
A sensor has one or more channels in which it handles the actual monitoring data. In the
channel settings you can define how to display the data from the sensor's different channels
displayed in graphs, gauges, and tables. Additionally, the channel data can determine the
sensor status 135 . Use the limit settings to achieve this.
On the sensor's Overview tab, click the gear icon of a specific channel gauge to change its
settings. Click the pin symbol on the left of the gear icon in a gauge to make this channel the
primary channel of the selected sensor.
You can also open the settings of a channel by clicking the respective gear icon in the
channels data table underneath the gauges.
Note: For lookup 3095 channels, we recommend that you stay below 120 lookup values to get
expressive gauges. For non-primary lookup channels, the upper limit is around 40 lookup
values.
The Gear Ic on of an SNMP Traffic Total Channel to

Open Channel Settings
The available options are nearly the same for all sensor types. An exception applies to the
"Downtime" channel which is automatically calculated and does not offer all settings. Channels
with "absolute" values additionally have an option for defining the Value Mode. You can quickly
choose another channel of the selected sensor via the dropdown list on the top of the
channel settings dialog.
15.04.2016
2711
Channel Settings for a Memory Sensor
Available Channel Settings

EDIT CHANNEL
Name
Enter a meaningful name to identify the channel (not editable for

script sensors after sensor creation). The name will appear in
graphs and tables. You can automatically add the sensor's ID to the
name by using the placeholder [#id].
Unit
This field is only visible for script sensors, the SNMP Custom
sensor, and the SNMP Library sensor. Enter a string describing the
unit of the returned values. This is for display purposes only.
2712
15.04.2016
EDIT CHANNEL
Scaling Multiplication
This field is only visible for channels with a custom unit. If you want
to multiply the received raw data with a certain value, enter the
multiplier here. Please enter an integer value. Otherwise, use the
Note: The following sensor types provide the scaling factor for
received values with custom units in their sensor settings:
Sensor Fact ory Sensor 1376 (you can use multiplication and
division in the channel definition)
SNMP Cust om Sensor
1577

SNMP Library Sensor
WMI Cust om Sensor
Scaling Division
1469
1659
1849
2450
This field is only visible for channels with a custom unit. If you want
to divide the received raw data with a certain value, enter the
divisor here. Please enter an integer value. Otherwise, use the
Note: The following sensor types provide the scaling factor for
received values with custom units in their sensor settings:
Sensor Fact ory Sensor 1376 (you can use multiplication and
division in the channel definition)
SNMP Cust om Sensor
1577

SNMP Library Sensor
WMI Cust om Sensor
1469
1659
1849
2450
Value Lookup
This field is only visible for script sensors, the SNMP Custom
sensor, and the SNMP Library sensor. Select the lookup 3095 file that
you want to use with this channel.
ID
Shows the ID of the channel. You cannot change it. PRTG uses it
for unique identification. For example, you need the ID when using
Sensor Fact ory 1374 sensors.
There are a few special channel IDs which are fixed:
-1 is for sum channels of traffic channels (for example, of the
SNMP Traffic Sensor 2071 ).
15.04.2016
2713
EDIT CHANNEL
-4 is for the Downt ime channel (you can use it, for example, for
an uptime percentage calculation in a Sensor Fact ory Sensor 1374
).
-2 (coverage) and -3 (error) are used internally.
Graph Rendering
Define if you want to show this channel in data graphs

between:
140
. Choose
Show in Graphs: Sensor graphs contain the data of this

channel.
Hide from Graphs: Sensor graphs do not contain data of this
channel.
Note: If you choose to hide this channel in graphs, it will also not
appear in a Report 2786 if you include this graph.
Table Rendering
Define if you want to show this channel in data tables

between:
137
. Choose
Show in Tables: Sensor data tables contain the data of this

channel.
Hide from Tables: Sensor data tables do not contain the data of
this channel. This option hides the channel gauge as well, but the
channel will still be available in the data table of the sensor's
Overview tab.
Note: If you choose to hide this channel in data tables, PRTG will
also not use it for the calculation of the "sum" (total) channel of
this sensor!
Line Color
Define the color of the channel display in graphs. Choose

between:
Aut omat ic: PRTG sets the color of this channel in graphs
automatically.
Manual: Individually define the color of this channel. You can
enter the desired color code below.
Color (#rrggbb)
This option is only available if choose manual line color above.

Enter a color in hexadecimal RGB notation (as in HTML/CSS), or
choose a color from the visual color selector. The field with the
hexadecimal color value will change to the selected color
automatically.
Line Width
Define the width of the channel line in graphs. Enter an integer

value in pixels. The maximum line width is 25px, but we
recommend that you use values between 1 and 7 only to get
optimal results.
2714
15.04.2016
EDIT CHANNEL
Data
This setting is available for most channels. Define how to display

data. Choose between:
Display act ual values in [unit]: Display the values in the unit
shown.
Display in percent of maximum: Calculate and show percent
values based on a maximum value. Provide a maximum below.
Note: If you choose this option, you cannot display the data of
traffic sensors on a positive/negative graph.
Maximum ([unit])
This field is only visible if you choose the percent of maximum

setting above. Enter a value to use as maximum. Please pay
attention to the given unit. PRTG calculates all percent values
based on this value. Please enter an integer value.
Value Mode
This setting is only available for sensor channels which return

absolute values. It is not available for sensors showing difference
values, such as traffic channels. Depending on this setting, the
channel cannot only show averages, but also minimum or maximum
values in the graphs for the respective time spans. Choose
between:
Average: The channel shows average values.
Minimum: The channel shows minimum values.
Maximum: The channel shows maximum values.
See this Knowledge Base article for more information about the
value modes: http://kb.paessler.com/en/topic/60238
Decimal Places
Define how many decimal places of the channel's data to display in

graphs and tables. Choose between:
Aut omat ic: PRTG automatically defines how many decimal places
are used for optimal viewing results.
All: Display all available decimal places.
Cust om: Manually define the number of decimal places. If you
choose this option, an additional field will appear. Please enter an
integer value.
Spike Filter
15.04.2016
You can use a spike filter to correct faulty monitoring data.

Sometimes, sensors report enormously high or far too low values.
This can be because of an error in data transmission, or because of
incompatibilities of the physical device you are monitoring. This can
make graphs unreadable. A spike filter can compensate for these
flaws. If you enable a spike filter, values above and below a certain
limit are disregarded in the monitoring data for graphs and tables.
2715
EDIT CHANNEL
Choose between:
Disable Filt ering: Display all data as it retrieved. Do not filter out
spikes.
Enable Filt ering: Enable a filter to remove spike values.
Additional fields appear below.
Note: This does not change monitoring data itself but only the
presentation of the data. This setting is valid for all data of this
channel, including historic data.
Note: The spike filter option is not available for the channel
Downt ime.
Spike Filter Max. Value
[unit]
This field is only visible if you enable the spike filter above. Enter
the maximum value to show in the channel data. PRTG disregards
all data above this value in graphs and tables. Please enter an
Spike Filter Min. Value

[unit]
This field is only visible if you enable the spike filter above. Enter
the minimum value to show in the channel data. PRTG disregards all
data below this value in graphs and tables. Please enter an integer
value or leave the field empty.
Vertical Axis Scaling
Define how to display the vertical axis for the channel in graphs.
Choose between:
Aut omat ic Scaling: PRTG automatically uses the optimum
scaling. Usually the scaling ranges from the minimum to the
maximum value. PRTG uses one single scale for each unit label
only.
Manual Scaling: Define the scaling manually. Additional fields
appear below. Defining manual axis scaling can make low values
better visible in your graph, but it may result in a graph with
multiple vertical axis for the same unit label.
Note: Settings for this option are ignored if you enable the Chart
Type St ack channels on t op of each ot her or Show in and out
t raffic as posit ive and negat ive area chart (available for traffic
sensors) on the sensor's Set t ings tab.
Vertical Axis Maximum

[unit]
This field is only visible if you enable vertical axis scaling above.
Enter the maximum value to use on the vertical axis for the
channel. Please enter an integer value.
Vertical Axis Minimum

[unit]
This field is only visible if you enable vertical axis scaling above.
Enter the minimum value to use on the vertical axis for the channel.
2716
15.04.2016
EDIT CHANNEL
Limits
Define if you want to use thresholds for this channel. The channel
can affect the status of the sensor 135 it is part of. With limits you
can define when the sensor will show a Warning or Down status,
depending on the channel data. For example, you can use this
function to set a traffic sensor (which is usually never in a down
state) to error when the monitored values reach critical limits.
Choose between:
Disable Limit s: Do not use the channel data to control the
sensor status.
Enable Limit s: Define limits. Additional fields appear below. The
sensor of this channel will enter a Warning or Down status when
limits are undercut or overrun.
Note: The limits option is not available for the channel Downt ime.
Note: If a channel uses lookups 3095 , we strongly recommend that
you control the sensor status only via the lookup definition. If you
define limits in addition here, the sensor will use both the channel
limits and the status as defined in the lookup file. In this case,
channel limits will determine the overall status of the sensor and
overwrite the sensor message while the channel gauge still shows
the status as defined in the lookups.
Note: You can show limits in graphs (highlighted in yellow or red) if
you select exactly one channel with a limit in a graph.
Upper Error Limit [unit]
This field is only visible if you enable limits above. Specify an upper
limit for a Down status. If the channel values overrun this value, the
sensor will be Down. Please enter an integer value or leave the
field empty.
Note: While a sensor shows a Down 135 status triggered by a limit,
it will still receive data in its channels.
Upper Warning Limit

[unit]
This field is only visible if you enable limits above. Specify an upper
limit for a Warning status. If the channel values overrun this value,
the sensor will be Warning. Please enter an integer value or leave
the field empty.
Lower Warning Limit

[unit]
This field is only visible if you enable limits above. Specify a lower
limit for a Warning status. If the channel values undercut this value,
the sensor will be Warning. Please enter an integer value or leave
the field empty.
15.04.2016
2717
EDIT CHANNEL
Lower Error Limit [unit]
This field is only visible if you enable limits above. Specify a lower
limit for a Down status. If the channel values undercut this value,
the sensor will be Down. Please enter an integer value or leave the
field empty.
Note: While a sensor shows a Down 135 status triggered by a limit,
it will still receive data in its channels.
Error Limit Message
This field is only visible if you enable limits above. Enter an

additional message. It will be added to the sensor message when
showing a Down status. Please enter a string or leave the field
empty.
Warning Limit Message
This field is only visible if you enable limits above. Enter an

additional message. It will be added to the sensor message when
showing a Warning status. Please enter a string or leave the field
empty.
Click Ok to store your settings and to close the settings window. Click Apply to save the
changed settings while the Edit Channel window remains open. This functionality is useful if
you want to change the settings of other channels of the current sensor as well. You can
select another channel via the drop-down menu on top of the settings window. You can close
the settings window without saving with by clicking Cancel.
Note: If you have changed any settings and click Cancel or choose another channel via the
drop-down menu without applying the changes, PRTG will ask you to confirm this step.
Discard Changes will ignore any edits and closes the window or shows the settings of
another selected channel. Click Save to apply your changes.
More
Knowledge Base: What is the Value Mode in channel settings?

Sensor Set t ings
347

2707
2711
2718
348
2719
15.04.2016
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 11 Sensor Notifications Settings
6.11
Sensor Notifications Settings
configure external alerting tailored to you needs.
Example of Notific ation Trigger Settings

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/notific ation_trigger.png
Although the sensors activate a trigger, you can set notification triggers higher in the hierarchy
(for example for groups or devices). Because of this you can define triggers for multiple
sensors using the inheritance mechanism 94 . Monitoring objects with inherited triggers show
these in section Triggers That Can Be Inherit ed From Parent Object (s) on the
Not ificat ions tab.
PRTG already includes a default notification trigger for the Root Group 90 . This default trigger
provokes the standard notification Email and push not ificat ion t o admin if there is any
sensor in down status 135 in your PRTG installation for at least 10 minutes.
You can also define notification triggers in Libraries 2770 . Sensors which are in a library with
defined triggers show these triggers in section Triggers That Are Defined in Library Object
(s) on the Not ificat ions tab.
Note
This section describes one of four steps to set up the notification system in PRTG. A complete
notification setup involves:
1. Checking and setting up the Not ificat ion Delivery settings. This tells PRTG how and where
to send messages.
For detailed information, see Sy st em Administ rat ionNot ificat ion Delivery 2877 .
11.11.2015
2719
2. Checking and setting up Not ificat ion Cont act s for the users of your PRTG installation. This
defines where to send notifications.
For detailed information, see Account Set t ingsNot ificat ion Cont act s 2852 .
3. Checking and setting up Not ificat ions. This defines the kind of message and its content.
For detailed information, see Account Set t ingsNot ificat ions 2836 .
4. Checking and setting up Not ificat ion Triggers for objects. These provokes the defined
notifications.
For detailed information, see Sensor Not ificat ions Set t ings 2719 .
Note: We recommend that you always set up at least two notifications with different delivery
methods for a notification trigger, for example, one email notification 2841 and one SMS
notification 2843 . If delivery via email fails (due to a email server failure or other reasons), PRTG
can still notify you via your smartphone. Simply set your latency setting to a state trigger 2721
and a notification via a delivery method other than the one for the first trigger. Or by sett up a
second trigger with another notification for the corresponding object.
For background information, please see the Not ificat ions
2759
section.
Available Notification Triggers Settings

On an object's detail page, click on the Not ificat ions tab to change sensor notification
triggers. The available options are the same for all objects. When defining triggers for probes,
groups, or devices, they can be inherited down to sensor level.
TR IGGER S THAT CAN BE INHER ITED FR OM PAR ENT OBJECT(S)

You see a list of all notification triggers that are defined higher in the hierarchy. The list is
empty and shows the message (no t riggers defined) when you have not set any triggers in
probes, groups, or devices above the current object in the Object Hierarchy 89 . You can
see the Ty pe of trigger and the Not ificat ions that the monitoring objects executes once
this trigger is activated.
Trigger Inheritance
Define if you want to use the triggers shown above on the current
object. Choose between:
Inherit all t riggers from parent object s and use t he t riggers
defined below: Use the triggers shown above. If the defined
condition is met, the corresponding trigger is activated and the
notification provoked. Click the notification name to open its
settings page 2836 . Click the name of the monitoring object in the
column Inherit ed from to open its Overview tab.
Only use t riggers defined below: Do not use the triggers
shown above. Do only use the triggers that you define below in
section Object Triggers for this object.
This setting is valid for all triggers shown above. It is not possible
to only select some of the triggers.
2720
11.11.2015
In section Triggers t hat are defined in library object (s) you see all notification triggers that
are set for Libraries 2770 which contain the currently selected sensor.
TR IGGER S THAT AR E DEFINED IN LIBR AR Y OBJECT(S)

You see a list of all notification triggers that are defined in libraries which include the
currently selected sensor. The list is empty and shows the message (no t riggers defined)
when you have not set any triggers in libraries that contain the current sensor. You can see
the Ty pe of trigger and the Not ificat ions that the sensor executes once this trigger is
activated.
Click the notification name to open its settings page
Inherit ed from to view this library.
2836
. Click a library name in the column
Note: You cannot turn off trigger usage for the current sensor from a library here. If you do
not want to use any notification triggers from a library for this sensor, open the library and
remove this sensor from it or refine the triggers on the Not ificat ions 2783 tab.
You can set up one or more of the following triggers, each with different setting options.
Which trigger types are visible depends on the kind of object you edit:
Add State Trigger
2721
Add Speed Trigger
2723
Add Volume Trigger
2725
Add Threshold Trigger

Add Change Trigger
2727
2728
You can create all notification triggers by forming sentences in "natural language". There are
different options available for every type.
Add State Trigger

Define a trigger that is activated when a sensor changes its current status. This is the most
common reason to send out notifications. Click the Add St at e Trigger button to add a new
trigger, or click the Edit button next to an existing notification to change it. Define the
settings as described below. Every trigger provokes one or more notification(s) 2836 to be
executed.
STATE TR IGGER
When sensor state is
[...]
11.11.2015
Select the condition that will trigger the notification. The trigger
will be activated when a sensor enters the selected status.
Choose from the drop down menu:
2721
STATE TR IGGER
Down: The trigger is activated if a sensor changes to a Down
status.
Warning: The trigger is activated if a sensor changes to a
Warning status.
Unusual: The trigger is activated if a sensor changes to an
Unusual status.
Part ial Down: The trigger is activated if a sensor changes to a
Down (Part ial) status (available in a cluster 87 configuration).
...for at least [...]
seconds
Define how many seconds PRTG waits before it sends out a

notification. This can avoid false alarms if a sensor 'flickers' and, for
example, changes to a down status for just a few seconds. If the
selected condition (the sensor status) persists after the defined
time in seconds, the notification is triggered. Please enter an
integer value.
...perform [...]
Select a notification that PRTG sends out if the selected condition

(the sensor status) is true and the latency time defined has
elapsed. Choose a notification from the drop down menu. The
menu shows all notifications defined in the Account Set t ings
Not ificat ions 2836 settings. You can also choose no not ificat ion
to only use other conditions for this trigger.
When sensor state is

[...] for at least [...]
seconds
Define an escalation latency in seconds. This "escalation" triggers a

second notification if the number of seconds you enter here has
passed since the sensor status has entered the defined condition.
Use this to automatically escalate a notification in case a problem
persists for a longer time. Please enter an integer value.
Note: PRTG takes automatically the status from the first trigger
condition above.
...perform [...]
Select a (second) notification that PRTG sends out if the selected

condition (the sensor status) is true and the escalation latency
time defined has elapsed. Choose a notification from the drop
down menu. The menu shows all notifications defined in the
Account Set t ingsNot ificat ions 2836 settings. You can also
choose no not ificat ion to only use other conditions for this
trigger.
Hint: Select a notification with another delivery method than above
to ensure the delivery in case of technical issues with the first
notification.
2722
11.11.2015
STATE TR IGGER
...and repeat every [...]
minutes
Define an interval in minutes in which PRTG sends the escalation

notification (defined above) repeatedly. The second (escalation)
notification defined will be resent every x minutes which you enter
here. Please enter an integer value.
Note: If you enter 0, PRTG will not send repeating escalation
notifications.
When condition clears

after a notification was
triggered perform [...]
Select a notification that PRTG sends out if the selected condition

(the sensor status) is not true any more because the sensor status
changed again. Choose a notification from the drop down menu.
The menu shows all notifications defined in the Account Set t ings
Note: PRTG sends notifications about cleared conditions if the time
for the trigger activation elapsed (defined in the first line) and you
choose a notification here. If you select "no notification" above,
you will get the notification about the cleared condition
nevertheless if you define it here. The definition of an "escalation"
notification does not influence notifications for cleared conditions.
Save
Click Save to confirm your settings.
Cancel
Click Cancel to undo your changes.
Add Speed Trigger

Define a trigger that is activated when the currently monitored speed in a sensor changes (for
example, a traffic sensor). Click the Add Speed Trigger button to add a new trigger, or click
the Edit button next to an existing notification to change it. Define the settings as described
below. Every trigger provokes one or more notification(s) 2836 to be executed.
SPEED TR IGGER
When [...] channel
From the drop down menu, select the channel whose data PRTG
considers for speed comparison. Select Primary to generally use
the primary channel of a sensor (you can define this in the sensor
settings 347 ), or choose a specific channel name from the list (there
are different channels for every sensor type). All following settings
for this trigger are based on the chosen channel.
...is [...]
Select the condition that will trigger the notification. Choose from
the drop down menu:
11.11.2015
2723
SPEED TR IGGER
Above: The trigger is activated if the value of the selected
channel exceeds a defined value.
Below: The trigger is activated if the value of the selected
channel falls below a defined value.
Equal To: The trigger is activated if the value of the selected
channel is the same as a defined value.
Not Equal To: The trigger is activated if the value of the selected
channel is different than a defined value.
[value]
Define the value to which PRTG compares the channel data. Please
[scale]
From the drop down menu, select the unit in which you entered
the [value] above. [scale] and [t ime] together define the unit for
the given value. If the channel data is shown in a different unit,
PRTG will automatically convert values internally. Choose between:
bit
kbit
mbit
gbit
t bit
By t e
KBy t e
MBy t e
GBy t e
TBy t e
[time]
Select the time for the scale (so you create a scale per time unit).
Choose from the drop down menu:
second
minut e
hour
day
[scale] and [t ime] together define the unit for the given value. If
the channel data is shown in a different unit PRTG will automatically
convert values internally.
2724
11.11.2015
SPEED TR IGGER
..for at least [...]
seconds

notification. This can avoid false alarms if a channel reaches a limit
for just a few moments. If the combined channel condition of
[value], [scale], and [t ime] persists after the defined time span,
the notification will be triggered. Please enter an integer value.
...perform [...]
Select a notification that is triggered if the combined channel

condition of [value], [scale], and [t ime] is true and the latency
time defined has elapsed. Choose a notification from the drop
down menu. The menu shows all notifications defined in the
Account Set t ingsNot ificat ions 2836 settings. You can also
trigger.

perform [...]
Select a notification that is triggered if the combined channel

condition of [value], [scale], and [t ime] is not true any more
because the channel value has changed again. Choose a
notification from the drop down menu. The menu shows all
notifications defined in the Account Set t ingsNot ificat ions 2836
settings. You can also choose no not ificat ion to only use other
conditions for this trigger.
nevertheless if you define it here.
Save
Cancel
Note: No escalation notification and no repeat are available for this trigger type.
Add Volume Trigger

Define a trigger that is activated when a sensor (for example, a traffic sensor) reaches a certain
volume limit in a specified time. Click the Add Volume Trigger button to add a new trigger, or
click the Edit button next to an existing notification to change it. Define the settings as
described below. Every trigger provokes one or more notification(s) 2836 to be executed.
11.11.2015
2725
VOLU ME TR IGGER
When [...] channel
considers for this comparison. Select Primary to generally use the
primary channel of a sensor (you can define this in the sensor
...has reached [value]
Define the value to which PRTG compares the channel data. If the
channel data exceeds this value, a notification is triggered. Please
[scale]
From the drop down menu, select the unit in which you entered
the [value] above. [scale] and [t ime] together define the unit for
the given value. If the channel data is shown in a different unit,
PRTG will automatically convert values internally. Choose between:
By t e
KBy t e
MBy t e
GBy t e
TBy t e
per [time]
Select the time for the scale (so you create a scale per time
designation). Choose from the drop down menu:
Hour
Day
Week
Mont h
[scale] and [t ime] together define the unit for the given value. If
the channel data is shown in a different unit, PRTG will automatically
convert values internally.
...perform [...]
Select a notification that is triggered if the [value] in the combined

unit of [scale] and [t ime] is exceeded. Choose a notification from
the drop down menu. The menu shows all notifications defined in
the Account Set t ingsNot ificat ions 2836 settings. You can also
trigger.
Save
Cancel
2726
11.11.2015
Note: No escalation notification, no repeat, and no notification when condition clears are
available for this trigger type.
Add Threshold Trigger

Define a trigger that is activated when a sensor reaches specific values. Click the Add
Threshold Trigger button to add a new trigger, or click the Edit button next to an existing
notification to change it. Define the settings as described below. Every trigger provokes one
or more notification(s) 2836 to be executed.
THR ESHOLD
TR IGGER
When [...] channel
considers for this comparison. Select Primary to generally use the
primary channel of a sensor (you can define this in the sensor
...is [...]
Select the condition that will trigger the notification. Choose from
the drop down menu:
Above: The trigger is activated if the value of the selected
channel exceeds a defined value.
Below: The trigger is activated if the value of the selected
channel falls below a defined value.
Equal To: The trigger is activated if the value of the selected
channel is the same as a defined value.
Not Equal To: The trigger is activated if the value of the selected
channel is different than a defined value.
[value]
Define the value to which PRTG compares the channel data. Enter
values in the smallest possible (base) unit, for example, in bytes or
seconds. Please enter an integer value.
..for at least [...]

seconds

notification. This can avoid false alarms in case a channel reaches a
limit for just a few moments. If the defined channel condition
persists after the defined time span, the notification is triggered.
11.11.2015
2727
THR ESHOLD
TR IGGER
...perform [...]
Select a notification that is triggered if the defined channel

condition is true and the latency time defined has elapsed. Choose
a notification from the drop down menu. The menu shows all
notifications defined in the Account Set t ingsNot ificat ions 2836
settings. You can also choose no not ificat ion to only use other
conditions for this trigger.

perform [...]
Select a notification that is triggered if the defined channel

condition is not true any more because the channel value has
changed again. Choose a notification from the drop down menu.
The menu shows all notifications defined in the Account Set t ings
nevertheless if you define it here.
Save
Click Save button to confirm your settings.
Cancel
Note: No escalation notification and no repeat are available for this trigger type.
Add Change Trigger

Define a trigger that is activated by an 'on change' trigger. Some sensors offer the option to
send such a trigger whenever sensor values have changed. Click the Add Change Trigger
button to add a new trigger, or click the Edit button next to an existing notification to change
it. Then define settings as described below. Every trigger will provoke one or more notification
(s) 2836 to be executed.
CHANGE TR IGGER
When sensor changes
perform [...]
2728
Select a notification that is triggered whenever a compatible

sensor sends a 'change notification'. You can enable this option in
the settings 347 of some sensors. The notification trigger is
activated immediately whenever a sensor sends an 'on change'
trigger. Choose a notification from the drop down menu. The menu
shows all notifications defined in the Account Set t ings
Not ificat ions 2836 settings.
11.11.2015
Note: There are no other options available for this trigger type.

Sensor Set t ings
347

348
2707
2711
2719
Object Settings Overview

For more general information about object settings, please see section Object Set t ings
11.11.2015
159
2729
Part 7
Ajax Web InterfaceAdvanced Procedures
24.03.2015
2731
Part 7: Ajax Web InterfaceAdvanced Procedures |
Ajax Web InterfaceAdvanced

Procedures
The following sections introduce more advanced procedures in the Ajax Graphical User
Interface (GUI).
Ajax Web InterfaceAdvanced ProceduresTopics

Toplist s
2734
Arrange Object s
Clone Object
Mult i-Edit
2739
2740
2742

Show Dependencies
Geo Maps
Report s
Maps
Set up
2751
2753
Not ificat ions

Libraries
2747
2759
2770
2786
2810
2828

108
218
Related Topics
Ent erprise Console
2732
2938
24.03.2015
Part 7: Ajax Web InterfaceAdvanced Procedures |
24.03.2015
2990
2733
Part 7: Ajax Web InterfaceAdvanced Procedures | 1 Toplists
7.1
Toplists
Packet Sniffer and xFlow (NetFlow, jFlow, sFlow, IPFIX) sensor types can not only measure the
total bandwidth usage, they can also break down the traffic by IP address, port, protocol, and
other parameters. The results are shown in so-called Toplist s. This way PRTG is able to tell
which IP address, connection, or protocol uses the most bandwidth. PRTG looks at all network
packets (or streams) and collects the bandwidth information for all IPs, ports, and protocols. At
the end of the toplist period, PRTG stores only the top entries of each list in its database.
Only Top Entries are Stored

Storing all available analysis data in a database during the analysis process would create a huge
amount of data which would be very slow to transfer between probe and core and also
retrieving data would be too slow. By storing only the top 100 entries for short periods of
time it is possible to reduce the amount of data to a minimum while still being able to identify
devices with huge bandwidth usage.
Toplists Overview
Toplist s are available for xFlow, IPFIX, and Packet Sniffer sensors 349 only. Toplist graphs are
displayed right on the sensor overview page. By default, there are three different toplists
predefined for each sensor:
Top Connect ions: Shows bandwidth usage by connection.
Top Prot ocols: Shows bandwidth usage by protocol.
Top Talkers: Shows bandwidth usage by IP address.
2734
18.03.2016
Toplist Top Protoc ols for a Pac ket Sniffer Sensor
Click one of these items to view a distribution chart and a list of source and destination IP and
port, protocols, kind of traffic in different channels, for example. It depends on the selected list
which information is available. Click an entry in the Toplist periods list on the left side to view
data for a certain time span. By default, a time span of 15 minutes is set. You can also manually
define start and end time of the Toplist period you want to view. Use the date time picker to
enter the date and time. Additionally, several table list options 178 are available.
To print a Toplist, click the Print This Toplist button to view a printer-friendly version. Use the
print option of your browser to send it to your printer. With Sensor Overview you can return
to the current sensor's overview tab. For a quick selection of other Toplists of the current
sensor, click one of the Toplist icons at the top of the page.
In the sensor overview, you can add or delete new Toplists, or edit existing ones.
18.03.2016
2735
Add
Click the Add Toplist tile in the sensor overview to create a new Toplist. The available options
are the same as for editing 2736 a list.
Edit
Click the small gear icon of a Toplist tile in the sensor overview to modify it.
TOPLIST
Name
Enter a meaningful name to identify the toplist.
Type
Top Talkers (Which IPs use t he most bandwidt h?): Shows

bandwidth usage by IP address.
Top Connect ions (Which connect ions use most bandwidt h?):
Shows bandwidth usage by connection.
Top Prot ocols (Which prot ocols use t he most bandwidt h?):
Shows bandwidth usage by protocol.
Cust om (Creat e y our own Toplist ): Create your own list by
selecting criteria below.
Toplist Fields
This setting is only available if you select a custom type above.

Select the fields you want to add to the Toplist by adding a check
mark in front of the respective field name. The available options
depend on the type of sensor used. They are different for Packet
Sniffer, NetFlow v5, v9 (and IPFIX), and sFlow.
Note: For performance reasons, only select the fields you really
want to monitor. Please see Performance Considerat ions 2738
section below.
Period (Minutes)
Define the interval for the Toplist in minutes. Please enter an

integer value. Toplists always cover a certain time span. Once a
time span has passed, the top results are stored and a new Toplist
is started.
Note: To avoid load problems on your probe system, please do not
set this interval too long. Default setting is 15 minutes. Please see
Performance Considerat ions 2738 section below.
Top Count
Define the length of your Toplist. Only this number of entries will
be stored for each period. Please enter an integer value.
Note: To avoid load problems on your probe system, please set
this value as low as possible. Default setting is 100 to store the
top 100 entries for each period. Please see Performance
Considerat ions 2738 section below.
2736
18.03.2016
TOPLIST
Reverse DNS
Define if your you want to do a reverse Domain Name Service

(DNS) lookup for IP addresses stored in the Toplist. Choose
between:
Do a reverse DNS lookup for IPs: Determine the domain name
associated with an IP address and show it in the Toplist.
Do no reverse DNS lookup (fast er): Show IP addresses only.
Choose this option to increase performance.
Probe/Core Data
Transfer
Define how the probe sends the Toplist data set to the core
server. Choose between:
According t o sensor int erval (default ): Send data in the
interval defined in the settings of the sensor for which you
create this Toplist. This can create a lot of bandwidth and CPU
load with many sniffer sensors, complex traffic, or long Toplists.
Wait unt il Toplist period ends (less CPU and bandwidt h
usage): Send data once a Toplist period has finished. This will
create less bandwidth usage and CPU load, but you cannot see
the current Toplist in the web interface, only Toplists with
finished periods.
For more information, please see Performance Considerat ions
section below.
Memory Limit (MB)
2738
Define the maximal amount of memory in MB the probe will use for
collecting the different connection information. Every Toplist adds
its amount to the probe's memory consumption. Increase this
value if the number of captured connections is not sufficient.
Delete
Click the small trashcan icon of a Toplist tile in the sensor overview to delete it. Confirm with
Delet e to delete the list.
Details
Click on the windows symbol to show details of a Toplist.
18.03.2016
2737
Performance Considerations
If you create Toplists for data lines with considerable usage (for example, steady bandwidth
over 10 Mbit/s) or if the traffic is very diverse (for example, many IPs/ports with only little traffic
each) please consider the following aspects:
The probe gathers all information needed for the Toplist in RAM memory during each period.
Only the top 100 entries are transferred to the core. Depending on the Toplist type and
traffic patterns the required memory can grow into many megabytes.
Choose periods as short as possible (especially important when traffic has a high level of
diversity) to minimize memory usage.
Memory requirements can grow almost exponentially with each field used in the Toplist
definition (depending on traffic pattern). Avoid complex Toplists for high and diverse traffic.
For example, Top Connect ions (5 fields) needs a lot more memory than Top Talkers (1
field).
If you experience high bandwidth usage between core and probe try to choose the Wait
unt il Toplist period ends option in the Toplist settings 2736 .
If you experience Data incomplete, memory limit was exceeded messages, try to increase
the memory limit in the Toplist settings but keep an eye on the memory usage of the probe
process.
To increase the performance of a Toplist, disable the reverse DNS lookup.
Notes
When working with Toplists, be aware that privacy issues can come up for certain
configurations of this feature. Using Toplists you can track all single connections of an
individual PC to the outside world and you, as the administrator, must make sure it is legal for
you to configure PRTG like this.
Keep in mind that Toplists can be viewed through the web interface. You may not want to
show lists of domains used in your network to others, so restrict access rights 101 to sensor
types having Toplists.
Note that diagrams, for example, for top connections are not meant to be used for detailed
analysis. Rather they should indicate if there is an uncommon bigger change in this Toplist.
More
Monit oring Bandwidt h via Flows
3012
Monit oring Bandwidt h via Packet Sniffing
2738
3010
18.03.2016
Part 7: Ajax Web InterfaceAdvanced Procedures | 2 Arrange Objects
7.2
Arrange Objects
There are several options to move objects within the device tree, or to move objects from
one probe or group to another.
Manage Tab in Device Tree

While viewing the device tree (or parts of it), click the Management tab to switch to a tree
view in which you can move monitoring objects using drag&drop in your browser window. For
more information, see section Manage Device Tree 258 .
Device Details View: Arrange Sensors

When you view the Overview tab of a device, you see a list of all sensors on this device.
Arrange Sensors on a Dev ic e
Click the column headers Pos, Sensor, St at us, or Priorit y to re-sort the sensor list. To
change a sensor's position, click the small grip at the beginning of the row, drag it to the
position you like, and drop it. Changes take effect immediately.
Context Menu: Move

You can also right-click any object in the device tree to show the context menu 186 . Select the
Move entry to move sensors, devices, or groups up and down, or to move groups or devices
into other groups or on other probes.
21.01.2016
2739
Part 7: Ajax Web InterfaceAdvanced Procedures | 3 Clone Object
7.3
Clone Object
If you want to duplicate an object with the same settings, you can clone it. Cloning is available
for groups, devices, and sensors. Unlike the results when using the Creat e Device Templat e
2747 option, a cloned device contains all objects of the original device, regardless of whether
they bring about working sensors or not (which often depends on the settings of the cloned
device).
Note: You cannot clone 'fixed' objects, such as the root group or a probe device.
Note: If you want to clone a sensor, a faster way is to use the Manage Device Tree
function.
To start, right-click an object in your device tree, and from the context menu
Clone... to open an assistant.
186
258
, select
Clone Dialog for a Sensor
2740
21.01.2016
Part 7: Ajax Web InterfaceAdvanced Procedures | 3 Clone Object
Clone Object Settings

OBJECT TO BE CLONED
Object
Several fields show information about the object that you are
going to clone. The available information varies depending on
whether you are about to clone a group, device, or sensor.
NAME OF NEW OBJECT

New Object Name
Enter a meaningful name for the new object to identify it later in,
for example, the device tree or lists. By default, PRTG uses the old
name with a preceding Clone of.
New IP Address/DNS
Name
This field is only available when you clone a device. Enter the IP
address or DNS name for the new device.
PAR ENT GR OU P/DEVICE FOR NEW OBJECT

From the device tree shown, choose an object you want to add the object clone to. If you
clone a group or device, select a group. If you clone a sensor, select the device you want to
add it to.
You will be redirected to the overview 137 page of the new object that you cloned. By default,
all sensors are initially paused 185 so you can change settings before monitoring starts. Please
check the settings 159 and resume 185 monitoring.
Related Topics
Manage Device Tree
21.01.2016
2747
258
2741
Part 7: Ajax Web InterfaceAdvanced Procedures | 4 Multi-Edit
7.4
Multi-Edit
Device and sensor table lists, as well as some other lists, offer multi-edit functionality. With this,
you can bulk edit the properties of many objects at a time. Multi-edit is also available in the
Management tab if you select multiple objects by holding down the Ctrl key (see Manage
Device Tree 259 ).
Note: You cannot change every setting type with multi-edit. PRTG only displays settings which
all selected objects have in common.
Note: You cannot multi-edit the standard user groups
Users Group".
2896
"PRTG Administrators" and "PRTG
Example of a Table List
Start Multi-Edit in Lists

Start with viewing a table list. For example, choose Sensors | By Ty pe | ... or Devices | Device
List | ... from the main menu. Table lists are also available in the Overview tab of Libraries 2770 ,
Maps 2810 , Report s 2786 , Not ificat ions 2759 , and Schedules 2856 .
In a table list, start multi-edit by selecting objects using the check boxes on the right. You can
also select all objects of the current page at once by clicking the check box in the table
header. Use the It em Count option to view more items per page. As soon as you select one
or more objects, the multi-edit menu will appear at the top of the table. Chosen objects are
shaded in green.
2742
28.04.2016
Multi Edit Menu
Depending on the object type, different functions are available. For example, for sensor lists,
some frequently used functions are available as quick buttons, such as Delet e, Pause, Resume,
Check Now, and Set t ings. Click one of those buttons to apply the respective function to all
selected objects.
Other options are available in the drop down menu. Hover over the arrow symbol to show it.
Example of Multi Edit Drop

Down Menu
The options in this menu vary depending on the kind of objects selected. Choose an entry to
apply the according function to all selected objects.
Once you have selected the objects you want to change settings for, click the wrench symbol
to enter the edit settings mode. For available settings, please see below.
Start Multi-Edit in Management Tab

In the device tree, start by clicking the Management tab.
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.
28.04.2016
2743
For available settings, please see below.
Edit SettingsSettings
The Edit Mult iple Object s dialog box shows most of the settings which the selected sensors
respectively devices have in common. For example, you can edit the name, tags, priority,
scanning interval, and access rights.
Example of Dev ic e Settings in Multi-Edit Mode
The available options depend on the selected objects and vary according to your selection.
When editing multiple sensors, it may be useful to only choose one certain sensor type from
the list, so that there are as much settings as possible available for multi-edit.
To change a property, add a check mark in front of the respective line and then change the
settings. The new setting(s) will be applied to all objects you selected for multi-edit. All
properties that are not activated with a check mark remain unchanged.
Click OK to store your settings. If you close the dialog box via the X or Cancel button, all
2744
28.04.2016
Edit SettingsChannel Settings

The Channel Set t ings tab in the Edit Mult iple Object s dialog box is only available when
editing sensors. You can edit settings of all channels which the selected sensors have in
common. Select a channel name from the Channel list. You can then edit, for example, display
settings, colors, scaling, and limits.
Example of Sensor Channel Settings in Multi-Edit Mode
The available options depend on the selected sensors and vary according to your selection. It
may be useful to only choose one certain sensor type from the list, so that there are as much
channel settings as possible available for multi-edit.
To change a property, add a check mark in front of the respective line and then change the
channel settings. The new setting(s) will be applied to all sensors you selected for multi-edit.
All properties that are not activated with a check mark remain unchanged.
Click OK to store your settings. If you close the dialog box via the X or Cancel button, all
Related Topics
28.04.2016
178
2745
Manage Device Tree
2746
258
28.04.2016
Part 7: Ajax Web InterfaceAdvanced Procedures | 5 Create Device Template
7.5
Create Device Template
If you want to add a certain device several times, you can create a device template from an
existing device in your device tree. When creating a device template, PRTG will save information
for nearly all sensors on this device to a template file that you can later use in combination
with Aut o-Discovery 219 (restrictions 2748 apply for a few sensor types). From the sensors, all
relevant settings are saved, except settings that refer to other objects, such as schedules 99 ,
notification triggers 2759 , and access rights 101 . PRTG will automatically revert them to Inherit .
To start, right-click a device in your device tree. From the context menu
Device Templat e.... An assistant appears.
186
, select Creat e
Create Dev ic e Template Assistant
11.03.2016
2747
Device Template Settings

CHOOSE TEMPLATE NAME
File Name
Enter a name under which PRTG will store the file. Template files
have the extension .odt in the \PRTG Network Monitor
\devicetemplates sub-directory of your PRTG core installation 3135
(of the Master node, if in a cluster 87 ). If a file with this name
already exists in this directory, you will see an according error
message.
Template Name
Enter a meaningful display name for the template as it will appear in

the web interface.
Exclude Sensors
Select sensors that you do not want to include into the device
template. Mark the corresponding checkboxes of the sensors
which you do not want to include into the device template.
Note: Sensors that cannot be saved into templates
appear in this list.
2748
will not
Note: Sensor types that dynamically scan for available monitoring

items when you add the sensor to a device will not appear in this
list. PRTG includes these sensors automatically into the template if
they support template functionality. You cannot exclude them from
the device template that you create.
If your template file was saved successfully, you will see an according message. Click OK to
finish. The device template is now stored in the program path of your PRTG core installation.
Your device template file contains all sensors, including their settings, of the original device.
During your next auto-discovery, choose the Aut omat ic sensor creat ion using specific
device t emplat e(s) option and select the name of your newly created device template from
the list. PRTG will then try to discover the stored sensor types on the new (or existing) device.
If the physical device answers to a sensor request, the sensor is added to the PRTG device.
For detailed information, please see Aut o-Discovery 219 section.
Settings That Are Not Saved

There are a few settings that you cannot save into a device template, so PRTG will set them to
default, for example, the Dependency Type setting Mast er object for parent (in Schedules
and Dependencies section) and Result Handling settings Writ e result do disk (because this is
intended for debugging purposes only). Also, settings in the Access Right s section are not
saved to avoid security flaws.
2748
11.03.2016
Note: In general, you cannot save all Sensor Set t ings 347 and Sensor Channels Set t ings
(for example, channel limits) of sensor types that dynamically scan for available monitoring
items when you add the sensor. This affects, for example, traffic sensors where you can
choose the interfaces you want to monitor in the add sensor dialog 256 .
2711
Furthermore, due to internal restrictions, the following sensor types will not be saved into a
device template:
Business Process
Core/Probe/Clust er Healt h
DHCP
Docker Cont ainer St at us
Dropbox
Ent erprise Virt ual Array
Google Analy t ics
Google Drive
IPFIX
IPFIX (Cust om)
IPMI Sy st em Healt h
jFlow V5
jFlow V5 (Cust om)
Microsoft OneDrive
Net App cDOT Aggregat e (SOAP)
Net App cDOT I/O (SOAP)
Net App cDOT Phy sical Disk (SOAP)
Net App cDOT Sy st em Healt h (SOAP)
Net Flow V5
Net Flow V5 (Cust om)
Net Flow V9
Net Flow V9 (Cust om)
Packet Sniffer
Packet Sniffer (Cust om)
Passive Applicat ion Performance
QoS (Qualit y of Service)
QoS (Qualit y of Service) Roundt rip
Sensor Fact ory
11.03.2016
2749
sFlow
sFlow (Cust om)
SNMP Trap Receiver
Sy slog Receiver
WMI Securit y Cent er
WMI Volume (use WMI Free Disk Space (Mult i Drive) Sensor
2509
instead)
No Update of Device Templates

Once a device template is created, it is not possible to add additional sensors to it. If you want
to create a template with an extended set of sensors, please create a new one.
Note: When saving a new device template, all internal IDs of the sensors in this template are
updated. Because of this, when you apply a new template to an existing device, PRTG will
newly create all sensors that this template contains on this device, even if these sensors were
previously created using another device template!
Related Topics
Clone Object
2740
Manage Device Tree
2750
258
11.03.2016
Part 7: Ajax Web InterfaceAdvanced Procedures | 6 Show Dependencies
7.6
Show Dependencies
This function shows an overview of the dependencies configured for the objects in your
setup. For a general introduction please see the Dependencies 98 section.
In the main menu, choose Devices. Point on the menu item Dependencies to show other
menu items. Follow the menu path (it is specific to your setup) to view dependencies of the
objects in a specific probe or group only.
Select ed Dependencies shows a table of manually set dependencies (section Select object
in any object's settings).
Mast er Dependencies shows a table of master dependencies.
Dependencies Graph shows a visualization of device, group and sensor dependencies. See
below 2751 .
Dependenc ies Graph View
Dependencies Graph
Choose the menu item Dependencies Graph to see the device tree in the dependencies
graph view with lines of different color connecting objects. Point on Dependencies Graph to
show other menu items for the dependency graph (probes and groups). Click a probe or
group menu item to show its dependencies directly. The lines in the dependencies graph
symbolize dependencies between the monitoring objects in the device tree. Additionally, a
color code 2752 is used for the dependencies.
Note: To show the Dependencies Graph, you need to access the PRTG web interface as a
PRTG Sy st em Administ rat or user.
11.03.2016
2751
Part 7: Ajax Web InterfaceAdvanced Procedures | 6 Show Dependencies
Above the graph header bar, you can switch the dependencies view to tables of the
currently selected object with the buttons Select Dependencies Table and Mast er
Dependencies Table. The button Group View will show the Overview tab 126 of the
currently selected object.
Mark the radio button in the header bar to Show Mast er Dependencies. By default, Hide
Mast er Dependencies is selected and only parent, selected, and broken dependencies are
shown.
Note: These buttons are not available in Internet Explorer for technical reasons. Please use
Google Chrome 49 or later (recommended) or Mozilla Firefox 45 or later.
Click the + or buttons on the left in the header bar to zoom in or out of the graph.
Click probe and group nodes to show the respective dependencies.
Click device or sensor nodes to open the corresponding overview tab.
Click the + or boxes to expand or collapse probe and group nodes.
Numbers in parentheses indicate how many child nodes of an object are shown.
The Highlight Connect ion buttons to the right of sensors show the corresponding
dependency line and parent and dependent objects in bold.
Color Code of Dependencies Graph

The line's colors show the kind and source of a dependency. This represents the Dependency
Ty pe as defined in the Schedule, Dependencies, and Maint enance Window settings of a
probe, group, device, or sensor 218 .
Note: You can find the color legend also in the graph header bar.
Gray
Gray lines show a dependency by inheritance (Use parent). The source of the dependency is
the parent object on the left end of the line, for example, Root is the parent of Local Probe.
Pink
Pink lines show a dependency that was set manually (Select object). The source of the
dependency points to the dependent with a pink arrow at the line's end.
Blue
Blue lines show a master dependency for a device (Master object for parent). The sensor
which is set as the master points to the dependent device with a blue arrow head at the
line's end. The arrow head from the dependent device to its master object is pink.
Red
The red color indicates broken dependencies, for example, if the master is not available.
2752
11.03.2016
Part 7: Ajax Web InterfaceAdvanced Procedures | 7 Geo Maps
7.7
Geo Maps
With the PRTG Geo Maps feature you can visualize geographical information about your
monitored objects. You can display the location of probes, groups, and devices in a graphical
map on the details page of an object, or on PRTG Maps 2810 . This feature is especially useful
when you monitor networks which are spread over different locations, for example, in various
cities of a country or all over the globe.
For each probe, group, or device, you can enter Locat ion information. PRTG will use the first
line of this information to query a geographical map which shows your objects. Your location
specification will be resolved to global geographical coordinates by the PRTG core server with
the help of an external map service provider.
PRTG will connect to the specified maps provider to get map tiles. These are used to set up
the graphical map. Then PRTG marks the defined locations with the corresponding object icons
and their status 2756 on the map. You can select your favorite map tiles provider in Sy st em
Administ rat ionUser Int erface 2861 (setting Geo Maps).
You can display geographical maps on the device tree. PRTG adjusts the zoom of a map
automatically so that it can show all locations of a selected object. You can also add
geographical maps to PRTG Maps 2810 . To do so, open the PRTG Map Designer 2816 (either in an
existing map or create a new one) and choose the entry Geo Maps from the properties menu
on the right.
09.07.2015
2753
The Global Status of a Network in a Geo Map
Using Geo Maps

To use geographical maps within the PRTG web interface
ensure the following:
108
or Ent erprise Console
2938
, please
1. In the system administration in the PRTG web interface, select the maps provider and type
you want to view. There, you will also find an option to disable geo maps integration if you
do not want to use it. See section Sy st em Administ rat ionUser Int erface 2861 (setting
Geo Maps) for detailed information.
2. In the settings of a monitoring object 159 (probe, group, device), add a city name, or address,
or coordinates in the first line of the Locat ion field. When you view the details of this
object, PRTG will show a geographical map. PRTG uses the Locat ion information also when
you view objects in the Ent erprise Console 2938 or add Geo Maps objects to PRTG Maps 2810 .
3. Make sure your PRTG core server has access to the internet to obtain map tiles. If a proxy is
mandatory in your network, configure proxy settings accordingly. For details, please see
Sy st em Administ rat ionCore & Probes 2883 . For details about tile server domains, please
2754
09.07.2015
Labeling Locations
You can define your own labels for locations of objects. To do so, enter the desired label in
the first line of the Locat ion settings and provide the geo coordinates of the location in the
second line. This object will appear with the defined label in PRTG geo maps.
For example, add the following to the location field:
Big Apple
40.712778,-74.005833
Defining Loc ation New York City with Geo Coordinates and Label
Big Apple
The location New York City appears the with the label Big Apple:
Loc ation New York City with Label Big Apple
09.07.2015
2755
It is also possible to define the same label for different locations. For example, imagine your
company's headquarter is spread over several different locations. For each object representing
a dedicated headquarter in the PRTG device tree, enter its coordinates in the second line of
the respective Locat ion settings and the label "Headquarter" in the first line. All corresponding
objects will be displayed as "Headquarter". This way, you can easily find your desired objects
on the map.
Map Icon Colors

On the geographical maps the different location icons show the overall status at this location
by using a color code. Following, you can see all possible location states in order of their
hierarchy:
2756
09.07.2015
Flag
Flag Color
Locat ion St at us Meaning
Red
Down
Bright-Red
Down
At least one sensor at this location is Down and
(Acknowledged) a PRTG user acknowledged this status with the
Acknowledge Alarm function. The Down states
of all sensors at this location must be
acknowledgedif at least one sensor is
unacknowledged down, this location will be
displayed as Down.
Yellow
Warning
At least one sensor at this location shows a

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

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

(Acknowledged), Warning, Paused, or Unusual
Blue
Paused
All sensors at this location show a blue Paused

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

(Acknowledged), Warning, Unusual, Paused, or
Up status at this location.
At least one sensor at this location shows a red

Down status. Hover the circle with the letter
symbol in the legend to view the total number of
alarms at this location.
Note: For detailed information about sensor states, please see the section Sensor St at es
135
Geo Tracking of Your Mobile Device

It is possible to show the location of an Android device and track its movements on PRTG Geo
Maps. PRTG can draw the route a device has taken directly into geo maps. For this feature, you
need the PRTG Mobile Probe for Android. See section More 2758 for details.
09.07.2015
2757
More
Knowledge Base: Which provider should I use for PRTG's "Geo Maps" feature?
Knowledge Base: Which domains and ports does the GeoMaps feature use?
Knowledge Base: Why does my street not appear on the Geo Map shown in PRTG?
Knowledge Base: How do I get a Google Maps API key for use in PRTG?
Knowledge Base: Which limitations apply when using the Google Maps API in PRTG?
Knowledge Base: How can I change the way markers look like in PRTG's geo maps?
Knowledge Base: How can I track geo data of my Mobile Probe device?
Knowledge Base: My geo maps are displayed without background. What can I do?
2758
09.07.2015
Part 7: Ajax Web InterfaceAdvanced Procedures | 8 Notifications
7.8
Notifications
PRTG uses notifications to send you alerts whenever PRTG discovers a defined status, such as
slow or failing sensors, or when sensor channels breach threshold values. You can define an
unlimited number of notifications allowing to use one, or more, of several communication
channels like email 2841 , text messaging 2843 , push notifications 2842 to Android and iOS devices,
and many more 2840 . PRTG sends notifications to the desired user's Not ificat ion Cont act s 2852
that you can define for each user account of your PRTG installation.
For video instructions, please see the More
2761
section below.
Overview
PRTG sends a notification when a defined event evokes it. The following events can trigger
notifications:
Sensor st at us changes
For example, when a sensor changes status to Down or Warning, if responses are slow, or
sensors show an Unusual status.
Sensor value t hreshold breaches
For example, when a sensor shows a request time higher than 1,000 ms for more than 30
minutes, or when free disk space is below 10%.
Speed t hreshold breaches
For example, when a traffic sensor shows more than 1 Mbit/s for more than 5 minutes.
Volume t hreshold breaches
For example, when a traffic sensor shows more than 1 Gbyte transferred in 24 hours.
Sensor value changes
For some sensors you can trigger a notification whenever the value changes, for example,
when monitoring files on a hard disk drive.
A notification can be one of these actions:
Send Email
2841
Send Push Not ificat ion
2842
Send SMS/Pager Message

Add Ent ry t o Event Log
Send Sy slog Message
Send SNMP Trap
2843
2845
2845
2846
Execut e HTTP Act ion

Execut e Program
2847
2848
Send Amazon Simple Not ificat ion Service (SNS) Message

Assign Ticket
2849
For details, see section Account Set t ingsNot ificat ions
21.01.2016
2848
2840
2759
Note: Usually there are three successive attempts to deliver a notification. If all of these
attempts fail, the notification is lost. To never miss a notification, we recommend that you
always add two different ways to get a notification. For example, use the latency setting of a
state trigger 2721 to choose a notification with another delivery method than in the first trigger
condition, or set up a second trigger with another notification for the corresponding object.
Notifications can contain valuable sensor information, such as:
Last error message
Last good/failed request
Total downtime
Total uptime
Recent sensor history
A direct link to the web interface
See More
2761
for available placeholders.
Notifications Setup
Overall, you have to go through four steps to use notifications with PRTG. Please go through
all of them for a first setup:
1. Check and set up the Not ificat ion Delivery settings. This tells PRTG how to send
messages.
2. Check and set up Notification Contacts for the users of your PRTG installation. This defines
where to send notifications.
3. Check and set up several Not ificat ions. This defines the kind of message and its content.
4. Check and set up Not ificat ion Triggers for objects. These provoke the defined
notifications.
notification 2843 . If delivery via email fails (due to a email server outage or for other reasons),
PRTG can still notify you via your smartphone in this case as a fallback. You can achieve this, for
example, by using the latency setting in a state trigger 2721 and selecting a notification with
another delivery method than for the first trigger condition.
Please see section Set t ing Up Not ificat ions Based on Sensor Limit s: Example
by-step guide that describes a potential notifications setup.
2760
2762
for a step-
21.01.2016
More
https://www.paessler.com/support/video_tutorials/notification-and-trigger
Knowledge Base: Notifications based on priorities
21.01.2016
2761

1 Setting Up Notifications Based on Sensor Limits: Example
7.8.1
Setting Up Notifications Based on Sensor Limits: Example
This section shows you exemplarily how to set up a notification for exceeded disk free limits.
We provide the approach for this specific use case step by step so you can adapt it to define
limits and corresponding notifications for other sensor types.
You have to take several steps to set up notifications based on limits:
Step 1:
2762
Provide necessary information about the delivery of notifications (SMTP and SMS).
Step 2:
2762
Specify recipients for notifications for each user account of your PRTG installation.
Step 3:
2763
Create notifications, specifying the type of notification and its content.
Step 4: 2764 Define thresholds that change a sensor's status (this is not necessary for every
kind of notification).
Step 5: 2766 Add suitable triggers to objects which evoke notifications if something is going
wrong in your network.
Step 6:
2767
Test if the created notification is triggered and delivered correctly.
Note: When you set up your own notifications, you do not necessarily need to go through all
the steps we describe here. In this section, our main goal is to give you a general idea of the
notifications concept.
Step 1: Setting up the Notification Delivery

Before creating your actual notifications, you first have to define how those notifications are
delivered to your email account, mobile phone, or pager. To do so, choose Set up | Sy st em
Administ rat ion | Not ificat ion Delivery from the PRTG main menu bar. Specify the mechanism
of SMTP delivery, sender email and name, as well as the HELO ident. For SMS delivery, select
your service provider and provide the corresponding credentials.
You can find details about notification delivery in section Sy st em Administ rat ion
Not ificat ion Delivery 2877 .
Step 2: Setting up Notification Contacts

Create notification contacts to define where you want receive notifications. Recipients can be
email addresses, phone numbers, or push devices (Android or iOS devices, or Windows Phone,
with the corresponding PRTG smartphone app 2995 ). You can define as many recipients for each
user account in your PRTG installation as you want. By default, the recipient "Primary Email
Address" is availablethis is the email address you provide in your account settings 2830 . This is
sufficient for a first setup of notifications. Later on, when you see how it works, you can define
more contacts. When you add a notification to a device, you just have to select a user or user
group as recipient then and PRTG uses the according contacts you define here.
For details, see section Account Set t ingsNot ificat ion Cont act s
2762
2852
21.01.2016

Step 3: Setting up the Notification's Content

To get an informative message when a disk is running out of capacity, create a corresponding
notification. Choose Set up | Account Set t ings | Not ificat ions from PRTG's main menu bar
and click on the button Add New Not ificat ion. Give the notification an explanatory name; in
our case you could use Disk Free Limit Notification. However, if you want to trigger this
notification on a global level (for example, for a probe or group) such that it would not only
apply to breached disk free limits, a general name would be more suitable (like the predefined
notification "Email to Admin"). If you leave the default text of the newly created notification, it
already contains all necessary information, for example:
which sensor is affected,
since when the sensor is affected,
last value of this sensor.
See section More
2767
for the other options you have here.
After providing this basic information, select the delivery method. In our case, we choose Send
Email for this notification by marking the corresponding checkbox. Specify who will receive
the notification (select a specific user, for example, and PRTG sends the notification to all
contacts of this user you specified in step 2 2762 ), its subject, the format, and its priority. By
default, the email notification contains several information parameters about the evoking
sensor: its name, status, time, message, location in the device tree, etc.
You can choose any other notification method, of course. Please see Account Set t ings
Not ificat ions 2840 .
Creating an Email Notific ation
Once you set up the notification completely, click Save. PRTG opens the notifications overview
page again. You can now use this notification for every trigger on every object in your device
tree.
21.01.2016
2763

Step 4: Define Limits

Before creating triggers that evoke notifications, first specify the limits which you want to
apply to your disks. For example, if you want to get a notification when a disk has exceeded
80% of its capacity, force the sensor into a Warning status at this utilization. You have several
options to set limits for disk free sensors:
Set limits checked against all disks in the settings of multi-drive sensors: WMI Free Disk
Space 2509 , SNMP Linux Disk Free 1857 , SSH Disk Free 2109
Enable limits in Sensor Channels Set t ings
You can achieve both with Mult i-Edit
2742
2711
of single sensors.
Step 4.1: Define Limits in Sensor Settings (Multi-Disk Free Sensors Only)
You can set limits for sensors monitoring multiple disks directly via the Set t ings tab on a
sensor's details page. Mult i-Edit 2744 for existing sensors is also possible. Open the settings of
the selected sensor(s) and go to section Set limit s checked against ALL disks. There, for
example, enable Percent age Limit Check. In the field Lower Warning Limit , enter the
percentage suitable to your needs. In our example, this would be 20. Alternatively, you can
use bytes to define a limit. However, we recommend using percentage values for more
flexibility. This limit applies to all channels of this sensor that represent disks.
Setting Limits for All Disks
Note: This sensor setting is only available for multi-drive sensors. You can omit Step 4.1 for all
sensors that are not from the type "disk free".
2764
21.01.2016

Step 4.2: Define Limits for Sensor Channels

To set specific limits for single disks, use the sensor's Channel settings. You can open channel
settings 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
Lower Warning Limit field. This limit only applies to the respective channel.
Note: If you define channel limits when using the sensor's limit setting in the sensor's Set t ings
tab at the same time, the first limit that applies will be considered. This way, you can individually
define harder limits for single disks in a multi-disk sensor. All defined limits are valid side-byside.
You have to take the approach via channel settings for sensor types that monitor only one
(logical) disk, for example, the SNMP Disk Free Sensor 1685 . For these sensor types, you can
use Mult i-Edit 2745 if you want to apply the same limits for each of these sensors automatically.
To see all sensors of this type at a glance, just filter for it: From PRTG's main menu bar,
choose Sensors | By Ty pe | SNMP Disk Free.
Mark the checkboxes of the sensors you want to add a limit for.
Click the wrench symbol in the multi-edit bar.
Open the Channel Set t ings tab.
Select the channel you want to add a limit for; in this case it would be most likely the
channel Free Space.
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 settingsthe new limit applies to all channels with this name
of the multi-edited sensors.
21.01.2016
2765

Setting Limits for Channels with Multi-Edit
Step 5: Setting up the Notification Trigger

You specified limits to define when a sensor will go into a Warning (or Error) status. Now you
can create the according triggers. The trigger we use in this example is the St at e Trigger. For
details about other possible notification triggers, see section More 2767 .
You can set up a St at e Trigger on any level in your device tree. For example, open a group
containing the device(s) representing your disks.
Open the Not ificat ions tab.
2766
21.01.2016

Click Add St at e Trigger.

Set the trigger to "When sensor is Warning" and choose the notification you created before
("Disk Free Limit Notification" or a more general one) from the drop down list.
Adjust the other notification settings to your needs and save this new object trigger.
Now you receive a notification immediately when the capacity of one of your disks falls below
the defined limit, in this case 20% free disk space.
Setting a Trigger for Disk Free Limit Notific ation
Step 6: Testing the Notification

Finally, test the notification that you created. You can trigger this notification for test purposes
immediately:
From the main menu bar
200
, choose Set up | Account Set t ings | Not ificat ions.
For the respective notification, click on the corresponding Test button.

Then, check if the notification was triggered and delivered correctly, depending on the delivery
method you defined before. If you do not get a notification (or a defined action is not
executed) at all, check the notification logs: From the main menu bar, choose Logs | Sy st em
Event s | Not ificat ions. Look for the triggered notification in the table list (verifying that the
notification delivery is set up correctly in general) and consider the corresponding message.
See section Logs 169 for more information.
More
This section provides information about additional options you have when working with
notifications.
21.01.2016
2767

Not ificat ion Set t ings:

You can create schedules to activate notifications only at specific times, for example, only on
weekdays. In section Not ificat ion Summarizat ion you can choose between various
options to avoid message floodings. Furthermore, define which user groups will have access
to edit this notification. For details about notification settings, refer to section Account
Set t ingsNot ificat ions 2836 .
Cont ent of Emails:
You can individually adjust the subject, header, and footer of emails to your needs. See
section Account Set t ingsNot ificat ions 2840 for details about editing the subject. The
article How can I include my own logo int o HTML emails? in the Knowledge Base explains
how to edit the header and footer of emails: http://kb.paessler.com/en/topic/65782
Ot her Triggers:
An alternative to the state trigger would be to add a Threshold Trigger; then you would not
need to set up limits explicitly, though, this trigger type would only be suitable for disk free
sensors when using the trigger for single sensors, one by one. Free disk sensors have free
space in percent as primary by default, other sensors have primary channels with the units
bytes or seconds. However, threshold triggers only apply to the primary or total channel.
General notification triggering by threshold might not work as expected for sensors of the
"percentage" type. You can find all available triggers in section Not ificat ions 2759 .
Add a Threshold Trigger to a sensor directly:
Go on a sensor's detail page and select the Not ificat ions tab. Click on Add Threshold
Trigger, select the desired channel, and provide the condition when this notification will be
sent. In this example for free disk space, the setting would be "When Free Bytes C: (%)
channel is Below 20 for at least 60 seconds perform Disk Free Limit Notification".
Not ificat ions wit h Libraries:
If your disk devices are spread over many groups, we recommend that you use a PRTG library
2770 for your disks. Choose Libraries | All diskspace sensors from the main menu bar, go on
the Not ificat ions tab, and add a state trigger as described above.
Note: Not all disk free sensor types might appear. You can add them to this library in the
settings of the library node. There you can filter by type or tag 2779 and add missing sensors
this way. You can also filter by priority and other sensor properties.
2768
21.01.2016

Settings of a Library with Diskspac e Sensors
21.01.2016
2769
Part 7: Ajax Web InterfaceAdvanced Procedures | 9 Libraries
7.9
Libraries
With PRTG's Libraries feature you can create special views of your device tree with up-to-theminute monitoring status information, arranged the way you want it.
Example of a Library
In this section:
Int roduct ion
2770
St art Libraries
Libraries List
2771
2771
Working wit h Libraries
2772
Introduction
Libraries are a powerful feature that enables you to create additional views of your device tree.
These views are updated with the same scanning interval as your device tree, showing the
same monitoring data, but arranged in a way you want it. This is interesting if you want to
display data in different ways, e.g. depending on target groups or a specific use case. For
example, you can create a library which contains an overview of all your bandwidth monitoring
sensors, regardless of which device they're running on.
The Library features include:
Create Libraries containing nodes with monitoring objects from all over your configuration.
Show data from different PRTG probes in one library.
Show different branches of your device tree right next to each other.
Arrange sensors in a tree-like view regardless of which device they are running on.
2770
28.04.2016
Filter your entire tree (or parts of it) for sensor type, state, or tag, showing only matching
sensors.
You can create libraries easily, using drag&drop.
PRTG comes with several pre-configured standard libraries, which you can use right away. You
can also change or delete them, if you like. The following libraries are automatically created
when you install PRTG for the first time (visible for the PRTG Administrator user). Some of them
will initially be empty, but as you add more sensors, they will be filled automatically according
to the filter settings defined for the nodes of the libraries:
All bandwidth sensors
All CPU load sensors
All diskspace sensors
All memory sensors
All VMware sensors
Sensors grouped by priority
Sensors grouped by state
Note: Sensors which are added to libraries are not counted against the maximum number of
sensors of your license.
Start Libraries
Click the Libraries entry from the main menu 204 to view or add custom views of your
network's status and monitoring data. Hover over St art Libraries to show other menu items.
Choose between:
LIBR AR IES
All
Open the Libraries overview list where you can view or add custom
device tree views of your network status and monitoring data.
Add Library
Open an assistant to directly create
Select Library
Open an existing library. Hover over Select Library to show other

select a library and open it.
2773
a new library.
Libraries List
In the All view, you see a list of all existing libraries. Using the links next to a library name, you
can perform the following actions.
Edit : Open this library and change the settings
28.04.2016
2779
of the library and its nodes
2771
Clone: Create a clone
2740
of this library.
Delet e: Delete this library.

Used by : Show which other monitoring objects use this library.
Click the Add Library button to add a new library.
Please also see Working wit h Table List s 178 . Additionally, the multi-edit functionality is
available. This enables you to change properties of several objects simultaneously via bulk
changes. For more details, see the Mult i-Edit List s 2742 section.
Working with Libraries

For detailed information on how to create and edit libraries please see the following sections.
Libraries St ep By St ep
Management
2773
2777
Libraries and Node Set t ings

Cont ext Menus
2772
2779
2785
28.04.2016

1 Libraries Step By Step
7.9.1
Libraries Step By Step
In order to create a new library, follow the steps in this section. In the web interface, click on
the Libraries entry in the main menu to show the libraries main screen.
In this section:
St ep 1: Add Library
2773
St ep 2: Add Library Nodes
2774
St ep 3: Set Library Node Display Set t ings

St ep 4: View
2774
2775
Step 1: Add Library

Click on the Add Library button. An assistant is shown. Enter a Library Name, and define
Tags and Access Right s, if you like. Click on Cont inue.
For detailed information, see Libraries Set t ings
2779
section.
Add Library Assistant Step 1
24.03.2015
2773

Step 2: Add Library Nodes

Click to the Management tab. You will see a split screen: On the left side, your library is
shown (empty in the beginning), and on the right side, you see a less colorful view of your
device tree, as known from the device tree's Management 258 tab.
Bandwidth Library in Management Mode
From the device tree on the right side, drag objects and drop them on the library on the left
side. Each dropped object will be added immediately as a new Library Node. Repeat this
procedure as often as you wish until you have added all desired items to the library.
Note: When adding single sensors to the library, there can only be one sensor in one library
node.
Note: Library nodes can contain up to 1,000 sensors.
You can also create nested library nodes by adding a new node underneath an existing one.
Drag and drop nodes within the library to change their position. If you want to change the
monitoring object that is associated with a library node, you can change the Linked Object in
the node's settings.
Step 3: Set Library Node Display Settings

You are still in the library Management tab.
2774
24.03.2015

Right-click the name of a Library Node and from the context menu, select Edit | Set t ings... to
change the Node Display Set t ings. In this dialog, you can change the name of the library and
its tags, as well as the linked object, node type, and filters.
These settings are available for each library node. You can choose to either show the Linked
Object as a sub-tree of your device tree, or to view a collection of all sensors underneath the
Linked Object .
When selecting the sub-tree view, the library node will just look like a branch in your device
tree, as shown in the screen shot below for the library node names "My Sub Tree".
Library with one Node Showing a Branc h of the Dev ic e Tree
When selecting a sensor collection view, only the sensors underneath the Linked Object are
shown, omitting probes, groups, and devices. You can additionally filter by certain sensor
Ty pe, St at us, and Tags. Only matching sensors will be shown. The screen shot below shows
the same Linked Object as above, but in sensor collection view, additionally filtered for
sensors with a bandwidt hsensor tag.
Library with one Node Showing a Collec tion of Bandwidth Sensors Only
For detailed information, see Libraries and Node Set t ings

Display Settings) section.
2779
(OverviewLibrary Node
Step 4: View
Click on the Overview tab to see the final appearance of your library. You have the following
options:
Hover over an object to view a popup window with recent monitoring and status data.
Use the sensor state selection bar to select which sensors you want to see for the library:
Simply remove check marks for sensor states you want to hide. Note: This function is the
same you know from the device tree's Sensor Status Bar 126 . The setting is reset the next
time you open the library.
Use the Device Tree View selection in the page header bar 126 to change the size of the
library display. Note: This function is the same you know from the device tree 129 .
24.03.2015
2775

Use the Search box in the page header bar 126 to search the library for a string in object
names. Matching objects will be shown full-colored, all others will be grayed out while the
filter is active. Click on the small x symbol in the search field to reset the filter. Note: This
function is the same you know from the device tree 126 .
It depends on the library's access rights and the currently logged in user account if it will be
visible to other PRTG users. Also, clicking on objects (for example, on sensors) will lead to
more detailed information about the object or to an error message indicating insufficient
access rightsdepending on user account and access rights.
In libraries, you can right-click objects to access their Cont ext Menus
2776
2785
24.03.2015

2 Management
7.9.2
M anagement
Click to the Management tab. You will see a split screen: On the left side, your library is
shown (empty in the beginning), and on the right side, you see a less colorful view of your
device tree, as known from the device tree's Management 258 tab.
Bandwidth Library in Management Mode
Add and Change Library Nodes

From the device tree on the right side, drag objects and drop them on the library on the left
side. Each dropped object will be added immediately as a new Library Node. Repeat this
procedure as often as you wish until you have added all desired items to the library.
Note: When adding single sensors to the library, there can only be one sensor in one library
node.
Note: Library nodes can contain up to 1,000 sensors.
You can also create nested library nodes by adding a new node underneath an existing one.
24.03.2015
2777

2 Management
Drag and drop nodes within the library to change their position. If you want to change the
monitoring object that is associated with a library node, you can change the Linked Object in
the node's settings.
Set Library Node Display Settings

Right-click the name of a Library Node and from the context menu, select Edit | Set t ings... to
change the Node Display Set t ings. In this dialog, you can change the name of the library and
its tags, as well as the linked object, node type, and filters.
These settings are available for each library node. You can choose to either show the Linked
Object as a sub-tree of your device tree, or to view a collection of all sensors underneath the
Linked Object .
When selecting the sub-tree view, the library node will just look like a branch in your device
tree, as shown in the screen shot below for the library node names "My Sub Tree".
Library with one Node Showing a Branc h of the Dev ic e Tree
When selecting a sensor collection view, only the sensors underneath the Linked Object are
shown, omitting probes, groups, and devices. You can additionally filter by certain sensor
Ty pe, St at us, and Tags. Only matching sensors will be shown. The screen shot below shows
the same Linked Object as above, but in sensor collection view, additionally filtered for
sensors with a bandwidt hsensor tag.
Library with one Node Showing a Collec tion of Bandwidth Sensors Only
For detailed information, see Libraries and Node Set t ings

Display Settings) section.
2779
(OverviewLibrary Node
Context Menus
On right-click, there are different context menus availablein the Management as well as in
the Overview tab.
For detailed information, please see Cont ext Menus
2778
2785
section.
24.03.2015

3 Libraries and Node Settings
7.9.3
Libraries and Node Settings
Using the libraries tabs you can access all functionalities and settings for a library.
Library Tabs
Overview
Click on the Overview tab any time to show the current state of your library.
Library Node Display Settings

While in the Overview tab, click on a library node's name to change its settings. Or, while in
the Management tab, right-click a library node's name and select Edit | Set t ings... from the
context menu. In both cases, the following settings are shown. Note: You can only change the
settings of a node if it contains monitoring objects already, e.g., groups, devices, or sensors.
BASIC LIBR AR Y NODE SETTINGS

Library Node Name
Enter a meaningful name for the library node.
Tags
Enter one or more tags, separated by space or comma. For

example, you can use tags later to search for the library. Tags are
not case sensitive.
NODE DISPLAY SETTINGS

Linked Object
Click on the reading-class symbol to change the object which is

linked with this library node. A popup window will appear, showing
the Object Select or 181 .
Node Type
Select what you want to view for this library node. Choose
between:
Show a subt ree of t he device t ree in t he library : View all
objects underneath the linked object as a device tree.
Show a collect ion of filt ered sensors in t he library (max.
1000): View all sensors underneath the linked object (only
sensors are shown). You can combine several filters with each
other (see below).
Note: The node can show up to 1,000 sensors, surplus sensors
are discarded.
31.08.2015
2779


Filter By Type
This option is visible only if collection of sensors is enabled above.

Select if you want to filter the sensor list by a certain type. Choose
between:
Show all sensor t y pes: Do not filter for a sensor type.
Show specific sensor t y pes only : Filter the sensor list of the
linked object for certain sensor type(s).
Note: This filter is applied in real-time. If the configuration
underneath the linked object changes, the library node will show
matching sensors accordingly.
Select Sensor Types
This option is visible only if filtering by type is enabled above. A list

of all sensor types is shown, currently available sensor types are
shown in bold letters for your convenience. Set a check mark in
front of each sensor type you want to include in the library node
view. You can also select and deselect all items by using the check
box in the table head.
Note: You cannot filter for sensor types that are defined in PRTG
mini probes.
Filter By Status

Choose between:
Show all sensor st at es: Do not filter for a sensor status.
Show sensors wit h a specific st at us only : Filter the sensor list
of the linked object for sensors in certain states.
Select Sensor States
This option is visible only if filtering by sensor state is enabled

above. A list of sensor states is shown. Set a check mark in front
of each status you want to include in the library node view.
Choose from:
Unknown
Up
Warning
Down
Paused
Unusual
Down (Acknowledged)
Down (Part ial)
2780
31.08.2015


in the table head.
Filter By Tags

Choose between:
Show all sensor t ags: Do not filter for a tag.
Show object s wit h specific t ags only : Filter the sensor list of
the linked object for sensors with a certain tag. See section
Tags 96 for details.
Note: The tag of a sensor can also be inherited 94 by a parent
object.
Select Tags

Enter one or more tags of sensors that you want to include in the
library node view. You can also use plus (must have) and minus
(must not have) signs to categorize tags, for example, +snmp;wmi
(must have the tag snmp and must not have the tag wmi). See
section Tags 96 for details.
Filter By Priority

Choose between:
Show all priorit ies: Do not filter for the priority setting
sensor.
182
of a
Show object s wit h specific priorit y only : Filter the sensor list
of the linked object for sensors with specific priority. Note: The
priority setting of a group, device, or sensor is ignored here; only
the priority setting of the sensor itself is regarded.
Select Priority

Define which priority setting sensors must have to appear in this
collection. Set a check mark in front of each priority you want to
include in the library node view. Choose from:
***** (highest )
****
***
**
31.08.2015
2781


* (lowest )
Note: After applying filters it might take several seconds for the changes to become visible.
This is due to internal filter processes running in the background.
Management
Click on the Management tab to edit the contents of your library, for example, to add items to
the library using drag&drop. For detailed descriptions, please see Management 2777 section.
Settings
Click on the Set t ings tab to open a library's general settings.
BASIC LIBR AR Y SETTINGS

Library Name
Enter a meaningful name for the library.
Tags

example, you can use tags later to search for the library. Tags
entered here are inherited 94 to all library nodes underneath. Tags
are not case sensitive.
2782
31.08.2015

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Note: When giving access rights to a user group, all members of this user group will be able to
see the objects in the library just as seen by the user who originally created the library.
Notifications
You can define notification triggers for any kind of object libraries. This is even possible for
dynamic libraries which can change with every scanning interval, for example, when you filter a
library for the sensor status or priority. For details about how to use notifications, please see
section Not ificat ions 2759 .
Comments
31.08.2015
2783

History
Delete
You can delete the entire library any time by clicking on the trash symbol on the right.
2784
31.08.2015

4 Context Menus
7.9.4
Context M enus
On right-click, there are different context menus available.
Library Node Menu

While in the Overview or the Management tab, right-click on any library node to show its
context menu.
Library Node Menu
Select either Det ails... or Edit | Set t ings... to get to the Libraries and Node Set t ings
Note: While in the Overview tab, these settings are also accessible via left-click on the
node's name.
2779
Edit | Rename... will give you an option to rename the library node quickly.
Remove from Library ... will remove this library node from the current library. Note: This will
not delete any objects in your device tree.
The Move | ... options will move the library node up and down within the library.
Click on the Send Link by email entry to open a new email using your system's standard
email client. It will contain a direct link to the page you're currently viewing.
Monitoring Objects Menus

In libraries there are the same Cont ext Menus 186 available you already know from the device
tree. With one exception: While accessing these menus within libraries, the Move and Delet e
options are disabled to avoid accidental changes to your device tree.
15.10.2015
2785
Part 7: Ajax Web InterfaceAdvanced Procedures | 10 Reports
7.10
Reports
You can use reports to analyze historic monitoring results over a specified time such as one or
more days, one month, or an entire year, and for your system configuration. You can create
reports for all or only for certain sensors.
Introduction
PRTG includes a powerful reporting engine for the ad-hoc as well as scheduled report
generation in HTML, PDF, CSV, and XML format. This means that you can run reports on
demand or on a regular basis (for example, once a day or once a month). Furthermore, you can
create reports for a single sensor or for a whole range of sensors. It is also possible to create
HTML reports of your system configuration 2789 .
The content and layout of the report is controlled by the report template of your choice and is
the same for all sensors in a report. The report time that is shown in data tables and data
graph legends depends on the system time of your PRTG core server, not on the timezone
settings 2893 of the current user account.
Report Sample
The sample report above shows the report data for devices on a local probe. You can see
graphs for the preceding week, plus data tables with numeric results.
Start Reports
Click the Report s entry in the main menu 209 to view or add reports of your monitoring data.
Point on Report s to show other menu items. Choose between:
2786
21.01.2016
R EPOR TS
All
Open the Reports overview page where you can view or add
reports of your monitoring data.
Add Report
Select Report
Open an existing report. Point on Select Report to show other

select a report.
Configurat ion
Report s
Create reports for maps, reports, users & user groups, and system
configuration to document changes to the configuration. Point on
Report s | Configurat ion Report s to see the available
configuration reports 2789 .
2790
a new report.
Reports Overview
List of Reports
In the All view, you see a list of all existing reports for monitoring data. Every line shows
information about one report:
Object : Shows the name of the report.
21.01.2016
2787
Templat e: Shows the name of the template that this report uses.
Securit y Cont ext : Shows the user account that PRTG uses to run the report.
Period: Shows the time span that the report covers.
Schedule: Shows if you set a schedule to regularly execute the report automatically.
Email: If you set a schedule and an email address in the report settings, this shows the email
address to which PRTG sends the report automatically.
St at us: Shows the current status of the report.
Next Run: If you set a schedule in the report settings, this shows when PRTG runs the
report the next time.
Last Run: If you set a schedule in the report settings, this shows when PRTG ran the report
the last time.
Number of Sensors in Last Run: Shows about how many sensors the report includes data.
Using the buttons at the end of a row, you can Edit , Clone, and Delet e a report.
Click the Add Report button to add a new report, or click the name of an existing report to
view and edit its settings. You can also run a pre-configured report easily by clicking its name
and then using the options in the Run Now tab. For both options, please see the Report s
St ep By St ep 2790 section.
Note: You can run configuration reports
2786
only via the main menu.
Working With Reports

For detailed information on how to create, edit, and schedule reports, please see the following
sections:
Report s St ep By St ep
2790
View and Run Report s
2794
Report Set t ings
2798
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.
2788
21.01.2016
TIME SPAN IN R EPOR T
MINIMU M LEVEL OF DETAIL (AVER AGE

INTER VAL)
Up to 40 days
Any
40 to 500 days
60 minutes/1 hour or larger
A report for a time span of more than 500 days is not possible. If you try to set a larger time
span, it will be reduced to 365 days automatically.
Configuration Reports
Configuration reports are a special type of reports and show the current PRTG configuration.
They are available for Maps, Report s, Users & User Groups, and Sy st em Configurat ion. PRTG
generates configuration reports and displays them in a new browser window as an HTML page
in the common PRTG report style (like, for example, Hist oric Dat a Report s 146 of sensors).
You can use configuration reports, for example, to file and document changes to the
configuration of your PRTG installation.
Configuration reports contain the same information as you can see on the overview pages of
Maps 2810 , Report s 2786 , as well as on the system administration tabs User Account s 2890 and
User Groups 2896 . The configuration report Sy st em Configurat ion includes the current system
administration settings of the tabs User Int erface 2860 , Monit oring 2871 , Not ificat ion Delivery
2877 , Core & Probes 2883 , and Clust er 2905 . Configuration reports are interactive so you can click
on available links to go to the corresponding webpage in the PRTG web interface.
Related Topics
21.01.2016
137
146
2789

1 Reports Step By Step
7.10.1 Reports Step By Step

To create a new report or to run an existing one, follow the steps in this section. In the PRTG
web interface, click on the Report s entry in the main menu to show the reports main screen.
Quick Start: Run an Existing Report

PRTG is delivered with several pre-configured reports. To use one of them, click a report's
name in the reports main screen and select the Set t ings tab. The next steps are the same as
for completely new reports. Although some settings are already given, we recommend that
you check them. For example, check the sensors that are included in the report. For some
reports that come with PRTG, there are no sensors added yet. Continue with St ep 3: Define
Addit ional Opt ions 2791 in this section.
Step 1: Add Report

Click the Add Report button to add a new report. An assistant appears where you can define
various settings. First, enter a meaningful Report Name.
2790
21.01.2016

Add Report Assistant

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/add_report.png
Step 2: Select a Template

In the Templat e option, select one of the report templates from the list. This defines the
overall look of your report and how detailed (regarding the intervals) monitoring data is
included. For a detailed description of the available template options, please see the Report
Set t ings 2798 section. If you are not sure yet, try a template that appears most suitable to you.
You can still change all settings later.
Step 3: Define Additional Options

Select a Securit y Cont ext (best choose PRTG Sy st em Administ rat or, if available), your
Timezone, and the Paper Size for PDF generation. For detailed information, please see the
Report Set t ings 2798 section.
21.01.2016
2791

Step 4: Select Nodes and Sensors

Choose the sensors you want to include in the report. When running a cluster 87 , define the
Clust er Node the monitoring data is taken from first. Select a specific node from the list. If you
select All nodes, PRTG creates a report with data from all of your cluster nodes, but only the
primary channel of every sensor appears in the report.
Every report shows monitoring results based on sensor data. There are two ways to include
sensors in a report: You can either add sensors manually or by tag. In the Add Sensors by
Tag field, enter one or more tags that match the sensor range you want a report for.
For example, enter the tag bandwidthsensor to include all sensors that measure bandwidth (or
select it from the list of tags which PRTG suggests). PRTG provides this tag by default when
you add any bandwidth sensor, so the tag typically gathers all bandwidth sensors, unless you
configured your system differently. You can enter several tags. Hit the enter key, or insert
comma or space after each tag and enter the next one. Use the Filt er Sensors by Tag field to
explicitly filter sensors with certain tags from the bulk of tags or manually selected sensors
defined above.
Tagging is a great option to group sensors or other objects. For more information, see the
Tags 96 section. You can also leave the tag fields empty and only choose specific sensors
manually later.
Step 5: Decide on a Schedule and Additional Settings

In the Report Schedule section, choose if you want to run the report on a regular basis or on
demand only. Also define which time Period will be covered by the report, and if you want to
show percentiles, or add report comments or special access rights. For detailed information,
please see the Report Set t ings 2798 section.
Note: Scheduled reports are not executed on failover nodes
3122
by default.
Step 6: Check and Adjust the Sensors Included

After saving the settings, switch to the Sensors Select ed by Tag tab to see a list of all
sensors that you added with the tag(s) you defined in step 4. To change tags, go back to the
Set t ings tab. You can additionally add sensors manually. To do so, switch to the Select
Sensors Manually tab. See the Report Set t ings 2807 section for detailed information. The final
report shows sensors from both manual and by tag selection.
2792
21.01.2016

Step 7: Run Report

Switch to the Run Now tab, select a period, and in the Processing Opt ions select View
Report as HTML. Click the Run Report button. PRTG generates the report in a new browser
window or tab immediately. Depending on the number of selected sensors and the used
template, it may take a few minutes until you see the report. If you do not want to wait, close
the newly opened browser window or tab and select a PDF option in the Processing Opt ions.
Click on the Run Report button again. The report is then generated in the background and
you get a ToDo t icket or email once it is finished.
Note: For large PDF reports, PRTG automatically splits the output into separate files to avoid
huge PDF files. You can change the number of sensors which PRTG includes into each PDF file
by editing the report templates manually. See the More 2809 section of Report Settings 2798 .
21.01.2016
2793

2 View and Run Reports
7.10.2 View and Run Reports

In the web interface, click the Report s entry in the main menu to show the reports main
screen. Click a report's name to select it. Using the reports tabs you can access all
functionalities and settings for this report. Click the Go t o all report s button at the bottom of
the page to return to the list of Report s.
Report Tabs
Run Now
On the Run Now tab you can execute a report immediately with the settings configured.
R U N R EPOR T "[Name]"
Report for
Define the time span covered by the report. Choose between:

Current Period: Use monitoring data of the current period. The
actual time span depends on the report period type defined in
the report's settings 2798 . It can be today, this week, this month,
or this year.
Previous Period: Use monitoring data of the last period. The
actual time span depends on the report period type defined in
the report's settings 2798 . It can be yesterday, last week, last
month, or last year.
Select a Period: Use monitoring data of a period other than
current or previous. Select below.
Select Dat e Range Manually : Define a custom time span for the
monitoring data that will be used. Set start and end date below.
Date Range
This selection is only visible if you enable the period option above.
From the list, select a data range for which PRTG will generate the
report. The shown time spans depend on the available monitoring
data and on the report period type defined in the report's settings
2798 . It can be days, weeks, months, or years.
Start Date
This selection is only visible if you enable the date range option
above. Define the begin of the time span for which PRTG will
generate the report. Use the date time picker to enter the date
and time. Make sure you define a valid period.
2794
15.04.2016

R U N R EPOR T "[Name]"
End Date
above. Define the end of the time span for which PRTG will
generate the report. Use the date time picker to enter the date
and time. Make sure you define a valid period.
Quick Range
above. Choose between different pre-defined ranges by simply
clicking the desired range. Each click changes the St art and End
Dat e fields above accordingly.
PR OCESSING OPTIONS
File Format and
Delivery
Define how you want to view the report. Choose between:

View Report as HTML: Directly view the report in your web
browser. PRTG loads it in a new browser window or tab.
Creat e and st ore PDF and dat a files (available for t emplat es
wit h dat a t ables): Create a PDF file and, depending on the Dat a
Files settings of the report, CSV and XML files of the report and
store them. Once finished, you will find it in the St ored Report s
tab and a ToDo ticket 172 will be created. By default, PRTG sends
out a notification email to the administrator in this case.
Note: CSV and XML data files are only generated for report
templates that include data tables.
Creat e PDF and dat a files (available for t emplat es wit h dat a
t ables), st ore t hem, and send by email: Create a PDF file and
CSV and XML files of the report, store the files, and send them
via email once finished.
Note: CSV and XML data files are only generated for report
templates that include data tables.
Note: For large PDF reports, PRTG will automatically split the output
into separate files to avoid huge PDF files. You can change the
number of sensors included into each PDF file by editing the report
templates manually. See More 2797 section below.
Note: To create PDF files, ensure the print spooler service is
running on the system with your PRTG server.
Data Files
This option is only visible if you select the send by email option
above. Define if you want to generate and send CSV and XML files
for data tables in the report in addition to the PDF. Choose
between:
Do not include dat a files: PRTG will not generate CSV or XML
files for the report and only send the PDF file.
15.04.2016
2795

PR OCESSING OPTIONS
Include CSV files only (available for t emplat es wit h dat a
t ables): PRTG will generate and send CSV files in addition to the
PDF. CSV data files are only generated if the report uses a
template with data tables.
Include X ML files only (available for t emplat es wit h dat a
t ables): PRTG will generate and send XML files in addition to the
PDF. XML data files are only generated if the report uses a
Include all dat a files (available for t emplat es wit h dat a
t ables): PRTG will generate and send CSV and XML files in
addition to the PDF. CSV and XML data files are only generated if
the report uses a template with data tables.
Note: The Dat a Files option you select in the settings of this
report does not apply if you send the report via email.
Target Email Address
above. Enter a valid email address to which PRTG will send the
report.
Note: You can change the configuration for outgoing emails in the
Sy st em Administ rat ionNot ificat ion Delivery 2877 settings.
Compression
above. Define if you want to compress the attached report files
before sending. Choose between:
Send files uncompressed: PRTG will not compress the report
files before they are sent by email but send the files in their
original size.
Send all in one ZIP file: PRTG will compress the report files to a
ZIP file before they are sent by email.
Click the Run Report button to start report generation. Depending on the number of selected
sensors, this may take a while. If you experience a long waiting time when generating HTML
reports for immediate view, please consider using one of the PDF options. You can then view
the report as soon as it has finished.
Note: Any sensor graph in your report will only show the channels that are enabled via the
Show in Graphs option in the Sensor Graph Set t ings 2711 of the corresponding sensor.
Note: Reports cannot show uptime or downtime data for the Sensor Fact ory Sensor
2796
1374
15.04.2016

Stored Reports
In the St ored Report s tab you can view all PDF reports and data files created in the past. Click
a name to open the report. Reports are stored until they are deleted according to the data
purging settings of your PRTG configuration. You can set data purging limits for reports in the
Sy st em Administ rat ionCore & Probes 2887 settings.
Other Tabs
For all other tabs, please see the Report Set t ings
2798
section.
More
Knowledge Base: Can I change the number of PDFs created by a report?
Knowledge Base: Why is there missing data in historical data reports?
15.04.2016
2797

3 Report Settings
7.10.3 Report Settings

In the web interface, click the Report s entry in the main menu to show the reports main
screen. Click a report's name to select it. Using the reports tabs you can access all
functionalities and settings for this report. Click the Go t o all report s button at the bottom of
the page to return to the list of Report s.
Report Tabs
Run Now
On the Run Now tab you can execute a report immediately with the settings that you
configured before. Please see View and Run Report s 2794 section for details.
Stored Reports
On the St ored Report s tab you can view reports created in the past. Please see View and
Run Report s 2797 section for details.
Settings
Click the Set t ings tab to open the settings of a report.
BASIC R EPOR T SETTINGS

Report Name
Enter a meaningful name to identify this report. The name of the

report is used in reports lists 209 and as headline of generated
reports.
Tags

example, you can use tags later to search for the report. Tags are
not case sensitive.
Template
Select a template for the report. The template defines the overall
look of your report and in which detail (interval) the report shows
monitoring data. PRTG includes several report templates out of the
box. You can choose from templates in the following categories:
2798
11.03.2016

3 Report Settings

Dat a Table Only : Create a report with data tables only. Choose
from several intervals. Reports with this template also generate
data files (CSV and XML) if set in the Dat a Files section of the
report.
Graph Only : Create a report with graphs only. Choose from
several intervals. Reports with this template cannot generate
data files (neither CSV nor XML).
Graph wit h Dat a Table: Create a report with graphs and data
table. Choose from several intervals. Reports with this template
also generate data files (CSV and XML) if set in the Dat a Files
section of the report.
List of Sensors: Create a report in a compact sensor list style.
This is available with and without graphs. Reports with this
template cannot generate data files (neither CSV nor XML)
Top 10 Upt ime/Downt ime: Create a report with up to 10
objects with the highest uptime and downtime each. You can
choose between data in percent and hours. Reports with this
Top 100 Highest and Lowest : Create a report with up to 100
objects with the highest and lowest average values. Choose
from different intervals. Reports with this template cannot
generate data files (neither CSV nor XML)
Top 100 Upt ime/Downt ime: Create a report with up to 100
objects with the highest uptime and downtime each. You can
choose between data in percent and hours. Reports with this
Monitoring data within an interval is averaged. See also the
comment on data averaging in the Report s 2788 (Automatic
Averaging) section. For information on how to modify templates,
Security Context
Define the user account 2890 that you want to use for access to
your monitoring data. The report only contains objects which the
selected user 101 is allowed to view. Choose a PRTG user from the
list. The available users depend on your configuration. By default,
this is the user that created the report. PRTG System Administrator
users can change this setting.
Timezone
Define the time zone to use for all date-specific settings in this
report (see below). Choose a time zone from the list.
Paper Size
Define the paper size in which PDF reports are created. Choose
between:
11.03.2016
2799

3 Report Settings

None: Do not specify a paper format. The size is set
automatically.
A4: Use German DIN A4 format.
A3: Use DIN A3 format.
A2: Use DIN A2 format.
Legal: Use North American legal paper format.
Let t er: Use North American letter paper format.
Ledger: Use North American ledger paper format.
Orientation
Define the page orientation for the data in PDF reports. Choose
between:
Port rait : Use portrait mode for the page orientation.
Landscape: Use landscape mode for the page orientation. The
landscape format is designed to properly show data tables of
sensors with many channels. Other parts of the report will
remain in portrait mode and do not re-size to the landscape
format.
SENSOR S ("WHAT SENSOR S WILL BE INCLU DED IN THE R EPOR T?")

Cluster Node
This field is only visible when you run PRTG in Clust ering 87 mode.
Define the cluster node from which the report takes monitoring
data. Choose a cluster node from the list. The available options are
specific to your configuration. Select All nodes to create a report
with data from all of your cluster nodes.
Note: A report for all nodes includes data of the primary sensor
channels only, not for other sensor channels.
Note: If you select a failover node, report and data files will not
show data from the local probe or from a remote probe and might
be empty or show "0" values.
Note: You can generate CSV and XML data files only for a single
failover node. If you choose the option All nodes, the report will
not create data files!
2800
11.03.2016

3 Report Settings
SENSOR S ("WHAT SENSOR S WILL BE INCLU DED IN THE R EPOR T?")

Add Sensors Manually
If you want to manually choose the sensors included in this report,

please save settings and switch to the Select Sensors Manually
2807 tab.
Add Sensors by Tag
Define the sensors included in this report by tag 96 . Enter one or

more tags. The report covers all sensors that have at least one of
the tags. Please enter a string or leave the field empty.
You can also use plus (must have) and minus (must not have) signs
to categorize tags, for example, +snmp;wmi (must have the tag
snmp and must not have the tag wmi). See the section Tags 96 for
details.
Note: Tags are inherited 96 automatically. So, for example, if you
enter the tag of a group 90 here, the report will include all sensors
within this group. For detailed information, see the Inherit ance of
Set t ings 94 section. For sensors you add by tag, the report
includes all sensor channels automatically, except if you run a
PRTG cluster 87 and select All nodes in the Clust er Node
selection above.
Filter Sensors by Tag
Filter the included sensors further. This option works best in

combination with manually added groups and devices. From the
sensors that are implicitly added because of their parent objects,
the report includes only the ones with the tags you enter here.
Enter one or more tags to include sensors in the report. Confirm a
tag with enter, space, or comma key. Please enter a string or leave
the field empty.
You can also use plus (must have) and minus (must not have) signs
to categorize tags, for example, +snmp;wmi (must have the tag
snmp and must not have the tag wmi). See the section Tags 96 for
details.
SCHEDU LE
Report Schedule
Define at which time you want to run the report. Choose between:
No schedule (run int eract ive/on-demand only ): Only use the
options on the Run Now tab to start generating this report
manually.
Every full hour: Run this report every 60 minutes.
Every day at a specific hour: Run this report every 24 hours.
11.03.2016
2801

3 Report Settings
SCHEDU LE
Every specific day of a week: Run this report every 7 days.
Specify the day below.
Every specific day of a mont h: Run this report on a specific
day every month. Specify below.
The day aft er a quart er is finished (i.e. at 1. April for t he 1.
January - 31. March Quart er): Run this report for every quarter
of the year.
Every specific dat e: Run this report on a specific date every
year. Specify below.
Specify Hour
This setting is only visible if you select a specific hour above. From
the list, select the hour you want to run the report at. PRTG
automatically chooses a suitable time within this hour, usually at
the beginning of it.
Specify Day
This setting is only visible if you select the day of week or day of
month option above. From the list, select a day of week or a date
of the month you want to run the report. If you select Last , the
report will always run 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, February 31st , PRTG will
automatically run the report on the last day of this month.
Specify Date
This setting is only visible if you select the specific date option
above. Enter a valid date in the format DD.MM., for example, 31.12.
The report runs annually on this date.
Scheduled Processing
This setting is only visible if you select one of the schedule options
above. Define what to do with a finished report. Choose between:
Save report t o disk and send it by email: Create a PDF file
and, depending on the Dat a Files 2806 setting, data files of the
report, store it, and send it via email. You find the report in your
emails and on the St ored Report s tab. Define an email address
below.
Save report t o disk only : Create a PDF file and, depending on
the Dat a Files 2806 setting, data files of the report and store it.
Once finished, you find them on the St ored Report s tab. You
receive also a ToDo ticket 172 from PRTG. By default, PRTG sends
out a notification email to the administrator in this case.
Send report by email only : Create a PDF file and, depending on
the Dat a Files 2806 setting, data files of the report and send them
via email once finished. With this option the report is not
permanently stored in PRTG. Define an email address below.
2802
11.03.2016

3 Report Settings
SCHEDU LE
Note: For large PDF reports, PRTG automatically splits the PDF into
separate files to avoid huge PDF files. You can change the number
of sensors included into each PDF file by editing the report
templates manually. See the More 2809 section below.
Email Address
This setting is only visible if you select a send by email option

above. Enter a valid email address to which PRTG sends the report.
To enter more addresses, separate them by comma. PRTG sends a
message with all recipients in the "To" field of the email.
Note: You can change the configuration for outgoing emails in the
Sy st em Administ rat ionNot ificat ion Delivery 2877 settings.
Send to User Group

above. From the list, choose a user group to send an email with
the report to all members of this group. You can edit user groups
in Sy st em Administ rat ionUser Groups 2896 .
Note: If you define individual email addresses (see field above) and
a user group, PRTG will send the report to the individual email
addresses as well as to the members of the selected user group.
In both cases, PRTG will send one message with all recipients in the
"To" field of the email.
Compression

above. Define if PRTG will compress the attached report files
before sending them out. Choose between:
Send files uncompressed (default ): PRTG sends the report files
by email in their original size.
Send all in one ZIP file: PRTG will compress the report files to a
ZIP file before they are sent by email.
PER IOD
Reported Period
Define the time span the report covers. Choose between:

Current : Use monitoring data of the current period. Define the
period type below.
Previous: Use monitoring data of the last period. Define the
period type below.
11.03.2016
2803

3 Report Settings
PER IOD
Report Period Type
Define the type of period you want to create a report for. Choose
between:
Day
Week
Mont h
Quart er (January -March, April-June, et c.)
Year
Depending on your selection, different period selections are
shown below.
Day Period
This setting is only visible if you select day period type above.
Define the hours when a day starts and ends. Choose from the list
of hours. Default setting is 0:00-23:59.
Week Period
This setting is only visible if you select week period type above.
Define when the week starts and ends. Choose between:
Monday -Sunday : A reported week starts on Monday.
Sat urday -Friday : A reported week starts on Saturday.
Sunday -Sat urday : A reported week starts on Sunday.
Month Period
This setting is only visible if you select month period type above.
Define when the month starts and ends. Choose between:
1.-last day : A reported month starts on the first and ends on
last of the month.
15.-14.: A reported month starts on 15th and ends on 14th of
the month.
Year Period
This setting is only visible if you select year period type above.
Define when the year starts and ends. Choose between:
1/1-12/31: A reported year starts on January 1st.
7/1-6/30: A reported year starts on July 1st.
Report only for specific Include certain time spans within the defined period only. If a
hours-of-day
schedule is selected, the report will include only monitoring data
(Schedule)
for specified hours or weekdays within the defined period. Select
None to include all available monitoring data in the report, or
choose a schedule.
2804
11.03.2016

3 Report Settings
PER IOD
For example, select the schedule Weekday s to exclude all
weekends from the report. The available schedules depend on
your configuration. For more information, please see the Account
Set t ingsSchedules 2856 section.

Percentile Results
Define if you want to include an additional percentile calculation

of your data in the report. Choose between:
3107
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,
which shows percentiles for every sensor channel.
Note: 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 if in a cluster setup you
choose the option All Nodes in the Cluster setting in the sensor
section above.
Percentile Type
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.
Percentile Average
Interval
Enter a value to define the averaging interval on which PRTG bases
the percentile calculation. The default value is 300 (seconds),
which is equivalent to 5 minutes. This means that PRTG takes 5
minute averages as basic values for the percentile calculation.
Percentile Mode
Choose the mode for percentile calculation:
Discret e: PRTG takes discrete values to calculate percentile
results.
11.03.2016
2805

3 Report Settings

Cont inuous: PRTG interpolates between discrete values and
bases the calculation on interpolated values.
DATA FILES
CSV / XML Files
Define if you want to generate CSV and XML files for data tables in
the report in addition to the PDF. Choose between:
Do not include dat a files: PRTG will not generate CSV or XML
files for the report but only a PDF file.
Include CSV files only (available for t emplat es wit h dat a
t ables): PRTG will generate and store CSV files in addition to the
PDF. CSV data files are only generated if the report uses a
Include X ML files only (available for t emplat es wit h dat a
t ables): PRTG will generate and store XML files in addition to the
PDF. XML data files are only generated if the report uses a
Include all dat a files (available for t emplat es wit h dat a
t ables): PRTG will generate and store CSV and XML files in
addition to the PDF. CSV and XML data files are only generated if
the report uses a template with data tables.
Note: The option you select here does not apply if you send the
report via email on demand from the Run Now tab. You can define
there if you want to send data files along with the PDF.
Note: If you run PRTG in a cluster, the report will not generate data
files if you select All nodes in the sensors selection 2800 above.
Please specify a single failover node to get data files.
R EPOR T COMMENTS
Introduction
Enter a custom text that will show up on the first page of the
report. Please enter a string or leave the field empty.
Footer Comments
Enter a custom text that will show up at the end of the report.
Please enter a string or leave the field empty.
2806
11.03.2016

3 Report Settings
ACCESS R IGHTS
User Group Access
settings.
settings.
Select Sensors Manually

Click the Select Sensors Manually tab to manually choose sensors that you want to include
in the report. You see a split screen: On the left side, there is a list of objects that the report
already contains (empty in the beginning), and on the right side, you see a less colorful view of
your device tree, like on the Management 258 tab in the device tree. You can add objects to the
report using drag and drop.
11.03.2016
2807

3 Report Settings
Manual Selec tion for Reports
Add It ems
From the device tree on the right side, drag objects and drop them on the list on the left
side. This can be entire probes, groups, devices, or single sensors. Each dropped object is
added immediately as a new list item. Repeat this procedure as often as you wish until you
have added all desired items to the report.
Note: The objects you drop on the left side are always added to the end of the list, you
cannot add objects directly in another order.
Select Sensor Channels
If you add a sensor to the selection, you can specify the sensor channels that the report will
include. By default, all channels are selected. To exclude a channel from the report, remove
the check mark in front of a channel name.
Note: If you run a PRTG cluster 87 , you can only choose between single channels if you
select one specific Clust er Node in the report settings. If you select All nodes the report's
Clust er Node setting, the channel selection is not available and the report contains only the
primary channel of each sensor.
Change Order
You can change the order of manually selected objects on the left side with drag and drop.
Each item you add appears at the end of the list by default. To change the order, point to the
drag and drop symbol (two arrows) in the upper right corner of a selected item, drag it to the
desired position, and drop it there.
Remove
To remove any objects from the report, click the trash can symbol next the respective list
item, or select several list items while holding down the Ctrl key and click on the green trash
symbol appearing at the top of the list.
2808
11.03.2016

3 Report Settings
Your selection is saved automatically, and there is no undo function.

Note: The final report will include both sensors selected manually and those selected by tag.
Sensors Selected by Tag

Click the Sensors Select ed by Tag tab to view all sensors that are added to the report
depending on the Add Sensors by Tag setting of the report. In the table list 178 , you see all
sensors that you added to the report by their respective tags. This is for your information only,
you cannot change sensors here. However, you can switch to the Set t ings tab of the report
and change the tags that the report uses to include sensors. Additionally, you can also
exclude sensors with certain tags there. The final report will include both sensors selected
manually and those selected by tag.
For sensors that you add by tag, all sensor channels are included in the report automatically,
except you use a PRTG cluster 87 and select All nodes in the Clust er Node selection of the
report. In this case, the report includes only the primary channel of each sensor.
Note: The final report will include both sensors selected manually and those selected by tag.
Comments
More
Knowledge Base: Can I change the number of PDFs created by a report?
Knowledge Base: How do I modify PRTG's report templates?
Knowledge Base: How can I show full channel names below report graphs?
Manual Section: Calculat ing Percent iles
11.03.2016
3107
2809
Part 7: Ajax Web InterfaceAdvanced Procedures | 11 Maps
7.11
Maps
With PRTG's Maps feature (some people might call this 'dashboards') you can create web pages
with up-to-the-minute monitoring status information in a customizable layout. Using this unique
concept, you can also make your overview pages of live data publicly available, if you like.
Example of a PRTG Map
In this section:
Int roduct ion
St art Maps
2810
2811
Maps Overview
Maps Rot at ion
2812
2812
Working wit h Maps
2812
Introduction
There are countless possibilities for the implementation of maps. For example, you can use this
feature to:
Create network maps with status icons for each device on the map.
Create quick views of your network that can be shown on network operations center
screens.
2810
21.01.2016
Create a quick network overview for publishing on the Intranet, allowing at-a-glance
information for management of other employees.
Create a custom view of the most important sensors in your monitoring setup.
Create Top 10 lists of the sensors of a specific group or device.
Technically, a map is a usual HTML web page. You can build a schema of your network by
choosing from hundreds of device icons and connect them with lines. A map can consist of
the following elements:
A set of map items, which can include device icons, sensor status icons, graphs, data tables,
lists of sensors, connection lines, geographical maps, or custom HTML code.
An optional background image (a JPG, PNG, or GIF file, for example, your company logo, or a
graphical view of your network).
You can also specify the size of the map. Using the AJAX-based map editor, you can place the
items anywhere on the map, and you can also change their size. Each map has a unique URL
which you can use to link to the map. Users who want to access the map either need an
account in your PRTG installation, or can access a public URL of the map if you allow the Public
Access feature. Public maps contain a unique Map ID access key in the URL to block
unwanted visitors.
PRTG comes with several pre-configured standard maps which you can use right away. You can
also change or delete them, if you like. The following maps are automatically created when you
install PRTG for the first time (visible for the PRTG System Administrator 101 user):
Sample Dashboard: By default, this map shows a graphical structure of your device tree,
the sunburst view 129 of your device tree, a list of alarms 161 , a geo map 2753 , and more. This
sample map has a 5***** priority 182 so you can also open it under Home in the main menu
200 . To not show it in the main menu, define a lower priority.
Magic Map: By default, this map shows the sunburst view 129 of your device tree with
several graphics that demonstrate customization capabilities of the maps feature.
Start Maps
Click the Maps entry from the main menu 209 to view or add custom views of your network's
status and monitoring data. Hover over Maps to show other menu items. Choose between:
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
Select Map
Open an existing map. Hover over Select Map to show other

select a map.
21.01.2016
2814
a new map.
2811
Maps Overview
In the All view, you see a list of all existing maps. Using the links next to a map name, you can
perform the following actions.
Click the name of a map to view it.
Click the Edit button to adjust the settings of this map.
Click the Clone button to create an exact copy of this map. As soon as you click, the map is
cloned and the cloned map's settings are shown.
Click the Delet e button to remove this map.
Click the Add Map button to add a new map.
Define the priority 182 of a map. Maps with a 5***** priority appear in the main menu bar
under Home for direct selection (up to 10 entries).
200
Map Rotation
To show several maps in a rotation, mark the desired maps using multi-edit 2742 and then select
Map Rot at ion from the multi-edit menu. PRTG shows the selected maps in rotation on a new
page then. This requires login credentials for PRTG.
It is also possible to set up a public map rot at ion without login:
Allow public access in the settings
2823
of the desired maps.
Use the corresponding map IDs with its secret keys to build a URL that calls a public map
rotation.
The URL must have this format: the address of your PRTG server, followed by /public/
mapshow.htm?ids=.
Then list the IDs of the desired maps, each separated by a comma.
Each map ID has to be connected with its secret key using a colon: ht t p://yourprtgserver/
public/mapshow.ht m?ids=mapid1:secretkey1,mapid2:secretkey2,mapid3:secretkey3
While PRTG shows a map rotation, you can change the refresh interval any time when
hovering over the arrows symbol in the lower right corner. Choose between 10, 30, or 60
seconds, 10 minutes or Refresh now.
Working with Maps

For detailed information on how to create and edit maps, and to learn how to make them
accessible to others, please see the following sections.
Maps St ep By St ep
Map Designer
2812
2814
2816
21.01.2016
Maps Ot her Set t ings
21.01.2016
2823
2813

1 Maps Step By Step
7.11.1 M aps Step By Step

To create a new map, follow the steps in this section. In the web interface, click Maps in the
main menu bar 200 to show the maps main screen.
In this section:
St ep 1: Add Map
2814
St ep 2: Add Map It ems
2815
St ep 3: View and Share
2815
Step 1: Add Map

Click the Add Map button. An assistant appears. Enter a Map Name and define Map Lay out
settings (size and optionally a background image). in the Public Access section, define the
accessibility to your map without login.
For detailed information, see Maps Ot her Set t ings
2823
section (Settings).
Add Maps Assistant Step 1
2814
02.09.2015

1 Maps Step By Step
Step 2: Add Map Items

Click the Cont inue t o st ep 2 button to open the Map Designer. Select an object from the
device tree on the left, drag&drop an object from the items list on the right side, define further
properties of the item (mark it in the main window of the Map Designer and see section
Propert ies on the right), and confirm. The item appears on the map immediately. Repeat this
procedure as often as you wish until you have added all desired items to the map. Drag items
to change their position. Additionally, you can also draw connection lines between items or
edit existing items.
For detailed information, see Map Designer
2816
section.
Step 3: View and Share

Click the View Map tab to see your map. Later, PRTG will show it the way you see it there. If
available for an object, you can click most object names as well as all sensors. It depends on
the access rights of the object and the currently logged in user account if you can get more
detailed information about the object or an error message indicating insufficient access rights.
Click the Get HTML tab to get the direct URL of your map that you can share with others. For
detailed information, see Maps Ot her Set t ings 2826 section.
While showing a map, the single map items refresh in the refresh interval you define for this
map.
02.09.2015
2815

2 Map Designer
7.11.2 M ap Designer
In this section:
Use a Proper Browser
2816
Basic Design Concept
2816
Device Tree Select ion
2817
Propert ies Select ion
2818
Edit Exist ing Map It emsPropert ies Box

Edit Exist ing Map It emsHover Icons
2821
2821
Edit Exist ing Map It emsUsing Cursor Key s

Draw Connect ion Lines Bet ween It ems
Snap To Grid
More
2822
2822
2822
2822
Use the Proper Browser

Due to the map designer's extensive scripting capability, it is important that you use a
compatible browser when editing maps. We recommend that you use Google Chrome 49 or
later (recommended) or Mozilla Firefox 45 or later. You can use Microsoft Internet Explorer 11
as well. The map designer is not fully compatible with earlier versions of Internet Explorer or
Opera browsers.
Basic Design Concept

Click the Map Designer tab to open the editor. It might take a few moments to load (for
unresponsive script warnings, please see the More 2822 section below). Here, you can create
your map by adding or changing items. The designer screen consists of three main parts: The
Device Tree on the left side, the current Map in the middle, and the Propert ies on the right
side.
2816
03.09.2015

2 Map Designer
Map Designer
Each map item takes attributes from both selections.

Device Tree (left): Select the monitored object whose data you want to show on the map.
Propert ies (right): Define how to show the map item.
Simply drag and drop any object from either side onto the map, or double-click on an object.
You will always see all changes immediately.
Device Tree Selection

Use the Device Tree to select the monitored object whose data you want to show on the
map (this can be a probe, a group, a device, or a single sensor). To find the desired object you
have the following options:
Use the arrow symbols at the beginning of each line to open nodes in the device tree and
show objects below probes, groups, and devices.
Enter a few characters into the Search box in the upper left corner to search for names (or
part of names) of objects in your configuration. You will see the search results immediately.
Click the red x icon to clear your search.
03.09.2015
2817

2 Map Designer
Dev ic e Tree Selec tion in the Map Designer
No matter which method you choose to find the desired object, you can always drag any
object from the Device Tree onto a free area of the map to create a new map item.
If you drag it onto an existing map item, it replaces the existing item while Propert ies and
size stay the same.
You can also select a map item and double click a Device Tree object to replace the map
item. If no item is selected, double clicking an object adds a new map item.
To gain more space for map editing, reduce the size of the Device Tree box by dragging its
right border to the left. Drag it to the right to enlarge it again.
Properties Selection
Use the Propert ies selection to define how to show the map item (for example, as an icon, a
map, a table, or a graph). Select the appearance in different categories. Hover over a property
object to get a live preview of it (in most cases).
Note: If a certain Propert ies object is not available for the selected Device Tree object, you
will see a corresponding text note.
2818
03.09.2015

2 Map Designer
Properties Selec tion in the Map Designer
There are many different property object types available. Simply click one of the categories to
show all available types.
Default Icons A, Default Icons B
These categories offer a variety of iconic symbols of typical network devices in the current
PRTG style. Category A comes with object data which category B does not include.
Icons A, Icons B, Icons C
These three categories offer a variety of iconic symbols of typical network devices. Below
each icon you can see the object name and a sensor overview for the object. This shows
how many sensors are in which status 135 . For some sensors, a mini graph is shown as well.
Icons A (St at ic), Icons B (St at ic), Icons C (St at ic)
These three categories offer the same variety of iconic symbols of typical network devices
as the category described above. Here, no object data is displayed but only the icon.
St at ic Images
This category offers free or public domain geographical maps from different sources. For
additional geographical maps, please see the More 2822 section below. Use properties section
Geo Maps if you want to show PRTG Geo Maps 2753 in the map.
Note: The items in this section are independent from the selected Device Tree objects.
03.09.2015
2819

2 Map Designer
St at us Icons
This category offers options to insert status 135 icons in different styles. These show the
object name and an overview of how many sensors there are and their status. For example,
you can add "traffic lights" or the QR code of a monitoring object to your map. There is also
an object available for audible alert which will play a sound when the number of alarms of the
monitored object are > 0. Note that your browser must support playing embedded sounds
(see the More 2822 section below for further information) for this icon.
Clust er
If you use the PRTG Clust ering
cluster to your map.
87
feature, you can add icons that show the status of your
Dat a Tables
Choose from several table lists 178 that show sensor lists for the currently selected object.
You can also choose from several lists that show sensors in a certain status only.
Devices
Add several views of your device tree
select object.
129
to the map, including sensor gauges
137
for the
Geo Maps
In this category you can choose between a globe and a geographical map. You can see the
location of the currently selected object in the Device Tree on the map. To use this feature,
you must enable Geo Maps integration and you have to enter a Locat ion in the settings of
the monitoring object you want to use this with. For more information, please see the Geo
Maps 2753 section.
Note: If Geo Maps integration is disabled, you will only see white boxes instead of map
previews.
Graphs
This category offers different graph styles in several dimensions and detail. You can also
select graphs including a legend or sensor states.
Object s
Add some simple geometric shapes to your map. The items in this section do not depend on
the selected object in the Device Tree.
Top 10
Choose from several tables that show the top 10 sensors in certain categories, such as least
used CPUs, highest bandwidth usage, best availability, or slowest websites.
Cust om HTML
You can use this property, for example, to add external images or applets to your map. To
actually add custom HTML code to your map, add the item, and mark it to edit 2821 . You can
then copy your custom code into the HTML Before and HTML Aft er fields in the Propert ies
box on the right side.
No matter which object you choose, you can always drag any object from the Propert ies box
onto a free area of the map to create a new map item. If you drag it onto an existing map item,
it replaces this item, while its Device Tree object attributes and size stay the same. You can
also select a map item and double click an object in the Propert ies box to replace the map
item. If no item is selected, double clicking an object will add a new map item.
To gain more space for map editing, reduce the size of the Propert ies box by dragging its left
border to the right. Drag it to the left to enlarge it again.
2820
03.09.2015

2 Map Designer
Edit Existing Map ItemsProperties Box

Click a map item to select it. You can then edit its attributes using the fields in the upper part
of the Propert ies box on the right side:
Top, Left , Widt h, and Height fields
Enter position and size values for direct positioning. Click the Save button to save your
settings. Alternative: Use the mouse to move and resize a map item.
Lay er field
The layer number defines if an item appears on top of or behind another item if they overlap.
The item with the higher number appears on top. Enter a positive integer value and click the
Save button to save your settings. Alternative: Use the arrow symbols in the context menu
of a map item to Bring t o front or Send t o back an item one layer (see below).
Ext ernal Link
PRTG maps are interactive. You can define an address to any website here. If you click the
map item when viewing the map, PRTG open this page in a browser window. Enter the whole
URL to an external website (for example, https://www.paessler.com) or the address of a
subpage of your PRTG installation (for example, devices.htm).
HTML
Click the arrow symbol underneath to show the HTML Before and HTML Aft er fields. Any
HTML code you enter in these fields is added before or respectively after the map item. Enter
your custom HTML code that embeds an object and click the Save button. Your HTML object
is inserted into the map. For example, you can enter the code <img src="http://
media.paessler.com/common/img/logoclaim_r1.gif"> to insert an image of a Paessler logo.
Edit Existing Map ItemsHover Icons

Hover over a map item to show the edit icons for it.
Bring t o front (arrow up sy mbol)
Move this item one layer to the front. This is useful when adding several items to a map that
overlap each other.
Send t o back (arrow down sy mbol)
Move this item one layer to the back. This is useful when adding several items to a map that
overlap each other.
Delet e (t rash sy mbol)
Delete this item.
Note: Be careful! The item will be deleted immediately without notice and you cannot undo
this. Alternative: Select the item and press the Del button on your keyboard.
Drop Connect ions (scissors sy mbol)
If there are connection lines between two items, you can delete all lines starting from this
item. Connection lines will be dropped immediately.
03.09.2015
2821

2 Map Designer
Edit Existing Map ItemsUsing Cursor Keys

While an object is selected, use the cursor keys to move it one pixel at a time. Hold the Shift
key in combination with the cursor keys to move the object 10 pixels at a time.
Draw Connection Lines Between Items

You can draw connection lines between any map items via drag and drop. Click the gray
handles next to an item and drag a line to the item you want to draw a connection to. A line
between these items appears immediately. This can be useful to indicate network connections
or logical coherence between two items. To delete connection lines, click the scissors symbol
in the item's edit icons 2821 .
Lines between objects are colored dynamically. They are red as long as one of the object's
icons shows a red Down status. This only affects half of the line, at the end where the red
sensor is shown. If both objects connected show a red sensor, this results in a continuous
red line.
Snap to Grid
Select whether to use Snap To Grid or Don't Snap, using the buttons below the Device Tree
box. This affects how map items are positioned when adding or moving them via drag and
drop. The setting is active immediately. With snap to grid enabled, you can place items aligned
with the grid only.
More
Knowledge Base: Why does my browser show an unresponsive script warning while loading
the Map Designer?
Knowledge Base: How can I add or edit map objects used for PRTG's maps?
sound?
Knowledge Base: Where can I find custom map objects and other map customizations?
2822
03.09.2015

3 Maps Settings
7.11.3 M aps Settings

Using the Map tabs you can access all functionalities and settings for a map.
Map Tabs
View Map
Click on the View Map tab any time to show a preview of your map.
Map Designer
Click on the Map Designer tab to edit the contents of your map. Please see Map Designer
section.
2816
Settings
Click on the Set t ings tab to open a map's general settings. Note: When using the Add Map
dialog, not all of these settings are available. You can change them later by clicking on the
Set t ings tab.
BASIC MAP SETTINGS

Map Name
Enter a meaningful name for the map.
Security Context
Define the user account that will be used for access to monitoring
data. The map will only contain objects which the selected user 101
is allowed to view. Please choose a user from the list. The available
users depend on your configuration. By default, this is the user
that created the map. PRTG Administrator users can change this
setting.
Timezone
Define the time zone that will be used for all date-specific options
in this map. Select a time zone from the list.
Tag Filter
This setting affects table maps objects. Enter one or more tags
separated by space or comma to include sensors in tables. Only
sensors with one of the tags entered here will appear in this map's
data tablesincluding sensors which inherit 94 tags from parent
objects. Please enter a string or leave the field empty.
Note: Use with care! This setting will affect all tables of the current
map!
21.01.2016
2823

3 Maps Settings
MAP LAYOU T
Map Width
Define the width of the map in pixels. Please enter an integer

value.
Map Height
Define the height of the map in pixels. Please enter an integer

value.
Automatic Scaling
Define if you want the map to automatically adapt to your screen

size. Choose between:
Scale map view t o fit browser size: The size of the map adapts
automatically to the size of your screen. Choose this method if
the map is shown on various screens with different resolutions
so that it uses the available place in the browser window the
best possible way.
Do not aut o-scale map view: The map uses always the size
that you define above.
Note: When showing a map 2826 with enabled automatic scaling (/
mapshow.htm), you can disable the automatic scaling in this view
by adding the parameter &noaut oscale to the URL.
Background Picture
Define if you want to use a background picture for the map.

Choose between:
Use an image in t he background of t he map: Use a custom
background image that you define below.
Do not use a background image: Do not use a background
image.
Background Image
This option is only visible if you enable a background picture

above. Click on the Choose File button and select an image from
your computer or network.
Note: Only images in the format JPG, PNG, and GIF are supported.
The file size must be smaller than 2 MB. If you try to upload other
images, you get an error message. In a cluster, background images
are not automatically deployed to the other nodes! In order to
view maps on other nodes, copy the background pictures manually
to \webroot\mapbackground of the program directory on every
node. For detailed information on how to find this path, please
see Dat a St orage 3135 section.
Background Color
2824
Select a background color for this Map. Either enter a hex color
code or choose a color from the color selector. The hex color
code field will always display the currently defined color.
21.01.2016

3 Maps Settings
PU BLIC ACCESS
Public Access
Define if others can see the map. Choose between:

No Public Access: Do not allow public access to the map. Only
users with both a login to the PRTG web interface and sufficient
access rights can see the map.
Allow Public Access: Allow access to the map using a unique
address. The URL contains a key that you can change below.
Secret Key
This field is only visible if public access is enabled above. The key is
automatically generated. It is part of the public URL for the map.
You can also enter a customized string. We recommend that you
use the default value. For more information on public access,
please see the Get HTML 2826 section. Note: The characters comma
"," and colon ":" are not allowed in the secret key field!
ACCESS R IGHTS
User Group Access
settings.
settings.
21.01.2016
2825

3 Maps Settings
Get HTML
Your PRTG map is like a standalone HTML page. You can make it accessible to others, if you
like. Depending on the Public Access setting 2823 of your map, a visitor needs to provide PRTG
user account login data to view the map, or sees the map immediately using a URL containing a
secret key. When using this unique key, you can also include your map on another webpage,
embedding it via <iframe>.
Opt ion 1: Link t o a web page wit h t he map t hat requires login credent ials
The shown URL requires login credentials in order to display the map. PRTG asks the user
trying to view the map via this URL for login credentials.
Note: In the URL, usually the IP address is given via which the page is available. Maybe a NAT
translation is set in your firewall, or you may want to use a domain name or a name from a
dynamic DNS service for public access. Please customize URL you use for access to your
needs.
Opt ion 2: Link t o a web page t hat display s t he map wit hout a login
To get the shown URL working for public access without a login, enable Allow Public
Access in the settings tab 2823 of your map.
needs.
Opt ion 3: Show a map inside ot her web pages using an IFRAME
For your convenience, this shows source code for adding an iframe to another webpage. It
includes a URL for direct access. Just copy the code and paste it into your webpage code.
Also enable Allow Public Access in the settings tab 2823 .
needs.
While a map is shown via these URLs, you can change the refresh interval any time by hovering
over the arrows symbol in the lower right corner. Choose between 10, 30, or 60 seconds, 10
minutes or Refresh now. The map adapts automatically to the size of the browser window if
you enable the auto-scaling setting 2823 .
Comments
History
2826
21.01.2016

3 Maps Settings
Delete
You can delete the entire map any time by clicking on the trash symbol on the right.
More
Knowledge Base: How to disable links in public maps?
PRTG Manual:
Dat a Report ing
21.01.2016
104
2827
Part 7: Ajax Web InterfaceAdvanced Procedures | 12 Setup
7.12
Setup
In the setup settings of the PRTG web interface, you can define almost all system settings for
PRTG. However, some of the machine-oriented settings are defined using two Windows
administration tools (see Ot hers 2829 section below).
In the main menu, click on Set up to show the available options.
Setup Ov erv iew Page
PRTG Status
PRTG St at usSy st em St at us
PRTG St at usClust er St at us
2907
2923
PRTG St at usLicensing St at us and Set t ings

PRTG St at usAut o-Updat e
2925
2918
Account Settings
Account Set t ingsMy Account
2830
Account Set t ingsNot ificat ions
2836
Account Set t ingsNot ificat ion Cont act s

Account Set t ingsSchedules
2852
2856
System Administration
Sy st em Administ rat ionUser Int erface
Sy st em Administ rat ionMonit oring
2828
2860
2871
24.03.2015
Sy st em Administ rat ionNot ificat ion Delivery

Sy st em Administ rat ionCore & Probes
2883
2890
2896
Sy st em Administ rat ionAdminist rat ive Tools

Sy st em Administ rat ionClust er
2877
2900
2905
Optional Downloads and Add-Ons

DownloadsClient App for Windows (Ent erprise Console)
DownloadsClient Apps for Mobile Devices
DownloadsRemot e Probe Inst aller
2928
2928
2928
2930
Support
Support Cont act Support
2932
Others
There are some settings that you have to make in the PRTG Administ rat ion Tool 3046 , running
as Windows application. For more details, please see sections PRTG Administ rat ion Tool on
Core Server Sy st em 3047 and PRTG Administ rat ion Tool on Remot e Probe Sy st em 3073 .
24.03.2015
2829

1 Account SettingsMy Account
7.12.1 Account SettingsM y Account

In the My Account settings you can define values regarding your (currently logged in) PRTG
user. All settings in this section are user-specific. Some account options may not available, but
restricted to the administrator.
Note: If you open the system administration page from another administration page and 15
minutes (900 seconds) have passed since your last credential-based login, you will be asked to
enter your credentials again for security reasons. A dialog box will appear. Simply enter your
Login Name and Password for PRTG in the corresponding fields, confirm and you're done.
My Ac c ount Settings
My Account Settings
2830
28.04.2016

U SER ACCOU NT
Login Name
Enter the login name for the user.
Display Name
Enter a name that the user recognizes. It will not be used for login
purposes.
Primary Email Address
Enter the user's email address.
Password
Define the user password. For security reasons, the account

settings page does not contain the password. Choose between:
Don't change
Specify new password
If you choose to specify a new password, enter the old password
and then the new password twice.
Note: The new password must be at least 8 characters long. It
must contain a number and a capital letter. The password of a PRTG
Administrator user can only be changed by this PRTG Administrator
user himself.
Passhash
Click Show passhash to display the passhash for the selected

user. You need the passhash of a user if you use the PRTG
Applicat ion Programming Int erface (API) 3086 . This setting is
shown for your information only and cannot be changed here.
ACCOU NT CONTR OL
Account Type
This setting is only visible to administrator users. However, it will

not shown if the user who's account you want to modify is a
member of a group with administrative rights.
Define the account type for the current user. Choose between:
Read/Writ e User: You can change settings.
Read Only User: You can not edit any settings except your own
password. This is a good choice for public or semi-public logins.
Note: This setting cannot be changed for the default administrator
user.
28.04.2016
2831

ACCOU NT CONTR OL
Allow Acknowledge
Alarms
This setting is only visible if read only user is enabled above.

Acknowledging an alarm is an action which requires write access
rights. However, you can explicitly allow this action to read-only
users. If enabled, they still do not have write access, but may
acknowledge alarms 162 . Choose between:
Allow: Allow acknowledging alarms for this user.
Deny : The user will not be able to acknowledge alarms.
Password Changes
Decide if you want the user to be able to change his account's

password or not. If you allow the user to change the password,
this option will be available in the My Account 2830 settings of the
respective user. Choose between:
User may change his account 's password
Deny t he right t o change t he password (default)
Note: This field is only visible if you edit this option for read-only
users as an administrator.
Primary Group
This setting is available only for administrator users. Select the

primary group for the current user. Every user has to be member of
a primary group to make sure there is no user without group
membership. Membership in other user groups is optional. For
user experience there is no difference between the primary and
other user groups.
Note: You cannot change the primary group of Active Directory
users. Users which you added with Act ive Direct ory Int egrat ion
3083 can only have this AD group as their primary group. If you need
to change this, please delete this user account and add it anew.
Status
This setting is only shown for administrator users. Define the

status of the current user. Choose between:
Act ive: The current user can login to the account.
Inact ive: The current user's login is disabled. Use this option to
temporarily deny access for this user.
user.
Last Login
2832
Shows the time stamp of the user's last login. This setting is shown
for your information only and cannot be changed here.
28.04.2016

U SER GR OU PS
Member of
Shows the groups the current user is member of. Access rights to
the device tree are defined on group level. This setting is shown
AU TO R EFR ESH AND ALER TING

Auto Refresh
Define if you want PRTG to reload web pages automatically for the
current user. Choose between:
Refresh pages (recommended): Automatically refresh the single
page elements on the web pages in PRTG.
No aut omat ic refresh: Do not automatically refresh web pages.
Auto Refresh Interval

(Sec.)
This setting is only relevant if you enable auto refresh above. Enter
the number of seconds that PRTG waits between two refreshes.
We recommend that you use 30 seconds or more. Minimum value
is 20 seconds.
Note: Shorter intervals create more CPU load on the server running
PRTG. If you experience load problems while using the web
interface (or PRTG maps 2810 ), please set a higher interval.
Play Audible Alarms
Define when an audible alarm will be played for the current user on
web pages whenever there are alarms 161 in PRTG. Choose
between:
Never: Do not play sound files on any web pages.
On dashboard pages only : When there are alarms, play a
predefined sound on dashboard 200 pages only. The sound
snipped will be played again with every refresh of the dashboard
page.
On all pages: When there are alarms, play a predefined sound on
all web pages. The sound will be replayed with every page
refresh.
For more information about audible notifications and supported
browsers, see the More 2835 section below.
28.04.2016
2833

WEB INTER FACE

Homepage URL
Define the user's default page, which is loaded after logging in or

clicking on the Home 200 button in main menu.
Max. Groups/Devices
per Group
In order to provide a fast and smooth user experience, PRTG

attempts to reduce page size when displaying the device tree. It
automatically collapses groups and devices when reaching a
specified number of items. Enter this threshold for groups and
devices here. We recommend values between 10 and 30.
Max. Sensors per

Device

specified number of items. Enter this threshold for sensors per
Timezone
Define the time zone for the current user. Depending on the time
zone you select here, PRTG shows the current user's local time
zone in all data tables and graph legends.
Note: PRTG receives the UTC (Coordinated Universal Time) from
the system time set on the PRTG core server for this purpose.
Date Format
Define the format of dates for the current user.

Note: This setting will take effect after the next login.
TICKET SYSTEM
Email Notifications
Define if you want to get emails from the ticket system. Choose
between:
I want t o receive an email whenever a t icket changes: You
will receive an email each time a ticket is assigned to you or your
user group, or if a ticket which is assigned to you or your user
group is changed.
Note: If you edit tickets which are assigned to you or your user
group, or you assign a ticket to yourself or your user group, you
will not get an email.
I do not want t o receive any emails from t he t icket sy st em:
You will not get any emails about tickets.
2834
28.04.2016

Notification Contacts
In the Not ificat ion Cont act s 2852 tab you can define recipients for each user account.
Recipients can be email addresses, phone numbers, or push devices (iOS, Android and
Windows Phone devices with the corresponding PRTG smartphone app 2995 ).
Comments
History
More
sound?
28.04.2016
2835

2 Account SettingsNotifications
7.12.2 Account SettingsNotifications

In the notification settings you can define and change notifications for the current PRTG user.
Notifications can be triggered for specific sensor states and values.
Notific ation Settings
Note
to send messages.
notifications.
2836
09.05.2016

2759
section.
Notifications Overview
Click the Not ificat ions tab to show a list of existing notifications. Using the buttons in the
column Links, perform the following actions to set up a notification:
Test : Trigger this notification immediately for testing purposes.
Note: When testing notifications, PRTG will not resolve the placeholders, but rather send the
original variables instead.
Pause: Pause this notification. If a notification is paused
when this notification is triggered.
Edit : Open the settings of a notification
2837
185
, PRTG will not send messages
to edit them.
Clone: Create an exact copy of this notification. The clone

list as Clone of [...]
2740
is added to the notifications
Delet e: Delete this notification (not possible for predefined notifications).

Used by : Show all objects which trigger this notification.
Notifications Settings
Click the Add new not ificat ion button to add a new notification, or click the name of an
existing notification to edit it.
BASIC NOTIFICATION SETTINGS

Notification Name
09.05.2016
Enter a meaningful name for the notification, for example, SMS to

service team or similar.
2837

BASIC NOTIFICATION SETTINGS

Tags
Enter one or more tags 96 . Confirm each tag with space, comma,
or enter key. You can use tags to group sensors and use tagfiltered views later on. Tags are not case sensitive. Tags will be
Status
Select the status of the notification. Choose between:

St art ed: This notification is active. PRTG executes this
notification when it is triggered.
Paused: Pause this notification. If a notification is paused, PRTG
does not execute this notification when it is triggered.
Schedule
Define for which intervals you want notifications to pause. You

might want the notifications to pause for scheduled maintenance
periods or regular server reboots at certain intervals. For
continuous notification select None. This selection will make your
notifications be active 24/7 without pause. You can also choose
one of the suggested schedules from the list. Usually schedules
define when this notification will be active. Schedules defined as
period list set this notification to inactive at the corresponding
time spans. The available options depend on your setup. To add or
change existing schedules, please see Account Set t ings
Schedules 2856 .
Postpone
Define if PRTG should send you notifications that were triggered

during the Paused status later on, when the notification function is
in St art ed status again.
No: Discard all notifications that are triggered while the
notification is paused.
Yes: Collect all notifications that are triggered while the
notification is paused. Send out all these notifications once the
Paused status ends.
NOTIFICATION SU MMAR IZATION

Method
2838
Define if and how PRTG summarizes notifications. Define if several

notification triggers are to be collected over a specified time
period and then sent as a single summarized notification. Choose
between:
09.05.2016

NOTIFICATION SU MMAR IZATION

Alway s not ify ASAP: Always send out one notification for each
received notification trigger as soon as possible (i.e.
immediately).
Send first DOWN message ASAP, summarize ot hers: When
receiving several Down triggers, send the first notification
immediately, but summarize other notifications into one
message.
Send first DOWN and UP message ASAP, summarize ot hers:
When receiving several Down or Up triggers, send each first
notification immediately, but summarize other notifications into
one message.
Send all DOWN messages ASAP, summarize ot hers: When
receiving several Down triggers, send out one notification for
each trigger received, but summarize notifications for all other
triggers into one message.
Send all DOWN and UP messages ASAP, summarize ot hers:
When receiving several Down or Up triggers, send out one
notification for each trigger received, but summarize notifications
for all other triggers into one message.
Alway s summarize not ificat ions: When receiving several
notification triggers, summarize all notifications into one
message, regardless of the kind of trigger received.
Note: Regardless of the option you choose, PRTG executes
notifications of the types Execut e HTTP Act ion and Execut e
Program always ASAP. They can never be summarized.
Note: The maximum length of entries in summarized email
notifications is 1,000 characters per entry.
Subject for
Summarized Messages
Define a subject that PRTG will include when sending summarized

notifications. You can use the placeholder %SUMMARYCOUNT for
the number of messages which are summarized.
Note: The subject you define is only used for Send Email and
Amazon Simple Notification Service Message notifications.
Gather Notifications
For (Minutes)
Define a time span in minutes to define how long PRTG collects

notifications for summarization. Please enter an integer value.
Note: If you enter a long timespan, for example, 60 minutes, PRTG
will collect notifications for one hour until sending them out
summarized in a single message.
09.05.2016
2839

ACCESS R IGHTS
User Group Access
settings.
settings.
Notifications SettingsChoose Notification Methods

With the following settings, you can add one or more methods how PRTG sends out a
notification message. You can choose only one method or combine several methods from the
list. Whenever the notification is triggered, PRTG sends out messages or performs actions for
all configured methods at a time.
To choose a method, mark the check box in front of the corresponding notification type. You
can then see and set the options as described below. The following notification methods are
available:
Email
2841
Push Notification
2842
SMS/Pager Message
2843
Add Entry to Event Log

Syslog Message
2845
SNMP Trap Message

Execute HTTP Action
Execute Program
2846
2847
2848
Amazon SNS Message

Ticket
2840
2845
2848
2849
09.05.2016

Note: In your message, you can use various placeholders. Some of them are already filled in by
default. For a complete list of available placeholders, see the More 2761 section below.
SEND EMAIL
Note: This notification method uses notification contacts to deliver the messages. Please
set up and check them for the desired user accounts in advance under Account Set t ings
Not ificat ion Cont act s 2853 .
Note: The three options for recipients below (user, user group, email address) work
simultaneously. Because of this, you can define more than one user as recipient of this
notification. PRTG sends the notification email to the active email contacts of the user you
select, to the active email contacts of all members of the user group you select, and to all
email addresses you enter into the "Send to Email Address" field.
Note: You can include custom email headers and footers into PRTG's HTML emails. For
details, please see section More 2850 .
Note: The predefined default notifications (Email and push notification to admin, Email to all
members of group PRTG User Group) will revert to their default users or user groups (PRTG
System Administrator or PRTG Users Group) and be reset to "active" state after restarting the
PRTG core server.
Send to User
Select a user of your PRTG installation to send the notification

email to. PRTG sends this notification to each email contact of this
user account. You can add and edit email contacts of a user in
Account Set t ingsNot ificat ion Cont act s 2853 . Choose None to
not use this feature.
Send to User Group
Select a user group to send an email with the notification to all

members of this group. PRTG sends this notification to the email
contact of every group member. You can edit user groups under
Sy st em Administ rat ionUser Groups 2896 and email contacts
under Account Set t ingsNot ificat ion Cont act s 2853 . Choose
None to not use this feature.
Note: If you select a user group and a specific member of this
group as recipients, the user will only receive a single email. This
also applies if you enter an individual email address below that is
already defined as an email contact of the selected user.
Note: If you define individual email addresses (see below), to a
specific user (see above), and a user group, PRTG sends the
message to the individual email addresses, to the individual user, as
well as to the members of the selected user group. In all cases,
PRTG sends one message with all recipients in the "To" field of the
email.
09.05.2016
2841

SEND EMAIL
Send to Email Address
Enter one or more recipient email addresses to which PRTG sends

the notification email. If you enter more than one address, separate
them by comma. Leave this field empty to send this notification
only to the email contacts of the user or members of the user
group you choose above.
We recommend that you use the options "Send to User" and/or
"Send to User Group" instead because you can manage the
notification contacts of users more easily this way.
Subject
Enter the subject of the email notification.

Several placeholders 2850 (variables) are used here by default: [%
sitename] %device %name %status %down (%message)
Format
Define the kind of email that PRTG sends when the notification is
triggered. Choose between:
HTML: PRTG uses the default HTML email template for the
message part of the email.
Text : PRTG uses the default plain text email template for the
message part of the email.
Text wit h cust om cont ent : PRTG uses custom plain text for the
message part of the email. You can enter your individual text
below.
Custom Content
This field is only visible if you select the custom text option above.
Enter the desired message for this email notification in plain text
format. You can use placeholders 2850 here.
Priority
Define the priority that PRTG sets for the email. Most email clients
can show this priority flag. Choose between:
highest
high
normal
low
lowest
2842
09.05.2016

SEND PU SH NOTIFICATION
Note: Push notifications work only with the apps PRTG for Android 2995 , PRTG for iOS 2995 ,
and PRTG for Windows Phone 2996 . You have to activate push notifications in the settings of
your app first. Please see section More 2850 for details about the setup and further
information.
Note: The PRTG server needs to communicate on port 443 to the PRTG Cloud to send push
notifications, which is ht t ps://api.prt gcloud.com:443 (and the same as for the Cloud
HTTP Sensor 523 , the Cloud Ping Sensor 533 and support tickets 2932 ).
Note: The two options for recipients below (user, user group) work simultaneously.
Because of this, you can define more than one user as recipient of this notification. PRTG
sends the notification to the active push contacts of the user you select and to the active
push contacts of all members of the user group you select.
Send to User
Select a user of your PRTG installation to send the push

notification to. PRTG sends this notification to each push contact
of this user account. You can edit push contacts of a user in
Account Set t ingsNot ificat ion Cont act s 2853 and add push
contacts by activating push notifications in the Android or iOS app
with this user. Choose None to not use this feature.
Note: The predefined default notification (Email and push
notification to admin) will revert to the default user (PRTG System
Administrator) and be reset to "active" state after restarting the
PRTG core server.
Send to User Group
Select a user group to send the push notification to all members of

this group. PRTG sends this notification to each push contact of
every member of this group. You can edit user groups under
Sy st em Administ rat ionUser Groups 2896 and push contacts
under Account Set t ingsNot ificat ion Cont act s 2853 . Choose
None to not use this feature.
group as recipients at the same time, this user receives the text
message only one time.
Message
Define the message. A message with information about the sensor

status is already predefined. Several placeholders 2850 (variables) are
used here: [%sitename] %device %name %status %down (%message)
You can change the message to your liking. To reset this field to
its default value, enter a single star symbol * (and nothing else).
09.05.2016
2843

SEND SMS/PAGER MESSAGE

Note: You have to set up this notification method in the Sy st em Administ rat ion
Not ificat ion Delivery 2877 settings first.
Note: This notification method uses the central proxy settings that you define for your PRTG
core server. For details, please see Sy st em Administ rat ionCore & Probes 2883 (section
Proxy Configurat ion).
Note: The three options for recipients below (user, user group, email address) work
simultaneously. Because of this, you can define more than one user as recipient of this
notification. PRTG sends the notification to the active SMS contacts of the user you select,
to the active SMS contacts of all members of the user group you select, and to every phone
number you enter into the "Send to Number" field.
Send to User
Select a user of your PRTG installation to send the notification to.

PRTG sends this notification to each SMS contact of this user
account. You can add and edit SMS contacts of a user in Account
Set t ingsNot ificat ion Cont act s 2853 . Choose None to not use
this feature.
Send to User Group
Select a user group to send a text message with the notification to

all members of this group. PRTG sends this notification to each
SMS contact of every member of this group. You can edit user
groups under Sy st em Administ rat ionUser Groups 2896 and SMS
contacts under Account Set t ingsNot ificat ion Cont act s 2853 .
Choose None to not use this feature.
group as recipients at the same time, this user receives the text
message only one time. This also counts if you enter an individual
phone number below that is already defined as an SMS contact of
the selected user.
Recipient Number
Define the number to which PRTG sends the text message. The
format depends on the SMS provider. Usually, you use a plus sign
"+", followed by country code and number. For example, enter
+1555012345. If you enter more than one number, separate them
by comma. Leave this field empty to send this notification only to
the SMS contacts of the user or members of the user group you
choose above.
We recommend that you use the options "Send to User" and/or
"Send to User Group" instead because you can manage the
notification contacts of users more easily this way.
2844
09.05.2016

SEND SMS/PAGER MESSAGE

Message

used here: [%sitename] %device %name %status %down (%message)
You can change the message to your liking. To reset this field to
its default value, enter a single star symbol * (and nothing else).
ADD ENTR Y TO EVENT LOG

Logfile
Define the log file into which PRTG writes the message. Choose
between:
Applicat ion: Use the Windows application log file in the event
log.
PRTG Net work Monit or: Write messages to the PRTG Network
Monitor log file in the Windows event log.
Event Source
This setting is only relevant when using the Applicat ion log file.
Enter the source for the event. Usually, this is the name of the
application.
Event Type
Select the type of the event. Choose between:

Error
Warning
Informat ion
Event Log Message

used here. You can change it to your liking. To reset this field to its
default value, enter a single star symbol * (and nothing else).
SEND SYSLOG MESSAGE

Host/IP
09.05.2016
Define the IP address or DNS name of the computer running the

syslog server.
2845

SEND SYSLOG MESSAGE

Note: You can receive and analyze syslog messages with the
Sy slog Receiver Sensor 2245 .
Syslog Port
Enter the port number on which syslog messages are sent. By

default, this is port number 514.
Note: Only User Datagram Protocol (UDP) is supported.
Facility
Define the facility information. There are several options available

from the list.
Message

SEND SYSLOG MESSAGESYSLOG MESSAGE SEVER ITY STATU S

Depending on the status of the sensor that triggers the syslog notification, PRTG sets the
Severit y level of the message automatically.
OK
Warning
Error
Severity level: Notice (5)
Severity level: Warning (4)
Severity level: Error (3)
SEND SNMP TR AP
For information about the OIDs that are used in the contents of the traps which PRTG sends,
please see the SNMP Trap documentation in the More 2850 section below.
Host/IP
Define the IP address or DNS name of the computer running the

trap receiver.
Note: You can receive and analyze trap messages with the SNMP
Trap Receiver Sensor 2082 .
2846
09.05.2016

SEND SNMP TR AP
SNMP Port
Enter the port number on which trap messages are sent. By

default, this is port number 162.
Community String
Enter the community string of the device. By default, this is set to

public. Please enter a string or leave the field empty.
Specific Trap Code
Enter a code that can help you identify the purpose of the trap.
Default value is 0. Please enter an integer value.
Message ID
This ID helps you identify the origin of the trap. For example, enter
1.3.6.1.4.1.32446.1.1.1
Message

Agent IP
Define the IP address of the agent. Leave this field empty to use
the IP address of your PRTG web server.
EXECU TE HTTP ACTION

Note: Regardless of the Not ificat ion Summarizat ion method chosen above, PRTG sends
notifications of the type Execut e HTTP Act ion always as soon as possible (ASAP). They are
never summarized.
Note: This notification method uses the central proxy settings that you define for your PRTG
core server. For details, please see Sy st em Administ rat ionCore & Probes 2883 (section
Proxy Configurat ion).
Note: For more details, please see the PRTG Applicat ion Programming Int erface (API)
Definit ion 3086 in your PRTG web interface.
URL
Enter the URL to which PRTG sends the request.

Note: HTTP notifications work with and without SSL, also with
servers which do not use SSLv3.
Postdata
09.05.2016
Enter postdata if you want to send this data to the URL. You can
use placeholders 2850 here. Line breaks are supported.
2847

EXECU TE PR OGR AM
notifications of the type Execut e Program always as soon as possible (ASAP). They are
never summarized.
Note: For more details, please see the Applicat ion Programming Int erface (API)
Definit ion 3086 in your PRTG web interface.
Program File
Select an executable file from the list. PRTG runs it every time the
notification is triggered. In this list, you see the files which are in
the corresponding /Not ificat ions/EX E sub-directory of your PRTG
core server system. To appear in this list, store the files as BAT,
CMD, DLL, EXE, PS1, or VBS. To find this path, please see section
Dat a St orage 3135 .
Note: In a cluster setup, copy your files to every cluster node
installation manually. This makes sure PRTG can execute the
notification even when the master node fails. If your custom
notification executes an external program, install it on all cluster
nodes as well. Please see also Applicat ion Programming
Int erface (API) Definit ion 3086 for detailed information.
Parameter
Enter parameters with which the program file will be started. You
can use placeholders 2850 here. For example, is you use a batch file
that contains a %1 variable, you can provide a value for this variable
here.
Domain or Computer
Name
Enter a Windows authority if you want to use another security

context for the program than the security context of the PRTG
probe service.
Username
Enter the username for Windows access.
Password
Enter the password for Windows access.
Timeout
Enter a timeout in seconds. After this time has passed, PRTG stops
the process if it has not terminated yet. Please enter an integer
value.
2848
09.05.2016

SEND AMAZON SIMPLE NOTIFICATION SER VICE MESSAGE

AWS Access Key ID
Enter your access key as shown in your login area at

aws.amazon.com. Please enter a string.
AWS Secret Access

Key
Enter your secret access key as shown in your login area at

aws.amazon.com. Please enter a string.
Location
Define the location of your Amazon service. Choose one of the

shown locations:
US-East (Northern Virginia)
US-West (Northern California)
EU West (Ireland)
US West (Oregon)
EU Central (Frankfurt)
ARN
Enter the Amazon resource name. Please enter a string.
Subject
Enter the subject of the message. Please enter a string.
Message

Note: The message part is only sent if you use email based
notifications delivered by Amazon SNS. For SMS delivery, only the
subject is sent while the message part is ignored because of SMS
size restrictions.
ASSIGN TICKET
notifications of the type Assign Ticket always as soon as possible (ASAP). They are never
summarized.
09.05.2016
2849

ASSIGN TICKET
For details about the ticket system, please see section Ticket s
Assign to User or User
Group
171
Specify whether to assign the notification ticket to a user group or

to a single user. Choose between:
To User Group: Select a user group below to which PRTG
assigns this ticket.
To User: Select the dedicated user below to whom PRTG assigns
this ticket.
Note: The predefined default notification (Ticket Notification) will
revert to the default user group (PRTG Administrators) and be reset
to "active" state after restarting the PRTG core server.
Assign Ticket to this

User Group / User
Select the user resp. user group to which PRTG assigns the
notification ticket.
Subject
Enter the subject of the ticket. Several placeholders (variables) are

used here by default. You can change it to your liking.
Content
Define the message in the ticket. A message with information

about the sensor status is already predefined. Several
placeholders 2850 (variables) are used here. You may change it as
you wish.
When Condition Clears
Specify if PRTG closes the ticket automatically when the defined

trigger condition clears. Choose between:
Close t icket aut omat ically (recommended): PRTG closes the
ticket automatically if the trigger condition is not met anymore.
Leave t icket open: PRTG does not close the ticket after the
condition has cleared.
Others
For information about the comments and history tabs, please see Object Set t ings
159
section.
More
3086

2850
09.05.2016

Knowledge Base: Documentation of SNMP Traps Sent by PRTG

Knowledge Base: How can PRTG send instant messages to Jabber, ICQ, MSN, Yahoo, etc., using
external software?
sound?
Knowledge Base: How can I send push notifications with PRTG?
How can I include my own logo into HTML emails?
09.05.2016
2851

3 Account SettingsNotification Contacts
7.12.3 Account SettingsNotification Contacts

In the notification contacts settings you can define and change notification contacts for the
currently logged in PRTG user. Notifications contacts contain information about how and
where to PRTG will send you notifications 2759 . They are unique for each user account.
Recipients of notifications can be email addresses, phone numbers, and push devices (these
are Android 2995 or iOS 2995 devices or a Windows Phone 2996 with the corresponding PRTG app).
This way, every user with a PRTG installation can individually define how and where to receive
messages from PRTG.
When you set up one of the notification methods 2840 Send Email, Send SMS/Pager Message,
or Send Push Notification, you can choose a PRTG user to send a notifications to all act ive
notification contacts of this user. If you select a user group, PRTG sends the notification to all
contacts of all users that this group contains. A user can also pause one or more of the
contacts to temporarily not receive any messages with this recipient.
Note
to send messages.
notifications.
2852
2759
section.
28.04.2016

Notification Contacts Overview

Click on the Not ificat ion Cont act s tab to show a list of all existing notification contacts of
the currently logged in PRTG user. Using the buttons in the particular contact rows, you can
perform the following actions:
Pause: Pause this notification contact. If a notification contact is paused 185 , PRTG does not
send any messages to this contact when a notification for this user is triggered.
Edit : Open the settings of this notification contact 2853 and change its description and
recipient.
Note: This is not possible for predefined notification contacts, for example, the primary email
address. You can change the primary email address under Account Set t ingsMy Account
2830 .
Delet e: Delete this notification contact.
Note: This is not possible for predefined notification contacts, for example, the primary email
address.
Notification Contacts Settings

Click Add Email Cont act or Add SMS Cont act button to add a new notification contact, or
click the Edit button of an existing notification contact to edit it. A dialog box appears where
you can enter the contact settings.
Note: PRTG adds push contacts automatically for the corresponding user when you install a
PRTG mobile app on your smartphone or tablet, connect to the PRTG server, and activate push
notifications. You cannot add push contacts manually. If your mobile device rejects push
notifications actively for an existing push contact, for example, because you deactivated push
on the target device or reset it, the PRTG server will pause this contact automatically. The
affected PRTG user account will receive a ToDo ticket 172 in this case.
ADD NEW / EDIT NOTIFICATION CONTACT

Description
Enter a meaningful name for the notification contact, for example,

SMS to Admin Mobile or similar.
Recipient
Enter a valid email address for the contact type Email or a valid
phone number for the contact type SMS. The format of the phone
number depends on the SMS provider. Usually, you use a plus sign
"+", followed by country code and number. For example, enter
+1555012345
For the contact type Push, this field shows a unique token that you
cannot change here. This token is needed to send push
notifications through the cloud. For details, see the More 2854
section.
Contact Type
28.04.2016
Shows the type of contact, either Email, SMS, or Push. This setting
is shown for your information only and cannot be changed here.
2853

ADD NEW / EDIT NOTIFICATION CONTACT

If you want to use another contact type, create a new contact
with Add Email Cont act or Add SMS Cont act , or activate push
notifications in your PRTG for iOS, Android, or Windows Phone app.
Click on the Save or Add button to store your settings, or click on Cancel to close the dialog
box without changes to your configuration.
A cloud contact is added automatically when you install the PRTG app on your smartphone,
connect to the PRTG server, and enable push notifications.
More
Knowledge Base: How can I use push notifications with PRTG?
2854
28.04.2016

SetupTopics
2830
2836

2852
2856

2860
2871

2883
2890
2896
2905

PRTG St at usAut o Updat e
2907
2923
PRTG St at usAct ivat ion St at us
2900
2918
Downloads and Add-Ons
2877
2925
2928
2930
2932
Others
There are some settings that you must make in the PRTG Administ rat ion Tool
as native Windows application. For more details, please see the sections:
PRTG Administ rat ion Tool on Core Server Sy st em
, available
3047
PRTG Administ rat ion Tool on Remot e Probe Sy st em
28.04.2016
3046
3073
2855

4 Account SettingsSchedules
7.12.4 Account SettingsSchedules

In the schedule settings you can define or change schedules for the currently logged in user.
You can use schedules to pause 185 monitoring/notification at for certain time periods with the
period lists option. Also you can activate it at certain times with the time table option. You can
also use schedules to define the time periods that are to be covered when creating reports 2786
.
Sc hedules Settings
Schedules Settings
Click on the Schedules tab to show a list of all existing schedules. By following the links next
to the notification name, you can perform the following actions:
Delet e: Delete this notification (not possible for predefined notifications)
Used by : Show a list of objects using this notification.
2856
28.04.2016

Click on the Add new schedule button or click on the name of an existing notification to edit.
Edit Sc hedule Time Table
BASIC SETTINGS
Schedule Name
Enter a meaningful name for the schedule that describes the

defined time span(s) or their purpose.
Edit Mode
Select how you want to define a schedule. Choose between:

Use weekday /hour t ime t able: Define a schedule by adding
check marks to available checkboxes. The lowest possible
increment is one hour. Note: This time table posit ively defines
which time slots are active.
28.04.2016
2857

BASIC SETTINGS
Use list of period definit ions: Define a schedule by entering
text lines using a specific syntax (see below). Note: This time
table negat ively defines which time slots are inactive.
Time Table
This selection is only visible if the time table option has been
enabled above. Define the schedule. It will be used for monitoring
objects, reporting, and notifications. You can set time spans with a
precision of one full hour by adding check marks. If a box is
checked, it means the object is active during this hour, if
unchecked, the object will be paused during this hour. You can set
check marks individually, or change complete ranges for certain
days of the week or time spans.
To add ranges of check marks, use the buttons All, Mo, Tu, We,
Th, Fr, Sa, and Su, as well as the time buttons on the left side.
To remove ranges of check marks, use the buttons All Off, Mo
Off, Tu Off, We Off, Th Off, Fr Off, Sa Off, and Su Off, as well as
the time Off buttons on the right side.
Period List
This field is only visible if period definitions are enabled above.

Define the date/time ranges in which the objects using this
schedule will be inactive (i.e., paused). During other times, the
objects will be active. Enter the ranges in the format ww:hh:mmww:hh:mm. For details and examples, see Schedules Settings
Period Definition Syntax 2859 below.
Note: Schedules use the timezone of the computer on which your PRTG core server is
running. This may diverge to other time displays in PRTG which are saved in UTC. If you define a
schedule with the Time Table option in the schedule settings 2857 , the time to which the
schedule applies is converted to the timezone of your PRTG user account 2833 . This means that
the schedule is executed according to the time that your user account shows. If you use the
Period List option, PRTG will not adjust the schedule to the timezone of your user account!
The schedule will apply according to the time on your PRTG server in this case. Because of this,
you will encounter time shifts for schedules if there are changes to the timezone on the
server or in case of different daylight saving and standard time changes.
ACCESS R IGHTS
User Group Access
2858
28.04.2016

ACCESS R IGHTS
settings.
settings.
Schedules SettingsPeriod Definition Syntax

Define one or more periods of time during which the object using this schedule will be
inactive. In each line, enter one range in the format ww:hh:mm-ww:hh:mm: weekday, hour,
minute.
Possible values for ww: mo, tu, we, th, fr, sa, su.
Possible values for hh: Enter the hour in 24 hours format (no AM/PM allowed), i.e. a number
between 00 and 23.
Possible values for mm: Enter the minute, i.e. a number between 00 and 59.
Example
In the following, find an example for a schedule that pauses an object during the weekend
as well as on Wednesday evenings.
fr:19:30-mo:06:05
we:18:45-we:23:00
Any object using this schedule will be paused from Friday, 7:30 p.m. to Monday, 6:05 a.m. as
well as on Wednesday from 6:45 p.m. to 11 p.m. It will be active during the other times.
Others
For information about the comments and history tabs, see the Object Set t ings
28.04.2016
159
section.
2859

5 System AdministrationUser Interface
7.12.5 Sy stem AdministrationUser Interface

In the user interface settings you can define global values regarding the PRTG web site
appearance, PRTG web server settings and performance, geo maps, and graph settings.
User Interface Settings

WEBSITE
PRTG Site Name
When using the web interface, the site name is shown in the title
bar of your browser window. It is also used by default in
notification emails. Please enter a string.
DNS Name
If your PRTG web interface is (additionally) reachable via a DNS

name, please enter it here. It is e.g. used by default in notification
emails to generate links. Please enter a string.
Website Language
Choose the system language from the drop down list. Default is
English. Depending on your installation, you may be able to
choose other languages here. This setting defines the language of
the Ajax web interface 108 , as well as of the PRTG Administ rat ion
Tool 3046 .
Note: If you change this setting, PRTG needs to restart the core
server. Because of this, all users of PRTG's web interface, of the
Ent erprise Console 2938 , or of Smart phone Apps 2995 will be
disconnected. After clicking on the Save button, a dialog box will
appear which asks you to confirm the required core server restart.
Click OK to trigger the restart and follow the instructions on the
screen.
Graph Type
Select how graphs will be displayed throughout the web interface

and in reports 2786 .
Use area graphs (recommended): Display filled graphs.
Use line graphs: Display graphs using single lines only.
2860
15.04.2016

WEBSITE
We recommend using area charts, as they're better to read. Note:
Graphs containing data from more than one cluster node will
always be displayed with line graphs automatically.
Automatic Logout
Define if a user who is inactive for a certain period of time will be

logged out from the PRTG interface automatically for security
reasons. Choose between:
Keep user logged in, even for a longer period of inact ivit y .
Logout user aut omat ically aft er a cert ain period of
inact ivit y .
Automatic Logout after This field is only visible if you selected the logout option above.
Minutes
Specify in minutes after which time of inactivity a user will be
logged out automatically. Please enter an integer value. PRTG will
redirect to the login page once this time has expired. Note: The
countdown will start with one minute delay.
Google Analytics
Tracking ID
You can track the usage of PRTG web pages with Google Analytics
by entering your Google Universal Analytics Tracking ID into this
field. You need a Google Analytics account for this feature. Create
a tracking ID within the Google Analytics portal and provide it here.
PRTG will then dynamically integrate it into the website.
Please enter a string or leave the field empty. The string will look
like this: UA-xxxxxx-xx
For details, please see section More.
GEO MAPS
Map Service Provider
Select if and how you want to integrate the Geo Maps feature into
the web interface. If enabled, PRTG uses the first line of the
location setting of an object 159 to show it on a geographical map.
Please choose a map provider:
Do not show maps (disables Geo Maps int egrat ion): Disable
Geo Maps integration and do not show geographical maps in the
web interface.
MapQuest : Use MapQuest to show geographical maps. This is
the recommended option.
Nokia Maps: Use Nokia Maps to show geographical maps.
15.04.2016
2861

GEO MAPS
CloudMade (API key required): Use CloudMade to show
geographical maps. Please sign up for an API key on their
developer website to use this service.
Google St at ic Maps (API key required): Use Google Static
Maps to show geographical maps. Please sign up for a Google
Maps API v3 key to use this service as of PRTG version 13!
For more information about the different map providers, please see
the More 2869 section below.
Map Type
This setting is only visible for some map providers. Depending on

the chosen provider, several options are shown. Each will show
map tiles in a different appearance. Please choose a map type from
the list.
API Key (required)
This field is only visible if you selected a provider that requires an

API key. Please obtain your personal key and paste it here. For
more information on how to get an API key, please see the More
2869 section below. Please enter an alphanumeric string.
WEB SER VER

Performance Strategy
Select if you want to enable performance improvements for the

web interface.
All Feat ures: Show all feat ures and live dat a (recommended):
Provide full functionality and show all menu items.
More Speed: Limit feat ures and delay display
(experiment al): Improve reaction time and speed of the web
interface by delaying display of monitoring data and hiding some
features.
For more information on how to speed up the web interface,
IP Address for Web

Server
PRTG is running a web server in order to provide access via the

web and Windows interface. Please specify which IP address this
web server will run on. Note: Later, you can log in to PRTG by
simply pointing your browser to the specified IP address.
Choose between:
2862
15.04.2016

WEB SER VER

Localhost , 127.0.0.1 (PRTG will not be accessible from ot her
comput ers): Use 127.0.0.1 only. PRTG's web and Windows
interface will only be accessible from the computer PRTG is
installed on.
Note: Either the selected port or at least one port in the range
from 8080 to 8089 has to be available on 127.0.0.1.
Note: If you run PRTG on localhost, please do not use the DNS
name http://localhost to log in to the web server, as this may
considerably slow down PRTG's web interface. Please use your
local IP address or http://127.0.0.1 instead.
All IPs available on t his comput er: Use all IP addresses
available on this computer and enable access to the web server
for all of these addresses. Note: The TCP port selected below
must be free on every available IP address.
Specify IPs: Select specific IP addresses on which the PRTG Web
server will run on. A list specific to your system is shown. Add a
check mark in front of every IP address you want the PRTG web
server to be available at. You can also select and deselect all
addresses by clicking on the check box in the table header.
Note: Either the selected port or at least one port in the range
from 8080 to 8089 has to be available on the specified IP
address.
Note: Regardless of the selected setting above, one port in the
range from 8080 to 8180 has to be available on the specified IP
address so PRTG can create reports. The report engine will try to
connect to the core server on one of these ports.
Note: If PRTG does not find a network card on startup it will switch
the IP setting to Localhost . This setting will remain, even if a
network card is available later on. If you disabled or removed the
network card on the machine running the PRTG core server, please
re-check this setting.
screen.
TCP Port for Web
Server
15.04.2016
PRTG is running a web server in order to provide the web and

Windows interface. Please specify on which port this web server
will run. Choose between:
2863

WEB SER VER

Secure HTTPS server (recommended, mandat ory for int ernet
access): This is the recommended setting and needed to access
the PRTG server via the internet. Use a secure HTTPS connection
that is encrypted via SSL on port 443.
Note: Although the connection is secure, you will see an SSL
Cert ificat e Warning 113 in your browser when logging in to the
PRTG web interface, because the default certificate is unknown
to your browser. You can install another SSL certificate for PRTG
later. Please see Using Your Own SSL Cert ificat e 3137 .
Note: If port 80 is free, PRTG will reserve it as well. When users
try to connect on port 80 via HTTP, they will then be redirected
to port 443 via HTTPS. You can change this behavior using a
registry setting.
Note: If port 443 is not available, PRTG will try port 8443 as
fallback. If this port is also not available, PRTG searches from port
32000 upwards for a free port. PRTG sends a ticket 171 that
shows you the currently used port number and will switch back
to 443 as soon as it is available again.
Insecure HTTP server (st andard port 80, not recommended):
Use a standard web server without SSL encryption on port 80.
This setting is not recommended for WAN connections.
Note: If used on the internet, attackers could potentially spy on
credentials you enter into PRTG. We strongly recommend using
this option in a LAN only.
Expert configurat ion: This setting allows you to specify a
custom web server port and the security of the connection. This
option is intended for systems with an existing web server on
the standard port. Define port and encryption below.
Note: If PRTG always uses a fallback port after a server restart,
check for other programs that use the same port as PRTG. For
example, the Microsoft IIS web server also uses the port 80 (443
for SSL) by default and blocks it. Please disable such programs and
services on startup.
screen.
Web Server Port
2864
This setting is only visible if the expert configuration is selected

above. Enter the desired TCP port number you want the PRTG web
server to run on. Please enter an integer value.
15.04.2016

WEB SER VER

Note: If you use a secure connection and port 80 is free, PRTG will
reserve it as well. When users try to connect on port 80 via HTTP,
they will then be redirected to the custom port via HTTPS. You can
change this behavior using a registry setting.
Note: If port the defined port for a secure connection is not
available, PRTG will try port 8443 as fallback. If this port is also not
available, PRTG searches from port 32000 upwards for a free port.
PRTG sends a ticket 171 that shows you the currently used port
number and will switch back to the original port as soon as it is
available again.
screen.
Web Server Security
This setting is only visible if the expert configuration is selected

above. Specify if you want to use an SSL encryption. Choose
between:
Use SSL encry pt ion (HTTPS): Use a secure HTTPS connection
that is encrypted via SSL on a custom port as defined above.
Note: Although the connection is secure, you will see an SSL
Cert ificat e Warning 113 in your browser when logging in to the
PRTG web interface, because the default certificate is unknown
to your browser. You can install another SSL certificate for PRTG
later. Please see Using Your Own SSL Cert ificat e 3137 .
Don't use encry pt ion (not recommended): This setting is not
recommended for WAN connections. Use a standard web server
without SSL encryption on a custom port as defined above.
Note: If used on the internet, attackers could potentially spy on
credentials you enter into PRTG. We strongly recommend using
this option in a LAN only.
screen.
SSL Security
15.04.2016
Specify the security level which will be used for SSL connections
from and to the PRTG web server. Choose between:
2865

WEB SER VER

High securit y (recommended): The web server will only accept
high security connections from clients like web browsers, apps
2995 , the Ent erprise Console 2938 , or API clients. These clients
must be able to support modern ciphers which support
authentication and encryption of 128 bits or stronger and
forward secrecy. All modern web browsers do this.
Weakened securit y (necessary for old web browser and old
client soft ware): If you have clients which do not support the
high security setting, you can choose this 'normal security level'
setting in order to connect (for example, older browsers,
browsers running on Windows XP, some default browsers on
Android systems). However, we strongly recommend that you
update your clients in this case. For details about how to do this
with the Enterprise Console, see the section More 2869 below.
Currently Active IP
Address/Port
Combination(s)
Shows all currently active combinations of IP addresses and ports

on which the PRTG server listens for web requests. This setting is
Note: PRTG internally uses port 8085 for report generation.
GR APH SETTINGS: SELECT FOR HOW MANY DAYS HISTOR IC DATA R EMAINS
ACCESSIBLE
PRTG shows several graphs in the objects' detail pages 137 in the web interface. These are
kept in RAM memory for fast display without causing extra CPU load or disk usage. The
longer the time frames and the shorter the intervals are, the more memory will be used for
this. You can adapt the details for all four graphs. This setting will also change the caption of
the objects' tabs in the web interface 108 and Enterprise Console 2938 .
Note: If you change this setting, PRTG needs to restart the core server. Because of this, all
users of PRTG's web interface, of the Ent erprise Console 2938 , or of Smart phone Apps 2995
will be disconnected. After clicking on the Save button, a dialog box will appear which asks
you to confirm the required core server restart. Click OK to trigger the restart and follow
the instructions on the screen.
2866
15.04.2016

ACCESSIBLE
Live Graph
The live graph is available for sensors only. For the live graph, no
fixed time span is given, but you can define how many values will
be displayed. The actual time span covered by the live graph
depends on the scanning interval set for the sensor you're viewing
and is calculated automatically. By default, 120 Values is set, which
results in a graph covering a time span of two hours, if a scanning
interval of 60 seconds is set for the sensor. Other scanning
intervals will result in graphs covering different time spans. Choose
between:
60 Values: This corresponds to a live graph covering a time span
of one hour if a 1 minute scanning interval is set. Uses least RAM
memory. We recommend this setting for installations with 10,000
sensors or more.
120 Values: This corresponds to a live graph covering a time
span of two hours if a 1 minute scanning interval is set.
span of four hours if a 1 minute scanning interval is set.
span of eight hours if a 1 minute scanning interval is set.
span of 16 hours if a 1 minute scanning interval is set. Uses most
RAM memory.
Graph 1
By default, this is the 2 day s graph in the web interface. You can
change it to more or less detail by choosing a time span and a
monitoring interval average associated with it. Monitoring results
will be averaged regardless of the actual scanning interval set for
the sensors. Choose between:
1 day wit h 1 minut e averages: Results in 1440 values.
1 day wit h 5 minut es averages: Results in 288 values.
1 day wit h 15 minut es averages: Results in 96 values. Uses
least RAM memory. We recommend this setting for installations
with 10,000 sensors or more.
2 day s wit h 1 minut e averages: Results in 2880 values. Uses
most RAM memory.
2 day s wit h 5 minut es averages: Results in 576 values.
2 day s wit h 15 minut es averages: Results in 192 values.
4 day s wit h 1 hour averages: Results in 96 values. Uses least
RAM memory. We recommend this setting for installations with
10,000 sensors or more.
15.04.2016
2867

ACCESSIBLE
Graph 2
change it to more or less detail by choosing a time span covered
and a monitoring interval average associated with it. Choose
between:
10 day s wit h 1 hour averages: Results in 240 values.
30 day s wit h 6 hour averages: Results in 120 values. Uses
60 day s wit h 1 hour averages: Results in 1440 values. Uses
most RAM memory.
Graph 3
change it to more or less detail by choosing a time span covered
and a monitoring interval average associated with it. Choose
between:
100 day s wit h 1 day averages: Results in 100 values. Uses
200 day s wit h 1 day averages: Results in 200 values.
750 day s wit h 1 day averages: Results in 750 values. Uses
most RAM memory.
R EPOR T COMMENTS
Introduction
2868
Define a custom text that will show up on the first page of the
15.04.2016

R EPOR T COMMENTS
Footer Comments
Define a custom text that will show up on the last page of the
More
Knowledge Base: Which provider should I use for PRTG's "Geo Maps" feature?
Knowledge Base: Which domains and ports does the GeoMaps feature use?
Knowledge Base: How do I get a Google Maps API key for use in PRTG?
Knowledge Base: Which limitations apply when using the Google Maps API in PRTG?
Paessler Blog: Version 12 of PRTG introduces "Continuous Rollout"
https://www.paessler.com/blog/2012/04/25/
Knowledge Base: Enterprise Console connection failure error in content: What can I do?
Knowledge Base: How can I integrate Google Analytics in PRTG?
15.04.2016
2869

2870
15.04.2016

6 System AdministrationMonitoring
7.12.6 Sy stem AdministrationM onitoring

In the monitoring settings you can define global values regarding scanning intervals, unusual
and similar sensors detection, auto-discovery, and uptime threshold.
Monitoring Settings
SCANNING INTER VALS

Available Intervals
Define the intervals available in the drop down list of every object's
settings 159 . In the text field, enter one value in each line. Use s, m,
h, and d for defining seconds, minutes, hours, and days. By default,
there are the following scanning intervals defined:
30s: 30 seconds
1m: 1 minute
5m: 5 minutes
10m: 10 minutes
15m: 15 minutes
30m: 30 minutes
1h: 1 hour
4h: 4 hours
6h: 6 hours
12h: 12 hours
1d: 1 day
Note: We recommend that you do not use intervals shorter than
10 seconds to prevent system overload. Intervals below 10
seconds are not officially supported! The maximum supported
scanning interval is 10 days.
05.11.2015
2871

SCANNING INTER VALS

You can also define specific points in time to indicate when PRTG
executes scanning actions. Enter up to 50 concrete UTC points in
time according to the formula
@ UTC hh:mm, hh:mm
Note: Your local time may be different from the UTC time! For more
information on how to set specific points in time as a scanning
time for sensors, see the More 2876 section below.
U NU SU AL DETECTION
The unusual detection can set sensors to an Unusual status 135 when there are values that
are untypical for the time span in which they are measured. PRTG compares the current
average values to the historic monitoring results for this purpose. If the current values show
a big difference to the values that are normally retrieved by a sensor, this sensor will
indicate this with the unusual status. You can define the granularity of the detection here
(this means, how big the difference must be to cause an unusual status). If you disable the
unusual detection (both settings to Never), sensors will never show an unusual status.
Note: You can enable and disable unusual detection for specific devices, entire groups, and
probes in the respective Object Set t ings 159 .
Show Unusual When
Define when a sensor shows the unusual status, comparing the

weekday. If you enable the detection here, the average of the
values which were measured on the day before is compared to the
average of the same weekday in previous weeks. Choose
between:
Never: Disable unusual detection for weekday average.
24h average is <80% or >120% of weekday average: The
average of the values measured on the day before is either
lower than 80% or higher than 120% than usually on the same
weekday.
24h average is <50% or >200% of weekday average: The
lower than 50% or higher than 200% than usually on the same
weekday.
24h average is <20% or >500% of weekday average
(recommended): The average of the values measured on the day
before is either lower than 20% or higher than 500% than usually
on the same weekday.
2872
05.11.2015

24h average is <10% or >1,000% of weekday average: The
lower than 10% or higher than 1,000% than usually on the same
weekday.
24h average is <1% or >10,000% of weekday average: The
lower than 1% or higher than 10,000% than usually on the same
weekday.
For example, consider a traffic sensor that usually measures 100
MB average traffic on a weekday. If you choose the first option, it
would show an unusual status if the average from the day before is
below 80 MB or above 120 MB.
Show Unusual When
Define when a sensor shows the unusual status, comparing the

hour-of-day. If you enable the detection here, the average of the
values which were measured in the hour before is compared to the
average of the same hour on the same weekday in previous
weeks. Choose between:
Never: Disable unusual detection for hour-of-day average.
Hourly average is <80% or >120% of hour-of-day average: The
average of the values measured in the hour before is either
lower than 80% or higher than 120% than usually in this hour of
this weekday.
Hourly average is <50% or >200% of hour-of-day average: The
average of the values measured in the hour before is either
lower than 50% or higher than 200% than usually in this hour of
this weekday.
Hourly average is <20% or >500% of hour-of-day average
(recommended): The average of the values measured in the
hour before is either lower than 20% or higher than 500% than
usually in this hour of this weekday.
Hourly average is <10% or >1,000% of hour-of-day average:
The average of the values measured in the hour before is either
lower than 10% or higher than 1,000% than usually in this hour of
this weekday.
Hourly average is <1% or >10,000% of hour-of-day average:
The average of the values measured in the hour before is either
lower than 1% or higher than 10,000% than usually in this hour of
this weekday.
Consider a traffic sensor that usually measures 10 MB average
traffic within an hour. If you choose the first option, it would show
an unusual status if the average from the hour before is below 8
MB or above 12 MB.
05.11.2015
2873

Logging
Define if unusual events will be written to the log file. Choose

between:
Do not log unusual event s
Writ e unusual event s int o t he log
SIMILAR SENSOR S DETECTION

Similar sensors detection enables PRTG to analyze sensor data for similarities. The detection
will run in the background with low priority. The recommended setting for similar sensors
detection is to let PRTG automatically decide how many channels will be analyzed. However,
you can also override this setting.
Note: When similar sensors analysis is turned off or you have exceeded 1,000 sensors and
have chosen the automatic analysis depth option, the similar sensors entry will not be
shown in the main menu bar.
Analysis Depth
Define the number of channels PRTG will analyze to detect

similarities between sensors or turn the analysis off. Choose
between:
Manage aut omat ically based on sensor count
(recommended): The analysis depth depends on the total
number of sensors you have configured. PRTG will analyze all
channels for up to 500 sensors, and only the primary sensor
channels for up to 1,000 sensors. If exceeding 1,000 sensors,
the analysis will be turned off.
Analy ze primary channels only : Only the primary channels of
sensors are analyzed. Be aware of potentially high CPU load of
PRTG when choosing this setting for more than 1,000 sensors.
Analy ze all channels (higher CPU load): Similarity detection is
applied to all channels. Be aware of potentially high CPU load of
PRTG when choosing this setting for more than 500 sensors.
Turn analy sis off: No similarity detection takes place. Choose
this option if you are not interested in the analysis results or you
want to keep PRTG's CPU load at a minimum.
2874
05.11.2015

R ECOMMENDED SENSOR S DETECTION

With the sensor recommendation engine, PRTG can analyze devices in your network and
suggest you sensors that are still missing for a complete monitoring. The analysis runs with
low priority in the background when you add a new device, when the last analysis was
executed more than 30 days ago, or when you manually start 156 it.
See the manual section Recommended Sensors 155 for more information, for example, on
SNMP settings 156 , on the results 156 you get and on how you add the suggested sensors 157
.
Detection Engine
Define if you want PRTG to analyze your devices to recommend

useful sensor types. Choose between:
Manage aut omat ically based on sensor count
(recommended): PRTG runs the detection engine for
installations with up to 5,000 sensors by default. If you exceed
this threshold, PRTG disables the detection engine for
performance reasons. We recommend that you set this option
so you do not miss any important monitoring data about your
network, without risking to run into performance issues.
Alway s show recommendat ions: PRTG always analyzes your
devices even if your installation exceeds 5,000 sensors and you
will never miss any suggestion to complete your monitoring. But
if you enable this option, please keep in mind this setting in case
you encounter performance issues.
Turn recommendat ions off: PRTG never recommends sensors.
Select this option if you have performance issues with PRTG or if
you do not want to see this information on device overview tabs
137 . Moreover, you will not find the option Recommend Now in
device context menus 192 or on overview tabs anymore.
AU TO-DISCOVER Y
Run Discovery at
05.11.2015
Define the time when PRTG automatically runs an Aut o-Discovery

219 in your network if you configured a daily or weekly Discovery
Schedule in the auto-discovery group settings 221 . Choose a full
hour between 0:00 and 23:00. We recommend that you choose a
time when there is little user activity in your network, because
auto-discoveries can produce a certain amount of load.
2875

U PTIME THR ESHOLD

Desired Minimum
Uptime
Define which uptime in percent PRTG regards as 100 percent. This

setting affects the colors shown next to the sensor icons in
reports. Select one of the predefined values between 90 % and
99.999 %.
More
Knowledge Base: Can I set a sensor to run at a specific time?
2876
05.11.2015

7 System AdministrationNotification Delivery
7.12.7 Sy stem AdministrationNotification Delivery

In the notification delivery settings you can define global settings for notification delivery. If
you do not want to use a specific notification method, just leave the respective fields empty.
Note
to send messages.
notifications.
2759
section.
Notification Delivery Settings

09.11.2015
2877

SMTP DELIVER Y
SMTP Delivery
Mechanism
Define how PRTG sends emails using Simple Mail Transfer Protocol
(SMTP). Choose between:
Direct delivery using built -in email relay server (default ): Use
the SMTP relay server built into PRTG. This server manages its
own email queue. For each email, it looks up the target SMTP
server via the MX record of the target domain, and send the
email.
Use SMTP relay server (recommended inside LANs/NATs): Set
up your own SMTP relay server to send emails. Enter data below.
Use t wo SMTP relay servers (primary and fallback server):
Set up two own SMTP relay serversone primary and one as
fallback server. Enter data below.
Note: When monitoring inside your NAT or LAN, it is often a good
idea to use your own LAN-based relay server to deliver notification
emails quicker.
Sender Email
Enter an email address to use as sender of all emails. This setting is

global and can only be changed centrally here.
Sender Name
Enter a name to use as sender of all emails. This setting is global

and can only be changed centrally here.
HELO Ident
Enter the HELO Ident for SMTP. This must be a unique name,
preferably the DNS name of the machine running PRTG. See SMTP
RFC 2821: The sender-SMTP must ensure that the domain
parameter in a HELO command is a valid principal host domain name
for the client host.
SMTP Relay Server
This field is only visible if you enable SMTP relay server above. Enter
the IP address or DNS name of the SMTP relay server.
SMTP Relay SMTP Port
the port number the SMTP relay server is running on. Standard
value is 25.
SMTP Relay
Authentication
This field is only visible if you enable SMTP relay server above.
Select the kind of authentication required for the SMTP server.
Choose between:
No aut hent icat ion is required: Use SMTP without
authentication.
Use st andard SMTP aut hent icat ion: Use standard
authentication.
2878
09.11.2015

SMTP DELIVER Y
SASL aut hent icat ion is required: Use secure authentication via
Simple Authentication and Security Layer (SASL).
SMTP Relay User

Enter a valid username.
SMTP Relay Password

Enter a valid password.
Use Encrypted
Connection
the security level for SMTP connections. Choose between:
Never: Use insecure connection with plain text transfer.
If support ed by server: Use a secure connection (default).
SSL Method
This setting is only visible if you enable SMTP relay server and
encryption above. It is only relevant for secure connections. Select
the SSL or TLS version that your SMTP device supports. We
recommend that you use the default value. If you do not get a
connection, try with another setting. Choose between:
SSL V2
SSL V2 or V3
SSL V3
TLS V1
SMTP Relay Server

(Fallback)
SMTP Relay SMTP Port
(Fallback)
SMTP Relay
Authentication
(Fallback)
These fields are only visible if you enable the option for two SMTP
relay servers above. Please see also the settings that you made for
your primary SMTP relay server.
Use Encrypted
Connection (Fallback)
SSL Method (Fallback)
SMTP Relay User
(Fallback)
09.11.2015
2879

SMTP DELIVER Y
SSL Method (Fallback)
SMTP Relay User
(Fallback)
SMTP Relay Password
(Fallback)
Security (Fallback)
SMS DELIVER Y
Note: Although PRTG has built-in support for the Application Programming Interface (API) of
some SMS providers, we cannot officially provide support regarding these SMS service
providers. If you have technical questions about SMS delivery beyond PRTG, please contact
your SMS provider directly.
Note: Instead of using a pre-configured provider you can always use a custom URL, enabling
you to use extended parameters (this is also an alternative when using providers for which
we offer pre-configured options).
You need an internet connection to send text messages via the HTTP API. For information
about sending SMS via separate hardware using third party software, please see the More
2881 section below.
Configuration Mode
Define how you want to select an SMS provider. Choose between:

Select an SMS provider from a list of providers: Select a
provider from a list below.
Ent er a cust om URL for a provider not list ed: Use another
provider and enter the service URL manually below.
Service Provider
This field is only visible if the provider list is enabled above. Choose
a service provider from the list. PRTG offers a small incomplete list
of providers. Note: Some providers might require a port
configuration in your firewall. See More 2881 section below for more
information.
User
This field is only visible if the provider list is enabled above. Enter a
username for the service provider account.
2880
09.11.2015

SMS DELIVER Y
Password
This field is only visible if the provider list is enabled above. Enter a
password for the service provider account.
API ID / Account
This field is only visible if the provider list is enabled above. Some
providers need an additional API ID or account information. If
provided, enter it here. Please enter a string or leave the field
empty.
Custom URL
This field is only visible if the custom provider option is enabled

above. From the documentation of your SMS provider, please
enter the service URL that is used to send SMS messages. Use the
following placeholders for the recipient phone number and the
text message: %SMSNUMBER, %SMSTEX T.
Maximum Length of
Text
Some SMS providers will not allow SMS messages exceeding a

certain amount of characters. PRTG will restrict the number of
characters according to the length specified in this field. A value of
0 means the SMS is sent at its full length.
Note: The notification 2836 methods "Send SMS/Pager Message" and "Execute HTTP Action" will
use the central proxy settings defined for your PRTG core server. For details, please see
Sy st em Administ rat ionCore & Probes 2883 (section Proxy Configurat ion).
More
Knowledge Base: How can I send SMS text message notifications via a modem or a mobile
phone with PRTG?
Knowledge Base: Why do I get a connection timeout message when sending SMS via bulksms?
Knowledge Base: Which URLs does PRTG use for its preconfigured SMS providers?
Knowledge Base: How do I send SMS with PRTG using a Clickatell account?
Knowledge Base: How can PRTG send instant messages to Jabber, ICQ, MSN, Yahoo, etc., using
external software?
Knowledge Base: Can GMail / Google Apps be used for SMTP relay?
09.11.2015
2881

Knowledge Base: How can I enable Notification Delivery Logging?
Knowledge Base: How can I include my own logo into HTML emails?
2882
09.11.2015

8 System AdministrationCore & Probes
7.12.8 Sy stem AdministrationCore & Probes

In the core and probe management settings you can define settings for the core server, as
well as the settings for probe connections if you use remote or mini probes.
Note: If you cannot save changes to Core & Probes settings because you get an Error (Bad
Request ) with the message Act ive Direct ory Domain not accessible, ensure you provide
the correct access type for your domain in section Act ive Direct ory Int egrat ion 2887 ! For
example, change from "local user" to Use explicit credent ials and provide correct credentials
for the domain. Please note that PRTG automatically sets the access type "local system" by
default, so you might need to change this.
Core and Probes Settings

PR OXY CONFIGU R ATION

Use Proxy Server
We recommend using PRTG with a direct internet connection.

However, if you need to use a proxy, you can configure the
relevant settings here. Choose between:
No, use direct connect ion t o t he Int ernet (default ): Do not
use a proxy. Use this setting if there is a direct internet
connection available to the server running the PRTG core server.
Yes, in our net work a proxy is mandat ory : Define proxy
settings below.
Note: Proxy settings are valid for Aut o-Updat e 2918 , Act ivat e t he
Product 65 , obtaining Geo Maps 2753 tiles, and for sending out
HTTP, push, and SMS text message Not ificat ions 2840 . The sensor
types Cloud HTTP 523 and Cloud Ping 533 use these proxy settings
as well.
Proxy Server
21.01.2016
This setting is only visible if proxy usage is enabled above. Enter

the address of the proxy server that you use for outbound
connections. Please enter a valid address.
2883

PR OXY CONFIGU R ATION

Port
This setting is only visible if proxy usage is enabled above. Enter

the port number of the proxy server that you use for outbound
Use Proxy Credentials
This setting is only visible if proxy usage is enabled above.

Determine whether the proxy server needs credentials or not.
Choose between:
Yes, t he proxy server requires credent ials: Define credentials
(username and password) below.
No, t here are no credent ials necessary : Do not use
credentials for proxy connections.
User
This setting is only visible if proxy credentials are enabled above.

Enter a username for proxy authentication. Please enter a string.
Password
This setting is only visible if proxy credentials are enabled above.

Enter a password for proxy authentication. Please enter a string.
PR OBE CONNECTION SETTINGS

Probe Connections IPs
Define how PRTG handles incoming connections from probes.

Choose between the following options:
Local Probe only , 127.0.0.1 (PRTG will not be accessible for
Remot e Probes): This is the default setting. The PRTG core
server 84 only accepts local probe connections. You cannot use
remote probes 3108 with this setting enabled.
All IPs available on t his comput er: The PRTG server will always
accept incoming connections from remote probes, no matter on
which IP address of the core server they come in.
Specify IPs:The PRTG server will accept Incoming connections
from remote probes 3117 only on the selected IP address(es) of
the core server. In the list, select the IP addresses by adding a
check mark in front of the desired IPs.
You can also change this setting in the PRTG Administ rat ion Tool
on Core Server Sy st em 3051 .
2884
21.01.2016


screen.
Access Keys
Enter a list of access keys, one per line. Every (remote) probe that
wants to connect to this PRTG installation has to use one of these
keys. For more information on how to set this key for a probe,
please see the PRTG Administ rat ion Tool 3074 section.
Allow IPs
Enter a list of remote probe IPs that will be accepted when

connecting to this PRTG installation; one IP address per line. The
local probe (127.0.0.1) is always allowed automatically. Allowed IPs
are checked first (before denied IPs). You can use PRTG's syntax for
IP address ranges here (for information about the syntax please
see the Define IP Ranges 3094 section).
[Empty]: An empty field does not allow any remote probes (but
only the local probe). Please enter IP addresses to allow remote
probe connections.
any : Enter the word any to automatically allow all remote probe
connections. Note: This is recommended for use in Intranets
only!
Note: If the IP address of your remote probe changes regularly
(e.g. due to an internet provider assigning IP addresses
dynamically), please enter the potential IP range for this remote
probe or use the any option.
Deny IPs
21.01.2016
Enter a list of remote probe IPs that will not be accepted when
connecting to this PRTG installation; one IP address per line. This is
useful to explicitly deny connections from certain remote probes
you do not want to include in your setup any more (e.g. for a
certain time). Access to IP addresses you allowed above will be
denied if you enter them here. This is useful to allow access to an
IP range in the field above, but deny access to a single IP address.
You can use PRTG's syntax for IP address ranges here (see the
Define IP Ranges 3094 section).
2885


Deny GIDs
Enter a list of GIDs, one global ID (GID) per line. The access to
matching GIDs will be denied. If you remove a remote probe from
the device tree or if you deny a remote probe after installation, its
global ID (GID) will be automatically entered here. This specific
remote probe will not be able to connect anymore. Denying GIDs
is more precise than denying IPs, where other remote probes at
the same location could be excluded too.
Mini Probes
Define if you want to allow Mini Probe connections to your PRTG

server. If you want to use Mini Probes, you need to set up your
PRTG web server to accept connections of Mini Probes here and
choose the secure HTTPS server option in the web server settings
2862 . Choose between:
No Mini Probes: Mini Probes cannot connect to your PRTG web
server. You are not able to monitor with Mini Probes if you
choose this option.
Allow Mini Probes t o connect t o t he web server: Mini Probes
can connect to your PRTG web server and use the defined TCP
port for the web server 2862 for this purpose. The default port for
SSL connections is 443.
Allow Mini Probes t o connect t o an ext ra port : Mini Probes
can connect via a specific port to your PRTG web server. This is
useful if you do not want to have your whole PRTG web server
reachable from other networks all the time only because of Mini
Probes.
Note: SSL is always required to be active on the Mini Probe port.
Please refer to the PRTG API 3086 for the full Mini Probe
documentation. See also the section More 2889 below for further
information about PRTG Mini Probes.
screen.
Mini Probe Port
2886
This field is only visible if you select the extra Mini Probe port
option above. Enter the number of the port that you want to use
for Mini Probe connections. Ensure that SSL is available on this
port.
21.01.2016


screen.
ACTIVE DIR ECTOR Y INTEGR ATION

Domain Name
To use the Act ive Direct ory Int egrat ion 3083 enter the name of
your local domain. Please enter a string or leave the field empty.
Access Type
Define which user account PRTG will use to configure Active

Directory (AD) access. PRTG uses this account to query the AD for
existing groups. Choose between:
Use t he PRTG core service account (usually LOCAL SYSTEM):
Use the same Windows user account configured for the "PRTG
Core Server Service". In a default installation, this is the "local
system" Windows user account. If this account does not have
the right to query all groups of your Active Directory, do not use
this option.
Use explicit credent ials: Define a user account that PRTG will
use to authenticate against the Active Directory. This should be
a user account with full access to all of your Active Directory
groups.
Access User
This field is only visible if you enable the use of explicit credentials
above. Enter the Windows user account name that PRTG will use to
authenticate for Active Directory configuration.
Access Password
This field is only visible if you enable the use of explicit credentials
above. Enter the password for the Windows user account that
PRTG will use to authenticate for Active Directory configuration.
21.01.2016
2887

HISTOR IC DATA PU R GING LIMITS: SELECT FOR HOW MANY DAYS HISTOR IC
DATA R EMAINS ACCESSIBLE
Data purging enables you to automatically delete unnecessary data to free up disk space
and improve system performance. You can define different time spans for several kinds of
data. Select here for how many days historic data remains accessible. For further information
on storage locations, please see the Dat a St orage 3135 section.
Logfile Records
Define how long records in the system logfile Log Database.db will
be kept. Enter a value in days. All entries older than this value will
be deleted from the log file automatically. This also affects the
content of the Logs 169 tab of monitoring objects like sensors.
Keep this value as low as possible to enhance system
performance.
Web Server Log

Records
PRTG creates one web server log file every day. Define how many
web server log files are kept. Enter a value in days. All web server
log files files older than this value will be deleted automatically.
Historic Sensor Data
Define for how many days historic sensor data are kept for all
sensors. It is used to create reports 2786 of monitoring data. Enter a
value in days. Depending on the used intervals and the number of
sensors in your setup, the file containing this data can become
large. For smaller installations (500 sensors or less) a value of 365
should be fine. Historic sensor data is the basis for reports on
monitoring data. If you decrease this value, there will be less
historic monitoring data available!
Toplist Records
Define how long toplist records for Flow 3012 and Packet Sniffer 3010
sensors are kept. Enter a value in days. We recommend using 30
days here. However, old toplist data will be purged automatically as
soon as a limit of 2 GB is reached. Thereby the oldest data is
deleted first from the database.
Closed Tickets
Define how long tickets which are in status closed are kept. Enter
a value in days.
Reports
Reports generated in PDF format are stored on disk for later

reference. Define the maximum age for these reports. Enter a value
in days. All reports older than this value are deleted automatically.
Configuration AutoBackups
PRTG creates one backup of your configuration every day. Define

the maximum age for these backups. Enter a value in days. All
configuration backup files older than this value will be deleted
automatically.
Full HTTP Sensor

Screenshots
Define how long the screenshots of the HTTP Full Web Page
Sensor 859 (PhantomJS browser engine) are kept. Enter a value in
days. PRTG will delete older screenshots with every sensor scan.
2888
21.01.2016

Remote Probe Setup

Find more information about setting up remote probes in the Mult iple Probes and Remot e
Probes 3108 section.
More
Define IP Ranges
3094
Knowledge Base: Where can I find PRTG Mini Probes which are ready to use?
21.01.2016
2889

9 System AdministrationUser Accounts
7.12.9 Sy stem AdministrationUser Accounts

PRTG administrator users can change all users' account settings and add new users.
User Accounts Overview

To change a user's settings, select it from the list by clicking on the username. The available
setting options are the same as shown in the My Account 2830 settings of the currently
logged in user (plus some account control options).
To add a new user, click on the New User button. The options are the same as for existing
users (with slight differences).
To batch-add several users at once in a simple way, please click the Mult iple New Users
button. In the dialog box appearing, select an existing user group 2896 from the drop down
menu and enter or paste a list of email addresses. They can be separated by space, comma,
semicolon, or a new line. Click the Add button to confirm. For each address, PRTG will create
a new local user account within the selected user group, carrying the email address as value
for Login Name, Username, and Email Address. A new password will be generated
automatically and sent to the email address.
To add a new user group, click on the New User Group button. The options are the same as
for existing groups (with slight differences).
Access rights in PRTG are given via user groups. Please make sure a user account is member
of the correct user group 2896 and give access to this group in your device tree object's
settings 159 .
Note: Predefined objects cannot be deleted!
User Accounts Settings

U SER ACCOU NT
Login Name
Enter the login name for the user.
Display Name
Enter a name that the user recognizes. It will not be used for login
purposes.
2890
04.11.2015

U SER ACCOU NT
Primary Email Address
Enter the user's email address.
Password
Define the user password. For security reasons, the account

settings page does not contain the password. Choose between:
Don't change
Specify new password
If you choose to specify a new password, enter the old password
and then the new password twice.
Note: The new password must be at least 8 characters long. It
must contain a number and a capital letter. The password of a PRTG
Administrator user can only be changed by this PRTG Administrator
user himself.
Passhash
Click Show passhash to display the passhash for the selected

user. You need the passhash of a user if you use the PRTG
Applicat ion Programming Int erface (API) 3086 . This setting is
ACCOU NT CONTR OL
Account Type
This setting is only visible to administrator users. However, it will

not shown if the user who's account you want to modify is a
member of a group with administrative rights.
Define the account type for the current user. Choose between:
Read/Writ e User: You can change settings.
Read Only User: You can not edit any settings except your own
password. This is a good choice for public or semi-public logins.
user.
Allow Acknowledge
Alarms
This setting is only visible if read only user is enabled above.

Acknowledging an alarm is an action which requires write access
rights. However, you can explicitly allow this action to read-only
users. If enabled, they still do not have write access, but may
acknowledge alarms 162 . Choose between:
Allow: Allow acknowledging alarms for this user.
Deny : The user will not be able to acknowledge alarms.
04.11.2015
2891

ACCOU NT CONTR OL
Password Changes
Decide if you want the user to be able to change his account's

password or not. If you allow the user to change the password,
this option will be available in the My Account 2830 settings of the
respective user. Choose between:
User may change his account 's password
Deny t he right t o change t he password (default)
Note: This field is only visible if you edit this option for read-only
users as an administrator.
Primary Group
This setting is available only for administrator users. Select the

primary group for the current user. Every user has to be member of
a primary group to make sure there is no user without group
membership. Membership in other user groups is optional. For
user experience there is no difference between the primary and
other user groups.
Note: You cannot change the primary group of Active Directory
users. Users which you added with Act ive Direct ory Int egrat ion
3083 can only have this AD group as their primary group. If you need
to change this, please delete this user account and add it anew.
Status
This setting is only shown for administrator users. Define the

status of the current user. Choose between:
Act ive: The current user can login to the account.
Inact ive: The current user's login is disabled. Use this option to
temporarily deny access for this user.
user.
Last Login
Shows the time stamp of the user's last login. This setting is shown
U SER GR OU PS
Member of
2892
Shows the groups the current user is member of. Access rights to
the device tree are defined on group level. This setting is shown
04.11.2015

AU TO R EFR ESH AND ALER TING

Auto Refresh
Define if you want PRTG to reload web pages automatically for the
current user. Choose between:
Refresh pages (recommended): Automatically refresh the single
page elements on the web pages in PRTG.
No aut omat ic refresh: Do not automatically refresh web pages.
Auto Refresh Interval

(Sec.)
This setting is only relevant if you enable auto refresh above. Enter
the number of seconds that PRTG waits between two refreshes.
We recommend that you use 30 seconds or more. Minimum value
is 20 seconds.
Note: Shorter intervals create more CPU load on the server running
PRTG. If you experience load problems while using the web
interface (or PRTG maps 2810 ), please set a higher interval.
Play Audible Alarms
Define when an audible alarm will be played for the current user on
web pages whenever there are alarms 161 in PRTG. Choose
between:
Never: Do not play sound files on any web pages.
On dashboard pages only : When there are alarms, play a
predefined sound on dashboard 200 pages only. The sound
snipped will be played again with every refresh of the dashboard
page.
On all pages: When there are alarms, play a predefined sound on
all web pages. The sound will be replayed with every page
refresh.
For more information about audible notifications and supported
browsers, see the More 2835 section below.
WEB INTER FACE

Homepage URL
Define the user's default page, which is loaded after logging in or

clicking on the Home 200 button in main menu.
Max. Groups/Devices
per Group

specified number of items. Enter this threshold for groups and
04.11.2015
2893

WEB INTER FACE

Max. Sensors per
Device

specified number of items. Enter this threshold for sensors per
Timezone
Define the time zone for the current user. Depending on the time
zone you select here, PRTG shows the current user's local time
zone in all data tables and graph legends.
Note: PRTG receives the UTC (Coordinated Universal Time) from
the system time set on the PRTG core server for this purpose.
Date Format
Define the format of dates for the current user.

Note: This setting will take effect after the next login.
TICKET SYSTEM
Email Notifications
Define if you want to get emails from the ticket system. Choose
between:
I want t o receive an email whenever a t icket changes: You
will receive an email each time a ticket is assigned to you or your
user group, or if a ticket which is assigned to you or your user
group is changed.
Note: If you edit tickets which are assigned to you or your user
group, or you assign a ticket to yourself or your user group, you
will not get an email.
I do not want t o receive any emails from t he t icket sy st em:
You will not get any emails about tickets.
Notification Contacts
In the Not ificat ion Cont act s 2852 tab you can define recipients for each user account.
Recipients can be email addresses, phone numbers, or push devices (iOS, Android and
Windows Phone devices with the corresponding PRTG smartphone app 2995 ).
Comments
2894
04.11.2015

History
More
sound?
04.11.2015
2895

10 System AdministrationUser Groups
7.12.10 Sy stem AdministrationUser Groups

PRTG administrator users can change existing user groups or add new ones, and define the
users that are member of a certain group.
All the security settings as well as further rights management are conducted via the user
groups. This means that group membership controls what a user may do and which objects
the user will see when logged in. The actual rights for each object can be defined in an
object's settings. There, you can define different rights for each user group.
To change a user group's settings, select it from the list by clicking on the group name.
To add a new user, click on the New User button. The options are the same as for existing
users (with slight differences).
To batch-add several users at once in a simple way, please click the Mult iple New Users
button. In the dialog box appearing, select an existing user group 2896 from the drop down
menu and enter or paste a list of email addresses. They can be separated by space, comma,
semicolon, or a new line. Click the Add button to confirm. For each address, PRTG will create
a new local user account within the selected user group, carrying the email address as value
for Login Name, Username, and Email Address. A new password will be generated
automatically and sent to the email address.
To add a new user group, click on the New User Group button. The options are the same as
for existing groups (with slight differences).
For each user group you create, PRTG automatically adds a new group
[group_name] home to the device tree.
90
with the name
For each user group you create, PRTG automatically adds a new email notification 2841 to
notifications 2759 with read access rights 101 for this user group. It has the name Email to all
members of group [group_name].
By default, there are no access rights 101 on existing objects for a newly created PRTG user
group. Initially, users in this group will not see any objects in the PRTG device tree except
the automatically created home group (with write access rights). Please edit the object
settings 159 in your device tree and set access rights for your newly created user group in
the Inherit Access Right s section.
Note: The easiest way is to set these rights in the Root Group Set t ings 260 .
Note: The multi-edit option is not available for the standard user groups PRTG Administrators
and PRTG Users Group.
Note: Predefined objects cannot be deleted!
Note: If you want to delete an Active Directory group, you have to delete all users that are in
this group in PRTG first. This is because users which you add with Act ive Direct ory
Int egrat ion 3083 always have this group as their primary group.
2896
21.01.2016

User Groups Settings

U SER GR OU P SETTINGS
User Group Name
Enter a name for the user group.
Administrative Rights
Define if the members of this group will be PRTG administrators. If

you enable this option, all members of this group will have full
access to all monitoring objects, maps, reports, user accounts and
user groups, and they can change the PRTG monitoring
configuration. Choose between:
Yes: Give full PRTG administrator rights to all members of this
group.
No: Do not make members of this group administrators. Access
to monitoring objects for users that are member of this group
will be controlled by the Access Right s settings defined in the
Object Set t ings 159 of Probes, Groups, Devices, or Sensors.
Note: This option is especially useful in combination with the Active
Directory option below.
Default Homepage
Enter a PRTG internal web page. This will set the default homepage
for all new users created with this group. A user will be redirected
to this page after logging in. This concerns new users either added
by an Act ive Direct ory login or by the Add mult iple users
feature.
Use Active Directory
Define if this PRTG user group will be connected to a group in your

active directory. Choose between:
Yes: Connect this group to an AD group. Choose below. For
detailed information, please see Act ive Direct ory Int egrat ion
3083 .
No: Do not use Active Directory integration for this group, but
choose local user accounts instead.
21.01.2016
2897

Active Directory Group
If a valid Active Directory Domain is set in the Sy st em

Administ rat ionCore & Probes 2887 settings and Active Directory
integration is enabled above, a drop down menu will appear,
showing the groups in your Active Directory. Choose the group
whose members will be able to log in to PRTG using their Active
Directory domain credentials. All of those AD users will be in the
security context of the PRTG group you're about to create/edit.
For detailed information, please see Act ive Direct ory Int egrat ion
3083 .
If your Active Directory contains more than 1000 entries in total,
PRTG will display an input field instead of a drop down menu. This is
done due to performance reasons. In the input field, you can enter
the group name only. PRTG will then add the prefix automatically.
New User Type
If Active Directory integration is enabled above, define the default

rights for all new users in this user group. If a user logs in for the
first time using Active Directory credentials, PRTG will automatically
create a new local user account for this user, applying the user
type defined here. Choose between:
Read/Writ e User: The user may change settings.
Read Only User: The user may not edit any settings except the
own password. This is a good choice for public or semi-public
logins.
Allowed Sensors
Define if members of this user group will be able to create all

available sensor types or only specific ones. Choose between:
Users may alway s creat e all sensor t y pes: No restrictions for
group members are applied.
Users may creat e cert ain sensor t y pes only : Choose the
allowed sensor types below. This option is especially interesting
for a Managed Service Provider (MSP).
Users May Create

These Sensor Types
This field is only visible if you defined that the users in this group
are only allowed to create certain sensor types. A list of all
available types is shown with their name. Select the desired types
by adding check marks in front of the respective lines. You can
also select and deselect all items by using the check box in the
table head.
Ticket System Access
Define if the members of this user group will be able to use PRTG's
ticket system 171 . Choose between:
Members can use t he Ticket Sy st em: No restrictions for group
members are applied.
2898
21.01.2016

Members can NOT use t he Ticket Sy st em: The Ticket s 211
option in the main menu bar 211 will not be visible to users in this
group.
MEMBER S
Members
This setting is available only if Active Directory integration is

disabled above. Define which local user accounts will be a member
of this group. To add a user account from the list, add a check
mark in front of the username. The user accounts available depend
on your setup.
PR IMAR Y U SER S
User List
Shows a list of all user accounts with this group set as primary
group. This is shown for information purposes only. You can
change it in a user account's settings 2890 .
Comments
History
21.01.2016
2899

11 System AdministrationAdministrative Tools
7.12.11 Sy stem AdministrationAdministrative Tools

With the administrative tools you can start system specific processes for debugging purposes.
Use them if Paessler's technical support staff advises you to do so. You can start the
respective processes by clicking on the Go! button on the right.
Sy stem Administrativ e Tools
2900
09.07.2015

Core Administrative Tools

COR E ADMINISTR ATIVE TOOLS
Create Database
Snapshot
This will create a snap shot of your PRTG configuration. This action
can take up to 100 seconds. Once finished, you will find a ZIP file
containing a *.dat file in the Configurat ion Aut o-Backups sub
folder of your PRTG data directory 3135 . If you run a PRTG cluster, this
action is executed on the cluster node you are currently logged in
to. The ZIP file follows the name pattern PRTG Configuration
(Snapshot YYYY-MM-DD HH-MM-SS).zip.
Write Core Status File
This will create status files of your PRTG core server. You will find
the two text files in the Logs (Sy st em) sub folder of your PRTG
data directory 3135 . If you run a PRTG cluster, this action is executed
on the cluster node you are currently logged in to. The files are
named Core Status.txt and Core Memory.txt. They are overwritten
each time you click this button.
Clear Caches
PRTG caches tiles for Geo Maps 2753 and user data for Act ive
Direct ory Int egrat ion 3083 . Use this button to delete the cache if
you encounter broken geo map tiles, or if you changed a user's
password in the Active Directory.
Load Lookups
This will (re)load the lookup files 3095 from the \lookups\cust om
folder. In this folder your customized lookup files are stored. If you
have created a new lookup file or changed something in an
existing lookup file, it might be necessary to load or to reload
these files.
Recalculate PRTG
Graph Data Cache
PRTG writes monitoring data to the disk constantly and keeps the
graphs for your graph tabs in memory. If PRTG is ended
unexpectedly, the graph cache may get corrupted. In this case,
graphs may be shown empty or show wrong data.
If you experience graph display problems, a graph recalculation will
fix the problem. Click on Go! so that PRTG will delete the data
cache file and recalculate it automatically.
Note: If you apply recalculation, PRTG needs to restart the core
disconnected. After clicking on the Go! button, a popup will appear
which asks you to confirm the required core server restart. Click
on OK to trigger the restart and follow the instructions on the
screen.
Note: Directly after this action your graphs will be empty. They will
be re-filled successively while recalculation in the background
progresses. Until recalculation is finished, performance of the PRTG
web interface may be affected due to high disk I/O activity.
09.07.2015
2901

COR E ADMINISTR ATIVE TOOLS

Restart Core Server
You can restart the PRTG core server service manually. Click on
the Go! button for this purpose.
Note: If you restart the core server, all users of PRTG's web
interface, of the Ent erprise Console 2938 , or of Smart phone Apps
2995 will be disconnected. After clicking on the Go! button, a popup
will appear which asks you to confirm the required core server
restart. Click on OK to trigger the restart and follow the
instructions on the screen.
Note: If you want to schedule an automatic restart of Windows
services for both core server and probe service, you can do this in
the corresponding Probe Set t ings 295 .
Probe Administrative Tools

PR OBE ADMINISTR ATIVE TOOLS
Write Probe Status
Files
This will create status files of your PRTG probes. Status files will be
written for the local probe running on the PRTG core server (if
you're running a PRTG cluster, on the cluster node you're currently
logged in to) as well as for all remote probes configured (if any). On
the respective systems, you will find four text files in the Logs
(Sy st em) sub folder of the PRTG data directories 3135 . The files
follow the name pattern Probe Memory XX.txt, ProbeState XX.txt,
ProbeState AXX.txt, and ProbeState BXX.txt. They are overwritten
each time you click this button.
Restart All Probes
This will restart all PRTG probes as well as the local probe Windows
service. If there are any remote probes 3108 configured, the probe
Windows services on the respective remote systems will be
restarted as well. In order to start single probes only, please see
below. Note: If you run a PRTG cluster, this action is executed on
the cluster node you are currently logged in to. In this case,
remote probes are only restarted if you're logged in to the primary
master node. The cluster probe Windows service of failover nodes
is not restarted if this action is executed on the master node. If
you want to restart the cluster probe Windows service of a failover
node, please log in to this failover node's web interface and click
on the same button there.
2902
09.07.2015

PR OBE ADMINISTR ATIVE TOOLS

Probe [#Number]
"[Name]"
Information about the connection status is shown. If the probe is

currently connected, the field shows the source IP address and
port number used by the probe. For the "Local probe", the IP will
always be IP 127.0.0.1. You will also see information about the date
when the last data packet was received from the probe. If you
want to restart a single probe, please click on the Rest art Probe
button. Note: Entries for every single probe are following.
SetupTopics
2830
2836

2852
2856

2860
2871

2883
2890
2896
2905

PRTG St at usAut o Updat e
2907
2923
PRTG St at usAct ivat ion St at us
2925
2928
2930
09.07.2015
2900
2918
Downloads and Add-Ons
2877
2932
2903

Others
There are some settings that you must make in the PRTG Administ rat ion Tool
as native Windows application. For more details, please see the sections:
PRTG Administ rat ion Tool on Core Server Sy st em
, available
3047
PRTG Administ rat ion Tool on Remot e Probe Sy st em
2904
3046
3073
09.07.2015

12 System AdministrationCluster
7.12.12 Sy stem AdministrationCluster

In the cluster settings you can define the cluster settings. During Failover Clust er
Configurat ion 3122 , the cluster settings were already pre-defined. See the cluster status
see if all nodes in your cluster are properly connected.
2923
to
Cluster Settings
You can set up two, three, four, or five nodes in one cluster. In the table of the cluster
settings, the information of each node is written in one line.
CLU STER NODE SETU P

Node Name
Enter the name of the node (for display purposes).
Node ID
The ID is unique for every node. We recommend that you use the
default value.
Node State
You can set the state for every failover node. Choose between:
Act ive: Set the node to be active.
Inact ive: Set the node to be not active. It will be disabled in the
cluster configuration. It will then be not an active part of the
cluster and will not appear in the cluster status 2923 any more.
This setting is not available for the master node of a cluster. The
master is always set to Act ive.
IPs/DNS Names Used

for Connections
Between Nodes
Define the IP addresses or DNS names that will be used for the
connections between the nodes. You can enter different values for
every nodenode connection.
For example, in the field #2 => #1, enter the address under which
the master node server can be reached from the second cluster
member. Usually, this is the IP address or DNS name of the master
node. Do this for all available node connections, for example, if you
run three nodes, enter the address under which second node can
be reached from the third cluster member into the field #3 => #2.
21.10.2015
2905

12 System AdministrationCluster
CLU STER NODE SETU P

Please see also section Failover Clust er St ep by St ep, St ep 4
and following.
3131
Note: If you use remote probes 3109 outside your local network or
outside your Network Address Translation (NAT), ensure the IP
addresses or DNS names you enter here are valid for both the
cluster nodes to reach each other and for remote probes to reach
all cluster nodes individually. These addresses must not be private
and have to be reachable from the outside, otherwise your remote
probes will not be able to connect.
For how to set a cluster node into Maint enance Mode, please see PRTG St at usClust er
St at us 2923 .
The entire setup process for a cluster requires several different steps. For more information
and step-by-step guidance, please see Failover Clust er Configurat ion 3122 section.
2906
21.10.2015

13 PRTG StatusSystem Status
7.12.13 PRTG StatusSy stem Status

To view the status of your PRTG installation, select Set up | PRTG St at us from main menu. Click
on the tabs to change the different settings.
PRTG Status Tabs
You can view the following aspects of the PRTG status:

2907
2923
System Status
Click on the Sy st em St at us tab to view relevant system information. You might need this data
for debugging or when you contact our support team. They ask you in some cases to provide
PRTG status information to analyze your issues with PRTG. Furthermore, this page shows
interesting usage statistics.
SOFTWAR E VER SION AND SER VER INFOR MATION

PRTG Version
Shows the exact version of the build your PRTG installation is

currently running on.
Auto-Update Status
Shows the latest auto-update message available from Soft ware

Aut o-Updat e 2918 . For example, the message will indicate any PRTG
updates ready to be installed.
Operating System
Shows the exact Windows version build and service packs, the
number and kind of CPUs, and the computer name, of the system
the PRTG core server is installed on. If you run a PRTG cluster, this
will show information for the system of the cluster node you're
currently logged in to. Note: When running PRTG on virtual
systems, not all of the mentioned values may be available.
Server Time
Shows the date and time of the system the PRTG core server is
installed on. If you run a PRTG cluster, this will show information for
the system of the cluster node you're currently logged in to.
Server CPU Load
Shows the current CPU load of the system the PRTG core server is
installed on. If you run a PRTG cluster, this will show information for
11.03.2016
2907

SOFTWAR E VER SION AND SER VER INFOR MATION

Username
Shows the username

in as.
Browser
Shows the name and user agent string of the browser you're
currently viewing this page with.
2830
of the PRTG user you're currently logged
LICENSING
Licensee
Shows the name of the license 62 that you use for this installation
of PRTG. Licensee (name) and license key together build your
license information.
Key
Shows the beginning and the end of the license 62 key that you
use for this installation of PRTG. Licensee (name) and license key
together build your license information.
Edition
Shows the PRTG edition that you use for this installation of PRTG.
This determines how many sensors you can use in your monitoring
(see below).
Activation Status
Shows the activation status of this installation of PRTG. Usually,

activation is done automatically on first start-up. Only if PRTG
cannot connect directly to the internet, a manual activation is
necessary. For details, please see Act ivat e t he Product 65 .
Current Activation
Stamp
Shows an internal activation stamp code.
Software Maintenance
Shows the days remaining for your active maintenance contract.

You can buy maintenance for each PRTG license. With an active
maintenance contract you may download any available updates and
use our premium email support, without additional costs.
Number of Sensors
Shows the number of sensors you can use in your monitoring with
your current edition of PRTG (see above). If you reach the limit,
PRTG sets each new sensor that you add to a Pause status 135
automatically. To upgrade your license right now, click the Need
more sensors? Click here t o upgrade! button to visit our web
shop.
2908
11.03.2016

LICENSING
Editions that allow an unlimit ed number of sensors do not restrict
the number of possible sensors by license, so you can create
sensors until the performance limit 23 is reached. This means that
you can use about 10,000 sensors per core server (depending on
your system's performance, sensor types, and scanning intervals).
For details, see section Det ailed Sy st em Requirement s 23 .
SYSTEM STAR TU P LOG

Shows the log information created during the last startup of the PRTG core server. If you run
a PRTG cluster, this will show information for the system of the cluster node you're currently
logged in to.
SYSTEM WAR NINGS

If there are any warnings, PRTG will show them here. Usually, you will see "None" system
warnings.
CLU STER STATU S

This box is only visible if you run a PRTG cluster. This section lists all cluster nodes
configured in your monitoring.
Node [Number]
11.03.2016
Shows the name of the cluster node as well as the node type
(primary/secondary node) and status (current master/failover
node). Additionally, all connections from this node to the other
cluster nodes are shown, as illustrated on the PRTG St at us
Clust er St at us 2923 page.
2909

LOCAL STATU S
This box is only visible if you run a PRTG cluster. This section lists information about the
cluster node you're currently logged in to.
Server State Cluster
Messages
Shows internal summary information about the current node and

the communication between the nodes. You might be asked about
this by Paessler's technical support staff.
CLU STER CONNECTIONS

This box is only visible if you run a PRTG cluster. This section lists information about the
connections between the different cluster nodes.
State of Local Node
Shows Treeversion and size of the Server Volume, both internal

system information.
State of Cluster
Members
For each cluster node, the name and IP address is shown, as well
as a state CRC code, the time stamp of the last "keep alive" signal
sent, the current size of the buffer, and the remote IP.
Message State of
Cluster Members
For each cluster node, the name, IP address, and unique identifier is
shown, as well as the connection state, and statistic information
about the cluster message system which is used for the
communication between the different nodes.
COR E SYSTEM MEMOR Y

Shows machine-oriented information regarding the memory usage of the core server
system. If you run a PRTG cluster, this will show information for the system of the cluster
node you're currently logged in to.
2910
11.03.2016

THR EAD INFOR MATION

Shows machine-oriented information regarding the threads running on the core server
system. If you run a PRTG cluster, this will show information for the system of the cluster
node you're currently logged in to.
ACTIVITY HISTOR Y
The "Activity History" shows how busy PRTG was for you in the past. The graphs indicate the
number of activities on the last 365 days. Right to the graphs, you see statistics about the
past day.
Sensor Scans
Shows how often all sensors

their data in the past.
Sensor State Changes
Shows how often the Sensor St at es
Notifications Sent
Shows how many Not ificat ions
Reports Generated
Shows how many Report s
Page Views
Shows how often pages in the PRTG web interface were opened in
the past.
Sensors
Shows how many sensors

the past.
92
Devices
Shows how many devices

past.
91
Reports
Shows how many Report s

the past.
Maps
Shows how many Maps

past.
11.03.2016
2810
92
2786
in this PRTG installation refreshed
2759
135
changed in the past.
PRTG sent out in the past.
PRTG created in the past.
existed in this PRTG installation in
existed in this PRTG installation in the
2786
existed in this PRTG installation in
existed in this PRTG installation in the
2911

AU TO-DISCOVER Y TASKS
Currently Running
Shows the number of auto-discovery tasks that are currently

running. A high number of auto-discovery tasks can negatively
influence system performance.
BACKGR OU ND TASKS
Historic Data
Shows if PRTG is re-calculating the historic data cache in the

background. If so, you will see the tasks to do until done. Usually,
this calculation is done after every core server restart.
Toplist Buffer
When using xFlow 3012 or Packet Sniffer 3010 sensors, PRTG stores
Toplist data. The data stream received is buffered and written to
the data directory of the core system. Depending on the number
and size of the data stream as well as the hard disk and system
performance of the core system, the buffer size can rise. When
reaching a buffer size of 500, Toplist data is dropped which can
lead to incorrect Toplist values for the sensors.
Toplist Upgrade
If you recently updated from an older PRTG version (7 or 8), Toplist

data needs to run through a one-time conversion process. While
conversion is running you may experience a considerably slow
monitoring system. Usually, you will see n/a here.
Similar Sensors
Analysis
Shows the current status and the selected setting for the analysis
depth of the Similar Sensors 151 analysis.
Recommended
Sensors Detection
Shows the current status of the detection engine and the current
tasks of the Recommended Sensors Det ect ion 2874 .
DATABASE OBJECTS
Shows statistic information about your monitoring configuration. This information might be
necessary when contacting Paessler's technical support staff.
Probes
2912
Shows the total number of probes
278
configured.
11.03.2016

DATABASE OBJECTS
Groups
Shows the total number of groups
Devices
Shows the total number of devices
Sensors
Shows the total number of sensors
User Groups
Shows the total number of user groups
Users
Shows the total number of users
Notifications
Shows the total number of notifications
Schedules
Shows the total number of schedules
Maps
Shows the total number of created maps
Libraries
Shows the total number of created libraries
Reports
Shows the total number of reports
Requests/Second
Shows a value calculated from the total number of sensors and the
average scanning interval configured. This number indicates how
many monitoring requests per second are sent from the probe(s)
to the devices in your network. There are no general guidelines
what is a "good" value here. This depends on the sensor types
used as well as on your system's performance.
Sensors
Shows a list with numbers and types of sensors used in your

configuration.
299
2890
324
347
in your configuration.
2896
configured.
2786
2856
2836
configured.
configured.
2810
in your installation.
2770
Note: In the list, internal short names are used for sensor types
instead of the official designations.
SENSOR S BY PER FOR MANCE IMPACT

Shows all sensor types used in your configuration ordered by performance impact (from
very low to very high). If your PRTG system is very slow, you can see which sensors might
cause this issue. Please consider the recommended number of sensors in the respective
manual sections 347 for sensors with high and very high performance impact.
11.03.2016
2913

SENSOR S BY PER FOR MANCE IMPACT

Note: In the list, internal short names are used for sensor types instead of the official
designations.
SENSOR S BY INTER VAL

Shows all sensor types used in your configuration ordered by scanning interval. Please
choose reasonable scanning intervals for sensors which can affect the system
performance. See the respective manual sections 347 for sensors for more information.
Note: In the list, internal short names are used for sensor types instead of the official
designations.
PR OBES
This section lists all probes configured in your monitoring. If there are no remote probes
configured, only the "Local probe" appears in the list, which runs mandatorily on the PRTG
core server.
Note: If you run a PRTG cluster, this will show information for the system of the cluster node
you're currently logged in to. Remote probes (if any) will only be shown when you are
logged in to the primary master node. When logged in to a failover node, the cluster probe
running on this node will appear as "Local probe".
Probe [#Number]
"[Name]"
2914
Information about the connection status is shown. If the probe is

currently connected, the field shows the source IP address and
port number used by the probe. For the "Local probe", the IP will
always be IP 127.0.0.1. You will also see information about the date
when the last data packet was received from the probe. If you
want to restart a single probe, please go to the Administ rat ive
Tools Set t ings 2900 .
11.03.2016

SYSTEM SETTINGS
Web
Server
URL
Shows the URL to access the PRTG web interface 108 . If you run a PRTG cluster,
this will show information for the system of the cluster node you're currently
logged in to.
Web
Server
IPs
Shows all IP addresses the PRTG web server is running at. If you run a PRTG
cluster, this will show information for the system of the cluster node you're
currently logged in to.
Web
Server
Ports
Shows the port the PRTG web server is running at. If you run a PRTG cluster, this
will show information for the system of the cluster node you're currently logged
in to.
Web
Server
Port
Usage
Shows the number of ports used by the PRTG web server.
Incomin
g Probe
Connect
ion
Binding
Shows a combination of the two values below.
Incomin
g Probe
Connect
ion IPs
Shows a list of all IP addresses on which your current PRTG installation listens to
incoming remote probe connections. This is the same information as shown in
the Sy st em Administ rat ionCore & Probes 2883 settings. 0.0.0.0 means that the
core server listens on all local network adapter IPs.
Incomin
g Probe
Connect
ion Port
Shows the port number on which your current PRTG installation listens to
incoming remote probe connections. The default port is 23560.
Probe
Shows all source IP addresses that will be accepted by the core server for
Allow IPs incoming remote probe connections. This is the same information as shown in
the Sy st em Administ rat ionCore & Probes 2883 settings and can be changed
there. any means that all remote probe connections are accepted, regardless of
the IP address of the remote probe system.
Probe
Deny IPs
11.03.2016
Shows all source IP addresses that will be denied by the core server for incoming
remote probe connections. This is the same information as shown in the Sy st em
Administ rat ionCore & Probes 2883 settings and can be changed there. Denied
IPs are superior to allowed IPs. If this field is empty, there are no denied IPs. Note:
PRTG automatically adds the IP address of a remote probe system to this list
when you delete a remote probe from your device tree 89 .
2915

SYSTEM SETTINGS
DataPath Shows the path where PRTG stores its configuration, monitoring database, etc. If
you run a PRTG cluster, this will show information for the system of the cluster
node you're currently logged in to. In order to change this setting, please open
the PRTG Administ rat ion Tool 3047 on the system of the PRTG core server (or of
the respective cluster node, if applicable).
WEB SER VER ACTIVITY

Shows statistic information about the web server since last startup. All values are reset
when the core server is restarted. If you run a PRTG cluster, this will show information for
Time Since Startup
Shows the time that has passed since the PRTG web server was
started.
Page Views
Shows the total number of page views on this core server.
Geo Maps
Shows the total number of geo maps shown on this core server.
HTTP Requests
Shows the total number of HTTP requests to this core server.
HTTP Requests >

500/1000/5000 ms
Shows for how many (percent) of the HTTP requests above the
page delivery took longer than 500, 1,000, or 5,000 milliseconds.
Slow Request Ratio
Shows a calculated number of the HTTP request values above. The

lower this number, the faster is your installation's web interface.
SYNCHR ONIZATION
The core server holds the configuration of the entire monitoring and deploys it to the
probes. This section shows statistic information about the synchronization of the core
server with the local probe and all connected remote probes (if any), since last startup of
the core server. All values shown here are reset when the core server is restarted. If you
run a PRTG cluster, this will show information for the system of the cluster node you're
currently logged in to.
2916
11.03.2016

SYNCHR ONIZATION
Note: Only when logged in to the primary master node, you will see synchronization data for
remote probe connections.
Last Synchronization
with a Probe
Shows the time stamp of the last probe synchronization, and if

there is still something to do.
Probe/Core Message
Count
Shows the total number of messages sent between core and

probe(s), as well as a calculated message speed value.
Raw Buffer Count
Shows the number of raw buffers and a corresponding status

indicator.
Sync Cycle Speed
Shows the time necessary for a full synchronization, as well as an

evaluation comment of this time (usually, this will be "OK").
Configuration
Requests Sent
Shows the total number of configuration requests and the

requests that still have to be sent.
Configuration
Requests Deleted
Internal debug information. Usually, this value will be 0.
Configuration
Requests With
Response
Internal debug information. Usually, this value will be 0.
More
Paessler Website: Detailed System Requirements for PRTG Network Monitor
https://www.paessler.com/prtg/detailed-requirements
11.03.2016
2917

14 PRTG StatusAuto-Update
7.12.14 PRTG StatusAuto-Update

Whenever a new version of the software is available from the Paessler website PRTG will
download the setup file automatically if a direct internet connection is available. The PRTG
Sy st em Administ rat or user will then receive a ToDo ticket 172 with instructions to initiate the
update installation.
For customers using a Freeware or Trial Edition 20 , automatic software updates are available at
any time. Customers using a Commercial Edition 20 need to have an active maintenance
contract so updates are available.
Status
To view the auto-update page of your PRTG installation, select Set up | Aut o-Updat e from main
menu. On the St at us tab you can download and perform updates.
Using Auto-Update
If there is a new version available, you will see detailed information about the available version.
Please read these notes carefully! You find a summary of current and past release notes below
the update section. For detailed release notes, click PRTG Release Not es and Version
Hist ory which will redirect you to the version history page on paessler.com.
To install the latest available version, click Inst all Updat e [version number]. PRTG will ask you
to confirm installation and licenseand that's it!
2918
11.03.2016

Automatic Software Update Page
Manually Install an Interim Update

Not all available updates from Paessler will be pushed to all customers, but they are still
available from the website. Sometimes Paessler support may ask you to update to the latest
version.
In this case please click the Check For Lat est Updat e and Download button. PRTG will then
connect to the Paessler servers and download the setup file, regardless of the status of the
update-check. Then Inst all Updat e [version number].
Note: To use this function, a direct internet connection is necessary on the computer running
the PRTG core server.
Select Other Release Channel

PRTG is available in three different release channels. For details about continuous rollout and
release channels, please see the blog article in the More 2922 section below.
To change the release channel you receive updates from, please open the auto-update
Set t ings 2920 tab and choose the desired release channel in the Release Channel section.
11.03.2016
2919

Log
Click the Log tab to show log information about the update status of PRTG, newest first. In
the table list 178 appearing, you can filter the items by using the respective options 178 . For
more information, please see the Logs 169 section.
Settings
Click the Set t ings tab to configure the PRTG Soft ware Aut o-Updat e.
SOFTWAR E AU TO-U PDATE

When a New Version is
Available
Define what to do when there are software updates available.

Choose between:
Aut omat ically download and inst all t he lat est version: PRTG
automatically downloads and installs any new version as soon as
PRTG detects that there is a newer version available (PRTG
checks this once per day).
Note: Without prior notice, the installation of a new version will
restart the PRTG Windows services and may also include a server
restart.
Aut omat ically download t he lat est version and alert t he
admin: PRTG automatically downloads any new version as soon
as PRTG detects that there is a newer version available (PRTG
checks this once per day). After successful download, PRTG will
create a ToDo ticket 172 for the PRTG System Administrator user.
Alert t he admin only : When PRTG detects that there is a newer
version available, it will not download updates automatically, but
create a ToDo ticket 172 only. You can still download updates
manually on the Aut o-Updat e 2919 page.
Installation Time
If you select the automatic installation option above, choose the

desired time for installation of updates from the drop-down menu.
Release Channel
PRTG updates are delivered in different release channels. You can

choose between maximum stability, or most early access to new
features. Please choose between:
St able: Updat ed about once per mont h (most conservat ive
opt ion, recommended): These are our best tested versions.
Choose this channel for live environments you have to depend
on!
2920
11.03.2016

SOFTWAR E AU TO-U PDATE

Preview: Updat ed about once per week: Versions in this
channel are already thoroughly tested in our labs, but may still
contain limitations in certain monitoring configurations. Choose
this channel if you are willing to take a little risk for the benefit of
getting new features and bug fixes a little earlier. We strongly
recommend to not use those versions in live environments you
have to depend on!
Canary : Updat ed daily (t est ing only , should not be used on
live sy st ems): Updated every night. Use with CAUTION! Software
versions in this channel are not tested yet, might contain severe
bugs, and are provided for testing purposes only. We strongly
recommend to not use those versions in live environments you
have to depend on!
For more information about the different release channels, please
see the blog article linked in the More 2869 section below.
Notes
There are a few things we ask you to consider regarding automatic software updates:
In order for auto-update to work the machine running the PRTG core server needs direct
internet access. If a proxy connection is needed, please configure it in the Sy st em
Administ rat ionCore & Probes 2883 settings. For details about the update servers, see the
During installation the core server may be restarted without notice.
PRTG updates existing remote probes automatically, causing short downtimes in monitoring
of remote locations. In rare cases a manual update of remote probes is required after you
update the core server. In these cases you will be notified in the device tree, and monitoring
of remote locations will be interrupted until you perform the manual update 3117 on the
system(s) running the remote probe(s). If a server with a probe uses several network
connections with different IP addresses, ensure these addresses are included in the list of
allowed IPs 2884 . Otherwise the remote probe on this machine might be disconnected after an
update.
In a cluster installation the update needs to be installed on one node only. The new version
will then be deployed to all other cluster nodes automatically (causing a short downtime for
the monitoring on the cluster nodes, one after another).
If you run several individual PRTG core servers that are not in a cluster, for example, in
combination with the Ent erprise Console 2938 , an update has to be initiated and confirmed
for each single core server.
You can disable automatic downloading on the Aut o-Updat e Set t ings 2920 tab. Updates will
then only be downloaded on request, when you click on the Check For Lat est Updat e and
Download button.
11.03.2016
2921

PRTG does not start auto-update downloads if there is less than 500 MB disk space available
on the core server system. If this is the case, you can check this on the Log 2920 tab.
More
Knowledge Base: Which servers does PRTG connect to for Software Auto-Update and for
Activation?
Knowledge Base: Which information does PRTG send back to Paessler?
Paessler Blog: Version 12 of PRTG will introduce "Continuous Rollout"
https://www.paessler.com/blog/2012/04/25/news/prtg-12-introduces-continuous-rollout
2922
11.03.2016

15 PRTG StatusCluster Status
7.12.15 PRTG StatusCluster Status

To view the status of your PRTG installation, select Set up | PRTG St at us from main menu. Click
on the tabs to change the different settings.
PRTG Status Tabs
You can view the following aspects of the PRTG status:

2907
2923
Cluster Status
Click the Clust er St at us tab to view all nodes connected to the cluster. This tab is only
available if you run PRTG in cluster mode 87 . The following information is available:
Cluster Status with all connected nodes as table and graphic
Cluster Log with all log entries concerning cluster connections
15.03.2016
2923

15 PRTG StatusCluster Status
Example of a PRTG Cluster Status View
Click the St art Maint enance Mode link to put a cluster node in maintenance mode. A node in
this mode is still connected to the cluster, but its monitoring results are discarded until you
click the St op Maint enance Mode link. You can use this functionality to explicitly exclude a
node from monitoring if you know that the monitoring values will not be accurate, for example,
because you reconfigure the failover server. During maintenance, a cluster node is displayed
with a transparent color in the overview graphic.
Note: You will not see on this page if your remote probes are connected to failover nodes 3125 .
Please connect to your failover nodes and check explicitly if remote probes are connected (for
example, in the device tree of the PRTG web interface on a cluster node).
For more information about cluster settings, please see Sy st em Administ rat ionClust er
section.
2924
2905
15.03.2016

16 PRTG StatusLicensing Status and Settings
7.12.16 PRTG StatusLicensing Status and Settings

To view information about the license of your PRTG installation and to enter your license key,
select Set up | License | St at us from the main menu. Click the tabs to change the different
settings.
PRTG Lic ense Tabs
You can view the following aspects of your PRTG license:

Your LicenseSt at us
Your LicenseLog
2925
2926
Your LicenseEnt er License Key
2926
Status
Click on the St at us tab to view information about your license.
LICENSING
Licensee
Shows the name of the license 62 that you use for this installation
of PRTG. Licensee (name) and license key together build your
license information.
Key
Shows the beginning and the end of the license 62 key that you
use for this installation of PRTG. Licensee (name) and license key
together build your license information.
Edition
Shows the PRTG edition that you use for this installation of PRTG.
This determines how many sensors you can use in your monitoring
(see below).
02.11.2015
2925

LICENSING
Activation Status
Shows the activation status of this installation of PRTG. Usually,

activation is done automatically on first start-up. Only if PRTG
cannot connect directly to the internet, a manual activation is
necessary. For details, please see Act ivat e t he Product 65 .
Current Activation
Stamp
Shows an internal activation stamp code.
Software Maintenance
Shows the days remaining for your active maintenance contract.

You can buy maintenance for each PRTG license. With an active
maintenance contract you may download any available updates and
use our premium email support, without additional costs.
Number of Sensors
Shows the number of sensors you can use in your monitoring with
your current edition of PRTG (see above). If you reach the limit,
PRTG sets each new sensor that you add to a Pause status 135
automatically. To upgrade your license right now, click the Need
more sensors? Click here t o upgrade! button to visit our web
shop.
Editions that allow an unlimit ed number of sensors do not restrict
the number of possible sensors by license, so you can create
sensors until the performance limit 23 is reached. This means that
you can use about 10,000 sensors per core server (depending on
your system's performance, sensor types, and scanning intervals).
For details, see section Det ailed Sy st em Requirement s 23 .
Log
Click on the Log tag to show a table list of all system log entries with all messages and status
changes regarding your license.
Enter License Key

Click on the Ent er License Key tab to enter name and key for your PRTG Network Monitor
license. You can also view your licensed edition. For more details about activation, please see
Act ivat e t he Product 65 section.
2926
02.11.2015

SOFTWAR E LICENSE
License Name
Enter the license name you have received from Paessler via email.
To avoid typing errors, please copy and paste the License Name
from the email. It must be transferred exactly as shown in the
email.
License Key
Enter the license key you have received from Paessler via email. To
avoid typing errors, please copy and paste the License Key from
the email. It must be transferred exactly as shown in the email.
Licensed Edition
Shows the edition of the license that you currently use for this
installation of PRTG. This determines how many sensors you can
use in your monitoring. If you run a PRTG cluster, this field shows
information for the system of the cluster node you are currently
logged in to.
02.11.2015
2927

17 Optional Downloads and Tools
7.12.17 Optional Downloads and Tools

To see optional downloads, select Set up | Downloads from the main menu. Click a tab to
switch between different options.
Downloads Tabs
There are the following downloads available:

Client App for Windows (Enterprise Console)
Remote Probe Installer
PRTG Tools
2928
2928
2928
2928
2928
Client App for Windows (Enterprise Console)

Download the Windows Graphical User Interface (GUI) Enterprise Console to the current
system. If you use the Enterprise Console, you can access the PRTG interface with a native
Windows application. The version of the Enterprise Console must match the version of your
PRTG server. For more information, please see Inst all t he Ent erprise Console 72 .

To monitor your network while on the go, use our free apps for smartphones and tablets.
They run on iOS, Android (including BlackBerry devices), and on Windows Phone. For more
information on PRTG for iOS, PRTG for Android, and PRTG for Windows Phone, please see
the More 2929 section below.
Remote Probe Installer

With remote probes you can extend your monitoring to distributed networks that are not
directly reachable from your PRTG core installation. The version of the remote probe installer
must match your version of PRTG. For more information, please see Inst all a PRTG Remot e
Probe 67 .
PRTG Tools
You can use several freeware tools directly from the Paessler labs which help you to manage
your network and to diagnose and test network monitoring issues. Open the PRTG Tools tab
and click the More Informat ion and Download button to navigate to Paessler's freeware
tools webpage. There you can find a collection of various tools for PRTG Network Monitor.
This tab is only visible if you access the PRTG web interface with Google Chrome or Firefox
browser. For details, please see Deskt op Not ificat ions 2930 section.
2928
21.01.2016

17 Optional Downloads and Tools
More
Paessler Website: Mobile Network Monitoring with PRTGMobile Apps for Smartphones and
Tablets
https://www.paessler.com/apps
Paessler Website: Freeware Network Tools
https://www.paessler.com/tools
21.01.2016
2929

18 Desktop Notifications
7.12.18 Desktop Notifications

While you are logged in to the PRTG web interface with your Chrome or Firefox browser, PRTG
can show notifications on your desktop whenever there are new alarms in your monitoring.
PRTG will show desktop notifications (by default, in the lower right corner of your desktop)
whenever there are new alarms after a page refresh in the PRTG web interface. The notification
displays the number of new alarms and the current number of each sensor status.
Example of a Chrome Desktop Notific ation
You have to initially allow those notifications for each installation/profile of Firefox or Google
Chrome. In the PRTG web interface, click Set up 2828 and choose Deskt op Not ificat ions.
Note: Desktop notifications are not available for Internet Explorer.
Desktop Notifications Settings

On the settings page, you see one of the following status messages.
St at us: Click but t on below t o enable Deskt op Not ificat ions
Click the Enable Deskt op Not ificat ions button to add your PRTG URL to the list of allowed
sites for desktop notifications in Chrome or Firefox.
On top of your browser window a message appears, asking you to allow desktop
notifications.
In Chrome, click Allow to add the URL of the PRTG web interface to the allowed sites.
In Firefox, click Alway s Show Not ificat ions to add the URL of the web interface to the
allowed sites.
Clic k 'Allow' to enable Chrome Desktop

Notific ations
2930
15.04.2016

18 Desktop Notifications
Clic k 'Alway s Show Notific ations' to enbale Firefox Desktop Notific ations
St at us: Sorry , Deskt op Not ificat ions cannot be enabled or Unknown

Desktop Notifications are explicitly blocked for the URL of the PRTG web interface in the
browser options. Please see section Disabling or Re-Enabling Desktop Notifications 2931
below.
St at us: Deskt op Not ificat ions enabled
Desktop Notifications are successfully activated. To disable them, please see Disabling or ReEnabling Desktop Notifications 2931 below.Microsoft Internet Explorer 11
Disabling or Re-Enabling Desktop Notifications

To disallow or re-allow desktop notifications for the PRTG web interface, edit your browser
options:
In Google Chrome: Click the View sit e informat ion symbol in the address bar of the
browser. You can block or re-allow notifications for the current URL in section Permissions.
In Firefox: In the PRTG web interface, hold the Shift key and right-click to open the browser's
context menu. Click on View Page Info and select the Permissions tab. In section
Not ificat ions, select the desired option for the PRTG website, for example, block desktop
notifications or enable them again.
15.04.2016
2931

19 SupportContact Support
7.12.19 SupportContact Support

To open the Cont act Paessler Support / Send Your Feedback t o Paessler window in PRTG,
choose Set up | Cont act Support from the main menu. You can open this form also via the
footer Cont act Support on any page in PRTG.
On the one hand, you can adapt this page as feedback form. Help improve PRTG by providing
criticism, praise, bug reports, and feature requests. Any comments are welcome! Your feedback
will be handled directly by the Paessler support team.
On the other hand, you can use this function to ask for support regarding technical issues. To
make the support contact more comfortable, PRTG can automatically attach a screenshot in
combination with a Support Bundle which contains several selected PRTG log and status files.
This information will help our support team a lot to analyze any issues you may have with
PRTG. Please also consider the suggested links to articles regarding the scope of your issue.
Note: PRTG transmits your feedback or support question including the support bundle 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
2932
21.01.2016

Contac t the Paessler Support or Send Feedbac k
Ask a Question or Give Us Your Feedback

Provide the following information in this section of the contact form:
Your Ticket ID PAExxx: If you have already opened a new ticket (either directly via email to
support@paessler.com, or via the Knowledge Base, or via the support form on paessler.com),
enter its ID here. You can find it in your confirmation email regarding the request we
received. You can provide the ID with "PAE" in front or just the number. If you leave this field
empty, you will create a new ticket when you submit this form.
21.01.2016
2933

Your Email Address: Enter your email address here. You can provide any of your addresses;
however, recommended and default is the email address of your PRTG account to be able to
associate you with your license.
Scope of Your Quest ion: Select a topic regarding your issue and consider the proposed
links.
Emot ional St at e: If you want to, you can indicate your current feelings about PRTG.
Describe Your Quest ion in One Sent ence: Provide short information that indicates the
topic of your issue.
Do You Have Any Furt her Comment s?: Leave your comments here. It can be feedback or
support questions. Please describe your issue as detailed as possible!
Attach a Screenshot and/or Support Bundle

To provide as helpful information as possible, you can attach a screenshot of the current page
and various support bundles with useful analytical data about your PRTG installation.
In section Screenshot , choose between:
Do not at t ach screenshot : Send the ticket without a screenshot.
Note: We recommend that you attach a screenshot of the affected PRTG webpage so that
we can understand your request easier and faster.
Creat e and at t ach screenshot (recommended): Create a screenshot of the currently
displayed page in PRTG to send it with your ticket. You can see a preview below the
screenshot section.
Note: If you encounter issues on a specific page in PRTG, call the contact support form on
this page to get a screenshot of it.
In the section Support Bundle, you can choose between several packages which differ in
coverage of information:
At t ach Base Pack wit h log files (recommended): Contains log files of your PRTG
installation and the following information:
System status
Lists of sensors regarding their current states
Core state data
Probe Health sensor data
Current log entries
At t ach Base Pack wit h log files and PRTG configurat ion file: Additionally contains the
configuration file.
Note: Send this package only if our support team told you so! Encrypted passwords in the
config.dat file and passwords that your browser masks while you enter them on settings
pages will be removed before PRTG sends this package to Paessler Support.
Do not at t ach a Support Bundle: The ticket will not contain files. Choose this option only
when sending feedback.
2934
21.01.2016

Click the Submit button to send your request directly to our technical support team, or click
Cancel to return to the page from which you opened the contact form. Usually you will receive
an answer by our support team within one or two business days, no matter whether you
provide feedback or you have a question.
Note: If you have questions or feedback regarding your license purchase, upgrade, or
maintenance extension, please contact our customer service 121 .
More
Knowledge Base: How does Paessler handle user feedback and feature requests?
21.01.2016
2935
Part 8
Enterprise Console
27.04.2016
2937
Part 8: Enterprise Console |
Enterprise Console
The Enterprise Console (in old PRTG versions called "Windows GUI") is one alternative interface
83 that you can use to connect to the PRTG core server to configure your setup, view
monitoring results, and keep an eye on your network. It is a native Windows application for
fast access to data and monitoring management.
The Enterprise Console (EC) provides extended pop-up window functionalities, as well as a
seamless link to the Ajax web interface 108 where you can change your monitoring
configuration and access further functionalities such as reporting 2961 , maps 2959 , system setup
2967 , tickets 2965 , and libraries 2953 . The EC shows most of the functions with an embedded webkit
browser, for a few options the EC opens an external browser window (using your default
browser).
Note: The Enterprise Console runs under all supported Windows versions 23 , 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.
Note: The Enterprise Console does not support Sy st em Informat ion 164 and does not show
this tab on devices. Please use the PRTG web interface to access system information of a
device.
Access Several Core Servers in One Console

As an additional functionality, you can configure access to several PRTG core servers in the
Enterprise Console. It can show data of all your independent core server installations at a
glance (for example, the device tree 2946 and alarms list 2957 ), so you can manage your monitoring
centrally, also when it is spread across different servers.
Getting Started
Every installation of PRTG Network Monitor includes the Enterprise Console and installs it
automatically on the computer running the PRTG core server. If you want to use the Enterprise
Console on another computer, please download 2928 and install it there. For details, please see
the Inst all t he Ent erprise Console 72 section.
Note: The Enterprise Console is mainly designed to review and manage an existing installation
of PRTG which you already set up. If you just start monitoring, we recommend that you first run
through the Smart Set up 37 in the PRTG web interface 108 and add your network devices
there.
For detailed instructions, please see Quick St art Guide
seamlessly switch to the Enterprise Console.
32
section. Once finished, you can
Requirements for Connections to PRTG Web Server(s)

To show monitoring data of your PRTG setup, the Enterprise Console must be able to establish
a connection to your PRTG web server(s). For this purpose, please ensure the following:
2938
27.04.2016
The following server settings in the Enterprise Console (see section PRTG Servers
details) have to match the following settings in the PRTG Administ rat ion Tool 3047 :
Ent erprise Console

Server Set t ings
PRTG Administ rat or Set t ings
Server IP / DNS name
IP address for PRTG's Web Server on the Web Server tab
Port
TCP Port for PRTG's Web Server on the Web Server tab
2970
for
Note: PRTG switches to port 8080 as a fallback after a restart

when port 80 is already used, and to port 8443 if port 443 is not
available. PRTG keeps the SSL connection in this case. If this port
is also not available, PRTG tries from port 32000 on until it finds an
available port. Because the EC cannot recognize these ports
(8080, 8443, 32000+) automatically, enter the currently used port
manually here in the Port setting. If you do not get a connection
to the PRTG web server, check the currently used port in the Web
Server settings under Sy st em Administ rat ionUser Int erface
2862 in the PRTG web interface.
Login Name
Login Name on the Administ rat or tab
Password
Password on the Administ rat or tab
No local software firewall blocks the connection.

No local virus protection program blocks the connection.
The specified port is not used by another application.
No (hardware) firewall blocks the connection when connecting through a network (LAN or
WAN).
The software versions of the Enterprise Console and the PRTG web server have to match at
least in the third number (for example, EC version 2944 15.3.18.3590 can connect to server
version 123 15.3.18.3796).
See section More
2939
for common issues with the Enterprise Console and their solutions.
More
Knowledge Base: Problems with the Enterprise Console: What can I do?
Knowledge Base: Enterprise Console connection failure error in content: What can I do?
Knowledge Base: Why is the Enterprise Console so slow?
27.04.2016
2939
The following sections introduce the features and concepts of the Enterprise Console:
Enterprise ConsoleTopics
First St art
2941
General Lay out
2942
Menu Tabs and Page Cont ent

PRTG Servers
Opt ions
2945
2970
2973
Windows Menu St ruct ure

Cont ext Menus
2979
2986
Short cut s Overview
2987
Related Topics
108

2940
218
2732
2990
27.04.2016
Part 8: Enterprise Console | 1 First Start
8.1
First Start
This section helps you to start the Enterprise Console for the first time.
Opening the Enterprise Console

Double click the PRTG Ent erprise Console icon in the Windows start menu to open it. As
soon as it opens, the Enterprise Console tries connecting to your PRTG installation, according
to the defined PRTG server connection settings. In a fresh install of PRTG, the settings for the
Enterprise Console installed on the computer running the PRTG core server are already
predefined, so you can use the Enterprise Console right away. If you get an error message
when opening the Enterprise Console, please check the connection settings 2938 . For example,
adjusting the settings is necessary if you changed the IP address of the server.
For detailed information, please see the PRTG Servers
2970
(PRTG Server Connect ion) section.
Note: The Enterprise Console runs under all supported Windows versions 23 , 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.
Tray Window
By default, the Enterprise Console runs in background and shows a message box whenever
there are new alerts, new messages, or new tickets for your monitoring. This window is one of
the first things you see after opening the Enterprise Console.
Example of the Tray Window
This window is shown as always on top. Click the OK button to close it. You can change the
tray behavior in the Enterprise Console settings. For detailed information, please see Opt ions
2975 settings (Sy st emAlert ing).
11.03.2016
2941
Part 8: Enterprise Console | 2 General Layout
8.2
General Layout
The main layout of the Enterprise Console (EC in short form) program consists of different
elements. See below for details.
PRTG Enterprise Console
From top to bottom, the main layout consists of:

The Windows menu
2942
The page header bar 2943 with the PRTG logo, the viewpoint arrow symbols, the refresh icon,
and the sensor states overview.
The menu tabs bar and page content
The server selection
The news feed
The status bar
2944
2944
2943
2943
and search bar
underneath.
2944
in the upper right corner.
underneath the page content.

at the bottom of the window.
Often, the Enterprise Console displays data and setting directly. Some functionalities and
extended setup additionally require a new window of the system's default browser and the
web interface 108 shows up. In this case, you are logged in to the web interface automatically
via username and hash value 2830 . In your browser, it might be necessary to confirm the
certificate that is used by the PRTG web server. For more information, please see SSL
Cert ificat e Warning 113 section. If you configure your Enterprise Console for a connection
with more than one PRTG core server, keep an eye on the server selection 2943 bar to choose
which server's data you want to access.
Windows Menu
The Windows menu gives access to general configuration and settings. For details, please see
section Windows Menu St ruct ure 2979 .
2942
05.11.2015
Page Header Bar

Enterprise Console Page Header Bar
The page header consists of the following parts:

PRTG Logo
Click the PRTG Network Monitor logo to open the Ajax web interface 108 in the browser
which you define in the Enterprise Console Opt ions 2973 . If you configured several PRTG core
servers, the browser loads the web interface of the server that you have currently selected
in the Devices 2946 tab.
Previous Viewpoint / Next Viewpoint (Arrow Sy mbols)
The Enterprise Console stores the different views which you navigate to in the application.
Using these arrows (or using the shortcuts Alt+Left and Alt+Right), you can step back and
forth in the history, just as you know from your web browser.
Refresh (Arrow Circle Sy mbol)
Click the refresh symbol (F5) any time to refresh the current screen. This immediately queries
data for the current screen from all active PRTG core servers just as the automatic refresh
does. You can configure the update interval in the Opt ions 2973 settings.
Global Sensor St at us Sy mbols
This area shows the aggregated status of all sensors from all active PRTG core servers,
divided into different sensor states. Depending on the particular sensor states, you see
colored boxes with numbers which symbolize the sensors. For example, you can see how
many sensors are in Up, Down, Warning, Pause, Unusual, or Unknown status. Click a status
icon to view a list of all sensors in the respective status. For a detailed description, please
see manual section Sensor St at es 135 . Next to the global sensor status symbols you can
also see the number of new alarms and new log entries, as well as the number of new
tickets, if there are any. Click the respective icons to view Alarms 161 , Logs 169 , or Ticket s
171 .
Note: When you view sensor lists, you can show the sensors of only one server at once. So,
the global sensor overview shows the total number of sensors in a certain status on all
active servers, but viewing a list of all sensors in a certain status from all servers is not
possible for performance reasons.
Menu Tabs Bar and Page Content

You can navigate through your setup using the menu tabs bar. Please take a few minutes to
familiarize yourself with all menu items. The page content underneath varies depending on the
selected menu tab. It shows various information about your monitored objects. For a detailed
description of all tabs, please see the Menu Tabs and Page Cont ent 2945 section.
Server Selection
Enterprise Console's Serv er Selec tion and Searc h Bar
05.11.2015
2943
In the server selection bar you see all active PRTG core server connections which are
configured for the current Windows user account (saved in the registry).
The server you select here determines globally which information the EC shows in all Menu
Tabs 2945 (except the Devices tab: the server selection does not apply for the devices tab).
Depending on your selection, Libraries, Sensors, Alarms, Maps, Report s, Logs, Ticket s, and
Set up options are shown for the respective server only. Select All PRTG Servers to show
consolidated information for all active PRTG core servers which appear in the list.
Note: For technical reasons, you cannot show consolidated information from all servers in the
Sensors, Set up, and Search Result s tab. To use these tabs, please select one single PRTG
core server from the server selection bar.
Select File | Manage PRTG Server Connect ions from the main menu
PRTG Servers 2970 from the list, or to edit an existing one.
2979
to add or remove
Search Bar
Select a single PRTG core server from the server selection 2943 bar and enter a key word to
search the respective server. In the Search Result s tab, the Enterprise Console displays
matching monitoring objects, help topics, and related objects. If you click a monitoring object
(for example, a sensor) in the search results, the Enterprise Console opens this object on the
Devices 2946 tab with details in the device tree.
Note: If you have configured a connection in the PRTG Servers 2970 options that uses a Root ID
2972 other than 0, the EC ignores this setting while searching. In this case, the EC shows Search
Result s for the entire server (starting at Root ID 0).
News Feed Bar

The news feed bar shows latest news by Paessler. Click the bar to open a window with an
overview about recent articles. You can open a specific article in the web browser by clicking
the particular header. If you do not want to show the news feed in your Enterprise Console,
click the X symbol besides the bar. You can enable it again via View 2983 | Show News Feed in
the main menu (Ctrl+N).
Status Bar
Enterprise Console Status Bar
The status bar shows the version number of your PRTG Enterprise Console and the Paessler
logo which leads you to the Paessler website when you click it. Furthermore, the status bar
contains a Cont act Support 2932 link which opens a window to leave feedback or to ask for
support, and a Follow & Share link which opens PRTG's social network contact information in
the Ajax web interface. You will also see a note if an update for one of connected servers is
available. Click Update Available to open the Aut o-Updat e 2918 page in the EC.
2944
05.11.2015
Part 8: Enterprise Console | 3 Menu Tabs and Page Content
8.3
Menu Tabs and Page Content
Under the different menu tabs of the Enterprise Console, you can navigate through various
pages with information about your monitored objects, such as your network status and
monitoring results, for example.
PRTG Enterprise Console Dev ic e Details
The following sections introduce the available options within the different tabs:
Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
05.11.2015
2969
2945

1 Devices
8.3.1
Devices
The Enterprise Console has a tab-like interface. Using the tabs you can navigate through
various pages with information about your monitored objects, such as your network status
and monitoring results, for example, as well as access maps, reports, tickets and settings.
Enterprise Console Menu Tabs Bar
There is documentation available for the following tabs:

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
Devices Menu Tab

The Devices tab is your starting point for everyday use. The page is split into two parts. On
the left hand side, it shows the tree-like device view which lists all configured PRTG core
servers with their probes, groups, devices, and the sensors on the devices, in a hierarchical
order. Next to each object you see an overview of the number of sensors, grouped by their
current status.
The first child node of the tree is called Favorit e Devices and Sensors. It contains all devices
and sensors that you marked as favorites. To add an object to the favorites list, right-click on
the desired device or sensor and select the Add t o Favorit es entry from the context menu
186 . For details, please see Priorit y and Favorit es 182 section.
Note: For more information about the hierarchical order of the different objects in the device
tree, please see Object Hierarchy 89 section.
On the right side you see details about the object selected on the left. The information is
spread over several tabs.
2946
15.04.2016

1 Devices
Over the object's name you see always a path which you can use to navigate through the
device tree. It can also help you to orient yourself if you get lost. If you click a breadcrumb
item, a drop-down menu opens that shows all available objects on the same level. For
example, you can use this to directly access all other sensors or a device, other devices within
a group, another group on the same probe, other probes in your root group, or another PRTG
server.
Enterprise Console Sensor Sub-Tabs on the Dev ic e Tab
Edit Objects in the Device Tree

Use the Edit menu (or the object's context menu 2986 ) to access different important functions
of the items you have currently selected in the device tree on the left hand side, such as
Add devices or sensors to the favorites list (or remove them from the list)
Sort all sub nodes of an object alphabetically
Move objects up and down in the tree
Check now
Pause monitoring
Access tools
and many more
For details about the available options, please see section Windows Menu St ruct ure
2979
Select Multiple Items in Device Tree

In the device tree shown on the left, you can select one or more objects, even from different
PRTG core servers. Hold down the Ctrl key to select more objects simultaneously with your
mouse. Usually, you select more than one item to view combined graphs, or to apply a
command from the Windows Menu 2979 (for example, Check Now or Pause) to several objects.
When you select multiple items, the sub-tabs on the right side show data for all selected items
at a glance. For example, when if you select two sensors, you see their tables next to each
other. Graphs will actually appear combined! This is a great way to instantly show one chart
containing the graphs of all selected objects. Each sensor channel is represented as one line.
This aggregated view works for all kind of objects.
Note: The tab Live Graph shows data for sensors only.
Note: Below each graph you see a key. Point to an entry in the key to display the
corresponding line in the graph above in bold.
15.04.2016
2947

1 Devices
Aggregated Graph View in Enterprise Console
Note: You may need to enlarge the Enterprise Console's window to see all tables and graphs.
DevicesOverview
The Overview tab shows general information about the selected object. Depending on the
selected object selected, you can see different information.
For servers, probes, and groups the table shows information in the Name and St at us
section, such as priority, parent objects and number of sensors on this object. Additionally,
the window shows a geographical map, if enabled in your PRTG configuration as well as in
the Enterprise Console's View 2983 menu, and index graphs 139 . For detailed information about
geographical maps, please see Geo Maps 2753 section.
For devices, the Overview tab shows device details and summary graphs for different time
spans, gauges, as well as a list of all sensors on this device, recommended sensors 155 , and a
geo map.
For sensors, the Overview tab shows sensor details, current status, and the last value of all
sensor channels, as well as sensor graphs for different time spans. You can also edit channel
settings in this tab by clicking on a channel's gear icon. For details, please see section
Sensor Channels Set t ings 2711 .
DevicesLive Graph, 2 days, 30 days, 365 days

These tabs are only available if you enable the Large Single Graph (Ctrl+L) view in the
Windows Menu 2983 (View). For Small Mult iple Graphs view please see DevicesGraph
section below.
2948
2949
15.04.2016

1 Devices
Select one of the tabs to display an object's monitoring results as Live Graph (content
available for sensors only), or for different time spans in more or less detail (2 day s, 30 day s,
365 day s). On every tab, you will see graphs as well as data tables.
While you view a sensor graph, you can hide single sensor channels individually. Remove the
check mark symbol in front of a channel name underneath the graph, and the line of the
according channel disappears. You can also Show all or Hide all channels by clicking these
buttons in the graph. The graph view is reset immediately.
Note: The days mentioned here are the default setting. You can change the detail of the
different graphs any time under Sy st em Administ rat ionUser Int erface 2866 .
DevicesGraph
This tab is only available if you enable the Small Mult iple Graphs (Ctrl+S) view in the Windows
Menu 2979 (View). For Large Single Graphs view please see above 2948 . This tab shows an
overview with single graphs and data tables for live data, 2 days, 30 days, and 365 days. It
might be necessary to enlarge the window to display all graphs.
Note: The days mentioned here are the default setting. You can change the detail of the
different graphs any time under Sy st em Administ rat ionUser Int erface 2866 .
DevicesHistoric Data
The Hist oric Dat a tab is available for sensors only (not for probes, groups, or devices). When
you call the historic data reports via this tab, there is no sensor selection available because
you already determined which sensor you want to create a report for. If you want to select
another sensor for the report, choose Sensors | View Hist oric Dat a from the main menu in
15.04.2016
2949

1 Devices
Historic Data Tab of Ping Sensor

Clic k here to enlarge: http://media.paessler.c om/prtg-sc reenshots/historic _data_tab_ping_sensor.png
Select the File Format for the results:

HTML web page: Opens a new browser window with the historic data report
X ML file: Opens a new browser window with the historic data report as XML file.
CSV file: Opens a new browser window with the historic data report as CSV file.
When you click one of these items, a new window or tab of the external browser configured in
the Enterprise Console's Opt ions 2977 will open. PRTG automatically logs in and redirects you to
the respective web page. If your browser displays a certificate warning, please find more
information in the SSL Cert ificat e Warning 113 section.
View and functionality are the same as in the web interface. For details about the available
Hist oric Dat a report options, please see the Hist oric Dat a Report s 146 section of the Ajax
Web Interface 108 documentation.
DevicesLog
Click the Log tab to show a table list with all log information on this object. This is a subset of
the entries available via the Logs 2963 menu tab.
2950
15.04.2016

1 Devices
The list can show up to one hundred entries at a time. Use the arrow symbols above the list to
show other items. You can jump to the beginning of the list, or browse through it hundred by
hundred. If the list has more than one entry, you can also sort the items by the contents of a
certain column. To sort, simply click the header of the column you want to sort by once or
twice.
DevicesSettings
The Set t ings tab loads and displays the currently selected object's settings from the web
interface. View and functionality are the same as in the web interface. For every type of object
and for every sensor, different options are available. For detailed information, please see the
following sections (depending on the selected object) in the Ajax Web Interface 108
documentation:
Probe Set t ings
278
Group Set t ings
299
Device Set t ings
324
Sensor Set t ings
347
DevicesSettingsMulti-Edit
If you select several objects on the left side, the Set t ings tab switches into multi-edit mode 2742
. Using multi-edit, you can set a check mark for one or more settings. All changes apply to all
selected objects. The multi-edit dialog displays settings which are common among the
selected objects only.
If you select only sensors on the left side in the device tree, the Set t ings tab additionally
displays a Channel Set t ings tab. Using this tab you can multi-edit the settings of any channels
2711 which are common among the selected sensors, as long as the channels have the same
name. Set a check mark for one or more channel settings. All changes apply to all selected
sensors.
Note: You cannot use multi-edit for objects on different PRTG core servers.
DevicesNotifications
The Not ificat ions tab loads and displays the currently selected object's settings from the web
interface. View and functionality are the same as in the web interface. You can set different
notification triggers.
For detailed information, please see the Sensor Not ificat ions Set t ings
Web Interface 108 documentation.
2719
section in the Ajax
Note: You cannot change notification settings for multiple objects at a time. We recommend
that you use the Inherit ance of Set t ings 94 for easy configuration.
15.04.2016
2951

1 Devices
DevicesComments
The Comment s tab loads and displays the currently selected object's settings from the web
interface. View and functionality are the same as in the web interface.
DevicesHistory
The Hist ory tab shows all changes to the settings of an object with a timestamp, the PRTG
user which conducted the change, and a message.
Drag & Drop Sorting in Device Tree

In the device tree, you can also move probes, groups, and devices simply via drag and drop.
Activate it in the Windows menu 2979 Edit | Drag & Drop Sort ing and then drag your objects as
you like: You can move devices and groups, or add groups or devices to other groups. You
can also move objects via the context menu 2986 .
Note: You cannot move objects in the following cases:
You cannot move any objects from one PRTG core server to another.
You cannot move sensors from one device to another. To clone sensors to other devices
using drag & drop, please use the Ajax Web Interface 108 . For detailed information, please see
the Manage Device Tree 258 section.
You cannot move devices from one group to another.
You cannot move groups from one probe to another.
You cannot move probes from one core server to another.
2952
15.04.2016

2 Libraries
8.3.2
Libraries

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
Using Libraries is a great way to keep an eye on your network status because you can
individually select which sensors you would like to see there. For a general introduction to
PRTG Libraries, please see Libraries 2770 section.
Libraries Menu Tab

The page is split into two parts. On the left hand side you see all available libraries from one or
several servers, on the right hand side the actual libraries.
Click a library's name to display it. In the tabs above the library, select from Overview 2770 ,
Management 2777 , Set t ings 2779 , Not ificat ions 2759 , Comment s 2783 , and Hist ory 2784 . Each of
these tabs loads the respective functionality of the Ajax Web Interface 108 . Click the Save
button to apply changes to your settings. For more details, please see the Libraries 2770
section.
Underneath the tabs bar, there are different options available to change the current library
view: You can set sensor filters (set or remove check marks to include or exclude sensors in
a certain status) and change the device tree view. For details about the tree view, please
see General Lay out Tree View Lay out 123 section.
Click a library node to edit the node settings
2779
in a new window.
Double-click a library's name on the left to open the library in the configured external web
browser. You can edit it or add new libraries to this PRTG server. For more details, please
see the Libraries 2770 section.
05.11.2015
2953

2 Libraries
Right-click a library's name to open its context menu 2986 . The following options are available:
Add, Edit , Delet e, Clone, Send link by email, and Open in Web Browser in the libraries
overview on the left, Det ails..., Edit , Remove from Library ..., Add Library Node..., Add
Group..., and Send Link by Email on the Overview tab of a specific library on the right. For
more details, please see the Libraries 2770 section.
Use the button Add Library to create a new library and the button for object history
view all changes to libraries.
210
to
Libraries Menu TabAdd Library

Click the Add Library button to add a new library to a PRTG server.
Depending on the current setting shown in the server selection 2943 bar in the upper right
corner, an (embedded) window will open (if one specific server is selected), or you will see a
selection window that asks you to choose the core server you want to add the new item to.
Choose an installation to start.
For details about adding a library, please see Libraries St ep By St ep
2954
2773
05.11.2015

3 Sensors
8.3.3
Sensors

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
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 want to see. You can filter by various parameters like
object or sensor type, for example, and current sensor status.
Sensors Menu Tab

Note: For technical reasons, this function is available for one server at a time only. If you have
configured more than one PRTG core server, please choose one server from the server list in
the upper right corner.
Click the Sensors entry in the menu tabs bar to show a table list of all sensors. You can enable
a filter to only show certain sensors. To do so, choose from three different drop down menus
to build a filter. With each filter you can further decrease the number of shown sensors.
By Ty pe
The second drop down menu shows all sensor types 348 available in your monitoring setup.
Select an entry to only show sensors of this type. The default value is All Ty pes.
05.11.2015
2955

3 Sensors
By St at us
The third drop down menu shows all possible sensor states 135 . Select an entry to only
show sensors that currently show this status. Choose between All St at es, Down, Down
(Acknowledged), Down (Part ial), Warning, Up, Paused, Unusual, and Unknown. The default
value is All St at es.
Note: If you click a sensor symbol in the page header bar 2943 , you can directly view a sensor
list filtered by the selected sensor status for the selected server.
If you have filtered out all sensors and the list below shows no entries, remove some filters by
reverting them to the default values.
Note: In the column Last Value, the table shows only the last value of the sensor's primary
channel.
twice.
From this list view, you can select multiple items to apply the same action to them, for
example, Edit | Check Now.
You can select multiple items by the following means (you can also combine them):
Click and hold your left mouse key while pointing to the lines you want to select
Hold the Ctrl key while clicking to toggle the selection status of a single line
Click a line and hold the Shift key while clicking another line to select all lines in between.
2956
05.11.2015

4 Alarms
8.3.4
Alarms

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
Alarms Menu Tab

In the Alarms tab you can show the alarms of all active PRTG core servers. To do so, select All
PRTG Servers from the server selection in the upper right corner.
The alarms list shows all sensors that are currently in a Down, Down (Part ial), Down
(Acknowledged), Warning, or Unusual status. Sensors in other states (for example, Up,
Paused, or Unknown) do not appear here. This is useful to keep track of all irregularities in
your network.
Using the options Error, Warning, and Unusual, you can hide and show sensors in the
respective status by removing and adding a check mark. When choosing Error, this includes
sensors in the states Down, Down (Part ial), and Down (Acknowledged).
Click Show as Gauges to show the sensors on the Alarms tab represented with gauges
137
If the list has more than one entry, you can also sort the items by the contents of a certain
column. To sort, simply click once or twice on the header of the column you want to sort by.
From this list view, you can select multiple items to apply the same action to them, for
example, Edit | Check Now.
You can select multiple items by the following means (you can also combine them):
05.11.2015
2957

4 Alarms
Click and hold your left mouse key while pointing to the lines you want to select
Hold the Ctrl key while clicking to toggle the selection status of a single line
Click a line and hold the Shift key while clicking another line to select all lines in between.
Acknowledge Alarm
An acknowledged alarm shows up in the alarms list as "acknowledged" (see Sensor St at es
and will not trigger 2719 any more notifications 2759 .
135
Note: If the alarm condition clears, the sensor usually returns into an Up status immediately
with the next sensor scan.
To acknowledge an alarm, right-click 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:
ACKNOWLEDGE ALAR M U NTIL

Selected Objects
Shows the sensor(s) for which you want to acknowledge the

alarm. You can acknowledge alarms for more than one sensor
using multi-edit 2742 .
Message
Enter a text, for example, the reason why you acknowledge the
alarm. Please enter a string or leave the field empty.
Until
Enter the date when the acknowledge status will end. Use the date
time picker to enter the date and time.
Note: If the alarm condition still persists after the specified date,
the sensor will show a Down status again.
Only users 2890 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 2890 , section
Account Cont rol.
2958
05.11.2015

5 Maps
8.3.5
M aps

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
Maps Menu Tab

The page is split into two parts. On the left hand side you see all available maps from one or
several servers, on the right hand side the details of the selected map.
Click a map's name to display it. In the tabs above the map, select from View Map, Map
Designer 2816 , Set t ings 2823 , Get HTML 2826 , Comment s 2826 , and Hist ory 2826 . Each of these tabs
loads the respective functionality of the Ajax Web Interface 108 . Remember to click the Save
button to apply your settings. For more details, please see the Maps 2810 section.
Double-click a map's name to open the map in the configured external web browser. You can
edit it using the Map Designer 2816 , or add new maps to this PRTG server. For more details,
please see the Maps 2810 section.
Right-click a map's name to open a context menu 2986 . The following options are available:
Add, Edit , Delet e, Clone, Send link by email, and Open in Web Browser.
Use the button Add Map to create a new map and the button for object history
all changes to maps.
210
to view
Maps Menu TabAdd Map

Click the Add Map button to add a new map to a PRTG server.
05.11.2015
2959

5 Maps
For details about adding a map, please see section Maps St ep By St ep
2960
2814
05.11.2015

6 Reports
8.3.6
Reports

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
Reports Menu Tab

On the Report s tab you see all available reports from one or several servers in one list.
If the list has more than one entry, you can also sort the items by the contents of a certain
column. To sort, simply click once or twice on the header of the column you want to sort by.
Choose one report and double click its name to open its details. The page will split into two
parts. On the left hand side you see all available reports from one or several servers, on the
right hand side the options for the currently selected report.
Click a report's name in the list on the left to display its options. In the tabs above the
report, select from Run Now 2794 , St ored Report s 2797 , Set t ings 2798 , Select Sensors
Manually 2807 , Sensors Select ed by Tag 2809 , and Comment s 2809 . Each of these tabs loads the
respective functionality of the Ajax web interface 108 . Remember to click the Save button to
apply your settings. For details, please see the Report s 2786 section.
Right-click a report's name to open its context menu 2986 . The following options are available:
Add, Run Now, Edit , Delet e, Clone, Send link by email, and Open in Web Browser.
Use the button Add Report to create a new report and the button for object history
view all changes to reports.
05.11.2015
210
to
2961

6 Reports
Reports Menu TabAdd Report

Click the Add Report button to add a new report to a PRTG server.
For details about adding a report, please see Report s St ep By St ep
2962
2790
05.11.2015

7 Logs
8.3.7
Logs

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
The Logs list shows all past activities and events of your PRTG monitoring setup. This is useful
to keep track of all important activities and, for example, to check whether messages were
sent. In a typical setup, a huge amount of data is produced here. As the activity of every single
object is minuted, you can use this data to check exactly if your setup works as expected.
There are two options to call the logs list: Either you click the Log tab while you view an
object's details on the Devices 2950 menu tab, or you choose the Logs entry from the menu
tabs bar.
Logs Menu Tab

Click the Logs entry in the menu tabs bar to show a list of all log entries of a PRTG core
server.
You can either view the entries of one or all servers. If you have configured more than one
PRTG core server and you want to view entries from all servers in your PRTG Servers 2970 setup,
simply select All PRTG Servers from the server selection in the upper right corner.
11.11.2015
2963

7 Logs
You can enable a filter to only show log entries of a certain event from the categories St at us
Changes, Sy st em Event s, and Object Hist ory . Choose a category from the Show menu. The
second drop down menu shows all possible event types for the selected category. Select an
entry to only show events of the respective event type. Choose a sensor status 135 for status
changes, Probe Relat ed, Aut o Discovery , Not ificat ions, or St at us Messages for system
events, or a system object for object history 169 . You can also define the time span for which
you want to show logs.Use the date time picker to enter the date and time.
twice.
2964
11.11.2015

8 Tickets
8.3.8
Tickets

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
Tickets Menu Tab

On the Ticket s tab you can view all tickets on the currently selected PRTG core server.
Note: You can only display tickets from one server at the same time, not from all PRTG servers.
In the header bar of the tickets list, you can choose several filters to find and display certain
tickets: by status, type, concerned user or user group, related monitoring objects, and last
edit. Click the X symbol to undo the date selection.
Double-click an entry in the tickets list to open a ticket in a new window and to conduct ticket
related actions (edit, assign, resolve, close, or reopen). You can also multi-edit tickets via the
context menu: mark several tickets by holding Ctrl or Shift and clicking on the corresponding
tickets. Right-click a ticket to open the context menu. The following actions are available:
Open Ticket , Edit Ticket , Assign Ticket , Resolve Ticket , Reopen Ticket , Close Ticket ,
Priorit y /Favorit e, Open in Web Browser.
11.11.2015
2965

8 Tickets
twice.
Tickets Menu TabOpen Ticket

To open a new ticket, click Open Ticket in the upper right corner or in the context menu.
Select a related object, click Cont inue, and provide Subject , Assigned t o, Priorit y , and
Comment s. Once finished, click Save to create the ticket.
Open Tic ket Dialog in PRTG Enterprise Console
For details about working with the PRTG ticket system, please see section Ticket s
PRTG web interface.
2966
171
for the
11.11.2015

9 Setup
8.3.9
Setup

Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
Setup Menu Tab

In the Set up tab you can access all options available in the Set up 2828 menu of the Ajax web
interface. You can collapse and expand the sections by clicking the or + symbol.
For more information, please refer to the respective section in the documentation for the PRTG
web interface.
Account Set t ings:
My Account
2830
Not ificat ions
2836
Not ificat ion Cont act s

Schedules
2852
2856
Sy st em Administ rat ion:

User Int erface
11.11.2015
2860
2967

9 Setup
Monit oring
2871
Not ificat ion Delivery

Core & Probes
2883
Administ rat ive Tools

Clust er
2905
2877
2900
(available in a cluster
87
setup only)
User Account s:
You see a list of configured user accounts. Select one to change settings. For details, please
see User Account s 2890 section.
User Groups:
You see a list of configured user groups. Select one to change settings. For details, please
see User Groups 2896 section.
PRTG St at us:
Sy st em St at us
Clust er St at us
2907
2923
(available in a cluster
Licensing St at us and Set t ings

Aut o Updat e
87
setup only)
2925
2918
Opt ional Downloads and Add-Ons:

Client App for Windows (Ent erprise Console)
Remot e Probe Inst aller
2928
2928
2928
Support :
Cont act Support
2968
2932
11.11.2015

10 Search Results
8.3.10 Search Results


Devices
2946
Libraries
Sensors
Alarms
Maps
2955
2957
2959
Report s
Logs
2953
2961
2963
Ticket s
Set up
2965
2967
Search Result s
2969
Search Results Menu Tab

The Search Result s tab is only visible if you do a search using the search box in the upper
right corner. For your search, the Enterprise Console shows all matching objects on one PRTG
core server. Click a monitoring object in the results to show it in the Enterprise Console's
Devices 2946 tab.
Other objects, for example, manual sections, load in an external browser window.
11.11.2015
2969
Part 8: Enterprise Console | 4 PRTG Servers
8.4
PRTG Servers
The Enterprise Console connects to the web server API running on every PRTG core server
installation. It supports saving the configuration for a connection to one or more PRTG core
servers. In a full PRTG installation, there is already a connection predefined.
Note: For a successful connection, the program versions of Enterprise Console and PRTG core
server have to match. When connecting to several servers, make sure they all run on the same
software version. At least the third number of the whole version number has to be equal. For
example, EC version 15.4.21.4476 can connect to server version 15.4.21.4768.
PRTG Servers List

From the main menu, select File | Manage PRTG Server Connect ions to view a list of all
servers configured for the currently logged in Windows user account. You can also access this
list by clicking the PRTG Server Connect ions entry above the device tree.
PRTG Serv ers List in the Enterprise Console
The list shows the server or display name, as well as login information used. In the St at us
column you see an overall sensor status for this server connection. You can also see if there
is any Background Act ivit y on the respective server (for example, a running Aut o-Discovery
219 ), which can potentially affect performance and response times.
In the list, set a check mark for every PRTG server you want to poll with every update interval.
If a server is not reachable, the Enterprise Console deactivates it automatically after several
unsuccessful connection attempts. When opening the Enterprise Console, it automatically reestablishes the connection to all active servers.
Add or Edit a PRTG Server Connection

In the header bar above the server list, click Add PRTG Server Connect ion to add a new
server connection configuration. Use Delet e PRTG Server Connect ion to remove an entry
from the list. With Move Up and Move Down you can change the order of the servers on the
Devices 2946 tab. There is also a context menu 2986 available for each server connection with the
options to Deact ivat e PRTG Server Connect ion, to Add a server, to open and edit the
Set t ings of the server, to Delet e the server, to open the server in the Ajax web interface
(Open in Web Browser), as well as Move Up and Move Down to change its position on the
Devices 2946 tab.
2970
11.11.2015
To change the settings of an existing server in the list, open its context menu with right-click
and click Set t ings or click the respective wrench symbol in the table. You can alternatively use
the context menu of a server on the Devices 2946 tab: There you can choose between Edit
PRTG Server Connect ion (opens the edit dialog), Deact ivat e PRTG Server Connect ion (the
Enterprise Console will not show this server's monitoring data anymore; you can activate it
again later in the servers list 2970 ), or view Dependencies 98 .
When adding or editing, a dialog box appears to enter connection information.
Note: Connection settings are stored for each Windows user individually in the registry under
the following node: HKEY_CURRENT_USER\Software\Paessler\PRTG Network Monitor\WinGUI
PRTG Serv er Connec tion Settings in Enterprise Console
Server IP/DNS name

Enter the IP address or DNS name of the PRTG server the Enterprise Console connects to.
This is the same address or name as defined in the web server settings for the core server.
For detailed information please see PRTG Administ rat ion Tool 3048 (Web Server) section.
Make sure the values match.
Make sure the server is reachable (especially when using Network Address Translation (NAT))
and no firewall settings block the connection.
Port
Enter the port on which the PRTG server runs.
This is the same port as defined in the web server settings for the core server. For detailed
information please see PRTG Administ rat ion Tool 3048 (Web Server) section. Make sure the
values match.
Make sure the server is reachable (especially when using Network Address Translation (NAT))
and no firewall settings block the connection.
11.11.2015
2971
Login Name
Enter the login name that you use to login to the web server.
This can be the administrator login or the login of another PRTG user.
In a new installation, the login name is prt gadmin by default.
For detailed information about user accounts, please see Sy st em Administ rat ionUser
Account s 2890 section.
Password
Enter the password for the login name entered above.
In a new installation, the password is prt gadmin by default.
Root ID
Enter the ID of the object that is the root of the device tree
90 .
Default value is 0, which is the Root group of your configuration.

If you enter an other object's ID here, the device tree will start at this object, only showing
all other objects below in the hierarchy.
This is useful to only view a part of the device tree, which might load much faster.
You can create several connections that only differ in the Root ID value to quickly switch
between different views within your configuration, choosing different PRTG core server
connections in the Enterprise Console's Devices 2946 tab.
Display Name (opt ional)
Optionally enter a name that the EC displays in the PRTG Server Connect ions list.
If you leave this field blank, the Enterprise Console displays the Server IP/DNS name setting
there.
Click the OK button to save your settings or Cancel to discard them.
2972
11.11.2015
Part 8: Enterprise Console | 5 Options
8.5
Options
From the Windows menu

options dialog.
2979
of the Enterprise Console, select File | Opt ions... to open the
You can choose from these options on the left hand side:
System
2973
SystemAlerting
Device Tools
2975
2975
Select External Browser

Proxy Settings
2977
2978
Contact Support
2932
System
From the Windows menu 2979 of the Enterprise Console, select File | Opt ions... to open the
settings dialog. Please select a setting on the left and change the respective values on the
right side. Click the OK button to save your settings.
Change general system settings for the Enterprise Console.
Enterprise Console Options
12.11.2015
2973
ENTER PR ISE CONSOLE OPTIONS: SYSTEM

Show in Tray
By default this setting is enabled. With this setting enabled, a PRTG

icon appears in the Windows tray 2941 . When you point your mouse
to it, it will show information with the most important status
information about your monitoring. With a right-click you can
access a menu with access to the most important functions.
To use any alerting functionalities (see Sy st emAlert ing 2975
section), you must enable this option. If the tray icon is not shown,
no alerting from the Enterprise Console is available.
Start with Windows
This setting is only available to change only if you enable the tray
option above. By default this setting is enabled. With this setting
enabled, the Enterprise Console will start up automatically when
Windows starts.
Clear "Tray Blink

Notification"
automatically
This setting is only available to change only if you enable the tray
option above. Whenever there are new entries in the Alarms 2957
list, the tray icon will start blinking. If you enable this option, the
tray icon will stop blinking automatically as soon as there are no
more alarms.
With this option disabled, the icon will keep blinking, even if all
alarms are cleared meanwhile.
Restore last viewpoint

after application start
If this option is enabled, the Enterprise Console saves information

about the currently shown view (for example, sensor details, a
certain graph, or a map 2810 ). It is written to the registry 2978 when
you close or exit the program. When you open the Enterprise
Console again, it will try to restore the same view.
Only if the object is not available any more (due to changes on the
server, or due to unavailability of a server), the default view loads.
Update Interval (Sec.)
Define the number of seconds that the Enterprise Console waits

before the screen refreshes. Please enter an integer value. Default
value is 60 seconds. You can use the up and down arrows to go
one second up or down.
Language
Choose the language for the Enterprise Console from the drop
down menu. Default is English. Depending on your installation,
you can choose other languages here.
This setting influences the language of the Enterprise Console
only.
2974
12.11.2015
SystemAlerting
You can define what the Enterprise Console will do in case of new Alarms, Log Ent ries, or
Ticket s. The settings are the same for all of these three cases, but you can individually define
them for each case. On the left side, select either Alert ing for new Alarms, Alert ing for new
Log Ent ries, or Alert ing for new Ticket s and define the settings as follows.
Note: All alerting options only take effect if you enable the Show in Tray option in the system
2973 settings above. If the tray icon is disabled, there will be no alerting from the Enterprise
Console.
ENTER PR ISE CONSOLE OPTIONS: ALER TING FOR NEW ALAR MS

Blink Tray Icon
The tray icon will blink if there are new items to be alerted for. You
can additionally set the Clear Tray Blink Not ificat ion
aut omat ically option in the system 2973 settings above.
Balloon Info in Tray
Show a balloon info next to the PRTG tray icon if there are new
items to be alerted for.
Popup Message
Show a popup message window if there are new items to be

alerted for.
Note: The popup window will be always on top until it is closed.
Play Sound
Play an audible notification if there are new items to be alerted for.

There is a default sound defined. To change it, please click the
folder icon and select any standard WAV file from your hard disk
drive. PRTG already comes with a small set of sounds you can
choose from.
Note: The sound file is played only on the computer running the
Enterprise Console.
Open Enterprise
Console
Open the Enterprise Console if there are new items to be alerted

for.
Device Tools
12.11.2015
2975
In the Device Tools settings you can define commands that will be available in the Windows
Menu 2979 and context menu 2986 of groups, devices, and sensors. A command to initiate a
remote desktop connection is already predefined.
Note: You may need to run the Enterprise Console as administrator to make the tool function
work with your Windows version.
Click the Add button to add a new command, or choose an existing one from the list and click
the Edit button to change the settings. Use the Delet e button to remove an entry from the
list.
ENTER PR ISE CONSOLE OPTIONS: EDIT TOOL

Name
Enter a custom name for your command. The command will show
up with this name in context menus. Please enter a string.
Command
Enter the command you want to execute on the local machine.

This can be, for example the name of a program or script, with or
without path, according to your system's configuration.
Parameters
Enter the parameters with which you want to execute the

command.
You can use the placeholders (variables) shown in the window,
section Available placeholders 2976 . Other placeholders are not
possible. During runtime, these placeholders are replaced by the
respective values set for the monitoring object you select to
execute this device tool.
For example, the %id placeholder will be replaced by the ID of a
group, a device, or a sensor, depending on which object you
execute the command for.
Shortcut
Select a key shortcut for the command. Choose an F-Key from the
list or select None to not use a key.
Paramet ersAvailable placeholders

The following placeholders (variables) are available in the Enterprise Console.
2976
12.11.2015
Available
For
Groups
Available
For
Devices
Available
For
Sensors
The object's ID as shown in the

page header on the object's
details page
The object's Name
The sensor's or device's IP

Address/DNS Name
%message
The sensor's Last Message
%value
The sensor's Last Result value
%type
The sensor's Ty pe
Placeholder
%id
%name
%host
Will Be Resolved To
If you use a placeholder in combination with an object it is not available for, it will simply not be
resolved but the placeholder itself will be returned.
Note: To see the output of all placeholders for different objects you can create a simple test
tool that displays the output in a command line window. Just create a tool with the command
cmd and the following content in the Paramet ers field:
/K echo.id: %id && echo.name: %name
&& echo.host: %host && echo.message: %message
&& echo.value: %value && echo.type: %type
Right-click an object in the device tree and run the tool from the Tools option in the menu
(either Windows 2979 or context menu 2986 ).
Select External Browser

With these settings you can define which browser the Enterprise Console will use when you
select a command that requires to open an external browser window, for example when you
select View | Open in Web Browser from the Windows menu of the EC. You can only select
browsers installed on the system running the Enterprise Console, other browser options are
disabled.
By default, the system's default browser is opened. To change the Enterprise Console's
behavior, choose between:
12.11.2015
2977
Use sy st em default browser (browser.exe)

Use IE (Version: x)
Note: Only Microsoft Internet Explorer 11 is supported by the Ajax web interface! Please do
not use it with Internet Explorer 10 or earlier! We recommend that you use Google Chrome
49 or later (recommended) or Mozilla Firefox 45 or later as external browser.
Use Firefox (Version: x)
Use Chrome (Version: x)
Use Safari (Version: x)
Proxy Settings
If the connection to the PRTG core servers requires a proxy connection, you can set it here.
ENTER PR ISE CONSOLE OPTIONS: PR OXY SETTINGS

No Proxy
Use a direct connection to the servers.
Use System Settings
Use your Windows default settings, configured in Internet Explorer.

To view these settings, open the Internet Explorer on your system
and select Tools | Int ernet Opt ions from the menu. Select the
Connect ions tab and click the LAN set t ings button.
Manual Proxy
Configuration
Manually enter a proxy configuration. Enter the IP address/DNS

name of the proxy, a port number, as well as username and
password (if required by the proxy).
Note: Only basic authentication is available!
Settings Storage
For each individual Windows user account, the settings of the Enterprise Console are stored in
the Windows registry. For details, please see Dat a St orage 3135 .
2978
12.11.2015
Part 8: Enterprise Console | 6 Windows Menu Structure
8.6
Windows Menu Structure
The Windows menu of the Enterprise Console has four main menu items:
File
2979
Edit
2979
View
Help
2983
2984
File
The File menu offers system related options for the Enterprise Console. The particular close
and exit options depend on the enabling status of the tray option.
FILE
Manage PRTG Server
Connections
Show a list of all configured PRTG core server connections. For

detailed instructions, please see PRTG Servers 2970 section.
Options...
Open the Opt ions 2973 dialog to set EC system options and to
configure one or more PRTG core server connections.
Close or Exit
This menu item appears as either Close or Exit , depending on

whether the tray icon is enabled or disabled in the Opt ions 2973
settings.
Use Close to close the Enterprise Console window. Alerting is still
available via the tray icon then. You can also double-click the tray
icon to re-open the Enterprise Console.
Exit shuts down the Enterprise Console completely. This option is
only available if the tray icon is not running.
Shortcut: Alt+X
Close and Exit
This menu item is only available if the Show in Tray option is

enabled in the Opt ions 2973 settings. It will completely shut down
the Enterprise Console and tray icon, so no tray alerts are shown
any more.
Shortcut: Ctrl+Alt+X
Edit
The content of the Edit menu varies, depending on which menu tab 2945 you are and whether
and which objects are selected within the Devices 2946 , Sensors 2955 , or Alarms 2957 tab.
21.01.2016
2979
Note: Some of the options open the Ajax web interface when you select them.
EDIT
Check Now
Perform an immediate scan for all selected objects (use the Ctrl key
to select multiple objects). This option polls all selected devices
and queries new data for all sensors on them. If you choose this
option for a probe or a group, you query data for all sensors in
the object hierarchy 89 underneath.
Shortcut: Ctrl+K
Details
Open the overview tab for the selected object (probe, group,
device, or sensor).
Edit
Access the pages for editing Set t ings... 159 , Not ificat ions 159 ,
Access Right s... 101 , and Management 159 (not for sensors) of the
selected object. In addition, you can Rename... this object. Point
on it to see available options.
Dependencies
This option is only available if you select a server (the Root group),
a probe, or group. This function shows an overview of the
dependencies 98 configured for the selected object. If you select a
dependencies option, the Enterprise Console opens the respective
dependencies overview in a new window. For details, please see
section Show Dependencies 2751 .
Add Group...
This option is only available if you select a probe or group (not the
Root group). This option opens an assistant in a new window
which guides you through adding a new group to the selected
probe or group. For detailed instructions, please see Add a Group
237 .
Add Auto-Discovery
Group...
which guides you through adding such a group. For detailed
instruction, please see section Aut o-Discovery 219 .
Add Device...
which guides you through adding a new device to the selected
probe or group. For detailed instructions, please see Add a
Device 244 .
2980
21.01.2016
EDIT
Add Sensor...
This option is only available if you select a device. This option

opens an assistant in a new window which guides you through
adding a new sensor to the selected device. For detailed
instructions, please see Add a Sensor 256 .
Auto-Discovery
This option is only available if you select a device. Point on it to

see available options. You can choose between:
Run Aut o-Discovery : This option starts an automatic search and
adds new sensors to the selected device. The search is running
in background. You will see new sensors after a few minutes
automatically. For more information, please see Aut o-Discovery
220 (Run Aut o-Discovery Now).
Run Aut o-Discovery wit h Templat e: With this option you can
run an auto-discovery with a pre-defined device template.
Create Device
Template...
This option is only available if you select a device. This option

opens an assistant in a new window which guides you through
creating a device template. This template is then available for autodiscovery 219 . For detailed instructions, please see Creat e Device
Templat e 2747 .
Sort Alphabetically
This option is only available if you select a probe, a single group, or

a device. This will sort direct children of the selected node such as
groups, devices, or sensors in alphabetical order.
Caution: The ordering is stored in the monitoring configuration so
you cannot revoke it!
Acknowledge Alarm...
This option is only available if you select a sensor in a Down or

Down (Part ial) status 135 . Point on it to see available options. For
details on how to acknowledge an alarm, please see Alarms 2958
section.
Delete
Delete the selected object(s). You will be asked for confirmation

before anything is actually deleted.
Clone...
This option is only available if you select a single group, device, or

sensor. This options opens an assistant in a new window which
guides you through cloning the selected object. For detailed
instructions, please see Clone Object 2740 .
Move
Move the selected object(s) of the device tree (use the Ctrl or Shift
key to select multiple objects). Point on it to see available options.
Choose between Top, Up, Down, and Bot t om to move the object
(s) to the top or bottom of the mother node, or one entry up or
down.
21.01.2016
2981
EDIT
You can also move the selected group or device to another group
with To Ot her Group... This option opens an assistant in a new
window to guide you through the movement. Please see section
Devices 2952 for details about allowed movements.
Pause
Pause and resume monitoring for the selected objects from the
device tree (use the Ctrl key to select multiple objects). Point on it
to see available options.
Choose between: Pause Indefinit ely , Resume from pause, pause
For 5 Minut es, For 15 Minut es, For 1 Hour, For 3 Hours, For 1
Day , Pause Unt il... The option Pause Unt il... opens an assistant in
a new window where you can enter a message and a date. Use the
date time picker to enter the date and time. PRTG will resume
monitoring after this date.
You can also set up a One-t ime maint enance window: Enter a
message and start and end date of the maintenance in the
appearing window. Use the date time picker to enter the date and
time.
Simulate Error Status
This option is only available if you select a sensor. Set the selected
sensor to a simulated error status. As for the pause status,
Resume will appear in the context menu if a the selected sensor is
already in a simulated error state.
Note: "Simulate error status" does not work for sensors that run
on a PRTG Mini Probe.
Priority/Favorite
Set the priority for the selected object. You can also add devices
and sensors to favorites. For details, please see section Priorit y
and Favorit es 182 .
Historic Data
Open the historic data tab of the selected object. Point on it to

see available options.
You can choose between Last 2 day s..., Last 30 day s..., and Last
365 day s...., or when selected one sensor Live Dat a... and View
Hist oric Dat a.... You can also create a report. For detailed
instructions, please see Hist oric Dat a Report s 147 (Menu).
When you select one or more sensors (hold the Ctrl or Shift key to
select multiple items), you can open the Compare Sensors 143
dialog. The graphs of all chosen sensors appear in the comparison
dialog automatically. You can add additional sensors in the
comparison dialog.
For sensors, you can open the Similar Sensors Overview
2982
151
21.01.2016
EDIT
Device Tools
Call a tool command. All placeholders (variables) configured in a

tool command will be resolved for the currently selected object.
Point on it to see all available tools configured in your Opt ions 2975
settings (Device Tools). By default, a Remot e Deskt op tool is preconfigured which tries to initiate a remote desktop connection to
the IP address or DNS name of the selected object (this will usually
work for devices, of course). You can also add a device tool
directly to the selected object: Add Device Tool... will open
Opt ionsDevice Tools 2975 .
For devices, additional options are available. They allow you to
connect to the Service URL value defined in the device's settings
2951 , or open the IP address/DNS name of the device via the
protocols HTTP, HTTPS, and FTP. For each of these functions, your
system's default programs will be used. Usually, this is your
browser. You can also install a remote probe on a device via
Remot e Probe Quick Set up 3112 .
Note: You may need to run the Enterprise Console as administrator
to make the tool function work with your Windows version.
Find Duplicates
This option is only available if you select a device. Search in your

PRTG configuration for devices with the same IP address or DNS
name as the selected device. A new window with the results will
appear, either showing existing duplicates or a message indicating
that there are no duplicates.
Drag & Drop Sorting
Enable this option to sort all objects in the device tree via drag and
drop. By default, this option is disabled to avoid accidental moves
of objects. For details, please see section Devices 2952 .
Send Link by Email
Send the link to the selected object by email. This option opens a
new email using your system's standard email client. It contains a
direct link to the details page of the selected object.
Open Ticket
Open a ticket that refers to the currently selected object. For

details, please see section Ticket s 2965 .
View
The View menu provides settings related to what the Enterprise Console shows.
21.01.2016
2983
VIEW
Refresh
Query data for the current screen from the PRTG core server
immediately, just as the automatic refresh does. You can configure
the auto-refresh in the Opt ions 2973 settings.
Shortcut: F5
Large Single Graph
Change the view in Devices 2946 menu tabs to large single graphs.
This option displays live graphs and graphs for three other time
spans in different tabs.
Shortcut: Ctrl+L
Small Multiple Graphs
Change the view in Devices 2946 menu tab to multiple small graphs.
This option displays live graphs and graphs for three other time
spans in one tab.
Show Geo Maps
Choose if you want to show geographical maps

Enterprise Console.
2753
in the
Shortcut: Ctrl+G
Show News Feed
Choose if you want to show the news feed in the Enterprise

Console.
Shortcut: Ctrl+N
Next Viewpoint
Go forward to the next viewpoint (only available if you went back

to a previous viewpoint before). This is similar to a browser's
function to go forth in history.
Shortcut: Alt+Right
Previous Viewpoint
Go backwards to the previous viewpoint. This is similar to a

browser's function to go back in history.
Shortcut: Alt+Left
Open in Web Browser
Open the currently selected object in the Ajax web interface. This
option is not available if multiple objects are selected. You can set
the default browser in the Opt ions 2977 settings.
Help
This menu provides links to help and information.
2984
21.01.2016
HELP
Help Center
Open the Help and Support Cent er in the Ajax web interface.
HTML Manual
Enterprise Console...
Open the Ent erprise Console

Ajax web interface.
PRTG Network Monitor

Homepage...
Open https://www.paessler.com/prtg in your browser for overall

information about PRTG.
Follow & Share
Open PRTG's social network contact information in the Ajax web

interface.
Contact Support
Open the Cont act Support 2932 dialog box to leave feedback or to
ask for support by sending a support bundle.
About...
Open an information window about the Enterprise Console

application with version number and copyright information.
2938
sections of this manual in the
See Also
Short cut s Overview
21.01.2016
2987
2985
Part 8: Enterprise Console | 7 Context Menus
8.7
Context Menus
For every object in the Enterprise Console, there are context menus available which appear
when you right-click an object in the device tree. These context menus vary depending on the
selected object and always contain a sub-set of the options available in the Windows menu.
For detailed explanations, please see Windows Menu St ruct ure 2979 .
Context Menu of a Dev ic e in the Enterprise Console
2986
12.11.2015
Part 8: Enterprise Console | 8 Shortcuts Overview
8.8
Shortcuts Overview
The following shortcut keys are available in the Enterprise Console:

Alt +X : File | Close or Exit
With the Show in Tray option enabled in the Opt ions
Exit .
2973
settings, this is Close, otherwise
Ct rl+Alt +X : File | Close and Exit

This menu item is only shown if the Show in Tray option is enabled in the Opt ions
settings.
2973
Alt +Right : Next Viewpoint

Alt +Left : Previous Viewpoint
Ct rl+K: Edit | Check Now
Ct rl+P: Edit | Pause | Indefinitely
Ct rl+R: Edit | Pause | Resume
Ct rl+E: Edit | Simulate Error Status
Ct rl+L: View | Large Single Graph
Ct rl+S: View | Small Multi Graphs
Ct rl+G: View | Show Geo Maps
Ct rl+N: View | Show News Feed
F5: View | Refresh
F6: [Context Menu] | Tools | Custom tool command, if available
F9: [Context Menu] | Tools | Custom tool command (default: Remot e Deskt op)
12.11.2015
2987
Part 8: Enterprise Console | 8 Shortcuts Overview
See Also
Windows Menu St ruct ure
2988
2979
12.11.2015
Part 9
Other User Interfaces
24.03.2015
2989
Part 9: Other User Interfaces |
Other User Interfaces
This chapter introduces other available user interfaces additional to PRTG's Ajax web interface
and Enterprise Console. There are special interfaces optimized for mobile access, including
apps for mobile devices. Read more in the following sections.
Other User InterfacesTopics

Mobile Web GUI
2991
Smart phone Apps
2995
Related Topics
108

Ent erprise Console
2990
218
2732
2938
24.03.2015
Part 9: Other User Interfaces | 1 Mobile Web GUI
9.1
Mobile Web GUI
IMPOR TANT NOTICE

The Mobile Web GUI is deprecated. We do not maintain this interface anymore and will
completely remove it from PRTG soon. For mobile access to your PRTG server, please use
our PRTG Apps for Mobile Net work Monit oring 2995 instead. For access to the fully
featured Ajax web interface 108 , please use the current version of a supported browser 27 .
For more information, please see section More 2994 .
The Mobile Web GUI is a slim interface to view your monitoring results while on the go. It is
optimized for both small screens and low bandwidth usage in order to provide an easy and
fast access to your PRTG core server when connecting with mobile devices. You can view
sensor lists, data tables, and graphs with live data.
Compared to the Ajax Web GUI 108 , this interface comes with limited functionality and is
primarily provided for quick review of data while on the go. Nevertheless, you can
acknowledge alarms, pause or resume monitoring, and interactively view geo maps as well as
sensors and other lists.
This interface is based on jQuery Mobile 1.0, supporting all major mobile operating systems
and browsers.
Loading the Web Interface

Make sure your PRTG core installation is accessible via the internet. In your mobile device,
enter the IP address or URL of the system PRTG is running on. When using a cluster, you can
connect to any node accessible.
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 113 .
Login Screen
After loading the web interface, the login screen is shown.
16.11.2015
2991
Mobile Web GUI Login
Enter your credentials, choose the Use Mobile Web GUI (Limit ed funct ionalit y , opt imized
for mobile access) option, and click Login. For detailed information on different credentials,
please see the Login 110 section for the Ajax Web GUI.
General Layout
The home screen of the Mobile Web GUI shows the sensor overview as well as all available
main menu entries. Click/tab on menu items to get to groups, devices, and sensor data. You
will be guided through a sequence of sub and sub-sub screens. Whenever you get lost, click/
tab on the house symbol in the upper left corner to get back to the home screen.
2992
16.11.2015
PRTG Mobile Web GUI
There are also different sensor top lists available in the Sensors menu entry. Note: Most of the
functionality is read-only, because this interface is intended for viewing data. In order to
change your monitoring configuration or settings, please switch to the Ajax Web Int erface 108
. If you would like to have more options on your mobile devices, take a look at our
Smart phone Apps 2995 .
Using the Mobile Web GUI

The device tree and lists of sensors, alarms, logs, and tickets are available as usual, but in a
view that is optimized for mobile screens. In addition, you can show monitoring data for all
objects. This section will not explain the GUI in detail, because the concepts are the same as
throughout the Ajax web interface 108 . In the following, find a list with the main differences
compared to the full Ajax interface:
There are no context menus available, but actions such as acknowledge an alarm, scan now,
pause, etc. can be initiated directly on an object's details page, using the corresponding
buttons.
Reports and Maps are accessible in a view-only mode.
You cannot edit system settings.
To save bandwidth, an automatic page refresh is only activated after confirmation.
You can switch from the Mobile Web GUI to the Ajax web interface at any time by using the
Swit ch t o AJAX GUI option.
16.11.2015
2993
You will just need a few minutes to become familiar with this interface, because the structure is
basically the same as you know it from PRTG's Ajax web interface. Have fun monitoring while
on the go!
More
Knowledge Base: Why does Paessler remove the Mobile Web GUI from PRTG?
2994
16.11.2015
Part 9: Other User Interfaces | 2 PRTG Apps for Mobile Network Monitoring
9.2
PRTG Apps for Mobile Network Monitoring
You can access your PRTG installation on your mobile devices with several PRTG apps. We
provide apps for iOS devices, Android systems, and Windows Phone. You can download and
use these apps for free. PRTG for iOS 2995 , PRTG for Android 2995 , and PRTG for Windows Phone
, and make it possible to monitor your network while on the go.
2996
The basic requirements to use these free apps are a running PRTG core server which is
accessible from the network your device is connected to (either directly or via a VPN
connection) and a recent operating system version on your mobile device. For details about
requirements, see below.
PRTG for iOS

PRTG for iOS is the iOS app for PRTG Network Monitor version 13 or later. You can use it on
iPhone, iPad, and iPod touch with iOS version 7 or later. You can also use free push
notifications 2842 with this app.
For more information and to download this app, please see our web page PRTG for iOS.
Maps on iPad
PRTG for Android

PRTG for Android is the Android app for PRTG Network Monitor version 13.1 or later. Use it on
your smartphone or tablet with Android version 4.0 or later, on a BlackBerry device or on a
Kindle Fire. For full functionality, we recommend that you use at least PRTG 13.x.4 and Android
4.1. On your BlackBerry device you need version 10.3. Note: You cannot deploy the app via
BlackBerry Enterprise Service (BES).
You can also use free push notifications
2842
with the PRTG for Android app.
For more information and to download this app, please see our web page PRTG for Android.
21.01.2016
2995
Sensor List on PRTG

for Android
PRTG for Windows Phone

PRTG for Windows Phone is the Windows Phone app for PRTG Network Monitor 13.3 or later.
You can run it on Windows Phone 8.0 or later.
For more information and in order to download this app, please see our web page PRTG for
Windows Phone.
PRTG for Windows Phone

Menu
Note: Push notifications are currently not supported with this app.
More
PRTG for iOS:
https://www.paessler.com/apps/iosapp
PRTG for Android:
2996
21.01.2016
https://www.paessler.com/apps/androidapp
PRTG for Windows Phone:
https://www.paessler.com/apps/windowsphoneapp
PRTG for Blackberry:
https://www.paessler.com/apps/blackberryapp
Knowledge Base: Which features do the PRTG mobile apps support?
Knowledge Base: How can I use push notifications with PRTG?
21.01.2016
2997
Part 10
Sensor Technologies
24.03.2015
2999
Part 10: Sensor Technologies |
10
Sensor Technologies
This section introduces different technologies that PRTG uses for monitoring to give you more
background information. Please read more in the following sections.
Sensor TechnologiesTopics
Monit oring via SNMP
3001
Monit oring via WMI
3005
Monit oring via SSH
3008
Monit oring Bandwidt h via Packet Sniffing

Monit oring Bandwidt h via Flows
3012
Bandwidt h Monit oring Comparison

Monit oring Qualit y of Service
Monit oring Email Round Trip
Monit oring Backups
3015
3017
3022
3024
Monit oring Virt ual Environment s

Monit oring Dat abases
3025
3033
Monit oring Sy slogs and SNMP Traps
3000
3010
3038
24.03.2015
Part 10: Sensor Technologies | 1 Monitoring via SNMP
10.1
Monitoring via SNMP
Monitoring via Simple Network Management Protocol (SNMP) is the most basic method of
gathering bandwidth and network usage data.
How SNMP Monitoring Works

You can use SNMP to monitor bandwidth usage of routers and switches on a port-by-port
basis, as well as device readings such as memory and CPU load. The queried devices must
support SNMP.
Network Monitoring v ia SNMP

Clic k here to enlarge: http://media-s3.paessler.c om.s3.amazonaws.c om/prtg-sc reenshots/network-monitoringv ia-snmp.png
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
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.
Reasons to Choose SNMP Monitoring

SNMP is the most commonly used method mainly because it is easy to set up and requires
minimal bandwidth and CPU cycles. If your network devices support SNMP and/or if you want
to monitor large networks with several hund

PRT G Manual

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PRT G Manual

Încărcat de

Drepturi de autor:

Formate disponibile

PRTG Net work Monit or User Manual

Part 1 Welcome to PRTG Network M onitor

About this Document

Part 2 Quick Start Guide

Part 3 Installing the Software

Part 4 Understanding Basic Concepts

Architecture and User Interfaces

Part 5 Ajax Web InterfaceBasic Procedures

Part 6 Ajax Web InterfaceDevice and Sensor Setup

Cloud Ping Sensor

SNMP Custom Sensor

SNMP Synology Physical Disk Sensor

WMI Microsoft SQL Server 2005 Sensor (Deprecated)

Part 7 Ajax Web InterfaceAdvanced Procedures

System AdministrationNotification Delivery

Part 8 Enterprise Console

Part 9 Other User Interfaces

Part 10 Sensor Technologies

Monitoring via SNMP

10 Monitoring Virtual Environments

Part 11 PRTG Administration Tool

Part 12 Advanced Topics

Active Directory Integration

Part 1: Welcome to PRTG Network Monitor |

Welcome to PRTG Network Monitor

A PRTG Network Monitor standard installation

Why Network Monitoring is Important

Part 1: Welcome to PRTG Network Monitor |

Monitoring Networks with PRTG Network Monitor

Part 1: Welcome to PRTG Network Monitor | 1 About this Document

About this Document

Part 1: Welcome to PRTG Network Monitor | 2 Key Features

What is PRTG for?

What is included in PRTG?

Part 1: Welcome to PRTG Network Monitor | 2 Key Features

Part 1: Welcome to PRTG Network Monitor | 3 New in This Version

New in This Version

in the current version, visit the version history

Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses

Supports all available sensor types.

Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Planning an Installation With Hundreds of Sensors or More?

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Detailed Sy stem Requirements

Net work Size: Recommendat ions

Running PRTG on Virt ual Machines

Running PRTG in a Failover Clust er

Web Browser Requirement s

Requirement s for Monit ored Devices

Requirement s for t he Ent erprise Console

Supported Operating Systems

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

the system provides 6 GB RAM or more.

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Network Size: Recommendations

We recommend that you use Windows Server 2012 R2 to run the

We recommend that you mainly use 1-minute scanning intervals

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Our general recommendation is to stay below 30 remote probes

CPU Intensive Features

Try keeping the usage of the following features down: Many

The quality of your network also plays an important role. When