PRTG Manual

PRTG Net work Monit or User Manual
2014 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: November 2014 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
15
16
18
19
21
23
32
Part 2 Quick Start Guide

1 ONEDownload, Installation, and First Login
2 TWOUsing the Configuration Guru
33
36
44
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
45
47
51
56
57
60
62
67
71
76
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
Data Reporting
User Access Rights
IPv6
77
81
83
88
90
91
92
93
94
95
98
100
Part 5 Ajax Web InterfaceBasic Procedures

1 Login
2 SSL Certificate Warning
3 General Layout
102
105
108
3
Contents
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Sensor States
Review Monitoring Data
Compare Sensors
Historic Data Reports
Similar Sensors
Object Settings
Alarms
Logs
Tickets
Working with Table Lists
Object Selector
Priority and Favorites
Pause
Context Menus
Hover Popup
Main Menu Structure
121
124
130
133
137
141
143
146
148
155
158
159
162
163
174
175
192
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 Sensor
Amazon CloudWatch Sensor
AVM FRITZ!Box WAN Interface v2 Sensor
Cisco IP SLA Sensor
Citrix XenServer Host Sensor
Citrix XenServer Virtual Machine Sensor
ClusterState Sensor
Core Health Sensor
Dell PowerVault MDi Logical Disk Sensor
Dell PowerVault MDi Physical Disk Sensor
DHCP Sensor
DNS Sensor
Enterprise Virtual Array Sensor
Event Log (Windows API) Sensor
Exchange Backup (Powershell) Sensor
Exchange Database (Powershell) Sensor
Exchange Mailbox (Powershell) Sensor
4
194
208
209
215
224
226
228
244
262
284
304
305
323
332
341
350
358
365
373
381
385
391
399
408
416
423
432
442
450
459
Contents
Exchange Mail Queue (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
HTTP Sensor
HTTP Advanced Sensor
HTTP Apache ModStatus PerfStats Sensor
HTTP Apache ModStatus Totals Sensor
HTTP Content Sensor
HTTP Full Web Page Sensor
HTTP Push Count Sensor
HTTP Push Data Sensor
HTTP Push Data Advanced Sensor
HTTP SSL Certificate Expiry 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
INI File Content Check Sensor
IP on DNS Blacklist Sensor
IPFIX Sensor
IPFIX (Custom) Sensor
IPMI System Health Sensor
jFlow V5 Sensor
jFlow V5 (Custom) Sensor
LDAP Sensor
Microsoft SQL Sensor
Microsoft SQL v2 Sensor
MongoDB System Health Sensor
MySQL Sensor
MySQL v2 Sensor
NetFlow V5 Sensor
NetFlow V5 (Custom) Sensor
NetFlow V9 Sensor
Oracle SQL Sensor
Oracle SQL v2 Sensor
Packet Sniffer Sensor
Packet Sniffer (Custom) Sensor
Passive Application Performance Sensor
PerfCounter Custom Sensor
467
475
483
494
504
512
520
528
536
545
553
562
575
584
593
604
613
620
629
638
647
659
672
681
688
697
706
714
726
733
741
751
761
770
780
789
795
804
817
824
833
846
856
865
875
884
894
907
916
925
932
5
Contents
PerfCounter IIS Application Pool Sensor

Ping Sensor
Ping Jitter Sensor
Pingdom Sensor
POP3 Sensor
POP3 Email Count Sensor
Port Sensor
Port Range Sensor
PostgreSQL Sensor
Probe Health Sensor
QoS (Quality of Service) One Way Sensor
QoS (Quality of Service) Round Trip Sensor
RADIUS Sensor
RADIUS v2 Sensor
RDP (Remote Desktop) Sensor
SCVMM Host Sensor
SCVMM Virtual Machine Sensor
Sensor Factory Sensor
sFlow Sensor
sFlow (Custom) Sensor
SFTP Secure File Transfer Protocol Sensor
Share Disk Free 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 Chassis Sensor
SNMP Cisco UCS Physical Disk Sensor
SNMP Cisco UCS System Health Sensor
SNMP CPU Load Sensor
SNMP Custom Sensor
SNMP Custom String Sensor
SNMP Dell Hardware Sensor
SNMP Dell PowerEdge Physical Disk Sensor
SNMP Dell PowerEdge System Health Sensor
SNMP Disk Free Sensor
SNMP GSA System Health Sensor
SNMP Hardware Status 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
6
940
948
956
963
969
977
986
994
1001
1014
1020
1027
1035
1042
1051
1058
1067
1076
1094
1103
1112
1119
1126
1134
1142
1151
1161
1169
1176
1183
1191
1198
1205
1213
1221
1229
1236
1243
1252
1262
1270
1278
1286
1294
1301
1309
1317
1325
1333
1341
1349
Contents
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 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
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
SSH VMWare ESX(i) Disk Sensor
SSL Security Check Sensor
Syslog Receiver Sensor
System Health Sensor
1357
1365
1373
1381
1389
1397
1405
1412
1423
1433
1440
1447
1455
1463
1471
1480
1487
1495
1503
1511
1518
1526
1533
1541
1549
1557
1565
1572
1580
1588
1596
1604
1611
1621
1632
1639
1645
1656
1664
1672
1680
1688
1697
1706
1715
1724
1734
1744
1753
1760
1771
7
Contents
TFTP Sensor
Traceroute Hop Count Sensor
Virtuozzo Container Disk Sensor
Virtuozzo Container Network Sensor
VMware Host Hardware (WBEM) Sensor
VMware Host Hardware Status (SOAP) Sensor
VMware Host Performance (SOAP) Sensor
VMware Virtual Machine (SOAP) Sensor
WBEM Custom Sensor
Windows CPU Load Sensor
Windows IIS 6.0 SMTP Received Sensor
Windows IIS 6.0 SMTP Sent Sensor
Windows IIS Application Sensor
Windows Last Update (Remote Registry) Sensor
Windows Logged In Users Sensor
Windows MSMQ Queue Length Sensor
Windows Network Card Sensor
Windows Pagefile Sensor
Windows Physical Disk Sensor
Windows Print Queue Sensor
Windows Process Sensor
Windows Registry Sensor
Windows Scheduled Task 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 Drive) Sensor
WMI HDD Health Sensor
WMI Logical Disk Sensor
WMI Memory Sensor
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
WMI Volume Fragmentation Sensor
WMI Windows Version Sensor
8
1776
1783
1790
1797
1803
1810
1818
1826
1835
1843
1851
1859
1867
1876
1884
1892
1901
1909
1917
1926
1935
1943
1952
1961
1969
1977
1986
1996
2006
2015
2024
2032
2043
2052
2060
2068
2080
2091
2102
2113
2121
2129
2138
2147
2155
2162
2169
2176
2184
2192
2201
Contents
WSUS Statistics Sensor

9 Additional Sensor Types (Custom Sensors)
10 Sensor Channels Settings
11 Sensor Notifications Settings
2209
2217
2220
2227
2238
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
Reports Settings
Maps
Maps Step By Step
Maps Designer
Maps Settings
Setup
Account SettingsMy Account
Account SettingsNotifications
Account SettingsNotification Contacts
Account SettingsSchedules
System AdministrationUser Interface
System AdministrationMonitoring
System AdministrationNotification Delivery
System AdministrationCore & Probes
System AdministrationUser Accounts
System AdministrationUser Groups
System AdministrationCluster
System AdministrationAdministrative Tools
PRTG StatusSystem Status
PRTG StatusAuto-Update
PRTG StatusCluster Status
PRTG StatusLicensing Status and Settings
Optional Downloads and Add-Ons
Desktop Notifications
SupportContact Support
2240
2245
2246
2248
2253
2256
2258
2263
2266
2275
2278
2282
2284
2290
2291
2295
2298
2301
2311
2314
2317
2323
2327
2329
2334
2349
2353
2357
2367
2372
2379
2385
2390
2394
2396
2401
2411
2416
2418
2421
2423
2425
Contents
2430
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
2433
2434
2437
2438
2445
2447
2449
2451
2453
2455
2457
2459
2461
2462
2465
2471
2478
2479
2482
Part 9 Other User Interfaces

1 Mobile Web GUI
2 Smartphone Apps
2483
2486
2490
Part 10 Sensor Technologies

1
2
3
4
5
6
7
8
9
10
11
12
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
Monitoring Virtual Environments
Monitoring Databases
Monitoring Syslogs and SNMP Traps
2491
2495
2498
2500
2502
2505
2507
2512
2514
2515
2524
2526
2536
Part 11 PRTG Administrator Tool

1 PRTG Administrator on Core Server System
2 PRTG Administrator on Remote Probe Systems
2537
2560
2568
Part 12 Advanced Topics

1 Active Directory Integration
2 Application Programming Interface (API) Definition
3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
10
2569
2571
2572
Contents
4
5
6
7
8
9
10
11
12
Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors

Define IP Ranges
Define Lookups
Regular Expressions
Add Remote Probe
Remote Probes and Multiple Probes
Remote Probe Quick Setup
Remote Probe Setup Using Installer
Failover Cluster Configuration
Failover Cluster Step by Step
Data Storage
Using Your Own SSL Certificate with PRTG's Web Server
Calculating Percentiles
2576
2578
2579
2587
2588
2589
2592
2597
2602
2605
2611
2613
2615
2618
Part 13 Appendix
1
2
3
4
Index
Glossary
List of Abbreviations
Support and Troubleshooting
Legal Notices
2619
2623
2626
2627
11
Part 1
Welcome to PRTG Network Monitor
19.09.2014
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.
Why Network Monitoring is Important

Today, most businesses rely on a computer and network infrastructure for internet, internal
management, telephone, and email. A complex set of servers and network equipment is
required to ensure that business data flows seamlessly between employees, offices, and
customers. The economical success of an organization is tightly connected with the flow of
data.
The computer network's reliability, speed, and efficiency are crucial for businesses to be
successful. But, like all other technical objects, network devices may fail from time to time
potentially causing trouble and loss of sales, no matter what migration efforts have been made
up-front.
Network administrators need to take three key steps to maintain network uptime, reliability,
and speed:
1. Set up a well-planned network with reliable components.
2. Create recovery plans for the event of device failure.
3. Monitor their network to know about failures as they build up or actually happen.
PRTG Network Monitor, the software described in this document, is a complete solution for
monitoring small, medium, and large networks.
Monitoring Networks with PRTG Network Monitor

PRTG Network Monitor is a powerful network monitoring application for Windows-based
systems. It is suitable for small, medium, and large networks and capable of LAN, WAN, WLAN,
and VPN monitoring. You can also monitor physical or virtual web, mail, and file servers, Linux
systems, Windows clients, routers, and many more. PRTG monitors network availability and
bandwidth usage, as well as various other network parameters such as quality of service,
memory load, and CPU usages. It provides system administrators with live readings and
periodical usage trends to optimize the efficiency, layout, and setup of leased lines, routers,
firewalls, servers, and other network components.
The software is easy to set up and use and monitors a network using Simple Network
Management Protocol (SNMP), Windows Management Instrumentation (WMI), packet sniffer,
Cisco NetFlow (as well as IPFIX, sFlow, and jFlow), and many other industry standard protocols.
It runs on a Windows-based machine in your network for 24-hours every day. PRTG Network
Monitor constantly records the network usage parameters and the availability of network
systems. The recorded data is stored in an internal database for later analysis.
14
19.09.2014
Part 1: Welcome to PRTG Network Monitor | 1 About this Document
1.1
About this Document
This document introduces you to the system concepts of PRTG Net work Monit or and
explains how to set up the software to achieve the best monitoring results. You will learn how
to plan your monitoring setup, how to set up your devices and sensors, dependencies,
reports, notifications, maps, user accounts, and clustering for fail-safe monitoring.
This document is also meant as a reference for all available settings. Short contextual help is
already provided within the Ajax web interface; in this manual you often get some more help
regarding the different options available.
This document does not explain monitoring protocols and file formats in-depth. Also, the use
of the Application Programming Interface (API) built into PRTG is only briefly addressed.
Whenever possible, hyperlinks to more detailed resources are provided, such as articles in the
Paessler Knowledge Base.
To start using PRTG right away, please see the Quick St art Guide
detailed instructions, see the other sections.
19.09.2014
32
section. For more
15
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
1.2
Key Features
PRTG Network Monitor monitors your network and requires no third party software.
Conducting a quick ad-hoc download, you do not need to fill web forms and will not have any
registration hassles. The installation process requires only a few minutes, as well as the first
configuration which is mainly done automatically. The initial setup is achieved by an interactive
guidance by the software.
What PRTG Can Be Used For

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

The PRTG installer contains all modules and software necessary to run the monitoring system
without the need for third party modules, including:
High performance: PRTG's own fast and efficient database system stores the raw monitoring
results, as well as logs, toplists, and tickets (outperforms SQL servers for monitoring data),
accessible through the Application Programming Interface (API). You can distribute high loads
over multiple probes.
Low system requirements: An average PC from the year 2007 is sufficient and even a
netbook can monitor over thousand sensors.
High security standards: SSL encryption for connections and web server, and multiple user
accounts with shared and private sensors, as well as rights management, and many more.
16
19.09.2014
Part 1: Welcome to PRTG Network Monitor | 2 Key Features
Built-in SSL secured web server with HTTP and HTTPS support for the user interface.
Fast web interface, works as Single Page Application (SPA) to avoid time-extensive reloading
of the page.
Mail server for automatic email delivery.
Flexible alerting
including nine notification technologies, for example, email, SMS, syslog and SNMP trap,
HTTP request, event log, Amazon SNS, executing scripts, etc.
including various triggers, for example, status alerts, limit alerts, threshold alerts, multiple
condition alerts, escalation alerts.
including dependencies to avoid alarms floods, acknowledging alarms to avoid further
notifications for this alarm, and alert scheduling.
In-depth report generator to create reports on-the-fly as well as scheduled reports in HTML
or Portable Document Format (PDF). Many report templates are available by default.
Graphics engine for user-friendly live and historic data charts.
Network analysis module to automatically discover network devices and sensors.
Distributed monitoring to monitor several networks in different locations.
Special features for Managed Service Provider (MSP) to monitor customer networks and
increase the quality of service.
Data publishing with real time dashboardsprivate and publicincluding live performance
and status information. You can design these maps as you like with many different objects,
as well as you can integrate external custom objects.
Different languages like English, German, Spanish, French, Portuguese, Dutch, Czech,
Japanese, and Simplified Chinese.
Customizations: The PRTG Application Programming Interface (API) allows you to program
your own features and to customize and re-brand PRTG's web interface to your needs. In
addition, you can create custom sensors, notifications, and device templates.
PRTG Network Monitor supports monitoring up to 20,000 thousand sensors per installation. It
can optionally work with multiple remote probes to monitor multiple sites or network
segments from one central core installation, and to distribute high loads. You can also
configure fail-safe monitoring using a cluster installation to perform automatic failovers. Single
failover installations are allowed with every PRTG license.
The software is based on Paessler's reliable monitoring technology, which has been constantly
improved since 1997 and is already used by more than 150,000 users around the world every
day. An outstanding support ensures that your inquiries are answered within one business day
to ensure best possible network monitoring. Attractive licensing packages from freeware (up
to 30 sensors) to enterprise level (with thousands of sensors) make sure that every user finds
the proper solution.
19.09.2014
17
Part 1: Welcome to PRTG Network Monitor | 3 New in This Version
1.3
New in This Version
With ongoing continuous development and rollout, we constantly extend and improve on the
functionalities provided by PRTG. Instead of delivering just a few versions distributed over the
year with massive changes in every version, PRTG is automatically and seamlessly enhanced
with new features and fixesfast and with high quality. There are three release channels for
PRTG:
St able: best tested version of PRTG for live systems; updated about once or twice a month;
for usage on live systems
Preview: offering the latest features and fixes; updated about once a week; consider this
version as "beta", thus, do not use this version on live systems you have to depend on!
Canary : providing "nightly builds"; updated very often; not tested extensively; never use on
live systems you have to depend on!
Because of these three channels, you can choose either maximum stability, earlier access to
new features, or a mixture of both.
For an overview of all most recent changes in the current version, please visit the version
history on our website. Please see the More 18 section below for more information.
More
Paessler Website: PRTG Network Monitor Version History
http://www.paessler.com/prtg/history
Paessler Blog: Version 12 of PRTG introduces "Continuous Rollout"
http://www.paessler.com/blog/2012/04/25/
18
19.09.2014
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
1.4
Available Licenses
There are four different PRTG flavors available.
Freeware Edition
The Freeware Edition is a good solution to get started with PRTG or for private use:
Is for free for personal and commercial use.
Can monitor up to 30 sensors.
Supports all available sensor types.
Shortest available monitoring interval is one minute.
Note: If you want to use the Freeware Edition, please first install the Trial Edit ion 19 and get a
free trial key. After the trial period has ended, your Trial Edition will automatically revert into a
Freeware Edition.
Special Edition
The Special Edition has all the features of the Freeware Edition, plus it supports up to 50
sensors. You can extend your Freeware Edition by entering the key for a Special Edition. This
key is not for download and is only used for special marketing campaigns.
Trial Edition
The Trial Edition is intended for evaluation purposes for customers who are interested in
purchasing commercial licenses:
Can monitor an unlimited number of sensors.
Shortest available monitoring interval is one second (not officially supported; a minimum
interval of 10 seconds is recommended).
Temporary license key must be requested from Paessler's website.
Trial period limited to 30 days (automatically reverts to Freeware Edition
19
afterwards).
With each license one single failover cluster setup 81 , consisting of two nodes, is included.
Cluster installations with two and three failover nodes will require one additional trial license
key; a cluster installation with four failover nodes will require two additional trial license
keys.
After the trial period has ended, a Trial Edition will revert into a Freeware Edition, allowing you
to monitor up to 30 sensors for free.
Commercial Editions
There are several licenses of PRTG Network Monitor available to suit the demands of smaller as
well as larger customers and organizations:
18.11.2014
19
Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses
Can monitor maximum number of sensors (from 100 to unlimited).

Shortest available monitoring interval is one second (not officially supported; a minimum
interval of 10 seconds is recommended).
With each license one single failover cluster setup 81 , consisting of two nodes, is included.
Cluster installations with two and three failover nodes will require one additional license of
the same size; a cluster installation with four failover nodes will require two additional
licenses of the same size.
For more information about available commercial licenses, please see More
20
section below.
More
Knowledge Base: What is the PRTG Special Edition license?
http://kb.paessler.com/en/topic/8063
Paessler Website: Request a Free PRTG Trial Key for Evaluation
http://www.paessler.com/prtg/trial
Paessler FAQs: What is the difference between the PRTG Network Monitor licenses?
http://www.paessler.com/support/faqs#e1912
20
18.11.2014
Part 1: Welcome to PRTG Network Monitor | 5 System Requirements
1.5
System Requirements
In order to install and work with PRTG Network Monitor, you need to meet the following
requirements:
A PC server or virtual machine with roughly the CPU performance of an average PC built in
the year 2007 or later and minimum 1024 RAM memory. For cluster 81 installations, use
systems with similar performance.
Operating systems Microsoft Windows 7, Windows 8, Server 2012, Server 2012 R2, or
Windows 2008 R2 (all 32-bit or 64-bit) are officially supported. You can also use Windows
Vista or 2008 R1, but we recommend not using these systems, because there are known
performance issues related to them.
Web browser to access the web interface. The following browsers are supported:
Google Chrome 38 or later (recommended)
Mozilla Firefox 33 or later
Microsoft Internet Explorer 10 or 11
Planning an Installation With Hundreds of Sensors or More?

As a rule of thumb, an average PC/server built in the year 2007 or later should be able to
monitor 1,000 sensors with ease. Some exceptions apply for version 3 of Simple Network
Management Protocol (SNMP), Windows Management Instrumentation (WMI) and packet sniffer.
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,
consider the following rules:
SNMP V1 and V2, Ping, Port , and HTTP
These sensor types are recommended for scenarios with thousands of sensors. With these
technologies up to 20,000 sensors are possible.
SNMP V3
You will be able to monitor about 5,000 SNMP V3 sensors with an interval of 60 seconds on
a common two core computer, and about 10,000 sensors on a four core system (the main
limiting factor is your CPU power).
WMI
Try to keep the number of WMI sensors per probe below 120 sensors (with 60s interval), or
600 sensors (with 300s interval).
xFlow (IPFIX , Net Flow, sFlow, jFlow)
Monitoring the maximum number of sensors depends on the traffic pattern, the number of
xFlow packets per second received by the PRTG probe, as well as the performance of the
probe system (see site planner tool linked in the More 22 section below).
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 2588 should be used.
18.11.2014
21
VMware Monit oring

Monitoring of VMware is limited to about 20 sensors at a 60 seconds monitoring interval, or
100 sensors at a 5 minutes interval. These limitations issue from the VMware platform. A
registry hack is available to boost this to 150 sensors at a 5 minutes interval (this will require
a change in the ESX/vCenter configuration). For details please see More 22 section below.
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; 5,000 sensors per
probe) to bold red (very high impact; 50 sensors per probe).
To overcome any limitations mentioned above you should distribute the sensors over two
remote probes 2588 or more. For clusters we recommend to stay below 10,000 sensors per
cluster. For detailed information, please use the site planner tool to plan large installations.
See More 22 section below.
We recommend using a dedicated physical machine to run both the PRTG core server and PRTG
remote probes. For more information please see the Det ailed Sy st em Requirement s 23
section.
More
Updat e From Previous Versions
47
Knowledge Base: Planning Large Installations of PRTG Network Monitor

Knowledge Base: Paessler PRTG Site Planner Tool
Knowledge Base: How can I speed up PRTGespecially for large installations?
Knowledge Base: Increasing Maximum Connections for VMware Sensors
Knowledge Base: Checklist for Running PRTG on VMware
Knowledge Base: Which ports does PRTG use on my system?
Knowledge Base: Which .NET version does PRTG require?
22
18.11.2014

1 Detailed System Requirements
1.5.1
Detailed Sy stem Requirements
This section lists different aspects of system requirements for PRTG. Please consider these
requirements in order to avoid issues while network monitoring.
Support ed Operat ing Sy st ems
Hardware Requirement s
Sample Configurat ions
23
24
25
Running PRTG on Virt ual Machines

Web Browser Requirement s
Screen Resolut ion
27
28
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
29
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 (Intel x86/x64 architectures only):
Microsoft Windows 7
Microsoft Windows 8
Microsoft Windows Server 2008 R2 and Windows Server 2008 R2 SP1
Microsoft Windows Server 2012**
Microsoft Windows Server 2012 R2**
Microsoft Windows Vista*
Microsoft Windows Server 2008*
* For performance reasons, we do not recommend using Windows Vista or Windows Server
2008 R1, especially when monitoring via Windows Management Instrumentation (WMI). Using
these operating systems, you will only be able to add a limited number of WMI sensors! For
detailed information, please see More 29 section below. If you need to use Windows Server
2008 R1, we strongly recommend installing Service Pack 2 (SP2).
** Windows Server 2012 in Core mode and the Minimal Server Interface are not officially
supported.
18.11.2014
23

Note: The operating systems Windows XP, Windows Server 2003, and Windows Server 2000
are not officially supported. If you run PRTG on one of these operating systems, you have to
accept limited monitoring functionality. We do not provide support for any issues that might be
caused (directly or indirectly) by using these Windows versions.
The version (32-bit or 64-bit) of the PRTG Core Server depends on the version of your
operating system. The 64-bit version of the PRTG Core Server will be installed if
the operating system is a 64-bit Windows system, and
the system provides 6GB RAM or more.
Otherwise the 32-bit version of the PRTG Core Server will be installed.
We recommend you to provide Microsoft .NET Framework versions 3.5 and 4.0 (with latest
updates) on all systems running a PRTG probe. Note: Version 4.0 is imperatively needed for
monitoring VMware and XenServer virtual environments.
More details: Some sensor types need the Microsoft .NET Framework to be installed on the
computer running the PRTG probe. This is either on the local system (on every node, if on a
cluster probe), or on the system running a remote probe 2589 . Depending on the sensor type,
the required versions are 2.0, 3.0, 4.0, or 4.5. See section More 29 for details. Note: According
to the Microsoft website, .NET version 3.5 contains versions 2.0 SP1 and 3.0 SP1. Version 4.0
is not downward compatible, but must be installed side-by-side to older version(s), if required.
For best performance of 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 2589 .
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
An average PC built in 2007 can easily monitor 1,000 sensors (see sensor type specific notes
below). PRTG supports native x86 architectures.
RAM memory
Minimum requirement: 1024 MB RAM. You will need about 150 KB of RAM per sensor.
Hard Disk Drive
You will 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
18.11.2014

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 2588 . If you plan installations with more than 500 to 1,000 sensors, or
more than 10 Packet Sniffer or xFlow (NetFlow, sFlow) sensors, please consult the site planner
tool linked in the More 29 section below. For clusters we recommend staying below 10,000
sensors per cluster.
Sample Configurations
The sample configurations in the table below will give you an overview of the hardware
requirements for PRTG, based on your configuration.
18.11.2014
25

Large Inst allat ion

A
Large Inst allat ion B Net book

Inst allat ion
Sy st em
DELL Alienware
DELL PowerEdge
2900 III
DELL Inspiron Mini

10
CPU
Intel Core2 QuadCore

2.6 GHz
Intel Xeon QuadCore

1.87 GHz
Intel Atom Z520

1.33 GHz
RAM
8 GB
16 GB
1 GB
Windows 7 64-Bit
Windows 2003 64Bit

Note: Windows
Server 2003 is not
officially supported.
Windows XP 32-Bit
Note: Windows XP is
not officially
supported.
20,000 SNMP
100 Other
20,000 SNMP
600 SNMP
750 WMI
400 switches 48
ports
400 switches 48
ports
24 switches 25
ports
+ 30 Windows
server
Scanning Int erval
1 minute
1 minute
5 minutes
Number of Probes
Average CPU Load

While Monit oring*
3%
20 %
35 %
Average CPU Load

While Generat ing
Report s*
20 %
30 %
85 %
Average Memory Used
3 GB
3.5 GB
260 MB
Average Dat a Writ t en

t o Disk Per Year
800 GB
800 GB
55 GB
550 kbit/s
150 kbit/s
Operat ing Sy st em
Sensors
Inst allat ion

Corresponds To
Average Net work Load 80 kbit/s

26
18.11.2014

* CPU load is higher while users are accessing the web interface.
Running PRTG on Virtual Machines

PRTG core server as well as PRTG probe can be run on virtualized platforms. The following
platforms were tested successfully:
Virt ual Host Technology
Client OS
VMware ESX/ESXi versions 3.5, 4.0, 5.0, or

5.5
Windows Vista, Windows 7 (32/64 bit),

Windows Server 2008 R2 (32/64 bit),
Windows 8 (32/64 bit), Windows Server 2012
(32/64 bit)
VMware Server 2.0

R2, Windows 8 (32/64 bit), Windows Server
2012 (32/64 bit)
XEN Server 5.0

2012 (32/64 bit)
Parallels Virtuozzo Containers

2012 (32/64 bit)
Cloud Hosting Platforms (Amazon EC2,

TheRackspaceCloud, and others)

2012 (32/64 bit)
Important notice: We recommend using a dedicated physical machine to run both the PRTG
core server and PRTG remote probes. If you run PRTG on a virtual machine, we strongly
recommend to stay below 2,000 sensors for performance reasons. Unfortunately, we cannot
offer technical support regarding performance and stability problems for PRTG installations on
virtual machines that run with more than 5,000 sensors. In this case, please migrate PRTG to
one or more, preferably physical, machines.
Note: When running PRTG on a virtual machine, do not use dynamic resource allocation, but
please make sure that full resources are available to the virtual machine at any time. In our
experience, dynamic resource allocation is not working efficiently for a monitoring software
and can therefore lead to massive performance issues.
Please see also section More
18.11.2014
29
regarding running PRTG on VMware.
27

Web Browser Requirements

The following browsers are officially supported by the PRTG web interface (in order of
performance and reliability):
Google Chrome 38 or later (recommended)
Mozilla Firefox 33 or later
Microsoft Internet Explorer 10 or 11
Note: Deprecated Internet Explorer versions as well as mobile browsers might not be able to
display the full featured Ajax web int erface 100 . Using these browsers, you can access the
feature-limited Mobile Web GUI 2483 , which does not require CSS or Javascript capability.
Screen Resolution
A screen resolution of at least 1024x768 pixels is sufficient for most functions of PRTG.
However, we recommend a screen resolution of 1200x800 or higher.
Requirements for Monitored Devices

SNMP monit oring
The monitored device(s) must be equipped with SNMP Version 1, 2c, or 3 (i.e., an 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.
Windows/WMI monit oring
In order to use WMI (Windows Management Instrumentation) monitoring, you will need a
Windows network. For client PCs monitored with WMI, only the operating systems as given
above 23 are officially supported. Windows Server 2000 and Windows Server 2003 are not
officially supported. Windows XP is also not officially supported and might not work with
sensors which use Remote Powershell. Please do not use Windows Vista or Windows 2008
R1 for WMI monitoring (they both have WMI performance issues).
xFlow (IPFIX , Net Flow, sFlow) monit oring
The device must be configured to send NetFlow data packets (NetFlow version 5 or 9; IPFIX
is the successor protocol of NetFlow 9) or sFlow packets (version 5) to the machine running
the PRTG probe.
Packet Sniffer monit oring
Only data packets passing the local machine's network card can be analyzed. Switches with
so-called 'monitoring ports' are necessary for network-wide monitoring in switched
networks.
Ot her sensor t y pes
Depending on the specific sensor type, you can find requirements (for example, modules,
components, device configurations) which may have to be fulfilled in the corresponding
manual section, as well as partly when adding the sensor to a device.
28
18.11.2014

Requirements for the Enterprise Console

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

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

The optional smartphone apps for iOS devices require iOS version 6 or later and PRTG v12 or
later. For Android devices, the app "PRTG for Android" requires Android OS 4.0 or later (version
4.1 or later recommended), as well as PRTG Network Monitor 13.1 or later. For more
information, please see Smart phone Apps 2486 . The 'Mobile Web GUI 2483 ' interface can be used
on most phones with a browser. We successfully tested it on Symbian, BlackBerry, Windows,
Android, and iOS devices.
More
47
Paessler Website: Paessler PRTG Site Planner Tool

Knowledge Base: My WMI sensors don't work. What can I do?
Knowledge Base: Frequent Questions about xFlow, Packet Sniffing, Traffic Monitoring and
Cisco
Knowledge Base: My SNMP sensors don't work. What can I do?
Knowledge Base: Checklist for Running PRTG on VMware
18.11.2014
29

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

Knowledge Base: Why can't I save my PRTG password in Google Chrome?
30
18.11.2014
Part 2
Quick Start Guide
19.09.2014
31
Part 2: Quick Start Guide |
Quick Start Guide
Welcome to PRTG Network Monitor! This section will support you with a quick start into PRTG,
so you can start monitoring your network right away!
Welc ome Sc reen
Setting up monitoring for your network is easy! You only need to download the installer from
Paessler's website, run through the installation wizard, and provide some information in the
configuration guru. PRTG will start monitoring your network immediately without any further
complicated stumbling blocks! Of course, later on, you still can adjust everything to your
needs.
Please see the following quick steps.
Quick Start GuideTopics

ONEDownload, Inst allat ion, and First Login
TWOUsing t he Configurat ion Guru
32
33
36
19.09.2014
Part 2: Quick Start Guide | 1 ONEDownload, Installation, and First Login
2.1
ONEDownload, Installation, and First Login
Simply download and install the version of PRTG Network Monitor which meets your needs.
For video tutorials with PRTG basics, please see section More 35 below.
Download
On the Paessler website, you find two different installers for PRTG, a public download for the
Freeware, Special, and Trial editions, and a login link to download the commercial editions
(which is only available for paying customers).
PRTG Download on Paessler Website with Marked Full Version Download Link
19.09.2014
33
Downloading the Freeware or Trial Edition

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

Downloads and updates are free to customers with an active maintenance contract. Please log
into the Paessler website to get the latest download. You can also find your license key there,
which must be entered during installation:
ht t p://www.paessler.com/login
If you do not have an active maintenance contract, please contact sales@paessler.com.
Note: Once installed, you will usually use the Soft ware Aut o-Updat e 2411 function of PRTG to
download and install new versions. This will further ease the process of installing updates.
Installation
Please double click the setup file on the computer that will be your PRTG server. Follow the
installation wizard and install the software.
At the end of the installation, a browser window will be opened automatically, and it will
connect to the PRTG web interface, showing the Configurat ion Guru. Please make sure you
load the web interface with one of the supported browsers:
Google Chrome 38 or later (recommended),
Mozilla Firefox 33 or later, or
Microsoft Internet Explorer 10 or 11.
Note: Due to scripting incompatibilities, you might not be able to use all functionalities of the
PRTG Ajax web interface with Internet Explorer 9 or earlier and other older browsers. If you
cannot access the Configurat ion Guru, please open the URL of the PRTG web interface in
another browser.
Login
If everything works fine, you will not see the login screen on first startup. Only when switching
browsers you will have to log in.
34
19.09.2014
PRTG Login Sc reen
Leave the Login Name and Password fields empty.

Choose the AJAX Web GUI (All feat ures, opt imized for deskt op access) option.
Click on the Default Login button to login.
Please make sure you use a supported web browser when logging in to PRTG. Please use
Google Chrome 38 or later (recommended), Mozilla Firefox 33 or later, or Microsoft Internet
Explorer 10 or 11. Only with a supported browser you can use the AJAX Web GUI (All
feat ures, opt imized for deskt op access) option. If you see this option grayed out, please
change your browser and open the URL again.
Please see the next step for more information about Using t he Configurat ion Guru
36
More
Video Tutorials for PRTG Network Monitor:
http://www.paessler.com/support/video_tutorials
19.09.2014
35
Part 2: Quick Start Guide | 2 TWOUsing the Configuration Guru
2.2
TWOUsing the Configuration Guru
For a new inst allat ion, PRTG will open t he Configurat ion Guru aut omat ically aft er each
login. It will reappear unt il y ou eit her ran t hrough it complet ely or skipped it . In order
t o open it at any t ime, please click t he Run Configurat ion Guru but t on on PRTG's Home
screen.
Note: When using the Ent erprise Console
Configurat ion Guru from the main menu.
2430
, please start the Guru by selecting Help | Run
Ajax Web Interfac e Home Sc reen
By answering about ten simple questions, this assistant will guide you through an initial setup
and pre-configure an essential monitoring of your network including important devices,
servers, and websites. You can later adjust these automatically generated monitoring settings
later by hand.
36
19.09.2014
Configuration Guru Start Sc reen
The steps to go are:

Enable SSL Encry pt ion
38
Configure Administ rat or Account

Ent er Windows/WMI Credent ials
Ent er SNMP Credent ials
38
38
39
Ent er VMware/X enServer Credent ials
39
Ent er Linux/Solaris/Mac OS Credent ials

Monit or Your Int ernet Connect ion
Monit or LAN Servers
40
40
Monit or Websit es/Online Shops

Monit or Cloud Services
41
41
Discover a Net work Segment

You Are Done!
40
41
42
Click on the St art Guru button to start. You can skip a step at any time by clicking on the Skip
button.
19.09.2014
37
Enable SSL Encryption

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

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

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

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

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

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

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

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

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

To see if the cloud services that you usually use are up and running, PRTG can set up http
sensors for those as well. In the list of services, simply switch the radio button to Yes for each
service you want to monitor. Choose from:
Google Search, Google Mail, Google Drive
Microsoft Office 365
Salesforce
Dropbox
iCloud
Facebook
Twit t er
Sky pe
PRTG will create a new device for all of cloud services, with one sensor for each URL.
Discover a Network Segment

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

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

Inst all a PRTG Core Server
Inst all a PRTG Clust er
Ent er a License Key
51
56
57
Act ivat e t he Product
60
Inst all a PRTG Remot e Probe
62
Inst all t he Ent erprise Console

Uninst all PRTG Product s
44
47
67
71
19.09.2014
Part 3: Installing the Software | 1 Download PRTG
3.1
Download PRTG
On the Paessler website, you find two different installers for PRTG, a public download for the
Freeware, Special, and Trial editions, and a login link to download the commercial editions
(which is only available for paying customers).
PRTG Download on Paessler Website with Marked Full Version Download Link
Downloading the Freeware or Trial Edition

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

Downloads and updates are free to customers with an active maintenance contract. Please log
into the Paessler website to get the latest download. You can also find your license key there,
which must be entered during installation:
ht t p://www.paessler.com/login
If you do not have an active maintenance contract, please contact sales@paessler.com.
Note: Once installed, you will usually use the Soft ware Aut o-Updat e 2411 function of PRTG to
download and install new versions. This will further ease the process of installing updates.
46
19.09.2014
Part 3: Installing the Software | 2 Update From Previous Versions
3.2
Update From Previous Versions
If you already have installed a previous software version, there are several things you should
consider before updating to the current PRTG version. Please see section Det ailed Sy st em
Requirement s 23 to see all requirements for the current PRTG version.
Note: We recommend you always have a proper backup of your monitoring data and
configuration. In most cases both will be maintained when upgrading. Anyway, we recommend
a backup before upgrading. Please see More 49 section below.
Update From PRTG Network Monitor 12 or later

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

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

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

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

Knowledge Base: Why is the Enterprise Console so slow?
Knowledge Base: Some of my SNMP sensors do not work after updating from PRTG 8 to PRTG
9 or later
Knowledge Base: Probe Service or Core Service stop working after updating from PRTG 8 to
PRTG 9 or later
Knowledge Base: How and where does PRTG store its data?
Knowledge Base: Can I update from PRTG Traffic Grapher or IP Check 5 to the current PRTG
version?
Knowledge Base: How do I Import Data from PRTG Traffic Grapher 6 or IPCheck Server Monitor
5 in PRTG Network Monitor?
50
19.09.2014
Part 3: Installing the Software | 3 Install a PRTG Core Server
3.3
Install a PRTG Core Server
Installing PRTG is easy. It is similar to other Windows-based applications. To install the

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

Only if you entered incorrect license information before you will be asked to enter a correct
license name and key.
Welc ome Wizard Enter Lic ense Information
Please enter both Name and Key exactly as stated in the email received from Paessler. We
recommend using copy&paste to avoid typing mistakes. For details, please see Ent er a
License Key 57 .
More
Knowledge Base: What is the PRTG Special Edition license?
Knowledge Base: How can I establish a secure web interface connection to PRTG?
Knowledge Base: PRTG blocks port 80 although I'm using SSL on port 443. How to free port
80?
19.09.2014
55
Part 3: Installing the Software | 4 Install a PRTG Cluster
3.4
Install a PRTG Cluster
PRTG offers single failover clustering in all licenseseven using the freeware edition. A single
failover cluster consists of two servers ("Current Master" Node and "Failover Node"), each of
them running one installation of PRTG. They are connected to each other and exchange
configuration and monitoring data. You can run a cluster with up to 5 nodes.
Illustration of a Single Failov er Cluster
For detailed information, please see Failover Clust er Configurat ion
2602
More
Knowledge Base: What's the Clustering Feature in PRTG?
56
19.09.2014
Part 3: Installing the Software | 5 Enter a License Key
3.5
Enter a License Key
A license key for PRTG Network Monitor consists of the license name and a license key. The
key is a string consisting of approx. 70 characters.
Your Personal License Information

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

License Name: John Q. Public
License Key: 0223515-FFSEJC-ZHGRDFM-UR1CS8-U73FGK-G645F2-YVF1DD-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 45 section.
Commercial license key : This key can only be entered if you install the Commercial Edition
of PRTG, available for download in the customer service center. See Download PRTG 46
section for details. Your installation allows the number of sensors according to your license.
Change License Key

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

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

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

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

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

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

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

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

Please execute the setup program you just have downloaded.
19.09.2014
67
Windows GUI Setup Wizard Welc ome Sc reen
After accepting the license agreement, you can choose the folder you wish to install the
software in. We recommend using the default value.
68
19.09.2014
Select which icons will be created. We recommend using the default value.
Windows GUI Setup Wizard Additional Tasks
19.09.2014
69
Windows GUI Setup Wizard Install
After installation, click Finish to start the Enterprise Console.
Windows GUI Setup Wizard Finish
More
Please see section Ent erprise Console
User Interface (GUI).
70
2430
for more information on how to use this Graphical
19.09.2014
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.
19.09.2014
71
Uninstall PRTG Network Monitor Step 1
Step 4
Wait while the software is being removed.
Step 5
Confirm a system restart by clicking the Yes button.
72
19.09.2014
Step 6
After system restart, the software is removed. However, there are still custom data in the PRTG
program folder left. If you have uninstalled an entire PRTG Network Monitor installation or a
remote probe installation, your monitoring data is still stored on the system. To completely
remove all PRTG data, please delete the PRTG Net work Monit or program folder as well as the
Paessler\PRTG Net work Monit or folder in your data path. For more information where data is
stored see Dat a St orage 2611 section.
More
Knowledge Base: Can we remotely and silently uninstall a Remote Probe?
19.09.2014
73
Part 4
Understanding Basic Concepts
19.09.2014
75
Part 4: Understanding Basic Concepts |
Understanding Basic Concepts
There are a number of basic concepts that are essential for understanding the functionality and
ease of use of PRTG Network Monitor. We have made using our software as easy as possible;
setting it up for the first start and getting first monitoring results happens almost automatically.
Nevertheless, there are some basic principles we would like to explain to you. Please read this
section carefully to understand the underlying workflow like architecture of the monitoring
system, hierarchy of objects, settings inheritance, notifying, etc. Afterwards, you will be able to
enhance your monitoring experience permanently.
Understanding Basic ConceptsTopics

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

Tags
Scheduling
Not ify ing
91
92
93
Dat a Report ing
94
User Access Right s
76
88
90
Dependencies
IPv6
77
95
98
19.09.2014
Part 4: Understanding Basic Concepts | 1 Architecture and User Interfaces
4.1
Architecture and User Interfaces
PRTG Network Monitor consists of different parts which can be divided into three main
categories: System parts, control interfaces, and a basic administration interface.
Ty pe
Part of PRTG
System Parts
Core Server 78
This is the central part of a PRTG installation and includes data
storage, web server, report engine, a notification system, and
more. The core server is configured is Windows service which run
permanently.
Probe(s) 78
The part of PRTG on which the actual monitoring is performed.
There are local probes, remote probes, and cluster probes
available. All monitoring data is forwarded to the central core
server. Probes are configured as Windows services which run
permanently.
A special kind of probes are the mini probes. Please see the
Applicat ion Programming Int erface (API) Definit ion 2571 for
details.
User Interfaces
Ajax Web Int erface 100

The Ajax-based web interface is used for configuration of devices
and sensors, as well as the review of monitoring results. Also
system administration and user management are configured here.
Ent erprise Console 2430
A native Windows application (former Windows GUI) as alternative
to the web interface to manage your monitoring. With the
Enterprise Console, you can connect to different independent
PRTG core server installations and review their data at a glance!
Mobile Web GUI 2483
A read-only interface optimized for mobile access to your PRTG
installation. View latest states, tables, and graphs. Using jQuery
Mobile, this interface is compatible with almost all mobile devices
available on the market, as well as with older and unsupported
browser versions.
Smart Phone Apps 2486
Monitor your network on the go with PRTG and apps for iOS,
Android, Windows Phone, and BlackBerry devices.
System Administration
Program
19.09.2014
PRTG Administ rat or on Core Server Sy st em 2537

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.
77
Ty pe
Part of PRTG
PRTG Administ rat or on Remot e Probe Sy st em 2560
Used to configure basic probe settings such as name of the probe,
IP and server connection settings, and more.
Core Server
The core server is the heart of your PRTG system and performs the following processes:
Configuration management for object monitoring
Management and configuration of the connected probes
Cluster management
Database for monitoring results
Notification management including a mail server for email delivery
Report generator and scheduler
User account management
Data purging (culling data that is older than 365 days, for example)
Web server and API server
In a cluster
81 ,
the current master node is responsible for all of these tasks.
The built-in, fast, and secure web server (no additional IIS or Apache is required) supports HTTP
as well as secure HTTPS (via SSL). It serves the web interface when accessed with a browser
and also answers PRTG Application Programming Interface (API) calls (for example, for user
scripts or the Enterprise Console).
Note: Core server and probe(s) are configured as Windows services which are permanently run
by the Windows system without the requirement for a logged-in user.
Probe(s)
On a probe, PRTG performs the actual monitoring with the sensors created on a device (for
example, computer, router, server, firewall, etc.). The probe receives its configuration from the
core server, runs the monitoring processes, and delivers monitoring results back to the core
server. On every system running a PRTG core server, there is always a local probe running with
it on the same machine.
78
19.09.2014
PRTG Core Serv er and Loc al Probe Monitoring a Loc al Area Network
The actual monitoring is performed by PRTG probe processes which run on one or more
computers. During installation, the system automatically creates the so-called Local Probe. In a
single-probe installationwhich is the default setupthe local probe performs all monitoring.
The PRTG core server inside the corporate LAN (bottom right in the figure above) is able to
monitor services and servers in the entire Local Area Network (LAN). Note: Core server and
probe(s) are configured as Windows services which are permanently run by the Windows
system without the requirement for a logged-in user.
In a cluster setup 81 , a cluster probe runs on all nodes. There is an additional so-called Clust er
Probe. All devices created on it are monitored by all nodes in the cluster, so data from
different perspectives is available and monitoring for these devices always continues, also if
one of the nodes fails.
PRTG automatically monitors system health of its own core server and of each probe to
discover overloading situations that may distort monitoring results. To monitor the system
status of the probe computer, PRTG automatically creates a few sensors. These include Core
and Probe Healt h, Sy st em Healt h, Clust er Probe Healt h, Disk Free, and a bandwidth sensor
for all installed network cards. We recommend keeping these sensors, but you can optionally
remove all except the Healt h sensors. They measure various internal system parameters of
the probe system hardware and the probe's internal processes and then computes a resulting
value. Frequent or repeated values below 100% should be investigated. Please check the
channels 124 of a particular sensor for details.
Additional so-called Remot e Probes can be created by the user in order to achieve monitoring
of multiple locations, or for several other scenarios. They are using SSL-secured connections
to the core and allow to securely monitor services and systems inside remote networks which
are not openly accessible or secured by firewalls. For more information, please see Remot e
Probes and Mult iple Probes 2588 section. For a video on this please see More 207 section
below.
PRTG Mini Probes allow you to create small probes on any device (not just on Windows
systems). You can implement mini probes to gather monitoring data exactly like you need it
and create them on any platform. For more information, see the Mini Probe API definition in
the PRTG web interface.
19.09.2014
79
More
Video Tutorial: There is a video available on the Paessler video tutorials page.
80
19.09.2014
Part 4: Understanding Basic Concepts | 2 Clustering
4.2
Clustering
A PRTG Cluster consists of two or more installations of PRTG 51 that work together to form a
high availability monitoring system. The objective is to reach true 100% uptime for the
monitoring tool. Using clustering 2602 , 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 100 or Enterprise Console 2430 ). The master automatically distributes the
configuration to all other nodes in real time. All nodes are permanently monitoring the
network according to this common configuration and each node stores its results into its own
database. This way, the storage of monitoring results also is distributed among the cluster (the
downside of this concept is that monitoring traffic and load on the network is multiplied by the
number of cluster nodes, but this will not be a problem for most usage scenarios). The user
can review the monitoring results by logging into the web interface of any of the cluster nodes
in read only mode. Because the monitoring configuration is centrally managed, it can only be
changed on the master node, though.
By default, all devices created on the Clust er Probe are monitored by all nodes in the cluster,
so data from different perspective is available and monitoring for these devices always
continues, even if one of the nodes fails. In case the Primary Mast er fails, one of the Failover
Nodes takes over the master role and controls the cluster until the master node is back. This
ensures a fail-safe monitoring with gapless data.
Note: During the outage of a node, it will not be able to collect monitoring data. The data of
this single node will show gaps. However, monitoring data for this time span is still available on
the other node(s). There is no functionality to actually fill in other nodes' data into those gaps.
If downtimes or threshold breaches are discovered by one or more nodes, only one
installation, either the Primary Master or the Failover Master, will send out notifications (via
email, SMS text message, etc.). Thus, the administrator will not be flooded with notifications
from all cluster nodes in case of failures.
Note: For clusters we recommend you to stay below 10,000 sensors per cluster.
Set Up a PRTG Cluster

For detailed information, please see Failover Clust er Configurat ion
2602
More
18.11.2014
81
Part 4: Understanding Basic Concepts | 2 Clustering
82
18.11.2014
Part 4: Understanding Basic Concepts | 3 Object Hierarchy
4.3
Object Hierarchy
All objects in a PRTG monitoring configuration are arranged in a tree-like hierarchy to create an
easy to navigate list and to give the user the possibility to arrange them in groups that monitor
similar devices, services, or same locations. The hierarchical order described is also used to
define common settings for larger groups of objects, for example, settings of the Root group
apply by default to all other objects underneath (see section Inherit ance of Set t ings 88 ).
Objec t Hierarc hy in PRTG
The figure shows the object hierarchy in PRTG:

Root group contains all objects in your setup; all probes are directly under the root node.
A Probe contains one or more groups.
A Group contains one or more devices.
20.11.2014
83
A Device represents one component in your network which is reachable via an IP address.
On a device are several sensors.
A Sensor monitors one single aspect of a device and has at least one channel.
A Channel receives the monitoring results and is part of a sensor.
Root Group
The Root group is the topmost instance in PRTG. It contains all other objects in your setup.
Using the inheritance 88 mechanism, we recommend adjusting the default settings for the
Root group 228 . 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 2588 ). In a
cluster, there is an additional Clust er Probe running on all nodes. Devices on the cluster
probe are monitored by all nodes of the cluster, so data from a different perspective is
available and monitoring for these devices will always continue, even if one of the nodes fails.
Group
On each probe, there are one or more Groups, which serve merely structural purposes. Use
groups to arrange similar objects in order to inherit same settings to them. To a group, you
add the devices. You can arrange your devices in different nested groups to reflect the
structure of your network.
Find below a sample configuration: A device tree with local probe, several groups, devices and
their sensors.
84
20.11.2014
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.
20.11.2014
85
To get a better and more detailed picture about your devices, PRTG automatically analyzes the
devices which you add and recommends appropriate sensor types 305 on the device overview
tab 124 . 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
2369 .
Sensor
On each device you can create a number of Sensors. Every sensor monitors one single aspect
of a device. This can be, for example:
One network service like SMTP, FTP, HTTP, etc.
One network switch port's traffic
CPU load of a device
Memory load of a device
Traffic on one network card
One NetFlow device
System health of a device
Other content (for example, of databases, mails, HTTP, XML, files, etc.)
etc.
Channel
Every sensor has a number of Channels through which it receives the different data streams.
The available channels depend on the type of sensor. One sensor channel can contain, for
example:
Downt ime and upt ime of a device
Traffic in of a bandwidth device (for example, a router)
Traffic out of a bandwidth device (for example, a router)
Traffic sum of a bandwidth device (for example, a router)
WWW t raffic of a NetFlow device
Mail t raffic of a NetFlow device
Ot her t raffic of a NetFlow device
CPU load of a device
Loading t ime of a web page
Download bandwidt h of a web page
Time t o first by t e of a web page
86
20.11.2014
Response t ime of a Ping request to a device

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

You can override this inheritance on any level of the hierarchy by setting a different value for a
specific probe, group, device, or sensor. All objects below will inherit these new settings;
object settings from levels above will stay unchanged.
Settings that are inherited among all objects include:
Monitoring interval
Notification triggers
Authentication settings for several systems
Compatibility settings (for certain types of sensors)
Channel and unit configuration
User access rights
Tags
95
90
Paused status: If an object is paused by the user, or a schedule, all sensors on it are paused
as well
etc.
There is one exception for devices and sensors: The IP address or DNS name of a device and
compatibility settings are always inherited by sensors and can not be changed on sensor level.
The actual overriding of the parent's settings takes place in an object's settings: Remove the
check mark symbol at the beginning of the respective line inherit from [parent object ]. For
example, the screenshot below shows Windows systems credentials settings after removing
the check mark symbol.
Credentials for Windows Sy stems
88
19.09.2014
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
228
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
19.09.2014
2227
for details.
89
Part 4: Understanding Basic Concepts | 5 Tags
4.5
Tags
For every object in your PRTG setup, you cannot only name objects, but also define tags in
the object settings 141 to additionally mark an object as a member of certain categories.
Although there are tags predefined when adding objects 208 , 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 2248 of settings), or choose sensors by tag when creating
reports 2291 . 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
2248
function.
View and Edit Tags in Basic Sensor Settings
Tags Are Inherited

The tags in the settings of an object are automatically inherited 88 to all other objects
underneath in the hierarchy 83 . So, for example, a device with the tag myExampleTag
automatically and invisibly inherits this tag to all sensors which you create on it. This is not
visible in the sensor tag settings, but the sensors appear in the list whenever you search for
myExampleTag. This is useful, for example, when you add sensors by tag in reports 2291 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 155 for specific objects, for example, show only sensors
with the tag bandwidth_important on the sensors overview page 179 , or to add sensors to
Libraries 2275 and Report s 2291 . For this concern, you can also use plus (+) and minus () signs to
categorize tags. Plus means that the shown objects must have this tag, minus means that the
shown objects must not have this tag.
For example, if you enter windows into a tag field, all sensors/devices that do not have
"windows" as tag are shown. You can use more than one logical operator in a tag field: For
example, if you enter +netflow;bandwidth_important into one tag field or if you use the single
tags +netflow and bandwidth_important, the corresponding list, library, or report includes all
sensors that are tagged with "netflow" but not with the tag "bandwidth_important".
90
18.11.2014
Part 4: Understanding Basic Concepts | 6 Dependencies
4.6
Dependencies
Using dependencies, you can pause sensor monitoring based on the status of another sensor
in order to avoid false alarms and incorrect downtime recording. A dependency stops the
monitoring of one sensor or a set of sensors as soon as a specific sensor is not in an Up
status. This means, for example, you can stop monitoring remote network services when the
corresponding firewall is down due to connection problems.
When using the auto-discovery 194 function, the Ping sensor on a device is by default set as
the master object for this device. This means that monitoring for the entire device is paused if
the Ping sensor is in a Down status. Usually, it does not make sense to monitor other aspects
of a device with other sensors while the Ping sensor indicates that the device is not even
reachable.
In order to view a list of all dependencies or only selected dependencies, choose Devices |
Dependencies and the corresponding dependencies path from the main menu 177 . From there
you can also access the Dependencies Graph 2256 that visualizes all dependencies within your
network.
Dependenc ies Graph
For more information about the dependency settings, please see the settings of the
respective object 141 you want to set a dependency for.
19.09.2014
91
Part 4: Understanding Basic Concepts | 7 Scheduling
4.7
Scheduling
Using schedules, monitoring of an object can be paused 162 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 93 . 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 2353 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 2602 .
92
19.09.2014
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
2339 , SMS 2334 , push messages 2340 , 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 2263 section for more details and Set t ing Up
Not ificat ions Based on Sensor Limit s: Example 2266 for a step-by-step guide.
Limits
In a sensor channel's settings 2220 , 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
143 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 146 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 148
section for more information.
18.11.2014
93
Part 4: Understanding Basic Concepts | 9 Data Reporting
4.9
Data Reporting
With Report s 2291 you can analyze and review monitoring data for specific time spans. There are
several ways to create data reports in PRTG for your individual needs.
View Historic Data

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

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

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

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

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

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

Login
102
SSL Cert ificat e Warning

General Lay out
Sensor St at es
105
108
121
Review Monit oring Dat a

Compare Sensors
130
Hist oric Dat a Report s

Similar Sensors
Object Set t ings
Alarms
Logs
124
133
137
141
143
146
Ticket s
148
Working wit h Table List s

Object Select or
158
Priorit y and Favorit es

Pause
155
159
162
Cont ext Menus

Hover Popup
163
174
Main Menu St ruct ure
175
Other Ajax Web Interface Sections

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

In a web browser window, please enter the IP address or URL of the system PRTG is installed
on. When using a cluster, please connect to the primary master node. You can also double
click on the PRTG Net work Monit or icon on the desktop of the system PRTG is installed on.
Note: If you run PRTG on localhost, please do not use the DNS name http://localhost to log in
to the web server, as this may considerably slow down PRTG's web interface. Please use your
local IP address or http://127.0.0.1 instead.
Desktop Ic on
If you see a certificate warning in your browser, you can usually just confirm it. For more
information please see SSL Cert ificat e Warning 105 .
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 2385 with administrator rights or
with more restricted privileges (for example, read only users).
Additionally, there are different GUI versions available.
102
19.09.2014
PRTG Login Sc reen
Login as Default Administrator (First Time Login)

When logging in for the first time, login name and password for the default administrator login
are both prt gadmin. You can leave the login name and password fields empty and click on
the Default Login button to log in using these default credentials.
Note: After login you should change the default password. To do so, go to Set up | Account
Set t ings | My Account and specify a new password in section User Account .
Note: If you are not logged in into the web interface, you can change the credentials for this
default user account any time in the PRTG Administ rat or 2547 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 38 or later (recommended) or Mozilla Firefox 33 or later for
best performance. In some browsers, the Ajax option is not shown, for example, in old
browser versions.
Note: Although you can login using Microsoft Internet Explorer 10 or 11, the Ajax web
interface might not be fully compatible with Internet Explorer! When using Microsoft
Internet Explorer 10 or 11, please set the security level at least to Default level Mediumhigh and make sure you do not use the Compat ibilit y View! For detailed information,
please see More 104 section below.
19.09.2014
103
Use Mobile Web GUI (Limit ed funct ionalit y , opt imized for mobile access): The Mobile
Web GUI 2483 interface is optimized for slow network connections and old browsers. It only
offers read-only functionality and comes with less scripting. It is also a fallback solution when
using a browser that is not supported by the Ajax interface.
Download Client Soft ware (for Windows, iOS, Android): This option calls PRTG's download
page in the Mobile Web GUI. You can optionally download the native Windows application
Ent erprise Console to the desktop (called Windows GUI in previous deprecated PRTG
versions). It has to be installed 2430 on the client computer before use. The Enterprise
Console 2430 provides full functionality; however, for some functions the Ajax Web GUI is
opened. As an additional feature, the Enterprise Console can view data of several
independent PRTG core installations in a single application.
You can also access pages on Paessler's website from here for information about the PRTG
apps 2486 PRTG for Android and iPRTG for iOS. These pages contain also the download links
for the apps for your mobile device. Note: Also when using this download option, login
name and password (or a Default Login) are required!
Note: Only Google Chrome 38 or later (recommended) and Mozilla Firefox 33 or later are fully
compatible with the Ajax web interface. For more information about Internet Explorer support,
Click on the Login button to proceed to the PRTG web interface.
More
Knowledge Base: Why are Internet Explorer IE6 and IE7 not supported by PRTG's Ajax Interface?
Knowledge Base: How can I access the AJAX web interface of PRTG with Internet Explorer 9 or
IE10?
104
19.09.2014
Part 5: Ajax Web InterfaceBasic Procedures | 2 SSL Certificate Warning
5.2
SSL Certificate Warning
If you use PRTG outside your internal LAN, especially when you use it on the internet, you
should switch the internal web server to use SSL. After doing so, your browser shows a
certificate warning because the certificate that comes with PRTG cannot be signed by a valid
authority. Anyway, the connection to your PRTG web server is secured via SSL, and you can
confirm the claimed security risk. For more information on secure browser connections, please
see the More 107 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
105
106
Internet Explorer
Other
106
107
Google Chrome
In Google Chrome, click on Advanced and then on Proceed t o [y ourPRTGserver] (unsafe)
every time you call the PRTG web interface.
Sec urity Warning in Google Chrome Browser
18.11.2014
105
Mozilla Firefox
In Mozilla Firefox, click on I Underst and t he Risks and then on the Add Except ion... button.
In the appearing window, leave the check mark for Permanent ly st ore t his except ion and
finally click on the Confirm Securit y Except ion button.
Sec urity Warning in Mozilla Firefox
You only have to go through this procedure once for every Firefox browser and PRTG core
server.
Internet Explorer
In Int ernet Explorer, click on Cont inue t o t his websit e (not recommended) every time you
call the web interface.
106
18.11.2014
Sec urity Warning in Internet Explorer
Other
For other browsers that are not officially supported, the procedures to confirm the certificate
are similar to the ones described above.
More
Using Your Own SSL Cert ificat e
2613
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?
18.11.2014
107
Part 5: Ajax Web InterfaceBasic Procedures | 3 General Layout
5.3
General Layout
This manual section provides an overview about the structure of PRTG's web interface. The
main focus is on the Devices view which you can select via the main menu bar, because there
you see your monitoring results at a glance so you will widely use it.
Welcome Page
Once you have run through the Configurat ion Guru 36 , you will see PRTG's welcome page as
default after you log in to the web interface. You can set another homepage in your account
settings 2329 , section Web Int erface.
You have the following options on the welcome page:
Run Configurat ion Guru
36
Download Windows Client App
2421
Perform Net work Aut o-Discovery

Inst all Smart phone Client Apps
Review Result s
194
2486
133
Get Help and Support : Opens the help center where you find links to this manual, to the
Knowledge Base, and the contact Paessler support form 2425 .
PRTG Welc ome Sc reen
108
18.11.2014
Tree View Layout

Click on the Review Result s option on the welcome screen to display the tree-like device
view which will be a starting point for everyday use or on Devices in the main menu bar.
PRTG Dev ic e Tree
From top to bottom, the main layout consists of:
18.11.2014
109
Screen
Number
Part
Descript ion
Global Header
Area 111
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, etc.
of the current object, the object's status bar, quick action
buttons, and the QR code linking to the current URL.
112
Device Tree
View 115
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.
119
Page Footer
Icons
With these icons you have quick access to the PRTG AutoUpdate page, to PRTG's social network accounts, and to the
contact support form 2425 . 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 2416 . In a failover node, you
can review all data, but changes in the settings will not be
saved. In order to change settings, please log into the master
node of your cluster.
Page Footer
Shows information about the current version of PRTG, the

logged in user, the time remaining to the next automatic page
refresh, and the current time.
Simply click on an object to see more details about it. In the page heading of the page header
bar 112 you always see which object you're looking at.
When you navigate through PRTG's web interface you will always use one of the following
navigational paths:
The main menu provides access to all important aspects of the software.
The quick search is often the fastest way to navigate to an object.
Using the page's tabs, you can switch between various sub-pages for an object.
Many objects offer a context menu that will pop up when you right-click them.
Many objects offer a quick-info menu that will pop up when hovering an object
110
18.11.2014
And, finally, you are able to drill down into the object hierarchy of probes, groups, devices,
and sensors in the object tree by merely clicking an sub-object of the currently displayed
object (for example, a sensor on the device page).
These six navigation paths put PRTG's complete functionality at your fingertips. Quite likely you
are already familiar with these techniques from many other websites and web-based user
interfaces.
In the following, the different areas of the web interface are described.
Global Header Area
PRTG's Global Header Area
The header area of the web interface is both base for the most important information of your
installation and starting point for all actions. You can view the global status and navigate
through the web interface using the main menu.
Note: This documentation refers to the PRTG Sy st em Administ rat or user accessing the Ajax
interface on a master node. For other user accounts, interfaces, or nodes, not all of the
options might be available as described. When using a cluster installation, failover nodes are
read-only by default.
The global header area consists of the following parts:
18.11.2014
111
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 175 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, there is always a path shown, leading to

the homepage. Use it to go back to where you came from. It
can also help you to orient yourself in case you get lost. If you
click on a 'breadcrumb' item to open a drop-down menu
showing all available object on the same level. Enter a view
letters to search for a name, or select an object directly. For
example, you can use this to directly access all other sensors
or a device, the other devices within a group, another group on
the same probe, or other probes in your root group.
Buttons New
These buttons show the number of new alarms and new log
Alarms, New Log entries, as well as the number of new tickets. Click on the
Entries, New
respective button to view the Alarms 143 , Logs 146 , or Ticket s
148 .
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 state.
Click on a box to view a list of all sensors in the respective
status. For a detailed description, please see Sensor St at es 121
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.
112
18.11.2014
PRTG's Page Header Bar
The page header and tabs area consists of the following parts:
18.11.2014
113
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 159 .
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 141 .
124
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
146 . 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 163 section.
114
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 121
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 then highlight matching devices and sensors by
graying out all others. This can help to gain a quick overview
over sensors monitoring a specific part of your network. For
example, you can enter the keyword "firewall" to highlight
devices and sensors which match this name.
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 115 below.
18.11.2014
Depending on the selected object type, the page header bar shows additional information. All
objects underneath the Root group indicate their dependency 91 , groups and devices show
the past time since the last auto-discovery 194 was run on the selected object (hover to show
the exact date and time), and devices show their respective DNS/IP address as defined in the
device settings 284 . 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).
18.11.2014
115
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.
116
18.11.2014
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 121 ) 121 . 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:
18.11.2014
117
Flag
Flag Color
Object St at us
Meaning
Red
Down
At least one sensor of this object shows a red

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

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

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

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

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

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

You can adjust the size of the different squares. They can be calculated by the number of
sensors running on a device or within a group, or by the sensors' priority (see Priorit y and
Favorit es 159 ), 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.
118
18.11.2014
Page Content
The page content of the general layout varies dependent on the selected object. It shows
information about the current object and all other objects underneath in the tree hierarchy.
The deeper down in the hierarchy you select an object, the more detailed is the displayed
information.
By default, a Probe Device is created in the device tree on the local probe. It represents the
probe system running with your PRTG installation. PRTG automatically monitors the system
health of the core server and each probe in order to discover overloading situations that may
distort monitoring results. To monitor the system status of the probe computer, PRTG
automatically creates a few sensors. These include a Core/Probe Healt h Sensor, a WMI
sensor that measures disk usage, and a bandwidth sensor for all installed network cards. It is
recommended to keep these sensors, but you can optionally remove all except the Core/
Probe Healt h sensor. In a cluster installation, PRTG also creates a Clust er Probe Device with
a Clust er Probe Healt h Sensor 381 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 112 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 159 for this concern.
For more details about page contents, please see the following sections:
18.11.2014
124
119

Object Set t ings
141
Compare Sensors
Geo Maps
133
130
2258
More
Knowledge Base: How can I change the width of the devices and group "boxes" shown in the
PRTG 9 device tree?
120
18.11.2014
Part 5: Ajax Web InterfaceBasic Procedures | 4 Sensor States
5.4
Sensor States
In PRTG's device tree you usually create several sensors on each 'device 284 '. 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 109 , or on geo maps 2258 ) : 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 115 ), as this state is hierarchically higher.
Note: Down and Down (Part ial) states are hierarchically equal.
Sensor
Color
St at us Name
Meaning
Red
Down
1. PRTG is not able to reach the device or the

sensor has reached an error state. Please
see Sensor Warning and Down Behavior 122
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 2220 , or an error status due to a
sensor Lookup 2579 . Note: In this case, the
sensor continues to record data in all sensor
channels although the sensor shows an
error.
18.11.2014
Red/Green Down (Part ial)
In a cluster, at least one node reports this

sensor as Down, while at least one other node
reports the same sensor as Up.
Bright-Red
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 2263 are sent. To set this
sensor status, right-click on a sensor in a Down
status and from the context menu 163 , select
Acknowledge Alarm.... Then enter a comment
and click OK.
Down
(Acknowledged)
121
Sensor
Color
St at us Name
Meaning
Yellow
Warning
There was an error reading the sensor, but

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

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

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

time or unlimitedly, or by dependency).
Black
(Gray)
Unknown
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
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 238 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.
122
18.11.2014
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 2220 .
More
Knowledge Base: What to check if sensors are black (gray)?
18.11.2014
123
Part 5: Ajax Web InterfaceBasic Procedures | 5 Review Monitoring Data
5.5
Review Monitoring Data
Pages of probes, groups, device, and sensors have a tab-like interface. Using the tabs you can
navigate through various sub-pages of an object in order to show your network's status, view
monitoring results, or change settings.
Tabs Bar on Sensor Pages
Overview
The Overview tab shows an overview of the currently selected object and of its sensors. The
pages share a common layout, but include different elements, depending on the kind of object
you look at:
For probes and groups, the Overview tab shows a tree-like view with devices and sensors,
a Geo Map, as well as summary graphs for different time spans of the current probe or
group.
For devices, the Overview tab shows device details, a Geo Map, and summary graphs for
different time spans, colored gauges for high priority sensors, as well as a table list of all
sensors on this device. Additionally, you see a table list 155 with Recommended Sensors.
PRTG analyzes the devices which you add to PRTG and shows sensors that give you a much
more detailed picture about your devices when you add them. Click on Add Sensors to add
all recommended sensors of the corresponding table row. Click on Recommend Now to
manually start an analysis.
Note: You can turn off (and disable this table list) the sensor recommendation in Sy st em
Administ rat ionMonit oring 2369 .
Note: To display gauges, you have to tag corresponding sensors with 4 stars (****) or 5
stars (*****) in the priority settings 159 . 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 137
which show correlations in your network.
Gauges represent sensor values on Overview tabs of devices and channel values on
Overview tabs of sensors. They graphically illustrate the current values of a sensor or a
channel so you can use them as a quick status indicator. The red and yellow parts of gauges
correspond to the error and warning limits of the respective sensor channel settings 2220 .
Device overview tabs show gauges of high priority sensors, sensor overview tabs show
gauges of all sensor channels (except the Downt ime channel), the primary channel in
biggest size.
Note: For sensors using lookups 2579 , 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.
124
20.11.2014
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 306 only. Toplist graphs are
displayed right on the sensor overview page. Please see section Toplist s 2240 .
Live Data and Data By x Days

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

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

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

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

<< scrolls one graph window left and >> one window right. The scrolled time depends on
the graph you select, for example, 2 days on a 2 days graph.
< scrolls left on the time axis and > right. The scrolled time depends on the graph you select.
+ zooms into and - out of the graph. The shown time depends on the graph you select. For
example, you can zoom a 30 days graph so that it shows data for 6 days.
x resets the graph to the default view.
In the upper right corner of every graph, you see three small icons:
You can do the following with them:

Zoom graph in new window: Opens a larger version of the graph in a new browser window.
Download t he graph (PNG or SVG): Shows a PNG or SVG file of the graph in a new browser
window. You can then save or copy it for later use.
In every graph, you can also choose which channels (only on sensor pages) resp. indexes you
want to see in specific by using the corresponding check boxes or the Show all and Hide all
buttons.
Historic Data
The Hist oric Dat a tab is available for sensors only. Please see section Hist oric Dat a Report s
133 .
128
20.11.2014
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 155 appearing, you can re-sort the items by clicking on the
column's header items (see section Working wit h Table List s 155 ). Hover to show other menu
options. For detailed information about the available options, please see Main Menu
St ruct ure 179 (Sensors) section.
Alarms
The Alarms tab is not available for sensors, but for probes, groups, and devices only. Please
see section Alarms 143 .
Log
The logs tab shows past activities and events regarding the currently selected object. Please
see section Logs 146 .
Related Topics
Object Set t ings
141
Compare Sensors
130
More
Knowledge Base: How does PRTG compute CPU Index, Traffic Index and Response Time Index?
20.11.2014
129
Part 5: Ajax Web InterfaceBasic Procedures | 6 Compare Sensors
5.6
Compare Sensors
This function allows you to visually compare the graphs of two or more specific sensors. The
selected graphs are shown next to each other so you can have a look at all of them at the
same time.
To open the page to compare graphs of several sensors, from the main menu, choose Sensors
| Compare Sensors. Hover and select how many sensors you want to compare.
PRTG Main Menu: Compare

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

OPTIONS
Time Span
Specify the time span for which you want to show the graphs for.
Choose between:
2 day s
30 day s
365 day s
Dat a Comparison
Select the objects you want to show a graph for. Click on Please click here t o edit ! to open
the Object Select or 158 . There appear as many selection screens as you defined before.
18.11.2014
131
Selec t the Objec ts to be Compared
The graphs are shown immediately after object selection. You can now work with the
compared graphs like on the historic data tabs of sensors 127 : select the channels you want to
show and zoom and scroll in the graphs. Click on Select New Sensor to choose another
sensor for comparison.
Related Topics
If you want to create a sensor that combines the data of different other sensors, please see
the following sensor type:
Sensor Fact ory Sensor
132
1076
18.11.2014
Part 5: Ajax Web InterfaceBasic Procedures | 7 Historic Data Reports
5.7
Historic Data Reports
For quick reporting on monitoring data, use historic data reports as an alternative to the
exhaustive reports 2291 function. You can view a report of the historic data for each single
sensor, on demand. Additionally, you can also export this data and download it to your
computer for further processing in external applications.
There are two possibilities to call the function for historic data reports: Either you click on the
Hist oric Dat a tab on a sensor's detail page, or you choose Sensors | View Hist oric Dat a
from the main menu 179 .
Historic Data (Sensor Tab)

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

When you call historic data reports via the View Hist oric Dat a entry from the Sensors entry in
the main menu, you additionally have to choose the sensor you want to create a report for
with the Object Select or 158 .
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 158 .
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 136 below.
134
18.11.2014
SETTINGS
Channels
Select the channels you want to include in the report. You can
select or deselect single channels with the respective check
boxes, and select or deselect all channels with the buttons Show
all resp. Hide all. PRTG shows only the data of selected data in the
report.
Cluster Node
This field is only visible if the sensor is running on a cluster probe.

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

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

Percentile Results
Select if PRTG shows percentiles in the report. Choose between:

Do not show percent iles: PRTG does not calculate percentiles.
Show percent iles: Enable percentiles in the report. In the
overview table, PRTG displays additional values with averages/
sums for each sensor channel. Define additional settings below.
For more information about percentiles, please see section
Calculat ing Percent iles 2615 .
Percentile
18.11.2014
This field is only visible if you enable percentile results above. Enter
which percentile you want to calculate. Please enter an integer
value.
135
INCLU DE PER CENTILES

Percentile Average
This field is only visible if you enable percentile results above. Enter
the averaging interval in seconds that is used for percentile
calculation. Please enter an integer value.
Percentile Mode
This field is only visible if you enable percentile results above.

Choose between:
Discret e: Chooses the next smaller discrete value.
Cont inuous: Interpolates between discrete values.
See section Calculat ing Percent iles 2615 for more information
about the discrete and continuous modes.
Click on St art to start the generation of a historic data report. Note: Data reporting is limited
to 5 requests per minute.
Automatic Averaging
For performance reasons, PRTG automatically averages monitoring data when calculating data
for large time spans. Data is then averaged regardless of the selected average interval.
TIME SPAN IN R EPOR T
MINIMU M LEVEL OF DETAIL (AVER AGE

INTER VAL)
Up to 40 days
Any
40 to 500 days
60 minutes/1 hour or larger
A report for a time span of more than 500 days is not possible. If you try to set a larger time
span, it will be reduced to 365 days automatically.
Related Topics
Report s
124
2291
More
Knowledge Base: Why is there missing data in historical data reports?
136
18.11.2014
Part 5: Ajax Web InterfaceBasic Procedures | 8 Similar Sensors
5.8
Similar Sensors
With PRTG you can detect relationships between different components in your network. This
function is called similar sensors analysis, a heuristic calculation showing similar behavior of
your sensors. The analysis is completely automated and sensor type agnostic. It is based on
mathematics and fuzzy logic. This feature helps you find interconnections in your network you
were not aware of and optimizes your sensor usage by tracking redundant monitoring of
some aspects of your system.
You can adjust the depth of similar sensors analysis or turn it off in Sy st em Administ rat ion
Monit oring 2368 . You can also switch on and off the similarity analysis for specific probes,
groups, and devices and specify inheritance 88 in the respective object settings 141 , section
Aut omat ic Monit oring Analy sis.
There are two possibilities to view similar sensors:
The overview page of sensors contains a similar sensors section. PRTG lists channels there
which show similarities to channels of the current sensor.
In addition, you can call a similar sensors overview page via Sensors | Similar Sensors
Overview from the main menu 179 .
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.
26.09.2014
137
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 2368 . You see an
according notice in this case.
138
26.09.2014
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 155 .
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.
26.09.2014
139
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.
140
26.09.2014
Part 5: Ajax Web InterfaceBasic Procedures | 9 Object Settings
5.9
Object Settings
Device Tree Management

The Management tab is available when viewing probes or groups. After clicking this tab you
can move devices and sensors right within the tree view. If moving is not possible, the web
interface will start a clone process automatically.
For more information, please see Manage Device Tree
226
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
244
Group Set t ings
228
Neuer Link
95
262
Device Set t ings
284
Sensor Set t ings
304
Note: The available setting options are different for each sensor, but always the same for
probes, groups, and devices. Sensor Channels Set t ings 2220 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
2227
section.
Comments
In the Comment s tab you can enter free text for each object. This can be used for
documentation purposes or to leave information for other users.
18.11.2014
141
Part 5: Ajax Web InterfaceBasic Procedures | 9 Object Settings
History
In the Hist ory tab all changes in the settings of an object are logged with a timestamp, the
PRTG user which conducted the change, and a message. The history log keeps the last 100
entries.
Note: On some pages, you can access the history of subordinate objects via the according
context button in the page header bar 112 . This includes Sy st em Administ rat ion 2357 and the
overview pages of User Account s 2385 , User Groups 2390 , Report s 2291 , Libraries 2275 , and Maps
2311 . See section Logs (Main Menu) 146 for details.
Related Topics
General Lay out
108

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

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

Click the Alarms entry from the main menu 182 to show a table list of all sensors in your
configuration that currently show a Down, Down (Part ial), Down (Acknowledged), Warning,
or Unusual status. You can also show these sensors as gauges. Hover the Alarms entry and
select another option to only show a subset of sensors in certain states. Choose between:
ALAR MS
All
Open a list of all sensors which are currently in Down, Down

(Part ial), Down (Acknowledged), Warning, or Unusual status
121
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 121 )
and will not trigger 2227 any more notifications 2263 . Note: If the alarm condition clears, the sensor
usually returns into an Up status immediately with the next sensor scan.
To acknowledge an alarm, right-click on a sensor and choose Acknowledge Alarm... from the
context menu, enter a message and click the OK button. The message will appear in the last
message value of the sensor. You can choose between: Acknowledge Indefinit ely ...,
acknowledge For 5 Minut es..., For 15 Minut es..., For 1 Hour..., For 3 Hours..., For 1 Day ...,
or Unt il....
If you choose Unt il... a dialog box appears:
ACKNOWLEDGE ALAR M U NTIL

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

alarm. You can acknowledge alarms for more than one sensor
using multi-edit 2248 .
19.09.2014

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 2385 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 2385 , section
Account Cont rol.
More
Knowledge Base: Which audible notifications are available in PRTG? Can I change the default
sound?
19.09.2014
145
Part 5: Ajax Web InterfaceBasic Procedures | 11 Logs
5.11
Logs
The Logs list shows all past activities and events of your PRTG monitoring setup. This is useful
to keep track of all important activities and, for example, to check whether messages were
sent, etc. In a typical setup, a huge amount of data is produced here. As the activity of every
single object is minuted, you can use this data to check exactly if your setup works as
expected.
To support you when viewing the log files, there are several filters available. Please see
Working wit h Table List s 155 section for more information.
List with Log Entries
There are two possibilities to call the logs list: Either you click on the Log tab on the detail
page of a probe, group, device, or sensor, or you choose the Logs entry in the main menu.
Log (Object Tab)

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

Click the Logs entry from the main menu 184 to show a table list of all system log entries in
your configuration. Hover the Logs entry and select another option to only show a subset of
entries for certain objects for certain kind of entries. Choose between:
146
19.09.2014
Part 5: Ajax Web InterfaceBasic Procedures | 11 Logs
LOGS
All
Open a table list 155 with log information for all objects in your
configuration, newest first.
By Group
Open a list with log information for objects in a certain group only,
newest first. Hover to show other menu items. Select All, or follow
the menu path (it is specific to your setup) to select a group you
would like to show log information for.
St at us Changes
Open a list with log information for certain status changes only.
Hover to show other menu items. Follow the menu path to view
log entries with a special value in the St at us field only. Select
between Up & Down (shows entries with either Up or Down in
the St at us field), Down, Warning, Unusual, Up, Paused/Resumed
(shows entries with either Paused or Resumed in the St at us field),
or Acknowledged Alarms.
Sy st em Event s
Open a list with log information regarding certain system event

types only. Hover to show other menu items. Select between the
following event types: Probe Relat ed, Clust er Relat ed, Aut oDiscovery , 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 112 on the corresponding pages.
19.09.2014
147
Part 5: Ajax Web InterfaceBasic Procedures | 12 Tickets
5.12
Tickets
PRTG Network Monitor includes its own ticket system. With tickets you can manage and
maintain various issues which may appear while monitoring a network. A ticket in PRTG
contains information about recent events in your PRTG installation which need a closer look by
the administrator or another responsible person. You can see each ticket as a task for a
particular PRTG user.
Each monitoring related task has a lifecycle in the ticket system. PRTG itself can create tickets,
for example, when Aut o-Discovery 194 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 152 for details and how to turn off
emails about tickets.
List of Tic kets
148
19.09.2014
Note: You can turn off the tickets system for particular user groups in Sy st em Administ rat ion
User Groups 2390 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 152 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
2263
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
2263
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.
19.09.2014
149
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 2390 . 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 175 , hover on Ticket s to show all available filter options or click directly to show all
tickets assigned to the current user. You can also create a new ticket via the main menu.
Available options are:
My Ticket s
Click to show all open tickets which are assigned to the current user. Hover to show other
menu items for filtering these tickets depending on their status:
Open
Resolved
Closed
All
All Ticket s
Click to show all open tickets of all PRTG users. Hover to show other menu items for filtering
these tickets depending on their status:
Open
Resolved
Closed
All
ToDo Ticket s
Click to show all open tickets from the type 149 ToDo. Hover to show other menu items for
filtering these tickets depending on their status:
Open
Click to show all open ToDo tickets. Hover to show other menu items for filtering these
tickets depending on their event type:
Report Relat ed
Aut o-Discovery Relat ed
Probe Relat ed
Sy st em Errors
New Soft ware Version
Resolved
Closed
150
19.09.2014
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 158 . Click on Cont inue. Note: You can leave
this step out when using the context menu 163 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
159
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 155 .
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 158 .
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.
19.09.2014
151
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 95 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 2385 . If you disable
emails for tickets for a user account, this particular user will not receive any ticket emails
anymore.
152
19.09.2014
Note: If you have defined to get tickets as emails and you are PRTG System Administrator, you
will receive emails for ToDo tickets as well, although ToDo tickets are considered to be
opened by the PRTG System Administrator.
More
Paessler Blog: A New Feature Was Assigned to You in PRTG: Ticket System Keeps Track of
Network Monitoring Issues
http://www.paessler.com/blog/2014/02/03/prtg/ticket-system-keeps-track-of-networkmonitoring-issues
Ajax Web InterfaceBasic ProceduresTopics

Login
102
SSL Cert ificat e Warning

General Lay out
Sensor St at es
105
108
121

Compare Sensors
130

Similar Sensors
Object Set t ings
Alarms
Logs
124
133
137
141
143
146
Ticket s
148

Object Select or
158
Priorit y and Favorit es

Pause
159
162
Cont ext Menus

Hover Popup
163
174
Main Menu St ruct ure
19.09.2014
155
175
153

192
2238
Related Topics
Ent erprise Console
2430
154
2482
19.09.2014
Part 5: Ajax Web InterfaceBasic Procedures | 13 Working with Table Lists
5.13
Working with Table Lists
Throughout the web interface often you see table lists of items, for example, sensor or device
lists. Table lists are also available in the overview pages of Libraries 2275 , Maps 2311 , Report s 2291 ,
Not ificat ions 2263 , and Schedules 2353 , as well as in Logs 146 and Ticket s 148 . 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 179 , tickets 150 , and similar sensors 139 , there is
also an inline filter available directly above the table. The filter options depend on the current
page.
Example of a Table List
18.11.2014
155
FE DISPLAY
AT
U
RE
WHAT IT DOES
Pa
gin
g
The content of a table

is displayed on several
pages. Click on the
arrow symbols at the
beginning or the end
of a list to view other
pages, or to jump to
the beginning or the
end of the list.
Ne
w
Wi
nd
ow
Click on 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 on the first
date field for the start
date and on the
second field for the
end date. A calender
dialog opens where
you can particularly
select date and time.
Click on the Done
button to apply the
selected date and
time.
Sel
ect
Ra
ng
e
When viewing log lists

(not available in other
lists), hover 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.
156
Ite
ms
Hover the It ems

option at the
18.11.2014
Related Topics
Mult i-Edit List s
18.11.2014
2248
157
Part 5: Ajax Web InterfaceBasic Procedures | 14 Object Selector
5.14
Object Selector
For some functions, the object selector is shown. It enables you to browse all objects in your
configuration and select an object in two steps.
Objec t Selec tor
Step 1: Navigate Device Tree

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

If you have selected a device on the left hand side, you will see the sensors on this device
here, on the right hand side. Also, the sensor type is shown. Hover a sensor on the right side
to view its parent device and group.
You can also directly search and find sensors by entering its sensor name, group name, device
name, or tag into the Find... box above the sensor list.
Select an object and click on the Save button.
158
19.09.2014
Part 5: Ajax Web InterfaceBasic Procedures | 15 Priority and Favorites
5.15
Priority and Favorites
You can set priorities for all objects in your setup as well as categorize devices or sensors as
favorites. Both settings affect how your objects are displayed.
Note: Settings for priority and favorites are stored for the entire installation; they are not user
specific.
Priority for All Objects

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

To call a list of all your favorite devices or sensors, select Devices | Favorit e Devices or
Sensors | Favorit e Sensors from the main menu. These lists are sorted by priority as well.
You can mark any device or sensor as favorite to add it to the favorite list. Right click on it to
open the context menu 163 . Select Priorit y /Favorit e | Add t o Favorit es. A small black flag
symbol will be added next to the object's name.
18.11.2014
159
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 163 .
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
160
18.11.2014
Priority and Favorites in the Page Header Bar

You can add any device or sensor to favorites on its respective details page by clicking on the
small flag symbol in the page header bar 112 . 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
18.11.2014
161
Part 5: Ajax Web InterfaceBasic Procedures | 16 Pause
5.16
Pause
While a sensor is paused, it will not collect any monitoring data, will not change its status 121 ,
and will not trigger any notifications 93 . You can pause monitoring for every object by
selecting Pause from the context menu 163 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 2248 , the object(s) will be paused indefinitely until resumed.
174
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;
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 2353 ) in the Object Set t ings 141 .
Inheritance and Resume

If you pause monitoring for an object in the device tree 108 , 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 163 . 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.
162
19.09.2014
Part 5: Ajax Web InterfaceBasic Procedures | 17 Context Menus
5.17
Context Menus
Right-click on an object to view a context menu with many options for direct access to
monitoring data and functions. You can also access many of the functionalities via the main
menu 175 or the hover popup 174 window. However, using the context menus is the easier way
in most cases.
Note: In order 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 your browser's 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
163
Group Cont ext Menu
166
Device Cont ext Menu
168
Sensor Cont ext Menu
171
Probe Context Menu
Probe Context Menu
Check Now
This will perform an immediate scan for the selected probe. The data for all devices and
sensors in the object hierarchy 83 underneath will be queried.
Det ails...
This will show the details of the selected probe, such as its status, the groups on the
selected probe, and an overview about the sensor states on the selected probe.
20.11.2014
163
Edit
The edit menu will appear.
Context Menu Edit
Edit Set t ings...

This will open the Probe Set t ings
Edit Not ificat ions...
This will open the Not ificat ions
244
2263
tab.
tab.
Edit Access Right s...

This will open a popup to edit access rights
95 .
Edit Rename...
This will open a popup to edit the name of the selected probe.
Edit Management ...
This will open the management
226
tab.
Add Group...
This will 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 209 .
Add Aut o-Discovery Group...
This will open an assistant which guides you through the process of adding a new autodiscovery group to your setup. PRTG will create a new group and run an auto-discovery in
your network in order to add devices and sensors for these devices automatically. For more
information, please see section Using t he Aut o-Discovery 194 .
Add Device...
This will open an assistant which guides you through adding a new device to the selected
probe. For detailed instructions, please see Add a Device 215 .
Sort Alphabet ically
This will sort direct children (groups and devices) of the selected probe in alphabetical order.
The ordering will be stored in the monitoring configuration and cannot be revoked.
Delet e...
This will delete the selected probe. You will be asked for confirmation before anything is
actually deleted.
Move
The move menu will appear.
164
20.11.2014
Context Menu Mov e
This will move the selected probe. Choose between

Move Top: This will move the probe to the top of the mother node (here the root
group).
Move Up: This will move the probe one entry up under the root group.
Move Down: This will move the probe one entry down under the root group.
Move Bot t om: This will move the probe to the bottom of the root group.
Move Management ...: This will open the management
226
tab.
Pause
The pause menu will appear.
Context Menu Pause
If the probe is already in a paused state, Resume will appear in the context menu instead
of Pause .
Context Menu Paused
You can pause and resume monitoring on the selected probe. The monitoring for all
sensors in the object hierarchy 83 underneath will be paused resp. resumed. You can
choose between: Pause Indefinit ely ..., pause For 5 Minut es..., For 15 Minut es..., For 1
Hour..., For 3 Hours..., For 1 Day ..., or Pause Unt il.... If you choose Pause Unt il... a
popup window will appear where you can define a date. Monitoring will be resumed after
this date.
You can directly add a One-t ime maint enance window to pause monitoring during a
planned downtime. In the appearing window, use the date time picker to enter the start
date and time of the maintenance window, as well as the end time, for the selected object.
20.11.2014
165
Priorit y
The priority menu will appear.
Context Menu Priority
Define the priority of the selected probe. For details, please see Priorit y and Favorit es
159 .
Hist oric Dat a
The historic data menu will appear.
Context Menu Historic

Data
Depending on what time interval you choose, Last 2 day s..., Last 30 day s..., or Last 365
day s..., the Hist oric Dat a Report s 133 tab for the specified interval will be opened.
Hist oric Dat a Creat e Report ... will open an assistant to add a report. For details, please
see Report s St ep by St ep 2295 .
Send Link by email
You can send the link to the selected probe by email. This will open a new email using your
system's standard email client. It will contain a direct link to the selected probe's details
page.
Open Ticket
This will open the New Ticket dialog. For details, see section Ticket s
151
Group Context Menu

Note: The context menu of the Root group is special and differs from the other groups' menu.
Check Now
This will perform an immediate scan for the selected group. The data for all devices and
sensors in the object hierarchy 83 underneath will be queried.
Det ails...
This will show the details of the selected group, such as its status, the devices on the
selected group, and an overview about the sensor states on the selected group.
Edit
166
20.11.2014
Set t ings...
This will open the Group Set t ings
Not ificat ions...
262
2263
tab.
tab.
Access Right s...

95 .
Rename...
This will open a popup to edit the name of the selected group.
Management ...
This will open the management
226
tab.
Add Group...
This will open an assistant which guides you through the process of adding a new group to
the selected group. For detailed instructions, please see Add a Group 209 .
Add Aut o-Discovery Group...
This will open an assistant which guides you through the process of adding a new autodiscovery group to your setup. PRTG will create a new group and run an auto-discovery in
your network in order to add devices and sensors for these devices automatically. For more
information, please see section Using t he Aut o-Discovery 194 .
Add Device...
This will open an assistant which guides you through adding a new device to the selected
group. For detailed instructions, please see Add a Device 215 .
Run Aut o-Discovery
If you select this option, an automatic search is started, adding new sensors to the selected
group. The search is running in the background. If found, you will see new sensors after a
few minutes automatically. For more information, please see Aut o-Discovery 195 (Run Aut oDiscovery Now).
This will sort direct children (devices and other groups) of the selected group in alphabetical
order. The ordering will be stored in the monitoring configuration and cannot be revoked.
Delet e...
This will delete the selected group. You will be asked for confirmation before anything is
actually deleted.
Clone
This will open an assistant which guides you through cloning the selected group. For
detailed instructions, please see Clone Object 2246 .
Move
The move menu will appear.
This will move the selected group. Choose between:
Move Top: This will move the group to the top of the mother node (here usually a
probe or another group).
Move Up: This will move the group one entry up under the mother node.
Move Down: This will move the group one entry down under the mother node.
Move Bot t om: This will move the group to the bottom of the mother node.
20.11.2014
167
Move To Ot her Group: This will move the group to another group. An assistant
will appear in this case with information about the selected group and the subobjects which also will be moved. Please choose a target group from the list.
Move Management ...: This will open the management
226
tab.
Pause
The pause menu will appear.
If the group is already in a paused state, Resume will appear in the context menu instead
of Pause .
You can pause and resume monitoring on the selected group. The monitoring for all
this date.
planned downtime. In the appearing window, use the date time picker to enter the start
date and time of the maintenance window, as well as the end time, for the selected object.
Priorit y
The priority menu will appear. Define the priority of the selected group. For details, please
see Priorit y and Favorit es 159 .
Hist oric Dat a
Depending on what time interval you choose, Last 2 day s..., Last 30 day s..., or Last 365
day s..., the Hist oric Dat a Report s 133 tab for the specified interval will be opened.
Hist oric Dat a Creat e Report ... will open an assistant to add a report. For details, please
see Report s St ep by St ep 2295 .
Send Link by email
You can send the link to the selected group by email. This will open a new email using your
page.
Open Ticket
151
Device Context Menu

Check Now
This will perform an immediate scan for the selected device. The data for all sensors in the
object hierarchy 83 underneath will be queried.
Det ails...
This will show the details of the selected device, such as its status and the sensor states on
the selected device.
Edit
168
20.11.2014
Set t ings...
This will open the Device Set t ings
284
Not ificat ions...

tab.
2263
tab.
Access Right s...

95 .
Rename...
This will open a popup to edit the name of the selected device.
Add Sensor...
This will open an assistant which guides you through adding a new sensor to the selected
device. For detailed instructions, please see Add a Sensor 224 .
Run Aut o-Discovery
If you select this option, an automatic search is started, adding new sensors to the selected
device. The search is running in the background. If found, you will see new sensors after a
few minutes automatically. For more information, please see Aut o-Discovery 195 (Run Aut oDiscovery Now).
Creat e Device Templat e...
This will open an assistant which guides you through creating a new device template; this will
then be available in auto-discovery 194 . For detailed instructions, please see Creat e Device
Templat e 2253 .
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 124 where you can add the according sensor types directly.
Note: This option is only available if the recommendation engine is enabled 2369 .
This will sort direct children (sensors) of the selected device in alphabetical order. The
ordering will be stored in the monitoring configuration and cannot be revoked.
Delet e...
This will delete the selected device. You will be asked for confirmation before anything is
actually deleted.
Clone
This will open an assistant which guides you through cloning the selected device. For
Move
The move menu will appear. This will move the selected device. Choose between:
Move Top: This will move the device to the top of the mother node (here usually a
group or a probe).
Move Up: This will move the device one entry up under the mother node.
Move Down: This will move the device one entry down under the mother node.
Move Bot t om: This will move the device to the bottom of the mother node.
20.11.2014
169
Move To Ot her Group: This will move the device to another group. An assistant
will appear in this case with information about the selected device and the subobjects which also will be moved. Please choose a target group from the list.
Pause
The pause menu will appear. If the device is already in a paused state, Resume will appear in
the context menu instead of Pause .
You can pause and resume monitoring on the selected device. The monitoring for all
this date.
planned downtime. In the appearing window, use the date time picker to enter the start date
and time of the maintenance window, as well as the end time, for the selected object.
Priorit y /Favorit e
The priority/favorite menu will appear. Define the priority of the selected device, or add resp.
remove the device to resp. from the favorites. For details, please see Priorit y and
Favorit es 159 .
Hist oric Dat a
Depending on what time interval you choose, Last 2 day s..., Last 30 day s..., or Last
365 day s..., the Hist oric Dat a Report s 133 tab for the specified interval will be opened.
Hist oric Dat a Creat e Report ... will open an assistant to add a report. For details,
please see Report s St ep by St ep 2295 .
Device Tools
The device tools menu will appear.
Context Menu Dev ic e Tools
Go To Service URL...
This will open the service page you have defined in the Device Set t ings
284
New window wit h HTTP...

This will open a new browser window with Hypertext Transfer Protocol (HTTP) and the IP
address / DNS name of the device.
170
20.11.2014
New window wit h HTTPS...

This will 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...
This will open a new browser window with File Transfer Protocol (FTP) and the IP address /
DNS name of the device.
Remot e Deskt op...
This will download a .rdp file. When you execute the file remote desktop will start with the
IP address / DNS name of the device. Note: In Firefox you have to use mstsc.exe
(Microsoft Terminal Service) to open the file.
Tracerout e...
This will 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...
This will 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 2592 .
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
You can send the link to the selected device by email. This will open a new email using your
page.
Open Ticket
151
Sensor Context Menu

Check Now
This will perform an immediate scan for the selected sensor.
Det ails...
This will show the details of the selected sensor, such as its status and channels.
Edit
Set t ings...
This will open the Sensor Set t ings
304
Not ificat ions...

tab.
2263
tab.
Access Right s...

95 .
Rename...
This will open a popup to edit the name of the selected device.
Acknowledge Alarm
This option is available only in the sensor context menu when a sensor in a Down or Down
(Part ial) status is selected.
20.11.2014
171
Context Menu Ac knowledge Alarm
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 121 ) and will not trigger
2227 any more notifications 2263 . 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 popup window will appear where you can
define a date. 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 will usually return into
an Up status immediately with the next sensor scan. For details about acknowledging an
alarm, please see Alarms 144 section.
Delet e...
This will delete the selected sensor. You will be asked for confirmation before anything is
actually deleted.
Clone
This will open an assistant which guides you through cloning the selected sensor. For
Move
The move menu will appear. This will move the selected sensor. Choose between:
Move Top: This will move the sensor to the top of the mother node (here a
device).
Move Up: This will move the sensor one entry up under the device.
Move Down: This will move the sensor one entry down under the device.
Move Bot t om: This will move the sensor to the bottom of the device.
Pause
The pause menu will appear. If the sensor is already in a paused state, Resume will appear in
the context menu instead of Pause .
172
20.11.2014
You can pause and resume monitoring on the selected sensor. 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... a popup
window will appear where you can define a date. Monitoring will be resumed after this
date.
planned downtime. In the appearing window, use the date time picker to enter the start date
and time of the maintenance window, as well as the end time, for the selected object.
Simulat e Error St at us
This will set the selected sensor to a simulated error state. As for the paused state, Resume
will appear in the context menu if a the selected sensor is already in a simulated error state.
The priority/feature menu will appear.
Define the priority of the selected sensor. For details, please see Priorit y and Favorit es
159 .
Hist oric Dat a
Opens the historic data tab for the specified interval
30 day s..., or Last 365 day s...
Compare... opens the Compare Sensors
sensor.
130
127
: Live Dat a, Last 2 day s..., Last
assistant with the currently selected
View Hist oric Dat a... opens the Hist oric Dat a
133
tab of this sensor.
Creat e Report ... opens an assistant to add a report. For details, please see Report s
St ep by St ep 2295 .
Send Link by email
You can send the link to the selected sensor by email. This will open a new email using your
page.
Open Ticket
20.11.2014
151
173
Part 5: Ajax Web InterfaceBasic Procedures | 18 Hover Popup
5.18
Hover Popup
Whenever you rest the mouse pointer for a second over an object's icon in the device tree 108 ,
a hover popup window will appear, showing details about this object. It contains information
from the object's overview tab 124 , as well as several graphs. The exact information provided
depends on the kind of object you are hovering.
Hov er Menu Example: VMware Virtual Mac hine Sensor
Note: The hover popup does only appear if your browser is the currently focused window on
your desktop. It disappears with every (automatic) page refresh.
Menu Icons
At the top of the hover popup window, several icons are shown which enable you to view or
edit the current object. These are the most important options from this object's context menu
163 which is shown when right-clicking it.
174
19.09.2014
Part 5: Ajax Web InterfaceBasic Procedures | 19 Main Menu Structure
5.19
Main Menu Structure
You can access all functions of PRTG using the main menu. In this section, you find descriptions
about the most important menu items. Often, you can either click on an item directly, or hover
it to show more items.
PRTG Main Menu Bar
The following menu items are available:
Home
175
Devices
177
Libraries
179
Sensors
179
Alarms
Maps
182
183
Reports
Logs
184
184
Tickets
Setup
185
186
Refresh (Arrows Symbol)

Help Center (? Symbol)
Logout (Off Symbol)
Search Box
188
189
189
189
Home
Click to open the user's homepage. The default setting is the PRTG welcome page 108 . You can
change the homepage in the user account settings 2329 . Hover to show other menu items.
18.11.2014
175
PRTG Main Menu: Home
HOME
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: Dashboards are not customizable. You can create your own
overview pages using the Maps 2311 feature.
Swit ch Clust er Node This option is only available if PRTG runs in Clust ering 81 mode.
Show available cluster nodes. Hover to show other menu items.
Follow the menu path (it is specific to your setup) to select
another cluster node. The current Master node is shown in bold
letters. Click on a node's name to leave the current node and
connect to the other, showing the same page there.
Sit emap
Open the sitemap which contains a flat text view of all menu items.
You can easily search for key words using the search function in
your browser (usually shortcut CTRL-F).
Go t o Mobile Web GUI Switch to the Mobile Web GUI 2483 which is optimized for low
bandwidth and mobile devices. This interface uses less scripting for
more compatibility.
Note: This is a read-only interface for most parts of PRTG.
Welcome t o PRTG
Open the welcome screen 108 that shows the Paessler news feed
and provides quick links to the major sections of the web
interface.
Configurat ion Guru
Open the Configurat ion Guru welcome page. For details about
the guru, please see section Using t he Configurat ion Guru 36 .
176
18.11.2014
HOME
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 2329
settings.
Devices
Click to show a group view of all your devices, starting with the Root group which contains all
other groups of your setup. Hover to show other menu items.
PRTG Main Menu: Dev ic es
DEVICES
All
Open the Overview tab of the Root 84 group that shows a group
view of all your devices (the device tree).
Group View
Open a tree view of all probes and groups in your setup. Click to
show a group view of all your devices, starting with the Root 84
group which contains all other groups of your setup. Hover to
show other menu items. Follow the menu path (it is specific to
your setup) to view the devices in a specific probe or group only.
Device List
Open a list view of all devices in your setup. Click to show a table
list of all devices in your setup. Hover to show other menu items.
Choose Favorit e Devices to show a list of all devices marked as
Favorit e 159 . 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.
18.11.2014
177
DEVICES
Note: In the table list 155 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 159 . 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 91 configured for the

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

a new group to your setup. For more information, please see
section Creat e Object s Manually 208 .
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 194
Note: You can create new groups much faster by choosing Add
Aut o-Discovery Group... from a probe's or group's context menu.
178
18.11.2014
DEVICES
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 208 .
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 2275 section.
Hover to show other menu items.
PRTG Main Menu: Libraries
LIBR AR IES
All
Open the Libraries overview list where you can view or add custom
device tree views of your network status and monitoring data.
Add Library
Open an assistant to directly create
Select Library
Open an existing library. Hover to show other menu items. Follow

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

a new sensor to an existing device. For more information, please
see section Add a Sensor 224 . During the process, you can also
choose to create a new device via the Add a Device 215 assistant
(that you can also open from the "Devices" menu 177 directly).
Favorit e Sensors
Open a table list of all sensors which you marked as Favorit e
159
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.
180
18.11.2014
SENSOR S
Top 10 List s
Open a dashboard view with different top 10 lists which show

best/worst uptime, Ping, bandwidth usage, website response
times, CPU usage, disk usage, memory usage, and system uptime.
Click to show top 10 lists for all sensors. Hover to show other
menu items. Follow the menu path (it is specific to your setup) to
view top 10 lists for a specific probe or group only.
Note: The shown sensors are selected by default tags.
By Current Value
Open a list of sensors filtered by value. Hover to show other menu

items. Follow the menu path to view table lists 155 of Fast est or
Slowest sensors for
Ping
Port
Webpages
IMAP/POP3/SMTP
FTP
as well as a list of sensors with Most Used or Least Used
Bandwidt h
CPU
Disk
Memory
Note: The shown sensors are selected by default tags.
By Current St at us
Open a list of sensors filtered by status. Hover to show other

menu items. Follow the menu path to view table lists 2201 of all
sensors in a certain status. For more information about sensor
states, please see Sensor St at es 121 section.
By Upt ime/Downt ime
Open a list of sensors filtered by different parameters. Hover to

show other menu items. Follow the menu path to view table lists
155 of all sensors sorted by
Best Upt ime (%)
Highest Upt ime (Time)
Worst Downt ime (%)
Highest Downt ime (Time)
18.11.2014
181
SENSOR S
By Group
Open a list of sensors filtered by their parent group. Hover to

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

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

menu items. Follow the alphabetical menu path (it is specific to
your setup) to see available tags. Select a tag view a table list 155
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 159 , scanning interval
238 , access rights 95 , notification trigger settings 141 , schedule 92 ,
and dependency 91 . Click to show a sensor cross reference for all
sensors. Hover to show other menu items. Follow the menu path
(it is specific to your setup) to view cross reference information for
sensors in a specific probe or group only, or to view them by type
or tag.
Compare Sensors
Compare the data graphs of two or more sensors. Hover to show

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

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

information, please see Similar Sensors 137 section.
Alarms
Click to show a all sensors that currently show a Down, Down (Part ial), Warning, or Unusual
status. In the table list 155 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 124 in a
size corresponding to their priority. Hover to show other menu items.
182
18.11.2014
PRTG Main Menu: Alarms
ALAR MS
All

(Part ial), Down (Acknowledged), Warning, or Unusual status
121
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.
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 2311 section. Hover
to show other menu items.
PRTG Main Menu: Maps
18.11.2014
183
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 to show other menu items. Follow

the menu path (it is specific to your setup) to select a map.
2314
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 2291 section. Hover to show other
menu items.
PRTG Main Menu: Reports
R EPOR TS
All
Open the Reports overview page where you can view or add
reports of your monitoring data.
Add Report
Select Report
Open an existing report. Hover to show other menu items. Follow

the menu path (it is specific to your setup) to select a report.
Configurat ion
Report s
Create reports for maps, reports, user and user groups, and
system configuration to document changes to the configuration.
Hover to see the available configuration reports 2294 .
2295
a new report.
Logs
Click to show log information for all objects in your configuration, newest first. In the table list
155 appearing, you can filter the items by using the respective options 155 . Hover to show
other menu items. For more information, please see Logs 146 section.
184
18.11.2014
PRTG Main Menu: Logs
LOGS
All
Open a table list 155 with log information for all objects in your
configuration, newest first.
By Group
Open a list with log information for objects in a certain group only,
newest first. Hover to show other menu items. Select All, or follow
the menu path (it is specific to your setup) to select a group you
would like to show log information for.
St at us Changes
Open a list with log information for certain status changes only.
Hover to show other menu items. Follow the menu path to view
log entries with a special value in the St at us field only. Select
between Up & Down (shows entries with either Up or Down in
the St at us field), Down, Warning, Unusual, Up, Paused/Resumed
(shows entries with either Paused or Resumed in the St at us field),
or Acknowledged Alarms.
Sy st em Event s
Open a list with log information regarding certain system event

types only. Hover to show other menu items. Select between the
following event types: Probe Relat ed, Clust er Relat ed, Aut oDiscovery , 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 112 on the corresponding pages.
Tickets
Click to show all tickets which are assigned to the current user. In the table list 155 appearing,
you can re-sort the items by clicking on the column's header items, as well as you can filter the
list with the inline filter directly above the table. Hover to show other menu items.
18.11.2014
185
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 148 .
PRTG Main Menu: Tic kets
You have several options to display a list of tickets which is filtered to your needs. You can
also create a new ticket via the main menu.
TICKETS
All
Open a list of all open tickets which are assigned to the current
user.
My Ticket s
Open a list of all open tickets which are assigned to the current
user. Hover to show other menu items for filtering these tickets
depending on their status.
All Ticket s
Open a list of all open tickets of all PRTG users. Hover to show
other menu items for filtering these tickets depending on their
status.
ToDo Ticket s
Open a list of open tickets from the type ToDo. Hover to show
other menu items for filtering these tickets depending on their
status.
Open Ticket
Open the New Ticket dialog. Provide the needed information and
confirm by clicking on Save to create a User Ticket . For more
information about available options, please refer to section
Ticket s 148 .
Setup
Click to show the setup page. Hover to show other menu items. For more information, please
see Set up 2327 section.
186
18.11.2014
PRTG Main Menu: Setup
SETU P
Overview
Open the setup page
Account Set t ings
Open the My Account 2329 settings. Hover to show and open the
tabs of account settings directly. Choose from:
My Account
2327
2329
Not ificat ions
2334
Not ificat ion Cont act s

Schedules
Sy st em
Administ rat ion
2353
Open the Sy st em Administ rat ion 2357 settings. Hover to show and
open the tabs of the system administration settings directly.
Choose from:
User Int erface
Monit oring
2357
2367
Not ificat ion Delivery

Core & Probes
Clust er
User Groups
2379
2385
2390
Administ rat ive Tools
18.11.2014
2372
2394
User Account s
PRTG St at us
2349
2396
Open the PRTG St at usSy st em St at us 2401 page. When running a

cluster, hover to show other menu items. Choose from:
Sy st em St at us
2401
Clust er St at us
2416
187
SETU P
License
Open the license act ivat ion st at us

other menu items. Choose from:
St at us
2418
2418
page. Hover to show
to view information about your license.
Ent er License Key 2419 to enter your license name and key and
to show your licensed PRTG edition.
Aut o-Updat e
Open information about the Soft ware Aut o-Updat e 2411 status of
your PRTG installation. On this page, you can also download and
install available updates. Hover to show other menu items. Choose
from:
St at us 2411 to view the update status and to manually check for
the latest update.
Set t ings
2413
to define your update settings.
Downloads / Add-Ons Open the downloads page
Choose from:
2421
of PRTG for additional downloads.
Client App for Windows (Ent erprise Console)

Client Apps for Mobile Devices
Remot e Probe Inst aller
PRTG Add-Ons
2421
2421
2421
2421
PRTG Billing Tool
2422
Deskt op Not ificat ions
2423
PRTG API
Open the documentation of the Applicat ion Programming

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

Paessler 2425 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.
188
18.11.2014
Help Center (? Symbol)
PRTG Main Menu: Help Button
Open the Help and Support Cent er to get help if you have any questions regarding your
PRTG setup.
Logout (Off Symbol)
PRTG Main Menu: Logout Button
Log out the current user and return to the login screen
102
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.
18.11.2014
163
available for all objects. Right-click on an object to
189
Part 6
Ajax Web InterfaceDevice and Sensor Setup
19.09.2014
191
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
194
Creat e Object s Manually

Manage Device Tree
Root Group Set t ings
Probe Set t ings
208
226
228
244
Group Set t ings
262
Device Set t ings
284
Sensor Set t ings
304
List of Available Sensor Ty pes
Addit ional Sensor Ty pes (Cust om Sensors)

Sensor Channels Set t ings
2217
2220
Sensor Not ificat ions Set t ings
192
305
2227
19.09.2014
Part 6: Ajax Web InterfaceDevice and Sensor Setup |

Ajax Web Int erfaceBasic Procedures
100
2238
Related Topics
Ent erprise Console
2430
19.09.2014
2482
193
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 1 Auto-Discovery
6.1
Auto-Discovery
PRTG's auto-discovery function is a great way to automatically create a sophisticated and

concise set of sensors for your complete network. It is mainly suitable for LAN discovery since
it involves a lot of SNMP and WMI. For video instructions, please see the More 207 section
below.
For a quick start auto-discovery, please see TWOUsing t he Configurat ion Guru
36
section.
How Auto-Discovery Works

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

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

There are several ways to start auto-discovery:
On the welcome screen
108
, click on the Perform Net work Aut o-Discovery option,
or select Devices | Add Aut o-Discovery Group from the main menu.
To start an automatic detection of devices and sensors in your network an assistant will
appear, leading you through two steps. For faster setup, you can select Add Aut o-Discovery
Group... in the context menu 163 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.
19.09.2014
195
Add Auto-Disc ov ery Group Dialog
St ep 1
Please choose a probe or group you want to add the new group to. Click on Cont inue.
St ep 2
Add auto-discovery settings as described below.
Add Auto-Discovery Group Settings

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

shown by default in the devices tree and in all alarms.
Tags
Enter one or more tags; confirm each tag by hitting the space,
comma, or enter key. You can use tags to group objects and use
tag-filtered views later on. Tags are not case sensitive. Tags are
automatically inherited 90 .
196
19.09.2014
GR OU P TYPE
Sensor Management
Select the method for automatic network discovery. Choose

between:
Aut omat ic device ident ificat ion (st andard, recommended):
Detect mainly based on Ping, SNMP, and WMI. This option should
work fine for most installations.
Aut omat ic device ident ificat ion (det ailed, may creat e many
sensors): Detect in a more detailed way and create more
sensors. This option uses all standard device templates for 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 using specific device templates (last

option) is enabled above. Please choose one or more templates by
adding a check mark in front of the respective template name. You
can also select and deselect all items by using the check box in the
table head. These will be used for auto-discovery on the current
device. Choose from:
ADSL
Cisco ASA VPN
Cisco Device (Generic)
Dell MDI Disk
DNS Server
Environment Jacart a
Environment Poseidon
Frit zbox
FTP Server
Generic Device (PING only )
Generic Device (SNMP-enabled)
Generic Device (SNMP-enabled, Det ailed)
HTTP Web Server
Hy per V Host Server
Linux/UNIX Device (SNMP or SSH enabled)
Mail Server (Generic)
19.09.2014
197
Mail Server (MS Exchange)

Microsoft Sharepoint 2010
NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
NTP Server
Print er (HP)
RDP Server
RMON compat ible device
Server (Compaq/HP agent s)
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
Swit ch (Cisco Cat aly st )
Swit ch (Cisco IOS Based)
Swit ch (HP Procurve)
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
VMware ESX / vCent er Server
Windows (Det ailed via WMI)
Windows (via Remot e Powershell)
Windows (via WMI)
Windows IIS (via SNMP)
X EN Host s
X EN Virt ual Machines
Once the auto-discovery is finished, PRTG will create a new ticket
148 and list the device templates which were actually used to
create new sensors. Templates which were not applied will not be
shown in the ticket.
Discovery Schedule
198
Define when the auto-discovery will be run. Choose between:
19.09.2014
Once: Perform auto-discovery only once. New devices and

sensors will be added once. You can run auto-discovery manually
any time using an object's context menu 163 .
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 2370 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 2382 .
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
19.09.2014
This field is only visible if Class C network detection is selected

above. Enter a class C network as IP base for the auto-discovery.
Enter the first three octets of an IPv4 IP address, for example,
192.168.0
199
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 the IP list option is selected 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 the IP and subnet option is selected

above. Enter an expression in the format address/subnet , e.g.
192.168.3.0/255.255.255.0. You can also use the short form like
192.168.3.0/24 in this example. PRTG will scan the complete host
range (without network and broadcast address) defined by the IP
address and the subnet mask.
IP with Octet Range
This field is only visible if the octet range option is selected above.
Enter an expression in the format a1.a2.a3.a4, where a1, a2, a3,
and a4 are each a number between 0-255, or a range with two
numbers and a hyphen like 1-127. All permutations of all ranges are
calculated, e.g. 10.0.1-10.1-100 results in 1,000 addresses that
PRTG will scan during auto-discovery.
Organizational Unit
This field is only visible if active directory is selected above. Enter

an organizational unit (OU) to restrict the active directory search to
computers which are part of this OU. Just enter the name of the OU
without any other term (i.e., without "OU" in front). If you leave this
field empty, there will not be any restriction.
If you have sub-OUs, consider the correct syntax in the format
Y,OU=X : OUs that are part of another OU have to be listed
together with their parent(s). Enter the sub-OU followed by ,OU=
and the name of the parent OU.
Examples:
Assuming that the organizational unit 'Y' is part of the OU named
'X'. Then the syntax would be Y,OU=X.
For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would
be Z,OU=Y,OU=X.
Note: The order is important, sub-OUs have to be listed left of their
particular parents!
200
19.09.2014
Name Resolution
Define how newly discovered devices will be monitored. This only

affects new devices. The setting for existing devices will be kept.
Choose between:
Use DNS / WMI / SNMP names (recommended): Monitor newly
discovered devices via their DNS, WMI, or SNMP names (if
available).
Use IP addresses: Monitor newly discovered devices via their IP
address.
We recommend using the default value.
Device Rescan
Define if you want to rescan known devices. Choose between:

Skip aut o-discovery for known devices/IPs (recommended):
Do not re-scan known devices or IP addresses, but only scan for
new devices/IPs when auto-discovering. This can avoid recreation of manually deleted sensors. PRTG will also avoid adding
devices that are already included elsewhere in your
configuration, e.g. in other groups.
Perform aut o-discovery for known devices/IPs: Re-scan
known devices and IP addresses with every auto-discovery. This
will re-create manually deleted sensors on existing devices.
Inherited Settings
By default, all following settings are inherited from objects higher in the hierarchy and should
be changed there, if necessary. Often, best practice is to change them centrally in the Root 228
group's settings. To change a setting for this object, disable inheritance by clicking on the
check mark symbol in front of the respective setting name. You will then see the options
described below.
If you have not set credentials yet, set them now before starting the auto-discovery in order
to fully exploit the power of this feature!
CR EDENTIALS FOR WINDOWS SYSTEMS

Domain or Computer
Name
19.09.2014
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.
201

Username
Enter the username for Windows access. Usually, you will use
credentials with administrator privileges.
Password
Enter the password for Windows access. Usually, you will use
CR EDENTIALS FOR LINU X/SOLAR IS/MAC OS (SSH/WBEM) SYSTEMS

Username
Enter a login name for the access via SSH and WBEM. Usually, you
will use credentials with administrator privileges.
Login
Define which authentication method will be used for login. Choose

between:
Login via Password: Provide a password for login. Enter below.
Login via Privat e Key : Provide a private key for authentication.
Note: PRTG can only handle keys in OpenSSH format which are
not encrypted. You cannot use password protected keys here.
In the text field, please paste the entire private key, including the
"BEGIN" and "END" lines. Please make sure the according public
key is provided on the target machine. For details, please see
Monit oring via SSH 2498 .
Password
This field is only visible if password login is selected above. Enter a

password for the Linux access via SSH and WBEM. Usually, you will
use credentials with administrator privileges.
Private Key
This field is only visible if private key login is selected above. Paste
a private key into the field (OpenSSH format, unencrypted). Usually,
you will use credentials with administrator privileges. Note: If you
do not insert a private key for the first time, but change the private
key, you need to restart your PRTG core server service in order for
the private key change to take effect! For details, please see
For WBEM Use Protocol Define the protocol that will be used for WBEM. This setting is only
relevant when using WBEM sensors. Choose between:
HTTP: Use an unencrypted connection for WBEM.
HTTPS: Use an SSL-encrypted connection for WBEM.
For WBEM Use Port
202
Define the port that will be used for WBEM. This setting is only
19.09.2014

Set aut omat ically (port 5988 or 5989): Use one of the
standard ports, depending on whether unencrypted or
encrypted connection is chosen above.
Set manually : Use a custom port. Define below.
WBEM Port
This setting is only visible if manual port selection is enabled

above. Enter the WBEM port number.
SSH Port
Define the port number which will be used for SSH connections.
Note: By default, this setting is automatically used for all SSH
sensors 310 , unless you define a different port number in the
sensor settings.
SSH Rights Elevation
Define with which rights the command will be executed on the

target system. Choose between:
Run t he command as t he user connect ing (default ): Use the
rights of the user who establishes the SSH connection.
Run t he command as anot her user using 'sudo': Use the rights
of another user, for example, the administrator.
Run t he command as anot her user using 'su': Use the rights of
another target user.
Target Username
This field is only visible if sudo or su is enabled above. Enter a

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

for the specified target user.
CR EDENTIALS FOR VMWAR E/XENSER VER

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

19.09.2014
203

VMware Protocol
Define the protocol used for the connection to VMware and

XenServer. Choose between:
HTTPS (recommended): Use an SSL-encrypted connection to
VMware and XenServers.
HTTP: Use an unencrypted connection to VMware and
XenServers.
CR EDENTIALS FOR SNMP DEVICES

SNMP Version
Select the SNMP version that will be used for device connection.
Choose between:
v1: Use the simple standard v1 protocol for SNMP connections.
This protocol only offers clear-text data transmission, but it is
usually supported by all devices.
v2c: Use the more advanced v2c protocol for SNMP
connections. Data is still transferred as clear-text, but it supports
64-bit counters.
v3: Use the latest v3 protocol for SNMP connections. It provides
secure authentication and data encryption.
Note for SNMP v3: Due to internal limitations you can only monitor
a limited number of sensors per second using SNMP v3. The limit is
somewhere between 1 and 50 sensors per second (depending on
the SNMP latency of your network). This means that using an
interval of 60 seconds you are limited to between 60 and 3000
SNMP v3 sensors for each probe. If you experience an increased
"Interval Delay" or "Open Requests" reading of the probe health
sensor, you need to distribute the load over multiple probes. SNMP
v1 and v2 do not have this limitation.
Community String
This setting is only visible if SNMP version v1 or v2c are enabled

above. Enter the community string of your devices. This is a kind of
"clear-text password" used for simple authentication. We
recommend using the default value.
Authentication Type
This setting is only visible if SNMP version v3 is enabled above.

Choose between:
MD5: Use Message-Digest Algorithm 5 (MD5) for authentication.
SHA: Use Secure Hash Algorithm (SHA) for authentication.
The chosen type has to match the authentication type of your
device.
204
19.09.2014

Note: If you do not want to use authentication, but you need SNMP
v3, for example, because your device requires context, you can
leave the field password empty. In this case,
SNMP_SEC_LEVEL_NOAUTH will be used and authentication will be
deactivated entirely.
User

Enter a username for secure authentication. This value has to
match the username of your device.
Password

Enter a password for secure authentication. This value has to
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.
The chosen type has to 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 will be encrypted using the encryption
algorithm selected above, providing increased security. The
provided key here has to match the encryption key of your
device. Note: If the key entered in this field does not match the
key configured in the target SNMP device, you will not get an error
message! Please enter a string or leave the field empty.
Context Name

Enter a context name only if it is required by the configuration of
the device. Context is a collection of management information
accessible by an SNMP device. Please enter a string.
SNMP Port
Enter the port used for SNMP communication. We recommend

using the default value.
SNMP Timeout (sec.)
Enter a timeout in seconds for the request. If the reply takes

longer than this value the request is aborted and an error message
is triggered.
19.09.2014
205
PR OXY SETTINGS FOR HTTP SENSOR S

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

URL. You can enter data for a proxy server that will be used when
connecting via HTTP or HTTPS. Note: This setting is valid for the
monitoring only and determines the behavior of sensors. In order
to change proxy settings for the core server, please see Sy st em
Name
Enter the IP address or DNS name of the proxy server to use. If

you leave this field empty, no proxy will be used.
Port
Enter the port number of the proxy. Often, port 8080 is used.
Please enter an integer value.
User
If the proxy requires authentication, enter the username for the

proxy login. Note: Only basic authentication is available! Please
enter a string or leave the field empty.
Password
If the proxy requires authentication, enter the password for the

ACCESS R IGHTS
User Group Access
Define which user group(s) will have access to the object you're
editing. A table with user groups and right is shown; it contains all
user groups from your setup. For each user group you can choose
from the following access rights:
Inherit ed: Use the settings of the parent object.
None: Users in this group cannot see or edit the object. The
object does not show up in lists.
Read: Users in this group can see the object and review its
settings.
Writ e: Users in this group can see the object, as well as review
and edit its settings. However, they cannot edit access rights
settings.
Full: Users in this group can see the object, as well as review
and edit its settings and edit access rights settings.
You can create new user groups in the Sy st em Administ rat ion
User Groups 2390 settings.
Click on the Cont inue button to store your settings. If you change tabs or use the main menu,
all changes to the settings will be lost!
206
19.09.2014
Auto-Discovery in Progress
While auto-discovery is running you may experience a lower system performance as usual,
because PRTG works in the background in order to discover your network. Depending on the
IP ranges defined (up to 65,536 addresses) , the discovery may run up to several days before
complete. You can review the status of the discovery process as follows:
In the device tree, behind the group or device name, you will see a percentage value
showing the progress of auto-discovery.
During auto-discovery, the web interface will display a box in the lower right corner, showing
the number of active auto-discovery tasks.
In order to stop a running auto-discovery, right-click the group or device, and select Pause |
For 5 minut es... from the context menu 163 . Monitoring will be paused for 5 minutes, and
auto-discovery tasks will be shut down.
Related Topics
Creat e Device Templat e
2253
More
Knowledge Base: Why can automatic auto-discoveries evoke performance issues?

19.09.2014
207
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 2 Create Objects Manually
6.2
Create Objects Manually
We recommend using the auto-discovery 194 function to create a basic monitoring setup for
your network. Afterwards, you can manually create devices that could not be discovered, or
arrange 2245 detected devices in groups.
The procedure depends on the kind of object you want to add. Choose between:
Add a Group
209
Add a Device
215
Add a Sensor
224
Add a Remote Probe

Please see Mult iple Probes and Remot e Probes
208
2588
section for more information.
19.09.2014
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 163 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,
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
19.09.2014
209
1 Add a Group

Domain or Computer
Name
Username
Password

Username
Login

between:
Password

Private Key
210
19.09.2014
1 Add a Group

For WBEM Use Port
WBEM Port

SSH Port
sensor settings.

Target Username


19.09.2014
211
1 Add a Group

User
Password

VMware Protocol

XenServers.

SNMP Version
Choose between:
64-bit counters.
Community String
212

19.09.2014
1 Add a Group

Authentication Type

Choose between:
device.
User

Password

Encryption Type

algorithm.
algorithm.
Data Encryption Key

Context Name

SNMP Port

19.09.2014
213
1 Add a Group

SNMP Timeout (sec.)

is triggered.
ACCESS R IGHTS
User Group Access
settings.
settings.
214
19.09.2014
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 163 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.
19.09.2014
215
2 Add a Device
DEVICE NAME AND ADDR ESS

device.
IP Address/DNS Name
Enter the IP address (either v4 or v6, depending on your selection

above) or DNS name for the device. Most sensors created on this
device will inherit this setting and they will try to connect to this
address for monitoring. Note: There are some sensor types that
still have their own setting for IP address/DNS name. Those
sensors will use their own settings.
Tags
Enter one or more tags; confirm each tag by hitting space, comma,
or enter key. You can use tags to group sensors and use 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.
Hourly : Perform auto-discovery for new sensors every hour.
216
19.09.2014
2 Add a Device
DEVICE TYPE
Daily : Perform auto-discovery for new sensors every day.
Weekly : Perform auto-discovery for new sensors every week.
Device Template(s)

ADSL
Cisco ASA VPN
Dell MDI Disk
DNS Server
Frit zbox
FTP Server
HTTP Web Server
NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
NTP Server
Print er (HP)
19.09.2014
217
2 Add a Device
DEVICE TYPE
RDP Server
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
Windows (via WMI)
X EN Host s
218
19.09.2014
2 Add a Device

Domain or Computer
Name
Username
Password

Username
Login

between:
Password

Private Key
19.09.2014
219
2 Add a Device

For WBEM Use Port
WBEM Port

SSH Port
sensor settings.

Target Username


220
19.09.2014
2 Add a Device

User
Password

VMware Protocol

XenServers.

SNMP Version
Choose between:
64-bit counters.
Community String
19.09.2014

221
2 Add a Device

Authentication Type

Choose between:
device.
User

Password

Encryption Type

algorithm.
algorithm.
Data Encryption Key

Context Name

SNMP Port

222
19.09.2014
2 Add a Device

SNMP Timeout (sec.)

is triggered.
ACCESS R IGHTS
User Group Access
object does not show up in lists and in the device tree.
Exception: If a child object is visible to the user, the object is
visible in the device tree, though not accessible.
monitoring results.
Writ e: Users in this group can see the object, review its
monitoring results, and edit the object's settings. They cannot
edit access rights settings.
Full: Users in this group can see the object, review its
monitoring results, edit the object's settings, and edit access
rights settings.
User Groups 2390 settings. To automatically set all objects further
down in the hierarchy to inherit this object's access rights, set a
check mark for the Revert children's access right s t o inherit ed
option.
For more details about access rights, please see section User
Access Right s 95 .
19.09.2014
223
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 163 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
224
19.09.2014
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 305 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?
19.09.2014
225
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 141 and resume 162 monitoring.
Note: You cannot clone 'fixed' objects, such as the root group or a probe device. You cannot
clone the sensor types QoS (Qualit y of Service) One Way Sensor 1020 and QoS (Qualit y of
Service) Round Trip Sensor 1027 .
Note: In order to clone entire groups or devices, please use the Clone Object
accessible via the objects' Context Menu 163 .
2246
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.
226
19.09.2014
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 would like to edit, change the according
values and click on Save. The changes will be applied to all selected objects.
The dialog is the same as described in the Mult i-Edit
2250
(Edit Settings) section.
Related Topics
For other ways to arrange objects, please see
Arrange Object s
2245

Clone Object
19.09.2014
2253
2246
227
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.
228
19.09.2014
LOCATION
Location (for geo
maps)
When using geo maps using Google's API 2258 please enter a
location in the first line. Objects will then be displayed on a
geographical map with a flag, showing the current status using a
color code similar to the sensor status icons 121 (green - yellow orange - red). You can enter a full postal address, city and country
only, or latitude and longitude. It is possible to enter any text
before, between, and after the coordinates, PRTG will parse latitude
and longitude automatically; for example: 49.452778 11.077778 or
enter 49.452778 any 11.077778 text
A minus sign (-) in the first line will hide an object from geo maps. In
this case you can enter location information in line two and
following.
You can define a specific label for each location: enter a string
denoting the label in the first line and provide geo coordinates in
the second line. This object will be displayed then with the label in
PRTG's geo map.

Domain or Computer
Name
Username
Password

Username
19.09.2014
229

Login

between:
Password

Private Key
For WBEM Use Port
WBEM Port

SSH Port
sensor settings.
230
19.09.2014


Target Username



User
Password

VMware Protocol

XenServers.

SNMP Version
19.09.2014
231

Choose between:
64-bit counters.
Community String

Authentication Type

Choose between:
device.
User

Password

232
19.09.2014

Encryption Type

algorithm.
algorithm.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (sec.)

is triggered.
WINDOWS COMPATIBILITY OPTIONS

When experiencing problems while monitoring via Windows sensors, you can set some
compatibility options for trouble shooting.
Preferred Data Source
19.09.2014
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:
233

Performance Count ers and fallback t o WMI (recommended):
Try to query data via performance counters. If this is not
possible, establish a connection via WMI. This is the
recommended setting to best balance resource usage and
functionality.
Performance Count ers only : Query data via performance
counters only. If this is not possible, a sensor will return no data.
WMI only : Query data via WMI only. If this is not possible, a
sensor will return no data.
Timeout Method
Specify the time the sensor will wait for the return of its WMI query
before aborting it with an error message. Choose between:
Use 1.5x scanning int erval (recommended): Use a default of
one and a half times the scanning interval set for the sensor (see
below in this settings).
Set manually : Enter a timeout value manually.
We recommend using the default value. Only if you experience
ongoing timeout errors, try increasing the timeout value.
Timeout Value (Sec.)
This field is only visible if the manual timeout method is selected

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

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

requests. This can help increase device compatibility. Please enter
an integer value. We recommend using the default value. If you
experience SNMP connection failures, please increase it. You can
define a delay between 0 and 100, higher delays are not supported
and will be discarded.
Failed Requests
Define if an SNMP sensor will try again after a request fails.

Ret ry (recommended): Try again if an SNMP request fails. This
can help prevent false error messages due to temporary timeout
failures.
234
19.09.2014

Do not ret ry : Do not retry if an SNMP request fails. With this
setting enabled an SNMP sensor will be set to error status
earlier.
Overflow Values
Define how PRTG will handle overflow values. Some devices do not
handle internal buffer overflows correctly. This can cause false
peaks.
Ignore overflow values (recommended): Ignore overflow
values and do not include them in the monitoring data.
Handle overflow values as valid result s: Regard all overflow
values as regular data and include them in the monitoring data.
We recommend using the default value. If you experience
problems, change this option.
Zero Values
Define how PRTG will handle zero values. Some devices send
incorrect zero values. This can cause false peaks.
Ignore zero values for delt a sensors (recommended): Ignore
zero values and do not include them in the monitoring data.
Handle zero values as valid result s for delt a sensors: Regard
all zero values as regular data and include them in the monitoring
data.
32-bit/64-bit Counters
Define which kind of traffic counters PRTG will search for on a

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

Port Name Template
Define how the name of SNMP sensors created on a device will be

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

Port Identification
Define which field will be used for SNMP interface identification.

Choose between:
Aut omat ic (recommended): Tries the ifAlias field first to identify
an SNMP interface and then ifDescr. Note: ifName will not be tried
automatically.
Use ifAlias: For most devices ifAlias is the best field to get
unique interface names.
Use ifDescr: Use this option if the port order of your device
changes after a reboot, and there is no ifAlias field available. For
example, this is the best option for Cisco ASA devices. Note:
When using this option it is important that your device returns
unique interface names in the ifDescr field.
Use ifName: You can also use this option if there is no unique
ifAlias available. Note: When using this option it is important that
your device returns unique interface names in the ifName field.
No Port Updat e: Use this option to disable automatic port
identification.
Start Port
For SNMP Traffic sensors, define at which port number PRTG will
start to create sensors. Use 0 for automatic. We recommend using
the default value.
End Port
stop to create sensors. Use 0 for automatic. We recommend using
the default value.
SNMP Debug Log
Define if you want to create an SNMP log file for debugging

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

HTTP Proxy Settings

Name

Port
User

Password

238
19.09.2014
SCANNING INTER VAL

Scanning Interval
The scanning interval determines the time the sensor waits

between two scans. Select a scanning interval (seconds, minutes,
or hours) from the list. You can change the available intervals in
the system administration 2367 .
When a Sensor
Reports an Error
With this setting, you can define the number of scanning intervals a
sensor has to report an error until the sensor will be set to a
Down status. The sensor can try reaching a device several times,
depending on your setup you can specify here, to help avoid false
alarms if the monitored device has only temporary issues. For
previous scanning intervals with failed requests, the sensor will
show a Warning status. Choose between:
Set sensor t o "down" immediat ely : The sensor will show an
error after the first failed request.
Set sensor t o "warning" for 1 int erval, t hen set t o
"down" (recommended): After the first failed request, the
sensor will show a yellow warning status. If the following
request also fails, the sensor will show an error.
Set sensor t o "warning" for 2 int ervals, t hen set t o "down":
The sensor will only show an error status after three failed
requests in a row.
The sensor will only show an error status after four failed
requests in a row.
The sensor will only show an error status after five failed
requests in a row.
The sensor will only show an error status after six failed
requests in a row.
Note: Sensors that monitor via Windows Management
Instrumentation (WMI) will always wait at least one scanning interval
until an error is shown. 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.
19.09.2014
239
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 2334 . 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 284 , and Sensor Settings 304 .
240
244
, Group Settings
262
, Device
19.09.2014
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
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.
19.09.2014
241
AU TOMATIC MONITOR ING DATA ANALYSIS

Unusual Detection
Define if unusual detection is enabled for sensors. You can

configure the behavior of unusual detection (or disable it
completely) in the system settings 2367 .
Enabled: Enable unusual detection for this group. Sensors in this
group will turn to orange color if unusual activity is detected.
Disabled: Disable unusual detection for this group. Unusual
values will be ignored for sensors in this group; they will not
show an unusual sensor status.
Similar Sensors
Detection
Define if similar sensors detection is enabled for sensors. You can

configure the depth of analysis of similar sensors detection (or
disable it completely) in the system settings 2368 .
Enabled: Enable similar sensors detection for this group.
Sensors in this group will be considered during similarity analysis.
Disabled: Disable similar detection for this group. Sensors in this
group will not be taken into account during similarity analysis.
Click on the Save button to store your settings. If you change tabs or use the main menu, all
changes to the settings will be lost!
Notifications
The status or the data of a sensor can trigger notifications. Using this mechanism, you can
configure external alerting tailored to you needs. In an object's detail page, click on the
Not ificat ions tab to change sensor notification triggers. The defined triggers will be inherited
down to sensor level. For detailed information, please see Sensor Not ificat ions Set t ings 2227
section.
Others
For more general information about settings, please see Object Set t ings
141
section.
More
Knowledge Base: How can I add my own device icons for use in the PRTG web interface?
242
19.09.2014
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
19.09.2014
243
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
2588
section for more details.
Probe Settings
The following settings are available in the Set t ings tab of every probe. As you may not need
all of these for every probe, just regard those settings you really need, ignoring the others.
We recommend defining as many settings as possible in the Root
them to all other objects further down in the tree hierarchy.
228
group, so you can inherit
BASIC PR OBE SETTINGS

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

Tags
or enter key. You can use tags to group objects and use 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
244
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).
19.09.2014
Inherited Settings
described below.
LOCATION
Location (for geo
maps)
enter 49.452778 any 11.077778 text
following.
PRTG's geo map.

Domain or Computer
Name
Username
Password
19.09.2014
245

Username
Login

between:
Password

Private Key
For WBEM Use Port
WBEM Port
246

19.09.2014

SSH Port
sensor settings.

Target Username



User
Password

VMware Protocol

XenServers.
19.09.2014
247

SNMP Version
Choose between:
64-bit counters.
Community String

Authentication Type

Choose between:
device.
User

Password

248
19.09.2014

Encryption Type

algorithm.
algorithm.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (sec.)

is triggered.

19.09.2014
Choose between:
249

functionality.
Timeout Method

integer value.

SNMP Delay (ms)

Failed Requests

failures.
250
19.09.2014

earlier.
Overflow Values
peaks.
Zero Values
data.

device.
Request Mode
into one request.
19.09.2014
251

Port Name Template

among which are:
interface.
bandwidth (KBit/s).
names.
Port Name Update
252
19.09.2014

Port Identification

Choose between:
automatically.
identification.
Start Port
the default value.
End Port
the default value.
SNMP Debug Log

19.09.2014
253

HTTP Proxy Settings

Name

Port
User

Password

254
19.09.2014
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
255
CLU STER U SAGE

Scanning Distribution
This box is only visible if you're running a PRTG cluster. Sometimes

you want to exclude a certain node from monitoring the sensors
running on this probe, group, or device, for example, if a device is
not reachable from every node configured in your cluster. In the
list of cluster nodes, please select the nodes that will not be
included in sensor scans. By default, this setting is inherited 88 to
all objects underneath.

Note: Inheritance for schedules, dependencies, and maintenance windows cannot be
interrupted; the according settings from the parent objects will always be active. However,
you can define additional settings here. They will be active in parallel to the parent objects'
settings.
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:
256
19.09.2014

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 2256 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 158
to choose an object on which the current object will be
dependent on.
Delay (Seconds)
Define a time span. After the master object for this dependency
comes back to an Up status, monitoring of the depending objects
will be additionally delayed by the defined time span. This can help
avoid false alarms, for example, after a server restart, by giving
systems more time for all services to start up. Please enter an
integer value in seconds.
19.09.2014
257
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
258
19.09.2014

Unusual Detection

Similar Sensors
Detection

ADMINISTR ATIVE PR OBE SETTINGS / PR OBE SETTINGS FOR MONITOR ING

Define the IP address used for outgoing monitoring requests.
If there is more than one IP on the current system available, you can specify the IP address
that will be used for outgoing monitoring requests of certain sensor types.
The setting is valid for all monitoring requests sent from this PRTG probe.
This setting will be used for sensors using the following connection types: HTTP, DNS, FTP,
IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. Note: This feature does not support
all sensor types for technical reasons.
This is useful for devices that expect a certain IP address when queried.
Default setting is aut o. PRTG will select an IP address automatically.
Note: If you change this setting, some sensors might stop working. For example, sensors
might show a Down status if the selected IP address is blocked on the way to or directly on
the monitored device.
Outgoing IPv4
19.09.2014
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.
259

Outgoing IPv6

system. Choose a specific IP address or select aut o. For details
about the basic concept of IPv6 in PRTG, please see IPv6 98
section.
ADMINISTR ATIVE PR OBE SETTINGS: SCHEDU LED R ESTAR TS

Restart Options
For best performance, we recommend you to regularly restart the

Windows servers on which PRTG is running. To do this
automatically for PRTG, you can schedule an automatic restart.
Choose between the following options:
Do not perform scheduled reboot /service rest art : Do not
perform any scheduled restart of services automatically. We
recommend a manual restart every few weeks. You can initiate a
restart of your PRTG core server and probes under Sy st em 2396
Administ rat ionAdminist rat ive Tools 2396 in the PRTG web
interface.
Perform scheduled rest art of PRTG services: Restart both
core server and probe service. Enter a schedule below.
Perform scheduled sy st em reboot (recommended): This is the
recommended setting, although not set by default. Enter a
schedule below. We recommend restarting Windows servers
once a month for best performance.
Restart Schedule
This setting is only visible if you selected a schedule option above.

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

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.
260
19.09.2014
ADMINISTR ATIVE PR OBE SETTINGS: SCHEDU LED R ESTAR TS

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!
Notifications
section.
Others
141
section.
More
SNMP sensors?
19.09.2014
261
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.
228
Group Name

Status
Choose if monitoring for this group is started or paused. .We

recommend using the default value. You can add additional tags to
it, if you like.
St art ed: Monitor this group.
Paused: Pause monitoring for this group. All sensors on all
devices in this group will be paused until this setting is changed
again.
Tags
262
or enter key. You can use tags to group objects and use tagfiltered views later on. Tags are not case sensitive.
19.09.2014
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:
device.
Device Template(s)

ADSL
Cisco ASA VPN
Dell MDI Disk
DNS Server
Frit zbox
19.09.2014
263
FTP Server
HTTP Web Server
NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
NTP Server
Print er (HP)
RDP Server
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
Windows (via WMI)
264
19.09.2014

X EN Host s
Discovery Schedule
Define when the auto-discovery will be run. Choose between:

Once: Perform auto-discovery only once. New devices and
sensors will be added once. You can run auto-discovery manually
any time using an object's context menu 163 .
Hourly : Perform auto-discovery for new devices and sensors
every 60 minutes. Note: Please use this option with caution!
Frequently executed auto-discoveries might cause performance
issues, especially when large network segments are scanned
every hour.
Daily : Perform auto-discovery for new devices and sensors
every 24 hours. The first auto-discovery will run immediately, all
Weekly : Perform auto-discovery for new devices and sensors
every 7 days. The first auto-discovery will run immediately, all
IP Selection Method
Define how you want to define the IP range for auto-discovery.

Choose between:
Class C base IP wit h st art /end (IPv4): Define an IPv4 class C
address range.
IP and Subnet (IPv4): Enter an IPv4 address and subnet mask.
IP wit h oct et range (IPv4): Enter an IPv4 address range for every
IP octet individually. With this, you can define very customizable
IP ranges.
19.09.2014
265
Use comput ers from t he act ive direct ory (maximum 1000
comput ers): Search in the active directory for computers to
perform auto-discovery. Note: Define your active directory
domain in advance in the system administration. See Sy st em
Note: Only subnets with up to 65,536 IP addresses can be
discovered! If you define a range with a higher number of
addresses, discovery will stop before it is completed.
IPv4 Base

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 the IP list option is selected 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 the IP and subnet option is selected

above. Enter an expression in the format address/subnet , e.g.
192.168.3.0/255.255.255.0. You can also use the short form like
192.168.3.0/24 in this example. PRTG will scan the complete host
range (without network and broadcast address) defined by the IP
address and the subnet mask.
IP with Octet Range
This field is only visible if the octet range option is selected above.
Enter an expression in the format a1.a2.a3.a4, where a1, a2, a3,
and a4 are each a number between 0-255, or a range with two
numbers and a hyphen like 1-127. All permutations of all ranges are
calculated, e.g. 10.0.1-10.1-100 results in 1,000 addresses that
PRTG will scan during auto-discovery.
Organizational Unit
This field is only visible if active directory is selected above. Enter

an organizational unit (OU) to restrict the active directory search to
computers which are part of this OU. Just enter the name of the OU
without any other term (i.e., without "OU" in front). If you leave this
field empty, there will not be any restriction.
266
19.09.2014
If you have sub-OUs, consider the correct syntax in the format

Y,OU=X : OUs that are part of another OU have to be listed
together with their parent(s). Enter the sub-OU followed by ,OU=
and the name of the parent OU.
Examples:
Assuming that the organizational unit 'Y' is part of the OU named
'X'. Then the syntax would be Y,OU=X.
For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would
be Z,OU=Y,OU=X.
Note: The order is important, sub-OUs have to be listed left of their
particular parents!
Name Resolution
Define how newly discovered devices will be monitored. This only

affects new devices. The setting for existing devices will be kept.
Choose between:
Use DNS / WMI / SNMP names (recommended): Monitor newly
discovered devices via their DNS, WMI, or SNMP names (if
available).
Use IP addresses: Monitor newly discovered devices via their IP
address.
Device Rescan
Define if you want to rescan known devices. Choose between:

Skip aut o-discovery for known devices/IPs (recommended):
Do not re-scan known devices or IP addresses, but only scan for
new devices/IPs when auto-discovering. This can avoid recreation of manually deleted sensors. PRTG will also avoid adding
devices that are already included elsewhere in your
configuration, e.g. in other groups.
Perform aut o-discovery for known devices/IPs: Re-scan
known devices and IP addresses with every auto-discovery. This
will re-create manually deleted sensors on existing devices.
Inherited Settings
described below.
19.09.2014
267
LOCATION
Location (for geo
maps)
enter 49.452778 any 11.077778 text
following.
PRTG's geo map.

Domain or Computer
Name
Username
Password

Username
268
19.09.2014

Login

between:
Password

Private Key
For WBEM Use Port
WBEM Port

SSH Port
sensor settings.
19.09.2014
269


Target Username



User
Password

VMware Protocol

XenServers.

SNMP Version
270
19.09.2014

Choose between:
64-bit counters.
Community String

Authentication Type

Choose between:
device.
User

Password

19.09.2014
271

Encryption Type

algorithm.
algorithm.
Data Encryption Key

Context Name

SNMP Port

SNMP Timeout (sec.)

is triggered.

272
Choose between:
19.09.2014

functionality.
Timeout Method

integer value.

SNMP Delay (ms)

Failed Requests

failures.
19.09.2014
273

earlier.
Overflow Values
peaks.
Zero Values
data.

device.
Request Mode
into one request.
274
19.09.2014

Port Name Template

among which are:
interface.
bandwidth (KBit/s).
names.
Port Name Update
19.09.2014
275

Port Identification

Choose between:
automatically.
identification.
Start Port
the default value.
End Port
the default value.
SNMP Debug Log

276
19.09.2014

HTTP Proxy Settings

Name

Port
User

Password

19.09.2014
277
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
278
19.09.2014
CLU STER U SAGE



settings.
Schedule

active.
Maintenance Window

between:
be set.

maintenance window.
Maintenance Ends At

maintenance window.
Dependency Type

can choose between:
19.09.2014
279

menu bar.
Dependency
dependent on.
Delay (Seconds)
280
19.09.2014
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
281

Unusual Detection

Similar Sensors
Detection

NU MBER OF SENSOR S LIMITATION

Sensor Limit
This setting allows the administrator to set a limit for the maximum
number of sensors in this group. Subgroups are also included. If
sensors exceed this limitation, they will be paused. This is of
special interest for a Managed Service Provider (MSP). Choose
between:
Allow unlimit ed number of sensors: Disable a limitation of the
number of sensors for this group. Any number of sensors can be
added to this group.
Limit number of sensors in t his group: Enables a limitation of
the number of sensors for this group. Only a limited number of
sensors can be added to this group.
Maximum Number of
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.
282
19.09.2014
Notifications
section.
Others
141
section.
More
SNMP sensors?
19.09.2014
283
Part 6: Ajax Web InterfaceDevice and Sensor Setup | 7 Device Settings
6.7
Device Settings
On a device's details page, click on the Set t ings tab to change settings.
Add Device
The Add Device dialog appears when adding a new device to a group. It only shows the
setting fields that are imperative for creating the device. Therefore, you will not see all setting
fields in this dialog. For example, the Device St at us option is not available in this step.
You can change all settings in the device's Set t ings tab later.
Device Settings
The following settings are available in the Set t ings tab of every device. As you may not need
all of these for every device, just regard those settings you really need, ignoring the others.
228
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 2248 section.
BASIC DEVICE SETTINGS

Device Name
Enter a meaningful name to identify the device. The name will be

Status
Choose if monitoring for this device is started or paused.

St art ed: Monitor this device.
Paused: Pause monitoring for this device. All sensors on it will be
paused until this setting is changed again.
IP Version
Define which IP protocol PRTG will use to connect to this device.

The setting is valid for all sensors created on this device. Choose
between:
device.
device.
284
19.09.2014
BASIC DEVICE SETTINGS

IP Address/DNS Name
Enter the IP address (either v4 or v6, depending on your selection

above) or DNS name for the device. Most sensors created on this
device will inherit this setting and they will try to connect to this
address for monitoring. (However, some sensor types still have
their own setting for IP address/DNS name.)
Tags
or enter key. You can use tags to group sensors and use tagfiltered views later on. Tags are not case sensitive. We recommend
using the default value. You can add additional tags to it, if you like.
Priority
Select a priority for the sensor. This setting determines where the
sensor will be placed in sensor lists. Top priority will be at the top
of a list. You can choose from one star (low priority) to five stars
(top priority).
ADDITIONAL DEVICE INFOR MATION

Device Icon
Choose a device icon from the list. It will be shown in the device
tree. For information on how to add your custom icons, please see
the link in the More 302 section below.
Service URL
Specify a URL you would like to open directly when choosing

Device Tools | Go To Service URL from the device's context menu
168 . For example, you can configure this option to call the address
http://www.example.com/service.html. Enter a valid URL or leave
the field empty.
DEVICE TYPE
Sensor Management

this device. Choose between:
device.
19.09.2014
285
DEVICE TYPE
Discovery Schedule
This option is only visible if one of the auto-discovery options is

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

ADSL
Cisco ASA VPN
Dell MDI Disk
DNS Server
Frit zbox
FTP Server
HTTP Web Server
286
19.09.2014
DEVICE TYPE
NAS LenovoEMC
NAS QNAP
NAS Sy nology
Net App
NTP Server
Print er (HP)
RDP Server
Server (Dell)
Sever Cisco UCS
Server IBM
SonicWALL
UNIX /Linux Device
UPS (APC)
Virt uozzo Server
Windows (via WMI)
X EN Host s
19.09.2014
287
DEVICE TYPE
Inherited Settings
described below.
LOCATION
Location (for geo
maps)
enter 49.452778 any 11.077778 text
following.
PRTG's geo map.
288
19.09.2014

Domain or Computer
Name
Username
Password

Username
Login

between:
Password

Private Key
19.09.2014
289

For WBEM Use Port
WBEM Port

SSH Port
sensor settings.

Target Username


290
19.09.2014

User
Password

VMware Protocol

XenServers.

SNMP Version
Choose between:
64-bit counters.
Community String
19.09.2014

291

Authentication Type

Choose between:
device.
User

Password

Encryption Type

algorithm.
algorithm.
Data Encryption Key

Context Name

SNMP Port

292
19.09.2014

SNMP Timeout (sec.)

is triggered.

Choose between:
functionality.
Timeout Method
19.09.2014

integer value.
293

SNMP Delay (ms)

Failed Requests

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

device.
294
19.09.2014

Request Mode
into one request.
Port Name Template

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

names.
Port Name Update
Port Identification

Choose between:
automatically.
identification.
Start Port
the default value.
End Port
the default value.
SNMP Debug Log

296
19.09.2014


HTTP Proxy Settings

Name

Port
User

Password

19.09.2014
297
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
298
19.09.2014
CLU STER U SAGE



settings.
Schedule

active.
Maintenance Window

between:
be set.

maintenance window.
Maintenance Ends At

maintenance window.
Dependency Type

can choose between:
19.09.2014
299

menu bar.
Dependency
dependent on.
Delay (Seconds)
300
19.09.2014
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
301

Unusual Detection

Similar Sensors
Detection

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

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

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

2217
2220
304
305
2227
19.09.2014

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 224 assistant, PRTG offers you various options to filter for
fitting sensor types easily.
Common Sensors
305
Bandwidth Monitoring Sensors

Web Servers (HTTP) Sensors
SNMP Sensors
306
306
307
Windows WMI/Performance Counters Sensors

Linux/Unix/OS X Sensors
Virtual Servers Sensors
Mail Servers Sensors
310
311
311
Database Servers Sensors

File Servers Sensors
312
312
Various Servers Sensors

VoIP and QoS Sensors
313
313
Hardware Parameters Sensors

Custom Sensors
314
315
PRTG Internal Sensors
316
All Sensors in Alphabetical Order

More
309
316
322
Common Sensors
HTTP Sensor
553
Ping Sensor
948
Port Sensor
986
Port Range Sensor
994
SNMP Traffic Sensor
1611
1753
18.11.2014
1901
305

Bandwidth Monitoring Sensors

IPFIX Sensor
350
741

jFlow V5 Sensor
751
770

NetFlow V5 Sensor
780
846

NetFlow V9 Sensor
856
865

875
907

sFlow Sensor
916
1094
1103
1169

SNMP Library Sensor
1183
1412

SNMP RMON Sensor
SNMP Traffic Sensor
1503
1557
1611
1901
Web Servers (HTTP) Sensors

HTTP Sensor
545
553
562

HTTP Content Sensor
584
593

604
613
620
306
575
629
18.11.2014


638
647

659
1753
1867
SNMP Sensors
1161
1169

1183
1191
1198

1205
1213
1221

SNMP Custom Sensor
1176
1229
1236
1243
1252
1262
1270

1286

1294
1301
1309
1317

1325
1333
1341
1349
1357
18.11.2014
1278
307

1365

1381
1389
1397

SNMP Library Sensor
1405
1412
1423

SNMP Memory Sensor
1433
1440
1447
1455
1463
1471
1480
1487
1495

1511
1518
SNMP Printer Sensor
1533
1541
1549
1557

1572
1580
1596
1604
1611
1621

308
1565
1588
SNMP Traffic Sensor
1503
1526
SNMP RMON Sensor
1373
1632
18.11.2014

Windows WMI/Performance Counters Sensors

432
932
940
1851
1859
Windows IIS Application Pool Sensor

323
940
1843

1884

1892
1901
1909

1935
1943
1917
1926

1952
1961

WMI Custom Sensor
1986
1996
2006
2015
2024

WMI Memory Sensor
2032
2043
2052
2060
2068
2080
18.11.2014
1969
1977
WMI File Sensor
1876
309


2113

WMI Service Sensor
WMI Share Sensor
2091
2121
2129
2138
2147
2155

WMI UTC Time Sensor
2169

WMI Volume Sensor
2162
2176
2184

2201
2209
Linux/Unix/OS X Sensors
1423

1440

1656
1664
1672

SSH Script Sensor
1680
1724

1734
1688

1697
1706

WBEM Custom Sensor
310
1447
1645
SSH Meminfo Sensor
1433
1715
1835
18.11.2014

Virtual Servers Sensors

341
365

373
423

681
688

SCVMM Host Sensor
672
697
706
1058

1067
1744
1790
1797
1803

1810
1818
1826
Mail Servers Sensors

442

450
459
467

IMAP Sensor
714

POP3 Sensor
733
969

SMTP Sensor
977
1134

18.11.2014
475
1142
1151
311

1753
2006

2015
1851
1859
Database Servers Sensors

ADO SQL Sensor
332
795
804

MySQL Sensor
817
824
MySQL v2 Sensor
833
Oracle SQL Sensor
884

PostgreSQL Sensor
894
1001
2068
2080
2091
2102
File Servers Sensors

391

File Sensor
504
File Content Sensor

Folder Sensor
FTP Sensor
512
520
528
536
726

1112
1119
312
399
1463
18.11.2014


1471
1480
1487

TFTP Sensor
1503
1511
1776
WMI File Sensor
2024

WMI Volume Sensor
2032
2184
Various Servers Sensors

DHCP Sensor
DNS Sensor
408
416

LDAP Sensor
Ping Sensor
789
948
Ping Jitter Sensor

Pingdom Sensor
Port Sensor
761
956
963
986
Port Range Sensor

RADIUS Sensor
994
1035
RADIUS v2 Sensor
1042

SNTP Sensor
1051
1621
1639
1760
1753
1783
VoIP and QoS Sensors

Cisco IP SLA Sensor
358
1126
18.11.2014
1020
313


1027
1198
Hardware Parameter Sensors

391

423
1161

1205
1213
1221

399
1229
1236
1262
1270

1278
1286

1294
1301
1309

1325
1333
1341
1349
1365

1405
1412
SNMP Memory Sensor
1455
1480
314
1381
1397

SNMP Library Sensor
1373
1471
18.11.2014

1495

1511
1541
1549

1588
1596
1688
1697
1706

1565
1572

1503
1715
2043
Custom Sensors
EXE/Script Sensor
483

494
751
780
856
875

Pingdom Sensor
963
1076

SNMP Custom Sensor
1103
1243

SSH Script Sensor
1252
1724
WBEM Custom Sensor

WMI Custom Sensor
1835
1977
18.11.2014
916
1986
315

PRTG Internal Sensors

ClusterState Sensor
Core Health Sensor
381
385
Probe Health Sensor
1014
1771
All Sensors in Alphabetical Order

The version numbers show when the respective sensor type was originally introduced to
PRTG.
ADO SQL Sensor
332
341
(v7)

Cisco IP SLA Sensor
358
365
381
385
(v9.1.0)
(v9.1.0)
416
(v7)
423
(v13.x.6)
432
(v7)
(v13.x.5)
442
450
459
EXE/Script Sensor
467
475
(v13.x.5)
494
(v7)
(v7)
File Content Sensor
316
(v13.x.5)
(v7)
483
Folder Sensor
(v13.x.5)
(v13.x.5)
504
(v14.x.13)
399
(v8.2.0)
File Sensor
(v12.x.1)
391
DNS Sensor
(v8.1.0)
373
408
(v14.x.13)
(v12.x.1)

ClusterState Sensor
350
(v7)
DHCP Sensor
(v8.3.0)
(v8.1.0)
Core Health Sensor
323
520
512
(v7)
(v7)
18.11.2014

FTP Sensor
(v7)
528

HTTP Sensor
(v8.3.0)
536
(v12.x.1)
545
(v7)
553
(v7)
562
575
(v12.x.3)
HTTP Content Sensor
(v7)
593

584
(v12.x.3)
613
620
(v7)
604
(v13.4.8)
(v14.1.9)

647
(14.1.10)
629
638
(v8.3.0)
(v7)
(v8.3.0)
659

681
688
(v7)
751
jFlow V5 Sensor
770
733
726
(v8.3.0)
(v8.3.0)
789
761
(v14.x.11)
(v8.2.0)
780
(v8.2.0)
(v8.1.0)
795
(v7)
804
(v14.x.12)

824
MySQL v2 Sensor
18.11.2014
(v12.4.4)
(v13.x.7)
MySQL Sensor
(v9.1.0)
(v13.x.7)
741
LDAP Sensor
706
697
(v7)
714
IPFIX Sensor
(v12.3.4)
(v7)
IMAP Sensor
672
817
(14.x.13)
(v7)
833
(v14.x.12)
317

NetFlow V5 Sensor
(v7)
846

NetFlow V9 Sensor
875
(v7)
(v7)
884

(v7)
(v7)
865

Oracle SQL Sensor
856
(v14.x.13)
894
907
(v7)
916
(v7)
Passive Application Performance Sensor

932
(v12.x.3)

Ping Sensor
Ping Jitter Sensor

Pingdom Sensor
(v12.x.6)
(v8.3.0)
956
(v8.4.0)
963
(v7)
969

Port Sensor
940
(v7)
948
POP3 Sensor
(v13.x.4)
925
977
(v8.3.0)
(v7)
986
Port Range Sensor
(v12.x.4)
994
PostgreSQL Sensor
1001
Probe Health Sensor
(v14.x.12)
1014
(v9.1.0)
1020

RADIUS Sensor
1035
RADIUS v2 Sensor
1042
SCVMM Host Sensor
1058
1051
(v7)
(v12.x.6)
1076
1067
(v12.x.6)
(v7)
(v7)
1103
(v7)

SMTP Sensor
318
1134
(v9.1.0)
(v14.x.13)
1094
1027
(v7)
sFlow Sensor
(v7)
1119
1126
1112
(v12.x.6)
(v7)
(v12.x.1)
(v7)
18.11.2014


(v7)
1142
(v7)
1151
(v9.1.0)
1161
(v12.x.1)
1169
(v12.x.1)
1176
1183
(v12.x.1)
1191
(v12.x.5)
1198
(v13.x.5)

1205
1213
(v12.x.4)
(v13.x.8)
1221

SNMP Custom Sensor
1243
1236
(v14.1.10)
(v13.x.8)
1229
(v12.x.4)
(v7)
1252
1262
(v9.1.0)
(v7)

1286
(v12.x.4)
1270
1278
(v12.x.4)
(v12.x.4)
1294
(v13.x.5)
1301
(v13.x.5)
1309
(v9.1.0)
(v12.x.6)
1317

1325
1333
(v12.x.6)
(v12.x.4)
(v12.x.6)
1341
1349
(v12.x.4)
1357
(v13.x.4)
(v13.x.4)
1365
1373
(v13.x.4)
1381
(v13.x.4)
1389
(v14.1.10)
1397

18.11.2014
(v13.x.8)
1405
(v13.x.8)
319

SNMP Library Sensor
(v7)
1412
(v8.1.0)
1423

(v8.1.0)
1440

SNMP Memory Sensor
1455
(v13.x.5)
1447
(v12.x.4)
1463
1471
(v8.1.0)
1433
1480
(v12.x.3)
(v12.x.4)
(v12.x.3)
(v12.x.4)
1487
(v13.x.7)
1495
1503
(v12.x.3)
1511
(v12.x.3)
1518
(v13.x.5)
SNMP Printer Sensor
(v14.x.11)
1526

1541

SNMP RMON Sensor
(v13.x.4)
1533
(v13.x.4)
1549
(v13.x.4)
(v12.x.1)
1557
1565
(v13.x.5)
1572
(v13.x.6)
1580
(v13.x.4)
1588

SNMP Traffic Sensor
1611
1621
(v7)
1632
(v13.x.8)
(v8.1.0)
(v8.1.0)
1645
1656

SSH Meminfo Sensor
1672
(v8.1.1)
1664
(v8.1.0)
(v8.1.0)

320
(v13.x.4)
(v7)
1604

1639
1596
(v7)
SNTP Sensor
(v13.x.4)
1680
(v12.x.1)
18.11.2014

(v14.x.12)
1688
(v14.1.9)
1697

SSH Script Sensor
1724
1734
(v12.x.6)

1776
(v14.1.9)
1715
(v12.x.1)
TFTP Sensor
(v14.1.9)
1706
(v14.x.12)
(v7)
1760
1771
1753
(v8.2.0)
1744
(v9.1.0)
(v8.1.0)
(v8.3.0)
1783
(v8.2.1)
1790
1797
(v8.2.1)
1803
(v8.1.0)
1810
(v12.x.1)
1818
1826
(v7)
1851
(v8.1.0)
WBEM Custom Sensor
1835
(v12.x.1)
(v8.1.0)
1843
(v7)

1867
(v8.1.0)
1859
(v12.x.1)

1909

1935
1943
1917
1926
(v8.3.0)
(v7)
(v9.1.0)
(v8.3.0)
(v7)
(v9.1.0)

18.11.2014
1892
(v12.x.4)
1901
(v8.3.0)
(v8.3.0)
1884

1876
1952
1961
(v9.1.1)
(v8.1.0)
321


WMI Custom Sensor
1977
1986
(v12.x.4)
(v7)
1996
2006
(v7.1.1)

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

1969
2015
(v12.x.1)
(v7)

WMI Memory Sensor
2060
(v7)
(v12.x.1)
2043
2032
2052
(v7)
2068
(v8.1.0)
2080
(v8.1.0)
2091
(v12.x.6)
2102
(v14.x.13)
2113

WMI Service Sensor
WMI Share Sensor
(v12.x.1)
2121
(v9)
(v7)
2129
(v8.1.0)
2138
2147
(v12.x.1)
2155
(v8.1.0)

WMI UTC Time Sensor
2169
2184
2176
(v7)
(v7)
WMI Volume Fragmentation Sensor

(v8.1.0)
(v9.2.0)

WMI Volume Sensor
2162
2209
2201
2192
(v13.x.8)
(v8.3.0)
(v9.1.0)
More
Did not find what you are looking for? Have a look into the Additional Sensor Types (Custom
Sensors) 2217 section.
322
18.11.2014

2 Active Directory Replication Errors Sensor
6.8.2
The Active Directory Replication Errors sensor uses its parent device's Windows credentials to
check domain controllers for replication errors. It can show the number of consecutive sync
failures, if the source is deleted, if the scheduled sync is disabled, when the last sync attempt
took place, the result of the last sync, when there was the last sync success, the number of
modified consecutive sync failures, and the number of pending replication operations.
Please make sure you enter valid domain credentials in the parent device's settings.
This sensor type uses lookups to determine the status values of some sensor channels. For
details, please see section Define Lookups 2579 .
Note: This sensor type can have a high impact on the performance of your monitoring system.
Please use it with care! We recommend using not more than 50 sensors, on each probe, of this
type of sensor.
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 2589 . If the framework is missing, you cannot create
this sensor. Note: You need to install the exact version required (a higher version will usually
not work; an exception applies to .NET 3.5 which comprises .NET 2.0 and .NET 3.0). Generally, it
is possible to run several .NET Framework versions on the same machine side-by-side. Please
install the latest update available for the required version.
Required .NET version: 4.0 (with latest update). Please see section More below for details.
Requirement: Member of Windows Domain

This sensor only works if the computer running the PRTG probe is part of the domain whose
AD should be monitored. The probe runs either on the local system (on every node, if on a
cluster probe), or on the system running the remote probe 2589 . If this requirement is not met,
the sensor will fail.
Requirement: Windows Credentials

For this sensor type credentials for Windows systems must be defined for the device you want
to use the sensor on. In the parent device's 288 Credent ials for Windows Sy st ems settings,
please prefer using Windows domain credentials.
Note: If you use local credentials, please make sure the same Windows user accounts (with
same username and password) exist on both the system running the PRTG probe and the
target computer. Otherwise the sensor cannot connect correctly.
Note: Your Windows credentials may not contain any double quotation marks ("). If they do,
this sensor will not work!
18.11.2014
323

Add Sensor
The Add Sensor dialog appears when adding a new sensor on a device manually 224 . It only
shows the setting fields that are imperative for creating the sensor. Therefore, you will not see
all setting fields in this dialog. You can change all settings in the sensor's Set t ings tab later.
In order to monitor replications, PRTG will create one sensor for each replication neighbor you
choose. The settings you make in this dialog are valid for all of the sensors that are created.
The following settings for this sensor differ in the 'Add Sensor' dialog in comparison to the
sensor's settings page:
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 sensor's details page, click on the Set t ings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS Name
defined in the settings of the parent device the sensor is created on.
BASIC SENSOR SETTINGS

Sensor Name
Enter a meaningful name to identify the sensor. The name will be

Tags
Enter one or more tags, separated by space or comma. You can

use tags to group sensors and use tag-filtered views later on. Tags
are not case sensitive. We recommend using the default value. You
can add additional tags to it, if you like. Other tags are
automatically inherited 90 from objects further up in the device
tree. Those are not visible here.
Priority
(top priority).
324
18.11.2014

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 result of the sensor. Choose
between:
Discard sensor result : Do not store the sensor result.
Writ e sensor result t o disk (Filename: "Result of Sensor
[ID].t xt "): Store the last result received from the sensor to the
"Logs (Sensor)" directory (on the Master node, if in a cluster). File
name: Result of Sensor [ID].txt. This is for debugging purposes.
The file will be overridden with each scanning interval. For
information on how to find the folder used for storage, please
see Dat a St orage 2611 section.
SENSOR DISPLAY
Primary Channel
Select a channel from the list to define it as the primary channel. In

the device tree, the last value of the primary channel will always be
displayed underneath the sensor's name. The available options
depend on what channels are available for this sensor. Note: You
can set another primary channel later by clicking on the pin symbol
of a channel in the sensor's overview tab.
Chart Type
Define how different channels will be shown for this sensor.

Show channels independent ly (default ): Show an own graph
for each channel.
St ack channels on t op of each ot her: Stack channels on top
of each other to create a multi-channel graph. This will generate
an easy-to-read graph which visualizes the different components
of your total traffic. Note: This option cannot be used in
combination with manual Vertical Axis Scaling (available in the
Sensor Channels Set t ings 2220 settings).
18.11.2014
325

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

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
327


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 2334 .
Note: Schedules are generally inherited. New schedules will be
added to existing ones, so all schedules are active.
Maintenance Window

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

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
Use parent : Pause the current sensor if the device it is created
on is in a Down status, or if it is paused by another dependency.
Select object : Pause the current sensor if the device it is
created on is in an Down status, or if it is paused by another
dependency. Additionally, pause the current sensor if a specific
other object in the device tree is in a Down status, or if it is
paused by another dependency. Select below.
328
18.11.2014


Mast er object for parent : Make this sensor the master object
for its parent device. The sensor will influence the behavior of
the device it is created on: If the sensor is in a Down status, the
device will be paused. For example, it is a good idea to make a
Ping sensor the master object for its parent device to pause
monitoring for all other sensors on the device in case the device
cannot even be pinged. Additionally, the sensor will be paused if
the parent group of its parent device is in a Down status, or if it
is paused by another dependency.
menu bar.
Dependency
to choose an object on which the current sensor will be
dependent on.
Delay (Seconds)
integer value in seconds. Note: This setting is not available if you
choose this sensor to be the Mast er object for parent . In this
case, please define delays in the parent Device Set t ings 284 or the
superior Group Set t ings 262 .
18.11.2014
329

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
330
18.11.2014

More
Edit Sensor Channels

In order to change display settings, spike filter, and limits, please switch to the sensor's
Overview tab and click on the gear icon of a specific channel. For detailed information, please
see Sensor Channels Set t ings 2220 section.
Notifications
Click on the Not ificat ions tab to change notification triggers. For detailed information, please
see Sensor Not ificat ions Set t ings 2227 section.
Others
18.11.2014
141
section.
331

3 ADO SQL Sensor
6.8.3
ADO SQL Sensor
The ADO SQL sensor monitors a database using an ActiveX Data Objects (ADO) connection. It
connects to the server and shows the response time. Additionally, it can read the number of
records and a value.
Note: For security reasons, you can only create a sensor on a device for which Windows
Credentials have been defined. With these credentials, the PRTG probe must be able to
connect to the Windows domain. If you don't enter valid credentials, you will get an Access
denied error message when scanning. For detailed information, please see More 339 section
below.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
332
19.09.2014

3 ADO SQL Sensor
ADO SPECIFIC DATA

Connection String
Enter the string that will be used to connect to the database. For
example, such a string could be: Provider=SQLOLEDB.1;Data
Source=10.0.0.200\SQLEXPRESS;User
ID=user;Password=userpass;Initial Catalog=Northwind. For more
information on how to build connection strings, please see More
339 section below.
DATA
SQL Expression
Enter a valid SQL statement to execute on the server. In your

SELECT statement, please specify the field name explicitly. Do not
use SELECT *! For example, a correct expression could be: SELECT
AVG(UnitPrice) FROM Products. When a cursor is returned (i.e. with
a SELECT statement), only the first row of data will be processed.
Record Count
If you want to know how many records in your database were

affected by your SQL expression as defined above, you can count
the number of concerned records. Choose between:
Do not count number of records: Affected records will not be
counted.
Count number of records: The number of affected records will
be counted. Note: Enabling this option might increase the
execution time of this sensor.
Post-Processing
If the SQL expression returns a result set, please define if you want
to further process it. Choose between:
Ignore result set : Do not do anything with the data returned.
Process numerical result : Regard the result set returned as
integer or float. You can set the sensor to Warning or Down
status for specific thresholds. Define below.
Process st ring result : Regard the result set returned as a
string. You can set the sensor to error for certain sub-strings
contained or missing. Define below.
Monit or for changes: Monitor if the result set has changed
since last check. The sensor will send an internal message
indicating that its value has changed. In combination with a
Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever a sensor value changes.
19.09.2014
333

3 ADO SQL Sensor
Condition "Warning"
This field is only visible if numeric results is enabled above. Define a

condition of the returned numeric SQL result set that will set the
sensor to a Warning status. Choose between:
none: Do not set the sensor to Warning status for any
condition.
equals: Result set must be the same as the value provided
below.
is above: Result set must be above the value provided below.
lower t han: Result set must be below the value provided below.
does not equal: Result set must be unequal to the value
provided below.
Note: This threshold check the SQL result set only. You can set
additional thresholds in the sensor's channel settings 2220 .
Value
This field is only visible if numeric results is enabled above. Enter a

value of the returned numeric SQL result set that will set the
sensor into a Warning status. Please enter an integer or float
value.
Condition "Down"

sensor to a Down status. Choose between:
none: Do not set the sensor to Down status for any condition.
below.
provided below.
Value

sensor to a Down status. Please enter an integer value.
Response Must Include This field is only visible if string results is enabled above. Enter a
string that must be part of the returned SQL string. If it is not, the
sensor will be set to an error state. Please enter a string or leave
the field empty.
334
19.09.2014

3 ADO SQL Sensor
Response Must Not

include
This field is only visible if string results is enabled above. Enter a

string that must not be part of the returned SQL string. If it is, the
the field empty.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
335

3 ADO SQL Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
336
19.09.2014

3 ADO SQL Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
337

3 ADO SQL Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
338
19.09.2014

3 ADO SQL Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: Monitoring (Almost) Any SQL Server Through ADO with PRTG Network
Monitor
Knowledge Base: How do I correctly configure credentials for ADO SQL sensors?

19.09.2014
339

3 ADO SQL Sensor
Notifications
Others
340
141
section.
19.09.2014

4 Amazon CloudWatch Sensor
6.8.4
The Amazon CloudWatch sensor monitors performance of Amazon Cloud services, such as
Elastic Compute Cloud (EC2), Simple Queue Service (SQS), Elastic Load Balancing (ELB), Elastic
Block Store (EBS), Simple Notification Service (SNS), Relational Database Service (RDS), and
ElastiCache.
Depending on the selected service, the sensor can show CPU utilization, network load in and
out, and disk read and write speed.
Note: The CloudWatch option must be enabled for the instance you want to monitor (you can
do this, for example, using Amazon's AWS console). Amazon will charge you (a small amount)
for each "Amazon CloudWatch API Request" query the sensor sends to the Amazon servers.
Depending on the service, each Amazon CloudWatch sensor sends about 10 to 30 requests
with each scanning interval. Last time we checked the Amazon price list, they charged max.
US$ 0.014 per 1,000 requests (depending on your region). Please see More 348 section for
detailed information.
type of sensor.
Requirement: Access Rights for Amazon CloudWatch Queries

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

Add Sensor
PRTG will perform a meta scan before you actually add this sensor type and requires basic
information for this scan in advance. Provide the requested information in the appearing
window. During the scan, PRTG will recognize all items available for monitoring based on your
input. The following settings differ in comparison to the sensor's settings page:
18.11.2014
341

AMAZON CR EDENTIALS
Region
Select the region in which the instance to be monitored is running.

The settings you make in this dialog are valid for all of the sensors
that are created. Choose between:
US East (Nort hern Virginia)
US West (Oregon)
US West (Nort hern California)
EU (Ireland)
Asia Pacific (Singapore)
Asia Pacific (Toky o)
Asia Pacific (Sy dney )
Sout h America (Sao Paulo)
Note: The CloudWatch option must be enabled for the instance
you want to monitor (you can do this e.g. using Amazon's AWS
console).
Select which service instances you want to monitor. PRTG will create one sensor for each
instance you choose. The settings you make in this dialog are valid for all of the sensors that
are created.
AMAZON CLOU DWATCH SPECIFIC

Service Instance
Select the instances you want to add a sensor for. You see a list
with the names of all items which are available to monitor. Select
the desired items by adding check marks in front of the respective
lines. PRTG creates one sensor for each selection. You can also
select and deselect all items by using the check box in the table
head.
Sensor Settings
342
18.11.2014


Sensor Name

Tags

Priority
(top priority).
AMAZON CR EDENTIALS
AWS Access Key ID
Enter your access key. You can obtain it from aws.amazon.com.
AWS Secret Access

Key
Enter your secret access key. You can obtain it from

aws.amazon.com.
Region
Shows the region your instance is located at. Once a sensor is

created, you cannot change this value. It is shown for reference
purposes only. If you need to change this, please add the sensor
anew.

Period (Interval)
Define in what granularity you want to receive datapoints from

CloudWatch. Choose between:
1 Minut e
2 Minut es
5 Minut es
10 Minut es
30 Minut es
1 Hour
18.11.2014
343


Service
Shows the service this sensor is monitoring. Once a sensor is

anew.
Instance
Shows the Instance ID of the Amazon Web Services instance this

sensor is monitoring. When using the "Simple Notification Service
(SNS)" service, this field is not visible. Once a sensor is created, you
cannot change this value. It is shown for reference purposes only.
If you need to change this, please add the sensor anew.
Topic Name
This field is only visible if you selected a "Simple Notification Service

(SNS)" instance before. It shows the topic name that is monitored
by this sensor. The sensor will show the number and size of
messages published, and the number of notifications delivered and
failed. Each sensor can monitor one topic name only. Once a
sensor is created, you cannot change this value. It is shown for
reference purposes only. If you need to change this, please add
the sensor anew.
Availability Zone
This field is only visible if you selected a "Elastic Load Balancing

(ELB)" instance before. Enter the name of the Availability Zone of
your Load Balancer you want to monitor. If you leave this field
empty, the average value of all zones will be taken.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
344
18.11.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
Note: For Amazon CloudWatch sensors, the scanning interval cannot be inherited. Please use
the individual settings of the sensor to define the interval in which data is received.

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.
18.11.2014
345



maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
menu bar.
Dependency
346
dependent on.
18.11.2014


Delay (Seconds)
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
18.11.2014
347


Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
More
Knowledge Base: How do I define access rights for Amazon CloudWatch queries?
Knowledge Base: How much does Amazon charge for using the CloudWatch API?
Knowledge Base: Why can't I use EU Frankfurt as region for my Amazon CloudWatch sensor?

Notifications
348
18.11.2014

Others
18.11.2014
141
section.
349

5 AVM FRITZ!Box WAN Interface v2 Sensor
6.8.5
The AVM FRITZ!Box WAN Interface Sensor monitors the internet traffic of a FRITZ!Box internet
access router from European manufacturer AVM. It shows incoming and outgoing internet
traffic, as well as the number of outgoing calls and the outgoing connection time.
Note: You have to enable "Transmit status information over UPnP" in the network settings of
your FRITZ!Box for this sensor. See More section below for detailed information about
enabling Universal Plug and Play (UPnP).
Important notice: Currently, this sensor type is in bet a 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.

Add Sensor
Sensor Settings

Sensor Name
350

18.11.2014


Tags

Priority
(top priority).
SENSOR SPECIFIC
Login Method
Select the login method for your FRITZ!Box. You have to use the
login settings exactly as defined in the FRITZ!Box web interface.
Please check this before you add this sensor. Choose between:
Login wit h FRITZ!Box username and password: Choose this
option if your FRITZ!Box settings require full credentials.
Login wit h FRITZ!Box password: Choose this option if your
FRITZ!Box settings require only a password.
No login: Choose this option if your FRITZ!Box does not require
credentials to login.
FRITZ!Box Username
This field is only visible if you select the full credentials option
above. Enter the username for your FRITZ!Box.
FRITZ!Box Password
This field is only visible if you select a credentials based login

option above. Enter the password for your FRITZ!Box.
Note: The sensor uses the credentials of the user accounts
defined in your FRITZ!Box and not the general password for the
hardware device.
DEBU G OPTIONS
Sensor Result
between:
18.11.2014
351

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
352
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
353


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
354
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
355

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
356
18.11.2014

More
Knowledge Base: How do I activate UPnP for my Fritz!Box?

Notifications
Others
18.11.2014
141
section.
357

6 Cisco IP SLA Sensor
6.8.6
Cisco IP SLA Sensor
The Cisco IP SLA sensor monitors Voice over IP (VoIP) network parameters using IP Service
Level Agreement (SLA) from Cisco via Simple Network Management Protocol (SNMP). It shows
different aspects provided by the queried device.
For a general introduction to the technology behind Quality of Service monitoring, please see
Monit oring Qualit y of Service 2507 section.
Add Sensor
IP SLA SPECIFIC
IP SLAs
Select the IP SLAs you want to add a sensor for. You see a list with
the names of all items which are available to monitor. Select the
desired items by adding check marks in front of the respective
head. The list options depend on the configuration of the queried
device. If you're missing a type here, please check your device's
configuration. PRTG can support the following operations:
echo
pat hEcho
fileIO
script
udpEcho
t cpConnect
ht t p
dns
jit t er
dlsw
dhcp
ft p
pat h-jit t er
358
19.09.2014

IP SLA SPECIFIC
Note: Packet Loss values are summarized, but have no explicit
channel for SourceDestination or DestinationSource values
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
IP SLA SPECIFIC
ID
Type
Name (Tag)
These fields show SLA specific settings provided by the queried

SLA device. 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
19.09.2014
359

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
360
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
361


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
362
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
363

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

Notifications
Others
364
141
section.
19.09.2014

7 Citrix XenServer Host Sensor
6.8.7
The Citrix XenServer Host Sensor monitors a Xen host server via Hypertext Transfer Protocol
(HTTP). It shows CPU, memory, and network usage, as well as the number of running virtual
machines and load average.
Note: The parent device must be a Citrix XenServer (version 5.0 or later).
For this sensor type credentials for Xen servers must be defined for the device you want to
use the sensor on.
type of sensor.

Monitoring a XenServer Pool

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

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

Tags

Priority
(top priority).
366
18.11.2014

HOST SETTINGS
UUID
Shows the Universally Unique Identifier (UUID) of the host

monitored by this sensor. 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.
Name
Shows the name of the host monitored by this sensor. Once a

the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
367

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
368
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
369


menu bar.
Dependency
dependent on.
Delay (Seconds)
370
18.11.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: Does PRTG impair my Citrix environment?

18.11.2014
371

Notifications
Others
372
141
section.
18.11.2014

8 Citrix XenServer Virtual Machine Sensor
6.8.8
Citrix XenServer Virtual M achine Sensor
The Citrix XenServer Virtual Machine Sensor monitors a virtual machine on a Xen server via
Hypertext Transfer Protocol (HTTP). It shows CPU usage and free memory in percent.
Note: The parent device must be a Citrix XenServer (version 5.0 or later).
For this sensor type credentials for Xen servers must be defined for the device you want to
use the sensor on.
type of sensor.

Monitoring a XenServer Pool

In a XenServer pool there is one "pool master" that manages the pool. Incoming queries on
any host are automatically forwarded to the pool master. If you want to monitor your virtual
machines, or host servers, simply create respective sensors on a device that represents one
host server of your pool. Internal processes will make sure that monitoring will take place and
continue independently from the physical host. Note: In PRTG's device tree, the sensors for
virtual machines will always remain on the host you originally created it on, also if it is currently
running on a different host.
Add Sensor
Note: PRTG requests a full list of all virtual machines configured on the device. Therefore, it may
take a few seconds before the dialog is loaded.
If you select more than one virtual machine, multiple sensors are created at once 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:
18.11.2014
373

VIR TU AL MACHINE SETTINGS

Virtual Machine
Select the Virtual Machine (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

Tags

Priority
(top priority).
374
18.11.2014


UUID
Shows the Universally Unique Identifier (UUID) of the virtual

machine. Once a sensor is created, you cannot change this value. It
is shown for reference purposes only. If you need to change this,
please add the sensor anew.
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

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
375

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
376
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
377


menu bar.
Dependency
dependent on.
Delay (Seconds)
378
18.11.2014

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

18.11.2014
379

Notifications
Others
380
141
section.
18.11.2014

9 ClusterState Sensor
6.8.9
ClusterState Sensor
The ClusterState sensor monitors the health of a PRTG cluster 81 and indicates PRTG's own
system health status. It is created automatically with a PRTG cluster installation and cannot be
deleted or added manually. It measures various internal system parameters of the cluster
system such as the number of connects per minute, cluster in- and outgoing messages per
minute, as well as the number of connected and disconnected cluster nodes. If at least one
cluster node is disconnected, this sensor will show 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 127 you can choose the cluster member of which you want to
show data (or of all nodes).
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel
19.09.2014

381

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
382
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
383

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

Notifications
Others
384
141
section.
19.09.2014

10 Core Health Sensor
6.8.10 Core Health Sensor

The Core Health sensor monitors internal PRTG parameters. It shows the state of the PRTG
core server. It is created automatically by PRTG and cannot be deleted. This sensor type
checks various parameters of your PRTG core which have an impact on the stability of the
system:
Healt h: This index value sums up the core state into a value between 100% (healthy) and 0%
(failing). Frequent or repeated health values below 100% should be investigated.
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.
Commit t ed Memory : This channel shows the amount of memory committed to the PRTG
core server as reported by the memory manager.
Free Page File Memory : This channel shows the amount of free page file memory currently
available on the system. Page file memory is aggregated RAM and the size of page file. It is
the maximum amount of memory that is available on the system to be used for all currently
running processes. If it gets too low the system can crash, at least some applications will
throw "Out of memory" errors.
Free Phy sical Memory : This channel shows the amount of free physical memory currently
available on the system. This is the RAM that is physically built-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 Virt ual Memory : This channel shows the accessible address space on the system for
PRTG. PRTG cannot use more memory than reported here, independently from free page file
and physical memory. On a 32bit OS (operating system) the maximum is 2 GB (3 GB with
special settings under Windows); on a 64bit OS it is 4 GB if PRTG is running as 32bit version,
and unlimited as 64bit version (only Core). If free virtual memory gets too low, PRTG will
throw "Out of memory" errors or the message "not enough storage to process this
command" (visible in the Core log).
Threads: This channel shows the number of program parts which are currently running
simultaneously. This number can increase with heavy load. The number should not exceed
100 in normal operation.
Raw Dat a Buffer: This channel shows how much raw data is temporarily stored on the
physical memory while I/O operations on the disk. Usually, this value should be 0 (or very
low). Investigate increasing values.
This sensor can be set up on a Probe Device only!
Sensor Settings
18.11.2014
385


Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
386

18.11.2014

Inherited Settings
described below.
18.11.2014
387

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
388
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
389


Notifications
Others
390
141
section.
18.11.2014

11 Dell PowerVault MDi Logical Disk Sensor
6.8.11 Dell PowerVault M Di Logical Disk Sensor

The Dell PowerVault MDi Logical Disk sensor monitors a virtual disk on a Dell PowerVault
MD3000i, MD3620i, MD3000f, MD3620f, or MD3820i. It might work with other models, too. This
sensor can show current, maximum, and total IOs, current and maximum speed, as well as read
and cache hit percentages.
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 2589 . 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
To monitor logical disks on a Dell PowerVault, PRTG creates one sensor for each disk you
select in the Add Sensor dialog. The settings you make in this dialog are valid for all of the
sensors that are created.
SENSOR SETTINGS
Virtual Disks
Select the disks you want to add a sensor for. You see a list with
head.
Sensor Settings
26.09.2014
391


Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Virtual Disk
Shows the name of the virtual disk monitored by this sensor. Once
a sensor is created, you cannot change this value. It is shown for
the sensor anew.
Sensor Result
between:
SENSOR DISPLAY
Primary Channel
392

26.09.2014

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
26.09.2014
393

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
394
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
395


menu bar.
Dependency
dependent on.
Delay (Seconds)
396
26.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
26.09.2014
397

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

Notifications
Others
398
141
section.
26.09.2014

12 Dell PowerVault MDi Physical Disk Sensor
6.8.12 Dell PowerVault M Di Phy sical Disk Sensor

The Dell PowerVault MDi Physical Disk sensor monitors a physical disk on a Dell PowerVault
MD3000i, MD3620i, MD3000f, or MD3620f. It might work with other models, too. The sensor
shows the physical disk states mode and status 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)
26.09.2014
None (status: warning)
The indicated slot is empty, or the array

cannot detect the physical disk.
399

"St at us" Channel
"Mode" Channel
Descript ion
Undefined (status:
down)
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 2589 . 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
To monitor physical disks on a Dell PowerVault, PRTG creates one sensor for each disk you
SENSOR SETTINGS
Physical Disks
head.
Sensor Settings
400
26.09.2014


Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Physical Disks
Shows the disk that this sensor monitors. Once a sensor is

anew.
Sensor Result
between:
26.09.2014
401

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
402
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
403


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
404
26.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
405

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
406
26.09.2014

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

Notifications
Others
26.09.2014
141
section.
407

13 DHCP Sensor
6.8.13 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. If a server
responds, the sensor shows both the address of the server and the offered IP in the sensor's
Message field. You can check the server's response using Regular Expressions 2587 . The
sensor's channels include response time (msec) and the lease time given by the server (in
days).
This sensor can be set up on a Probe Device only! On sensor creation, choose the network
card on the probe system which will be used to send the broadcast message.
Add Sensor
In order to monitor DHCP servers, PRTG will create one sensor for each network interface you
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.
Select the desired items by adding check marks in front of the
respective lines. PRTG creates one sensor for each selection. You
table head.
Sensor Settings

Sensor Name
408

19.09.2014

13 DHCP Sensor

Tags

Priority
(top 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 will only appear 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 will change to a Down status. 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
doesn't, the sensor will show an error. For more details, see
Regular Expressions 2587 section. Leave empty to not use this
field.
Client IP Must Not

Include
This field will only appear 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 contains the defined
string, the sensor will change to a Down status. See example
above. For more details, see Regular Expressions 2587 section.
Leave empty to not use this field.
19.09.2014
409

13 DHCP Sensor
DHCP SPECIFIC
Server IP
Specify if you want to check the returned server IP with a regular

expression. Choose between:
Don't check: The IP will only appear in the sensor message
without further processes.
Check: Enter the regular expression you want to use below.
Server IP Must Include
This field will only appear if you chose to check the server IP
above. In the response of the DHCP server, search using a regular
expression. If the answer for the server IP does not contain the
defined string, the sensor will change to a Down status. See
example above. For more details, see Regular Expressions 2587
section. Leave empty to not use this field.
Server IP Must Not

Include
This field will only appear if you chose to check the server IP
above. In the response of the DHCP server, search using a regular
expression. If the answer for the server IP contains the defined
string, the sensor will change to a Down status. See example
above. For more details, see Regular Expressions 2587 section.
Leave empty to not use this field.
Timeout (sec)

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

sensor scans, PRTG can write an entry to the system Logs 146 .
Choose between:
Ignore: Do not write a log entry if the offered IP address
changes.
Writ e log ent ry : Write an entry to the system Logs whenever
the DHCP server offers a different IP address compared to the
last sensor scan.
410
19.09.2014

13 DHCP Sensor
DHCP SPECIFIC
Note: Regardless of this setting, those entries will always be added
to the sensor Log.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
411

13 DHCP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
412
19.09.2014

13 DHCP Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
413

13 DHCP Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
414
19.09.2014

13 DHCP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
19.09.2014
141
section.
415

14 DNS Sensor
6.8.14 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 and goes to a Down
status if the DNS server does not resolve a given domain name correctly.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
DNS SPECIFIC
Timeout (Sec.)
416

is triggered. The maximum value is 900 seconds (15 minutes).
19.09.2014

14 DNS Sensor
DNS SPECIFIC
Port
Enter the number of the port the sensor will try to connect to. This
must be the port the sensor's parent device is running the DNS
service on. Usually you will use port 53. We recommend using the
default value. Note: The sensor will connect to the IP Address or
DNS Name value of the device it is created on.
Domain
Enter the domain name that will be resolved by the sensor using
the Domain Name Service (DNS) server specified in the sensor's
parent device's settings. You can enter an internet domain name
here (for example, example.com) or a DNS name in your internal
network (such as computer-xyz) depending on the type of DNS
server you monitor. You can also enter an IP address here.
Query Type
Select the type of query that should be sent 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 result received from the DNS server will be checked.
Choose between:
Ignore result : Any valid answer of the DNS server will be
accepted by the sensor.
Check result : Check if the response contains certain strings.
Define below.
Value
This field is only visible if result checking is enabled above. Enter

elements that must be contained in the response of the DNS
server. Enter each entry in one line. At least one of the elements
must be contained in the received result. 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.
Write Result
between:
19.09.2014
417

14 DNS Sensor
DNS SPECIFIC
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
418
19.09.2014

14 DNS Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
419

14 DNS Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
420
19.09.2014

14 DNS Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
421

14 DNS Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
422
141
section.
19.09.2014

15 Enterprise Virtual Array Sensor
6.8.15 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, for example, status of system, controllers, enclosures, disks, disk groups,
folders, hosts, snapshots, data replication, cabinets, and many more, depending on the
available measurement components. If devices have measuring tools for fans and temperature,
the corresponding data will be displayed as well.
For these EVA components, this sensor type can show the operational status, predicted
failures, accessible media, allocation in percent, availability for VRaids in bytes, exaggerated
bytes, group host access, the number of grouped and ungrouped disks, the age of snapshots,
and the license status.
Note: You have to explicitly specify the credentials of the EVA in the sensor settings.
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 431 .
Add Sensor
PRTG will perform a meta scan before you actually add this sensor type and requires basic
information for this scan in advance. Provide the requested information in the appearing
window. During the scan, PRTG will recognize all items available for monitoring based on your
input. The following settings differ in comparison to the sensor's settings page:
EVA CR EDENTIALS
Scanning Mode
Specify the depth of the meta scan. Choose between:

Basic: We recommend using this scanning mode. Various
modules of your EVA will be available for monitoring.
19.09.2014
423

EVA CR EDENTIALS
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
EVA SETTINGS
Modules
Select the modules you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
424
19.09.2014

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

Chart Type

for each channel.
19.09.2014
425

SENSOR DISPLAY
Stack Unit
426

19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
427


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
428
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
429

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
430
19.09.2014

More
HP Command View EVA Software
http://www8.hp.com/us/en/products/storage-software/product-detail.html?oid=471497
Knowledge Base: Do I really have to install the whole Command View on the probe to use the
EVA sensor?

Notifications
Others
19.09.2014
141
section.
431

16 Event Log (Windows API) Sensor
6.8.16 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).
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 440 .
type of sensor.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
432
19.09.2014

WINDOWS API EVENT LOG SPECIFIC

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

Event Type
Specify the type of event that this sensor processes. Other event
type will not 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 enabled source filtering above. Enter
a source from which the events come from. Only events from a
source matching this string will be 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:
19.09.2014
433


Off: Do not filter by event ID.
On: Enable filtering by event ID.
Match Value (Event ID)
This field is only visible if you enabled ID filtering above. Enter one
or more event IDs (comma separated) from which the events must
have. Only events with an ID matching one of the values will be
regarded. Please enter one integer value or more comma
separated integer values.
Filter by Category
Filter all received events for a certain event category. If you enable
Off: Do not filter by event category.
On: Enable filtering by event category.
Match String (Event

Category)
This field is only visible if you enabled category filtering above.

Enter a category which the events must have. Only events with a
category that matches this string will be 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 enabled filtering is enabled. Enter a

user name that the events must to be assigned to. Only events
with a user name that matches this string will be 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)
434
This field is only visible if you enabled computer filtering above.

Enter a computer name which the events must be assigned to.
Only events with a computer name that matches this string will be
regarded. Please enter a string.
19.09.2014


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 enabled message filtering above.

Enter a message that the event must contain. Only events with a
message matching this string will be 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

Chart Type

for each channel.
Stack Unit
19.09.2014

435

Inherited Settings
described below.
436
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
437


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
438
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
439

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?

Notifications
440
19.09.2014

Others
19.09.2014
141
section.
441

17 Exchange Backup (Powershell) Sensor
6.8.17 Exchange Backup (Powershell) Sensor

The Exchange Backup (Powershell) sensor monitors backups of an Exchange server using
Remote PowerShell. It shows several states of an Exchange database backup, for example, the
last full backup, the last differential backup, and if currently a backup is running.
Note: The parent device for this sensor must be an Exchange server version 2010 or higher.
to use the sensor on.
Requirement: Remote PowerShell and Remote Exchange Management Shell

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

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

The user of this sensor needs elevated rights on the Exchange system. It is not sufficient to
have administrator rights. Please see section More below for detailed information on rights
management.
Add Sensor
In order to monitor backups of Exchange server databases, PRTG will create one sensor for
each database you choose. The settings you make in this dialog are valid for all of the sensors
that are created.
442
19.09.2014

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

Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Database
Shows the name of the monitored database. Once a sensor is

anew.
Sensor Result
Choose between:
19.09.2014
443

SENSOR SETTINGS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
444
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
445


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
446
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
447

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
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?
448
19.09.2014


Notifications
Others
19.09.2014
141
section.
449

18 Exchange Database (Powershell) Sensor
6.8.18 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, its size, if the database is mounted, and if the database is recognized as valid.



management.
Add Sensor
In order to monitor databases of an Exchange server, PRTG will create one sensor for each
database you choose. The settings you make in this dialog are valid for all of the sensors that
are created.
450
19.09.2014

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

Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Database
Shows the name of the monitored database. Once a sensor is

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

automatically if it is unmounted. Choose between:
19.09.2014
451

SENSOR SETTINGS
Try t o remount
Just report t he current reading, keep unmount ed if so
Sensor Result
Choose between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
452

19.09.2014

Inherited Settings
described below.
19.09.2014
453

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
454
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
455


menu bar.
Dependency
dependent on.
Delay (Seconds)
456
19.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
19.09.2014
457


Notifications
Others
458
141
section.
19.09.2014

19 Exchange Mailbox (Powershell) Sensor
6.8.19 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, the
number of items, and the time of the last login.



management.
Add Sensor
In order to monitor mailboxes of Exchange servers, PRTG will create one sensor for each
mailbox you choose. The settings you make in this dialog are valid for all of the sensors that
are created.
19.09.2014
459

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

Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Mailbox Name
Shows the name of the monitored mailbox. Once a sensor is

anew.
Sensor Result
Choose between:
460
19.09.2014

SENSOR SETTINGS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
461

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
462
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
463


menu bar.
Dependency
dependent on.
Delay (Seconds)
464
19.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
19.09.2014
465


Notifications
Others
466
141
section.
19.09.2014

20 Exchange Mail Queue (Powershell) Sensor
6.8.20 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 shows, for example, queued
mails, retrying mails, unreachable mails, and poisonous mails. See section More 473 below for
an explanation of the transport queue types.



management.
Add Sensor
In order to monitor message queues of Exchange servers, PRTG will create one sensor for
each role you choose. The settings you make in this dialog are valid for all of the sensors that
are created.
19.09.2014
467

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

Tags

Priority
(top priority).
SENSOR SETTINGS
Sensor Result
Choose between:
468
19.09.2014

SENSOR SETTINGS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
469

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
470
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
471


menu bar.
Dependency
dependent on.
Delay (Seconds)
472
19.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
19.09.2014
473

Knowledge Base: Types of Transport Queues in Microsoft Exchange

Notifications
Others
474
141
section.
19.09.2014

21 Exchange Public Folder (Powershell) Sensor
6.8.21 Exchange Public Folder (Powershell) Sensor

The Exchange Public Folder (Powershell) sensor monitors public folders of an Exchange server
using Remote PowerShell. It shows several states of a public folder, for example, its total size,
the number of items, and the time of the last access.



management.
Add Sensor
In order to monitor public folders of Exchange servers, PRTG will create one sensor for each
folder you choose. The settings you make in this dialog are valid for all of the sensors that are
created.
19.09.2014
475

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

Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Public Folder
Shows the name of the monitored folder. Once a sensor is

anew.
Sensor Result
Choose between:
476
19.09.2014

SENSOR SETTINGS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
477

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
478
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
479


menu bar.
Dependency
dependent on.
Delay (Seconds)
480
19.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
19.09.2014
481


Notifications
Others
482
141
section.
19.09.2014

22 EXE/Script Sensor
6.8.22 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). The sensor shows the execution time,
and can show one value returned by the executable file or script (in one channel only). For
details about the return value format please see the Applicat ion Programming Int erface
(API) Definit ion 2571 .
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 1977 .
Add Sensor
19.09.2014
483

SENSOR SETTINGS
Script
Select an executable file from the list. It will be executed with

every scanning interval. In this list, files in the corresponding /
Cust om Sensors/EX E sub-directory of the probe system's PRTG
program directory are shown (see Dat a St orage 2611 ). In order for
the files to appear in this list, please store them into this folder.
Store files ending in BAT, CMD, DLL, EXE, PS1, and VBS. 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,
value:message to standard output). The file's exitcode will
determine the sensor status. 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 2571 ). 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 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!
Channel Name
Enter a name for the channel in which the returned values will be
shown. This is for display purposes only. Please enter a string.
Unit String
Enter a string describing the unit of the returned values. This is for
display purposes only. Please enter a string.
Sensor Settings
484
19.09.2014


Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
EXE/Script
Shows the executable or script file that is executed 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. 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 2571 ). 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're not sure.
19.09.2014
485

SENSOR SETTINGS
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
(Applicat ion Programming Int erface (API) Definit ion 2571 ).
Security Context
Define the Windows user account that will be used 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 is running 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 sensor's parent device's
settings 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
493 section below. Please enter a string or leave the field empty.
Timeout (sec.)

longer than this value the external process is killed and an error
message is triggered.
Value Type
Shows the expected value type, chosen on sensor creation. Once

the sensor anew. Note: The sensor cannot handle string values.
If Value Changes
Define what shall be done in case the value of this sensor

changes. You can choose between:
Ignore changes (default ): No action will be taken on change.
Trigger 'On Change' not ificat ion: The sensor will send an
internal message indicating that its value has changed. In
combination with a Change Trigger, you can use this mechanism
to trigger a notification 2227 whenever the sensor value changes.
486
19.09.2014

SENSOR SETTINGS
EXE Result
Define what will be done with the result the executable file gives
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

Chart Type

for each channel.
Stack Unit
19.09.2014

487

Inherited Settings
described below.
488
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
489


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
490
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
491

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
492
19.09.2014

More
Information about custom scripts and executables
Applicat ion Programming Int erface (API) Definit ion
2571
2217
Knowledge Base: What is the Mutex Name in PRTG's EXE/Script Sensor's settings?
Knowledge Base: How and Where Does PRTG Store its Data?
Knowledge Base: How can I test if parameters are correctly transmitted to my script when
using an EXE/Script sensor?

Notifications
Others
19.09.2014
141
section.
493

23 EXE/Script Advanced Sensor
6.8.23 EXE/Script Advanced Sensor

The EXE/Script Advanced sensor runs an executable file (EXE, DLL) or a script (batch file,
VBScript, Powershell) on the computer running the local or remote probe. This option is
provided as part of PRTG's Application Programming Interface (API). The sensor can show values
returned by the executable file or script in multiple channels. The return value of this sensor
must be valid XML. For details about the return value format please see the Applicat ion
Programming Int erface (API) Definit ion 2571 .
Note: The executable or script file must be stored on the system of the probe the sensor is
Note: If you want to execute a custom Windows Management Instrumentation Query Language
(WQL) script, please use the WMI Cust om Sensor 1977 .
Limited to 50 Sensor Channels

PRTG does not support more than 50 sensor channels officially. Depending on the data used
with this sensor type, you might exceed the maximum number of supported sensor channels.
In this case, PRTG will try to display all sensor channels. However, please be aware that you will
experience limited usability and performance.
Add Sensor
SENSOR SETTINGS
EXE/Script
494
Select an executable file from the list. It will be executed with

every scanning interval. In this list, files in the corresponding /
Cust om Sensors/EX EX ML sub-directory of the probe system's
PRTG program directory are shown (see Dat a St orage 2611 ). In
order for the files to appear in this list, please store them into this
folder. Store files ending in BAT, CMD, DLL, EXE, PS1, and VBS. In
order for the sensor to show the expected values and sensor
status, your files must return the expected XML format to standard
output. Values and message must be embedded in the XML. For
detailed information on how to build custom sensors and for the
expected return format, please see the API documentation
(Applicat ion Programming Int erface (API) Definit ion 2571 ). There,
find detailed information the the "Custom Sensors" tab.
19.09.2014

SENSOR SETTINGS
Note: Please do not use the folder \Custom Sensors\Powershell
Scripts to store your files. This remnant from previous software
versions is not used any more and may usually be deleted.
Note: When using custom sensors on the Clust er Probe, please
copy your files to every cluster node installation.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
EXE/Script
19.09.2014
Shows the executable or script file that is executed with each

sensor scan, as defined on sensor creation. Once a sensor is
anew.
495

Parameters
If your executable or 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 2571 ). 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're 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
(Applicat ion Programming Int erface (API) Definit ion 2571 ).
Security Context
executable or script file. Choose between:
Use securit y cont ext of probe service: Run the selected file
under the same Windows user account the probe is running on.
By default, this is the Windows system user account (if not
manually changed).
sensor is created on. Please go to sensor's parent device's
settings to change these Windows credentials.
Mutex Name
Timeout (Sec.)

longer than this value the external process will be killed and an
error message will be triggered. The maximum value is 900
seconds (15 minutes).
EXE Result
Define what will be done with the results the executable file gives
496
19.09.2014


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

Chart Type

for each channel.
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 2571 ).
19.09.2014
497

Inherited Settings
described below.
498
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
499


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
500
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
501

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
502
19.09.2014

More
2571
2217

Notifications
Others
19.09.2014
141
section.
503

24 File Sensor
6.8.24 File Sensor

The File sensor monitors a file located on the probe's local disk or a file accessible via Server
Message Block (SMB). You can monitor file content and file time stamp changes. The sensor
shows the file size and when the file was modified the last time (in days, hours, and minutes,
depending on the elapsed time). In contrast to the Folder sensor 520 , you are able to monitor if
the actual content of a specific file has changed.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
504
19.09.2014

24 File Sensor
SENSOR SPECIFIC
File Name
Enter the full path to the file this sensor will monitor. For example,
enter C:\Windows\file.txt. If the file is located on a network device
use the Uniform Naming Convention (UNC) path without the server
part (you would only enter share\folder\file.txt). The server part (\
\server\) is taken from this sensor's parent device's settings.
Please enter a valid path and file name. Note: In order to provide
any shares, the LanmanServer "Server" Windows service must be
running on the target computer.
Check If
Specify when the sensor will send an alert. Choose between:

File exist s: The sensor will send an alert if the file does not
exist.
File does not exist : The sensor will send an alert if the file
exists.
Monitor File Content
Specify if the sensor will send a change notification when the

content of the file changes (based on a checksum). Choose
between:
Ignore changes: No action will be taken on change.
Trigger 'change' not ificat ion: The sensor will send an internal
message indicating that its value has changed. In combination
with a Change Trigger, you can use this mechanism to trigger a
notification 2227 whenever the sensor value changes.
Monitor File Time

Stamp

content of the file's time stamp changes. Choose between:
SENSOR DISPLAY
Primary Channel
19.09.2014

505

24 File Sensor
SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
506
19.09.2014

24 File Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
507

24 File Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
508
19.09.2014

24 File Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
509

24 File Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
510
19.09.2014

24 File Sensor
More
Knowledge Base: What can I do if PRTG doesn't succeed with monitoring a share? PE029 PE032

Notifications
Others
19.09.2014
141
section.
511

25 File Content Sensor
6.8.25 File Content Sensor

The File Content sensor checks a text file (for example, log files) for certain strings and returns
the line number of the last match and the number of total matches. Additionally, matching lines
are quoted in the sensor message field.
Note: This sensor does not support UTF-16 encoded files! In this case, please try use a custom
sensor like the EX E/Script Sensor 483 or the EX E/Script Advanced Sensor 494 .
Note: This sensor does not support binary files officially! If you still try monitoring binary files
contrary to our recommendation, please choose the option Read ent ire file in section Read
Behavior in the sensor settings.
Note: This sensor supports Unix line feeds.
type of sensor.
Add Sensor
Sensor Settings

Sensor Name

Tags

512
26.09.2014


Priority
(top priority).
SENSOR SPECIFIC
File Name
enter C:\Windows\file.txt. If the file is located on a network device
part (you would only enter share\folder\file.txt). The server part (\
Please enter a valid path and file name.
Note: In order to provide any shares, the LanmanServer "Server"
Windows service must be running on the target computer.
Note: If you define a file on your network here, please be aware
that this might produce high network traffic, because PRTG will
query the entire file with every scanning interval.
Search String
Define the string inside the log file you would like to check for.
The input is not case-sensitive. Please enter a string.
Read Behavior
Define in which way the sensor will read the target file. Choose
between:
Read ent ire file: The sensor will check the whole file in every
sensor scanning interval. If this results in too much traffic on the
target system, we recommend you to choose the other read
behavior option.
Read lines appended t o t he file only : The sensor will check
the whole file only with the first scan. The following sensor
scans will then only read lines which were appended since the
last scan, all other lines (which already existed in the previous
scan) will be skipped. With this option, only content that were
actually added to the file will be read and checked.
Note: The newly added lines can only be read if the file is bigger
than at the previous scan and the last line in the file at the
previous scan still has to be at the same place in the file. The
sensor supports Windows ans Linux line endings (CRLF resp. LF).
Search Method
26.09.2014
Define the method you want to provide the search string with. The
pattern must be contained in one line and only the last matching
line will be given back. Choose between:
513

SENSOR SPECIFIC
Simple st ring search: Search for a simple string.
Regular Expression: Search using a regular expression. For
more details, see Regular Expressions 2587 section.
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
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
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
514
26.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
26.09.2014
515

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
516
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
517


menu bar.
Dependency
dependent on.
Delay (Seconds)
518
26.09.2014

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

Notifications
Others
26.09.2014
141
section.
519

26 Folder Sensor
6.8.26 Folder Sensor

The Folder sensor monitors a folder using Server Message Block (SMB). You can monitor file
changes and file ages. It shows the folder size and file count, as well as the oldest and newest
file value in days and hours.
Note: The Folder sensor counts all files in a folder, including hidden files.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
520
19.09.2014

26 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 (\
Please enter a valid path name. Note: In order to provide any
shares, the LanmanServer "Server" Windows service must be
Sub-Folder Recursion
Specify if subfolders will be included in the monitoring. Choose

between:
Do not recurse sub-folders: Only monitor the folder specified
above; 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 sub-folders 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.
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 error 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 error status if one of
the files in the specified folder is younger than a specific time
unit.
File Age Limit

19.09.2014
File Age Limit Unit
This field is only visible if a file age check is enabled above. Enter
the age of a file in the folder that will trigger the sensor's status
change if undershot respectively overrun. Please enter an integer
value. The value will be interpreted as days, hours, or minutes;
according to your setting below.
This field is only visible if a file age check is enabled above. Specify
521

26 Folder Sensor
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
522
19.09.2014

26 Folder Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
523

26 Folder Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
524
19.09.2014

26 Folder Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
525

26 Folder Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
526
19.09.2014

26 Folder Sensor
More

Notifications
Others
19.09.2014
141
section.
527

27 FTP Sensor
6.8.27 FTP Sensor

The FTP sensor monitors file servers using File Transfer Protocol (FTP) and FTP over SSL (FTPS).
It shows the response time of the server.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR SPECIFIC
Timeout (Sec.)

longer than this value, the request is aborted and an error
message is triggered. The highest timeout supported is 900
seconds (15 minutes). Please enter an integer value.
Port
Enter the number of the port the sensor tries to connect to.
Please enter an integer value. We recommend using the default
value.
528
18.11.2014

27 FTP Sensor
SENSOR SPECIFIC
If you do not get a connection, please try another port number.
FTP Mode
Specify which FTP mode will be used for the connection. Choose
between:
Use act ive mode
Use passive mode
We recommend using the default value. If you do not get a
connection, please try the passive mode.
TR ANSPOR T-LEVEL SECU R ITY

FTP Specific
Specify if the sensor uses an encryption for the connection.

Choose between:
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
18.11.2014
Enter a password for the FTP login. Please enter a string or leave
the field empty.
529

27 FTP Sensor
AU THENTICATION
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
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
530

18.11.2014

27 FTP Sensor
Inherited Settings
described below.
18.11.2014
531

27 FTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
532
18.11.2014

27 FTP Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
533

27 FTP Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
534
18.11.2014

27 FTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
18.11.2014
141
section.
535

28 FTP Server File Count Sensor
6.8.28 FTP Server File Count Sensor

The FTP Server File Count sensor logs in to an FTP server and returns the number of files
available in the directory listing.
type of sensor.

Required .NET version: 2.0.
Add Sensor
SENSOR SETTINGS
Channel Name
Enter a name for the channel in which the sensor shows the
returned values. This is for display purposes only. Please enter a
string. You can change this value later in the respective channel
settings 2220 of this sensor.
Sensor Settings
536
18.11.2014


Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Check Method
Define how to access the FTP server directory that this sensor
monitors. Choose between:
Check URL: The sensor uses an explicitly defined URL of an FTP
server to access the target directory.
Check folder on parent device: The sensor uses the IP address
or DNS name of the parent device where you add this sensor to
and monitors a defined folder on this device.
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.
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.
18.11.2014
537

SENSOR SETTINGS
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 login to the FTP server. Please enter a
string.
Password
Define the password for the login to the FTP server. Please enter a
string.
File Count
Define which file the sensor counts. Choose between:

Count t he t ot al number of files: The sensor always shows the
total number of all files in the defined folder.
Count only new files: The sensor shows only the number of
new files since the last sensor scan. You can define the
frequency of sensor scans in section Scanning Int erval 539 .
Note: With the every sensor scan, any new files from the
previous scan will be regarded as old.
If Value Changes
change.
DEBU G OPTIONS
Sensor Result
between:
538
18.11.2014

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
539

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
540
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
541


menu bar.
Dependency
dependent on.
Delay (Seconds)
542
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
543


Notifications
Others
544
141
section.
18.11.2014

29 Google Analytics Sensor
6.8.29 Google Analy tics Sensor

The Google Analytics sensor queries data from a Google Analytics account via Hypertext
Transfer Protocol (HTTP). It shows the values for different metrics in different sensor channels.
Note: To use the Google Analytics sensor, you have to enable Access for less secure apps in
section Account permissions in the Securit y settings of your Google account. Otherwise,
you might get the error message "The remote server returned an error. (403) Forbidden."
type of sensor.

Add Sensor
Sensor Settings

Sensor Name
18.11.2014

545


Tags

Priority
(top priority).
GOOGLE ANALYTICS SETTINGS

Period (Interval)
Enter how often the sensor will query data. Choose between:
1 Day
2 Day s
3 Day s
1 Week
Username
Please enter the username of the Google Analytics account you

want to query. Please enter a string.
Password
Please enter the password of the Google Analytics account you

want to query. Please enter a string.
Profile ID
Enter the 8-digits profile ID of the Google Analytics account. For

help, please see More 551 section below.
Metrics
Enter a comma separated list with all metrics you want to query. A
default set of metrics is already predefined. For help, please see
More 551 section below.
This sensor also supports the "exception" metrics exceptions,
fatalExceptions, exceptionsPerScreenview, and
fatalExceptionsPerScreenview.
Days
Define for how many days the sensor will query data. Enter 1 to
query yesterday's data only, or define any number of days. Please
enter an integer value.
Average
Define if the sensor will query averaged data. Select between:
546
18.11.2014

GOOGLE ANALYTICS SETTINGS

Use: Query averaged data. This setting only takes effect if your
entered more than "1" in the Day s setting above. Data will be
averaged over the number of days.
Don't use: Do not query averaged data, but receive raw data.
DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
18.11.2014
547

SENSOR DISPLAY
Stack Unit

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

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.
548
18.11.2014



maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
menu bar.
Dependency
18.11.2014
dependent on.
549


Delay (Seconds)
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
550
18.11.2014


Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om

HTTP Proxy Settings

Name

Port
User

Password

More
Knowledge Base: Where do I find my Google Analytics profile ID?
18.11.2014
551

Knowledge Base: Where do I find available Google Analytics metrics?


Notifications
Others
552
141
section.
18.11.2014

30 HTTP Sensor
6.8.30 HTTP Sensor

The HTTP sensor monitors a web server using Hypertext Transfer Protocol (HTTP). It shows the
loading time. This is the easiest way to monitor if a website (or a specific website element) is
reachable.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
HTTP SPECIFIC
Timeout (Sec.)
19.09.2014
Enter a timeout in seconds for the HTTP request. If the reply takes
553

30 HTTP Sensor
HTTP SPECIFIC
URL
Enter the URL the sensor connects to. It has to be URL encoded! If
you enter an absolute URL, the sensor uses this address
independently from the IP address/DNS name setting of the
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
The request method determines how the given URL is requested.

GET: Request the website directly, like browsing the web. We
recommend using this setting for a simple check of a web page.
POST: Send post form data to the URL. If this setting is chosen,
you must enter the data that will be sent in the Post dat a field
below.
HEAD: Only request the HTTP header from the server; without
the actual web page. Although this saves bandwidth since less
data is transferred, it is not recommended because the measured
request time is not the one experienced by your users and you
might not be notified for slow results or timeouts.
Postdata
This field is only visible when 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!
Content Type
This setting is only visible when POST is selected in the 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
554
This field is only visible when Cust om is selected above. Define the
content type which is needed, e.g., XML, JSON, HTTP.
19.09.2014

30 HTTP Sensor
SSL SPECIFIC
SSL Method
This setting is relevant only when using https in the URL field. We
recommend using the default value. If you experience connection
problems, please select another SSL method from the list. Choose
between:
SSL V2
SSL V2 or V3: This is the default setting.
SSL V3
TLS V1
Note: Other TLS versions are not supported.
Note: This sensor type implicitly supports Server Name Identification (SNI), an extension to the
TLS protocol.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
19.09.2014

555

30 HTTP Sensor
Inherited Settings
described below.

HTTP Proxy Settings

Name

Port
User

Password

556
19.09.2014

30 HTTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
557

30 HTTP Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
558
19.09.2014

30 HTTP Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
559

30 HTTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
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/
560
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
561

31 HTTP Advanced Sensor
6.8.31 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. It
shows the loading time, bytes received, download bandwidth (speed), and time to first byte.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
HTTP SPECIFIC
Timeout (Sec.)
562
19.09.2014

HTTP SPECIFIC
URL
Enter the URL the sensor connects to. It has to be URL encoded! If
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.
below.
Request Method

below.
Postdata
This field is only visible when POST is selected in the Request

Met hod setting above. Please enter the data part for the POST
Content Type
This setting is only visible when POST is selected in the 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
19.09.2014
This field is only visible when Cust om is selected above. Define the
content type which is needed, e.g., XML, JSON, HTTP.
563

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 (introduced in PRTG v13.x.7). 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 will execute
an external exe. Thus, this method will need 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, i.e., this sensor does not use the IP
Address/DNS value of the parent device automatically then.
SSL SPECIFIC
SSL Method
between:
SSL V2
SSL V3
TLS V1
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 SSL settings. SSL V2 is not available. You
can choose between:
SSL V3
TLS V1
SSL V3 or TLS V1: This is the default setting.
564
19.09.2014


Check SSL Certificates
Specify if the certificate of the monitored URL will be checked.

Choose between:
Do not check used cert ificat es: This the default setting.
Check if t he used cert ificat es are t rust ed: If the certificate of
the server is not trusted, the sensor will go into a Down status
and display a corresponding message.
TLS protocol.
ADVANCED SENSOR DATA

Protocol Version
Define the HTTP protocol version that will be used when

connecting to the URL. Choose between:
HTTP 1.0
HTTP 1.1: This is the default setting.
User Agent
Choose which user agent string will be sent by this sensor when
connecting to the URL defined above. Choose between:
Use PRTG's Default St ring: Do not enter a specific user agent,
use default setting. Usually, this is: Mozilla/5.0 (compatible; PRTG
Network Monitor (www.paessler.com); Windows)
Use a Cust om St ring: Use a custom user agent. Define below.
Custom User Agent
This field is only visible if custom user agent is enabled above.

Enter a string which will be used as user agent when connecting to
the URL specified above.
Content Changes
Define what will be done in case the content of the monitored web
page (element) changes. You can choose between:
message indicating that the web page content has changed. In
to trigger a notification 2227 whenever the web page content
changes.
Check For Existing Key

Words (Positive)
19.09.2014
Define whether the the result at the configured URL will be

checked for keywords. Choose between:
565


Disable: Do not search for keywords.
Enable key word check (posit ive): In the result returned at the
URL, check if a key word exists.
Note: The content check is only intended for html websites and
might not work with other target URLs.
Response Must Include This field is only visible if keyword checking is enabled above.
Define which string must be part of the source code at the given
URL. You can either enter plain text or a Regular Expression 2587 . If
the data does not include the search pattern, the sensor will be
set to an error state. Please enter a string.
For Key Word Search
Use
Define in which format you have entered the search expression in

the field above.
Plain Text : Search for the string as plain text. The characters *
and ? work here as placeholder, whereas * stands for no or any
number of characters and ? stands for exactly one character (as
known from Windows search). This behavior cannot be disabled,
so the literal search for these characters is not possible with
plain text search.
Regular Expression: Treat the search pattern as a Regular
Expression 2587 .

Words (Negative)

Enable key word check (negat ive): In the result returned at the
URL, check if a key word does not exist.
Response must not

include
This field is only visible if keyword checking is enabled 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
2587 . If the data does include this string, the sensor will be set to an
error state. Please enter a string.
For Key Word Search

Use

the field above.
566
19.09.2014


plain text search.
Expression 2587 .
Limit Download (kb)
Enter a maximum amount of data that will be transferred 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 will be done 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). 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 2611 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, e.g. 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 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 won't check for content.
AU THENTICATION
Authentication
Define if the web page at the configured URL need authentication.

Choose between:
No aut hent icat ion needed
Web page needs aut hent icat ion
19.09.2014
567

AU THENTICATION
User
This field is only visible if authentication is enabled above. Enter a

username. Please enter a string.
Password

password. Please enter a string.
Authentication Method
This field is only visible if authentication is enabled above. Please

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 will transmit 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.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
568

19.09.2014

Inherited Settings
described below.

HTTP Proxy Settings

Name

Port
User

Password

19.09.2014
569

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
570
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
571


menu bar.
Dependency
dependent on.
Delay (Seconds)
572
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
573


More
Knowledge Base: Which user agent should I use in the HTTP Advanced sensor's settings?

Notifications
Others
574
141
section.
19.09.2014

32 HTTP Apache ModStatus PerfStats Sensor
6.8.32 HTTP Apache M odStatus PerfStats Sensor

The HTTP Apache ModStatus PerfStats sensor monitors performance statistics of an Apache
web server using mod_status over HTTP. It can show the CPU load, the uptime (in seconds), the
requests per second, the bytes per request, and the number of current busy and idle worker
threads of the Apache at scan time.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
HTTP SPECIFIC
Timeout (Sec.)
19.09.2014
575

HTTP SPECIFIC
URL
Please 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. 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.
SSL SPECIFIC
SSL Method
between:
SSL V2
SSL V3
TLS V1
TLS protocol.
AU THENTICATION
Authentication

Choose between:
User

Password

576
19.09.2014

AU THENTICATION

Choose between:
as plain text!
for single sign-on.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
19.09.2014

577

Inherited Settings
described below.

HTTP Proxy Settings

Name

Port
User

Password

578
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
579


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
580
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
581

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

582
19.09.2014


Notifications
Others
19.09.2014
141
section.
583

33 HTTP Apache ModStatus Totals Sensor
6.8.33 HTTP Apache M odStatus Totals Sensor

The HTTP Apache ModStatus Totals sensor monitors accesses and transfered data (in kBytes)
of an Apache web server using mod_status over HTTP.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
HTTP SPECIFIC
Timeout (Sec.)
584
19.09.2014

HTTP SPECIFIC
URL
Please 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. 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.
SSL SPECIFIC
SSL Method
between:
SSL V2
SSL V3
TLS V1
TLS protocol.
AU THENTICATION
Authentication

Choose between:
User

Password

19.09.2014
585

AU THENTICATION

Choose between:
as plain text!
for single sign-on.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
586

19.09.2014

Inherited Settings
described below.

HTTP Proxy Settings

Name

Port
User

Password

19.09.2014
587

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
588
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
589


menu bar.
Dependency
dependent on.
Delay (Seconds)
590
19.09.2014

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

19.09.2014
591


Notifications
Others
592
141
section.
19.09.2014

34 HTTP Content Sensor
6.8.34 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 [ ].

Add Sensor
HTTP SPECIFIC
Value Type
Define what kind of values your HTML file gives back. Choose
between:
Int eger: An integer is expected as return value.
a buffer overflow.
Note: The sensor cannot handle string values.
Number of Channels
Define how many values your HTML file gives back. Each value will
be handled in its own sensor channel. Each value must be placed
between square brackets [ ]. Enter the number of bracket-value
pairs that will be returned at the defined URL. Note: Do not enter a
number less than the number of values returned. Otherwise you
will get an error message.
Sensor Settings
19.09.2014
593


Sensor Name

Tags

Priority
(top priority).
HTTP SPECIFIC
Timeout (Sec.)
Script 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.
Value Type
The kind of values the HTML file gives back. Once a sensor is
anew.
SSL SPECIFIC
SSL Method
between:
SSL V2
594
19.09.2014

SSL SPECIFIC
SSL V3
TLS V1
TLS protocol.

Content Changes
Define what will be done in case the content of the monitored web
page changes. You can choose between:
message indicating that the web page content has changed. In
to trigger a notification 2227 whenever the web page content
changes.
Sensor Result
Choose between:
(ID].t xt "): Store the last result received to the "Logs (Sensors)"
AU THENTICATION
Authentication

Choose between:
19.09.2014
595

AU THENTICATION
User

Password


Choose between:
as plain text!
for single sign-on.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
596

19.09.2014

Example
At the URL http://www.example.com/status.html a PHP script is giving back 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 will call 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.
Note: If you define the number of channels as 1, only the first value will be read by the
sensor; the second value will be ignored. Using 3 as number of channels will result in a
sensor error message.
Inherited Settings
described below.
19.09.2014
597


HTTP Proxy Settings

Name

Port
User

Password

598
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
599


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
600
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
601

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

602
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
603

35 HTTP Full Web Page Sensor
6.8.35 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. The sensor shows the loading time of the
full page. Note: Be careful with this sensor, as it can generate considerable internet traffic if
used with a low scanning interval!
type of sensor.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
604
19.09.2014

FU LL PAGE DOWNLOAD SETTINGS

Timeout (Sec.)
URL
Please enter the URL the sensor will load. It has to be URL
Browser Engine
Define which browser will be used to load the web page. Choose
between:
Chromium (recommended): Use the "WebKit" engine that is
delivered with PRTG to perform the loading test. With each
scanning interval, PRTG will load the URL defined above in an
instance of "Chromium" and measure the time until the page is
fully loaded. This is the recommended setting.
Phant omJS (Headless Webkit ): Use the "PhantomJS" engine. This
engine can have a high impact on your probe system's CPU and
memory load, but there are additional options for result handling
available (see below).
Int ernet Explorer: With each scanning interval, the URL defined
above is loaded in the background in an instance of Internet
Explorer. PRTG uses the Internet Explorer of the system running
the PRTG probe. Note: For full functionality we strongly
recommend installing Internet Explorer 8 or higher on the system
running the PRTG probe. The probe machine is either the local
system (on every node, if on a cluster probe), or the system
running the remote probe 2589 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
browser engine. Choose between:
Use securit y cont ext of probe service (default ): Run the
browser engine under the same Windows user account the
probe is running on. By default, this is the local Windows
"system" user account (if not manually changed).
19.09.2014
605


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, this is the recommended
setting here.
Result Handling
This setting is only visible if the PhantomJS engine is selected

above. This browser engine can render and store screenshots of
the loaded web page. Choose between:
Discard loaded web page (recommended): Do not store the
requested web page.
St ore lat est screenshot of t he web page: Render and store
the last result of the web page to the "Logs (Sensors)" directory
(on the remote system, when used on a remote probe; on the
Master node, if in a cluster). This is for debugging purposes. The
file will be overridden with each scanning interval. It will be
named after the pattern "Fullpage of Sensor (ID).jpg". For
St ore ongoing screenshot s of t he web page (use wit h
caut ion!): Render and store one new screenshot of the web
page with each sensor scan, and store the pictures in the
"Screenshots (Fullpage Sensor)" directory (on the remote system,
when used on a remote probe). For information on how to find
the folder used for storage, please see Dat a St orage 2611
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, a very high amount of data can
be created! Use with care, and make sure you set appropriate
data purging limits in the Sy st em Administ rat ionCore &
Probes 2383 settings.
Note: If necessary, you can change the window size of the
rendered screenshots. See section More 612 for details.
Authentication
This setting is only visible if the PhantomJS engine is selected

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 will automatically try
using HTTP Basic authentication (BA) or Windows NT LAN Manager
(NTLM) to access the web page with authentication. Enter the
credentials below. Note: The option basic access authentication
will forward the credentials in plain text!
606
19.09.2014


User
This setting is only visible if the PhantomJS engine with

authentication is selected above. Enter the user name for the web
page.
Password
This setting is only visible if the PhantomJS engine with

authentication is selected above. Enter the password for the web
page.
Inherited Settings
described below.
19.09.2014
607

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
608
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
609


menu bar.
Dependency
dependent on.
Delay (Seconds)
610
19.09.2014

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

19.09.2014
611

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
612
141
section.
19.09.2014

36 HTTP Push Count Sensor
6.8.36 HTTP Push Count Sensor

The HTTP Push Count sensor counts received messages which are pushed via an Hypertext
Transfer Protocol (HTTP) request to the PRTG server. It provides a URL that can be used to
push messages to the PRTG server using HTTP.
This function is known as webhook. Basically, a webhook works like a push notification:
Webhooks are usually triggered by some event (for example, a new comment to a blog post)
and send according information to a specified URL. The HTTP Push Count sensor then displays
the number of pushed and received messages.
Use the following URL to receive the HTTP requests of the webhook:
ht t p://<probe_ip>:<port_number>/<token>
Replace the parameters <probe_ip>, <port_number>, and <token> with the corresponding
values. You can define port number and identification token in the sensor settings; the "probe
IP" is the IP address of the system your PRTG probe with the sensor is running on.
Example: http://127.0.0.1:5050/XYZ123
Note: You can use several sensors with the same port and identification token. In this case,
the number of push messages will be shown in each of these sensors.
Add Sensor
Sensor Settings

Sensor Name
19.09.2014

613


Tags

Priority
(top 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.
614
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
615

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
616
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
617


menu bar.
Dependency
dependent on.
Delay (Seconds)
618
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
619

37 HTTP Push Data Sensor
6.8.37 HTTP Push Data Sensor

The HTTP Push Data sensor displays data from received messages which are pushed via an
Hypertext Transfer Protocol (HTTP) request to the PRTG server. It provides a URL that can be
used to push messages to the PRTG server using HTTP.
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
620
19.09.2014

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
621

HTTP PU SH
Request Method

Port
creation.
622
19.09.2014

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

Chart Type

for each channel.
19.09.2014
623

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
624
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
625


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
626
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
627

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

Notifications
Others
628
141
section.
19.09.2014

38 HTTP Push Data Advanced Sensor
6.8.38 HTTP Push Data Advanced Sensor

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

Add Sensor

Sensor Name

Tags

Priority
(top priority).
630
18.11.2014

HTTP PU SH
Request Method

Port
creation.
18.11.2014
631

HTTP PU SH DATA
No Incoming Data
Define which status the sensor attains 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

Chart Type

for each channel.
632
18.11.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
18.11.2014
633

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
634
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
635


menu bar.
Dependency
dependent on.
Delay (Seconds)
636
18.11.2014

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

Notifications
Others
18.11.2014
141
section.
637

39 HTTP SSL Certificate Expiry Sensor
6.8.39 HTTP SSL Certificate Expiry Sensor

The HTTP SSL Certificate Expiry Sensor checks a specific https-URL and returns the number of
days remaining until the site's SSL certificate expires. It shows a Warning when only 60 days
are left, and a Down status 121 when only 30 days are remaining until the certificate expires.
The sensor reports an error if the certificate is revoked.
Note: It might be necessary to run the PRTG probe service with administrative rights if this
sensor does not work (it might show a timeout error with code PE018 without according
rights).
Note: This sensor type might not work on probes running on Windows Server 2003 (including
SP1 and SP2).
type of sensor.

Add Sensor
Sensor Settings

Sensor Name
638

20.11.2014


Tags

Priority
(top priority).
SENSOR SETTINGS
URL
Enter the absolute URL to check (this sensor does not use the IP
Address/DNS Name of the parent device). It has to be URL
encoded.
SSL Connection
Define the encryption of the connection to the URL configured

above. Choose between:
Use TLS (recommended): The sensor tries to connect via TLS. If
this does not work, the sensor shows a Down status.
Use SSLv3 if available (not recommended): The sensor tries to
connect via TLS or SSL and determines the correct encryption
automatically.
Force usage of SSLv3 (not recommended): The connection
must be established using SSLv3. Otherwise, the sensor goes
into Down status.
Note: The force SSLv3 method does not work when the
requested URL uses forward secrecy. See section More 645 .
Certificate Name
Validation
Define if you want to check if the defined URL matches the

certificate. Choose between:
The cert ificat e must mat ch t he DNS name: The sensor
compares the certificate and the DNS name. If they do not match,
the sensor shows a Down status.
Accept any cert ificat e: The sensor does not compare the
certificate and the DNS name.
20.11.2014
639

DEBU G OPTIONS
Sensor Result
between:

HTTP Proxy Settings

Name

Port
User

Password

640
20.11.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
20.11.2014
641

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
642
20.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
20.11.2014
643


menu bar.
Dependency
dependent on.
Delay (Seconds)
644
20.11.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: My HTTP sensors could not create an SSL secure channel and are down.
What can I do?

20.11.2014
645

Notifications
Others
646
141
section.
20.11.2014

40 HTTP Transaction Sensor
6.8.40 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 returns the loading time.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
HTTP SPECIFIC
Timeout (Sec.)
19.09.2014
Enter a timeout in seconds for all HTTP requests. If the complete

transaction takes longer than this value the request is aborted and
an error message is triggered. The maximum value is 900 seconds
(15 minutes).
647

HTTP SPECIFIC
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 the transaction is
aborted and an error message is triggered. 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 (introduced in PRTG v13.x.7). 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 will execute
an external exe. Thus, this method will need 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, i.e., this sensor does not use the IP
Address/DNS value of the parent device automatically then.
SSL SPECIFIC
SSL Method
between:
SSL V2
SSL V3
TLS V1
648
19.09.2014


SSL Method
When using the compatibility mode, the SSL specific settings are a
bit different to the default SSL settings. SSL V2 is not available. You
can choose between:
SSL V3
TLS V1
SSL V3 or TLS V1: This is the default setting.
Check SSL Certificates
Specify if the certificate of the monitored URL will be checked.

Choose between:
Do not check used cert ificat es: This the default setting.
Check if t he used cert ificat es are t rust ed: If the certificate of
the server is not trusted, the sensor will go into a Down status
and display a corresponding message.
TLS protocol.

Limit Download (kb)
Enter a maximum amount of data that will be transferred per every

single request. If you set content checks below, please be aware
that only the content downloaded within this limit can be checked
for certain search expressions.
Cookie Management
Select if cookies will be 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.
Result Handling
Define what will be done with the web page loaded at the given
URL. Choose between:
Discard HTML result : Do not store the requested web page.
19.09.2014
649


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). This is for debugging purposes, especially in
combination with content checks. The file will be overridden with
AU THENTICATION
Authentication

Choose between:
User

Password


Choose between:
as plain text!
for single sign-on.
TR ANSACTION U R L
You can define up to 10 different transaction URLs which will all be called in a row. Only if
the complete transaction can be completed, the sensor will be in an Up status 121 . 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.
650
19.09.2014

TR ANSACTION U R L
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
Request Method

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

Words (Positive)
Define whether the result at the configured URL will be checked

for keywords. Choose between:
Enable key word check (posit ive): In the result returned at the
URL, check if a key word exists.
19.09.2014
651

TR ANSACTION U R L
Response Must Include Define which string must be part of the web at the given URL. If the
data does not include this string, the sensor will be set to an error
state. Please enter a string. Note: Only simple text search is
available here. The characters * and ? work here as placeholder,
whereas * stands for no or any number of characters and ? stands
for exactly one character (as known from Windows search). This
behavior cannot be disabled, so the literal search for these
characters is not possible.
Words (Negative)

Enable key word check (negat ive): In the result returned at the
URL, check if a key word does not exist.
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 be set to an
error state. Please enter a string. Note: Only simple text search is
available here. The characters * and ? work here as placeholder,
whereas * stands for no or any number of characters and ? stands
for exactly one character (as known from Windows search). This
behavior cannot be disabled, so the literal search for these
characters is not possible.
Inherited Settings
described below.
652
19.09.2014


HTTP Proxy Settings

Name

Port
User

Password

19.09.2014
653

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
654
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
655


menu bar.
Dependency
dependent on.
Delay (Seconds)
656
19.09.2014

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

19.09.2014
657

More
Knowledge Base: Configuration Tips for HTTP Transaction Sensors needed

Notifications
Others
658
141
section.
19.09.2014

41 HTTP XML/REST Value Sensor
6.8.41 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
return the values of specific nodes.
type of sensor.


Add Sensor
SENSOR SETTINGS
Channel Name
Enter a name for the channel which will display the value at the
given URL. The name can be changed later in the Sensor Channels
Set t ings 2220 .
Sensor Settings
18.11.2014
659


Sensor Name

Tags

Priority
(top 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.
670 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 669 section below.
Note: You can try using XPath syntax here but it does not work in
all cases and we do not provide any technical support for XPath
issues. For further documentation about XPath, please see More
659 section below.
HTTP Username
660
If the URL requires authentication, enter the username. Please

18.11.2014

SENSOR SETTINGS
HTTP Password
If the URL requires authentication, enter the password. Please

Sensor Value
Define what value this sensor shows. Choose between:

Use t he value of t he select ed X ML node: Return the value that
the sensor finds at the specified XML node. If this is non-numeric,
the sensor shows 0.
Use t he number of occurrences of t he select ed X ML node or
it s children/siblings: Return the number of occurrences found.
Define further below.
Count XML Nodes
This setting is only visible if you enable the return number option
above. Define which count the sensor shows. Choose between:
Occurrences of t he select ed X ML node: Return how often the
defined XML node occurs at the defined URL.
Child nodes of t he select ed X ML node: Return the number of
child nodes that exist below the node at the defined URL.
Sibling nodes of t he select ed X ML node: Return the number
of sibling nodes that exist next to the node at the defined URL.
Namespaces
Define whether namespaces in the XML document are used or not.

Choose between:
Use Namespaces: Process the value you enter in the "XML Node
(and optional property)" field including possibly existing
namespace information.
Remove Namespaces: Ignore namespace information in the XML
document and process the value you enter in the "XML Node
(and optional property)" field as node names only.
For more information see About Namespaces
Content Type in
Header
670
section below.
Choose if PRTG includes content-type="text/xml" 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.
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
18.11.2014
This field is only visible when you enable the custom option above.
Enter a custom content type like text/xml or text/html.
661

SENSOR SETTINGS
HTTP Headers
Optionally enter a list of custom HTTP headers with theirs

respective values that you want to transmit to the URL you define
above. The syntax of a list with header-value pairs is
header1:value1|header2:value2|...|headerx:valuex
Note: The sensor does not accept header field names that include
a dash (-) character. If you want to use such a HTTP header, please
leave out the dash of the name. For example, enter
ContentType:value instead of Content-Type:value.
Example: From:johnqpublic@example.com|AcceptLanguage:en-us
Note: Ensure that the HTTP header statement is valid! Otherwise,
the sensor request will not be successful.
Characters to Remove
This field is only visible if you enable the "use value of XML node"
option above. Optionally enter a string that the sensor removes
from the returned XML value. Use this to remove any unwanted
characters from the result, for example, a thousands separator
from numeric values. Please enter a string or leave the field empty.
Decimal Delimiter
This setting is only visible if you enable the "use value" option
above. If the sensor value of the selected XML node is of the type
float, you can define any character here which is handled as the
decimal delimiter. Enter one character or leave the field empty.
Custom Message
Optionally enter a custom sensor message. Use %1 as a

placeholder to automatically fill in the returned XML value. Please
SSLv3 Connection
Define if you want to allow SSLv3 only for connections to the URL
configured above. Choose between:
Use SSLv3 if available
Force usage of SSLv3
Note: The force method does not work when the requested URL
uses forward secrecy. See section More 671 .
If Value Changes
change.
662
18.11.2014

SENSOR SETTINGS
Unit String
Enter a string that will be added to the values as a unit description.

This is for display purposes only.
DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
18.11.2014

663

Inherited Settings
described below.
664
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
665


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
666
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
667

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
668
18.11.2014

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
18.11.2014
669

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.

670
18.11.2014

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?

Notifications
Others
18.11.2014
141
section.
671

42 Hyper-V Cluster Shared Volume Disk Free Sensor
6.8.42 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 and shows the available disk space.
Note: The parent device for this sensor must be a Windows server running Hyper-V.
type of sensor.
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
680
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).

672
18.11.2014

Add Sensor
In order to monitor cluster disks, PRTG will create one sensor for each disk. The settings you
make in this dialog are valid for all of the sensors that are created.
DISK FR EE SETTINGS
Disk
head. Note: Please make sure 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've set up monitoring. For detailed information, please see
Sensor Settings

Sensor Name

Tags

18.11.2014
673


Priority
(top priority).
DISK FR EE SETTINGS
Disk
Shows further information about the disk. Once a sensor is

anew.
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
674
18.11.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
18.11.2014
675

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
676
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
677


menu bar.
Dependency
dependent on.
Delay (Seconds)
678
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
679

More
Knowledge Base: Why don't my Hyper-V sensors work after changing names?

Notifications
Others
680
141
section.
18.11.2014

43 Hyper-V Host Server Sensor
6.8.43 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. It shows CPU usage in percent of
guests, hypervisor, and total, as well as host health critical values, the number of deposited
pages, and network traffic. Network traffic sums up the total bytes per second (received and
sent) on all ports of your virtual switch.
Note: The parent device for this sensor must be a Windows server running Hyper-V.
Note: By default, this sensor type uses a hybrid approach, first trying to query data via
Windows Performance Counters (which needs less system resources), and using Windows
Management Instrumentation (WMI) as a fallback in case Performance Counters are not
available. When running in fallback mode, the sensor will re-try to connect via Performance
Counters after 24 hours. You can change the default behavior in the Windows Compat ibilit y
Opt ions of the parent device's settings 293 this sensor is created on.
Sensors using the Windows Management Instrumentation (WMI) protocol have high impact on
the system performance! Try to stay below 200 WMI sensors per probe 77 . Above this number,
please consider using multiple Remot e Probes 2589 for load balancing.
section.
2495

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

In order for this sensor to work with Windows Performance Counters, please make sure a
Windows version 2008 or later is installed on the computer running the PRTG probe: This is
either on the local system (on every node, if on a cluster probe), or on the system running a
remote probe 2589 .
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.
19.09.2014
681

To enable the service, please log in to the respective computer and open the services
manager (e.g. via services.msc). In the list, find the respective service and set its Start Type to
Automatic.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
Sensor Result
between:
682
19.09.2014


SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
683

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
684
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
685


menu bar.
Dependency
dependent on.
Delay (Seconds)
686
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
687

44 Hyper-V Virtual Machine Sensor
6.8.44 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. It shows CPU
usage in percent of guests, hypervisor, and total, as well as disk read and write values, per
second.
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: In order 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.
2495


remote probe 2589 .
688
26.09.2014


work.
Automatic.
Add Sensor
In order to monitor virtual machines, PRTG will create one sensor for each machine. The
settings you make in this dialog are valid for all of the sensors that are created.

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: Please make sure the name of your VMs do not
contain unsupported characters, especially avoid the hash ('#') sign.
We recommend to not rename virtual machines once you've set up
monitoring. For detailed information, please see More 695 section
below.
Sensor Settings
26.09.2014
689


Sensor Name

Tags

Priority
(top priority).

GUID
Shows the Globally Unique Identifier (GUID) of the virtual machine

monitored by this sensor. Once a sensor is created, you cannot
Name
Shows the name of the virtual machine monitored by this sensor.

Once a sensor is created, you cannot change this value. It is
shown for reference purposes only. If you need to change this,
Name
Shows the name of the host server. Once a sensor is created, you
Powered Off VMs
Choose how the sensor will react to a virtual machine that is

powered off. Please choose between:
Alarm when powered off (default ): The sensor will change to a
Down 121 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
690
between:
26.09.2014


SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
26.09.2014
691

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
692
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
693


menu bar.
Dependency
dependent on.
Delay (Seconds)
694
26.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: Why don't my Hyper-V Virtual Machine / Network Adapter Sensor work after
changing names?

Notifications
26.09.2014
695

Others
696
141
section.
26.09.2014

45 Hyper-V Virtual Network Adapter Sensor
6.8.45 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. It shows sent and received bytes, packets, broadcast packets, directed packets, and
multicast packets, per second.
Note: The parent device for this sensor must be a Hyper-V server.
section.
2495


remote probe 2589 .

work.
19.09.2014
697

Automatic.
Add Sensor
In order to monitor network adapters, PRTG will create one sensor for each adapter. The

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.
You can also select and deselect all items by using the check box
in the table head. Note: We recommend to not rename virtual
machines once you have set up monitoring. Renaming them will
also change the internal virtual network adapter names, causing
the monitoring to be interrupted. For detailed information about
virtual machine naming, please see More 695 section below.
Sensor Settings

Sensor Name
698

19.09.2014


Tags

Priority
(top 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
Choose between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
699

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
700
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
701


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
702
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
703

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: Why don't my Hyper-V Virtual Machine / Network Adapter Sensor work after
changing names?

Notifications
704
19.09.2014

Others
19.09.2014
141
section.
705

46 Hyper-V Virtual Storage Device Sensor
6.8.46 Hy per-V Virtual Storage Device Sensor

The Hyper-V Virtual Storage sensor monitors a virtual storage device running on a Microsoft
Hyper-V host server, via Windows Performance Counters or Windows Management
Instrumentation (WMI), as configured in the "Windows Compatibility Options" of the parent
device. It shows read and write values in second, and the number of errors.
Note: The parent device for this sensor must be a Hyper-V server. Live Migration is not
supported.
section.
2495


remote probe 2589 .

work.
706
19.09.2014

Automatic.
Add Sensor
In order to monitor storage devices, PRTG will create one sensor for each device. The settings
you make in this dialog are valid for all of the sensors that are created.
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

Tags

19.09.2014
707


Priority
(top priority).
HYPER -V VIR TU AL STOR AGE DEVICE SETTINGS

Virtual Storage Device
Shows the unique name of the device monitored by this sensor.

Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
708
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
709

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
710
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
711


menu bar.
Dependency
dependent on.
Delay (Seconds)
712
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
713

47 IMAP Sensor
6.8.47 IM AP Sensor
The IMAP sensor monitors a mail server using Internet Message Access Protocol (IMAP) and
shows the server's response time as well as the 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 724 .
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.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
714
19.09.2014

47 IMAP Sensor
IMAP SPECIFIC
Timeout (Sec.)
Enter a timeout in seconds for the SMTP connect. If the reply takes
is triggered.
Port
Enter the number of the port that will be used to connect via IMAP.
For non-secure connections usually port 143 is used; usually port
993 for SSL connections. The actual setting depends on the server
you are connecting to. Please enter an integer value. We
recommend using the default value. If you do not get a connection,
please try another port number.
AU THENTICATION
Authentication Type
Select the kind of authentication for the IMAP connection. Choose

between:
Username/Password: Authenticate at the IMAP server via
username and password.
Simple Aut hent icat ion and Securit y Lay er (SASL): Use a
secure connection for the authentication at the IMAP server.
Username
Enter a username for IMAP authentication. Please enter a string or

leave the field empty. Note: If you leave this field empty, PRTG will
not attempt to log in to the mail server. The sensor will show a
green Up status if the IMAP server is available.
Password
Enter a password for IMAP authentication. Please enter a string or

leave the field empty. Note: If you leave this field empty, PRTG will
not attempt to log in to the mail server. The sensor will show a
green Up status if the IMAP server is available.
TLS (Transport-Level
Security)
This setting is only relevant if authentication is used. Choose if a

secure connection via TLS/SSL will be used. Choose between:
Don't use
Use
19.09.2014
715

47 IMAP Sensor
SSL-Method
This field is only visible if you enabled security above. Select the
SSL method that the sensor uses when connecting to the server.
connection problems, try another setting. Choose between:
SSL V2
SSL V2 or V3
SSL V3
TLS V1
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 mails in the IMAP mail account.
Process emails in t his mailbox: Login in to the IMAP mail
account and check the mails contained there. Define further
options below.
Mailbox Name
This field is only visible if email content processing is enabled

above. Enter the name of the mailbox (e.g. the name of the IMAP
folder) that will be checked. 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: Please make sure that you
do not manually edit mails in this mailbox with another mail client,
as this can lead to malfunctions of this sensor's email identification.
Identify by "From" Field
This option is only visible if email content processing is enabled

above. Define if you want to check the "From" 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 Regular Expressions 2587 section.
When using a search, the sensor will scan all emails from the
newest to the oldest. Note: The scan will be finished with the first
match! That means: After a match is found in one email, there will
be no further checks performed in older emails.
716
19.09.2014

47 IMAP Sensor
IDENTIFY EMAIL
Search For
This field is only visible if a check is enabled above. Enter a search

string using the method defined above.
Identify by "Subject"
Field

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
Search For

Identify by Mail Body

above. Define if you want to check the mail body of the emails.
Choose between:
Don't check: Do not check the mail body.
Check using st ring search: Check the mail body using simple
string search.
Check using regular expression: Check the mail body using a
regular expression. For more information about syntax, please
Search For

Check Last Message

Date

above. 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.
19.09.2014
717

47 IMAP Sensor
IDENTIFY EMAIL
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. Only emails that are younger will
be processed. If there is no matching email in the defined time
span, the sensor will show a Down status.
Warning Threshold
(Hours)
Enter the maximum age in hours. Only emails that are younger will
be processed. If there is no matching email in the defined time
span, the sensor will show a Warning status.
SENSOR BEHAVIOR
Set to Alarm
This setting is only visible if email content check is enabled above.

Define in which cases the sensor will show a Down status. Choose
between:
If subject cont ains
If subject does not cont ain
If mail body cont ains
If mail body does not cont ain
Alway s: Always set this sensor to a Down status in case any
emails could be identified.
Never: Never set this sensor to a Down status based on email
content.
Check Method
This setting is only visible if an if-condition is selected 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 2587 section.
Search Text
718
This setting is only visible if an if-condition is selected above. Enter

a search string using the method defined above.
19.09.2014

47 IMAP Sensor
SENSOR BEHAVIOR
Error Message
This setting is only visible if an alarm condition is selected above.

Define the message that will be shown in case the sensor shows
a Down status.
Set to Warning

Define in which cases the sensor will show a Warning status.
Choose between:
If subject cont ains
If subject does not cont ain
If mail body cont ains
If mail body does not cont ain
Alway s: Always set this sensor to a Warning status in case any
emails could be identified.
Never: Never set this sensor to a Warning status based on email
content.
Check Method
This setting is only visible if an if-condition is selected 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 2587 section.
Search Text
This setting is only visible if an if-condition is selected above. Enter

a search string using the method defined above.
Warning Message
This setting is only visible if a warning condition is selected above.

Define the message that will be shown in case the sensor shows
a Warning status.
No Matching Mail
Behavior

Define how the sensor will react if no matching emails are found in
the mailbox that is being scanned. Choose between:
Set sensor t o "Down" st at us
Set sensor t o "Warning" st at us
None: Don't do anything in this case.
19.09.2014
719

47 IMAP Sensor
SENSOR BEHAVIOR
Message
This field is only effective if a sensor change in case of no matching

mail is defined above. Define the message that will be shown in
case the sensor could not find any matching emails. It will be
shown together with a Warning or Down status, just as defined
above.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
720
19.09.2014

47 IMAP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
721

47 IMAP Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
722
19.09.2014

47 IMAP Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
723

47 IMAP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
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?

724
19.09.2014

47 IMAP Sensor
Notifications
Others
19.09.2014
141
section.
725

48 INI File Content Check Sensor
6.8.48 INI File Content Check Sensor

The INI File Content Check sensor reads an *.ini file. It indicates if the file exists and if a
specified section and field are found. The sensor returns the field's integer value (or -1 if the
field does not contain an integer). It will show a Warning status if a section or field is not
found, and a Down status if the file could not be opened.
type of sensor.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
726
19.09.2014

SENSOR SETTINGS
INI File Name
enter C:\Windows\win.ini. If the file is located on a network device
part (you would only enter share\folder\file.ini). The server part (\
Please enter a valid path and file name. Note: In order to provide
any shares, the LanmanServer "Server" Windows service must be
INI Section
Define the section inside the INI file you would like to check. A
section within the INI file is denoted in square brackets [ ]. Enter
the section name without the brackets here, for example, enter
Mail. This value is not case sensitive. If the section is not found, the
sensor will show a Warning status.
INI Field
Define the field inside the section you would like to check. In the
INI file, a field name is written before an equal sign =, followed by its
value. Enter the field name here, for example, enter MAPI. This value
is not case sensitive. The sensor will return the value of this field,
i.e. the value on the right side of the equal sign. If the field is not
found, the sensor will show a Warning status.
If Value Changes
Define what will be done in case the value of this sensor changes.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
727

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
728
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
729


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
730
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
731

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

Notifications
Others
732
141
section.
19.09.2014

49 IP on DNS Blacklist Sensor
6.8.49 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 and returns the number of hits found. If a DNS name is used as the parent
device's hostname, PRTG will resolve it to an IP address first.
During normal operation, there should be 0 hits and the sensor should show a green Up
status. If the IP address is found on at least one of the blacklist servers, the sensor changes to
a yellow Warning status by default. Note: You can set additional thresholds in the sensor's
Sensor Channels Set t ings 2220 , if you like.
type of sensor.

Add Sensor
Sensor Settings

Sensor Name
18.11.2014

733


Tags

Priority
(top priority).
SENSOR SETTINGS
Blacklist Servers
Define the blacklist servers that will be used for the check. You can
enter a comma separated list. Default is bl.spamcop.net. For a list
of servers, please see More 739 section below. Note: With each
scanning interval, PRTG will query all servers in the list! We
recommend you do not enter more than 10 servers to make sure
the check can be completed within the scanning interval of this
sensor. If you use too many blacklist servers, the sensor will show
a "Timeout (code: PE018)" error message.
Timeout (sec.)
Define a timeout in seconds for the check. If the reply takes longer
than this value the request is aborted and an error message is
triggered.
DEBU G OPTIONS
Sensor Result
between:
734
18.11.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
735

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
736
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
737


menu bar.
Dependency
dependent on.
Delay (Seconds)
738
18.11.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: Is there a list of anti spam black list servers?

Notifications
18.11.2014
739

Others
740
141
section.
18.11.2014

50 IPFIX Sensor
6.8.50 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. Please make sure your device supports IPFIX when using this
sensor.
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).
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.
For a general introduction to the technology behind flow monitoring, please see Monit oring
Bandwidt h via Flows 2502 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
18.11.2014
741

50 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 setting this one minute longer than the
respective timeout configured in your hardware router device.
Note: If you set this value too low, flow information might get lost!
Sampling Mode
Define if you want to use the sampling mode. This setting must
accord to the setting in the flow exporter. Choose between:
Off: The standard flow will be used.
On: Switch into sampling mode and specify the sampling rate
below.
Sampling Rate
This field is only visible when sampling mode is enabled above.

Enter a number that matches the sampling rate in your exporter
device. If the number is different, monitoring results will be
incorrect. Please enter an integer value.
Log Stream Data to

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 2611 ). 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.
742
18.11.2014

50 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.
18.11.2014
743

50 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 2572
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 2572 section.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

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
744
18.11.2014

50 IPFIX Sensor
PR IMAR Y TOPLIST
Top Connect ions
Top Prot ocols
[Any custom toplists you have added]
Inherited Settings
described below.
18.11.2014
745

50 IPFIX Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
746
18.11.2014

50 IPFIX Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
747

50 IPFIX Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
748
18.11.2014

50 IPFIX Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
749

50 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 2240 section.
More
Paessler Website: Paessler NetFlow Testers
http://www.paessler.com/tools/netflowtester
Knowledge Base: How can I change the default groups and channels for xFlow and Packet
Sniffer sensors?

Notifications
Others
141
section.
Related Topics
Filt er Rules for xFlow, IPFIX , and Packet Sniffer Sensors
2572
Channel Defint ions for xFlow, IPFIX , and Packet Sniffer Sensors
750
2576
18.11.2014

51 IPFIX (Custom) Sensor
6.8.51 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. Please make sure your
device supports IPFIX when using this sensor.
Note: In order for this sensor to work, you have to enable IPFIX export on the device. The

Add Sensor
Sensor Settings

Sensor Name
18.11.2014

751


Tags

Priority
(top 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 setting this one minute longer than the
respective timeout configured in your hardware router device.
Sampling Mode
below.
752
18.11.2014


Sampling Rate

Enter a number that matches the sampling rate in your device. If
the number is different, monitoring results will be incorrect. Please
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 2576 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

Chart Type

for each channel.
18.11.2014
753

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
754
18.11.2014

Inherited Settings
described below.
18.11.2014
755

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
756
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
757


menu bar.
Dependency
dependent on.
Delay (Seconds)
758
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
759

Toplists

Notifications
Others
141
section.
Related Topics
2572
760
2576
18.11.2014

52 IPMI System Health Sensor
6.8.52 IPM I Sy stem Health Sensor

The IPMI System Health sensor monitors the status of a system via the Intelligent Platform
Management Interface (IPMI). It can show temperature, rotation per minute of fans, voltage, and
the status of a power supply.
Note: You have to explicitly specify the credentials of the IPMI in the sensor settings.
This sensor type has predefined limits for several metrics. These limits can be changed
individually in the channel settings. For detailed information about channel limits please refer to
the section Sensor Channels Set t ings 2220 .

Add Sensor
Before you can actually add this sensor, PRTG will ask you to provide your credentials for the
Intelligent Platform Management Interface (IPMI) in the add sensor dialog 224 . Enter the
Username and the Password in the respective fields.
In order to monitor the system health via IPMI, PRTG will create one sensor for each metric you
26.09.2014
761

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

Tags

Priority
(top priority).
IPMI CR EDENTIALS
Username
Enter the username for the Intelligent Platform Management

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

Interface (IPMI). If not changed yet, this field shows the encrypted
password that you defined the sensor creation.
762
26.09.2014

IPMI SPECIFIC
Group
Shows the measurement that this sensor monitors. Once a sensor

is created, you cannot change this value. It is shown for reference
anew.
Logfile Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
26.09.2014

763

Inherited Settings
described below.
764
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
765


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
766
26.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
767

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
768
26.09.2014

More

Notifications
Others
26.09.2014
141
section.
769

53 jFlow V5 Sensor
6.8.53 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, please make sure it matches jFlow V5 and disable any
sampling option! There are several filter options available to divide traffic into different
channels.
Note: In order for the sensor to work, jFlow export of the respective version must be enabled
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). The sensor does not
support sampling, so please disable sampling in your jFlow device!
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.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
770
19.09.2014

53 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 setting this one minute
longer than the respective timeout configured in your hardware
router device.
Sampling Mode
below.
Sampling Rate

Log Stream Data to

19.09.2014
771

53 jFlow V5 Sensor
JFLOW V5 SPECIFIC SETTINGS

Ot her channel.
only.

Channel Selection
UDP and TCP.
Ot her.
channel.
772
19.09.2014

53 jFlow V5 Sensor

FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
773

53 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.
774
19.09.2014

53 jFlow V5 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
775

53 jFlow V5 Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
776
19.09.2014

53 jFlow V5 Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
777

53 jFlow V5 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
778
19.09.2014

53 jFlow V5 Sensor
Toplists
More
Knowledge Base: Where is the volume line in graphs?

Notifications
Others
141
section.
Related Topics
2572
19.09.2014
2576
779

54 jFlow V5 (Custom) Sensor
6.8.54 jFlow V5 (Custom) Sensor

The jFlow V5 (Custom) sensor receives traffic data from a jFlow V5 compatible device and
shows the traffic by type. On your hardware device, please make sure it matches jFlow V5 and
disable any sampling option! In this custom sensor, you can define your own channel
definitions to divide traffic into different channels.
Note: In order for the sensor to work, jFlow export of the respective version must be enabled
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). The sensor does not
support sampling, so please disable sampling in your jFlow device! 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.

Add Sensor
Sensor Settings

Sensor Name

Tags

780
19.09.2014


Priority
(top 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
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 setting this one minute
longer than the respective timeout configured in your hardware
router device.
Sampling Mode
below.
19.09.2014
781

JFLOW SPECIFIC SETTINGS

Sampling Rate

Channel Definition

please see Channel Defint ions for xFlow and Packet Sniffer
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 analyse.
Log Stream Data to

Ot her channel.
only.
FILTER ING
Include Filter
section.
Exclude Filter
782
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
19.09.2014
783

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
784
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
785


menu bar.
Dependency
dependent on.
Delay (Seconds)
786
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
787

Toplists
More

Notifications
Others
141
section.
Related Topics
2572
788
2576
19.09.2014

55 LDAP Sensor
6.8.55 LDAP Sensor

The LDAP sensor monitors directory services using Lightweight Directory Access Protocol
(LDAP), connecting to the server trying a "bind". It shows the response time. If the server does
not respond or authentication fails, an error message will be triggered.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
LDAP SPECIFIC
Port
19.09.2014
Enter the LDAP port number, usually port 389 for unencrypted
connections. Please enter an integer value.
789

55 LDAP Sensor
LDAP SPECIFIC
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.
Passwort
Enter the password for the entered Distinguished Name.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
790
19.09.2014

55 LDAP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
791

55 LDAP Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
792
19.09.2014

55 LDAP Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
793

55 LDAP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
794
141
section.
19.09.2014

56 Microsoft SQL Sensor
6.8.56 M icrosoft SQL Sensor

IMPOR TANT NOTICE
This sensor type is outdated. We strongly recommend you to use the Microsoft SQL v2
Sensor 804 instead. This is a new sensor type to monitor databases on Microsoft SQL
servers.
The Microsoft SQL sensor monitors a Microsoft Structured Query Language (SQL) server. It
shows the response time, the number of records, and the value. The sensor can monitor if the
database server accepts connections, processes requests, and returns an expected result
when executing a custom SQL command.
The following SQL servers are supported: SQL Server 2008, SQL Server 2005 (including SQL
Server Express / Server Compact Editions), SQL Server 2000, SQL Server 7 and MSDE (requires
OLE DB installed on the machine running the PRTG probe that accesses the server)
Add Sensor
Sensor Settings

Sensor Name

Tags

19.09.2014
795


Priority
(top priority).
SQL-SER VER SPECIFIC DATA

Timeout (sec.)

is triggered.
Instance
Enter the SQL server instance's name if you want to connect to a

"named instance". For example, such an instance's name could be
SQLEXPRESS. Note: Sometimes you will see connection strings
like SQLSERVER\SQLINSTANCE in database clients. The first part is
the server name configured under the general server settings. The
second part refers to the instance name mentioned above. Never
enter this complete string in this PRTG form, merely provide the
second part (without the backslash). Please enter a string or leave
the field empty.
Port
Define the port for the SQL connection. Choose between:

Aut omat ic: Automatically choose the right port.
Manual: Use a specific port. Define below. Standard value is
1433.
Port
This field is only visible if manual port selection is enabled above.

Define the port number for the SQL connection. Please enter an
integer value.
DATABASE
Database
Enter the name of the SQL database the sensor will connect to.
For example, such a database's name could be Northwind
Authentication
Define the kind of authentication used for the connection to the

database. Choose between:
SQL Server: Use credentials specific to the SQL server. Please
enter them below.
796
19.09.2014

DATABASE
Windows Aut hent icat ion: Use the Windows credentials defined
for the parent device this sensor is created on. Note: For
successful authentication, the defined Windows credentials must
be known to the SQL server, and SQL server and the computer
the PRTG probe is running on must be in the same domain.
User
This field is only visible if SQL server authentication is enabled

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

above. Enter the password that will be used for the database
connection.
DATA
SQL Expression

ProductName FROM Northwind.dbo.Products. When a cursor is
returned (i.e. with a SELECT statement), only the first row of data
will be processed.
Note: Executing stored procedures is currently not supported.
Record Count

counted.
Post-Processing
19.09.2014
797


Condition "Warning"

condition.
below.
provided below.
Value

value.
Condition "Down"

below.
provided below.
Value
798

19.09.2014

the field empty.
Response Must Not
include

the field empty.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
799

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
800
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
801


menu bar.
Dependency
dependent on.
Delay (Seconds)
802
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
803

57 Microsoft SQL v2 Sensor
6.8.57 M icrosoft SQL v2 Sensor

The Microsoft SQL v2 sensor monitors a database on a Microsoft SQL server and executes a
defined query. It shows the execution time of the whole request (including connection
buildup, query execution, transaction handling, disconnection), the execution time of a given
query, and the number of rows which were addressed by the query (including select
statements). It can also process the data table and show defined values in individual channels.
Note: Your SQL query must be stored in a file on the system of the probe the sensor is
Save the SQL script with the query into the \Cust om Sensors\sql\mssql subfolder of your
PRTG installation. See section Dat a St orage 2611 for more information about how to find this
path.
Note: This sensor type supports Microsoft SQL server 2005 or later.
Note: This sensor type supersedes the outdated Microsoft SQL sensor. We recommend you to
use this new sensor to monitor Microsoft SQL databases.

Add Sensor
Sensor Settings
804
26.09.2014


Sensor Name

Tags

Priority
(top priority).
DATABASE CR EDENTIALS
Port
Enter the number of the port to which this sensor connects.

Database
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.
Authentication
Select the authentication method for the connection to the SQL

Windows aut hent icat ion wit h impersonat ion: If you select this
option, the Windows credentials as defined in the settings of the
parent device will be used for the connection.
Note: The user whose credentials are used needs to have
permissions to log in to the system running the PRTG probe with
this sensor. This is required for the impersonation.
SQL server aut hent icat ion: Choose this option if you want to
use explicit credentials for the database connection.
User
This field is only visible if you selected SQL server authentication

above. Enter the username that will be used for the database
connection.
Password

connection.
26.09.2014
805

Database Timeout
(Sec.)
Enter a timeout in seconds for the request. Please enter an integer

value. If the reply takes longer than this value, the request will be
aborted and an error message is triggered. The maximum timeout
value is 900 seconds (15 minutes).
DATA
SQL Query File
Select an SQL script file that includes a valid SQL statement to

execute on the server. Once a sensor is created, you cannot
The script will be executed with every scanning interval. The list
contains SQL scripts from the database management system
specific \Cust om Sensors\sql subfolder of your PRTG installation.
Store your script there. If used on a remote probe, the file must be
stored on the system running the remote probe. If used on a
cluster probe, you must store the file on all servers running a
cluster node! For more information on how to find this path, please
see Dat a St orage 2611 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.
806
26.09.2014

DATA
Data Processing
Define if you want to process data from the database. Once a

the sensor anew. Choose between:
Just execut e t he query : If you select this option, the sensor
will only show information about the number of affected rows
and the execution time of the query.
Process dat a t able: Select this option to read and analyze the
queried data table.
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.
Sensor Channel #x
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.
26.09.2014
807

DATA
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.
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. 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. 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. Please enter an integer value.
Sensor Channel #x Key This setting is only visible if you selected the key value pair option
above. Provide the key which will be used to determine the
channel value. Please enter a string.
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
please add the sensor anew. Choose between:
Absolut e (recommended): The value will be shown as the
sensor retrieves it from the data table.
Difference: The sensor will calculate and show the difference
between the last and the current value.
Sensor Channel #x
Unit
This setting is only visible if you have selected the process data
table option above. Define the unit of the channel value. Once a
BytesBandwidth
BytesMemory
808
26.09.2014

DATA
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
For more information about the available units, please refer to the
PRTG Applicat ion Programming Int erface (API) Definit ion 2571 for
custom sensors.
Sensor Channel #x
Custom Unit
This setting is only visible if you selected the custom unit option
above. Define a unit for the channel value. Please enter a string.
Use Data Table Value in This setting is only visible if you selected the process data table
Sensor Message
option above. Define if the sensor message will show a value from
the data table. Choose between:
Disable: Do not use a custom sensor message.
Enable: Define a custom sensor message with the value of a
defined channel.
Sensor Message
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.
26.09.2014
809

DATA
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

Chart Type

for each channel.
810
26.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
26.09.2014
811

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
812
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
813


menu bar.
Dependency
dependent on.
Delay (Seconds)
814
26.09.2014

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

Notifications
26.09.2014
815

Others
816
141
section.
26.09.2014

58 MongoDB System Health Sensor
6.8.58 M ongoDB Sy stem Health Sensor

The MongoDB System Health sensor monitors the system health of a MongoDB server via
Hypertext Transfer Protocol (HTTP) and the MongoDB admin web console. It can show the
percentage of used connections and index misses, the average duration of background
flushing, as well as command, delete, insert, update, query, and get more operations per
second.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
DATABASE
Port
Enter the number of the port to which your MongoDB listens. The
default port is 27017.
Note: The sensor does not use this port. PRTG adds 1,000 to this
port number and uses the result to access the HTTP interface of
your MongoDB server.
26.09.2014
817

DATABASE
Authentication
Define if the sensor needs to authenticate at the MongoDB admin

web console. Choose between:
No aut hent icat ion required: Choose this option to connect to
the MongoDB web interface without credentials.
Aut hent icat ion required: Choose this option to authenticate
with MongoDB credentials.
User
This field is only visible if you select authentication above. Enter

the username for the MongoDB admin web console. Please enter a
string.
Password
This field is only visible if you select authentication above. Enter

the password for MongoDB admin web console. Please enter a
string.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
818

26.09.2014

Inherited Settings
described below.
26.09.2014
819

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
820
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
821


menu bar.
Dependency
dependent on.
Delay (Seconds)
822
26.09.2014

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

Notifications
Others
26.09.2014
141
section.
823

59 MySQL Sensor
6.8.59 M y SQL Sensor

IMPOR TANT NOTICE
This sensor type is outdated. We strongly recommend you to use the My SQL v2 Sensor
instead. This is a new sensor type to monitor databases on MySQL servers.
833
The MySQL sensor monitors a MySQL server. It connects to the server and shows the
response time. Additionally, it can read the number of records and a value.
The following SQL servers are supported: MySQL server 5.1, 5.0, 4.1, 4.0, and 3.23
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
824
19.09.2014

59 MySQL Sensor
MYSQL SER VER SPECIFIC DATA

Port
Define the port for the SQL connection. Choose between:

Aut omat ic: Automatically choose the right port.
Manual: Use a specific port. Define below. Standard value is
3306.
Timeout (sec.)

is triggered.
DB/SQL DATA
Database
tables or stored procedures exist. In case of the mySQL server it
also reflects a physical directory structure where your database
objects are stored. Enter the appropriate string which is the same
as you would supply when invoking the mysql.exe admin tool (with
the command line switch -p) or after the login with mysql.exe with
the command use.
User
Enter the user name that will be used for the database connection.
Password
Enter the password that will be used for the database connection.
DATA
SQL Expression

AVG(UnitPrice) FROM Products. When a cursor is returned (i.e. with
a SELECT statement), only the first row of data will be processed.
Record Count

counted.
19.09.2014
825

59 MySQL Sensor

Post-Processing
Condition "Warning"

condition.
below.
provided below.
Value

value.
Condition "Down"

below.
826
19.09.2014

59 MySQL Sensor

provided below.
Value

the field empty.
Response Must Not
include

the field empty.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
19.09.2014

827

59 MySQL Sensor
Note: For this sensor type, no port number can be set.
Inherited Settings
described below.
828
19.09.2014

59 MySQL Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
829

59 MySQL Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
830
19.09.2014

59 MySQL Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
831

59 MySQL Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
832
141
section.
19.09.2014

60 MySQL v2 Sensor
6.8.60 M y SQL v2 Sensor

The MySQL v2 sensor monitors a database on a MySQL server and executes a defined query. It
shows the execution time of the whole request (including connection buildup, query
execution, transaction handling, disconnection), the execution time of a given query, and the
number of rows which were addressed by the query (including select statements). It can also
process the data table and show defined values in individual channels.
Save the SQL script with the query into the \Cust om Sensors\sql\my sql subfolder of your
path.
Note: This sensor type supports MySQL server version 5.0 or later; it might also work with
previous versions.
Note: This sensor type supersedes the outdated MySQL sensor. We recommend you to use
this new sensor to monitor MySQL databases.

Add Sensor
Sensor Settings
26.09.2014
833

60 MySQL v2 Sensor

Sensor Name

Tags

Priority
(top priority).
Note: Regarding the Dat abase field below, the database name of the 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.
Port

Database
Authentication

834
26.09.2014

60 MySQL v2 Sensor
User

connection.
Password

connection.
Database Timeout
(Sec.)

DATA
SQL Query File

Use Transaction
executed.
26.09.2014
835

60 MySQL v2 Sensor
DATA
Data Processing

queried data table.
Handle DBNull in
Channel Values as

by
below.
value was found.
836
26.09.2014

60 MySQL v2 Sensor
DATA
Sensor Channel #x
Sensor Channel #x
Name
Sensor Channel #x
Column Number

value.
Sensor Channel #x
Column Name
Sensor Channel #x
Row Number
Sensor Channel #x
Mode
26.09.2014
837

60 MySQL v2 Sensor
DATA
Sensor Channel #x
Unit
BytesBandwidth
BytesMemory
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Message
defined channel.
838
26.09.2014

60 MySQL v2 Sensor
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
26.09.2014

839

60 MySQL v2 Sensor
SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
840
26.09.2014

60 MySQL v2 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
841

60 MySQL v2 Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
842
26.09.2014

60 MySQL v2 Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
843

60 MySQL v2 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More

Notifications
844
26.09.2014

60 MySQL v2 Sensor
Others
26.09.2014
141
section.
845

61 NetFlow V5 Sensor
6.8.61 NetFlow V5 Sensor

The NetFlow V5 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! There are several filter options available to divide traffic into different channels.
Note: In order for the sensor to work, NetFlow export of the respective version must be
enabled 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 remote probe only,
not on a cluster probe.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
846
19.09.2014

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 setting the timeout one
minute longer than the respective timeout configured in your
Sampling Mode
below.
Sampling Rate

Log Stream Data to

19.09.2014
847


Ot her channel.
only.

Channel Selection
UDP and TCP.
Ot her.
channel.
848
19.09.2014


FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
849

SENSOR DISPLAY
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
850
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
851


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
852
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
853

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
854
19.09.2014

Toplists
More
Sniffer sensors?

Notifications
Others
141
section.
Related Topics
2572
19.09.2014
2576
855

62 NetFlow V5 (Custom) Sensor
6.8.62 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.

Add Sensor
Sensor Settings

Sensor Name

Tags

856
19.09.2014


Priority
(top 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 setting the timeout one minute longer than
the respective timeout configured in your hardware router device.
Sampling Mode
below.
19.09.2014
857


Sampling Rate

Channel Definition

please see Channel Definit ions for xFlow, IPFIX , and Packet
Sniffer Sensors 2576 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 analyze.
Log Stream Data to

Ot her channel.
only.
FILTER ING
Include Filter
section.
Exclude Filter
858
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
19.09.2014
859

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
860
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
861


menu bar.
Dependency
dependent on.
Delay (Seconds)
862
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
863

Toplists
More

Notifications
Others
141
section.
Related Topics
2572
864
2576
19.09.2014

6.8.63 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.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
865


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 setting the timeout one
minute longer than the respective timeout configured in your
Sampling Mode
below.
Sampling Rate

Log Stream Data to

866
19.09.2014


Ot her channel.
only.

Channel Selection
UDP and TCP.
Ot her.
channel.
19.09.2014
867


FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
868
19.09.2014

SENSOR DISPLAY
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
19.09.2014
869

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
870
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
871


menu bar.
Dependency
dependent on.
Delay (Seconds)
872
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
873

Toplists
More
Sniffer sensors?

Notifications
Others
141
section.
Related Topics
2572
874
2576
19.09.2014

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

Add Sensor
Sensor Settings

Sensor Name

Tags

19.09.2014
875


Priority
(top 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 setting the timeout one minute longer than
the respective timeout configured in your hardware router device.
Sampling Mode
below.
876
19.09.2014


Sampling Rate

Channel Definition

please see Channel Definit ions for xFlow, IPFIX , and Packet
Sniffer Sensors 2576 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 analyze.
Log Stream Data to

Ot her channel.
only.
FILTER ING
Include Filter
section.
Exclude Filter
19.09.2014
877

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
878
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
879


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
880
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
881

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
882
19.09.2014

Toplists
More

Notifications
Others
141
section.
Related Topics
2572
19.09.2014
2576
883

65 Oracle SQL Sensor
6.8.65 Oracle SQL Sensor

IMPOR TANT NOTICE
This sensor type is outdated. We strongly recommend you to use the Oracle SQL v2
Sensor 894 instead. This is a new sensor type to monitor databases on Oracle servers.
The Oracle SQL sensor monitors an Oracle SQL server. It connects to the server and shows
the response time (measured from the time when the connection is opened to the time when
the return values of the SQL queryif configuredhave been received). Additionally, it can
read the number of records and a value.
The following SQL servers are supported: Supports Oracle servers 11g, 10g, 9i, 8i, 8.0, and 7.3,
including Oracle 10g Express, and Oracle 8i Personal and Lite editions (requires default TCP port
setting 1521).
Note: On the client computer running the PRTG probe where this sensor is created on, Oracle
Net is used for direct TCP/IP communication; OCI is not supported any more. You do not need
to install an Oracle client or define a TNSNAMES.ORA on the client computer.
Note: With Oracle version 11.2.0.4, Oracle's TCP/IP authentication method has changed. You
will encounter connection problems with credential errors when using the direct connection
mode as of this Oracle version. In this case, please install the 32-bit Oracle client on the
machine which is running the PRTG probe and choose Use Oracle client as connection mode
in the sensor settings.
Add Sensor
Sensor Settings

Sensor Name
884

19.09.2014


Tags

Priority
(top priority).
OR ACLE SPECIFIC DATA

Timeout (Sec.)

is triggered.
Port
Enter the port number that will be used for the connection. Default
value is 1521. Please enter an integer value.
Connection Mode
Select which mode you want to use to connect to the Oracle

server. Choose between:
Use direct mode (TCP/IP): Use Oracle Net for direct TCP/IP
communication.
Note: As of Oracle version 11.2.0.4, please use the Oracle client
(see sensor description above).
Use Oracle client : Use the Oracle client for communication. It
needs to be installed the machine which is running the PRTG
probe.
DB/SQL DATA
Service Name / Alias
For example, such a database's name could be orcl
User
Enter the user name that will be used for the database connection.
Password
Enter the password that will be used for the database connection.
19.09.2014
885

DATA
SQL Expression

sum(salary) FROM hr.employees. When a cursor is returned (i.e.
with a SELECT statement), only the first row of data will be
processed.
Record Count

counted.
Post-Processing
Condition "Warning"

condition.
below.
886
19.09.2014


provided below.
Value

value.
Condition "Down"

below.
provided below.
Value

the field empty.
Response Must Not
include

the field empty.
SENSOR DISPLAY
Primary Channel
19.09.2014

887

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
888
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
889


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
890
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
891

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: How do PRTG sensors connect to Oracle databases?

Notifications
892
19.09.2014

Others
19.09.2014
141
section.
893

66 Oracle SQL v2 Sensor
6.8.66 Oracle SQL v2 Sensor

The Oracle SQL v2 sensor monitors a database on an Oracle server and executes a defined
query. It shows the execution time of the whole request (including connection buildup, query
Save the SQL script with the query into the \Cust om Sensors\sql\oracle subfolder of your
path.
Note: This sensor type supports Oracle database servers version 10.2 or higher.
Note: This sensor type supersedes the outdated Oracle SQL sensor. We recommend you to
use this new sensor to monitor Oracle SQL databases.

Add Sensor
Sensor Settings
894
26.09.2014


Sensor Name

Tags

Priority
(top priority).
Port

System ID
Enter the Oracle System ID (SID) of the database the sensor will
connect to. For example, such a system ID could be orcl
Authentication

User

connection.
Password

connection.
26.09.2014
895

Database Timeout
(Sec.)

DATA
SQL Query File

Use Transaction
executed.
896
26.09.2014

DATA
Data Processing

queried data table.
Handle DBNull in
Channel Values as

by
below.
value was found.
Sensor Channel #x
26.09.2014
897

DATA
Sensor Channel #x
Name
Sensor Channel #x
Column Number

value.
Sensor Channel #x
Column Name
Sensor Channel #x
Row Number
Sensor Channel #x
Mode
Sensor Channel #x
Unit
BytesBandwidth
BytesMemory
898
26.09.2014

DATA
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Message
defined channel.
Sensor Message
Column Number
integer value.
Sensor Message
Column Name
string.
26.09.2014
899

DATA
Sensor Message Row
Number
integer value.
Sensor Message Key
Sensor Message

added.
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
900
26.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
26.09.2014
901

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
902
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
903


menu bar.
Dependency
dependent on.
Delay (Seconds)
904
26.09.2014

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

Notifications
26.09.2014
905

Others
906
141
section.
26.09.2014

67 Packet Sniffer Sensor
6.8.67 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.
Note: This sensor can be set up on a Probe Device only! 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.
For a general introduction to the technology behind packet sniffing, please see Monit oring
Bandwidt h via Packet Sniffing 2500 section.
type of sensor.
Add Sensor
Sensor Settings

Sensor Name

Tags

19.09.2014
907


Priority
(top 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 2572 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.

Channel Selection
908
19.09.2014


UDP and TCP.
Ot her.
channel.
SENSOR DISPLAY
Primary Channel

Chart Type
19.09.2014
909

SENSOR DISPLAY
for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
910
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
911


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
912
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
913

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
914
19.09.2014

Toplists
More
Sniffer sensors?

Notifications
Others
141
section.
Related Topics
2572
19.09.2014
2576
915

68 Packet Sniffer (Custom) Sensor
6.8.68 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.
Note: This sensor can be set up on a Probe Device only! 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.
type of sensor.

Add Sensor
Sensor Settings

Sensor Name
916

19.09.2014


Tags

Priority
(top 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 2572 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 2572 section.
Channel Definition

Sensors 2576 section. All traffic for which no channel is defined is
accounted to the default channel named Ot her.
filters for the data you really want to analyze. We recommend you
to not use more than 20 channels in graphs and tables, and not
more than 100 channels in total. For performance reasons, it is
better to add several sensors with less channels each.
Network Adapters
Define the network adapters that this sensor monitors. You see a
list of names with all adapters available on the probe system. To
select an adapter, set a check mark symbol in front of the
respective name. You can also select and deselect all items by
using the check box in the table head.
Log Stream Data to

19.09.2014
917

SNIFFER SPECIFIC
Ot her channel.
only.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist
918

19.09.2014

PR IMAR Y TOPLIST
Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
19.09.2014
919

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
920
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
921


menu bar.
Dependency
dependent on.
Delay (Seconds)
922
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
923

Toplists
More

Notifications
Others
141
section.
Related Topics
2572
924
2576
19.09.2014

69 Passive Application Performance Sensor
6.8.69 Passive Application Performance Sensor

The Passive Application Performance sensor monitors Transport Control Protocol (TCP)
connection timings using packet sniffer. It can measure the performance of many different web
applications without actually having direct access to neither the client nor the server. In order
to obtain valuable data, these applications must work TCP-based and initiate a new session
with each request.
The sensor shows the total number of packets per second on the selected network card, the
number of dropped packets per second by PRTG because of system overload (more processor
power is required if this value is above zero to cope with the traffic), as well as the number of
currently active connections on all monitored applications.
For defined applications, the sensor can show (together with the corresponding application
name):
Request time in msec: average time between the initial (SYN) packet from the client and the
first request package from the client
Response time in msec: average time between the initial (SYN) packet from the client and
first packet of the result from the server
ACK (acknowledge) time in msec: average time between the initial (SYN) packet of a
connection from the client until the server sends an ACK (acknowledge) packet. This means
that a TCP connection was successfully established (in LANs this value is zero in most cases
and only increases for extreme loads).
Count: total number of observed connections to the service in the last monitoring interval.
This is the number of measurements the average is based on. The higher the value the more
reliable/averaged the data is. If this value is zero, PRTG did not see any packets for this
service.
Important notice: This sensor is an experimental sensor. Currently, it is in bet a 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.
type of sensor.
Add Sensor
Sensor Settings
19.09.2014
925


Sensor Name

Tags

Priority
(top priority).
APPLICATIONS
Network Adapter
Select the network adapter you want to monitor.
Applications
Define the applications you want to monitor. For each application,

use one dedicated line. Use the following syntax to define an
application to be monitored: ip:port=application. Provide the IP
address and port number of the application. Behind the equals
sign, enter a name for the application which will be displayed in the
channels. Please enter a string. This sensor will create four sensor
channels with the application name, e.g., "Application (ACK)".
SENSOR DISPLAY
Primary Channel

Chart Type
926
19.09.2014

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
927

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
928
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
929


menu bar.
Dependency
dependent on.
Delay (Seconds)
930
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
931

70 PerfCounter Custom Sensor
6.8.70 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 939 .

possible.
Note: The user account has to be a member of the Performance Monitor Users user group on
the target system.

RemoteRegistry "Remote Registry" Windows service is running on the target computer. If you
fail to do so, a connection via Performance Counters will not be possible.
Automatic.

Windows version 2008 R2 or later is installed on the computer running the PRTG probe: This is
remote probe 2589 .
Add Sensor
932
19.09.2014

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::%
Mode
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

Sensor Name

Tags

Priority
(top priority).
19.09.2014
933

PER FOR MANCE COU NTER SETTINGS

List of Counters
The list of counters monitored by this sensor. Once a sensor is

anew.
Mode
The mode in which the returning values are displayed. Once a

the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
934
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
935


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
936
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
937

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
938
19.09.2014

More
Knowledge Base: How can I find out the names of available Performance Counters?
Knowledge Base: Remote Monitoring of Specific Performance Counters
Notifications
Others
19.09.2014
141
section.
939

71 PerfCounter IIS Application Pool Sensor
6.8.71 PerfCounter IIS Application Pool Sensor

The PerfCounter IIS Application Pool sensor monitors a Microsoft Internet Information Services
(IIS) application pool using Windows Performance Counters. This sensor can show the overall
state of an application pool, the number of worker processes, the number of failures in worker
processes, as well as the number of ping failures, shutdown failures, and startup failures in
worker processes.
Requirement: Microsoft IIS Version 7.5

In order to monitor Microsoft Internet Information Services (IIS) application pools, this sensor
needs IIS version 7.5 or later to be installed on the target system.

possible.
Note: The user account has to be a member of the Performance Monitor Users user group on
the target system.

RemoteRegistry "Remote Registry" Windows service is running on the target computer. If you
fail to do so, a connection via Performance Counters will not be possible.
Automatic.

Windows version 2008 R2 or later is installed on the computer running the PRTG probe: This is
remote probe 2589 .
Add Sensor
940
19.09.2014

In order to monitor Microsoft Internet Information Services (IIS) application pools, PRTG will
create one sensor for each pool. The settings you make in this dialog are valid for all of the
IIS APPLICATION POOL SPECIFIC

Application Pool
in the table head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
941

IIS APPLICATION POOL SPECIFIC

Application Pool
The name of the application pool that is monitored by this sensor.

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
942
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
943


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
944
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
945

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
946
19.09.2014


Notifications
Others
19.09.2014
141
section.
947

72 Ping Sensor
6.8.72 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. When using more than one Ping per interval (default is 5 Pings per interval), it also
measures minimum and maximum Ping time, as well as packet loss in percent.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
PING SETTINGS
Timeout (Sec.)
948
Enter a timeout in seconds for the Ping. If the reply takes longer
triggered. The maximum timeout value is 300 seconds (5 minutes).
19.09.2014

72 Ping Sensor
PING SETTINGS
Packet Size (Bytes)
Enter the packet size in bytes for the Ping. You can choose any
value between 1 and 10000. We recommend using the default
value.
Ping Method
Define the kind of Ping check that will be performed. 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 simply 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 in
order for the sensor to switch to a Down status. 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 sending multiple Pings is enabled above.

Enter the number of Pings that are sent 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 sending multiple Pings is enabled above.

Enter the time in milliseconds PRTG has to wait 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 144 automatically.
Show "Down" st at us on error (default ): Do not automatically
acknowledge an alarm if this sensor changes to a Down status.
Show "Down (Acknowledged)" st at us on error: Automatically
acknowledge an alarm. If this sensor changes to a Down status,
it will automatically change to Down (Acknowledged).
Note: The sensor will also go through a Down status, so any
sensor status triggers 2227 using this will still provoke
notifications, as configured.
19.09.2014
949

72 Ping Sensor
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
950
19.09.2014

72 Ping Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
951

72 Ping Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
952
19.09.2014

72 Ping Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
953

72 Ping Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: How to create/customize statistical PING sensor?
Knowledge Base: Can I create an inverse Ping sensor?


954
19.09.2014

72 Ping Sensor
Notifications
Others
19.09.2014
141
section.
955

73 Ping Jitter Sensor
6.8.73 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. 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 ) )
type of sensor.

Add Sensor
Sensor Settings

Sensor Name
956

19.09.2014


Tags

Priority
(top priority).
SENSOR SETTINGS
Ping Count
Define the number of pings that this sensor sends. Please enter an
integer value.
DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel
19.09.2014

957

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
958
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
959


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
960
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
961

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

Notifications
Others
962
141
section.
19.09.2014

74 Pingdom Sensor
6.8.74 Pingdom Sensor

The Pingdom sensor queries an account at Pingdom.com and retrieves values for one "check"
configured in the respective Pingdom account. With every scanning interval, the sensor always
catches the last value available in the "detailed check log" of your Pingdom account.
type of sensor.

Add Sensor
Sensor Settings

Sensor Name

Tags

19.09.2014
963

74 Pingdom Sensor

Priority
(top priority).
SENSOR SETTINGS
Pingdom Check Name
Enter the name of the "check" you want to retrieve data for. Enter
it exactly the way configured in your Pingdom account. This setting
is case sensitive! Please enter a string.
Username
Enter the username of the Pingdom account you want to query.

Please enter a string.
Password
Enter the password of the Pingdom account you want to query.

If Value Changes
change.
DEBU G OPTIONS
Sensor Result
between:
964
19.09.2014

74 Pingdom Sensor
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
SCANNING INTER VAL

Scanning Interval

Note: Please make sure you select the same scanning interval you
configured for the "check" in your Pingdom account. Only if the
intervals match, PRTG can catch every measurement from your
"check".
19.09.2014
965

74 Pingdom Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
966
19.09.2014

74 Pingdom Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
967

74 Pingdom Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
968
141
section.
19.09.2014

75 POP3 Sensor
6.8.75 POP3 Sensor

The POP3 sensor monitors an email server using Post Office Protocol version 3 (POP3). It
shows the response time of the server.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
969

75 POP3 Sensor
POP3 SPECIFIC
Timeout (Sec.)
Enter a timeout in seconds for the request. If the reply takes longer
triggered. The maximum value is 900 seconds (15 minutes). Please
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 using the default value. If you do not get a connection,
please try another port number.
Security
Specify if the POP3 connection is secured via SSL. Choose

between:
Encry pt dat a using Transport -Level Securit y (TLS): Connect
to the POP3 server using the SSL method you select below.
No encry pt ion (use plain t ext ): Do not use encryption for the
POP3 connection.
SSL-Method
SSL V2
SSL V2 or V3
SSL V3
TLS V1
970
19.09.2014

75 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 into the POP3 server with user
name and password (simple login, non-secure).
128-bit MD5 hash value (APOP): Send the password in an
encrypted form using APOP. This option must be supported by
the POP3 server you connect to.
Username
This field is only visible if you selected an option with login above.
Enter a username for POP3 authentication. Please enter a string.
Password
This field is only visible if you selected an option with login above.
Enter a password for POP3 authentication. Please enter a string.
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
971

75 POP3 Sensor
SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
972
19.09.2014

75 POP3 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
973

75 POP3 Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
974
19.09.2014

75 POP3 Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
975

75 POP3 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
976
141
section.
19.09.2014

76 POP3 Email Count Sensor
6.8.76 POP3 Email Count Sensor

The POP3 Email Count sensor connects to a POP3 email account and returns the number of
emails stored in it. Additionally, you can filter by to or from address, or by subject, to only
count mails matching the search pattern.
type of sensor.

Add Sensor
Sensor Settings

Sensor Name

Tags

26.09.2014
977


Priority
(top priority).
SENSOR SETTINGS
Username
ENter the username of the POP3 account you want to log into.
Note: As POP3 server, this sensor uses the parent device's IP
Address/DNS Name value.
Password
Enter the password for the POP3 account. Note: As POP3 server,
this sensor uses the parent device's IP Address/DNS Name value.
Mailserver POP3 Port
Define the port number the POP3 server is running at. Please enter
an integer value. Note: As POP3 server, this sensor uses the parent
device's IP Address/DNS Name value.
Use SSL
Define whether to use SSL for the connection to the POP3 server.
Choose between:
No
Yes
Note: As POP3 server, this sensor uses the parent device's
hostname.
Filter To Address
Optionally define a To address. Only mails containing this address

are counted by the sensor. Please enter a string or leave the field
empty.
Filter From Address
Optionally define a From address. Only mails containing this

address are counted by the sensor. Please enter a string or leave
the field empty.
Filter Subject Content
Optionally define an email Subject. Only mails containing this

subject are counted by the sensor. Please enter a string or leave
the field empty.
If Value Changes
change.
978
26.09.2014

SENSOR SETTINGS
DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
26.09.2014
979

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
980
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
981


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
982
26.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
983

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
984
26.09.2014

More

Notifications
Others
26.09.2014
141
section.
985

77 Port Sensor
6.8.77 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.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
POR T SPECIFIC
Timeout (sec.)
Enter a timeout in seconds for the port connect. If the reply takes
is triggered.
Port

986
19.09.2014

77 Port Sensor
POR T SPECIFIC
SSL (Secure Sockets
Layer)
Specify if an encryption will be used for the connection. Choose

between:
Don't use SSL (recommended)
Use SSL
SSL-Method
SSL V2
SSL V2 or V3
SSL V3
TLS V1
ADVANCED SENSOR SETTINGS

Goal
Define how the sensor will report on the port defined above.
Choose between:
Open: The sensor will return a green OK status if the port is
open, and show a red Down status if the port is closed.
Closed: The sensor will return a green OK status if the port is
closed, and show a red Down status if the port is open.
Command
Define whether a command will be sent after the port is opened.

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 webserver.
Command
19.09.2014
This field is only visible if sending a command is enabled above.

Enter a command that will be sent in 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.
987

77 Port Sensor
ADVANCED SENSOR SETTINGS

Response
Define if the response received will be further processed. Choose

between:
Ignore response: Do not check the response.
Check response code (int eger): Check if the response matches
a defined response code. Define below.
Check response t ext : Check if the response matches a defined
response text. Define below.
Allowed Code
This field is only visible if response code check is enabled above.

Enter a code that must be returned. If it does not match the sensor
will be set to 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)

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

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:
988
19.09.2014

77 Port Sensor
Check For Existing

Keywords (Positive)

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
989

77 Port Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
990
19.09.2014

77 Port Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
991

77 Port Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
992
19.09.2014

77 Port Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
19.09.2014
141
section.
993

78 Port Range Sensor
6.8.78 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 returns the number of closed ports and open ports in two
different channels. Optionally, you can set limits in the sensor's channel settings. This way you
can get alerted about open/closed ports.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
POR T R ANGE SPECIFIC

Timeout (Sec.)
994
is triggered.
19.09.2014

POR T R ANGE SPECIFIC

Port-by-Port-Delay (ms)
Specify in milliseconds how long the sensor will wait to go to the

next port while running through all given ports.
Port Range Selection

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: Provide a list of several individual ports to monitor.
Range Start
This field is only visible if the port range method is enabled above.
Enter the port number where the scan will start. Please enter an
integer value.
Range End
This field is only visible if the port range method is enabled above.
Enter the port number where the scan will end. Please enter an
integer value.
Port List
This field is only visible if the list of ports method is enabled above.
Enter the numbers of the ports the sensor will try to connect to.
Please enter one or more individual integer values.
If Value Changes
Define what will be done if the number of closed ports or open

ports. Choose between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
995

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
996
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
997


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
998
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
999

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

Notifications
Others
1000
141
section.
19.09.2014

79 PostgreSQL Sensor
6.8.79 PostgreSQL Sensor

The PostgreSQL sensor monitors a database on a PostgreSQL server and executes a defined
query. It shows the execution time of the whole request (including connection buildup, query
Save the SQL script with the query into the \Cust om Sensors\sql\post gresql subfolder of
your PRTG installation. See section Dat a St orage 2611 for more information about how to find
this path
Note: This sensor type supports PostgreSQL 7.x or later.

Add Sensor
Sensor Settings
26.09.2014
1001


Sensor Name

Tags

Priority
(top priority).
Port

Database
Authentication

User

connection.
Password

connection.
1002
26.09.2014

Database Timeout
(Sec.)

DATA
SQL Query File

Use Transaction
executed.
26.09.2014
1003

DATA
Data Processing

queried data table.
Handle DBNull in
Channel Values as

by
below.
value was found.
Sensor Channel #x
1004
26.09.2014

DATA
Sensor Channel #x
Name
Sensor Channel #x
Column Number

value.
Sensor Channel #x
Column Name
Sensor Channel #x
Row Number
Sensor Channel #x
Mode
Sensor Channel #x
Unit
BytesBandwidth
BytesMemory
26.09.2014
1005

DATA
BytesDisk
Temperature
Percent
TimeResponse
TimeSeconds
TimeHours
Count
CPU
BytesFile
SpeedDisk
SpeedNet
Custom
custom sensors.
Sensor Channel #x
Custom Unit
Sensor Message
defined channel.
Sensor Message
Column Number
integer value.
Sensor Message
Column Name
string.
1006
26.09.2014

DATA
Sensor Message Row
Number
integer value.
Sensor Message Key
Sensor Message

added.
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
26.09.2014
1007

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1008
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
1009


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1010
26.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
1011

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

Notifications
1012
26.09.2014

Others
26.09.2014
141
section.
1013

80 Probe Health Sensor
6.8.80 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 2589 , or a cluster 81 probe). 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.
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 238 ).
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 238 or distribute your sensors over multiple probes 2589 .
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 238 or distribute the sensors over several probes 2589 .
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 238 or distribute the sensors
over several probes 2589 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 2502 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 2589 .
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.
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.
1014
18.11.2014

Toplist Memory : This channel shows the amount of RAM that the Toplist s 2240 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 2589
.
Trap Buffer: This channel shows the number of buffered SNMP traps. Usually, this value
should be 0 (or very low). Investigate increasing values.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
18.11.2014
1015

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1016
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1017

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1018
18.11.2014


Notifications
Others
18.11.2014
141
section.
1019

81 QoS (Quality of Service) One Way Sensor
6.8.81 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, which 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 packet loss, jitter, Packet Delay Variation (PDV), etc.
Note: In order for this sensor to work, there has to be at least one remote probe 2588
configured in your setup. The sensor can be created on the Probe Device of either a local or
remote probe.
Note: This sensor type cannot be cloned using the Clone Object
2246
function.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1020
19.09.2014

QU ALITY OF SER VICE MEASU R EMENT

Timeout (Sec.)

is triggered. The maximum timeout is 900 seconds (15 minutes).
Target Probe
Define the target probe that will receive the UDP packets. In the
drop down menu, all local and remote probes of your setup are
shown. 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 2588 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. will allow the UDP packets to reach the target probe. The
Windows firewall on the target system will be automatically opened
by the probe.
Target Host/IP
Define the IP address of the target probe to which the probe the
sensor is created on will connect. When you're not using 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. Please 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 are sent for each scanning interval. We
recommend using 1000. Please enter an integer value.
Size of Packets (Bytes)
Define the size in bytes of the packets sent. We recommend using

172. Please enter an integer value.
Time between Packets

(ms)
Define the size in milliseconds that will be waited between two

packets. We recommend using 20. Please enter an integer value.
19.09.2014
1021

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1022
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1023


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1024
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1025

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

Notifications
Others
1026
141
section.
19.09.2014

82 QoS (Quality of Service) Round Trip Sensor
6.8.82 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 packet loss, jitter, Packet Delay Variation
(PDV), the round trip time (RTT), etc.
Note: In order for this sensor to work, there has to be at least one remote probe 2588
configured 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. For details, see section More 1033 .
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
1027

QU ALITY OF SER VICE MEASU R EMENT

Timeout (Sec.)

is triggered. The maximum timeout is 900 seconds (15 minutes).
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 1033 for
information about this tool.
Target Probe
This setting is only shown if you selected 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, please install and connect a remote probe 2588 first or use
the QoS Reflector. When running the sensor on a remote probe,
select either another remote probe or the local probe as target.
The sensor will measure values for the network track between the
probe the sensor is created on and the target probe.
Note: You must ensure that firewalls, NAT rules, etc. will allow the
UDP packets to reach the target probe. The Windows firewall on
the target system will be automatically opened by the probe.
Target Host/IP
Define the IP address of the QoS target. If you use the QoS
Reflector, enter the address of the machine on which the reflector
script runs. If you use a probe, enter the address of the probe to
which the probe the sensor is created on will connect. When
you're not using 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.
Please 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 are sent for each scanning interval. We
recommend using 1000. Please enter an integer value.
Size of Packets (Bytes)
Define the size in bytes of the packets sent. We recommend using

172. Please enter an integer value.
Time between Packets

(ms)
1028
Define the size in milliseconds that will be waited between two

packets. We recommend using 20. Please enter an integer value.
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1029

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1030
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1031


menu bar.
Dependency
dependent on.
Delay (Seconds)
1032
19.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: How can I monitor QoS roundtrips without using remote probes?

Notifications
19.09.2014
1033

Others
1034
141
section.
19.09.2014

83 RADIUS Sensor
6.8.83 RADIUS Sensor

IMPOR TANT NOTICE
This sensor type is outdated. We strongly recommend you to use the RADIUS v2 Sensor 1042
instead. This is a new sensor type to monitor RADIUS servers and shows the RADIUS code
in addition to the response time.
The RADIUS sensor monitors a Remote Authentication Dial-In User Service (RADIUS) server.
The sensor tries to authenticate at the server and shows the response time. If authentication
fails, the sensor shows a Down status.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
26.09.2014
1035

83 RADIUS Sensor
R ADIU S SPECIFIC
Timeout (Sec.)

message is triggered. The maximum value is 900 seconds (15
minutes). Please enter an integer value.
User
Define the user name that is used for authentication at the server.
Password
Define the password that is used for authentication between the

client and the RADIUS server. Please enter a string. Note: The
password must not be longer than 6 characters.
Secret
Define the shared secret that is used for authentication between

the authenticator (here the PRTG Probe) and the server. Please
enter a string.
Port
Enter the port number used for connection to the server. Default
value is 1812. Please enter an integer value.
NAS IP Address
Define a valid NAS IP address or leave the field empty.
NAS-Identifier
Enter a NAS identifier. Please enter a string or leave the field empty.
Chap
Define if you want to use the Challenge Handshake Authentication

Protocol. Choose between:
Don't use Chap
Use Chap
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1036
26.09.2014

83 RADIUS Sensor
SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
26.09.2014
1037

83 RADIUS Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1038
26.09.2014

83 RADIUS Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
1039

83 RADIUS Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
1040
26.09.2014

83 RADIUS Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
26.09.2014
141
section.
1041

84 RADIUS v2 Sensor
6.8.84 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
response time and the RADIUS code. If authentication fails, the sensor shows a Down status.
Note: This sensor type supersedes the outdated RADIUS sensor. We recommend you to use
this new sensor to monitor RADIUS servers.

Add Sensor

Sensor Name
1042

20.11.2014

84 RADIUS v2 Sensor

Tags

Priority
(top priority).
20.11.2014
1043

84 RADIUS v2 Sensor
R ADIU S SPECIFIC
Timeout (Sec.)

User
Define the user name that is used for authentication at the server.
Password
Define the password that is used for authentication between the

client (this is the PRTG probe on which the sensors runs) and the
RADIUS server. Please enter a string.
Note: The password must not be longer than 6 characters.
Secret
Define the shared secret that is used for authentication between

the authenticator (this is the PRTG Probe) and the server. Please
enter a string.
Port
Enter the port number that is used for connection to the server.
Default value is 1812. Please enter an integer value.
NAS-IP-Address
Define a valid Network Access Server (NAS) IP address or leave the

field empty.
Note: Please define either a NAS-IP-Address or a NAS-Identifier for
the access request.
NAS-Identifier
Enter a NAS identifier. Please enter a string or leave the field empty.
Note: Please define either a NAS-IP-Address or a NAS-Identifier for
the access request.
Sensor Result
between:
1044
20.11.2014

84 RADIUS v2 Sensor
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
20.11.2014
1045

84 RADIUS v2 Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1046
20.11.2014

84 RADIUS v2 Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
20.11.2014
1047

84 RADIUS v2 Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
1048
20.11.2014

84 RADIUS v2 Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More

Notifications
20.11.2014
1049

84 RADIUS v2 Sensor
Others
1050
141
section.
20.11.2014

85 RDP (Remote Desktop) Sensor
6.8.85 RDP (Remote Desktop) Sensor

The RDP (Remote Desktop) Sensor monitors remote desktop services (RDP, Terminal Services
Client) and shows the response time.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR SPECIFIC
Timeout (Sec.)

Port
Enter the number of the port the sensor will try to connect to.
Please enter an integer value. Default value is 3389. We
18.11.2014
1051

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1052
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1053


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1054
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1055

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

Notifications
1056
18.11.2014

Others
18.11.2014
141
section.
1057

86 SCVMM Host Sensor
6.8.86 SCVM M Host Sensor

The SCVMM Host sensor monitors a host that is managed by a Microsoft System Center Virtual
Machine Manager (SCVMM). This can be, for example, a Hyper-V host, a VMware host, or a
XenServer host. It can show the CPU usage, free memory (in bytes and percentage), the overall
status, the communication status, the status of the cluster node, the status of the virtual
server, the computer status, and the VM count.
type of sensor.


Requirement: Remote PowerShell 2.0

This sensor type uses PowerShell commands. In order to monitor devices with this sensor,
Remot e PowerShell 2.0 has to be enabled.
Note: PowerShell 1.0 is not supported.
1058
1065
section below.
18.11.2014

Requirement: VMM PowerShell Plugin

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

In order to make this sensor type compatible for Windows Server 2012 systems, the following
requirements have to be met:
The SCVMM PowerShell module has to be in the directory C:\Program Files\Microsoft System
Center 2012\Virtual Machine Manager\bin\psModules\virtualmachinemanager
\virtualmachinemanager.
You have to set the execution policy in PowerShell to allow the execution of Import-Module
C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules
\virtualmachinemanager\virtualmachinemanager. Use the command Set -Execut ionPolicy . We
recommend the execution policy Remot eSigned; AllSigned and Unrest rict ed are also
possible.
Add Sensor
In order to monitor hosts, PRTG will create one sensor for each host. The settings you make in
this dialog are valid for all of the sensors that are created.
18.11.2014
1059

HOST SETTINGS
Host
Select the hosts you want to add a sensor for. You see a list with
head. Note: Please make sure the name of your hosts do not
contain unsupported characters, especially avoid the hash ('#') sign.
We recommend to not rename hosts once you've set up
below.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
HOST SETTINGS
Sensor Result
Choose between:
1060
18.11.2014

HOST SETTINGS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
1061

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1062
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1063


menu bar.
Dependency
dependent on.
Delay (Seconds)
1064
18.11.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
18.11.2014
1065


Notifications
Others
1066
141
section.
18.11.2014

87 SCVMM Virtual Machine Sensor
6.8.87 SCVM M Virtual M achine Sensor

The SCVMM Virtual Machine sensor monitors a virtual machine (VM) that is managed by a
Microsoft System Center Virtual Machine Manager (SCVMM). This can be, for example, a HyperV virtual machine, a VMware virtual machine, or a XenServer virtual machine. It can show the
CPU usage, the status of a VM, and disk read and write speed.
type of sensor.


Requirement: Remote PowerShell 2.0

This sensor type uses PowerShell commands. In order to monitor devices with this sensor,
Remot e PowerShell 2.0 has to be enabled.
Note: PowerShell 1.0 is not supported.
18.11.2014
1074
section below.
1067

Requirement: VMM PowerShell Plugin

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

In order to make this sensor type compatible for Windows Server 2012 systems, the following
requirements have to be met:
The SCVMM PowerShell module has to be in the directory C:\Program Files\Microsoft System
Center 2012\Virtual Machine Manager\bin\psModules\virtualmachinemanager
\virtualmachinemanager.
You have to set the execution policy in PowerShell to allow the execution of Import-Module
C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules
\virtualmachinemanager\virtualmachinemanager. Use the command Set -Execut ionPolicy . We
recommend the execution policy Remot eSigned; AllSigned and Unrest rict ed are also
possible.
Add Sensor
In order to monitor VMs, PRTG will create one sensor for each VM. The settings you make in
this dialog are valid for all of the sensors that are created.
1068
18.11.2014


Virtual Machine
Select the Virtual Machines (VMs) you want to add a sensor for.
in the table head. Note: Please make sure the name of your VMs
do not contain unsupported characters, especially avoid the hash
('#') sign. We recommend to not rename VMs once you've set up
below.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).

Sensor Result
Choose between:
18.11.2014
1069


SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1070
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1071


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1072
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1073

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
1074
18.11.2014


Notifications
Others
18.11.2014
141
section.
1075

88 Sensor Factory Sensor
6.8.88 Sensor Factory Sensor

The Sensor Factory sensor is a powerful tool that allows you to create your own sensor with
channels based on data from other sensors. You can define one or more channels using
formulas that combine monitoring results from other sensors.
Samples for usage are:
Show single channels of one or more sensors in one graph.
Use the data from single channels of one or more sensors to calculate new values (for
example, you can subtract, multiply, and divide).
Create graphs with data from other sensor channels and add horizontal lines at specific
vertical positions.
Note: A sensor factory sensor does not show a "Downtime" channel. Downtime cannot be
calculated for this sensor type.
Note: The Sensor Factory sensor might not work with flow sensors 2502 . Sensor types using
active flow timeout, this is, NetFlow and jFlow sensors 306 , are not supported by the Sensor
Factory sensor.
type of sensor.

Add Sensor
Sensor Settings
1076
19.09.2014


Sensor Name

Tags

Priority
(top priority).
19.09.2014
1077

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 1083 below.
Error Handling
Define the behavior of the sensor if one of the sensors defined

above is in an error status. In this case, you can set the sensor
factory sensor either to down or to warning status. Choose
between:
Fact ory sensor shows error st at us when one or more source
sensors are in error st at us: If at least one sensor that you use
in a channel definition is in a Down status, the factory sensor
shows a Down status as well until all referred sensors leave this
status. While the factory sensor is Down, it will still show data of
all available sensor channels.
Fact ory sensor shows warning st at us when one or more
source sensors are in error st at us: If at least one sensor that
you use in a channel definition is in a Down status, the factory
sensor shows a Warning status until all referred sensors leave
the Down status.
Use cust om formula: Define the status of the factory sensor by
adding a status definition in the field below.
Status Definition
This field is only visible if you enable custom formula above. Define
when the sensor will switch to a Down status. You can use the
status() function in combination with Boolean operations. For
advanced users it is also possible to calculate a status value.
Please see section Define Sensor St at us 1090 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.
1078
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1079

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1080
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1081


menu bar.
Dependency
dependent on.
Delay (Seconds)
1082
19.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
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.
19.09.2014
1083

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() 1085 , min() 1086 , max() 1086 , avg() 1086 , or percent ()
1087 .
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)
1084
19.09.2014

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 1087 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 112 .
<channelId> is the ID of the sensor channel. It is displayed in the respective field of the
channel settings 2221 .
19.09.2014
1085

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()
1085
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()
1086
1085
functions.
19.09.2014

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()
1085
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 1089 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
19.09.2014
1087

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

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
19.09.2014
1089

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 1076 . 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 112 .
<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.
1090
19.09.2014

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

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 1083 . Using this functionality, it
is possible, for example, to display the numeric status value of sensors in a factory sensor
channel.
Using Factory Sensors in a Cluster Setup

If you run PRTG in Clustering
81
mode, please note these additional facts:
If you add a Sensor Factory sensor underneath the Clust er Probe, and in the Sensor Factory
formula you refer to a channel of a sensor running on the Clust er Probe as well, the Sensor
Factory sensor shows the data of all cluster nodes for this sensor channel.
If you add a Sensor Factory sensor underneath the Local Probe, and in the Sensor Factory
formula you refer to a channel of a sensor running on the Clust er Probe, the Sensor Factory
sensor only shows data of the primary master node for this sensor channel.
More
Knowledge Base: Can I add sensors to Sensor Factory sensors using tags?
Knowledge Base: How can I monitor the overall status of the business process "Email"?

Notifications
1092
19.09.2014

Others
19.09.2014
141
section.
1093

89 sFlow Sensor
6.8.89 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. Please make sure the device matches the sFlow
version V5! There are several filter options available to divide traffic into different channels.
Note: In order for the sensor to work, sFlow V5 export must be enabled on the device. The
The sensor accepts RAW data only. The stream must be sent via IPv4. 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.
Limitations of This Sensor Type

There are some limitations that you want to consider before using this sensor type:
Only sFlow version 5 datagrams are supported
Only IPv4 flows are supported
Only the "raw packet header" format is supported
Only the "Flow sample" format is supported. "Extended flow" and "Counter" formats cannot be
processed
PRTG processes only samples where the source ID matches the ifIndex of the input interface
(avoiding double counted traffic) and ascending sequence numbers. Due to internal
limitations, only interface numbers up to 65535 are supported.
Sample packets have to be of ethernet type "IP" (with optional VLAN tag)
Sampled packets of type TCP and UDP are supported
We recommend using sFlow tester for debugging (see More section below).
Add Sensor
Sensor Settings
1094
19.09.2014

89 sFlow Sensor

Sensor Name

Tags

Priority
(top 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, please make sure 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. Note:
When configuring export, please make sure you select the
appropriate sFlow version 5.

Channel Selection
19.09.2014
1095

89 sFlow Sensor

UDP and TCP.
Ot her.
channel.
FILTER ING
Include Filter
section.
Exclude Filter
1096
19.09.2014

89 sFlow Sensor
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
19.09.2014
1097

89 sFlow Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1098
19.09.2014

89 sFlow Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1099

89 sFlow Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
1100
19.09.2014

89 sFlow Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1101

89 sFlow Sensor
Toplists
More
Paessler Website: Paessler sFlow Tester
http://www.paessler.com/tools/sflowtester
Sniffer sensors?

Notifications
Others
141
section.
Related Topics
2572
1102
2576
19.09.2014

90 sFlow (Custom) Sensor
6.8.90 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.
Note: In order for the sensor to work, sFlow V5 export must be enabled on the device. The
the sensor is set up (either a local or remote probe). The sensor accepts RAW data. This
sensor type cannot be used in cluster mode. You can set it up on a local probe or remote
Limitations of This Sensor Type

There are some limitations that you want to consider before using this sensor type:
Only sFlow version 5 datagrams are supported
Only IPv4 flows are supported
Only the "raw packet header" format is supported
Only the "Flow sample" format is supported. "Extended flow" and "Counter" formats cannot be
processed
PRTG processes only samples where the source ID matches the ifIndex of the input interface
(avoiding double counted traffic) and ascending sequence numbers. Due to internal
limitations, only interface numbers up to 65535 are supported.
Sample packets have to be of ethernet type "IP" (with optional VLAN tag)
Sampled packets of type TCP and UDP are supported
We recommend using sFlow tester for debugging (see More section below).

Add Sensor
19.09.2014
1103

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SFLOW SPECIFIC SETTINGS

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, please make sure 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. Note:
When configuring export, please make sure you select the
appropriate sFlow version 5.
1104
19.09.2014

Channel Definition

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 analyse.
FILTER ING
Include Filter
section.
Exclude Filter
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
19.09.2014

1105

PR IMAR Y TOPLIST
Primary Toplist

Top Talkers
Top Connect ions
Top Prot ocols
Inherited Settings
described below.
1106
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1107


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1108
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1109

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1110
19.09.2014

Toplists
More
Paessler Website: Paessler sFlow Tester
http://www.paessler.com/tools/sflowtester

Notifications
Others
141
section.
Related Topics
2572
19.09.2014
2576
1111

91 SFTP Secure File Transfer Protocol Sensor
6.8.91 SFTP Secure File Transfer Protocol Sensor

The sFTP Secure File Transfer Protocol sensor monitors FTP servers of a Linux/Unix system
using SSH File Transfer Protocol (FTP over SSH). It tries to connect to a server and shows the
response time.
For this sensor type credentials for Linux/Solaris/Mac OS (SSH/WBEM) systems must be
defined for the device you want to use the sensor on.
Note: This sensor type cannot support all Linux/Unix and Mac OS distributions.
2498
section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1112
19.09.2014

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.
Shell Timeout (sec.)
Define a timeout for the shell response. This is the time in seconds
the sensor waits for the shell to return a response after it has sent
its specific command (e.g. cat /proc/loadavg).
SSH Port
Define which port this sensor will use for the SSH connection.
Choose between:
Inherit port number from parent device (default ): Use the
port number as defined in the Credentials for Linux/Solaris/Mac
OS (SSH/WBEM) Systems section of the device this sensor is
created on.
Ent er cust om port number: Do not use the port number from
the parent device's settings, but define a different port number
below.
Use Port Number
This field is only visible if the custom port number setting is

enabled above. Enter the port number this sensor will use for the
SSH connection. Please enter an integer value.
Result Handling
Define what will be done with the result data received by the
sensor. Choose between:
Discard result : Do not store the result data.
Writ e result t o disk (Filename: "Result of Sensor [ID].t xt ):
Store the last result received from the query to the "Logs
(Sensors)" directory (on the Master node, if in a cluster). File
SENSOR DISPLAY
Primary Channel

Chart Type
19.09.2014
1113

SENSOR DISPLAY
for each channel.
Show in and out t raffic as posit ive and negat ive area chart :
Show channels for incoming and outgoing traffic as positive and
negative area chart. This will visualize your traffic in a clear way.
Note: This option cannot be used in combination with manual
Vertical Axis Scaling (available in the Sensor Channels Set t ings
2220 settings).
Stack Unit

Inherited Settings
described below.
1114
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1115


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1116
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1117

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

Notifications
Others
1118
141
section.
19.09.2014

92 Share Disk Free Sensor
6.8.92 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 space in percent and total.
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.
Requirement: Server Service

In order to monitor shares on Windows machines, please make sure the LanmanServer "Server"
Windows service is running on the target computer.
Automatic.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
1119

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: In order to provide
any shares under Windows, the LanmanServer "Server" Windows
service must be running on the target computer. Once a sensor is
anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1120
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1121


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1122
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1123

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1124
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1125

93 SIP Options Ping Sensor
6.8.93 SIP Options Ping Sensor

The SIP Options Ping sensor monitors the connectivity for a Session Initiation Protocol (SIP)
server using SIP options "Ping". It can be used to monitor voice-over-IP (VoIP) services. The
sensor sends "auth" and "options" requests to the SIP server and shows the response time. It
can alert in case of an error.
Note: A SIP server might return a 480 Service temporarily unavailable error until at least one
reachable SIP client is connected to the server.
type of sensor.

Add Sensor
Sensor Settings

Sensor Name
1126

26.09.2014


Tags

Priority
(top priority).
SIP SPECIFIC
Port
Define the UDP port this sensor will connect to. Please enter an
integer value.
Username
Enter the username of the SIP account this sensor will log into
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 into
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
Retry Count
In case 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.
SENSOR DISPLAY
Primary Channel
26.09.2014

1127

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1128
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
1129


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1130
26.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
1131

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1132
26.09.2014

More

Notifications
Others
26.09.2014
141
section.
1133

94 SMTP Sensor
6.8.94 SM TP Sensor
The SMTP sensor monitors a mail server using Simple Mail Transfer Protocol (SMTP) and shows
the response time of the server. It can optionally send a test email with every check.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SMTP SPECIFIC
Timeout (Sec.)
1134
19.09.2014

94 SMTP Sensor
SMTP SPECIFIC
Port
Enter the number of the port that the sensor uses to send an email
via SMTP. For non-secure connections usually port 25 is used;
usually port 465 or 587 for SSL connections. The actual setting
depends on the server you are connecting to. Please enter an
integer value. We recommend using the default value. If you do not
get a connection, please try another port number.
Security)
Select if the SMTP connection is secured via SSL. Choose between:

Don't use: Do not use encryption for the SMTP connection.
Use: Connect to the SMTP server using the SSL method you
select below.
SSL-Method
SSL V2
SSL V2 or V3
SSL V3
TLS V1
AU THENTICATION
Type
Select whether to use an authentication method for the SMTP

connection. Choose between:
None: Do not use any authentication method.
Username and password: Authenticate at the SMTP server via
Username
This field is only visible if you enabled SMTP authentication above.

Enter a username for SMTP authentication. Please enter a string.
Password
This field is only visible if you enabled SMTP authentication above.

Enter a password for SMTP authentication. Please enter a string.
HELO Ident
Enter a server name for the HELO part of the email protocol. For
some mail servers, the HELO identifier must be the valid principal
host domain name for the client host. See SMTP RFC 2821.
19.09.2014
1135

94 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 use. Please enter a string or
leave the field empty.
Content
Specify which body the sent emails use. Please enter a string or
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type
1136
19.09.2014

94 SMTP Sensor
SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1137

94 SMTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1138
19.09.2014

94 SMTP Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1139

94 SMTP Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
1140
19.09.2014

94 SMTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
19.09.2014
141
section.
1141

95 SMTP&IMAP Round Trip Sensor
6.8.95 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 sensor shows the response time of SMTP and IMAP
server, and the sum of both.
The SMTP&IMAP Round Trip sensor will delete these emails automatically from the mailbox as
soon as PRTG retrieves them. Emails will only remain in the mailbox particularly if a timeout or a
restart of the PRTG server occurred during sensor run-time.
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 2512 section.
Add Sensor
We recommend adding this sensor on an SMTP server device only, because this sensor type's
settings are optimized for this scenario.
Sensor Settings

Sensor Name

Tags

1142
19.09.2014


Priority
(top priority).
Sensor Result
between:
EMAIL SETTINGS
From
Specify which address the sent emails will contain in the from field.
To
Specify to which address the emails will be sent to. Please enter a
valid email address.
Helo Ident
Enter a server name for the helo part of the mail protocol. For
some mail servers the helo ident must be the valid principal host
domain name for the client host.
19.09.2014
1143

STEP 1: SEND EMAIL TO PAR ENT DEVICE U SING SMTP

In this step, you configure how emails will be sent. As SMTP server, the sensor uses the IPAddress/DNS Name property's value of the device it is added on.
Port
Enter the number of the port that will be used to send an email via
SMTP. Please enter an integer value. For non-secure connections
usually port 25 is used; usually port 465 or 587 for SSL
connections. The actual setting depends on the server you are
connecting to. Please enter an integer value. We recommend using
the default value. If you do not get a connection, please try
another port number.
Timeout for SMTP

Connection (Sec.)
is triggered.
Security)
Select if the SMTP connection will be secured via SSL. Choose

between:
Use: Connect to the SMTP server using the SSL method selected
below.
SSL-Method
This field is only visible if security is enabled above. Select the SSL
method that will be used when connecting to the server. We
recommend using the default value. Only if you experience
SSL V2
SSL V2 or V3
SSL V3
TLS V1
SMTP Authentication
Type
Define if you want to use an authentication for the SMTP

Username/Password: Authenticate at the SMTP server via
Username
This field is only visible if SMTP authentication is enabled above.

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 (e.g.
19.09.2014
PRTG Roundtrip Mail: {5E858D9C-AC70-466A-9B2A55630165D276}). Use this field to place your custom text before
the automatically created text.
1144

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.
Please enter the IMAP mailbox/folder name.
Port
Specify the port that will be used for the IMAP connection. For
non-secure connections usually port 143 is used; usually port 993
for SSL connections. The actual setting depends on the server you
are connecting to. Please enter an integer value. We recommend
using the default value. If you do not get a connection, please try
Security)
Select if the IMAP connection will be secured via SSL. Choose

between:
below.
SSL-Method
This field is only visible when TLS is enabled above. Select the SSL
method that will be used when connecting to the IMAP server. We
problems, try another setting.
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, an error message will be triggered
for the sensor. Please enter an integer value.
IMAP Authentication
Type
Select the kind of authentication for the IMAP connection. Choose

between:
Username and Password (simple)
Simple Aut hent icat ion and Securit y Lay er (SASL)
Username
Enter a username for IMAP authentication. Please enter a string.
Password
Enter a username for IMAP authentication. Please enter a string.
19.09.2014
1145

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1146
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1147


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1148
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1149

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

Notifications
Others
1150
141
section.
19.09.2014

96 SMTP&POP3 Round Trip Sensor
6.8.96 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 sensor shows the response time of SMTP and POP3
server, and the sum of both.
The SMTP&POP3 Round Trip sensor will delete these emails automatically from the mailbox as
soon as PRTG retrieves them. Emails will only remain in the mailbox particularly if a timeout or a
restart of the PRTG server occurred during sensor run-time.
For a general introduction to the technology behind round trip monitoring, please see
Monit oring Email Round Trip 2512 section.
Add Sensor
We recommend adding this sensor on an SMTP server device only, as the sensor's settings are
optimized for this scenario.
Sensor Settings

Sensor Name

Tags

19.09.2014
1151


Priority
(top priority).
Sensor Result
between:
EMAIL SETTINGS
From
Specify which address the sent emails will contain in the from field.
To
Specify to which address the emails will be sent to. Please enter a
valid email address.
Helo Ident
Enter a server name for the helo part of the mail protocol. For
some mail servers the helo ident must be the valid principal host
domain name for the client host.
1152
19.09.2014

STEP 1: SEND EMAIL TO THE PAR ENT DEVICE U SING SMTP

In this step, you configure how emails will be sent. As SMTP server, the sensor uses the IPAddress/DNS Name property's value of the device it is added on.
Port
Enter the number of the port that will be used to send an email via
SMTP. Please enter an integer value. For non-secure connections
usually port 25 is used; usually port 465 or 587 for SSL
connections. The actual setting depends on the server you are
connecting to. Please enter an integer value. We recommend using
the default value. If you do not get a connection, please try
Timeout for SMTP

Connection (Sec.)
is triggered.
Security)
Select if the SMTP connection will be secured via SSL. Choose

between:
below.
SSL-Method
SSL V2
SSL V2 or V3
SSL V3
TLS V1
SMTP Authentication
Type
Define if you want to use an authentication for the SMTP

Username/Password: Authenticate at the SMTP server via
19.09.2014
1153

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
(e.g. PRTG Roundtrip Mail: {5E858D9C-AC70-466A-9B2A55630165D276}). Use this field to place your custom text before
the automatically created text.
1154
19.09.2014

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 will be used for the POP3 connection. For
non-secure connections usually port 110 is used; usually port 995
for SSL connections. The actual setting depends on the server you
are connecting to. Please enter an integer value. We recommend
using the default value. If you do not get a connection, please try
Security)
Select if the POP3 connection will be secured via SSL. Choose

between:
below.
SSL-Method
This field is only visible when TLS is enabled above. Select the SSL
method that will be used when connecting to the IMAP server. We
problems, try another setting.
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, an error message will be triggered
for the sensor. 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 into the POP3 server with user
name and password (simple login, non-secure).
128-bit MD5 hash value (APOP): Send the password in an
encrypted form using APOP. This option must be supported by
the POP3 server you're connecting to.
Username
This field is only visible if an option with login is selected above.

Password
This field is only visible if an option with login is selected above.

19.09.2014
1155

Inherited Settings
described below.
1156
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1157


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1158
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1159

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

Notifications
Others
1160
141
section.
19.09.2014

97 SNMP APC Hardware Sensor
6.8.97 SNM P APC Hardware Sensor

The SNMP APC Hardware sensor monitors performance counters on an APC UPS device using
Simple Network Management Protocol (SNMP). It can show actual voltage of a battery, its
capacity and temperature, and its remaining runtime, the input and output frequency, input and
output voltage, and output load. For additional counters, please see section More 1167 .
2491 section.
Add Sensor
For devices with multiple performance counters multiple sensors are created at once in the
Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are
created.
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
10.11.2014

1161


Tags

Priority
(top priority).
APC U PS SPECIFIC
Selected Interface
Shows the name of the interface (performance counter) monitored

by this sensor. Once a sensor is created, you cannot change this
Unit String
Define the unit of the numerical data that will be received 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 or float value.
Division
If you want to divide the received data by a certain value, enter the
divisor here. Please enter an integer or float value.
If Value Changes

1162
10.11.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
10.11.2014
1163

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1164
10.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
10.11.2014
1165


menu bar.
Dependency
dependent on.
Delay (Seconds)
1166
10.11.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: How can I monitor additional counters with the SNMP APC Hardware sensor?


10.11.2014
1167

Notifications
Others
1168
141
section.
10.11.2014

98 SNMP Cisco ADSL Sensor
6.8.98 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). It shows the speed of
downlink and uplink, remote and local attenuation, remote and local SNR (signal-to-noise ratio),
and remote and local power output.
2491 section.
Add Sensor
For devices with multiple performance counters, multiple sensors are created at once in the
created.
CISCO ADSL SETTINGS

Line Index

in the table head.
Sensor Settings

Sensor Name
19.09.2014

1169


Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1170
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1171


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1172
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1173

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

Notifications
1174
19.09.2014

Others
19.09.2014
141
section.
1175

99 SNMP Cisco ASA VPN Connections Sensor
6.8.99 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). It shows the active sessions of the connection types email, IPsec, L2L, LB,
SVC, WebVPN, as well as the total number of sessions, active users, and groups with active
users.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1176
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1177

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1178
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1179


menu bar.
Dependency
dependent on.
Delay (Seconds)
1180
19.09.2014

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

Notifications
19.09.2014
1181

Others
1182
141
section.
19.09.2014

100 SNMP Cisco ASA VPN Traffic Sensor
6.8.100 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
Simple Network Management Protocol (SNMP). It shows incoming and outgoing traffic, as well
as total traffic.
This sensor type is indented to monitor permanent connections. It will show an error if a
connection is interrupted. It can monitor IPsec connections only!
2491 section.
Add Sensor
If you select more than one connections, multiple sensors are created at once in the Add
Sensor dialog. The settings you make in this dialog are valid for all of the sensors that are
created.
ASA VPN SPECIFIC

Connections
Select the IPsec VPN connections you want to add a sensor for.
You see a list of all active IPsec VPN connections available on the
target ASA, listed with remote IP, user name, and the kind of
connection. 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. Note: This sensor type can only
monitor VPN connections based on IPsec. This means, for example,
that connections using "Cisco AnyConnect" will not be listed here.
Sensor Settings
19.09.2014
1183


Sensor Name

Tags

Priority
(top priority).
ASA VPN SPECIFIC

Remote IP
The IP address of the connection this sensor monitors. Once a

the sensor anew. Note: This sensor type can only monitor VPN
connections based on IPsec.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1184
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1185

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1186
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1187


menu bar.
Dependency
dependent on.
Delay (Seconds)
1188
19.09.2014

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

Notifications
19.09.2014
1189

Others
1190
141
section.
19.09.2014

101 SNMP Cisco ASA VPN Users Sensor
6.8.101 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). It can show the number of currently connected accounts and if a user
account is currently offline or online.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
1191

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1192
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1193


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1194
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1195

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

Notifications
1196
19.09.2014

Others
19.09.2014
141
section.
1197

102 SNMP Cisco CBQoS Sensor
6.8.102 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 shows current and maximum queue
depth, pre policy packets, pre and post policy size, drop packets and size, drop packets
without buffer, as well as fragment packets and size, depending on the particular class type.
2491 section.
Add Sensor
In order to monitor quality-of-service via compatible devices, PRTG will create one sensor for
each CBQoS entry you choose. The settings you make in this dialog are valid for all of the
CLASS BASED QOS SPECIFIC

CBQoS Entries
table head.
Sensor Settings
1198
19.09.2014


Sensor Name

Tags

Priority
(top priority).
CLASS BASED QOS SPECIFIC

Interface
Description
Shows further information about the parameter this sensor is

monitoring. Once a sensor is created, you cannot change this
Bitmask
ObjectID
ConfigID
19.09.2014
1199

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1200
19.09.2014

Inherited Settings
described below.

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
19.09.2014
1201


Dependency Type

can choose between:
menu bar.
Dependency
dependent on.
Delay (Seconds)
1202
19.09.2014

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

Notifications
19.09.2014
1203

Others
1204
141
section.
19.09.2014

103 SNMP Cisco System Health Sensor
6.8.103 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 percentage CPU load, available memory
in absolute and percentage values, the status of power supplies, temperatures (in Celsius), the
current temperature states, and many more, depending on the available components of your
device.
2491 section.
Add Sensor
In order to monitor the system health of a Cisco device, PRTG will create one sensor for each
measurement you choose. The settings you make in this dialog are valid for all of the sensors
that are created.
CISCO SYSTEM HEALTH SPECIFIC

Measurement
table head.
Sensor Settings
19.09.2014
1205


Sensor Name

Tags

Priority
(top priority).
CISCO SYSTEM HEALTH SPECIFIC

Measurement
Shows the ID of the measurement that this sensor is monitoring.

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1206
19.09.2014

SENSOR DISPLAY
Stack Unit
19.09.2014

1207

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1208
19.09.2014

Inherited Settings
described below.

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
19.09.2014
1209


Dependency Type

can choose between:
menu bar.
Dependency
dependent on.
Delay (Seconds)
1210
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1211

More

Notifications
Others
1212
141
section.
19.09.2014

104 SNMP Cisco UCS Chassis Sensor
6.8.104 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 configuration, license, oper, the operability, power status, thermal
status, as well as the serial electronic erasable programmable read-only memory (SEEPROM)
status. The creation of these channels depends on the available measurement components on
the UCS chassis.
2491 section.
Add Sensor
In order to monitor the health status of a Cisco UCS chassis, PRTG will create one sensor for
each chassis you choose. The settings you make in this dialog are valid for all of the sensors
that are created.
SENSOR SETTINGS
Chassis
Select the chassis you want to add a sensor for. You see a list with
head.
Sensor Settings
19.09.2014
1213


Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Chassis
Shows the chassis monitored by this sensor. Once a sensor is

anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1214
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1215

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1216
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1217


menu bar.
Dependency
dependent on.
Delay (Seconds)
1218
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1219

More

Notifications
Others
1220
141
section.
19.09.2014

105 SNMP Cisco UCS Physical Disk Sensor
6.8.105 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). It can show
the operability status of the disk, as well as if the monitored disk is still connected.
2491 section.
Add Sensor
In order to monitor physical disks in a UCS device, PRTG will create one sensor for each disk
you choose. The settings you make in this dialog are valid for all of the sensors that are
created.
U CS PHYSICAL DISK
Disks
head.
Note: Only working disks (with the current status Up or Warning)
will be shown here.
Sensor Settings
19.09.2014
1221


Sensor Name

Tags

Priority
(top 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

Chart Type

for each channel.
1222
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1223

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1224
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1225


menu bar.
Dependency
dependent on.
Delay (Seconds)
1226
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1227

More

Notifications
Others
1228
141
section.
19.09.2014

106 SNMP Cisco UCS System Health Sensor
6.8.106 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). It can show
the following: the number of operable resp. inoperable fans, the status of fan performance, fan
thermal and fan voltage, and if a fan failure is predicted; the number of operable resp.
inoperable fan modules, the status of fan module performance, fan module thermal and fan
module voltage, and if a fan module failure is predicted; the number of operable resp.
inoperable power supplies, the status of power supply performance, power supply thermal and
power supply voltage, and if a power supply failure is predicted.
The creation of these channels depends on the available measurement components in the UCS
device.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

19.09.2014
1229


Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1230
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1231


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1232
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1233

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1234
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1235

107 SNMP CPU Load Sensor
6.8.107 SNM P CPU Load Sensor

The SNMP CPU Load sensor monitors the system load using Simple Network Management
Protocol (SNMP). It can show the load of several CPUs in percent.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel
1236

19.09.2014

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1237

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1238
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1239


menu bar.
Dependency
dependent on.
Delay (Seconds)
1240
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1241

More

Notifications
Others
1242
141
section.
19.09.2014

108 SNMP Custom Sensor
6.8.108 SNM P Custom Sensor

The SNMP Custom sensor monitors a numerical value returned by a specific OID using Simple
Network Management Protocol (SNMP).
2491 section.
Add Sensor
OID VALU ES
Channel Name
Enter a name for the channel in which the sensor shows the
results at the given OID. Please enter a string. You can change this
value later in the respective channel settings 2220 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
19.09.2014
1243


Sensor Name

Tags

Priority
(top priority).
1244
19.09.2014

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: at 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
the given OID. Please enter a string.
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
change.
SENSOR DISPLAY
Primary Channel

Chart Type
19.09.2014
1245

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
1246
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1247


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1248
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1249

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: How do I find out what OID I need to use for a custom sensor?

1250
19.09.2014

Notifications
Others
19.09.2014
141
section.
1251

109 SNMP Custom String Sensor
6.8.109 SNM P Custom String Sensor

The SNMP Custom String sensor monitors a string returned by a specific OID using Simple
Network Management Protocol (SNMP). It can check for keywords. If you want to use limits for
the sensor channel value, you can also extract a numeric value contained in the string.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1252
19.09.2014

OID VALU ES
OID Value
Enter the OID of the SNMP object you want to receive a string
from. Note: Most OIDs begin with 1.3.6.1. However, entering OIDs
starting with 1.0, or 1.1, or 1.2 is also allowed. If you want to
disable the validation of your entry entirely, add the string
norfccheck: at the beginning of your OID, for example,
norfccheck:2.0.0.0.1.
Maximum Length of
String
Define the maximum length of the string that will be received from
the SNMP object at the given OID. If the string is longer than this
value, the sensor will be set to an error status. Please enter an
integer value or leave the field empty.
If Value Changes

19.09.2014
1253

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 2587 . If the data does not include the
search pattern, the sensor will be set to an error state. Please
For Keyword Search
Use

the field above.
plain text search.
Expression 2587 .
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 2587 . If the data does include the
search pattern, the sensor will be set to an error state. Please
For Keyword Search

Use

the field above.
plain text search.
Expression 2587 .
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 2587 . If the data does not include the
search pattern, the sensor will be set to a warning state. Please
For Keyword Search
Use
1254

the field above.
plain text search.
19.09.2014

Expression 2587 .

EXTENDED PR OCESSING
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 in order to use it with channel limits (see
Sensor Channels Set t ings 2220 ).
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
1260 below.
Regular Expression
This setting is only visible if number extraction is enabled above.

Enter a Regular Expression 2587 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 number extraction is enabled 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.
Thousands Separator

Define which character is used as thousands separator for the
number extracted above. Please enter a string or leave the field
empty.
SENSOR DISPLAY
Primary Channel

Chart Type
19.09.2014
1255

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
1256
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1257


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1258
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1259

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
Example: Number Extraction with Regular Expression

If you want to extract a number in the response string using a regular expression, please note
that the index for captures in this sensor is based on 1 (not on 0). Furthermore, capturing
groups are not created automatically. The example below will illustrate this issue.
Consider the following string as returned by a request for CPU usage:
5 Sec (3.49%), 1 Min (3.555%), 5 Min (3.90%)
Assuming you would like to filter for the number 3.555, i.e., the percentage in the second
parentheses. Then enter the following regex in the Regular Expression field:
(\d+\.\d+).*(\d+\.\d+).*(\d+\.\d+)
As Index of Capt uring Group enter 3. This will extract the desired number 3.555.
1260
19.09.2014

The index has to be 3 in this case because the capturing groups here are the following:
Group 1 contains "3.49%), 1 Min (3.555), 5 Min (3.90"
Group 2 contains "3.49"
Please keep in mind this note about index and capturing groups when using number
extraction.
More
Knowledge Base: How do I find out what OID I need to use for a custom sensor?

Notifications
Others
19.09.2014
141
section.
1261

110 SNMP Dell Hardware Sensor
6.8.110 SNM P Dell Hardware Sensor

The SNMP Dell Hardware sensor monitors performance counters on a Dell hardware device
using Simple Network Management Protocol (SNMP). It can show, for example, data about the
system management software and system status, information about chassis and BIOS, various
hardware parameters, and other valuable data. The data that you can monitor with this sensor
depends on the available performance counters on the target system.
2491 section.
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 1268 below.
Add Sensor
In order to monitor a Dell device, PRTG will create one sensor for each hardware performance
counter you choose. The settings you make in this dialog are valid for all of the sensors that
are created.
DELL HAR DWAR E SPECIFIC

Library OIDs

in the table head.
Sensor Settings
1262
19.09.2014


Sensor Name

Tags

Priority
(top priority).

Selected Interface

Unit String
Define the unit of the numerical data that will be received at the
given OID. Please enter a string.
Multiplication
the quotient here. Please enter an integer or float value.
Division
divisor here. Please enter an integer or float value.
If Value Changes
Define what will be done in case the value of this sensor changes.
19.09.2014
1263

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1264
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1265


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1266
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1267

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: What do I need to monitor Dell servers?

1268
19.09.2014

Notifications
Others
19.09.2014
141
section.
1269

111 SNMP Dell PowerEdge Physical Disk Sensor
6.8.111 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). It can show the disk status, the roll
up status, the component status, as well as if there is currently a warning regarding the SelfMonitoring, Analysis and Reporting Technology (S.M.A.R.T.) status.
2491 section.
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
In order to monitor physical disks in a Dell PowerEdge server, PRTG will create one sensor for
each disk. The settings you make in this dialog are valid for all of the sensors that are created.
DELL POWER EDGE PHYSICAL DISK SETTINGS

Disk
head.
Sensor Settings
1270
18.11.2014


Sensor Name

Tags

Priority
(top priority).
DELL POWER EDGE PHYSICAL DISK SETTINGS

Disk
Shows the name of the disk that this sensor is monitoring. Once a
the sensor anew.
Data Source
Shows the interface which is used to get monitoring data. This is

either Dell OpenManage Server Administrator (OMSA) or Integrated
Dell Remote Access Controller (iDRAC).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
18.11.2014
1271

SENSOR DISPLAY
Stack Unit
1272

18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1273


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1274
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1275

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1276
18.11.2014

More
Knowledge Base: My Dell PowerEdge sensor fails to validate and I can't add it. What can I do?

Notifications
Others
18.11.2014
141
section.
1277

112 SNMP Dell PowerEdge System Health Sensor
6.8.112 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 global
system status, the power supply status, the temperature status, the cooling device status, the
memory device status, the voltage status, and many more, depending on the available
components of your device.
2491 section.
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
In order to monitor the health status of a Dell PowerEdge server, PRTG will create one sensor
for each chassis you choose. The settings you make in this dialog are valid for all of the
DELL POWER EDGE SYSTEM HEALTH SPECIFIC

Chassis
1278
Select the chassis you want to add a sensor for. You see a list with
head.
19.09.2014

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
DELL POWER EDGE SYSTEM HEALTH SPECIFIC

Chassis
Shows the chassis this sensor monitors. Once a sensor is created,

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).
19.09.2014
1279

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
1280

19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1281


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1282
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1283

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1284
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1285

113 SNMP Disk Free Sensor
6.8.113 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). It can show free space in percent and in total, as well as the
total space. Note: This sensor uses more generic Object Identifier (OID) values compared to
the SNMP Linux Disk Free Sensor 1423 .
2491 section.
Add Sensor
In order to monitor memory usage, PRTG will create one sensor for each memory type you
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
1286

19.09.2014


Tags

Priority
(top priority).
DISK FR EE SETTINGS
Disk
the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1287

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1288
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1289


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1290
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1291

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1292
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1293

114 SNMP GSA System Health Sensor
6.8.114 SNM P GSA Sy stem Health Sensor

The SNMP GSA System Health sensor monitors the system health of a Google Search Appliance
(GSA) via Simple Network Management Protocol (SNMP). It can show the number of queries per
minute, the number of processed documents, the number of indexed documents, the number
of processed bytes, the activity status of crawling, the crawling rate per second, as well as the
health status of disk, temperature, and machine.
Note: The location you provide in the GSA's SNMP configuration section will be shown in
PRTG's GeoMaps 2258 . In order to use SNMP v3 for monitoring, you need to add an SNMP v3
user in the GSA's SNMP configuration.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1294
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1295

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1296
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1297


menu bar.
Dependency
dependent on.
Delay (Seconds)
1298
19.09.2014

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

Notifications
19.09.2014
1299

Others
1300
141
section.
19.09.2014

115 SNMP Hardware Status Sensor
6.8.115 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). It shows the current status of the
component, as well as the number of errors per time period.
2491 section.
Add Sensor
In order to monitor hardware components of a server, PRTG will create one sensor for each
component you choose. The settings you make in this dialog are valid for all of the sensors
that are created.
HAR DWAR E SPECIFIC

Hardware Component
Select the hardware components you want to add a sensor for.

in the table head.
Sensor Settings

Sensor Name
19.09.2014

1301


Tags

Priority
(top 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

Chart Type

for each channel.
1302
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1303

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1304
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1305


menu bar.
Dependency
dependent on.
Delay (Seconds)
1306
19.09.2014

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

Notifications
19.09.2014
1307

Others
1308
141
section.
19.09.2014

116 SNMP HP LaserJet Hardware Sensor
6.8.116 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 status of
the toner, of the paper, or if there is a paper jam.
2491 section.
Add Sensor
In order to monitor an HP LaserJet printer, PRTG will create one sensor for each performance
are created.

Library OIDs
Select the performance counters you want to add a sensor for. A

list of available counters for your device is shown with category
and name:
Toner/St at us
Paper/St at us
Jam/St at us
in the table head.
Sensor Settings
19.09.2014
1309


Sensor Name

Tags

Priority
(top priority).
HP LASER JET SPECIFIC

Selected Interface

If Value Changes

SENSOR DISPLAY
Primary Channel

Chart Type
1310
19.09.2014

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1311

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1312
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1313


menu bar.
Dependency
dependent on.
Delay (Seconds)
1314
19.09.2014

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

Notifications
19.09.2014
1315

Others
1316
141
section.
19.09.2014

117 SNMP HP ProLiant Logical Disk Sensor
6.8.117 SNM P HP ProLiant Logical Disk Sensor

The SNMP HP ProLiant Logical Disk sensor monitors a logical disk in an HP server via Simple
Network Management Protocol (SNMP). It can show disk status and completion. Completion is
only important when the disk status is "Reconstructing" or "Expanding" and illustrates the
progress of this task.
Note: This sensor type supports monitoring HP Integrated Lights-Out (iLO) as of iLO version 3.
We recommend you to use iLO 4 because this version applies its own dedicated SNMP
counters while iLO 3 only forwards SNMP counters from the particular operating system.
2491 section.
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. In
order to receive SNMP data from RAID controllers you will 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
In order to monitor logical disks in a HP server, PRTG will create one sensor for each disk you
18.11.2014
1317

HP PR OLIANT LOGICAL DISK SETTINGS

Disk
head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
HP PR OLIANT LOGICAL DISK SETTINGS

Disk
1318
the sensor anew.
18.11.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
1319

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1320
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1321


menu bar.
Dependency
dependent on.
Delay (Seconds)
1322
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
1323

More
Knowledge Base: Monitor HP ProLiant via SNMP

Notifications
Others
1324
141
section.
18.11.2014

118 SNMP HP ProLiant Memory Controller Sensor
6.8.118 SNM P HP ProLiant M emory Controller Sensor

The SNMP HP ProLiant Memory Controller sensor monitors a memory controller in an HP server
via Simple Network Management Protocol (SNMP). It shows the error status of the controller,
the condition of the controller, and states and conditions of available modules. Note: If
modules are inserted at a later point, the sensor has to be added again.
For supported lookup values of this specific sensor, please see subsection More
1332
below.
2491 section.

Add Sensor
In order to monitor memory controllers in a HP server, PRTG will create one sensor for each
controller you choose. The settings you make in this dialog are valid for all of the sensors that
are created.
18.11.2014
1325

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

Tags

Priority
(top priority).
HP PR OLIANT MEMOR Y CONTR OLLER SETTINGS

Controller
1326
Shows the name of the controller that this sensor is monitoring.

18.11.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
1327

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1328
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1329


menu bar.
Dependency
dependent on.
Delay (Seconds)
1330
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
1331

More
Knowledge Base: Which lookup values are supported by the SNMP HP ProLiant Memory
Controller Sensor?

Notifications
Others
1332
141
section.
18.11.2014

119 SNMP HP ProLiant Network Interface Sensor
6.8.119 SNM P HP ProLiant Network Interface Sensor

The SNMP HP ProLiant Network Interface sensor monitors a network interface in an HP server
via Simple Network Management Protocol (SNMP). It can show traffic in and out, the number of
transmitted and received good frames, the number of transmitted and received bad frames,
alignment and FCS (Frame Check Sequence) errors, late and excessive collisions, carrier sense
errors, and when the frames are too long.
2491 section.

Add Sensor
In order to monitor network interfaces in a HP server, PRTG will create one sensor for each
interface. The settings you make in this dialog are valid for all of the sensors that are created.
18.11.2014
1333

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: In the HP ProLiant Net work Int erface Set t ings section, the St at us 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).
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1334
18.11.2014

HP PR OLIANT NETWOR K INTER FACE SETTINGS

Network Interface
Shows the name of the interface that this sensor is monitoring.

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2220 settings).
Stack Unit

Inherited Settings
described below.
18.11.2014
1335

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1336
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1337


menu bar.
Dependency
dependent on.
Delay (Seconds)
1338
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
1339

More

Notifications
Others
1340
141
section.
18.11.2014

120 SNMP HP ProLiant Physical Disk Sensor
6.8.120 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
Network Management Protocol (SNMP). It can show read and written sectors, hard and
corrected read errors, hard and corrected write errors, the disk status, the drive condition, the
Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status, and if the threshold is
passed.
2491 section.

Add Sensor
In order to monitor physical disks in a HP server, PRTG will create one sensor for each disk.
The settings you make in this dialog are valid for all of the sensors that are created.
18.11.2014
1341

HP PR OLIANT PHYSICAL DISK SETTINGS

Disk
head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
HP PR OLIANT PHYSICAL DISK SETTINGS

Disk
1342
the sensor anew.
18.11.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2220 settings).
Stack Unit

Inherited Settings
described below.
18.11.2014
1343

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1344
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1345


menu bar.
Dependency
dependent on.
Delay (Seconds)
1346
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
1347

More

Notifications
Others
1348
141
section.
18.11.2014

121 SNMP HP ProLiant System Health Sensor
6.8.121 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). It can show the overall status, the
thermal status, the system fan status, the CPU fan status, the number of broken and running
fans, as well as the number of broken and running fans that are fault tolerant, and status and
condition of the power supply.
Furthermore, it can show several temperatures for various components of an HP ProLiant
serverfor example: memory, power supply, CPU, system, and storage. It is also possible to
display the power consumption and disk controller status. These channels are created at runtime, depending on the available measurement components.
The SNMP HP ProLiant System Health sensor has predefined limits for temperatures and broken
frames. You can change these limits individually in the channel settings 2220 .
Note: RAID controllers which have no hard disks assigned might cause a Down status 121 . In
this case, deactivate the respective controller(s) in the HP ProLiant BIOS to avoid sensor errors.
2491 section.

Add Sensor
18.11.2014
1349

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1350
18.11.2014

SENSOR DISPLAY
2220 settings).
Stack Unit

Inherited Settings
described below.
18.11.2014
1351

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1352
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1353


menu bar.
Dependency
dependent on.
Delay (Seconds)
1354
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
1355

More
Knowledge Base: Why is my SNMP HP ProLiant System Health sensor in error status after
updating PRTG?

Notifications
Others
1356
141
section.
18.11.2014

122 SNMP IBM System X Logical Disk Sensor
6.8.122 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
Network Management Protocol (SNMP). It shows the status of a logical disk.
2491 section.
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.
Add Sensor
In order to monitor the logical disks of an IBM device, PRTG will create one sensor for each
disk you choose. The settings you make in this dialog are valid for all of the sensors that are
created.
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
19.09.2014
1357


Sensor Name

Tags

Priority
(top priority).
IBM SYSTEM X LOGICAL DISK SETTINGS

Disk
Shows the ID of the logical disk. Once a sensor is created, you

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1358
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1359

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1360
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1361


menu bar.
Dependency
dependent on.
Delay (Seconds)
1362
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1363

More
Knowledge Base: What are the requirements to monitor IBM System x?

Notifications
Others
1364
141
section.
19.09.2014

123 SNMP IBM System X Physical Disk Sensor
6.8.123 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
Simple Network Management Protocol (SNMP). It shows the status of a physical disk.
2491 section.

More below.
Add Sensor
In order to monitor the physical disks of an IBM device, PRTG will create one sensor for each
created.
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
19.09.2014
1365


Sensor Name

Tags

Priority
(top priority).
IBM SYSTEM X PHYSICAL DISK SETTINGS

Disk
Shows the ID of the physical disk. Once a sensor is created, you

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1366
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1367

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1368
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1369


menu bar.
Dependency
dependent on.
Delay (Seconds)
1370
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1371

More

Notifications
Others
1372
141
section.
19.09.2014

124 SNMP IBM System X Physical Memory Sensor
6.8.124 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). It shows the condition of a memory
module, as well as its power status.
2491 section.

More below.
Add Sensor
In order to monitor the memory modules of an IBM device, PRTG will create one sensor for
each module you choose. The settings you make in this dialog are valid for all of the sensors
that are created.
IBM SYSTEM X PHYSICAL MEMOR Y SETTINGS

Module
Select the memory modules 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
19.09.2014
1373


Sensor Name

Tags

Priority
(top priority).
IBM SYSTEM X PHYSICAL MEMOR Y SETTINGS

Name
Caption
Serial Number
Shows further information about the module. Once a sensor is

anew.
Size
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1374
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1375

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1376
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1377


menu bar.
Dependency
dependent on.
Delay (Seconds)
1378
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1379

More

Notifications
Others
1380
141
section.
19.09.2014

125 SNMP IBM System X System Health Sensor
6.8.125 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
Simple Network Management Protocol (SNMP). It can show revolutions per minute of fans (or
the current percentage of the possible maximum), temperatures of ambient and CPUs, voltage,
status of power supplies, and many more, depending on the available measurement
components.
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 for this via channel limits 2221 .
2491 section.

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
In order to monitor the system health of an IBM device, PRTG will create one sensor for each
measurement you choose. The settings you make in this dialog are valid for all of the sensors
that are created.
19.09.2014
1381

IBM SYSTEM X SYSTEM HEALTH SPECIFIC

Measurement
table head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
IBM SYSTEM X SYSTEM HEALTH SPECIFIC

Source
Shows the source of the measurement. Once a sensor is created,

Measurement
Shows the ID of the measurement that this sensor is monitoring.

1382
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1383

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1384
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1385


menu bar.
Dependency
dependent on.
Delay (Seconds)
1386
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1387

More

Notifications
Others
1388
141
section.
19.09.2014

126 SNMP interSeptor Pro Environment Sensor
6.8.126 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
monitor temperature and humidity as measured by the Jacarta interSeptor Pro device.
Note: In order to monitor an interSeptor Pro device's data 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 for this purpose, and allow access for PRTG's IP address.
2491 section.
Add Sensor
In order to monitor the environment via an interSeptor Pro device, PRTG will create one sensor
for each measuring point you choose. The settings you make in this dialog are valid for all of
the sensors that are created.
INTER SEPTOR ENVIR ONMENT SPECIFIC

Measuring Point
Select the measuring points you want to add a sensor for. You see
table head.
Sensor Settings
19.09.2014
1389


Sensor Name

Tags

Priority
(top priority).
INTER SEPTOR ENVIR ONMENT SPECIFIC

Name
Shows information about the measurement which this sensor

Measuring Point
Shows the measuring point which this sensor monitors. Once a

the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1390
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1391

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1392
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1393


menu bar.
Dependency
dependent on.
Delay (Seconds)
1394
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1395

More

Notifications
Others
1396
141
section.
19.09.2014

127 SNMP LenovoEMC Physical Disk Sensor
6.8.127 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 Up), Unknown and Foreign (both
with sensor status Warning), as well as Faulted and Missing (both with sensor status Down).
2491 section.
Add Sensor
In order to monitor physical disks in a LenovoEMC NAS, PRTG will create one sensor for each
disk you select. The settings you make in this dialog are valid for all of the sensors that are
created.
LENOVOEMC PHYSICAL DISK SETTINGS

Disk
head.
Sensor Settings
19.09.2014
1397


Sensor Name

Tags

Priority
(top priority).
LENOVOEMC PHYSICAL DISK SETTINGS

Disk
Shows the disk monitored by this sensor. Once a sensor is

anew.
Name
Shows the name of the disk monitored by this sensor. Once a

the sensor anew.
Size
Shows the size of the disk monitored by this sensor. Once a

the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type
1398
19.09.2014

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1399

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1400
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1401


menu bar.
Dependency
dependent on.
Delay (Seconds)
1402
19.09.2014

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

Notifications
19.09.2014
1403

Others
1404
141
section.
19.09.2014

128 SNMP LenovoEMC System Health Sensor
6.8.128 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. States can be Normal (sensor status Up), Unknown, Rebuilding,
Degraded, and RebuildFS (all with sensor status Warning), as well as 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.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
1405

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1406
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1407


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1408
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1409

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

Notifications
1410
19.09.2014

Others
19.09.2014
141
section.
1411

129 SNMP Library Sensor
6.8.129 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 1421 for details.
2491 section.
Add Sensor
Manually add 224 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 2611 .
List of SNMP Library Files
1412
18.11.2014

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

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.
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 2611 . For more information and download of
MIB Import er, please see the link in the More 1421 section below.
SNMP Library SensorAdd Sensor Settings

1414
18.11.2014

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 you
click the Cont inue button.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
18.11.2014
1415

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 or float value.
Division
Enter the divisor if you want to divide the received data by a

certain value. Please enter an integer or float value.
If Value Changes
change.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1416
18.11.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
18.11.2014
1417

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1418
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1419


menu bar.
Dependency
dependent on.
Delay (Seconds)
1420
18.11.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: How do SNMP, MIBs and OIDs work?
Knowledge Base: How can I import my MIB files into PRTG?

18.11.2014
1421

Notifications
Others
1422
141
section.
18.11.2014

130 SNMP Linux Disk Free Sensor
6.8.130 SNM P Linux Disk Free Sensor

The SNMP Linux Disk Free sensor monitors free space on disks of a Linux/Unix system using
Simple Network Management Protocol (SNMP). It shows the free disk space in total, the free
disk space in percent and bytes for every mounted partition, and 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
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
26.09.2014
1423

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 2220 . 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.
1424
26.09.2014


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


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

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
26.09.2014
1427

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1428
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
1429


menu bar.
Dependency
dependent on.
Delay (Seconds)
1430
26.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
26.09.2014
1431

More
Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values for
my target Linux system?
Knowledge Base: Checklist: Setting up SNMP on Linux

Notifications
Others
1432
141
section.
26.09.2014

131 SNMP Linux Load Average Sensor
6.8.131 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). It shows the average system load within a
one, five, and 15 minutes interval (each in one channel).
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
1433

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1434
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1435


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1436
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1437

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

1438
19.09.2014

Notifications
Others
19.09.2014
141
section.
1439

132 SNMP Linux Meminfo Sensor
6.8.132 SNM P Linux M eminfo Sensor

The SNMP Linux Meminfo sensor monitors the memory usage of a Linux/Unix system using
Simple Network Management Protocol (SNMP). It shows the following values:
available memory in absolute and percentage values,
used physical memory (free memory plus buffer plus cache) in absolute values,
free physical memory (free memory plus buffer + cache) in percent,
used swap memory in percent,
free swap memory in absolute values,
used memory on the whole system (physical memory plus swap) in percent,
and free memory on the whole system (physical memory plus swap) in absolute values.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1440
26.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
26.09.2014
1441

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1442
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
1443


menu bar.
Dependency
dependent on.
Delay (Seconds)
1444
26.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
26.09.2014
1445

More

Notifications
Others
1446
141
section.
26.09.2014

133 SNMP Linux Physical Disk Sensor
6.8.133 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). It shows read and written bytes
per second, as well as the number of read and write accesses per second.
2491 section.
Add Sensor
To monitor I/O on disks of a Linux/Unix system, PRTG creates one sensor for each disk you
PHYSICAL DISK SETTINGS

Disk
Select one or more disks you want to add a sensor for. You see a
table head.
Sensor Settings

Sensor Name
18.11.2014

1447


Tags

Priority
(top priority).
PHYSICAL DISK SETTINGS

Disk
Bitmask
Shows further information about the disk that this sensor

It is shown for reference purposes only. If you need to change this,
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1448
18.11.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
18.11.2014
1449

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1450
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1451


menu bar.
Dependency
dependent on.
Delay (Seconds)
1452
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
1453

More

Notifications
Others
1454
141
section.
18.11.2014

134 SNMP Memory Sensor
6.8.134 SNM P M emory Sensor

The SNMP Memory sensor monitors the memory usage of a system via Simple Network
Management Protocol (SNMP). It can show the available memory in total and in percent, as well
as the total memory. Note: This sensor uses more generic Object Identifier (OID) values
compared to the SNMP Linux Meminfo Sensor 1440 .
2491 section.
Add Sensor
In order to monitor memory usage, PRTG will create one sensor for each memory type you
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
19.09.2014

1455


Tags

Priority
(top priority).
MEMOR Y SETTINGS
Memory
Shows the type of the memory that this sensor is monitoring.

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1456
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1457

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1458
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1459


menu bar.
Dependency
dependent on.
Delay (Seconds)
1460
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1461

More

Notifications
Others
1462
141
section.
19.09.2014

135 SNMP NetApp Disk Free Sensor
6.8.135 SNM P NetApp Disk Free Sensor

The SNMP NetApp Disk Free sensor monitors free space on disks of a NetApp storage system
via Simple Network Management Protocol (SNMP). It can show free disk space in total and
percent, deduplication saved space and shared space in total and in percent, the disk free
status, as well as percentage values for free files and INodes .
2491 section.
Add Sensor
In order to monitor disk space on a NetApp, PRTG will create one sensor for each disk. The
NETAPP DISK FR EE SETTINGS

File System
head.
Sensor Settings

Sensor Name
19.09.2014

1463


Tags

Priority
(top priority).

File System
the sensor anew.
Virtual Disk
Shows the name of the virtual disk that this sensor is monitoring (if
applicable). Once a sensor is created, you cannot change this
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1464
19.09.2014

SENSOR DISPLAY
2220 settings).
Stack Unit

Inherited Settings
described below.
19.09.2014
1465

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1466
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1467


menu bar.
Dependency
dependent on.
Delay (Seconds)
1468
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1469

More
Knowledge Base: How can I monitor capacity and used disk space on a NetApp?

Notifications
Others
1470
141
section.
19.09.2014

136 SNMP NetApp Enclosure Sensor
6.8.136 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 measure temperatures, fans, voltages, and currents.
2491 section.
Add Sensor
To monitor power supply and cooling of an enclosure on a NetApp, PRTG creates one sensor
for each enclosure/measurement combination you select. The settings you make in this dialog
are valid for all of the sensors 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

Sensor Name
18.11.2014

1471


Tags

Priority
(top 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

1472
18.11.2014

NETAPP SPECIFIC
N/A Measurements
Define the sensor behavior if the requested NetApp value is not

available ("N/A" values). Choose between:
Int erpret as error (default ): Choose this option to set the
sensor to a Down status if a measurement is not available. We
recommend you to use this setting to not miss any hardware
errors.
Int erpret as valid: Choose this option to handle unavailable
measurements as valid sensor results to keep the sensor in Up
status. This might be useful, for example, if a hardware sensor on
the NetApp is disabled for some reason but actually there is no
hardware error. If the NetApp returns an "N/A" measurement, the
sensor interprets this as "0".
We recommend you to use the lookup file
prt g.st andardlookups.net app.not available.ovl for channels
with unavailable measurements if you choose this option. This
replaces "0" with the message "Not Available". Open the Sensor
Channels Set t ings 2220 of the affected channel(s) and choose this
file in section Value Lookup. For details, please see section
Define Lookups 2579 .
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2220 settings).
18.11.2014
1473

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1474
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1475


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1476
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1477

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1478
18.11.2014

More

Notifications
Others
18.11.2014
141
section.
1479

137 SNMP NetApp I/O Sensor
6.8.137 SNM P NetApp I/O Sensor

The SNMP NetApp I/O sensor monitors input/output operations (IOPS) on a NetApp storage
system via Simple Network Management Protocol (SNMP). It can show FCP Read, CIFS Ops, Disk
Read, Disk Write, FCP Ops, FCP Write, HTTP Ops, ISCSI Ops, ISCSI Read, ISCSI Write, Network
Received, Network Sent, NFS Ops, Tape Read, and Tape Write.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1480
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2220 settings).
Stack Unit

Inherited Settings
described below.
19.09.2014
1481

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1482
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1483


menu bar.
Dependency
dependent on.
Delay (Seconds)
1484
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1485

More

Notifications
Others
1486
141
section.
19.09.2014

138 SNMP NetApp License Sensor
6.8.138 SNM P NetApp License Sensor

The SNMP NetApp License sensor monitors the licenses for the services of a NetApp storage
system via Simple Network Management Protocol (SNMP). It indicates 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.
2491 section.
Add Sensor
In order to monitor licenses on a NetApp, PRTG will create one sensor for each license. The
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
19.09.2014

1487


Tags

Priority
(top priority).
NETAPP LICENSE SETTINGS

License for Service
Shows the name of the license that this sensor is monitoring.

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1488
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1489

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1490
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1491


menu bar.
Dependency
dependent on.
Delay (Seconds)
1492
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1493

More

Notifications
Others
1494
141
section.
19.09.2014

139 SNMP NetApp Logical Unit Sensor
6.8.139 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). It can show
the total number of operations, the amount of read and written data, the number of errors, the
number of read, write, and other operations, as well as the overall status of the logical unit.
2491 section.
Add Sensor
In order to monitor logical units on a NetApp, PRTG will create one sensor for each unit. The

Logical Unit
Select the logical units you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name
19.09.2014

1495


Tags

Priority
(top priority).

Logical Unit
Shows the name of the logical unit that this sensor is monitoring.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1496
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1497

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1498
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1499


menu bar.
Dependency
dependent on.
Delay (Seconds)
1500
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1501

More

Notifications
Others
1502
141
section.
19.09.2014

140 SNMP NetApp Network Interface Sensor
6.8.140 SNM P NetApp Network Interface Sensor

The SNMP NetApp Network Interface sensor monitors a network card of a NetApp storage
system via Simple Network Management Protocol (SNMP). It can show traffic in and out, as well
as the number of errors per second (in and out).
2491 section.
Add Sensor
In order to monitor network interfaces on a NetApp, PRTG will create one sensor for each
interface. The settings you make in this dialog are valid for all of the sensors that are created.
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
19.09.2014

1503


Tags

Priority
(top priority).
NETAPP NETWOR K INTER FACE SETTINGS

Network Interface
Shows the name of the interface that this sensor is monitoring.

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1504
19.09.2014

SENSOR DISPLAY
2220 settings).
Stack Unit

Inherited Settings
described below.
19.09.2014
1505

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1506
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1507


menu bar.
Dependency
dependent on.
Delay (Seconds)
1508
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1509

More

Notifications
Others
1510
141
section.
19.09.2014

141 SNMP NetApp System Health Sensor
6.8.141 SNM P NetApp Sy stem Health Sensor

The SNMP NetApp System Health sensor monitors the status of a NetApp storage system via
Simple Network Management Protocol (SNMP). It can show the CPU load in percent, active
restore, current CIFS users; the number of disks active, being added, being scrubbed, failed,
failing soon, being out of date, reconstructing (parity), spare, verifying parity, and total; the
number of fans and power supplies failed; the max used disk space and max used inodes, in
percent. This depends on the available measurement components on the NetApp.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
1511

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2220 settings).
Stack Unit

Inherited Settings
described below.
1512
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1513


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1514
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1515

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1516
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1517

142 SNMP Poseidon Environment Sensor
6.8.142 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, for example, humidity and temperature in the environment, depending on available
measurement components on the hardware device.
2491 section.
Add Sensor
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
1518

19.09.2014


Tags

Priority
(top priority).
POSEIDON ENVIR ONMENT SPECIFIC

Name
Unit
Measuring Point
Shows further information about the measurement. Once a sensor

anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1519

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1520
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1521


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1522
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1523

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

Notifications
1524
19.09.2014

Others
19.09.2014
141
section.
1525

143 SNMP Printer Sensor
6.8.143 SNM P Printer Sensor

The SNMP Printer sensor is a generic sensor which monitors various types of printers via
Simple Network Management Protocol (SNMP). It can show the total number of printed pages,
the fill level of cartridges and toners, and the status of the printer cover. Additionally, the
sensor shows the printer status as sensor message.
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
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

1526
19.09.2014


Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1527

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1528
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1529


menu bar.
Dependency
dependent on.
Delay (Seconds)
1530
19.09.2014

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

Notifications
19.09.2014
1531

Others
1532
141
section.
19.09.2014

144 SNMP QNAP Logical Disk Sensor
6.8.144 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). It can show free space and
free bytes, as well as the status of a volume.
2491 section.
Add Sensor
In order to monitor the logical disks in a QNAP NAS, PRTG will create one sensor for each disk
created.
QNAP NAS SETTINGS

Disk
head.
Sensor Settings

Sensor Name
19.09.2014

1533


Tags

Priority
(top priority).
QNAP NAS SETTINGS

Disk
Description
File System

anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1534
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1535

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1536
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1537


menu bar.
Dependency
dependent on.
Delay (Seconds)
1538
19.09.2014

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

Notifications
19.09.2014
1539

Others
1540
141
section.
19.09.2014

145 SNMP QNAP Physical Disk Sensor
6.8.145 SNM P QNAP Phy sical Disk Sensor

The SNMP QNAP Physical Disk sensor monitors a physical disk in a QNAP Network Attached
Storage (NAS) via Simple Network Management Protocol (SNMP). It can show the temperature,
the HD status, and the Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) status
of the disk.
2491 section.
Add Sensor
In order to monitor the physical disks in a QNAP NAS, PRTG will create one sensor for each disk
you choose. You can also define the unit of the temperature measurement. The settings you
QNAP NAS SETTINGS

Disk
table head.
Unit
Select the unit of the temperature measurement. Choose

between Celsius and Fahrenheit .
Sensor Settings
19.09.2014
1541


Sensor Name

Tags

Priority
(top priority).
QNAP NAS SETTINGS

Disk
Description
Model
Capacity

anew.
Unit
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1542
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1543

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1544
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1545


menu bar.
Dependency
dependent on.
Delay (Seconds)
1546
19.09.2014

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

Notifications
19.09.2014
1547

Others
1548
141
section.
19.09.2014

146 SNMP QNAP System Health Sensor
6.8.146 SNM P QNAP Sy stem Health Sensor

The SNMP QNAP System Health sensor monitors the system health of a QNAP Network
Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show the
usage of the CPU, available memory in absolute numbers and percent, the temperature of CPU
and system, as well as various other values, for example, revolutions of fans per minute,
depending on the available measurement components.
2491 section.
Add Sensor
In order to monitor the system health of a QNAP NAS, please specify the unit of the
temperature measurement.
QNAP NAS SETTINGS

Unit

Sensor Settings

Sensor Name
19.09.2014

1549


Tags

Priority
(top priority).
QNAP NAS SETTINGS

Unit
Shows the unit of temperatures as monitored with this sensor.

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1550
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1551

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1552
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1553


menu bar.
Dependency
dependent on.
Delay (Seconds)
1554
19.09.2014

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

Notifications
19.09.2014
1555

Others
1556
141
section.
19.09.2014

147 SNMP RMON Sensor
6.8.147 SNM P RM ON Sensor

The SNMP RMON sensor monitors traffic on a device using the Remote Monitoring (RMON)
standard via Simple Network Management Protocol (SNMP). You can create it on an SNMP
compatible device that provides traffic data via RMON. Depending on the data returned by your
device, traffic data for each port can be displayed in different channels, allowing detailed
analysis.
For example, available channels for each traffic port may include 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), Packets 128 - 255 Bytes (#/s), Packets 256 - 511 Bytes (#/s),
Packets 512 - 1023 Bytes (#/s), Packets 1024 - 1518 Bytes (#/s), and Drop Events (#/s).
Note: You can define the displayed sensor name with port name t emplat es in the SNMP
Compat ibilit y Opt ions 293 of the parent device.
2491 section.
Add Sensor
To monitor SNMP devices with multiple interfaces, PRTG creates one sensor for each port you
choose in the Add Sensor dialog. The settings you make in this dialog are valid for all of the
R MON SPECIFIC
Ports
Select the ports you want to add a sensor for. You see a list with
head.
Sensor Settings
26.09.2014
1557


Sensor Name

Tags

Priority
(top priority).
R MON SPECIFIC
Port
Shows the number of the interface port in your physical device

that this sensor is monitoring. Once a sensor is created, you
Channel Mask
This setting is shown for your information only and cannot be

changed here. It describes which channels are available and might
be useful for technical support.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1558
26.09.2014

SENSOR DISPLAY
2220 settings).
Stack Unit

Inherited Settings
described below.
26.09.2014
1559

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1560
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
1561


menu bar.
Dependency
dependent on.
Delay (Seconds)
1562
26.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
26.09.2014
1563

More
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?

Notifications
Others
1564
141
section.
26.09.2014

148 SNMP SonicWALL System Health Sensor
6.8.148 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). It shows
usage of CPU and memory, as well as usage of the connection cache.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
18.11.2014
1565

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1566
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1567


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1568
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1569

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1570
18.11.2014

More
Knowledge Base: Why does PRTG write error messages into my SonicWALL log?

Notifications
Others
18.11.2014
141
section.
1571

149 SNMP SonicWALL VPN Traffic Sensor
6.8.149 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
Simple Network Management Protocol (SNMP). It can show the number of encrypted and
decrypted packets, the number of bytes of encrypted and decrypted transmissions, as well as
the number of in- and outgoing fragmented packets.
2491 section.
Add Sensor
In order to monitor the traffic of a SonicWALL VPN, PRTG will create one sensor for each
connection you choose. The settings you make in this dialog are valid for all of the sensors
that are created.
SONICWALL VPN SPECIFIC

Connections
Select the connections you want to add a sensor for. You see a
table head.
Identification Method
Select the criteria PRTG will use to identify the connection. PRTG
will always use 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.
1572
18.11.2014

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SONICWALL VPN SPECIFIC

Security Policy
Remote IP
Shows further information about the monitored connection. Once

the sensor anew.
Index
Identification Method
SENSOR DISPLAY
Primary Channel
18.11.2014

1573

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit
1574

18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1575


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1576
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1577

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1578
18.11.2014

More
Knowledge Base: Why does PRTG write error messages into my SonicWALL log?

Notifications
Others
18.11.2014
141
section.
1579

150 SNMP Synology Logical Disk Sensor
6.8.150 SNM P Sy nology Logical Disk Sensor

The SNMP Synology Logical Disk sensor monitors a logical disk in a Synology Network
Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show the
status of a volume.
2491 section.
Add Sensor
In order to monitor the logical disks in a Synology NAS, PRTG will create one sensor for each
created.
SYNOLOGY NAS SETTINGS

Disk
head.
Sensor Settings

Sensor Name
1580

19.09.2014


Tags

Priority
(top priority).

Disk
Name

anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1581

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1582
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1583


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1584
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1585

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

Notifications
1586
19.09.2014

Others
19.09.2014
141
section.
1587

151 SNMP Synology Physical Disk Sensor
6.8.151 SNM P Sy nology Phy sical Disk Sensor

The SNMP Physical Disk sensor monitors a physical disk in a Synology Network Attached
Storage (NAS) via Simple Network Management Protocol (SNMP). It can show temperature and
disk status.
2491 section.
Add Sensor
In order to monitor the physical disks in a Synology NAS, PRTG will create one sensor for each
created.

Disk
table head.
Sensor Settings

Sensor Name
1588

19.09.2014


Tags

Priority
(top priority).

Disk
Name
Model

anew.
Type
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1589

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1590
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1591


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1592
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1593

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

Notifications
1594
19.09.2014

Others
19.09.2014
141
section.
1595

152 SNMP Synology System Health Sensor
6.8.152 SNM P Sy nology Sy stem Health Sensor

The SNMP Synology System Health sensor monitors the system health of a Synology Network
Attached Storage (NAS) via Simple Network Management Protocol (SNMP). It can show
temperature, system status, power status, fan status, as well as several other values,
depending on the available measurement components.
2491 section.
Add Sensor
In order to monitor the system health of a Synology NAS, please specify the unit of the
temperature measurement.

Unit

Sensor Settings

Sensor Name
1596

19.09.2014


Tags

Priority
(top priority).

Unit
Shows the unit of temperatures as monitored with this sensor.

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1597

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1598
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1599


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1600
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1601

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

Notifications
1602
19.09.2014

Others
19.09.2014
141
section.
1603

153 SNMP System Uptime Sensor
6.8.153 SNM P Sy stem Uptime Sensor

The SNMP System Uptime sensor monitors the time a device is running via Simple Network
Management Protocol (SNMP). It reads the device's value for system uptime and shows it.
2491 section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel
1604

19.09.2014

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1605

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1606
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1607


menu bar.
Dependency
dependent on.
Delay (Seconds)
1608
19.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: Why does the SNMP System Uptime sensor report wrong values?

19.09.2014
1609

Notifications
Others
1610
141
section.
19.09.2014

154 SNMP Traffic Sensor
6.8.154 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. It can show traffic in, traffic out, and traffic total. You can also add
additional channels.
Note: You can define the displayed sensor name with port name t emplat es in the SNMP
Compat ibilit y Opt ions 293 of the parent device.
2491 section.
Add Sensor
To monitor traffic on SNMP devices with multiple interfaces, PRTG creates one sensor for each
port you choose in the Add Sensor dialog. The settings you make in this dialog are valid for all
of the sensors that are created.
26.09.2014
1611

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 2220 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 2220 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 2220 later.
Sensor Settings

Sensor Name

Tags

1612
26.09.2014


Priority
26.09.2014
(top priority).
1613

TR AFFIC SPECIFIC
Interface Number
Shows the number and name of the interface in your physical

device that this sensor monitors. Once a sensor is created, you
Additional Channels
By default, the channels "Traffic In" and "Traffic Out" are created for
each sensor. Choose additional channels for all selected
interfaces. Please click on the respective channel name(s); a check
mark symbol will appear in front of them. 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. They can
be disabled 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.
Ignore all "disconnect ed" st at es: No alarm will be shown in
PRTG; the sensor status remains green and monitoring will be
discontinued without notice.
1614
26.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2220 settings).
Stack Unit

Inherited Settings
described below.
26.09.2014
1615

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1616
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
1617


menu bar.
Dependency
dependent on.
Delay (Seconds)
1618
26.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
26.09.2014
1619

More
Knowledge Base: How do PRTG's automatic port name and number updates work for SNMP
traffic sensors?

Notifications
Others
1620
141
section.
26.09.2014

155 SNMP Trap Receiver Sensor
6.8.155 SNM P Trap Receiver Sensor

The SNMP Trap Receiver sensor receives and analyzes Simple Network Management Protocol
(SNMP) traps. It shows the overall number of received traps per second, warning and error
traps per second, as well as the number of dropped packets per second.
With the available filter options, you can define individually which types of messages will be
considered for monitoring, and which messages will be recognized as warning or error
messages. Depending on the filters, received messages will be counted in the respective
channels.
You can add the sensor to the probe device on the one hand; then the sensor will receive all
messages of the system running the probe. Alternatively, you can add the sensor to a specific
device to gain all messages from this device directly; this will make this sensor type faster than
just using source filters.
You can use trap specific placeholders in email notification templates 2338 to see the messages
when you receive an email notification. See the More 1630 section below for more information.
Note: You can copy the Management Information Base (MIB) file for your traps into the \MIB
subfolder of your PRTG installation 2611 . PRTG will then be able to translate the OIDs for the
traps into readable messages. For example, instead of the Object Identifier (OID)
1.3.6.1.4.1.32446.1.1.2 you would see SNMPv2-SMI-v1::enterprises.32446.1.1.2 = 0 (example
from the PRTG MIB).
Note: If you do not add the sensor to a probe device but to another device in PRTG, be careful
with the configuration: Ensure that the IP address or DNS name of the parent device matches
the proper trap sender. For example, if you want to receive traps from a Storage Area Network
(SAN), you might have to add a device to PRTG using the IP address of a specific array member
that sends the messages. Providing a DNS name that points to the IP address of a whole group
might not work for SANs.
For a general introduction to the SNMP trap receiver's configuration, please see section
Monit oring Sy slogs and SNMP Traps 2526 .
2491 section.
Add Sensor
18.11.2014
1621

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SNMP TR AP SPECIFIC
Listen on Port
Enter the port the sensor will listen on for SNMP traps. Usually
port 162 is used. Please enter an integer value. We recommend
Purge Messages After
Define how long received trap messages will be stored for

analysis. Choose a period of time from the drop down list.
FILTER
Include Filter
1622
Define if you want to filter traps. If you leave this field empty or use
the keyword "any", all data will be processed. To include specific
types of traps only, define filters using a special syntax. For more
information, see section Filt er Rules 1629 .
18.11.2014

FILTER
Exclude Filter
Define which types of traps will be discarded and not processed.

To exclude specific types of traps, define filters using a special
syntax. For more information, see section Filt er Rules 1629 .
Warning Filter
Define which types of traps will count for the Warnings channel.
To categorize received traps as warning messages, define filters
using a special syntax. For more information, see section Filt er
Rules 1629 .
Note: Messages are collected until a scanning interval ends; as
long as the scanning interval is running, no status change will
happen. By default, the sensor will turn into a Warning status after
a scanning interval has finished and there was at least one warning
message (and no error message) during this interval. The status will
remain Warning at least until the succeeding scanning interval has
finished. If in this scanning interval no warning or error message
occurred, the status of the sensor will turn Up again after the
interval.
Error Filter
Define which types of traps will count for the Errors channel. To
categorize received traps as error messages, define filters using a
special syntax. For more information, see section Filt er Rules 1629 .
happen. By default, the sensor will turn into a Down status after a
scanning interval has finished and there was at least one error
message during this interval. The status will remain Down at least
until the succeeding scanning interval has finished. If in this
scanning interval no warning or error message occurred, the status
of the sensor will turn Up again after the interval.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
18.11.2014
1623

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1624
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1625


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1626
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1627

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1628
18.11.2014

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 2611 ) to the disk for debugging
purposes. Choose between:
Off (recommended): Do not write additional log files.
On: Write log files for all data received.
only.
Filter Rules for Traps

Filter rules are used for the include, exclude, warning, and error definition fields of the Trap
Receiver sensor. They are based on the following format:
field[filter]
You can use various filters suitable to your needs. Include and exclude filters define which
traps will be monitored; warning and error filters define how received traps will be categorized.
Provide these filters in the sensor settings as formulas. Formulas are fields which can be
combined with boolean operators (AND, OR, NOT) and brackets.
Field
Paramet er
Examples
source[ip]
Enter an IP address where the UDPs come from; IP

masks and ranges 2578 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]
18.11.2014
1629

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

Received traps are stored as common files in PRTG's data folder (see section Dat a St orage 2611
). In order to review and analyze all received messages, you can access the most recent data
directly in PRTG's web interface via the respective sensors on the Overview tab in a table list
155 . 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 2329 is 30 seconds).
For more details and further filter options, click on the Messages tab of the SNMP Trap
Receiver sensor. You will see all received messages in a table list 155 . On the top, you have
display filter options to drill down into the data for specific events of your interest. The filters
are the same as available in the sensor settings, but you can define them without using
formulas. Provide the desired parameters and PRTG will load the filtered list automatically. Note:
You can automatically add a filter by clicking on the content of a column.
Advanced Filt er Set t ings
You can open advanced filter settings with a click on the gear icon in the Filt er row. The
Advanced Filt er will appear in a popup window. In the text field, you can define a filter using
the syntax as given in section Filt er Rules for Traps 1629 . If you have provided filter parameters
on the Messages tab, these will be already included in the advanced filter as a corresponding
formula with the correct syntax. You can adjust this filter to your needs. You can also copy the
automatically created and manually adjusted formula for usage in the filter fields of the sensor
settings.
More
Blog Article: Introducing the New High Performance Syslog and SNMP Trap Receiver Sensors
http://www.paessler.com/blog/2013/10/11/prtg/introducing-the-new-high-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?
1630
18.11.2014


Notifications
Others
18.11.2014
141
section.
1631

156 SNMP Windows Service Sensor
6.8.156 SNM P Windows Service Sensor

The SNMP Windows Service sensor monitors a Windows service via Simple Network
Management Protocol (SNMP). It shows the operating status of the monitored service.
Operating states can be Active (sensor status Up), or Continue-Pending, Pause-Pending, and
Paused (all with sensor status Down).
Note: This sensor type cannot distinguish the status "not installed" from "not running".
2491 section.
Add Sensor
In order to monitor services on Windows, PRTG will create one sensor for each service you
select. The settings you make in this dialog are valid for all of the sensors that are created.
SNMP WINDOWS SER VICE MONITOR

Service
Select the services you want to add a sensor for. You see a list
head.
Sensor Settings
1632
19.09.2014


Sensor Name

Tags

Priority
(top priority).
SNMP WINDOWS SER VICE MONITOR

Service
Shows the service monitored by this sensor. Once a sensor is

anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1633

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1634
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1635


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1636
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1637

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

Notifications
Others
1638
141
section.
19.09.2014

157 SNTP Sensor
6.8.157 SNTP Sensor

The SNTP Sensor monitors a Simple Network Time Protocol (SNTP) server. It returns the
response time and the 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.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR SPECIFC
Timeout (Sec.)
26.09.2014
Enter a timeout in seconds. If the reply takes longer than this

value, the request is aborted and an error message is triggered.
The maximum timeout value is 900 seconds (equals 15 minutes).
1639

157 SNTP Sensor
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1640
26.09.2014

157 SNTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
1641

157 SNTP Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1642
26.09.2014

157 SNTP Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
1643

157 SNTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Notifications
Others
1644
141
section.
26.09.2014

158 SSH Disk Free Sensor
6.8.158 SSH Disk Free Sensor

The SSH Disk Free sensor monitors free space on disks of a Linux/Unix system using Secure
Shell (SSH). It shows the free disk space in total, and the free disk space in percent for every
mounted partition.
Note: The free space returned by this sensor type shows the available disk space of the
volume, minus a reserve defined for this volume (e.g. 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 article linked in the More 1655
section below.
2498
section.
Add Sensor
Sensor Settings

Sensor Name

Tags

19.09.2014
1645


Priority
(top priority).
SSH SPECIFIC
Connection Timeout
(Sec.)
keep this value as low as possible. The maximum value is 900
Shell Timeout (Sec.)
its specific command (e.g. cat /proc/loadavg). The maximum value
is 60 seconds (1 minute). Please enter an integer value.
SSH Port
Define which port this sensor uses for the SSH connection.
Choose between:
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.
Result Handling
between:
1646
19.09.2014


breached applies.
Upper Error Limit
the field empty.
Upper Warning Limit
the field empty.
19.09.2014
1647


Lower Warning Limit
the field empty.
Lower Error Limit
the field empty.
Size Limit Check
Choose between:
or overrun.
Upper Error Limit
empty.
1648
19.09.2014


Upper Warning Limit
field empty.
Lower Warning Limit
field empty.
Lower Error Limit
empty.
Alarm on Missing/
Removed Disk

19.09.2014
1649

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1650
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1651


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1652
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1653

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1654
19.09.2014

More
Knowledge Base: Why do SSH Disk Free and SNMP Linux Disk Free show different values for
my target Linux system?

Notifications
Others
19.09.2014
141
section.
1655

159 SSH INodes Free Sensor
6.8.159 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 the 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.
2498
section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1656
19.09.2014

SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
Result Handling
between:
SENSOR DISPLAY
Primary Channel
19.09.2014

1657

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1658
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1659


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1660
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1661

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1662
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1663

160 SSH Load Average Sensor
6.8.160 SSH Load Average Sensor

The SSH Load Average sensor monitors the load average of a Linux/Unix system using Secure
Shell (SSH). It shows the average system load within a one, five, and 15 minutes interval (each
in one channel).
2498
section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1664
19.09.2014

SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
Result Handling
between:
SENSOR DISPLAY
Primary Channel
19.09.2014

1665

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1666
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1667


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1668
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1669

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1670
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1671

161 SSH Meminfo Sensor
6.8.161 SSH M eminfo Sensor

The SSH Meminfo sensor monitors the memory usage of a Linux/Unix system using Secure
Shell (SSH). It shows the available memory in total and in percent.
Note: This sensor type is not compatible with Mac OS systems.
2498
section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1672
19.09.2014

SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
Result Handling
between:
SENSOR DISPLAY
Primary Channel
19.09.2014

1673

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1674
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1675


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1676
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1677

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1678
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1679

162 SSH Remote Ping Sensor
6.8.162 SSH Remote Ping Sensor

The SSH Remote Ping sensor remotely monitors the connectivity between a system running
Linux/OS X and an other device, using Internet Control Message Protocol (ICMP) echo
requests ("Ping") and Secure Shell (SSH). It can show packet loss, as well as minimum, maximum,
and average response times; all measured from the remote device you connect to.
2498
section.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1680
19.09.2014

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)
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
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
19.09.2014
value.
1681

SSH SPECIFIC
Result Handling
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1682
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1683


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1684
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1685

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

Notifications
1686
19.09.2014

Others
19.09.2014
141
section.
1687

163 SSH SAN Enclosure Sensor
6.8.163 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. This sensor
type can show the overall status of an enclosure and the health status of its power supplies
and controllers.
Note: This sensor type does not support every SAN, even if it provides a CLI. The sensor only
works with specific devices, for example, with the HP P2000.
Note: Sometimes the devices which you monitor with this sensor return status values which
are not officially documented so that the shown sensor status in PRTG differs from the "real"
device status. For more information regarding this issue, please see section More below.
For this sensor type, corresponding credentials must be defined in section Credent ials for
Linux/Solaris/Mac OS (SSH/WBEM) Sy st em in the settings of the device 284 you want to use
the sensor on.
2498
section.
Add Sensor
In order to monitor the status of SAN enclosures, PRTG will create one sensor for each
enclosure you choose. The settings you make in this dialog are valid for all of the sensors that
are created.
SSH SAN ENCLOSU R E SETTINGS

Enclosure
Select the enclosures you want to add a sensor for. You see a list
head.
Sensor Settings
1688
19.09.2014


Sensor Name

Tags

Priority
(top priority).
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
sensor monitors. Once a sensor is created, you cannot change this
19.09.2014
1689

SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
Result Handling
between:
SENSOR DISPLAY
Primary Channel
1690

19.09.2014

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1691

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1692
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1693


menu bar.
Dependency
dependent on.
Delay (Seconds)
1694
19.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: Why does my SSH SAN sensor show a wrong status?

Notifications
19.09.2014
1695

Others
1696
141
section.
19.09.2014

164 SSH SAN Logical Disk Sensor
6.8.164 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. The
sensor can show the health status of the disk.
the sensor on.
2498
section.
Add Sensor
In order to monitor volumes on an SAN device, PRTG will create one sensor for each volume
created.
SSH SAN LOGICAL DISK SETTINGS

Volume
Select the volumes you want to add a sensor for. You see a list
head.
Sensor Settings
19.09.2014
1697


Sensor Name

Tags

Priority
(top priority).
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
1698
value.
19.09.2014

SSH SPECIFIC
Result Handling
between:
SSH SAN LOGICAL DISK SETTINGS

Volume
Shows the volume that this sensor monitors. Once a sensor is

anew.
Size
Shows the size of the volume that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1699

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1700
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1701


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1702
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1703

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1704
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1705

165 SSH SAN Physical Disk Sensor
6.8.165 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.
The sensor can show the health status of the disk, the total number of I/O operations, as well
as the amount of transferred data.
the sensor on.
2498
section.
Add Sensor
In order to monitor disks on an SAN device, PRTG will create one sensor for each disk you
SSH SAN PHYSICAL DISK SETTINGS

Disk
head.
Sensor Settings
1706
19.09.2014


Sensor Name

Tags

Priority
(top priority).
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
19.09.2014
value.
1707

SSH SPECIFIC
Result Handling
between:
SSH SAN PHYSICAL DISK SETTINGS

Disk
Shows the disk that this sensor monitors. Once a sensor is

anew.
Disk Name
Shows the label of disk that this sensor monitors. Once a sensor is
anew.
Size
Shows the size of the disk that this sensor monitors. Once a
the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1708
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1709

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1710
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1711


menu bar.
Dependency
dependent on.
Delay (Seconds)
1712
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1713

More

Notifications
Others
1714
141
section.
19.09.2014

166 SSH SAN System Health Sensor
6.8.166 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 the SAN, such as temperatures, voltages, the
overall unit status, as well as capacitor charge. Which monitoring data this sensor type can
show depends on the available measurement components on the SAN.
the sensor on.
2498
section.
Add Sensor
In order to monitor the system health of an SAN device, PRTG will create one sensor for each
metric you choose. The settings you make in this dialog are valid for all of the sensors that are
created.
SSH SAN SPECIFIC

Metric
19.09.2014
Select the metrics you want to add a sensor for. You see a list with
head.
1715

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SSH SAN SPECIFIC

Metric
Shows the metric this sensor monitors. Once a sensor is created,

SSH SPECIFIC
Connection Timeout
(Sec.)
1716
19.09.2014

SSH SPECIFIC
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
Result Handling
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1717

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1718
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1719


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1720
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1721

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1722
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1723

167 SSH Script Sensor
6.8.167 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. The sensor shows the execution time, and can show
one value returned by the executable file or script (in one channel only). For details about the
return value format please see the Applicat ion Programming Int erface (API) Definit ion 2571 .
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)".
type of sensor.
2498
section.
Add Sensor
1724
18.11.2014

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,
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 use the right
format for the returned values (in this case,
exitcode:value:message to stdout). The exitcode will determine
the sensor status. 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 2571 ). There, find detailed information the the "Custom
Sensors" tab. For an example script, please see More 1733 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.
a buffer overflow.
Count er: Your script returns an integer which increases. PRTG
will show the difference between the values of two sensor
scans. Note: A counter must return an integer; float is not
supported here!
Sensor Settings

Sensor Name
18.11.2014

1725


Tags

Priority
(top 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 2571 ). 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.
Mutex Name
Value Type
Shows the expected value type, chosen on sensor creation. Once

the sensor anew. Note: The sensor cannot handle string values.
If Value Changes

1726
18.11.2014

SENSOR SETTINGS
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
Result Handling
between:
18.11.2014
1727

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1728
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1729


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1730
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1731

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1732
18.11.2014

More
Knowledge Base: Is there a shell script example for PRTG's SSH Script Sensor?
2571
2217

Notifications
Others
18.11.2014
141
section.
1733

168 SSH Script Advanced Sensor
6.8.168 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. The sensor can show values returned by
the script in multiple channels. The return value of this sensor must be valid XML. For details
about the return value format please see the Applicat ion Programming Int erface (API)
Definit ion 2571 .
Note: For security reasons, the script file must be stored on the target system. Please make
sure the script has executable rights.
type of sensor.
2498
section.

Add Sensor
1734
19.09.2014

SENSOR SETTINGS
Script
Select a script file from the list. The drop down menu will list all
script files available in the /var/prtg/scriptsxml directory on the
target Linux/Unix system. In order for the files to appear in this list,
please store them into this directory. Please make sure the script
has executable rights. In order for the sensor to show the
expected values and sensor status, your files must return the
expected XML format to standard output. Values and message
must be embedded in the XML. For detailed information on the
expected return format and on how to build custom sensors,
please see the API documentation (Applicat ion Programming
Int erface (API) Definit ion 2571 ). There, find detailed information the
the "Custom Sensors" tab.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
1735

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 2571 ). 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.
Mutex Name
EXE Result
Define what will be done with the results the executable file gives
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
SSH SPECIFIC
Connection Timeout
(Sec.)
1736
19.09.2014

SSH SPECIFIC
SSH Port
Choose between:
created on.
below.
Use Port Number
value.
Result Handling
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
1737

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1738
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1739


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1740
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1741

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1742
19.09.2014

More
2571
2217

Notifications
Others
19.09.2014
141
section.
1743

169 SSH VMWare ESX(i) Disk Sensor
6.8.169 SSH VM Ware ESX(i) Disk Sensor

The SSH VMWare ESX(i) Disk sensor monitors free space on disks of a VMware ESX(i) system
using Secure Shell (SSH). It shows the free disk space in total and percent.
2498
section.
Requirement: Root Credentials

In the parent device's Credent ials for Linux/Solaris/Mac OS (SSH/WBEM) Sy st ems settings,
please use the root user of your VMware host for authentication! See More 1752 section below.
Please make sure you enable SSH on your VMware system!
Add Sensor
In order to monitor the free space of a disk on a ESX(i) system, PRTG creates one sensor for
each disk you select. The settings you make in this dialog are valid for all of the sensors that
are created.
ESX(I) DISK SPECIFIC

Disk
head.
Sensor Settings
1744
19.09.2014


Sensor Name

Tags

Priority
(top priority).
ESX(I) DISK SPECIFIC

Disk
Shows the name of the disk that this sensor monitors. Once a
the sensor anew.
SSH SPECIFIC
Connection Timeout
(Sec.)
SSH Port
Choose between:
created on.
19.09.2014
1745

SSH SPECIFIC
below.
Use Port Number
value.
Result Handling
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
1746

19.09.2014

Inherited Settings
described below.
19.09.2014
1747

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1748
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1749


menu bar.
Dependency
dependent on.
Delay (Seconds)
1750
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1751

More
Knowledge Base: Settings on ESXi 5 host when monitoring via SSH VMware ESX(i) Disk Sensor
Knowledge Base: Why do I need root credentials when monitoring VMware hosts via SSH?

Notifications
Others
1752
141
section.
19.09.2014

170 SSL Security Check Sensor
6.8.170 SSL Security Check Sensor

The SSL Security Check sensor monitors the Secure Sockets Layer (SSL) connectivity to the
port of a device. It tries connecting to the specified TCP/IP port number of a device with
various SSL/TLS protocol versions and shows if a particular protocol is supported.
The sensor checks connectivity with the following protocols in particular channels 86 with the
possible values Accept ed (sensor can connect with this protocol) or Denied (sensor cannot
connect with this protocol):
SSL 2.0: weak security (warning if accepted, up if denied)
SSL 3.0: weak security (warning if accepted, up if denied)
TLS 1.0: strong security (up if accepted, otherwise gray)
TLS 1.1: strong security (up if accepted, otherwise gray)
TLS 1.2: perfect security (up if accepted, otherwise gray)
The default primary channel Securit y Rat ing shows the connection security to the defined
port with one of the following states 121 :
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.
Add Sensor
Settings
18.11.2014
1753


Sensor Name

Tags

Priority
(top priority).
SSL SPECIFIC
Timeout (Sec.)
longer than this value defines, PRTG aborts the request and shows
a corresponding error message. The maximum value is 900
Port

Please enter an integer value. The default port is 443.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1754
18.11.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
18.11.2014
1755

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1756
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1757


menu bar.
Dependency
dependent on.
Delay (Seconds)
1758
18.11.2014

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

Notifications
Others
18.11.2014
141
section.
1759

171 Syslog Receiver Sensor
6.8.171 Sy slog Receiver Sensor

The Syslog Receiver sensor receives and analyzes syslog messages. It shows the overall
number of received syslog messages per second, warning and error messages per second, as
well as the number of dropped packets per second.
With the available filter options, you can define individually which types of messages will be
considered for monitoring and thus stored, and which messages will be recognized as warning
or error messages. Depending on the filters, received messages will be counted in the
respective channels. The messages are stored in an internal database for later analysis. The
received data will be available on your respective probe system as common files, as well as via
the web interface.
You can add the sensor to the probe device on the one hand; then the sensor will receive all
messages of the system running the probe. Alternatively, you can add the sensor to a specific
device to gain all messages from this device directly; this will make this sensor type faster than
just using source filters.
You can use syslog specific placeholders in email notification templates 2338 to see the
messages when you receive an email notification. See the More 1770 section below for more
information about placeholders.
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 section
Monit oring Sy slogs and SNMP Traps 2526 .
Add Sensor
Sensor Settings
1760
19.09.2014


Sensor Name

Tags

Priority
(top priority).
SYSLOG SPECIFIC
Listen on Port
Enter the port the sensor will listen on for Syslog messages.
Usually port 514 is used. Please enter an integer value. We
Purge Messages After
Define how long received syslog messages will be stored for

analysis. Choose a period of time from the drop down list.
FILTER
Include Filter
Define if you want to filter syslog messages. If you leave this field
empty or use the keyword "any", all data will be processed. To
include specific types of messages only, define filters using a
special syntax. For more information, see section Filt er Rules 1768 .
Exclude Filter
Define which types of syslog messages will be discarded and not

processed. To exclude specific types of messages, define filters
using a special syntax. For more information, see section Filt er
Rules 1768 .
19.09.2014
1761

FILTER
Warning Filter
Define which types of syslog messages will count for the Warnings
channel. To categorize received messages as warning messages,
define filters using a special syntax. For more information, see
section Filt er Rules 1768 .
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 1768 .
happen. By default, the sensor will turn into a Down status after a
scanning interval has finished and there was at least one error
message during this interval. The status will remain Down at least
until the succeeding scanning interval has finished. If in this
scanning interval no warning or error message occurred, the status
of the sensor will turn Up again after the interval.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1762
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1763

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1764
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1765


menu bar.
Dependency
dependent on.
Delay (Seconds)
1766
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1767

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 2611 ) to the disk for debugging
purposes. Choose between:
Off (recommended): Do not write additional log files.
On: Write log files for all data received.
only.
Filter Rules for Syslog Messages

Filter rules are used for the include, exclude, warning, and error definition fields of the Syslog
Receiver sensor. They are based on the following format:
field[filter]
You can use various filters suitable to your needs. Include and exclude filters define which
messages will be monitored; warning and error filters define how received messages will be
categorized. Provide these filters in the sensor settings as formulas. Formulas are fields which
can be combined with boolean operators (AND, OR, NOT) and brackets.
Field
Paramet er
Example
source[ip]
the IP address where the messages will be

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]
1768
19.09.2014

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

Received syslog messages are stored as common files in PRTG's data folder (see section Dat a
St orage 2611 ). In order to review and analyze all received messages, you can access the most
recent data directly in PRTG's web interface via the Overview tab of the respective sensor in a
table list 155 . 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 2329 is 30
seconds).
For more details and further filter options, click on the Messages tab of the Syslog Receiver
sensor. You will see all received messages in a table list 155 . On the top, you have display filter
options to drill down into the data for specific events of your interest. The filters are the same
as available in the sensor settings, but you can define them without using formulas. Provide
the desired parameters and PRTG will load the filtered list automatically. Note: You can
automatically add a filter by clicking on the content of a column.
19.09.2014
1769

Advanced Filt er Set t ings

You can open advanced filter settings with a click on the gear icon in the Filt er row. The
Advanced Filt er will appear in a popup window. In the text field, you can define a filter using
the syntax as given in section Filt er Rules for Sy slog Messages 1768 . If you have provided filter
parameters on the Messages tab, these will be already included in the advanced filter as a
corresponding formula with the correct syntax. You can adjust this filter to your needs. You
can also copy the automatically created and manually adjusted formula for usage in the filter
fields of the sensor settings.
More

Notifications
Others
1770
141
section.
19.09.2014

172 System Health Sensor
6.8.172 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%.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
26.09.2014
1771

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1772
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
1773

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1774
26.09.2014


Notifications
Others
26.09.2014
141
section.
1775

173 TFTP Sensor
6.8.173 TFTP Sensor

The TFTP sensor monitors a Trivial File Transfer Protocol (TFTP) server and checks if a certain file
is available for download. It shows the availability.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR SPECIFIC
Timeout (Sec.)
Enter a timeout in seconds for the TFTP connection. If the reply

takes longer than this value the request is aborted and an error
Port
Enter the number of the port the TFTP service is running on. The
sensor connects to this port. Please enter an integer value.
1776
19.09.2014

173 TFTP Sensor
SENSOR SPECIFIC
Filename
Enter the name of the file that this sensor checks. If this filename is
not available on the server, the sensor switches to a 'down' status.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1777

173 TFTP Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1778
19.09.2014

173 TFTP Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1779

173 TFTP Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
1780
19.09.2014

173 TFTP Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1781

173 TFTP Sensor

Notifications
Others
1782
141
section.
19.09.2014

174 Traceroute Hop Count Sensor
6.8.174 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.
It returns the number of hops. In case this number changes, you can additionally change the
sensor's status.
type of sensor.

Add Sensor
Sensor Settings

Sensor Name

Tags

18.11.2014
1783


Priority
(top priority).
SENSOR SETTINGS
If Route Changes
Define what will be done in case 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 error status.
DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type
1784
18.11.2014

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
1785

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1786
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1787


menu bar.
Dependency
dependent on.
Delay (Seconds)
1788
18.11.2014

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

Notifications
Others
18.11.2014
141
section.
1789

175 Virtuozzo Container Disk Sensor
6.8.175 Virtuozzo Container Disk Sensor

server. This sensor must be created on a Windows server parent device running Virtuozzo.
For each container, it can show free disk space in percent, used disk space (kb-blocks),
allowed quota (kb-blocks), and hard limit (kb-blocks).
Add Sensor
CONTAINER SETTINGS
Container
Select all containers for which you want to create a sensor for disk
monitoring. You see a list with the names of all items which are
available to monitor. Select the desired items by adding check
Sensor Settings

Sensor Name

Tags

1790
19.09.2014


Priority
(top priority).
CONTAINER SETTINGS
Env ID
Shows the unique ID of the container. Once a sensor is created,

Name
Shows the name of the monitored container. Once a sensor is

anew.
OS
Shows the operating system running on the container. Once a

the sensor anew.
Description
Shows a description for the container. Once a sensor is created,

Powered Off
Containers
Define if the sensor will go into an error state if the container is

powered off.
Alarm when powered off: Set the sensor for a container to
error if the container is powered off.
Ignore powered off st at e: Only show zero values for a sensor
when the monitored container is powered off. Do not set the
sensor to error.
SENSOR DISPLAY
Primary Channel
19.09.2014

1791

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1792
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1793


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1794
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1795

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

Notifications
Others
1796
141
section.
19.09.2014

176 Virtuozzo Container Network Sensor
6.8.176 Virtuozzo Container Network Sensor

The Virtuozzo Container Network sensor monitors the network traffic of a container on a
device running Virtuozzo. For each container, it can show network usage as incoming and
outgoing bytes as well as its sum, and the number of incoming and outgoing packets.
Add Sensor
CONTAINER SETTINGS
Container
Select all containers for which you want to create a sensor. You
table head.
Sensor Settings

Sensor Name

Tags

19.09.2014
1797


Priority
(top priority).
CONTAINER SETTINGS
Env ID
Shows the unique ID of the container. Once a sensor is created,

Name
Shows the name of the monitored container. Once a sensor is

anew.
OS
Shows the operating system running on the container. Once a

the sensor anew.
Description
Shows a description for the container. Once a sensor is created,

Powered Off
Containers
Define if the sensor will go into an error state if the container is

powered off.
Alarm when powered off: Set the sensor for a container to
error if the container is powered off.
Ignore powered off st at e: Only show zero values for a sensor
when the monitored container is powered off. Do not set the
sensor to error.
SENSOR DISPLAY
Primary Channel
1798

19.09.2014

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

SCANNING INTER VAL

Interval
The scanning interval of this sensor type cannot be inherited or

changed. Due to internal restrictions of the Virtuozzo system, a fix
value must be used.
Inherited Settings
described below.

settings.
19.09.2014
1799


Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1800
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1801

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

Notifications
Others
1802
141
section.
19.09.2014

177 VMware Host Hardware (WBEM) Sensor
6.8.177 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 shows the current reading and health status.
Note: The parent device must be a VMware ESX/ESXi server version 3.5, 4.0, 5.0, 5.1, or 5.5.
type of sensor.
Add Sensor
In order to monitor ESX servers, PRTG will create one sensor for each hardware element you
ESX SER VER ELEMENTS

ESX Element
Select the hardware elements you want to add a sensor for. You
table head.
Sensor Settings

Sensor Name
19.09.2014

1803


Tags

Priority
(top priority).
ESX SER VER ELEMENTS

Element
Shows the ESX element monitored by this sensor. Once a sensor

anew.
Automatic Sensor
State
Define if the sensor will change it's 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:
1804
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1805

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1806
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1807


menu bar.
Dependency
dependent on.
Delay (Seconds)
1808
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
1809

178 VMware Host Hardware Status (SOAP) Sensor
6.8.178 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" states, just as shown in the vSphere client. 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.
For this sensor type credentials for VMware servers must be defined for the device you want
to use the sensor on. Please make sure you enter a user with sufficient access rights to obtain
statistics (read-only should work).
Note: This sensor only shows items that report an actual state; therefore you might see more
"sensors" in your vSphere client than the number of states available in the channels of this
PRTG sensor.
We recommend to not use this sensor type on your vCenter. Reliable hardware information
can only be provided when this sensor is created on your physical host server as parent
device.
Note: If you use this sensor on a probe that runs on Windows Server 2003 (including SP1 and
SP2) and the target system is VMware ESXi 5.1 or later, you might receive the error message
"The underlying connection was closed: An unexpected error occurred on a send." For details,
please see section More below. Please note that PRTG does not officially support Windows
Server 2003!
type of sensor.

Settings on VMware Host System

If you set up this sensor on different probes (for example, when using remote probes 2589 or
when running a cluster 81 setup), you might need to change the settings of your VMware
host, so it accepts more incoming connections. Otherwise you might get connection timeouts
when running plenty of VMware sensors with a short scanning interval.
For details about this setting, please see More section below.
1810
26.09.2014

Add Sensor
VMWAR E HOST SETTINGS

Host Server
Select the host server you want to add a sensor for. You see a list
head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
26.09.2014
1811


MoID
The Managed Object ID (MoID) of the host. Once a sensor is

anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1812
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
1813


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1814
26.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
1815

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
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
1816
26.09.2014


Notifications
Others
26.09.2014
141
section.
1817

179 VMware Host Performance (SOAP) Sensor
6.8.179 VM ware Host Performance (SOAP) Sensor

The VMware Host Performance (SOAP) sensor monitors a VMware host server using Simple
Object Access Protocol (SOAP). It shows CPU (percent), network, disk, and memory (absolute)
usage, disk read and write speed, disk and data store latency, and network received and
transmitted speed of a VMware host server.
statics (read-only should work).
Server 2003!
type of sensor.


Add Sensor
1818
26.09.2014

Sensor Settings

Sensor Name

Tags

Priority
(top priority).

MoID
Shows the Managed Object ID (MoID) of the host. Once a sensor is

anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
26.09.2014
1819

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
1820
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
1821


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1822
26.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
1823

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
2003
1824
26.09.2014


Notifications
Others
26.09.2014
141
section.
1825

180 VMware Virtual Machine (SOAP) Sensor
6.8.180 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). It shows CPU (percent) and memory
(absolute) usage, disk read and write speed, read and write latency, and network usage (total,
received, and transmitted) of a single virtual machine.
statics (read-only should work).
Note: For VMware virtual machines, disk usage channels are only available as of virtual
hardware version 8.
Note: The parent device must be a VMware ESX/ESXi server version 3.5, 4.0, 5.0, 5.1, or 5.5; or
a respective Virtual Center server. We recommend using Virtual Center as parent device,
because this way PRTG will continue to monitor your virtual machines also when they change
the physical host using vMotion.
Server 2003!
type of sensor.


1826
26.09.2014

Add Sensor
Note: PRTG requests a full list of all virtual machines configured on the device. Therefore, it may
take a few seconds before the dialog is loaded.
In order to monitor VMware virtual machines, PRTG will create one sensor for each virtual
machine you choose. The settings you make in this dialog are valid for all of the sensors that
are created.

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

Tags

26.09.2014
1827


Priority
(top priority).

MoID
Shows the Managed Object ID (MoID) of the virtual machine. Once

the sensor anew.
Handling of "Powered
off" VM
Choose how the sensor will react to a virtual machine that is

powered off. Please choose between:
Ignore "powered off" st at e (default ): The sensor will not
change to a Down status 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 121 status if the virtual machine is powered off. Note: While
in Down status, a sensor does not record any data in all of its
channels.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1828
26.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
26.09.2014
1829

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1830
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
1831


menu bar.
Dependency
dependent on.
Delay (Seconds)
1832
26.09.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
2003
26.09.2014
1833


Notifications
Others
1834
141
section.
26.09.2014

181 WBEM Custom Sensor
6.8.181 WBEM Custom Sensor

The WBEM Custom Sensor performs a custom query via Web-Based Enterprise Management
(WBEM) and shows the retrieved parameters.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
CU STOM QU ER Y SPECIFIC
Namespace
19.09.2014
Enter the namespace for the query. Default value is root /cimv2.
1835

WBEM Query (WQL)
Enter the WBEM query that this sensor performs with every
scanning interval. It has to be written in WQL (WBEM Query
Language) or CQL (CIM Query Language). For example, a query can
look like this:
SELECT * FROM Linux_UnixProcess WHERE ModulePath = "/sbin/
portmap"
Numeric Format
Define the expected type of the returned values. Choose

between:
Int eger: The query returns integer values.
Float : The query returns float values.
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1836
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1837

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1838
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1839


menu bar.
Dependency
dependent on.
Delay (Seconds)
1840
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1841

More
For more tips and tricks regarding WQL scripts, please see the Paessler Knowledge Base and
search for WQL.
http://kb.paessler.com/en/tags/wql/

Notifications
Others
1842
141
section.
19.09.2014

182 Windows CPU Load Sensor
6.8.182 Windows CPU Load Sensor

The Windows CPU Load sensor monitors the CPU load on a computer via Windows
"Windows Compatibility Options" of the parent device. It shows the CPU usage of all
processors and the total load in percent.
section.
2495


remote probe 2589 .

work.
Automatic.
19.09.2014
1843

Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
WMI ALTER NATIVE QU ER Y

Errors and Invalid Data
This is an extended help field only. PRTG's WMI sensors are

equipped with the most efficient and accurate WMI queries.
However, Microsoft has changed (and will continue to do that in
the future) some WMI classes over the various Windows/
ServicePack/patchlevel versions, resulting in errors like "class not
valid" or "invalid data". Wherever possible, PRTG features an
alternative query that might work in your specific configuration.
When you keep getting errors for this sensor, please try enabling
the alternative query method below.
Alternative Query
Choose the method PRTG uses to query via WMI. For compatibility
reasons, you can enable an alternative query method. We
recommend using the default value. You can choose between:
1844
19.09.2014


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

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1845

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1846
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1847


menu bar.
Dependency
dependent on.
Delay (Seconds)
1848
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1849

More
Knowledge Base: My Windows sensors do not work when using direct Performance Counter
access. What can I do?

Notifications
Others
1850
141
section.
19.09.2014

183 Windows IIS 6.0 SMTP Received Sensor
6.8.183 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 of messages,
the bytes, and the number of retries per second for received messages.
Note: 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.
2495


remote probe 2589 .

work.
19.09.2014
1851

Automatic.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
DEBU G OPTIONS
Sensor Result
between:
1852
19.09.2014

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1853

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1854
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1855


menu bar.
Dependency
dependent on.
Delay (Seconds)
1856
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1857

More

Notifications
Others
1858
141
section.
19.09.2014

184 Windows IIS 6.0 SMTP Sent Sensor
6.8.184 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. It shows the number of messages,
the bytes, and the number of retries per second for sent messages.
Note: 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.
2495


remote probe 2589 .

work.
19.09.2014
1859

Automatic.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
DEBU G OPTIONS
Sensor Result
between:
1860
19.09.2014

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1861

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1862
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1863


menu bar.
Dependency
dependent on.
Delay (Seconds)
1864
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
1865

More

Notifications
Others
1866
141
section.
19.09.2014

185 Windows IIS Application Sensor
6.8.185 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).
The sensor shows bytes sent and received as well as the number of post, get, and CGI
requests, not found errors, anonymous and known users, and received and sent files per
second.
section.
2495


remote probe 2589 .

work.
19.09.2014
1867

Automatic.
Add Sensor
If you select more than one web service instance, PRTG will create one sensor for each
instance you select. The settings you make in this dialog are valid for all of the sensors that
are created.
WMI INTER NET INFOR MATION SER VICES

Specify Instance
in the table head.
Sensor Settings

Sensor Name

Tags

1868
19.09.2014


Priority
(top priority).
WMI INTER NET INFOR MATION SER VICES

Instance
Shows the name of the web service instance that this sensor
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
19.09.2014

1869

Inherited Settings
described below.
1870
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1871


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1872
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1873

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1874
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1875

186 Windows Last Update (Remote Registry) Sensor
6.8.186 Windows Last Update (Remote Registry ) Sensor

The Windows Last Update sensor uses the Windows Remote Registry service to read the
number of days since the last Windows update from its parent device. It shows the elapsed
time since the last update. Use threshold triggers 2227 to get notified if this number breaches a
certain value.
type of sensor.



In order for this sensor to work, you need to enable the RemoteRegistry "Remote Registry"
Windows service on the target machine. To do so, please log in to this machine and open the
services manager (for example, start services.msc). In the list of services, find the Remot e
Regist ry service and set its Start Type to Automatic. For details, see section More 1882 .
Add Sensor
1876
26.09.2014

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
If Value Changes
change.
DEBU G OPTIONS
Sensor Result
between:
26.09.2014
1877

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1878
26.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
26.09.2014
1879


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1880
26.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
26.09.2014
1881

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: How do I enable the Remote Registry Service on a Windows PC?
Knowledge Base: Fixing a Protocol Error Appearing With Windows Last Update Sensor

1882
26.09.2014

Notifications
Others
26.09.2014
141
section.
1883

187 Windows Logged In Users Sensor
6.8.187 Windows Logged In Users Sensor

The Windows Logged In Users sensor queries the number of users logged in to a Windows
installation on the parent device. It returns the total number and can show the names of all
logged in users. You can optionally filter for certain user names.
type of sensor.


Add Sensor
Sensor Settings
1884
19.09.2014


Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
User Filter (optional)
To filter the value returned by certain user names, define them

here. Enter a comma separated list of user names, or leave the field
empty.
Processing of Users in
"User Filter"
Define how the user names entered above will be used. Choose
between:
Do not count users list ed in "User Filt er": Exclude the users
entered above from counting and only count other users.
Only count users list ed in "User Filt er": Ignore all other users
and only count user names from the list entered above.
Show Usernames in
the Sensor Message
Define if the sensor shows the names of logged in users in its last
message. Choose between:
Yes, show list of logged in usernames: The sensor message
shows the names of all logged in users.
No, only show t he amount of logged in users: The sensor
message shows the number of logged in users.
If Value Changes
change.
19.09.2014
1885

SENSOR SETTINGS
DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1886
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1887

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1888
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1889


menu bar.
Dependency
dependent on.
Delay (Seconds)
1890
19.09.2014

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

Notifications
Others
19.09.2014
141
section.
1891

188 Windows MSMQ Queue Length Sensor
6.8.188 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. It shows the total number of messages in the queue.
type of 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 2589 .
Additionally, the MSMQ "Message Queuing" service must also be started on the target
computer.
Automatic.
Depending on your Windows version you may first need to install the Microsoft Message
Queue (MSMQ) Server.
1892
18.11.2014

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
1899
section below.
Add Sensor
To In order to monitor message queues, PRTG creates one sensor for each queue you select.
The settings you make in this dialog are valid for all of the sensors that are created.
SENSOR SETTINGS
Message Queue
in the table head. If there are no message queues available, you will
see a corresponding message.
Note: Sub-queues are not supported by this sensor.
Sensor Settings

Sensor Name
18.11.2014

1893


Tags

Priority
(top 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 will not be
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.
1894
18.11.2014

DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
1895

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1896
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1897


menu bar.
Dependency
dependent on.
Delay (Seconds)
1898
18.11.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: How do I activate Message Queuing in my Windows installation?

Notifications
18.11.2014
1899

Others
1900
141
section.
18.11.2014

189 Windows Network Card Sensor
6.8.189 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. It shows the
total traffic on the network card, traffic in and traffic out, as well as the number of packets per
second. This sensor type supports also teamed network adapters ("NIC teaming") on Windows
Server 2012.
section.
2495


remote probe 2589 .

work.
Automatic.
26.09.2014
1901

Add Sensor
For devices with multiple network cards, PRTG creates one sensor for each interface you
Network Interface
Select the network card(s) you want to add a sensor for. You see a
table head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1902
26.09.2014

SENSOR SPECIFIC
Selected Interface
Shows the name of the network card that this sensor monitors.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2220 settings).
Stack Unit

Inherited Settings
described below.
26.09.2014
1903

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1904
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
1905


menu bar.
Dependency
dependent on.
Delay (Seconds)
1906
26.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
26.09.2014
1907

More

Notifications
Others
1908
141
section.
26.09.2014

190 Windows Pagefile Sensor
6.8.190 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 usage in percent.
Note: This sensor does not work with Windows 2000, because the respective WMI class does
not exist on this operating system!
section.
2495


remote probe 2589 .

work.
19.09.2014
1909

Automatic.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type
1910
19.09.2014

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
1911

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1912
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1913


menu bar.
Dependency
dependent on.
Delay (Seconds)
1914
19.09.2014

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

Notifications
19.09.2014
1915

Others
1916
141
section.
19.09.2014

191 Windows Physical Disk Sensor
6.8.191 Windows Phy sical Disk Sensor

The Windows Physical Disk sensor monitors parameters of a physical disk of a Windows device
using Windows Performance Counters or Windows Management Instrumentation (WMI), as
configured in the "Windows Compatibility Options" of the parent device. It shows accumulated
disk read/write time and bytes, queue, split IO, etc. on physical disks.
section.
2495


remote probe 2589 .

work.
Automatic.
19.09.2014
1917

Add Sensor
WINDOWS PHYSICAL DISK SPECIFIC

Physical Disks
You see a list showing the Name of the counters you can monitor
as well as the Inst ance, i.e. the respective logical disk (or '_Total').
If there are no logical disks available, you will see a corresponding
message. From the list, choose all Name/Inst ance combinations
you want to monitor by adding a check mark in front of the
respective line (for example, choose '% Disk Read Time for C:').
in the table head.
Sensor Settings

Sensor Name

Tags

1918
19.09.2014


Priority
(top 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
Define what will be done with the result of the sensor. Choose
between:
[ID].t xt "): Store the last result received to the "Logs (System)"
SENSOR DISPLAY
Primary Channel
19.09.2014

1919

SENSOR DISPLAY
Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1920
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1921


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1922
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1923

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
1924
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
1925

192 Windows Print Queue Sensor
6.8.192 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. Additionally, this sensor can change to a defined status if there is a printer problem
such as out of paper, low toner, etc.
Note: You can add a 'change' trigger
jobs in the queue changes.
2338
to this sensor to get a notification when the number of
type of sensor.


Requirement: Print Spooler Service

In order for this sensor to work, the Spooler "Print Spooler" service must be started on the
target computer.
Automatic.
1926
18.11.2014

Add Sensor
In order to monitor print queues, PRTG will add a sensor for each task you choose. The
SENSOR SETTINGS
Print Queue
in the table head. If there are no print queues available, you will 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

Tags

Priority
(top priority).
18.11.2014
1927

SENSOR SETTINGS
Print Queue
Shows the name of the task monitored by this sensor. Once a

the sensor anew.
Advanced Status
Option
You can optionally define specific Sensor St at es 121 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 are reported by the monitored
printer.
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 will attain. Choose
between:
Needs User
Intervention
Ignore: The sensor will remain in the current status if this

message is reported by the printer.
Offline
Warning: The sensor will switch into the Warning status if this
message is reported by the printer.
Out of Memory
Error: The sensor will turn into 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
Min. Print Job Age
(Sec.)
1928
Optionally define the age of the print job in seconds. If set, jobs
younger than this value will not be 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.
18.11.2014

DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
1929

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1930
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1931


menu bar.
Dependency
dependent on.
Delay (Seconds)
1932
18.11.2014

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

Notifications
18.11.2014
1933

Others
1934
141
section.
18.11.2014

193 Windows Process Sensor
6.8.193 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 absolute working set, private bytes,
the number of threads, handles, and instances, as well as the average CPU usage (if there are
multiple instances running) and the total CPU usage of the process.
For the "total CPU usage" value of a process, all CPU usage values are summed up. The total is
divided by the number of all CPUs; the maximum value is 100%. This corresponds to the CPU
usage of all instances of this specific process. Regarding the "per instance" value, the summed
up CPU usage value is divided by the number of all instances. It shows the average CPU usage
of a single instance of the process on one CPU.
Note: This sensor type does not support 64bit processes on devices with the address
"localhost", "127.0.0.1" (IPv4 address), or "::1" (IPv6 address) in PRTG. This is the case for probe
devices, for example. The sensor works on all other target devices in your network though.
So if you want to monitor 64bit processes on your local machine, add this device to PRTG with
one of the IP addresses under which it is reachable in the local network (for example,
10.0.10.20 instead of 127.0.0.1) and create the sensor on this device.
section.
2495

18.11.2014
1935


remote probe 2589 .

work.
Automatic.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
1936
18.11.2014

WINDOWS PR OCESS MONITOR

Executable
Enter the name of the process that you want to monitor. Please
enter the name of an executable file without the .exe extension
(for example, enter firefox to monitor firefox.exe). The sensor
goes into a Down status if the process is not active on the device.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
1937

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1938
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1939


menu bar.
Dependency
dependent on.
Delay (Seconds)
1940
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
1941

More

Notifications
Others
1942
141
section.
18.11.2014

194 Windows Registry Sensor
6.8.194 Windows Registry Sensor

The Windows Registry sensor checks if a key and the defined string value exists in the
Windows registry and can show the retrieved value in its last message field. Additionally, the
sensor can process the result using a keyword search and switch to a defined status.
Note: This sensor type can process REG_SZ values only.

In order for this sensor to work, please make sure the RemoteRegistry "Remote Registry"
Windows service is running on both the computer running the PRTG probe and the target
machine.
Automatic.

Please make sure that the Windows user account running the PRTGProbeService "PRTG Probe
Service" on the computer running the PRTG probe has access to the registry of the remote
computer (by default, this is the probe computer's local Windows "system" account).
Additionally, the computer running the PRTG probe and the target computer must be member
of the same Windows local domain.
Note: You cannot perform a remote registry call with a Windows user account for which no
password is defined.
Add Sensor
Sensor Settings
19.09.2014
1943


Sensor Name

Tags

Priority
(top priority).
R EGISTR Y SETTINGS
Root
Select the root key of the registry entry you want to monitor.
Choose between:
HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE
HKEY_USERS
HKEY_PERFORMANCE_DATA
HKEY_CURRENT_CONFIG
HKEY_DYN_DATA
Key Name
Enter the path of the key you want to monitor. Enter the full path
after the root, each subkey separated by a backslash. For example,
enter Software\Microsoft\Windows\CurrentVersion
Value Name
Enter the name of the value you want to monitor. For example,
enter ProductId to read the product ID of the target computer's
Windows installation.
64-Bit Selection
Define how the sensor looks up the provided key name. This is
relevant for some registry keys only, for example those containing
the Wow6432Node subkey. Choose between:
1944
19.09.2014

R EGISTR Y SETTINGS
Use 32-bit regist ry view: The key provided above is copied
from the 32-bit registry editor.
Use 64-bit regist ry view: The key provided above is copied
from the 64-bit registry editor.
For more information, see the More
Value
1950
section below.
Select if the sensor processes the returned result further. Choose

between:
Ignore Value: Do not perform any keyword checks. The sensor
checks only if the defined key and value exists.
Process Text : Use the returned value to perform keyword
checks. Select below. If you choose this setting, the sensor
shows the registry value in its last message field.
Check For Existing

Keywords (Positive)

Text Must Include

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:
Check For Existing

Keywords (Negative)

Check if a certain keyword is not part of the received value. If
there is a match, the sensor shows a "Down" status.
Disable: Do not check for negative keywords.
Enable key word check (negat ive): Check if a certain keyword
does not exist in the received value. Define below.
Text Must Not Include
19.09.2014

Enter a search string that the returned value must not contain.
1945

Check For Existing

Keywords (Positive)

For Keyword Search

Use
Define the method you want to use for the search string. Choose
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1946
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1947


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1948
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1949

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
How do I discern 32-bit registry values vs. 64-bit registry values?

Notifications
1950
19.09.2014

Others
19.09.2014
141
section.
1951

195 Windows Scheduled Task Sensor
6.8.195 Windows Scheduled Task Sensor

The Windows Scheduled Task sensor returns the time since the last run of the specified task
as well as the corresponding exit code. If a task was never run, the sensor shows an error.
You can define limits (in seconds) in the channel settings 2220 for Last Run to set the sensor into
a warning or error status if the last run of the task was too long ago.
type of sensor.


In order for this sensor to work, please make sure the RemoteRegistry "Remote Registry"
Windows service is running on both the computer running the PRTG probe and the target
machine.
Automatic.

Requirement: Monitored Systems

Note: We recommend running the PRTG probe on Windows 2008 R2 or later.
1952
18.11.2014

Microsoft implemented two versions of scheduled task, V1 and V2. Windows 2000, Windows
XP, and Windows Server 2003 create scheduled tasks V1 by default. Later Windows versions
can create and read both versions.
If the system running the PRTG probe (either on the core server or a remote probe) runs on
one of these early Windows versions, you will not be able to monitor scheduled tasks of V2.
In this case, please create the tasks on the monitored machines compatible with "Windows
Server 2003, Windows XP, or Windows 2000" if there is a newer Windows version installed.
Note: These Windows versions are not officially supported by PRTG; see section Sy st em
Requirement s 21 .
If the system running the PRTG probe (either on the core server or a remote probe) runs on
Windows Vista or later, you will be able to monitor scheduled tasks of both V1 and V2 (i.e.
from all Windows versions).
Add Sensor
In order to monitor scheduled tasks, PRTG creates one sensor for each task you choose. The
SENSOR SETTINGS
Task Name
in the table head. If there are no scheduled tasks found in the
Windows Task Scheduler on the target device, you see a
corresponding message.
Note: If a task name changes after you created a sensor for it,
Sensor Settings
18.11.2014
1953


Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
Ignore Status Codes
Define exit codes of the monitored task which are not processed
by the sensor. If the external program returns one of these values,
they are converted into the code 0. Enter a comma separated list
of exit codes or leave this field empty.
Name
Shows the name of the task that this sensor monitors. Once a
the sensor anew.
If Value Changes
change.
DEBU G OPTIONS
Sensor Result
1954
between:
18.11.2014

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
1955

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1956
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1957


menu bar.
Dependency
dependent on.
Delay (Seconds)
1958
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
1959

More

Notifications
Others
1960
141
section.
18.11.2014

196 Windows System Uptime Sensor
6.8.196 Windows Sy stem Uptime Sensor

The Windows System Uptime sensor monitors uptime of a Windows system using Windows
"Windows Compatibility Options" of the parent device. It returns the total uptime of the system
in days, hours, minutes.
section.
2495


remote probe 2589 .

work.
Automatic.
19.09.2014
1961

Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1962
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
1963

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1964
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
1965


menu bar.
Dependency
dependent on.
Delay (Seconds)
1966
19.09.2014

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

Notifications
19.09.2014
1967

Others
1968
141
section.
19.09.2014

197 Windows Updates Status (Powershell) Sensor
6.8.197 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. This sensor can show the time
elapsed since the last update, as well as the following numbers:
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.
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.
type of sensor.
Note: We recommend setting the scanning interval
1971
of this sensor to at least 12 hours to limit
the load on the server being monitored.


Requirement: Remote PowerShell

The Windows Updates Status (Powershell) sensor uses PowerShell commands. To monitor
devices with this sensor, Remot e PowerShell access has to be enabled on the target
computer. Also ensure that you have installed PowerShell 2.0 or later on your probe machine.
18.11.2014
1969

680
section below.
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
1970
18.11.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
18.11.2014
1971

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
1972
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
1973


menu bar.
Dependency
dependent on.
Delay (Seconds)
1974
18.11.2014

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
18.11.2014
1975


Notifications
Others
1976
141
section.
18.11.2014

198 WMI Custom Sensor
6.8.198 WM I Custom Sensor

The WMI Custom Sensor performs a custom query via Windows Management Instrumentation
(WMI) and 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
path
Note: Sensors using the Windows Management Instrumentation (WMI) protocol have high
impact on the system performance! Try to stay below 200 WMI sensors per probe 77 . Above
this number, please consider using multiple Remot e Probes 2589 for load balancing.
section.
2495
Add Sensor
Channel Name
Enter a name for the channel in which PRTG shows the received
data. 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 2220 .
WQL File
Select a file that this sensor will use from the list. It will be
executed 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.
18.11.2014
1977

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 2611
section.
Note: Your query must return an integer or float value. Strings are
not supported!
Sensor Settings

Sensor Name

Tags

Priority
(top 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
1978
18.11.2014

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>
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
or float 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 or
float value.
SENSOR DISPLAY
Primary Channel

Chart Type
18.11.2014
1979

SENSOR DISPLAY
for each channel.
Stack Unit

Inherited Settings
described below.
1980
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
1981


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1982
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
1983

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
2217
Knowledge Base: How do I properly configure a WMI custom sensor?

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

1984
18.11.2014

Notifications
Others
18.11.2014
141
section.
1985

199 WMI Custom String Sensor
6.8.199 WM I Custom String Sensor

The WMI Custom String sensor performs a custom string query via Windows Management
Instrumentation (WMI).
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.
section.
2495
Add Sensor
Channel Name
Enter a name for the channel in which the received data will be
presented. The name will be displayed in graphs and tables. Please
enter a string. You can change the name later in the sensor's
channel settings 2220 .
WQL File
Select a file that will be used for this sensor from the drop down
menu. It will be executed with every scanning interval. The menu
contains WQL scripts from the \Cust om Sensors\WMI WQL
script s sub folder of your PRTG installation. Please store your
script there. If used on a remote probe, the file must be stored on
the system running the remote probe. If used on a cluster probe,
you must store the file on all servers running a cluster node! For
more information on how to find this path, please see Dat a
St orage 2611 section.
1986
19.09.2014

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
Namespace
Enter the namespace for the query.
WQL File
Shows the name of the file that this sensor is using. Once a sensor
anew.
Placeholder <#PH1>
Placeholder <#PH2>
Placeholder <#PH3>
19.09.2014
1987

If Value Changes

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.
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.
Multiplication
Define with which value the received values will be multiplied by. By
default, this is set to 1 in order to not change the received values.
Please enter an integer, a decimal value, or leave the field empty.
Division
Define with which value the received values will be divided by. By
default, this is set to 1 in order to not change the received values.
Please enter an integer, a decimal value, or leave the field empty.
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 2587 . If the data does not include the search pattern, the
the field empty.
Response Must Not
Include
Define which string must not be part of the data that is received
form the WMI object. You can either enter plain text or a Regular
Expression 2587 . If the data does include the search pattern, the
the field empty.
For Keyword Search

Use

the field above.
plain text search.
1988
19.09.2014

Expression 2587 .
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
or leave the field empty.
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 2220 ).
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
1994 below.
Regular Expression

Enter a Regular Expression 2587 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, 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.
Thousands Separator

Define which character is used as thousands separator for the
number extracted above. Please enter a string or leave the field
empty.
Sensor Result
Choose between:
19.09.2014
1989

(ID].t xt "): Store the last result received to the "Logs (Sensors)"
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
1990
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
1991


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
1992
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
1993

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
Example: Number Extraction with Regular Expression

If you want to extract a number in the response string using a regular expression, please note
that the index for captures in this sensor is based on 1 (not on 0). Furthermore, capturing
groups are not created automatically. The example below will illustrate this issue.
Consider the following string as returned by a request for CPU usage:
5 Sec (3.49%), 1 Min (3.555%), 5 Min (3.90%)
Assuming you would like to filter for the number 3.555, i.e., the percentage in the second
parentheses. Then enter the following regex in the Regular Expression field:
(\d+\.\d+).*(\d+\.\d+).*(\d+\.\d+)
As Index of Capt uring Group enter 3. This will extract the desired number 3.555.
1994
19.09.2014

The index has to be 3 in this case because the capturing groups here are the following:
Group 1 contains "3.49%), 1 Min (3.555), 5 Min (3.90"
Please keep in mind this note about index and capturing groups when using number
extraction.
More

Notifications
Others
19.09.2014
141
section.
1995

200 WMI Event Log Sensor
6.8.200 WM I Event Log Sensor

The WMI Event Log sensor monitors a specific Windows log file using Windows Management
Instrumentation (WMI). It shows the number of new records (volume), the number of new
records per second (speed), and it returns the last message in the sensor status.
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 2004 .
type of sensor.
section.
2495
Add Sensor
If you select more than one log file, PRTG will create one sensor for each selection. The
WMI EVENT LOG MONITOR

Log File
The Windows event log provides several different log files. You see
table head.
Sensor Settings
1996
19.09.2014


Sensor Name

Tags

Priority
(top 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
19.09.2014
Specify the type of event that this sensor processes. Other event
type will not be processed. Choose between the following event
types:
1997


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
Off: Do not filter by event source.
On: Enable filtering by event source.
Match String (Event

Source)
This field is only visible if you enabled source filtering above. Enter
a source from which the events come from. Only events from a
source matching this string will be 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
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 enabled ID filtering above. Enter one
or more event IDs (comma separated) from which the events must
have. Only events with an ID matching one of the values will be
regarded. Please enter one integer value or more comma
separated integer values.
Filter by Category
Filter all received events for a certain event category. If you enable
Off: Do not filter by event category.
On: Enable filtering by event category.
Match String (Event

Category)
1998
This field is only visible if you enabled category filtering above.

Enter a category which the events must have. Only events with a
category that matches this string will be regarded. Please enter a
string.
19.09.2014


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 enabled filtering is enabled. Enter a

user name that the events must to be assigned to. Only events
with a user name that matches this string will be 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 enabled computer filtering above.

Enter a computer name which the events must be assigned to.
Only events with a computer name that matches this string will be
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 enabled message filtering above.

Enter a message that the event must contain. Only events with a
message matching this string will be 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.
19.09.2014
1999

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2000
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2001


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2002
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2003

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
More
Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?

2004
19.09.2014

Notifications
Others
19.09.2014
141
section.
2005

201 WMI Exchange Server Sensor
6.8.201 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). It can show information about the
queue, delivery time, latency, users, etc.
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.
section.
2495
Add Sensor
In order to monitor an Exchange Server, PRTG will create one sensor for each performance
are created.
EXCHANGE SER VER DATA R EADINGS ACCESSIBLE U SING WMI

Performance Counter
You see a list of data values the sensor can monitor on your
Exchange server. The available options depend on your Exchange
server configuration. PRTG shows all possible performance
counters with name and instance description (if available). Select
head.
You might be able to select aspects regarding:
SMTP Server: Queue Lengths
2006
19.09.2014

EXCHANGE SER VER DATA R EADINGS ACCESSIBLE U SING WMI

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

Sensor Name

Tags

Priority
(top priority).
19.09.2014
2007


Display Name
Instance
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2008
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
2009

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2010
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
2011


menu bar.
Dependency
dependent on.
Delay (Seconds)
2012
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
2013

More

Notifications
Others
2014
141
section.
19.09.2014

202 WMI Exchange Transport Queue Sensor
6.8.202 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 2023 below for an explanation of the transport queue types.
Possible values that can be monitored: 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, Shadow Queue Auto Discards Total,
Submission Queue Items Expired Total, Submission Queue Length, Unreachable Queue Length.
section.
2495
Add Sensor
If you select more than one queue, multiple sensors are created at once in the Add Sensor
dialog. The settings you make in this dialog are valid for all of the sensors that are created.
19.09.2014
2015

WMI EXCHANGE TR ANSPOR T QU EU E SPECIFIC

MSExchangeTransport
Queues
You see a list of transport queues that can be monitored on your

Exchange server. The available options depend on your Exchange
server configuration. PRTG shows all possible queues 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. Note: For
performance reasons, we recommend to only select necessary
items!
Sensor Settings

Sensor Name

Tags

Priority
(top priority).

Display Name
Instance
2016
19.09.2014


WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
2017

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2018
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2019


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2020
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2021

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2022
19.09.2014

More
Knowledge Base: Types of Transport Queues in Microsoft Exchange

Notifications
Others
19.09.2014
141
section.
2023

203 WMI File Sensor
6.8.203 WM I File Sensor

The WMI File sensor monitors a file using Windows Management Instrumentation (WMI). It
shows the file size and the time since its last modification.
section.
2495
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
2024
19.09.2014

203 WMI File Sensor
WMI FILE MONITOR

File Name
Enter the name of the file that this sensor will check. Please enter a
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.
If Timestamp Changes
Define what this sensor will do when the timestamp of the file
change.
message indicating that the timestamp has changed. In
to trigger a notification 2227 whenever the timestamp changes.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
19.09.2014

2025

203 WMI File Sensor
Inherited Settings
described below.
2026
19.09.2014

203 WMI File Sensor
SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2027

203 WMI File Sensor

settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2028
19.09.2014

203 WMI File Sensor

menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2029

203 WMI File Sensor
ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2030
19.09.2014

203 WMI File Sensor
More

Notifications
Others
19.09.2014
141
section.
2031

204 WMI Free Disk Space (Multi Drive) Sensor
6.8.204 WM I Free Disk Space (M ulti Drive) Sensor

The WMI Free Disk Space (Multi Drive) sensor monitors the free disk space of one or multiple
drive(s) using Windows Management Instrumentation (WMI). It shows the space in percent and
total. One single sensor is used for all drives; the data is presented in different channels.
This sensor monitors logical partitions of a hard or fixed disk drive. PRTG identifies logical disks
by their drive letter, such as C.
section.
2495
Add Sensor
WMI DISK FR EE CONFIGU R ATION

Drive
From the drop down menu, select the drive(s) you want to
monitor. We recommend using 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
2032
19.09.2014


Sensor Name

Tags

Priority
(top priority).
WMI DISK FR EE CONFIGU R ATION

Drive
Shows the drive(s) that this sensor is monitoring; 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.
19.09.2014
2033


Upper Error Limit
the field empty.
Upper Warning Limit
the field empty.
Lower Warning Limit
the field empty.
Lower Error Limit
the field empty.
2034
19.09.2014


Size Limit Check
Choose between:
or overrun.
Upper Error Limit
empty.
Upper Warning Limit
field empty.
Lower Warning Limit
19.09.2014
field empty.
2035


Lower Error Limit
empty.
Alarm on Missing/
Removed Disk

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2036
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
2037

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2038
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
2039


menu bar.
Dependency
dependent on.
Delay (Seconds)
2040
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
2041

More

Notifications
Others
2042
141
section.
19.09.2014

205 WMI HDD Health Sensor
6.8.205 WM I HDD Health Sensor

This sensor type 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.
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.
Available sensor channels may vary, depending on the hardware used on the target system.
Available measurements may include: 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, and Total
LBAs Read.
The channel names indicate the ID of the channel, followed by a colon, and the typical meaning
of the channel. Note: Some vendors define meanings other than the common one.
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.
section.
2495
Add Sensor
In order to monitor the health of a disk, PRTG will create one sensor for each IDE device you
19.09.2014
2043

SMAR T SPECIFIC
IDE Devices
Please select one or more hard disks you want to add a sensor
for. You see a list with the names of all items which are available to
in the table head. . The items shown in the list are specific to the
parent device you create the sensor on.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SMAR T SPECIFIC
Serial No.
2044
Shows the serial number of the monitored disk. Once a sensor is

anew.
19.09.2014

SMAR T SPECIFIC
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)

is triggered.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
19.09.2014

2045

Inherited Settings
described below.
2046
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2047


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2048
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2049

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

Notifications
2050
19.09.2014

Others
19.09.2014
141
section.
2051

206 WMI Logical Disk Sensor
6.8.206 WM I Logical Disk Sensor

The WMI Logical Disk sensor monitors parameters of a logical disk of a Windows device using
Windows Management Instrumentation (WMI). It shows disk read/write time, queue, free space,
etc. on logical partitions of a disk drive.
section.
2495
Add Sensor
WMI LOGICAL DISK SPECIFIC

Logical Disks
You see a list showing the Name of the counters you can monitor
as well as the Inst ance, i.e. the respective logical disk (or '_Total').
If there are no logical disks available, you will see a corresponding
message. From the list, choose all Name/Inst ance combinations
you want to monitor by adding a check mark in front of the
respective line (for example, choose '% Disk Read Time for C:'). For
each selection one sensor will be created using the defined
settings.
Sensor Settings
2052
19.09.2014


Sensor Name

Tags

Priority
(top priority).

Display Name
Instance
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
between:
19.09.2014
2053

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2054
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2055


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2056
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2057

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2058
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
2059

207 WMI Memory Sensor
6.8.207 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 in
total.
section.
2495
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
2060
19.09.2014


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 using the default value. You can choose between:
Use default (recommended): Use PRTG's standard method to
query WMI. This is the best setting in most cases.
Use alt ernat ive (if default does not work): Use an alternative
method to query WMI. If you keep getting errors with the default
setting, please try this setting.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
19.09.2014

2061

Inherited Settings
described below.
2062
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2063


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2064
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2065

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2066
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
2067

208 WMI Microsoft SQL Server 2005 Sensor (Deprecated)
6.8.208 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.
2068
19.09.2014

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

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.
Note: This sensor can only be added to a device (computer) running a Microsoft SQL database.
section.
2495
Add Sensor
To monitor a Microsoft SQL server, PRTG creates one sensor for each instance you choose in
the Add Sensor dialog. The settings you make in this dialog are valid for all of the sensors that
are created.
2070
19.09.2014

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

Sensor Settings

Sensor Name

Tags

Priority
(top 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.
2072
19.09.2014


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:

SQL Performance
Counters
Shows the performance counter that this sensor monitors. Once a

the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
19.09.2014
2073

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2074
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2075


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2076
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2077

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

Notifications
2078
19.09.2014

Others
19.09.2014
141
section.
2079

209 WMI Microsoft SQL Server 2008 Sensor
6.8.209 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)

2080
19.09.2014

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.
section.
19.09.2014
2495
2081

Add Sensor
are created.

MS SQL Server
Instance
in the table head.
the SQL server.
SQL Server Version
default value.

SQL Performance
Counters

(per second).
2082
19.09.2014


second).
specified channels.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
2083


Service

anew.
Name
WMI Class Name
setting.
WMI Class
server instance.
Sensor Result
between:

SQL Performance
Counters
2084

the sensor anew.
19.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
2085

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2086
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
2087


menu bar.
Dependency
dependent on.
Delay (Seconds)
2088
19.09.2014

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

Notifications
19.09.2014
2089

Others
2090
141
section.
19.09.2014


CHANNEL OVER VIEW

User Connections

Logins
Logouts
Full Scans

Page Splits


Database Pages
Stolen Pages


references.
Connection Memory
(KB)

19.09.2014
2091

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.
section.
2092
2495
19.09.2014

Add Sensor
are created.

MS SQL Server
Instance
in the table head.
the SQL server.
SQL Server Version
default value.

SQL Performance
Counters

(per second).
19.09.2014
2093


second).
specified channels.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
2094
19.09.2014


Service

anew.
Name
WMI Class Name
setting.
WMI Class
server instance.
Sensor Result
between:

SQL Performance
Counters
19.09.2014

the sensor anew.
2095

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2096
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2097


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2098
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2099

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

Notifications
2100
19.09.2014

Others
19.09.2014
141
section.
2101


CHANNEL OVER VIEW

User Connections

Logins
Logouts
Full Scans

Page Splits


Database Pages
Stolen Pages


references.
Connection Memory
(KB)

2102
26.09.2014

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.
section.
26.09.2014
2495
2103

Add Sensor
are created.

MS SQL Server
Instance
in the table head.
the SQL server.
SQL Server Version
default value.

SQL Performance
Counters

(per second).
2104
26.09.2014


second).
specified channels.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
26.09.2014
2105


Service

anew.
Name
WMI Class Name
setting.
WMI Class
server instance.
Sensor Result
between:

SQL Performance
Counters
2106

the sensor anew.
26.09.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
26.09.2014
2107

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2108
26.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
26.09.2014
2109


menu bar.
Dependency
dependent on.
Delay (Seconds)
2110
26.09.2014

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

Notifications
26.09.2014
2111

Others
2112
141
section.
26.09.2014

212 WMI Remote Ping Sensor
6.8.212 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.
section.
2495
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
2113

WMI 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 WMI, then perform a Ping request from this remote
device to the target device/server. Please enter a string.
Timeout (Seconds)
Enter a timeout in seconds for the Ping. If the reply takes longer
triggered. Please enter an integer value. The maximum is 300.
Packet Size (Bytes)
value between 1 and 10000. Please enter an integer value. We
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit
2114

19.09.2014

Inherited Settings
described below.
19.09.2014
2115

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2116
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
2117


menu bar.
Dependency
dependent on.
Delay (Seconds)
2118
19.09.2014

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

Notifications
19.09.2014
2119

Others
2120
141
section.
19.09.2014

213 WMI Security Center Sensor
6.8.213 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 returns a 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
Note: 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 (i.e., Windows
Server 2003, 2008, 2012)!
section.
2495
Add Sensor
19.09.2014
2121

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 will see a corresponding message. Select the
head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).

Display Name
2122
Shows the name of the product monitored by this sensor. Once a

the sensor anew.
19.09.2014


Type
Shows the type of the product monitored by this sensor. Once a

the sensor anew.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
2123

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2124
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
2125


menu bar.
Dependency
dependent on.
Delay (Seconds)
2126
19.09.2014

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

Notifications
19.09.2014
2127

Others
2128
141
section.
19.09.2014

214 WMI Service Sensor
6.8.214 WM I Service Sensor

The WMI Service sensor monitors a Windows service using Windows Management
Instrumentation (WMI). It shows the execution time of the monitoring request. Additionally, it
can show CPU and pagefile usage, the number of handles and threads, and the working set of
the monitored service. You can monitor these channels if you enable Monit or ext ended
values in the sensor settings.
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.
section.
2495
Add Sensor
To monitor Windows services, PRTG creates one sensor for each service you select in the Add
Sensor dialog.
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, a sensor
status switches to Down if the service is not running.
Sensor Settings
18.11.2014
2129


Sensor Name

Tags

Priority
(top 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 2227
whenever PRTG (re)starts the service.
Do not hing: PRTG does not start any service on the device
automatically.
If Service is Restarted
This setting is only visible if you select the restart option above.
Define what will be done if PRTG restarts the service. Choose
between:
Monitoring
2130
Select whether you want to monitor CPU usage and other useful
performance counters. This might cause a "Class not found" error
on some Windows systems. If you do not monitor these counters,
the value '0' is returned for these channels. Choose between:
18.11.2014


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

Chart Type

for each channel.
18.11.2014
2131

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
2132
18.11.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
18.11.2014
2133


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2134
18.11.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
18.11.2014
2135

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

Notifications
2136
18.11.2014

Others
18.11.2014
141
section.
2137

215 WMI Share Sensor
6.8.215 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; you can set a sensor to Down
status for different share status messages.
section.
2495
Add Sensor
If you select more than one share, PRTG will create one sensor for each share you select. The
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: In order 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 will see a No Share
available message here.
Sensor Settings
2138
19.09.2014


Sensor Name

Tags

Priority
(top priority).
WMI SHAR ED R ECOU R CE

Shared Recource
Description
Type
Shows information about the shared resource monitored by this

TypeID
TR IGGER ER R OR STATE ON FOLLOWING CONDITIONS

Select under which conditions the sensor will change to a Down status from the list below.
As long as the share returns OK, the sensor status will be Up. Choose a Down condition by
adding a check mark symbol in front of the according line. Please 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.
19.09.2014
2139

TR IGGER ER R OR STATE ON FOLLOWING CONDITIONS

Unknown
Set sensor to Down status if the share returns an unknown status.
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.
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2140
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
2141

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2142
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
2143


menu bar.
Dependency
dependent on.
Delay (Seconds)
2144
19.09.2014

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

Notifications
19.09.2014
2145

Others
2146
141
section.
19.09.2014

216 WMI SharePoint Process Sensor
6.8.216 WM I SharePoint Process Sensor

The WMI SharePoint Process sensor monitors a Microsoft SharePoint server using Windows
Management Instrumentation (WMI). It shows the number of current page requests, active
threads, and SQL queries currently executed, as well as global heap size, object cache always
live size, template cache size, and CPU utilization.
section.
2495
Add Sensor
If you select more than one SharePoint process, multiple sensors are created at once in the
created.
WMI PR OCESS MONITOR

SharePoint Processes
You see a list of all SharePoint processes running on this device.

There is also a "_Total" process 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.
Sensor Settings
19.09.2014
2147


Sensor Name

Tags

Priority
(top priority).
WMI PR OCESS MONITOR

SharePoint Process
The name of the SharePoint process that is monitored by this

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
2148
19.09.2014

SENSOR DISPLAY
Stack Unit

Inherited Settings
described below.
19.09.2014
2149

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2150
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
2151


menu bar.
Dependency
dependent on.
Delay (Seconds)
2152
19.09.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
19.09.2014
2153

More

Notifications
Others
2154
141
section.
19.09.2014

217 WMI Terminal Services (Windows 2008) Sensor
6.8.217 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). It shows the number of active and total sessions. Active sessions are sessions with a
currently logged in user; inactive sessions (included in total) can be sessions with a
disconnected user that has not logged out, or system services using a session.
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.
Note: Depending on the OS that you want to monitor, please select either the sensor for
Windows XP/Vista/2003 or the one for Windows 2008.
section.
2495
Add Sensor
Sensor Settings

Sensor Name
19.09.2014

2155


Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2156
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2157


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2158
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2159

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

Notifications
2160
19.09.2014

Others
19.09.2014
141
section.
2161

218 WMI Terminal Services (Windows XP/Vista/2003) Sensor
6.8.218 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). It shows the number of active and total sessions. Active sessions are sessions with a
currently logged in user; inactive sessions (included in total) can be sessions with a
disconnected user that has not logged out, or system services using a session.
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.
Note: Depending on the OS that you want to monitor, please select either the sensor for
Windows XP/Vista/2003 or the one for Windows 2008.
section.
2495
Add Sensor
Sensor Settings

Sensor Name
2162

19.09.2014


Tags

Priority
(top priority).
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
19.09.2014
2163

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2164
19.09.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
19.09.2014
2165


menu bar.
Dependency
dependent on.
Delay (Seconds)
2166
19.09.2014

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

Notifications
19.09.2014
2167

Others
2168
141
section.
19.09.2014

219 WMI UTC Time Sensor
6.8.219 WM I UTC Time Sensor

The WMI UTC Time sensor monitors the UTC time of a target device using Windows
Management Instrumentation (WMI). It shows the UTC time of the target device and the time
difference between the PRTG system time and the target device in seconds.
section.
2495
Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
19.09.2014
2169

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2170
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2171


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2172
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2173

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

Notifications
2174
19.09.2014

Others
19.09.2014
141
section.
2175

220 WMI Vital System Data (V2) Sensor
6.8.220 WM I Vital Sy stem Data (V2) Sensor

The WMI Vital System Data sensor monitors vital system parameters (CPU, system, memory,
disk, network, pagefile, etc.) using Windows Management Instrumentation (WMI).
section.
2495
Add Sensor
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
2176
19.09.2014


Sensor Name

Tags

Priority
(top priority).

Display Name
Instance
WMI Class
Counter
Time Stamp
Time Frequency
Counter Type
Sensor Result
between:
19.09.2014
2177


SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2178
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2179


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2180
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2181

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2182
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
2183

221 WMI Volume Sensor
6.8.221 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). It shows free space in percent and total. For
each drive or logical volume, PRTG uses one sensor.
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.
Note: This sensor is not supported on Windows XP and earlier.
section.
2495
Add Sensor
For devices with multiple volumes, PRTG creates one sensor for each volume you select. The
WMI VOLU ME SPECIFIC

Volumes
Select the volume(s) you want to add a sensor for. You see a list
head.
Sensor Settings
2184
19.09.2014


Sensor Name

Tags

Priority
(top priority).

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
19.09.2014
This field is only visible when the drive letter option is selected
above. Enter the letter of the drive you want to monitor followed
by a double dot, for example, C:
2185

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
2186
19.09.2014

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
19.09.2014
2187


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
2188
19.09.2014


menu bar.
Dependency
dependent on.
Delay (Seconds)
19.09.2014
2189

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
2190
19.09.2014

More

Notifications
Others
19.09.2014
141
section.
2191

222 WMI Volume Fragmentation Sensor
6.8.222 WM I Volume Fragmentation Sensor

The WMI Volume Fragmentation sensor monitors the fragmentation of a logical volume via
Windows Management Instrumentation (WMI). It can show if a defragmentation is recommended
on the volume, the number of average fragments per file, the number of excess fragments in
total, the number of fragmented files in total, and file fragmentation in percent.
Note: This sensor is not supported on Windows XP and earlier.
section.
2495

Add Sensor
In order to monitor fragmentation on volumes, PRTG will create one sensor for each volume
created.
2192
18.11.2014


Volume
Select one or more volumes you want to add a sensor for. You
table head.
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
18.11.2014
2193


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
This field is only visible when the drive letter option is selected
above. Enter the letter of the drive you want to monitor followed
by a double dot, for example, C:
DEBU G OPTIONS
Sensor Result
between:
2194
18.11.2014

SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
2195

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2196
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
2197


menu bar.
Dependency
dependent on.
Delay (Seconds)
2198
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
2199

More

Notifications
Others
2200
141
section.
18.11.2014

223 WMI Windows Version Sensor
6.8.223 WM I Windows Version Sensor

The WMI Windows Version sensor reads the Windows version of the parent device via
Windows Management Instrumentation (WMI). It returns the version number (in a channel) and
the according version name in the sensor message.
section.
2495


Add Sensor
18.11.2014
2201

Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
If Value Changes
change.
DEBU G OPTIONS
Sensor Result
between:
2202
18.11.2014

DEBU G OPTIONS
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
2203

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2204
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
2205


menu bar.
Dependency
dependent on.
Delay (Seconds)
2206
18.11.2014

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

18.11.2014
2207

Notifications
Others
2208
141
section.
18.11.2014

224 WSUS Statistics Sensor
6.8.224 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 number of: 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, and the number of WSUS infrastructure updates
not approved for installation.
type of 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.
18.11.2014
2209

Add Sensor
Sensor Settings

Sensor Name

Tags

Priority
(top priority).
SENSOR SETTINGS
WSUS Server Port
Define the port where the WSUS server service is running on.
Use SSL
Define if SSL-encryption will be used for the connection to the

WSUS server. Choose between:
Yes
No
2210
18.11.2014

DEBU G OPTIONS
Sensor Result
between:
SENSOR DISPLAY
Primary Channel

Chart Type

for each channel.
Stack Unit

Inherited Settings
described below.
18.11.2014
2211

SCANNING INTER VAL

Scanning Interval

When a Sensor
Reports an Error
requests in a row.
requests in a row.
requests in a row.
requests in a row.
option will apply.
2212
18.11.2014


settings.
Schedule

Maintenance Window

between:
be set.
maintenance window.

maintenance window.
Maintenance End At

maintenance window.
Dependency Type

can choose between:
18.11.2014
2213


menu bar.
Dependency
dependent on.
Delay (Seconds)
2214
18.11.2014

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

Channel Unit Types
Bandwidt h
Memory
Disk
File
Cust om
18.11.2014
2215

More

Notifications
Others
2216
141
section.
18.11.2014
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, and by compiling an EXE or DLL file (using any Windows software
development tool).
Basics
For a general introduction, please see the sections about EXE/Script sensors and the API
documentation which contains details about the necessary return format for those sensors.
WMI Custom sensors allow executing WQL requests.
EX E/Script Sensor
483
EX E/Script Advanced Sensor

SSH Script Sensor
494
1724

WMI Cust om Sensor
2571
1977
Additionally, some types of SQL sensors execute script files with SQL queries:
My SQL v2 Sensor
804
833

Post greSQL Sensor
894
1001
Custom Sensors Included in PRTG

After installing PRTG Network Monitor, you will already find a selection of custom EXE/Script
and WMI WQL script sensors in the PRTG program directory 2611 , as well as scripts with SQL
queries for specific database sensors 2217 . 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
19.09.2014
2217
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.
483
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 494 and choose the respective file from the EX E/Script 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
2218
19.09.2014
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.
1977
and
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 2217 ) and choose the respective file from the
SQL Query File list in the sensor settings.
Downloading Pre-Build Custom Sensors

A good resource is the PRTG Add-Ons website on the open source platform Google Code.
There are also additional tools available.
Open Source Add-Ons for PRTG Network Monitor
http://code.google.com/p/prtg-addons/
More
For the other sensor types that work out-of-the-box, please see
305

Sensor Set t ings
304

2217
2220
19.09.2014
305
2227
2219
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 the data from the sensor's different channels will be
displayed in graphs, gauges, and tables. Additionally, the channel data can determine the
sensor's status. Use the limit settings to achieve this.
On the sensor's Overview page, click on the gear icon of a specific channel gauge to change
its settings. A click on the pin symbol on the left of the gear icon in a gauge will make this
channel the primary channel of the selected sensor.
You can alternatively call the settings of a channel by clicking on the respective gear icon in
the channels data table underneath the gauges.
Note: For lookup 2579 channels, we recommend staying 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
settings dialog.
2220
19.09.2014
Channel Settings for a Memory Sensor
Available Channel Settings

EDIT CHANNEL "[NAME]"
Name
19.09.2014
Enter a meaningful name to identify the channel (not editable for

script sensors after sensor creation). The name will be shown in
graphs and tables. You can automatically add the sensor's ID to the
name by using the placeholder [#id].
2221

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.
Value Lookup
This field is only visible for script sensors, the SNMP Custom
sensor, and the SNMP Library sensor. Select the lookup list to be
applied to this channel's settings.
ID
The ID of the channel cannot be changed; it is used for unique

definition. For example, you need the ID when using Sensor
Fact ory 1076 sensors.
Display
Define where the channel will be displayed. Choose from:

Show in Chart s: The data of this channel will be shown in sensor
graphs. Note: If you hide a channel here, it will also be hidden if
this graph is used in a Report 2291 .
Show in Tables: The data of this channel will be shown in sensor
data tables. Note: If you hide a channel here, it will not be
considered for the calculation of the "sum" (total) channel of this
sensor!
To change this setting, remove or add the check mark symbol in
front of it.
Line Color
Define in what color the channel will be displayed in graphs. You

can choose between
Aut omat ic
Manual
When you set this option to manual color definition please enter a
color below.
Color (#rrggbb)
This option is only available if Manual is selected in the Line Color

setting above. Please either enter a color in hexadecimal RGB
notation (as in HTML/CSS), or choose a color from the visual color
selector. The field containing the hexadecimal color value will
change to the resulting color immediately in both cases.
Data
This setting is available for most channels. Define how data will be
displayed. Choose between:
Display act ual values in [unit]: Display the values in the unit
shown.
2222
19.09.2014

Display in percent of maximum: Calculate and show percent
values based on a maximum value. Provide a maximum below.
Maximum ([unit])
This field is only visible if the percent of maximum setting is

selected above. Enter a value that will be regarded as maximum.
Please pay attention to the given unit. All percent values will be
calculated based on this value. Please enter an integer value.
Line Width
Define in what color the channel will be displayed in graphs. Enter

an integer value in pixels. Although the line width is not limited, we
recommend using values between 1 and 7 only in order to achieve
optimal results.
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 sensors. Depending on this setting, the
channel can not 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 section More
Decimal Places
2226
for a description of each value mode.
Define how many decimal places of the channel's data will be

displayed in graphs and tables. Choose between:
Aut omat ic: Let PRTG choose how many decimal places will be
used for optimal viewing results.
All: Force display of 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 there.
Spike Filter
19.09.2014
A spike filter can be used to correct obviously faulty monitoring

data. Sometimes, sensors report enormously high or far too low
values; due to an error in data transmission, or due to
incompatibilities of the physical device you are monitoring. This can
make graphs unreadable. A spike filter can compensate for these
flaws. When enabled values above and below a certain limit are
disregarded in the monitoring data for graphs and tables. Note: The
monitoring data itself will not be changed (but only the
presentation of the data) and this setting is valid for all data of this
channel (also the historic data). Choose between:
2223

Disable Filt ering: Display all data as it is; do not filter out spikes.
Enable Filt ering: Enable a filter to remove spike values.
Additional fields appear below.
Note: The spike filter option is not available for the channel
Downt ime.
Spike Filter Max. Value
[unit]
This field is only visible if spike filter is enabled above. Specify the
maximum value allowed in the channel's data. All values above this
value will be disregarded in graphs and tables. Please enter an
Spike Filter Min. Value

[unit]
This field is only visible if spike filter is enabled above. Specify the
minimum value allowed in the channel's data. All values below this
value will be disregarded in graphs and tables. Please enter an
Vertical Axis Scaling
Define how the vertical axis for the channel is displayed in graphs.
Choose between:
Aut omat ic Scaling: Let PRTG decide on the optimum scaling;
usually ranging from the minimum to the maximum value. PRTG
will use 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 chart with
multiple vertical axis for the same unit label.
Note: Settings for this option are ignored if 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) is
enabled in the sensor's Set t ings tab.
Vertical Axis Maximum

[unit]
This field is only visible if vertical axis scaling is enabled above.

Specify the maximum value that will be used on the vertical axis for
the channel. Enter an integer value.
Vertical Axis Minimum

[unit]
This field is only visible if vertical axis scaling is enabled above.

Specify the minimum value that will be used on the vertical axis for
the channel. Enter an integer value.
Limits
The channel can affect the status of the sensor it is part of. By
entering limits, you can define when the sensor will enter a
Warning or Down status; depending on the channel's data. Using
this function, you can e.g. set a traffic sensor (which is usually
never in a down state) to error when certain limits that you
consider critical are reached.
2224
19.09.2014

Choose between:
Disable Limit s: Do not use the channel's data to control the
sensor's status.
Enable Limit s: Define limits. Additional fields appear below. The
sensor belonging to the channel will enter a Warning or Down
status when limits are undercut or overrun.
Note: The limits option is not available for the channel "Downtime".
Note: If a channel uses lookups 2579 , we strongly recommend you to
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.
Upper Error Limit [unit]
This field is only visible if limits are enabled above. Specify an upper
limit for an error state. If the channel's values overrun this value,
the sensor will be set to Down. Note: While a sensor shows a
Down 121 status triggered by a limit, it will still receive data in its
channels. Please enter a decimal value or leave the field empty.
Upper Warning Limit

[unit]
This field is only visible if limits are enabled above. Specify an upper
limit for a warning state. If the channel's values overrun this value,
the sensor will be set to Warning. Please enter a decimal value or
Lower Warning Limit

[unit]
This field is only visible if limits are enabled above. Specify a lower
limit for a warning state. If the channel's values undercut this value,
the sensor will be set to Warning. Please enter a decimal value or
Lower Error Limit [unit]
This field is only visible if limits are enabled above. Specify a lower
limit for an error state. If the channel's values undercut this value,
the sensor will be set to Down. Note: While a sensor shows a
Down 121 status triggered by a limit, it will still receive data in its
channels. Please enter a decimal value or leave the field empty.
Error Limit Message
This field is only visible if limits are enabled above. Enter an

additional message. It will be added to the sensor's message when
entering a Down status. Please enter a string or leave the field
empty.
19.09.2014
2225

Warning Limit Message
This field is only visible if limits are enabled above. Enter an

additional message. It will be added to the sensor's message when
entering a Warning status. Please enter a string or leave the field
empty.
Click on Save to store your settings and to close the settings window. With a click on Apply
changed settings will be stored and the settings 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 then select another channel via the drop-down menu on top of the settings window. You
can Close the settings window with a click on this button.
Note: If you have changed any settings and click on Close 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 respectively. Click on Save to apply your changes.
More
Knowledge Base: What is the Value Mode in channel settings?

Sensor Set t ings
304

2217
2220
2226
305
2227
19.09.2014
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
Note: Although the sensors activate a trigger, you can set notification triggers higher in the
hierarchy (for example for groups or devices), thus defining triggers for multiple sensors using
the inheritance mechanism 88 .
Note
This section describes one of four steps to set up the notification system in PRTG. A complete
notification setup involves:
1. Check and set up the Not ificat ion Delivery settings. This tells PRTG how to send
messages.
For detailed information, see Sy st em Administ rat ionNot ificat ion Delivery 2372 .
2. Check and set 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 2349 .
3. Check and set up several Not ificat ions. This defines the kind of message and its content.
For detailed information, see Account Set t ingsNot ificat ions 2334 .
4. Check and set up Not ificat ion Triggers for objects. These provokes the defined
notifications.
For detailed information, see Sensor Not ificat ions Set t ings 2227 .
19.11.2014
2227
Note: We recommend you to always set up at least two notifications with different delivery
methods for a notification trigger, for example, one email notification 2339 and one SMS
notification 2341 . 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 by
using the latency setting in a state trigger 2229 and selecting a notification with another delivery
method than for the first trigger condition, or by setting up a second trigger with another
notification for the respective object.
For background information, please see Not ificat ions
2263
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 when there are no triggers defined in groups or devices above the current object.
You can see the type and the notifications that are executed once this trigger is activated.
Trigger Inheritance
Define whether the triggers shown above will be handed on to the

current object. Choose between:
Inherit t rigger(s) from parent object (s): Use the triggers
shown above.
Only use t riggers defined for t his object : Do not use the
triggers shown above; for this object only use the triggers
defined below.
This setting is valid for all triggers shown above. It is not possible
to only select some of them.
In section Triggers t hat are defined in library object (s) you see all notification triggers that
are set for Libraries 2275 which contain the currently selected sensor. Click on a library name in
the column "Inherited from" to view this library.
You can set up one or more of the following triggers, each with different setting options.
Which trigger types is visible depends on the kind of object you edit:
Add State Trigger
2229
Add Speed Trigger
2230
Add Volume Trigger
2232
Add Threshold Trigger

Add Change Trigger
2228
2234
2235
19.11.2014
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 on the Add St at e Trigger button to add a
new trigger, or click on 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) 2334 to be
executed.
STATE TR IGGER
When sensor state is
[...]
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:
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 81 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 2334 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.
19.11.2014
2229
STATE TR IGGER
...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 2334 settings. You can also
choose no not ificat ion to only use other conditions for this
trigger.
...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.
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
Save
Click on Save to confirm your settings.
Cancel
Click on 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 on the Add Speed Trigger button to add a new trigger, or
click on 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) 2334 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 304 ), 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:
2230
19.11.2014
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
designation). 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.
19.11.2014
2231
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 2334 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 2334
settings. You can also choose no not ificat ion to only use other
conditions for this trigger.
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 on the Add Volume Trigger button to add a new trigger,
or click on 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) 2334 to be executed.
VOLU ME TR IGGER
When [...] channel
2232
considers for this comparison. Select Primary to generally use the
primary channel of a sensor (you can define this in the sensor
19.11.2014
VOLU ME TR IGGER
...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 2334 settings. You can also
trigger.
Save
Cancel
Note: No escalation notification, no repeat, and no notification when condition clears are
available for this trigger type.
19.11.2014
2233
Add Threshold Trigger

Define a trigger that is activated when a sensor reaches specific values. Click on the Add
Threshold Trigger button to add a new trigger, or click on 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) 2334 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. Please
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.
...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 2334
settings. You can also choose no not ificat ion to only use other
conditions for this trigger.
2234
19.11.2014
THR ESHOLD TR IGGER

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
Save
Click on 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 on the Add Change Trigger
button to add a new trigger, or click on 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) 2334 to be executed.
CHANGE TR IGGER
When sensor changes
perform [...]
Select a notification that is triggered whenever a compatible

sensor sends a 'change notification'. You can enable this option in
the settings 304 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 2334 settings.
Note: There are no other options available for this trigger type.

Sensor Set t ings
304

2217
2220
19.11.2014
305
2227
2235
Object Settings Overview

For more general information about object settings, please see section Object Set t ings
2236
141
19.11.2014
Part 7
Ajax Web InterfaceAdvanced Procedures
19.09.2014
2237
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
2240
Arrange Object s
Clone Object
Mult i-Edit
2245
2246
2248

Show Dependencies
Geo Maps
Report s
Maps
Set up
2238
2256
2258
Not ificat ions

Libraries
2253
2263
2275
2291
2311
2327
19.09.2014
Part 7: Ajax Web InterfaceAdvanced Procedures |

100
192
Related Topics
Ent erprise Console
2430
19.09.2014
2482
2239
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 306 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.
2240
19.09.2014
Toplist Top Protoc ols for a Pac ket Sniffer Sensor
Click on 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, etc. It depends on the selected list
which information is available. Click on an entry in the Toplist Periods lists on the left side to
view data for a certain time span. By default, a time span of 15 minutes is set. Additionally,
several table list options 155 are available.
In order to print a toplist, click on the Print t his t oplist button to view a printer-friendly
version and then use the print option of your browser to send it to your printer. With Sensor
Overview you will return to the current sensor's overview tab. For a quick selection of other
toplists of the current sensor, click on 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.
19.09.2014
2241
Add
Click on the Add Toplist item in the sensor overview to create a new toplist. The available
options are the same as for editing 2242 a list.
Edit
Click on the small gear icon of a toplist item in the sensor overview to modify it.
TOPLIST SETTINGS
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 t oplist ): Create your own list by
selecting criteria below.
Toplist is based on
This setting is only available if a custom type is selected 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're different for Packet
Sniffer, NetFlow v5, v9 (and IPFIX), and sFlow. Note: For
performance reasons, only select the field you really want to
monitor. Please see Performance Considerat ions 2243 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: In order 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 2243 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: In
order to avoid load problems on your probe system, please do not
set this value as low as possible. Default setting is 100, in order to
store the top 100 entries for each period. Please see Performance
Considerat ions 2243 section below.
2242
19.09.2014
TOPLIST SETTINGS
Probe/Core Data
Transfer
Define how the probe sends the toplist dataset 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 this toplist is
created for. This can create a lot of bandwidth and CPU load with
many sniffer sensors, complex traffic, or long toplists.
Wait unt il t oplist period ends (less cpu&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, but only toplists with finished
periods.
For more information, please see Performance Considerat ions
section below.
Memory Limit (MB)
2243
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 on the small trashcan icon of a toplist item 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.
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 desirable (especially important when traffic has a high level of
diversity) to minimize memory usage.
19.09.2014
2243
Memory requirements can grow almost exponentially with each field used in the toplists
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 t oplist period ends option in the toplist settings 2242 .
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 probe process' memory usage.
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 that 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 you should restrict access 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
2502
Monit oring Bandwidt h via Packet Sniffing
2244
2500
19.09.2014
Part 7: Ajax Web InterfaceAdvanced Procedures | 2 Arrange Objects
7.2
Arrange Objects
There are several possibilities 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 on the Manage 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 226 .
Device Details View: Arrange Sensors

When viewing the Overview tab of a device, you will see a list of all sensors on this device.
Arrange Sensors on a Dev ic e
Click on the column headers Pos, Sensors, St at us, or Priorit y to re-sort the sensor list. To
change a sensor's position, simply click on 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 on any object to show the Context Menu 163 . 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.
19.09.2014
2245
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
2253 option, a cloned device will contain 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. You cannot
clone the sensor types QoS (Qualit y of Service) One Way Sensor 1020 and QoS (Qualit y of
Service) Round Trip Sensor 1027 .
Note: If you want to clone a sensor, a faster way will be to use the Manage Device Tree
function.
To start, right click on an object in your device tree, and from the context menu
Clone.... An assistant will appear.
163
226
, select
Clone Dialog for a Sensor
2246
19.09.2014
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 is to be

cloned. The available information varies depending on whether you
are about to clone a group, device, or sensor.
NEW Object Name

New Object Name
Enter a name for the cloned object. By default, the old name is
filled in, proceeded by Clone of.
New IP Address/DNS
Name
This field is only available when cloning a device. Enter the IP

address or DNS name for the new device.
PLEASE CHOOSE A GR OU P/DEVICE TO ADD THE NEW object t o

From the device tree shown, choose an object you want to add the cloned object to. When
cloning a group or device, select a group. When cloning a sensor, select the device you
want to add it to.
You will be redirected to the newly cloned object's overview 124 page. By default, all sensors
are initially paused to give you the chance to change settings before monitoring starts. Please
check the settings 141 and resume 162 monitoring.
Related Topics
Manage Device Tree
19.09.2014
2253
226
2247
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 227 ).
Note: Using multi-edit, not all settings can be changed. PRTG will offer only settings which all
selected objects have in common.
Note: The multi-edit option is not available for the standard user groups
Administrators and PRTG Users Group.
2390
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 2275 ,
Maps 2311 , Report s 2291 , Not ificat ions 2263 , and Schedules 2353 .
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 and chosen objects are
shaded in green.
2248
19.09.2014
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. If you click on one of those buttons, the respective function will be
applied to all selected objects.
Other options are available in the drop down menu. Hover 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. If you choose an
entry, the respective function will be applied to all selected objects.
Once you have selected the objects you want to change settings for, click on the screwdriver
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 would like to edit, change the according
values and click on Save. The changes will be applied to all selected objects.
19.09.2014
2249
For available settings, please see below.
Edit SettingsSettings
In the multi-selected sensors' Set t ings tab within the Edit Mult iple Object s popup, you can
edit most of the sensors' properties which they have in common, respectively in the Edit
Mult iple Object s popup for devices. For example, for devices or sensors, edit the name, tags,
priority, scanning interval, access rights, etc.
Example of Dev ic e Settings in Multi-Edit Mode
The available options depend on the selected objects and will 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.
In order 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 multiedit. All properties that are not activated with a check mark will remain unchanged.
Click on the OK button to store your settings. If you close the popup via the X or Cancel
button, all changes to the settings will be lost!
2250
19.09.2014
Edit SettingsChannel Settings

The Channel Set t ings tab in the Edit Mult iple Object s popup 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, channel name, ID,
display settings, colors, scaling, limits, etc.
Example of Sensor Channel Settings in Multi-Edit Mode
The available options depend on the selected sensors and will 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.
In order 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 will remain unchanged.
Click on the OK button to store your settings. If you close the popup via the X or Cancel
button, all changes to the settings will be lost!
Related Topics
19.09.2014
155
2251
Manage Device Tree
2252
226
19.09.2014
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, information for nearly all
sensors on this device will be saved to a template file which you can later use in combination
with Aut o-Discovery 194 (restrictions apply for a few sensor types). From the sensors, all
relevant settings will be saved, except those that refer to other objects, such as schedules,
triggers, access rights, etc. They will automatically be reverted to Inherit .
To start, right click on a device in your device tree, and from the context menu
Creat e Device Templat e.... An assistant will appear.
163
, select
Create Dev ic e Template Assistant
19.09.2014
2253
Device Template Settings

CHOOSE TEMPLATE NAME
File Name
Enter a name under which the file will be stored. It will be stored
with the extension .odt in the \PRTG Network Monitor
\devicetemplates sub-directory of your PRTG core installation (of
the Master node, if in a cluster). The file may not exist in this
directory, otherwise you will see an error message.
Template Name
Enter a meaningful display name for the template as it will appear in

the web interface.
Exclude Sensors
Select sensors which you do not want to include into the device
template. Mark the corresponding checkboxes of the sensors
which should not appear in the device template.
You will see a success message indicating that your template file was saved. Click on OK.
Finished! 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.
Note: Numbers will be added to the original sensor names. For detailed information, please
see Aut o-Discovery 194 section.
Settings That Are Not Saved

There are a few settings which cannot be saved into a device template, and will therefore be
set to default, such as the Dependency Type setting Mast er object for parent (in Schedules
and Dependencies section), and Result Handling settings Writ e result do disk (as this is
intended for debugging purposes only). Also, settings in the Access Right s section are not
saved to avoid security flaws.
Furthermore, due to internal restrictions, the following sensor types will not be saved into a
device template:
Amazon CloudWat ch
Core/Probe/Clust er Healt h
DHCP
Ent erprise Virt ual Array
2254
19.09.2014
IPFIX
IPFIX (Cust om)
IPMI Sy st em Healt h
jFlow V5
jFlow V5 (Cust om)
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
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
2032
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 contained in this template are
updated. Therefore, when applying a new template to an existing device, all sensors contained
in this template will be newly created on this device, even if those sensors were previously
created using (another) device template!
Related Topics
Clone Object
2246
Manage Device Tree
19.09.2014
226
2255
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 Dependencies 91 section.
In the main menu, choose Devices, and then hover 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 will show a table of manually set dependencies (section Select
object in any object's settings).
Mast er Dependencies will show a table of master dependencies.
Dependencies Graph will show a visualization of dependencies. See below
2256
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. Hover 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 2257 is used for the 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 112 of the
currently selected object.
2256
19.09.2014
Part 7: Ajax Web InterfaceAdvanced Procedures | 6 Show Dependencies
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.
Click on the + or buttons on the left in the header bar to zoom in resp. out of graph.
Click on probe and group nodes to show the respective dependencies.
Click on device or sensor nodes to open the respective overview tab.
Click on the + resp. boxes to expand resp. collapse probe and group nodes.
Numbers in parentheses indicate how many child nodes of an object are shown.
The Highlight Connect ion buttons right to sensors will 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 192 . 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 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.
19.09.2014
2257
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 an object's details page, or on PRTG Maps 2311 . 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 the defined locations will be marked with the corresponding object
icons and their status 2261 on the map. You can select your favorite map tiles provider in
Sy st em Administ rat ionUser Int erface 2358 (setting Geo Maps).
Geographical maps can be displayed on the device tree. PRTG will adjust the zoom of a map
automatically such that all locations of a selected object can be displayed. You can also add
geographical maps to PRTG Maps 2311 . For this concern, go to the PRTG Maps Designer 2317
(either in an existing map or creating a new one) and choose the entry Geo Maps from the
properties menu on the right.
2258
19.09.2014
The Global Status of a Network in a Geo Map
Using Geo Maps

In order to use geographical maps within the PRTG web interface
, please make sure the following:
100
or Ent erprise Console
2430
1. In the system administration (within the 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 2358 (setting
Geo Maps) for detailed information.
2. In your objects' settings 141 , add a city name, or address, or coordinates in the first line of
the Locat ion field. As soon as you view the details of such an object, a geographical map
will be shown. The Locat ion information will also be used when viewing objects in the
Ent erprise Console 2430 or when adding Geo Maps objects to PRTG Maps 2311 .
3. Make sure your PRTG core server has access to the internet in order to obtain map tiles. If a
proxy is mandatory in your network, please configure proxy settings accordingly. For
details, please see Sy st em Administ rat ionCore & Probes 2379 . For details about tile server
domains, please see More 2262 section below.
19.09.2014
2259
Labeling Locations
You can define your own labels for locations of objects. For this concern, 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. In PRTG's geo map, this object will be displayed with the defined label.
Defining Loc ation New York City with Geo Coordinates and Label
Big Apple
The location New York City will appear with the label Big Apple then:
Loc ation New York City with Label Big Apple
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.
2260
19.09.2014
Map Icon Colors

On the geographical maps the different location icons will show the overall status at this
location by using a color code. Following, all possible location states are listed ordered by
their hierarchy:
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) the status was acknowledged by a PRTG user,
applying the Acknowledge Alarm function. The
Down states of all sensors at this location have
to 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 Sensor St at es
19.09.2014
121
section.
2261
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 2262 for details.
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?
2262
19.09.2014
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 2339 , text messaging 2341 , push notifications 2340 to Android and iOS devices,
and many more 2338 . PRTG sends notifications to the desired user's Not ificat ion Cont act s 2349
that you can define for each user account of your PRTG installation.
For video instructions, please see the More
2265
section below.
Overview
PRTG sends a notification when a defined event evokes it. Notifications can be triggered by the
following events:
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
2339
Send Push Not ificat ion
2340
Send SMS/Pager Message

Add Ent ry t o Event Log
Send Sy slog Message
Send SNMP Trap
2341
2342
2343
2344
Execut e HTTP Act ion

Execut e Program
2345
2345
Send Amazon Simple Not ificat ion Service (SNS) Message

Assign Ticket
2346
For details, see section Account Set t ingsNot ificat ions
18.11.2014
2346
2338
2263
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 you to always
add two different ways to get a notification. For example, use the latency setting of a state
trigger 2229 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 respective 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 section More
2265
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:
messages.
2. Check and set up Notification Contacts for the users of your PRTG installation. This defines
where to send notifications.
notifications.
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 2229 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.
2264
2266
for a step-
18.11.2014
More
http://www.paessler.com/support/video_tutorials/notification-and-trigger
Knowledge Base: Notifications based on priorities
18.11.2014
2265

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:
2266
Provide necessary information about the delivery of notifications (SMTP and SMS).
Step 2:
2266
Specify recipients for notifications for each user account of your PRTG installation.
Step 3:
2267
Create notifications, specifying the type of notification and its content.
Step 4: 2269 Define thresholds that change a sensor's status (this is not necessary for every
kind of notification).
Step 5: 2271 Add suitable triggers to objects which evoke notifications if something is going
wrong in your network.
Step 6:
2272
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 2372 .
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 with the
corresponding PRTG smartphone app 2486 ). 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 2329 . 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
2266
2349
18.11.2014

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
2273
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 2266 ), its subject, the format, the content of the
email, 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. Feel
free to adjust email messages to your needs (see section More 2273 ).
You can choose any other notification method, of course. Please see Account Set t ings
Not ificat ions 2338 .
18.11.2014
2267

Creating an Email Notific ation
Once you set up the notification completely, click on Save. You will be redirected to the
notifications overview page. You can now use this notification for every trigger on every
object in your device tree.
2268
18.11.2014

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 2032 , SNMP Linux Disk Free 1423 , SSH Disk Free 1645
Enable limits in Sensor Channels Set t ings
You can achieve both with Mult i-Edit
2248
2220
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 2250 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".
18.11.2014
2269

Step 4.2: Define Limits for Sensor Channels

In order 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 will only apply 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 1286 . For these sensor types, you can
use Mult i-Edit 2251 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 screwdriver 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 will apply to all channels with this name
of the multi-edited sensors.
2270
18.11.2014

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 2273 .
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.
Go on the Not ificat ions tab.
18.11.2014
2271

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
175
, 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 146 for more information.
2272
18.11.2014

More
This section provides information about additional options you have when working with
notifications.
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 2334 .
Cont ent of Emails:
You can individually adjust the subject, content, header, and footer of emails to your needs.
PRTG allows you to use placeholders here. See section Account Set t ingsNot ificat ions
2338 for details about editing subject and message, and section Sy st em Administ rat ion
Not ifcat ion Delivery 2372 for details about editing header and footer of emails.
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 2263 .
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 you to use a PRTG library
2275 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 2284 and add missing sensors
this way. You can also filter by priority and other sensor properties.
18.11.2014
2273

Settings of a Library with Diskspac e Sensors
2274
18.11.2014
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
2275
St art Libraries
Libraries List
2276
2276
Working wit h Libraries
2277
Introduction
Libraries is a powerful feature which enables you to create additional views of your device
tree, which 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 show data
in different ways, e.g. depending on target groups or 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.
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
19.09.2014
2275
Arrange sensors in a tree-like view regardless of which device they are running on
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 right within your browser.
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 be initially 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 179 to view or add custom views of your
network's status and monitoring data. Hover 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 to show other menu items. Follow

the menu path (it is specific to your setup) to select a library and
open it.
2278
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.
2276
19.09.2014
Click on the name of a library to view it.

Delet e: Delete this library.
Clone: Create a clone of this library.
Used by : Show which other monitoring objects use this library.
Click on the Add Library button to add a new library.
Please see also Working wit h Table List s 155 . Additionally, there is multi-edit available. This
enables you to change properties of several objects at a time. For more details, please see
Mult i-Edit List s 2248 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
2278
2282
Libraries and Node Set t ings

Cont ext Menus
19.09.2014
2284
2290
2277

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
2278
St ep 2: Add Library Nodes
2279
St ep 3: Set Library Node Display Set t ings

St ep 4: View
2279
2280
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
2284
section.
Add Library Assistant Step 1
2278
19.09.2014

Step 2: Add Library Nodes

Click to the Management tab. You will see a split screen: On the left side, your library is show
(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 226 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.
19.09.2014
2279

Right-click on 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.
2284
(OverviewLibrary Node
Step 4: View
Click on the Overview tab to see the final appearance of your library. You have the following
options:
Hover 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 112 . The setting is reset the next
time you open the library.
Use the Device Tree View selection in the page header bar 112 to change the size of the
library display. Note: This function is the same you know from the device tree 115 .
2280
19.09.2014

Use the Search box in the page header bar 112 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 112 .
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
19.09.2014
2290
2281

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 show
(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 226 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.
2282
19.09.2014

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 on 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.
2284
(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
19.09.2014
2290
section.
2283

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 158 .
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 : View all
sensors underneath the linked object (only sensors are shown).
You can combine several filters with each other (see below).
Filter By Type
2284
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:
18.11.2014


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)
in the table head.
18.11.2014
2285


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 90 for details.
Note: The tag of a sensor can also be inherited 88 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 90 for details.
Filter By Priority

Choose between:
Show all priorit ies: Do not filter for the priority setting
sensor.
159
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 )
****
***
**
* (lowest )
2286
18.11.2014


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 2282 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
Enter one or more tags, separated by space or comma. For

example, you can use tags later to search for the library. Tags
entered here are inherited 88 to all library nodes underneath. Tags
are not case sensitive.
18.11.2014
2287

ACCESS R IGHTS
User Group Access
monitoring results.
rights settings.
option.
Access Right s 95 .
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 2263 .
Comments
2288
18.11.2014

History
entries.
Delete
You can delete the entire library any time by clicking on the trash symbol on the right.
18.11.2014
2289

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
Library Node Menu: Edit
Library Node Menu: Mov e
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.
2284
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 163 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.
2290
19.09.2014
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 ad-hoc, as well as scheduled report generation
in HTML and PDF format. So you can run reports on demand or on a regular basis (for example,
once a day). You can create reports for one single sensor, or you choose a range of sensors
you want to create a report for. It is also possible to create HTML reports for your system
configuration 2294 .
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.
Report Sample
The sample report above shows a 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 from the main menu 183 to view or add reports of your monitoring
data. Hover to show other menu items. Choose between:
18.11.2014
2291
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. Hover to show other menu items. Follow

the menu path (it is specific to your setup) to select a report.
Configurat ion
Report s
Create reports for maps, reports, user and user groups, and
system configuration to document changes to the configuration.
Hover to see the available configuration reports 2294 .
2295
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.
Templat e: Shows the name of the template that this report uses.
2292
18.11.2014
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 line, you can Edit , Clone, and Delet e the respective report.
Click on the Add Report button to add a new report, or click on the name of an existing
report to view and edit its settings. You can also run a pre-configured report easily by clicking
on its name and then using the options in the Run Now tab. For both options, please see
Report s St ep By St ep 2295 section.
Note: You can run configuration reports
2291
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
2295
View and Run Report s
2298
Report s Set t ings
2301
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.
18.11.2014
2293
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, User & User Groups, and Sy st em Configurat ion. PRTG
generates these reports in a new browser window as HTML page in the common reports style
of PRTG (for example, like Hist oric Dat a Report s 133 of sensors). You can use configuration
reports, for example, to file and document changes to the configuration of PRTG.
The particular configuration reports contain the same information as you can see on the
overview pages of Maps 2311 , Report s 2291 , as well as on the system administration tabs User
Account s 2385 and User Groups 2390 . The configuration report Sy st em Configurat ion includes
the current system administration settings of the tabs User Int erface 2357 , Monit oring 2367 ,
Not ificat ion Delivery 2372 , Core & Probes 2379 , and Clust er 2394 . Configuration reports are
interactive so you can click on available links to go to the corresponding webpage in the PRTG
web interface.
Related Topics
2294
124
133
18.11.2014

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 on a report's
name in the reports main screen, select the Set t ings tab. The other steps are the same as for
new reports. Although some settings are already given, we recommend you to check the
settings. 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 2296 in this section.
Step 1: Add Report

Click on the Add Report button to add a new report. An assistant appears where you can
define various settings. First, enter a Report Name.
Add Report Assistant
18.11.2014
2295

Step 2: Select a Template

In the Templat e section, select one of the report templates from the list. This defines the
overall look of your report and affects in which detail (interval) monitoring data is included. For
a detailed description on the available options, please see Report s Set t ings 2301 section. If you
are not sure, try a template that appears most suitable to you. You can change all settings
later.
Step 3: Define Additional Settings

Select a Securit y Cont ext (best choose PRTG Sy st em Administ rat or, if available), your
Timezone, and Paper Size for PDF generation. For detailed information, please see Report s
Set t ings 2301 section.
Step 4: Select Nodes and Sensors

Choose the sensors you want to include in the report. First, when running in a cluster 81 ,
define the Clust er Node the monitoring data is taken from. 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 from 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 matches 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 as default when you
add bandwidth sensors, so this tag typically gathers all bandwidth sensors, unless you
configured your system differently. You can enter several tags. Hit the enter key, comma, or
space after providing one 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 tool to group sensors or other objects. For more information, see Tags
section. You can also leave the tag fields empty and only choose specific sensors manually
later.
90
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 choose which time Period will be covered by the report, and if you want to
show percentiles, add report comments, or special access rights. For detailed information,
please see Report s Set t ings 2301 section.
Note: Scheduled reports are not executed on failover nodes
2602
by default.
2296
18.11.2014

Step 6: Check and Adjust the Sensors Included

When you saved 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 Report s Set t ings 2308 section for detailed information. The final
report shows sensors from both manual and by tag selection.
Step 7: Run Report

Switch to the Run Now tab, select the current or previous 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 More 2310 section of Reports Settings 2301 .
18.11.2014
2297

2 View and Run Reports
7.10.2 View and Run Reports

In the web interface, click on the Report s entry in the main menu to show the reports main
screen. Click on a report's name to select it. Using the reports tabs you can access all
functionalities and settings for this report. Click on the Go t o all report s button at the
bottom of the page to return to the list of Reports.
Report Tabs
Run Now
In 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 2301 . 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 2301 . 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 the period option is enabled above.

From the list, select a data range for which the report will be
generated. The actual time spans shown depend on the available
monitoring data and on the report period type defined in the
report's settings 2301 . It can be days, weeks, months, or years.
Start Date
This selection is only visible if the date range option is enabled

above. Define the begin of the time span for which the report will
be generated. Click in the field and select a date from the calendar.
Make sure you define a valid period.
2298
19.09.2014

R U N R EPOR T "[Name]"
End Date

above. Define the end of the time span for which the report will be
generated. Click in the field and select a date from the calendar.
Make sure you define a valid period.
Quick Range

above. Choose between different pre-defined ranges by simply
clicking on it. With each click the St art and End Dat e fields above
will be changed 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. It will be loaded in a new browser window or tab.
Creat e and st ore PDF file: Create a PDF file of the report and
store it. Once finished, you will find it in the St ored Report s tab
and a ToDo ticket 149 will be created. By default, PRTG sends out
a notification mail to the administrator in this case.
Creat e PDF file, st ore it and send by email: Create a PDF file of
the report, store it, and send it via email once it is finished.
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 2300 section below.
Note: In order to create PDF files, ensure that the print spooler
service is running on the system with your PRTG server.
Target Email Address
This option is only visible if sending by email is selected above.

Please enter a valid email address the report will be sent to. Note:
Configuration for outgoing email can be changed in the Sy st em
Administ rat ionNot ificat ion Delivery 2372 settings.
Compression
This option is only visible if sending by email is selected above.

Specify if the attached report files will be compressed before
sending. Choose between:
Uncompressed: The report files will not be compressed before
they are sent by email.
Compressed: The report files will be compressed to a ZIP file
before they are sent by email.
19.09.2014
2299

Click on 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's finished.
Note: Any sensor graphs in your report will only show the channels that are enabled via the
Show in Chart s option in the Sensor Channels Set t ings 2220 of the respective sensor.
Stored Reports
In the St ored Report s tab you can view PDF reports created in the past. Simply click on 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 2383 settings.
Other Tabs
For all other tabs, please see Report s Set t ings
2301
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?
2300
19.09.2014

3 Reports Settings
7.10.3 Reports Settings

In the web interface, click on the Report s entry in the main menu to show the reports main
screen. Click on a report's name to select it. Using the reports tabs you can access all
functionalities and settings for this report. Click on the Go t o all report s button at the
bottom of the page to return to the list of Reports.
Report Tabs
Run Now
In the Run Now tab you can execute a report immediately with the settings configured. Please
see View and Run Report s 2298 section.
Stored Reports
In the St ored Report s tab you can view reports created in the past. Please see View and Run
Report s 2300 section.
Settings
Click on the Set t ings tab to open a report's settings.
BASIC R EPOR T SETTINGS

Report Name
Enter a meaningful name to identify this report.
Template
Select a template for the report. This will define the overall look of
your report. There are several report templates delivered with
PRTG. They also define in which detail (interval) monitoring data is
included. You can choose from templates in the following
categories:
Dat a Table Only : Create a report with data tables only. Choose
from several intervals.
Graph Only : Create a report with graphs only. Choose from
several intervals.
Graph wit h Dat a Table: Create a report with graphs and data
table. Choose from several intervals.
18.11.2014
2301

3 Reports Settings
BASIC R EPOR T SETTINGS

List of Sensors: Create a report in a compact sensor list style.
This is available with and without graphs.
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.
Top 100 Highest and Lowest : Create a report with up to 100
objects with the highest and lowest average values. Choose
from different intervals.
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.
Monitoring data within an interval is averaged. See also the
comment on data averaging in the Report s 2293 (Automatic
Averaging) section. For information on how to modify templates,
Security Context
Define the user account that will be used for access to monitoring
data. The report will only contain objects which the selected user
95 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 report. PRTG Administrator users can change
this setting.
Timezone
Define the time zone that will be used for all date-specific settings
in this report (see below). Select a time zone from the dropdown
list.
Paper Size
Define the paper size in which PDF reports will be created. Choose
between:
A4: Use German DIN A4 format.
Legal: Use US legal paper format.
Let t er: Use US letter paper format.
SENSOR S
Cluster Node
2302
This field is only visible when running PRTG in Clust ering 81 mode.
Define the cluster node the report will take monitoring data from.
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.
18.11.2014

3 Reports Settings
SENSOR S
Note: A report for all nodes will include data of the primary sensor
channels only, not for other sensor channels.
Note: If you select a failover node, the report will not show data
from the local probe or from a remote probe and might be empty.
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
2308 tab.
Add Sensors by Tag
Define the sensors included in this report by tag 90 . 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 section Tags 90 for
details.
Note: Tags are inherited 90 invisibly and automatically. So, for
example, if you enter the tag of a group here, the report will
include all sensors within this group. For detailed information, see
Inherit ance of Set t ings 88 section. For sensors that are added by
tag, all sensor channels are included in the report automatically,
except All nodes is selected in the Clust er Node selection above.
Filter Sensors by Tag
Further filter sensors. This is used in combination with sensors that

are added manually, or added implicitly with their manually added
parent objects. From those sensors, only the ones with the tags
entered here will be included. Enter one or more tags to include
sensors in the report; hit enter, space, or comma to confirm a tag.
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 section Tags 90 for
details.
SCHEDU LE
Report Schedule
Define when the report will be run. Choose between:

No schedule (run int eract ive/on-demand only ): Only use the
options in the Run Now tab to start generation of this report
manually.
Every full hour: Run this report every 60 minutes.
18.11.2014
2303

3 Reports Settings
SCHEDU LE
Every day at a specific hour: Run this report every 24 hours.
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 specific hour is selected above. From

the list, please select the hour you want to run the report at. PRTG
will automatically choose a suitable time within this hour, usually at
the beginning of it.
Specify Day
This setting is only visible if the day of week or day of month

option is selected above. From the list, please select a day of week
or a date of the month you want to run the report. When selecting
Last , the report will always run on the last day of the month,
regardless of how many days the month has. When selecting a
date that does not exist in every month, e.g. the 30th in May, PRTG
will automatically run the report on the last day of this month.
Specify Date
This setting is only visible if the specific date option is selected

above. Please enter a valid date in the form DD.MM, e.g. 31.12. The
report will be run annually on this date.
Scheduled Processing
This setting is only visible if one of the schedule options is

selected above. Define what will be done when generating a
report. Choose between:
Save report t o disk and send it by email: Create a PDF file of
the report, store it, and send it via email. You will find the report
in your emails and in the St ored Report s tab. Define an email
address below.
Save report t o disk only : Create a PDF file of the report and
store it. Once finished, you will find it in the St ored Report s tab
and a ToDo ticket will be created. By default, PRTG will send out a
notification mail to the administrator in this case.
Send report by email only : Create a PDF file of the report and
send it via email once it is finished. The report is not permanently
stored, but only emailed. Define an email address below.
2304
18.11.2014

3 Reports Settings
SCHEDU LE
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 2310 section below.
Email Address
This setting is only visible if a send by email option is selected

above. Please enter a valid email address the report will be sent to.
To enter more addresses, separate them by comma. PRTG will send
a message with all recipients in the "To" field of the email. Note:
Configuration for outgoing email can be changed in the Sy st em
Administ rat ionNot ificat ion Delivery 2372 settings.
Send to User Group

above. From the drop down list, please choose a user group to
send an email with the report to all members of this group (you can
edit user groups under Sy st em Administ rat ionUser Groups 2390
). Note: If you define individual email addresses (see field above)
and a user group, the report will be sent 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. Specify if the attached report files will be compressed
before sending. Choose between:
Uncompressed: The report files will not be compressed before
they are sent by email.
Compressed: The report files will be compressed to a ZIP file
before they are sent by email.
PER IOD
Reported Period
Define the time span covered by the report. 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.
Report Period Type
Define the type of period you want to create a report for. Choose
between:
Day
18.11.2014
2305

3 Reports Settings
PER IOD
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 day period type is selected 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 week period type is selected above.

Define when a week starts and ends. Choose between:
Monday -Sunday : A reported week will start on Monday.
Sat urday -Friday : A reported week will start on Saturday.
Sunday -Sat urday : A reported week will start on Sunday.
Month Period
This setting is only visible if month period type is selected above.

Define when a month starts and ends. Choose between:
1.-last day : A reported month will start on the first and end on
last of the month.
15.-14.: A reported month will start von 15th and end on 14th of
the month.
Year Period
This setting is only visible if year period type is selected above.

Define when a year starts and ends. Choose between:
1/1-12/31: A reported year will start on January 1st.
7/1-6/30: A reported year will start on July 1st.
Report only for specific Include certain time spans within the defined period only. When a
hours-of-day
schedule is selected, only monitoring data for specified hours or
(Schedule)
weekdays within the defined period are included in the report.
Select None to include all available monitoring data in the report,
or choose a schedule. 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
Account Set t ingsSchedules 2353 section.
2306
18.11.2014

3 Reports Settings
PER CENTILE SETTINGS

Show Percentile
Define if percentiles
between:
2615
will be included in the report. Choose
Off: Do not show percentiles

On: Add a column to data tables, showing 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.
Show Percentile
This setting is only visible when showing percentiles. Enter the

percentile number you want to calculate. If you choose, for
example, to calculate the 95th percentile, enter "95" here and 5 %
of peak values will be discarded.
Percentile Average
(seconds)
This setting is only visible when showing percentiles. This is the

averaging interval in seconds, which is used for percentile
calculation. Default value is 300 which is equivalent to 5 minutes.
Percentile Mode
This setting is only visible when showing percentiles. Choose the

mode for percentile calculation:
Discret e: Discrete percentile chooses the next smaller discrete
value.
Cont inuous: Continuous percentile interpolates between
discrete values.
For details, see section Calculat ing Percent iles
2615
R EPOR T COMMENTS
Introduction
Define 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
Define a custom text that will show up on the last page of the
report. Please enter a string or leave the field empty.
18.11.2014
2307

3 Reports Settings
ACCESS R IGHTS
User Group Access
settings.
settings.
Select Sensors Manually

Click on the Select Sensors Manually tab to manually choose sensors that will be included in
the report. You will see a split screen: On the left side, your list of objects is show (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 226 tab. Adding objects to the report is very easy.
2308
18.11.2014

3 Reports 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 will
be added immediately as a new list item. Repeat this procedure as often as you wish until
you have added all desired items to the library. Note: Objects that already exist in the list on
the left side will be grayed out in the device tree on the right side.
Select Sensor Channels
If in the report settings one specific cluster node is selected and if you are adding a sensor
to the selection, you can specify the sensor channels that will be included in the report. By
default, all channels are selected. To exclude a channel from the report, simply remove the
check mark in front of a channel's name. Note: If All nodes is selected in the report's Clust er
Node selection, the channel selection is not available, but only the primary channel of every
sensor is included automatically.
Remove
To remove any objects from the report, click on 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.
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.
18.11.2014
2309

3 Reports Settings
Sensors Selected by Tag

Click on the Sensors Select ed by Tag tab to view all sensors that are added to the report
depending on the report's Add Sensors by Tag setting. In the table list 155 , you will see all
sensors that are added by tag. This is for your information only, you cannot change sensors
here. However, you can switch to the report's Set t ings tab and change the tabs that are used
to add sensors. Additionally, you can also exclude sensors with certain tabs there. The final
report will include both sensors selected manually and those selected by tag.
For sensors that are added by tag, all sensor channels are included in the report automatically,
except All nodes is selected in the report's Clust er Node selection. In this case, only the
primary channel of every sensor is included. 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?
Calculat ing Percent iles
2310
2615
18.11.2014
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
2311
2312
Maps Overview
Maps Rot at ion
2312
2313
Working wit h Maps
2313
Introduction
There are countless possibilities for the implementation of maps. For example, this feature can
be used 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.
19.09.2014
2311
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 can be used 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.
Start Maps
Click the Maps entry from the main menu 183 to view or add custom views of your network's
status and monitoring data. Hover 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 to show other menu items. Follow

the menu path (it is specific to your setup) to select a map.
2314
a new map.
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 on the name of a map to view it.
Click on the Edit button to adjust the settings of this map.
Click on 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.
2312
19.09.2014
Click on the Delet e button to remove this map.

Click on the Add Map button to add a new map.
Map Rotation
To show several maps in a rotation, mark the desired maps using multi-edit 2248 and then select
Map Rot at ion from the multi-edit menu. You will be redirected to a page where the rotation is
shown. 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 2323 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 a map rotation is shown, you can change the refresh interval any time when hovering 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
Maps Designer
2314
2317
Maps Ot her Set t ings
19.09.2014
2323
2313

1 Maps Step By Step
7.11.1 M aps Step By Step

In order to create a new map, follow the steps in this section. In the web interface, click on
Maps entry in the main menu to show the maps main screen.
In this section:
St ep 1: Add Map
2314
St ep 2: Add Map It ems
2315
St ep 3: View and Share
2315
Step 1: Add Map

Click on the Add Map button. An assistant is shown. Enter a Map Name and define Map
Lay out settings (size and optionally a background image). in the Public Access section, define
whether your map will be visible without login.
For detailed information, see Maps Ot her Set t ings
2314
2323
section (Settings).
19.09.2014

1 Maps Step By Step
Add Maps Assistant Step 1
Step 2: Add Map Items

Click on the Cont inue t o st ep 2 button to open the Map Designer. 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
will be added 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 Maps Designer
2317
section.
Step 3: View and Share

Click on the View Map tab to see the appearance of your map. Later, it will be shown the way
you see it there. If available for an object, most object names as well as all sensors can be
clicked on. It depends on the object's access rights and the currently logged in user account if
clicking the links will lead to more detailed information about the object or to an error
message indicating insufficient access rights.
Click on 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 2325 section.
19.09.2014
2315

1 Maps Step By Step
While showing a map, the single map items will be refreshed in the refresh interval defined for
this map.
2316
19.09.2014

2 Maps Designer
7.11.2 M aps Designer

In this section:
Use a Proper Browser
2317
Basic Design Concept
2317
Device Tree Select ion
2318
Propert ies Select ion
2319
Edit Exist ing Map It emsPropert ies Box

Edit Exist ing Map It emsHover Icons
2320
2320
Edit Exist ing Map It emsUsing Cursor Key s

Draw Connect ion Lines Bet ween It ems
Snap To Grid
More
2321
2321
2321
2321
Use a 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 using Google Chrome 38 or later
(recommended) or Mozilla Firefox 33 or later. You can use Microsoft Internet Explorer 10 or 11
as well. The maps designer is not fully compatible with earlier versions of Internet Explorer or
Opera browsers.
Basic Design Concept

Click on the Map Designer tab to open the editor. It might take a few moments to load (for
unresponsive script warnings, please see More 2321 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.
18.11.2014
2317

2 Maps Designer
Map Designer
Each map item takes attributes from both selections.

Device Tree (left): Select the monitoring object which's data will be shown on the map
Propert ies (right): Define how the map item will be shown
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 monitoring object which's data will be shown on the map
(this can be a probe, a group, a device, or a single sensor). In order to find the right object, you
have the following options:
Use the arrow symbols at the beginning of each line to open nodes in the device tree to
show objects underneath 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. The search results will be shown
immediately. Click on the red x icon to clear your search.
No matter which method you choose to find the desired object, you can always drag any
object from the Device Tree on a free area of the map to create a new map item. If you drag it
onto an existing map item, it will be replaced, while Propert ies and size will remain. You can
also select a map item and double click on a Device Tree object to replace the map item. If no
item is selected, a double-click on an object will add 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 left (or to the right to enlarge it again).
2318
18.11.2014

2 Maps Designer
Properties Selection
Use the Propert ies selection to define how the map item will be shown (for example, as an
icon, a map, a table, or a graph). Select the appearance in different categories. Hover 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 hint.
There are many different property object types available. Simply click a category's name to
show all available types.
Icons A, Icons B, Icons C
These three categories offer a variety of iconic symbols of typical network devices. Below
each icon the object name and a sensor overview for the object is shown. This shows how
many sensors are in which state. 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 displayed with them, but only the
icon is shown.
St at ic Maps
This category offers free or public domain geographical maps from different sources. For
additional geographical maps, please see More 2321 section below. Note: The items in this
section are independent from the selected Device Tree objects.
St at us Icons
This category shows options to insert status icons in different styles. These show the
object name and an overview of how many sensors are in which state. 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. Please note that your browser must support playing embedded
sounds (see More 2321 section below for further information).
Geo Maps
In this category you can choose from different geographical map styles from Google: road
map, satellite, hybrid, and terrain maps. The location of the currently selected object in the
Device Tree will be shown on the map as a pin mark. To use this feature, Geo Maps
integration must be enabled 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 Geo Maps 2258
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 shown in this tab are always the
same; the range displayed does not depend on the selected object in the Object field
above.
Dat a Tables
Choose from several tables showing sensor lists for the current selected object. You can
also choose from several lists showing sensors in a certain state only.
18.11.2014
2319

2 Maps Designer
Top 10
Choose from several tables showing the top 10 of sensors with certain monitoring data,
such as least used CPUs, highes bandwidth usage, best availability, slowest websites, etc.
Note: In order to provide live previews, PRTG calculates all top 10 lists from your monitoring
data when opening this tab. It may take a few seconds before thumbnails are shown.
Cust om HTML
This can be used, for example, to add external images or applets to your map. In order to
actually add custom HTML code to your map, please add this item and then click on it to edit
2320 . 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
on a free area of the map to create a new map item. If you drag it onto an existing map item, it
will be replaced, while its Device Tree object attributes and size will remain. You can also
select a map item and double click on an object in the Propert ies box to replace the map
item. If no item is selected, a double-click on 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 right (or to the left to enlarge it again).
Edit Existing Map ItemsProperties Box

Click on a map item to select it. You can then edit its attributes with 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 will be shown on top of or behind another item, if
overlapping. The item with the higher number will be shown on top. Enter a positive integer
value and click the Save button to save your settings. Alternative: Use the arrow symbols in
a map item's hover menu to Bring t o front or Send t o back an item one layer (see below).
HTML
Click on the arrow symbol underneath to show the HTML Before and HTML Aft er fields. Any
HTML code you enter in these fields will be added before respectively after the map item.
Please enter your custom HTML code that embeds an objects and click the Save button.
Your HTML object will be inserted. For example, you could enter the code <img src="http://
media.paessler.com/common/img/logoclaim_r1.gif"> to insert an image of the Paessler logo
from the Paessler website.
Edit Existing Map ItemsHover Icons

Hover 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.
2320
18.11.2014

2 Maps Designer
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 you have drawn connection lines between two items, you can delete all lines starting from
this item. Connection lines will be dropped immediately. Note: If a line between two items is
not dropped, you've probably drawn it starting from the other item. Try the scissors symbol
on the other item instead.
Edit Existing Map ItemsUsing Cursor Keys

While an object is selected, use the cursor keys to move it by one pixel. Hold the Shift key in
combination with the cursor keys to move the object by 10 pixels.
Draw Connection Lines Between Items

You can draw connection lines between any map items via drag and drop. Simply click on the
gray handles next to an item and drag a line to another item you want to draw a connection
to. A line will be shown immediately. This can be useful to indicate network connections or
logical coherences between two items. To delete connection lines, click the scissors symbol in
the item's edit icons 2320 .
Lines between objects are colored dynamically. They will turn red as long as one of the
object's icons shows a red Down status. This will only affect half of the line, at the end where
the red sensor is shown. If both objects connected show a red sensor, this will result in a line
that is red all over.
Snap to Grid
Select whether to use Snap To Grid or Don't Snap, using the buttons underneath the Device
Tree box. This will affect how map items will be 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 Maps Designer?
Knowledge Base: How can I add or edit map objects used for PRTG's maps?
18.11.2014
2321

2 Maps Designer
sound?
Knowledge Base: Where can I find custom map objects and other map customizations?
2322
18.11.2014

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 Maps Designer
section.
2317
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 95
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 88 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!
18.11.2014
2323

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.
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
Background Color
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.
PU BLIC ACCESS
Public Access
2324
Define if others can see the map. Choose between:
18.11.2014

3 Maps Settings
PU BLIC ACCESS
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 using the
default value. For more information on public access, please see
the Get HTML 2325 section. Note: The characters comma "," and
colon ":" are not allowed in the secret key field!
ACCESS R IGHTS
User Group Access
settings.
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 2323 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>.
18.11.2014
2325

3 Maps Settings
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 2323 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 2323 .
needs.
While a map is shown via these URLs, you can change the refresh interval any time by hovering
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 2323 .
Comments
History
entries.
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?
Dat a Report ing
2326
94
18.11.2014
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 2328 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
2401
2416
PRTG St at usLicensing St at us and Set t ings

PRTG St at usAut o-Updat e
2418
2411
Account Settings
Account Set t ingsMy Account
2329
Account Set t ingsNot ificat ions
2334
Account Set t ingsNot ificat ion Cont act s

Account Set t ingsSchedules
2349
2353
System Administration
Sy st em Administ rat ionUser Int erface
Sy st em Administ rat ionMonit oring
18.11.2014
2357
2367
2327
Sy st em Administ rat ionNot ificat ion Delivery

Sy st em Administ rat ionCore & Probes
2379
2385
2390
Sy st em Administ rat ionAdminist rat ive Tools

Sy st em Administ rat ionClust er
2372
2396
2394
Optional Downloads and Add-Ons

DownloadsClient App for Windows (Ent erprise Console)
DownloadsClient Apps for Mobile Devices
DownloadsRemot e Probe Inst aller
2421
2421
2421
2423
Support
Support Cont act Support
2425
Others
There are some settings that you have to make in the Sy st em Administ rat ion Tool 2536 ,
running as Windows application. For more details, please see sections PRTG Administ rat or on
Core Server Sy st em 2537 and PRTG Administ rat or on Remot e Probe Sy st em 2560 .
2328
18.11.2014

1 Account SettingsMy Account
7.12.1 Account SettingsM y Account

In the My Account settings you can define values regarding your own PRTG user currently
logged in. All settings in this section are user specific. Some account control options may not
available, but can only be defined by the administrator.
Note: If you open this system administration page from another administration page and 15
minutes (900 seconds) have passed since your last credential based login, you have to provide
your credentials again for security reasons. A dialog box will appear. Enter your Login Name
and Password for PRTG in the corresponding fields and click on the Login button. You can
continue with your task immediately.
My Ac c ount Settings
My Account Settings
19.09.2014
2329

U SER ACCOU NT
Login Name
Enter the login name for the user.
Display Name
Enter a name for the user for display purposes. This will not be
used for login.
Email Address
Enter the user's email address.
Timezone
Enter the time zone for the current user.
Date Format
Enter in what format dates will be displayed for the current user.
Note: This setting will take effect after the next login.
Password
Define the user's 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 the new password twice.
Note: The new password must be at least 8 characters long; no
character may occur more than 3 times. It must contain a number
and a capital letter.
AU TO R EFR ESH AND ALER TING

Auto Refresh Type
Specify how PRTG's web pages will be refreshed for the current
user. Choose between:
Refresh page element s using AJAX (recommended):
Automatically refresh the single page elements on the web
pages.
Refresh whole page: Automatically reload the whole page with
every refresh interval.
No aut o refresh: Do not automatically refresh web pages.
Auto Refresh Interval

(Sec.)
2330
This setting is only relevant when auto refresh is enabled above.

Enter the number of seconds that will be waited between two
refreshes. We recommend using 30 seconds or more. Minimum
value is 20 seconds. Note: Shorter intervals create more CPU load
on the server running the PRTG core server. If you experience load
problems while using the web interface (or PRTG maps 2311 ), please
set a higher interval.
19.09.2014


Play Audible Alarms
Define when an audible alarm will be played for the current user on
web pages whenever there are alarms 143 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 175 pages only. The sound will
be replayed with every refresh of a 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, please see More 2333 section below.
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.
WEB INTER FACE

Homepage URL
Define the user's default page loaded after login and when clicking
on the Home 175 button in main menu.
Max. Groups/Devices
per Group
In order to provide you with a speedy user experience PRTG tries

to keep the page size for the page showing the device tree small
by automatically folding groups and devices with many items.
Define how many groups and devices are shown at maximum
before the automatic reduction is performed. We recommend using
a value between 10 and 30.
19.09.2014
2331

WEB INTER FACE

Max. Sensors per
Device

Define how many sensors are shown at maximum before the
automatic reduction is performed. We recommend using a value
between 10 and 30.
ACCOU NT CONTR OL
Account Type
This setting is only shown for administrator users. However, it is

not shown if the user you modify the account settings for is a
member of a group with administrative rights.
Define the account type for the current user. Choose between:
Read/Writ e User: The user may change settings.
Read Only User: The user may not edit any settings. This is a
good choice for public or semi-public logins.
Note: This setting cannot be changed for the default administrator
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 144 . Choose between:
Allow: Allow acknowledging alarms for this user.
Deny : The user will not be able to acknowledge alarms.
Primary Group
This setting is only shown 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.
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.
2332
19.09.2014

ACCOU NT CONTR OL
user.
Last Login
Shows the time stamp of the user's last login. This setting is shown
for your information only and cannot be changed here.
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
Notification Contacts
In the Not ificat ion Cont act s 2349 tab you can define recipients for each user account.
Recipients are email addresses, phone numbers, and push devices (Android and iOS devices
with the corresponding PRTG smartphone apps 2486 ).
Comments
History
entries.
More
sound?
19.09.2014
2333

2 Account SettingsNotifications
7.12.2 Account SettingsNotifications

In the notifications settings you can define and change notifications for the currently logged in
PRTG user. They can be triggered for certain sensor states and data.
Notific ation Settings
Note
messages.
2334
18.11.2014

notifications.
2263
section.
Notifications Overview
Click on the Not ificat ions tab to show a list of all existing notifications. Using the links next
to the notification name, you can perform the following actions:
Delet e: Delete this notification (not possible for predefined notifications)
Test : Trigger this notification immediately for testing purposes. Note: When using
placeholders, they will not be resolved in a test notification, but the variables will be sent
instead.
Pause: Pause this notification. If a notification is paused, no messages will be sent when it is
triggered.
Clone: Create an exact copy of this notification. It will be added to the notifications list as
Clone of ...
Used by : Show a list of objects using this notification.
Notifications Settings
Click on the Add new not ificat ion button to add a new notification, or click on the name of
an existing notification to edit it.
BASIC NOTIFICATION SETTINGS

Notification Name
18.11.2014
Enter a meaningful name for the notification, for example, SMS to

service team or similar.
2335

BASIC NOTIFICATION SETTINGS

Tags
Enter one or more tags 90 . 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 are
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 when this notification is active. Select None to set it to be

always active, or choose a schedule from the list. Usually
schedules define when this notification is 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 2353 section.
Postpone
Define if PRTG executes notifications that are triggered during

Paused status later on when the notification is in St art ed status
again.
No: Discard all notification triggers received while the notification
is paused.
Yes: Collect all notification triggers received while the
notification is paused. Send out notifications once the pause
status ends.
NOTIFICATION SU MMAR IZATION

Method
Define if and how PRTG summarizes notifications if several

notification triggers are received in a certain time span. Choose
between:
Alway s not ify ASAP: Always send out one notification for each
received notification trigger as soon as possible.
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.
2336
18.11.2014

NOTIFICATION SU MMAR IZATION

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 here, PRTG executes
notifications of the types Execut e HTTP Act ion and Execut e
Program always ASAP; they can never be summarized.
Subject for
Summarized Messages
Define a subject that PRTG uses 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 define a high value, for example, 60 minutes, PRTG
sends out summarized notifications with a delay of up to one hour.
18.11.2014
2337

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 respective notification type. You can
then see and set the options as described below. The following notification methods are
available:
Email
2339
Push Notification
2340
SMS/Pager Message
2341
Add Entry to Event Log

Syslog Message
2343
SNMP Trap Message

Execute HTTP Action
Execute Program
2344
2345
2345
Amazon SNS Message

Ticket
2338
2342
2346
2346
18.11.2014

Note: In your message, you can use various placeholders. Some are already filled in by default.
For a complete list of available placeholders, see the More 2265 section below.
SEND EMAIL
Note: You can define the email header and footer in the Sy st em Administ rat ion
Not ificat ion Delivery 2372 settings.
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 2350 .
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.
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 2350 . 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 each email
contact of every member of this group. You can edit user groups
under Sy st em Administ rat ionUser Groups 2390 and email
contacts under Account Set t ingsNot ificat ion Cont act s 2350 .
Choose None to not use this feature.
Note: If you select a user group and a specific member of this
group as recipients at the same time, this user receives the email
only one time. This also counts 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), 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.
Send to Email Address
18.11.2014
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.
2339

SEND EMAIL
We recommend you to 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 2347 (variables) are used here by default: [%
sitename] %device %name %status %down (%message)
Format
Define the kind of email that PRTG sends. Choose between:

Text : The message part of the email is plain text.
HTML: The message part of the email is HTML encoded.
Message
Depending on the format option you select above, you see a text
or HTML message in this field. A complete message about the
sensor status is already predefined, including placeholders. You
can change it to your liking. To reset this field to its default value,
enter a single star symbol * (and nothing else) or click on the
trashcan symbol (Reset t o default ) next to the text box.
Priority
Define the priority that PRTG sets for the email. Most email clients
can show this priority flag.
SEND PU SH NOTIFICATION
Note: Push notifications work only with the apps PRTG for Android 2486 and PRTG for iOS 2486
. You have to activate push notifications in the settings of your app first. Please see section
More 2347 for details about the setup and further information.
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.
2340
18.11.2014

SEND PU SH NOTIFICATION
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 2350 and add push
contacts by activating push notifications in the Android or iOS app
with this user. Choose None to not use this feature.
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 2390 and push contacts
under Account Set t ingsNot ificat ion Cont act s 2350 . 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 2347 (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).
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 2372 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 2379 (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.
18.11.2014
2341

SEND SMS/PAGER MESSAGE

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 2350 . 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 2390 and SMS
contacts under Account Set t ingsNot ificat ion Cont act s 2350 .
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 you to 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.
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.
2342
18.11.2014

ADD ENTR Y TO 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
Define the IP address or DNS name of the computer running the

syslog server.
Note: You can receive and analyze syslog messages with the
Sy slog Receiver Sensor 1760 .
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

18.11.2014
2343

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 2347 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 1621 .
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.
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.
2344
18.11.2014

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 2379 (section
Proxy Configurat ion).
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
Enter postdata if you want to send this data to the URL. You can
use placeholders 2347 here. Line breaks are supported.
EXECU TE PR OGR AM
notifications of the type Execut e Program always as soon as possible (ASAP). They are
never summarized.
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 the probe
system's PRTG installation. To appear in this list, store the files as
BAT, CMD, DLL, EXE, PS1, or VBS. To find the corresponding path,
please see Dat a St orage 2611 section.
Note: In a cluster setup, copy your files to every cluster node
installation manually. This makes sure the notification can be
executed 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 2571 for detailed information.
Parameter
18.11.2014
Enter parameters with which the program file will be started. You
can use placeholders 2347 here. For example, is you use a batch file
that contains a %1 variable, you can provide a value for this variable
here.
2345

EXECU TE PR OGR AM
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.
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.
ARN
Enter the Amazon resource name. Please enter a string.
Subject
Enter the subject of the message. Please enter a string.
Message

2346
18.11.2014

ASSIGN TICKET
notifications of the type Assign Ticket always as soon as possible (ASAP). They are never
summarized.
For details about the ticket system, please see section Ticket s
Assign to User or User
Group
148
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.
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
2347 (variables) are used here. You can change it to your liking.
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
141
section.
More
2571
18.11.2014
2347

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?
2348
18.11.2014

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. Notification contacts provide the information to which recipient
PRTG can send notifications 2263 . Recipients of notifications can be email addresses, phone
numbers, and push devices (these are Android 2486 or iOS 2486 devices with the corresponding
PRTG app). This way, every user of a PRTG installation can define dedicated ways how and
where to receive messages from PRTG.
When you set up one of the notification methods 2338 Send Email, Send SMS/Pager Message,
or Send Push Notification, you can choose a PRTG user to send a notification 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
messages.
notifications.
18.11.2014
2263
section.
2349

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:
Edit : Change the description and recipient of this notification. 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 2329 .
Pause: Pause this notification contact. If a notification contact is paused, PRTG does not send
any messages to this contact when a notification for this user is triggered.
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 on the Add email cont act or on the Add SMS cont act button to add a new notification
contact, or click on 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 as soon as you
activate push notifications in a PRTG mobile app with this user account. You cannot add push
contacts manually.
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 section More 2351 .
Contact Type
Shows the type of contact, either Email, SMS, or Push. This setting
is shown for your information only and cannot be changed here.
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 Android or iOS app.
Click on the Save resp. Add button to store your settings, or click on Cancel to close the
dialog box without changes to your configuration.
2350
18.11.2014

More
Knowledge Base: How can I use push notifications with PRTG?
SetupTopics
2329
2334

2349
2353

2357
2367

2379
2385
2390
2394

PRTG St at usAut o Updat e
2401
2416
PRTG St at usAct ivat ion St at us
2418
2421
2423
18.11.2014
2396
2411
Downloads and Add-Ons
2372
2425
2351

Others
There are some settings that you have to make in the PRTG Administ rat ion Tool
available as native Windows application. For more details, please see sections:
PRTG Administ rat or on Core Server Sy st em
2537
PRTG Administ rat or on Remot e Probe Sy st em
2352
2536
2560
18.11.2014

4 Account SettingsSchedules
7.12.4 Account SettingsSchedules

In the schedules settings you can define and change schedules for the currently logged in
user. You can use schedules to pause 162 monitoring/notifying at certain times with the period
lists option, respectively activate it at certain times with the time table option. You can also use
schedules to define the time spans that are to be covered when creating reports 2291 .
Sc hedules Settings
Schedules Settings
Click on the Schedules tab to show a list of all existing schedules. Using 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.
19.09.2014
2353

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 purpose.
Edit Mode
Select how you want to define a schedule. Choose between:

Use weekday /hour t ime t able: Define a schedule with available
checkboxes. Lowest increment is one hour. Note: The time table
defines active time slots.
Use list of period definit ions: Define a schedule by entering
text lines using a specific syntax (see below). Note: The period
list defines inactive time slots.
2354
19.09.2014

BASIC SETTINGS
Time Table
This selection is only visible if the time table option is 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 hour by setting 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 2356 below.
ACCESS R IGHTS
User Group Access
settings.
settings.
19.09.2014
2355

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 of 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, please see Object Set t ings
2356
141
section.
19.09.2014

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 will influence the
language of the Ajax 100 and the Mobile Web GUI 2483 web
interfaces, as well as of the PRTG Administ rat or Tool 2536 .
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 2430 , or of Smart phone Apps 2486 will be
disconnected. After clicking on the Save 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.
Graph Type
Select how graphs will be displayed throughout the web interface

and in reports 2291 .
Use area chart s (recommended): Display filled graphs.
Use line chart s: Display graphs using single lines only.
19.09.2014
2357

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 charts 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 141 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.
2358
19.09.2014

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 v2 key to use this service. Note: As of PRTG version 13
you will need to acquire a Google Maps API v3 key!
For more information about the different map providers, please see
the More 2365 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
2365 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 into PRTG by
simply pointing your browser to the specified IP address.
Choose between:
19.09.2014
2359

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
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.
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.
the screen.
TCP Port for Web
Server
2360
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:
19.09.2014

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 105 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 2613 .
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.
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.
the screen.
Web Server Port
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.
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.
the screen.
19.09.2014
2361

WEB SER VER

Web Server Security

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.
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.
the screen.
SSL Security
Specify the security level which will be used for SSL connections
from and to the PRTG web server. Choose between:
High securit y (recommended): The web server will only accept
high security connections from clients like web browsers, apps
2486 , the Ent erprise Console 2430 , 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 you to
update your clients in this case. For details about how to do this
with the Enterprise Console, see section More 2365 .
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
shown for your information only and cannot be changed here.
Note: PRTG internally uses port 8085 for report generation.
2362
19.09.2014

GR APH SETTINGS: SELECT FOR HOW MANY DAYS HISTOR IC DATA R EMAINS
ACCESSIBLE
PRTG shows several graphs in the objects' detail pages 124 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 100 and Enterprise Console 2430 .
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 2430 , or of Smart phone Apps 2486
will be disconnected. After clicking on the Save 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.
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.
19.09.2014
2363

ACCESSIBLE
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.
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.
2364
19.09.2014

ACCESSIBLE
750 day s wit h 1 day averages: Results in 750 values. Uses
most RAM memory.
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"
Knowledge Base: Enterprise Console connection failure error in content: What can I do?
19.09.2014
2365

Knowledge Base: How can I integrate Google Analytics in PRTG?
2366
19.09.2014

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 141 . 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 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 not to use intervals shorter than 10 seconds
to prevent system overload. Intervals below 10 seconds are not
officially supported!
20.11.2014
2367

U NU SU AL DETECTION
The unusual detection can set sensors to an Unusual status 121 when there are values that
are untypical for the time span they're measured in, compared to historic monitoring results.
When disabled (both settings to Never), sensors will never be shown as unusual. Note: You
can enable and disable unusual detection for any object (e.g. for a device, or an entire
group) in the Object Set t ings 141 .
Show Unusual When
Define when a sensor will be shown as unusual, comparing the

weekday. Choose between:
Never: Disable unusual detection for weekday average.
24h average is <80% or >120% of weekday average
(recommended)
24h average is <10% or >1,000% of weekday average
24h average is <1% or >10,000% of weekday average
Show Unusual When
Define when a sensor will be shown as unusual, comparing the

hour-of-day. Choose between:
Never: Disable unusual detection for hour-of-day average.
24h average is <80% or >120% of hour-of-day average
(recommended)
24h average is <10% or >1,000% of hour-of-day average
24h average is <1% or >10,000% of hour-of-day average
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
2368
20.11.2014

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.
R ECOMMENDED SENSOR S DETECTION

With the sensor recommendation service, you can automatically analyze the devices which
you add to PRTG for useful but missing sensors. PRTG can show you sensor types 124 that
give you a much more detailed picture about your network when you monitor the
respective devices with them. The analysis runs with low priority in background when you
add a new device, the last analysis has been 30 days ago, or you click Recommend Now in
the context menu of a device 168 or on a device overview tab 124 . When the analysis is
finished for a device, suggested sensor types appear in the Recommended Sensors table
list on the device overview tab. You can add them directly to the device with the Add
Sensors button.
Note: The recommended sensors detection cannot run at the same time as Aut o-Discovery
194 . PRTG gives auto-discovery a higher priority, for example, when you add a new device,
and queues the sensor recommendation in this case.
20.11.2014
2369

R ECOMMENDED SENSOR S DETECTION

Detection Engine
Define if you want PRTG to analyze your devices to recommend

useful sensor types. Choose between:
Suggest recommended sensors (recommended): PRTG
analyzes your devices automatically to recommend useful sensor
types. We recommend you to set this option to not miss any
important data about your network.
Note: You can manually start the analysis for a device with
Recommend Now in the context menu 168 or on the overview
tab 124 .
Turn recommendat ions off: PRTG does not recommend
sensors. Select this option if you have issues with the
performance of PRTG or do not want to see this information on
device overview tabs 124 . Also you will not have the option
Recommend Now in device context menus 168 or on overview
tabs.
AU TO-DISCOVER Y SETTINGS
Run Discovery at
Define the time when PRTG automatically runs an Aut o-Discovery

194 in your network if you configured a daily or weekly Discovery
Schedule in the auto-discovery group settings 196 . Choose a full
hour between 0:00 and 23:00. We recommend you to choose a
time when there is little user activity in your network, because
auto-discoveries can produce a certain amount of load.
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 %.
2370
20.11.2014

More
20.11.2014
2371

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
messages.
notifications.
2263
section.
Notification Delivery Settings

2372
19.09.2014

EMAIL OPTIONS
Email Templates
Choose which templates will be used for all emails sent.

Use st andard email t emplat es (Recommended): Use this
option if you are not sure what to use. These templates offer the
best compatibility with all email clients.
Use t emplat es from previous version (for upgrade
inst allat ions from V7 only ): This option is provided for update
installations from V7 only. Use it if you have updated from PRTG
version 7 and really want to continue using the old email
templates. This can be useful when using custom HTML
templates in PRTG 7 format.
Depending on the option selected, the content of the other fields
in this section changes.
Email Header (HTML)
Define the HTML text that will be used as the header for each HTML
mail. To reset this field to its default value, click on the trash can
icon left to the field or enter a single star symbol * (and nothing
else).
Email Footer (HTML)
Define the HTML text that will be used as a suffix to every HTML
mail. To reset this field to its default value, click on the trash can
icon left to the field or enter a single star symbol * (and nothing
else).
For Text Mails
Select if a footer will be added to plain text mails. Choose

between:
Append t ext foot er (default ): Add a text footer to all text
mails. Define the text below.
Do not append t he foot er Append t ext foot er: Do not add a
footer to text mails.
Email Footer (Text)
Define a text that will be used as a suffix to every plain text mail (if
enabled above). You can use several placeholders in email
templates. See the More 2365 section below for more information.
To reset this field to its default value, click on the trash can icon
left to the field or enter a single star symbol * (and nothing else).
SMTP DELIVER Y
SMTP Delivery
Mechanism
19.09.2014
Define how mails are sent using Simple Mail Transfer Protocol
(SMTP). Choose between:
2373

SMTP DELIVER Y
Direct delivery using built -in mail relay server (default ): Use
the SMTP relay server built into PRTG. This server manages its
own email queue. For each email, it will look 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 that will be used as sender of all emails. This
setting is global and can only be changed centrally here.
Sender Name
Enter a name that will be used 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 SMTP relay server is enabled above. Enter
the IP address or DNS name of the SMTP relay server.
SMTP Relay SMTP Port
This field is only visible if SMTP relay server is enabled above. Enter
the port number the SMTP relay server is running on. Standard
value is 25.
SMTP Relay
Authentication
This field is only visible if SMTP relay server is enabled 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.
SASL aut hent icat ion is required: Use secure authentication via
Simple Authentication and Security Layer (SASL).
2374
19.09.2014

SMTP DELIVER Y
SMTP Relay Username

Enter a valid user name.
SMTP Relay Password

Enter a valid password.
Use Encrypted
Connection
This field is only visible if SMTP relay server are enabled above.
Enter 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 SMTP relay server and encryption are
enabled above. It is only relevant for secure connections. Select
the SSL or TLS version which is supported by your SMTP device.
We recommend using the default value. If you do not get a
connection, try with another setting.
SMTP Relay Server

(Fallback)
SMTP Relay SMTP Port
(Fallback)
SMTP Relay
Authentication
(Fallback)
Use Encrypted
Connection (Fallback)
SSL Method (Fallback)
These fields are only visible if the option for two SMTP relay
servers is enabled above. Please see respective settings for
primary SMTP relay server above.
SMTP Relay Username

(Fallback)
SSL Method (Fallback)
SMTP Relay Username
(Fallback)
SMTP Relay Password
(Fallback)
19.09.2014
2375

SMTP DELIVER Y
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
2377 section below.
Configuration Mode
Define how you want to select an SMS provider. Choose between:

Select a 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 2377 section below for more
information.
Username
This field is only visible if the provider list is enabled above. Enter a
user name for the service provider account.
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.
2376
19.09.2014

SMS DELIVER Y
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 2334 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 2379 (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?
Knowledge Base: How can I enable Notification Delivery Logging?
19.09.2014
2377

2378
19.09.2014

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 and/or mini probes.
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 according
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 2411 , Act ivat e t he
Product 60 , obtaining Geo Maps 2258 tiles, and for sending out HTTP
and SMS text message Not ificat ions 2338 .
Proxy Server
This setting is only visible if proxy usage is enabled above. Enter

the address of the proxy server that will be used for outbound
connections. Please enter a valid address.
Port
This setting is only visible if proxy usage is enabled above. Enter

the port of the proxy server that will be used for outbound
connections. Please enter an integer value.
Use Proxy Credentials
This setting is only visible if proxy usage is enabled above.

Determine whether the proxy server needs credentials. Choose
between:
Yes: Define credentials below.
26.09.2014
2379

PR OXY CONFIGU R ATION

No: Do not use credentials for proxy connections.
Username
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
Shows on which IP addresses the PRTG core server accepts

incoming probe connections. This setting is shown for your
information only and cannot be changed here. If you need to
change this setting, please use the PRTG Administ rat or on Core
Server Sy st em 2541 .
Probe Connection Port
Shows on which TCP port the PRTG core server accepts incoming
probe connections. This setting is shown for your information only
and cannot be changed here. If you need to change this setting,
please use the PRTG Administ rat or on Core Server Sy st em 2541 .
Access Keys
Enter a list of access keys, one in each line. Every (remote) probe
that wants to connect to this PRTG installation has to use one of
these keys. For information how to set this key for a probe, please
see PRTG Administ rat or 2561 section.
Allow IPs
Enter a list of remote probe IPs that will be accepted when

connecting to this PRTG installation; each IP address in one 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 Define IP Ranges 2578 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!
2380
26.09.2014


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
Enter a list of remote probe IPs that will not be accepted when
connecting to this PRTG installation; each IP address in one 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 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 Define
IP Ranges 2578 section).
Deny GIDs
Enter a list of GIDs, each global ID (GID) in one 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 must set you PRTG web
server to accept connections of Mini Probes here and choose the
secure HTTPS server option in the web server settings 2359 . 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 2359 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 2571 for the full Mini Probe
documentation. See also section More 2384 for more information
about PRTG Mini Probes.
26.09.2014
2381


the screen.
Mini Probe Port
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.
the screen.
ACTIVE DIR ECTOR Y INTEGR ATION

Domain Name
In order to use Act ive Direct ory Int egrat ion 2569 please enter the
name of your local domain. Please enter a string or leave the field
empty.
Access Type
Define which user account will be used to configure Active

Directory access. This account will be used 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 you should
not use this option.
Use explicit credent ials: Define a user account that will be
used by PRTG to authenticate against the Active Directory. This
should be a user account with full access to all of your Active
Directory groups.
2382
26.09.2014

ACTIVE DIR ECTOR Y INTEGR ATION

Access User
This field is only visible if the use of explicit credentials is chosen

above. Enter the Windows user account name which will be used
to authenticate for Active Directory configuration.
Access Password
This field is only visible if the use of explicit credentials is chosen

above. Enter the password for the Windows user account which
will be used to authenticate for Active Directory configuration.
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 Dat a St orage 2611 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. 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 will be 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 will be kept for all
sensors. It is used to create reports 2291 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 2502 and Packet Sniffer 2500
sensors will be kept. Enter a value in days. We recommend using
30 days here.
Closed Tickets
Define how long tickets which are in status closed will be kept.
Enter a value in days.
26.09.2014
2383

HISTOR IC DATA PU R GING LIMITS: SELECT FOR HOW MANY DAYS HISTOR IC
DATA R EMAINS ACCESSIBLE
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 will be 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 604 (PhantomJS browser engine) will be kept. Enter a value
in days. PRTG will delete older screenshots with every sensor scan.
Remote Probe Setup

Find more information about setting up remote probes in the Mult iple Probes and Remot e
Probes 2588 section.
More
Define IP Ranges
2578
Knowledge Base: Where can I find PRTG Mini Probes which are ready to use?
2384
26.09.2014

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 user name. The available
setting options are the same as shown in the My Account 2329 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 2390 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 2390 and give access to this group in your device tree object's
settings 141 .
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 for the user for display purposes. This will not be
used for login.
19.09.2014
2385

U SER ACCOU NT
Email Address
Enter the user's email address.
Timezone
Enter the time zone for the current user.
Date Format
Enter in what format dates will be displayed for the current user.
Note: This setting will take effect after the next login.
Password
Define the user's 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 the new password twice.
Note: The new password must be at least 8 characters long; no
character may occur more than 3 times. It must contain a number
and a capital letter.

Auto Refresh Type
Specify how PRTG's web pages will be refreshed for the current
user. Choose between:
Refresh page element s using AJAX (recommended):
Automatically refresh the single page elements on the web
pages.
Refresh whole page: Automatically reload the whole page with
every refresh interval.
No aut o refresh: Do not automatically refresh web pages.
Auto Refresh Interval

(Sec.)
This setting is only relevant when auto refresh is enabled above.

Enter the number of seconds that will be waited between two
refreshes. We recommend using 30 seconds or more. Minimum
value is 20 seconds. Note: Shorter intervals create more CPU load
on the server running the PRTG core server. If you experience load
problems while using the web interface (or PRTG maps 2311 ), 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 143 in PRTG. Choose
between:
2386
19.09.2014


Never: Do not play sound files on any web pages.
On dashboard pages only : When there are alarms, play a
predefined sound on dashboard 175 pages only. The sound will
be replayed with every refresh of a 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, please see More 2333 section below.
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.
WEB INTER FACE

Homepage URL
Define the user's default page loaded after login and when clicking
on the Home 175 button in main menu.
Max. Groups/Devices
per Group

Define how many groups and devices are shown at maximum
before the automatic reduction is performed. We recommend using
a value between 10 and 30.
19.09.2014
2387

WEB INTER FACE

Max. Sensors per
Device

Define how many sensors are shown at maximum before the
automatic reduction is performed. We recommend using a value
between 10 and 30.
ACCOU NT CONTR OL
Account Type
This setting is only shown for administrator users. However, it is

not shown if the user you modify the account settings for is a
member of a group with administrative rights.
Define the account type for the current user. Choose between:
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 144 . Choose between:
Allow: Allow acknowledging alarms for this user.
Deny : The user will not be able to acknowledge alarms.
Primary Group
This setting is only shown 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.
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.
2388
19.09.2014

ACCOU NT CONTR OL
user.
Last Login
Shows the time stamp of the user's last login. This setting is shown
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
Notification Contacts
In the Not ificat ion Cont act s 2349 tab you can define recipients for each user account.
Recipients are email addresses, phone numbers, and push devices (Android and iOS devices
with the corresponding PRTG smartphone apps 2486 ).
Comments
History
entries.
More
sound?
19.09.2014
2389

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 2390 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).
By default, there aren't any rights set for a newly created PRTG user group. Initially, users in
this group will not see any objects in the PRTG device tree. Please edit your device tree
object's settings 141 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 228 .
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!
User Groups Settings

2390
19.09.2014

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 141 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
2569 .
No: Do not use Active Directory integration for this group, but
choose local user accounts instead.
Active Directory Group
If a valid Active Directory Domain is set in the Sy st em

Administ rat ionCore & Probes 2382 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
2569 .
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.
19.09.2014
2391

U SER GR OU P SETTINGS
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:
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 148 . Choose between:
Members can use t he Ticket Sy st em: No restrictions for group
members are applied.
Members can NOT use t he Ticket Sy st em: The Ticket s 185
option in the main menu bar 185 will not be visible to users in this
group.
MEMBER S
Members
2392
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 user name. The user accounts available depend
on your setup.
19.09.2014

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 2385 .
Comments
History
entries.
19.09.2014
2393

11 System AdministrationCluster
7.12.11 Sy stem AdministrationCluster

In the cluster settings you can define the cluster settings. During Failover Clust er
Configurat ion 2602 , the cluster settings were already pre-defined. See the cluster status
see if all nodes in your cluster are properly connected.
2416
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 using 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 2416 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 IP address that the second cluster member (this is a
failover node) will use to connect to the master node server.
2394
19.09.2014

11 System AdministrationCluster
In order to put a cluster node to Maint enance Mode, please see PRTG St at usClust er
St at us 2416 .
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 2602 section.
19.09.2014
2395

12 System AdministrationAdministrative Tools
7.12.12 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
2396
19.09.2014

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 2611 . If you're running a PRTG
cluster, this action is executed on the cluster node you're 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 2611 . If you're running a PRTG cluster, this action is
executed on the cluster node you're 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 2258 and user data for Act ive
Direct ory Int egrat ion 2569 . 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 2579 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.
19.09.2014
2397

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 2430 , or of Smart phone Apps
2486 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
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 respective Probe Set t ings 259 .
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 2611 . 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 2588 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're running a PRTG cluster, this action is
executed on the cluster node you're 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.
2398
19.09.2014

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
2329
2334

2349
2353

2357
2367

2379
2385
2390
2394

PRTG St at usAut o Updat e
2401
2416
PRTG St at usAct ivat ion St at us
2418
2421
2423
19.09.2014
2396
2411
Downloads and Add-Ons
2372
2425
2399

Others
There are some settings that you have to make in the PRTG Administ rat ion Tool
available as native Windows application. For more details, please see sections:
2537
2400
2536
2560
19.09.2014

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:

2401
2416
System Status
Click on the Sy st em St at us tab to view relevant system information you may need for
debugging or when the support team asks you to provide system information in order to
support you with PRTG.
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 2411 . 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're running 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're running 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're running a PRTG cluster, this will show
logged in to.
18.11.2014
2401

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.
2329
of the PRTG user you're currently logged
LICENSING
Licensee
Shows the name of the license 57 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 57 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 60 .
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 121
automatically. To upgrade your license right now, click on the
Need more sensors? Click here t o upgrade! button to visit our
web shop.
2402
18.11.2014

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 20,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're
running a PRTG cluster, this will show information for the system of the cluster node you're
currently logged in to.
CLU STER STATU S

This box is only visible if you're running a PRTG cluster. This section lists all cluster nodes
configured in your monitoring.
Node [Number]
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 2416 page.
LOCAL STATU S
This box is only visible if you're running a PRTG cluster. This section lists information about
the cluster node you're currently logged in to.
Server State Cluster
Messages
18.11.2014
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.
2403

CLU STER CONNECTIONS

This box is only visible if you're running 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.
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 2502 or Packet Sniffer 2500 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.
2404
18.11.2014

BACKGR OU ND TASKS
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 current status and the selected setting for the analysis
depth of the Similar Sensors 137 analysis.
DATABASE OBJECTS
Shows statistic information about your monitoring configuration. This information might be
necessary when contacting Paessler's technical support staff.
Probes
Shows the total number of probes
244
configured.
Groups
Shows the total number of groups
262
in your configuration.
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
18.11.2014
2385
284
304
2390
configured.
2291
2353
2334
configured.
configured.
2311
in your installation.
2275
2405

DATABASE OBJECTS
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. 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 304 for sensors with high and very high performance 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 304 for sensors for more information.
Note: In the list, internal short names are used for sensor types instead of the official
designations.
2406
18.11.2014

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're running 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're 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]"
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 2396 .
SYSTEM SETTINGS
Web Server URL
Shows the URL to access the PRTG web interface 100 . If you're
running a PRTG cluster, this will show information for the system of
Web Server IPs
Shows all IP addresses the PRTG web server is running at. If you're
running a PRTG cluster, this will show information for the system of
Web Server Ports
Shows the port the PRTG web server is running at. If you're running
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.
Incoming Probe
Connection Binding
Shows a combination of the two values below.
Incoming Probe
Connection 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 ion
Core & Probes 2379 settings. 0.0.0.0 means that the core server
listens on all local network adapter IPs.
18.11.2014
2407

SYSTEM SETTINGS
Incoming Probe
Connection Port
Shows the port number 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 2379 settings. Default port is 23560.
Probe Allow IPs
Shows all source IP addresses that will be accepted by the core

server for incoming remote probe connections. This is the same
Probes 2379 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
Shows all source IP addresses that will be denied by the core

server for incoming remote probe connections. This is the same
Probes 2379 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 83 .
DataPath
Shows the path where PRTG stores its configuration, monitoring

database, etc. If you're running a PRTG cluster, this will show
logged in to. In order to change this setting, please open the PRTG
Administ rat or 2537 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're running a PRTG cluster, this will show information
for the system of the cluster node you're currently logged in to.
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.
2408
18.11.2014

WEB SER VER ACTIVITY

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're
running a PRTG cluster, this will show information for the system of the cluster node you're
currently logged in to. 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.
18.11.2014
2409

SYSTEM WAR NINGS

If there are any warnings they will be shown here. Usually "None" will be shown here.
COR E SYSTEM MEMOR Y

Shows machine-oriented information regarding the memory usage of the core server
system. If you're running a PRTG cluster, this will show information for the system of the
THR EAD INFOR MATION

Shows machine-oriented information regarding the threads running on the core server
system. If you're running a PRTG cluster, this will show information for the system of the
More
Paessler Website: Detailed System Requirements for PRTG Network Monitor
http://www.paessler.com/prtg/detailed-requirements
2410
18.11.2014

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
administrator will then receive a ToDo ticket 149 with instructions to initiate the update
installation.
For customers using a Freeware or Trial Edition 19 , automatic software updates are available at
any time. Customers using a Commercial Edition 19 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 | Soft ware Aut oUpdat 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! A summary of current and past release notes is given
underneath update section; for detailed release notes, click on the button PRTG Release
Not es and Version Hist ory which will redirect you to the corresponding page on
paessler.com.
In order to install an available version, click the Inst all Updat e [version number] button. You
will be asked to confirm installation and licenseand that's it!
19.09.2014
2411

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: In order 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 2415 section below.
In order to change the release channel you receive updates from, please open the auto-update
Set t ings 2413 tab by clicking on the Select Ot her Release Channel button and change the
settings in the Release Channel section.
2412
19.09.2014

Log
Click on the Log tab to show log information regarding the update status of PRTG, newest
first. In the table list 155 appearing, you can filter the items by using the respective options 155 .
For more information, please see Logs 146 section.
Settings
Click on the Set t ings tab to configure the Soft ware Aut o-Updat e.
SOFTWAR E AU TO-U PDATE

When a New Version is
Available
Define how PRTG will react to available software updates. Choose

between:
Aut omat ically download and inst all t he lat est version: Any
new PRTG version will be downloaded and installed automatically
as soon as your installation detects that there is a newer version
available (a check is performed once per day). Note: Without
prior notice, installation 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: Any new PRTG version will be downloaded automatically
as soon as your installation detects that there is a newer version
available (a check is performed once per day). After successful
download, PRTG will create a ToDo message for the
administrator.
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 message only. You can still download updates
manually on the Aut o Updat e 2412 page.
Installation Time
If you have select the automatic installation option above, choose

the desired time for 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!
19.09.2014
2413

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.
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 2365 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 2379 settings. For details about the update servers, see
During installation the core server may be restarted without notice.
Existing remote probes will be updated 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 on the system(s)
running the remote probe(s).
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 2430 , an update has to be initiated and confirmed
for each single core server.
You can disable automatic downloading in the Aut o-Updat e set t ings 2413 . Updates will then
only be downloaded on request, when you click on the Check For Lat est Updat e and
Download button.
2414
19.09.2014

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"
http://www.paessler.com/blog/2012/04/25/news/prtg-12-introduces-continuous-rollout
19.09.2014
2415

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:

2401
2416
Cluster Status
Click on the Clust er St at us tab to view all nodes connected to the cluster. This tab is only
available if you're running PRTG in cluster mode 81 . Following information is shown:
Cluster Status with all connected nodes as table and graphic
Cluster Log with all log entries concerning cluster connections
2416
19.09.2014

15 PRTG StatusCluster Status
Example of a PRTG Cluster Status View
Click on 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 on 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're reconfiguring things, etc. During maintenance, a cluster node is
displayed with a transparent color in the overview graphic.
For more information about cluster settings, please see Sy st em Administ rat ionClust er
section.
19.09.2014
2394
2417

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 | Ent er License Key from the main menu. Click on 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
2418
2419
Your LicenseEnt er License Key
2419
Status
Click on the St at us tab to view information about your license.
LICENSING
Licensee
Shows the name of the license 57 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 57 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).
2418
18.11.2014

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 60 .
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 121
automatically. To upgrade your license right now, click on 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 20,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 60 section.
SOFTWAR E LICENSE
License Name
18.11.2014
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.
2419

SOFTWAR E LICENSE
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.
2420
18.11.2014

17 Optional Downloads and Add-Ons
7.12.17 Optional Downloads and Add-Ons

To see optional downloads, select Set up | Downloads / Add-Ons from the main menu. Click
on the tabs to switch between different options.
Downloads / Add-Ons Tabs
There are the following downloads available:

Client App for Windows (Enterprise Console)
Remote Probe Installer
PRTG Add-Ons
2421
2421
2421
2421
PRTG Billing Tool
2422
2422
Client App for Windows (Enterprise Console)

Download the Windows Graphical User Interface (GUI) "Enterprise Console" to the current
system. Using it, you can access the PRTG interface with a native Windows application. The
version of the Enterprise Console must match your version of PRTG. For more information,
please see Inst all t he Ent erprise Console 67 section.

PRTG for iOS is a native iPhone application that enables you to use the PRTG web interface
with the original iFeeling. You can download PRTG for iOS on iTunes for free. PRTG for Android
gives you the possibility to monitor PRTG on the go with your Android device, available for free
as well. There are also apps available for Windows Phone and BlackBerry. For more information,
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 62 section.
PRTG Add-Ons
This will display a link to the PRTG add-ons page on Google Code. There you will find a
collection of various add-ons for PRTG Network Monitor and their source code. For more
information, please see More 2422 section below.
19.09.2014
2421

17 Optional Downloads and Add-Ons
PRTG Billing Tool

This will display a link to information and download of the PRTG Billing Tool. The PRTG Billing
Tool is an application that can read PRTG sensor data and generate bills in PDF format. We
provide this tool as a basis to develop your own billing applications. For more information,
This tab is only visible if you're accessing the PRTG web interface with Google Chrome or
Firefox browser. For details, please see Deskt op Not ificat ions 2423 section.
More
Paessler Website: Smartphone Apps for PRTG
http://www.paessler.com/apps
Project Hosting on Google Code: PRTG AddOns
http://code.google.com/p/prtg-addons/
Paessler Website: Billing Tool for PRTG
http://www.paessler.com/tools/billingtool
2422
19.09.2014

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 use it to show notifications on your desktop whenever there are new alarms in your
monitoring.
Desktop notifications will be shown (by default, in the lower right corner of your desktop)
whenever there are new alarms after a page refresh. The notification will display the number of
new alarms and the current number of each sensor status. Click on X to close the notification.
Example of a Chrome Desktop Notific ation
In your browser's default configuration, you have to initially allow those notifications for each
installation/profile of Firefox or Google Chrome. To do so, in the PRTG web interface, please
click on Set up 2327 , then click on Deskt op Not ificat ions.
Desktop Notific ations in Setup
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 on the Enable Deskt op Not ificat ions button to add your PRTG URL to Chrome's resp.
Firefox's list of allowed sites for desktop notifications.
On top of your browser window a message will appear, asking you to allow desktop
notifications.
In Chrome, click on Allow to add the web interface's URL to the allowed sites.
In Firefox, click on Alway s Show Not ificat ions to add the web interface's URL to the
allowed sites.
Clic k on 'Allow' to enable Chrome Desktop Notific ations
19.09.2014
2423

18 Desktop Notifications
Clic k on 'Alway s Show Notific ations' to enbale Firefox Desktop Notific ations
St at us: Sorry , Deskt op Not ificat ions cannot be enabled

Desktop Notifications are explicitly blocked for the PRTG web interface's URL in the browser
options. Please see section Disabling or Re-Enabling Desktop Notifications 2424 below.
Deskt op Not ificat ions enabled
Desktop Notifications are successfully activated. In order to disable them, please see
Disabling or Re-Enabling Desktop Notifications 2424 below.
Disabling or Re-Enabling Desktop Notifications

To disallow or re-allow your web interface's URL for desktop notifications, please edit your
browser options:
In Google Chrome: Choose Opt ions from the main menu and show the advanced opt ions.
In the Privacy section, click on the button Cont ent set t ings.... In the Not ificat ions
section, change settings corresponding to your needs. For example, click on Manage
except ions... and remove the URL of your PRTG web interface to disable the feature. Or
remove a blocked URL to re-enable the feature again.
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.
2424
19.09.2014

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 in order 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 the support team a lot in order to analyze any issues
you may have encountered with PRTG. Please also consider the suggested links to articles
regarding the scope of your issue.
Once you are finished, click on Submit t o Paessler Support to send your request, or click on
Cancel to return to the page from which you opened the contact form. You can be sure that
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: PRTG will try to send your feedback / support question to Paessler as an email using
Simple Mail Transfer Protocol (SMTP). Please ensure that your PRTG installation is able to send
emails to external destinations!
18.11.2014
2425

The Contac t Support / Feedbac k Form
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. Otherwise, a new
ticket will be created.
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.
2426
18.11.2014

Scope of Your Quest ion: Select a topic regarding your issue and consider the proposed
links.
Describe Your Quest ion in One Sent ence: Provide short information which 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

In order 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:
Creat e and at t ach screenshot (recommended): This will create a screenshot of the
currently displayed page in PRTG. It will be sent with your ticket. A preview will be shown
below the screenshot section. Note: If you encounter issues on a specific page in PRTG, call
the contact support form on this page in order to get a screenshot of it.
Do not at t ach screenshot : No screenshot will be taken. Note: We recommend to attach a
screenshot in order to understand your request easier and faster.
In 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: No files will be attached. Choose this option only when
sending feedback.
18.11.2014
2427
Part 8
Enterprise Console
19.09.2014
2429
Part 8: Enterprise Console |
Enterprise Console
The Enterprise Console (formerly called "Windows GUI") is one alternative interface 77 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 provides extended popup window functionalities as well as a seamless
link to the Ajax web interface 100 where you can change your monitoring configuration and
access further functionalities such as reporting, Maps, system setup, etc. Some of these
functionalities are shown with an embedded webkit browser, for others an external browser
window is opened.
Access Several Core Servers in One Console

As an additional functionality, you can configure access to several PRTG core servers in the
Enterprise Console. The console will then show data of your independent core server
installations at a glance (for example, the device tree and alarms list), so you can manage your
monitoring centrally, also when it is spread across different servers.
Getting Started
With an installation of PRTG Network Monitor, the Enterprise Console is included and installed
automatically on the computer running the PRTG core server. If you want to use the Enterprise
Console on another computer, please download and install it there, as described in the Inst all
t he Ent erprise Console 67 section.
Note: The Enterprise Console is mainly designed to review and manage an existing installation
of PRTG which has already been set up. If you just started monitoring, we recommend you use
the Configuration Guru 36 and the web interface's auto-discovery 194 function and add your
network's 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)

In order 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:
The following server settings in the Enterprise Console (see section PRTG Servers
details) have to match the following settings in the PRTG Administ rat or Tool 2537 :
2430
2462
for
19.09.2014
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
Note: PRTG switches to port 8080 as a fallback after a restart
when port 80 is already used. Because the EC does not recognize
port 8080 automatically, enter this port manually in the EC
settings. If you do not get a connection to the PRTG web server,
check the currently used port in the Web Server and Websit e
Set t ings 2359 of PRTG's web interface.
Login Name
Login Name on the Administrator tab
Password
Password on the Administrator 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
See section More
2431
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?
The following sections introduce the features and concepts of the Enterprise Console:
19.09.2014
2431
Enterprise ConsoleTopics
First St art
2433
General Lay out
2434
Menu Tabs and Page Cont ent

PRTG Servers
Opt ions
2437
2462
2465
Windows Menu St ruct ure

Cont ext Menus
2471
2478
Short cut s Overview
2479
Related Topics
100

2432
192
2238
2482
19.09.2014
Part 8: Enterprise Console | 1 First Start
8.1
First Start
This section helps you 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 will try to connect to your PRTG installation,
according to the given 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. For example,
editing the settings is necessary in case the IP address of the server has changed.
If you get an error message, please check your connection settings. For detailed information,
please see PRTG Servers 2462 (PRTG Server Connect ion) section.
Tray Window
By default, the Enterprise Console runs in the 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 on the OK button to close it. You can change
the tray behavior in the Enterprise Console settings. For detailed information, please see
Opt ions 2466 settings (Sy st emAlert ing).
18.11.2014
2433
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 which this section describes.
PRTG Enterprise Console
From top to bottom, the main layout consists of:

The Windows menu
2434
The page header bar 2435 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
2436
2436
2435
2435
and search bar
underneath.
2436
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 100 shows up. In this case, you are logged in to the web interface automatically
via username and hash value 2329 . 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 105 section. If you configure your Enterprise Console for a connection
with more than one PRTG core server, keep an eye on the server selection 2435 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 2471 .
2434
18.11.2014
Page Header Bar

Enterprise Console Page Header Bar
The page header consists of the following parts:

PRTG Logo
Click on the PRTG Network Monitor logo to open the Ajax web interface 100 in the browser
which you define in the Enterprise Console Opt ions 2465 . If you configured several PRTG core
servers, the browser loads the web interface of the server that you have currently selected
in the Devices 2438 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 known from your browser.
Refresh (Arrow Circle Sy mbol)
Click on 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 2465 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 state. Click on a box
to view a list of all sensors in the respective status. For a detailed description, please see
Sensor St at es 121 section. This section shows also the number of new alarms and new log
entries, as well as the number of new tickets. Click on the respective box to view Alarms 143
, Logs 146 , or Ticket s 148 .
Note: When viewing sensor lists, you can show the sensors of one server at a time only. 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 2437 section.
Server Selection
Enterprise Console's Serv er Selec tion and Searc h Bar
18.11.2014
2435
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 is shown in all Menu Tabs 2437
(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 2462 from the list, or to edit an existing one.
2471
to add or remove
Search Bar
Select a single PRTG core server from the server selection 2435 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 on a monitoring
object (for example, a sensor) in the search results, the Enterprise Console opens this object
in the Devices 2438 tab with details in the device tree.
Note: If you have configured a connection in the PRTG Servers 2462 options that uses a Root ID
2464 other than 0, the EC ignores this setting while searching. In this case, Search Result s for
the entire server (starting at Root ID 0) are shown.
News Feed Bar

The news feed bar shows latest news by Paessler. Click on the bar to open a window with an
overview about recent articles. You can open a specific article in the web browser by clicking
on the particular header. If you do not want to show the news feed in your Enterprise
Console, click on the X symbol besides the bar. You can enable it again via View 2475 | Show
News Feed in the main menu.
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 on it. Furthermore, the status bar
contains a Cont act Support 2425 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.
2436
18.11.2014
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,
monitoring results, etc.
PRTG Enterprise Console Dev ic e Details
The following sections introduce the available options within the different tabs:
Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
18.11.2014
2461
2437

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,
monitoring results, etc., as well as access maps, reports, and settings.
Enterprise Console Menu Tabs Bar
There is documentation available for the following tabs:

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
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 are 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
163 . For details, please see Priorit y and Favorit es 159 section.
Note: For more information about the hierarchical order of the different objects in the device
tree, please see Object Hierarchy 83 section.
On the right side you see details about the object selected on the left. The information is
spread over several tabs.
Enterprise Console Sensor Sub-Tabs on the Dev ic e Tab
2438
18.11.2014

1 Devices
Edit Objects in the Device Tree

Using the Edit menu (or the object's context menu 2478 ) you can 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 Windows Menu St ruct ure
2471
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 2471 (for example, Check Now or Pause) to several objects.
When selecting multiple items, the sub-tabs on the right side show data for all selected items at
a glance. For example, when selecting two sensors, you see their tables next to each other.
Graphs will actually be shown combined! This is a great way to instantly show one chart
containing the graphs of all selected objects. Each sensor channel will then be shown as one
line. This aggregated view works for all kind of objects.
Note: The tab Live Graph shows data for sensors only.
Note: Underneath each graph a legend is shown. Hover an entry in the legend to display the
according line in the graph above in bold.
18.11.2014
2439

1 Devices
Aggregated Graph View in Enterprise Console
Note: You may need to enlarge the Enterprise Console's window in order to see all tables and
graphs.
DevicesOverview
The Overview tab shows general information about the selected object. Depending on the
object selected, different information is displayed.
For servers, probes, and groups the table shows information in the Name section only, such
as priority and parent objects. On the right side, the window shows a geographical Map, if
enabled in your PRTG configuration as well as in the Enterprise Console's View menu 2475 . For
detailed information about geographical maps, please see Geo Maps 2258 section.
For devices, the Overview tab shows device details and summary graphs for different time
spans, as well as a list of all sensors on this device, recommended sensors for this device,
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 2220 ).
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 2475 (View). For Small Mult iple Graphs view please see DevicesGraph
section below.
2440
2441
18.11.2014

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). In every tab, you will see graphs as well as data tables.
While viewing a sensor graph you can hide single sensor channels individually. Simply remove
the check mark symbol in front of a channel name underneath the graph, and the according
channel's line will disappear. You can also Show all or Hide all channels by clicking on the
buttons besides the channel names. The graph view will be reset immediately.
Note: The days mentioned here are the default setting. You can change the detail of the
different graphs any time in PRTG's web interface under Sy st em Administ rat ionUser
Int erface 2363 .
DevicesGraph
This tab is only available if you enable the Small Mult iple Graphs (Ctrl+S) view in the Windows
Menu 2471 (View). For Large Single Graphs view please see above 2440 . 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 in order to display all graphs.
Note: The days mentioned here are the default setting. You can change the detail of the
different graphs any time in PRTG's web interface under Sy st em Administ rat ionUser
Int erface 2363 .
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.
18.11.2014
2441

1 Devices
Historic Data Tab of Ping Sensor
Depending on the File Format option you choose, the results will be shown:
HTML web page: Opens a new 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 on one of these items, a new window or tab of the external browser
configured in the Enterprise Console's Opt ions 2469 will open and PRTG will automatically login
and redirect you to the respective web page. If your browser displays a certificate warning,
please find more information in the SSL Cert ificat e Warning 105 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 Hist oric Dat a Report s 133 section of the Ajax Web
Interface 100 documentation.
DevicesLog
Click on 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 2455 menu tab.
2442
18.11.2014

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 once or twice on the header of the column you want to
sort by.
DevicesSettings
In the Set t ings tab the currently selected object's settings are loaded from the web interface
and displayed. 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 100
documentation:
Probe Set t ings
244
Group Set t ings
262
Device Set t ings
284
Sensor Set t ings
304
DevicesSettingsMulti-Edit
If you select several objects on the left side, the Set t ings tab switches into multi-edit mode
. Using multi-edit, you can set a check mark for one or more settings. All changes will be
applied to all selected objects. The multi-edit dialog displays settings which are common
among the selected objects only.
2248
If you select sensors only on the left side, 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 2220 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 will be applied to all selected
sensors.
Note: You cannot use multi-edit for objects on different PRTG core servers.
DevicesNotifications
In the Not ificat ions tab the currently selected object's settings are loaded from the web
interface and displayed. 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 100 documentation.
2227
section in the Ajax
Note: You cannot change notification settings for multiple objects at a time. We recommend
using the Inherit ance of Set t ings 88 for easy configuration.
18.11.2014
2443

1 Devices
DevicesComments
In the Comment s tab the currently selected object's settings are loaded from the web
interface and displayed. View and functionality are the same as in the web interface.
DevicesHistory
In the Hist ory tab all changes in the settings of an object are shown 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 2471 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 2478 .
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. In order to clone sensors to other
devices using drag&drop, please use the Ajax Web Interface 100 . For detailed information,
please see Manage Device Tree 226 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.
2444
18.11.2014

2 Libraries
8.3.2
Libraries

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
Using Libraries is a great way to keep an eye on your network's status because you can
individually select which sensors you would like to see there. For a general introduction to
PRTG Libraries, please see Libraries 2275 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 are displayed.
Single-click on a library's name to display it. In the tabs above the library, select from
Overview 2275 , Management 2282 , Set t ings 2284 , Not ificat ions 2263 , Comment s 2288 , and Hist ory
2289 . Each of these tabs loads the respective functionality of the Ajax Web Interface 100 . Click
on the Save button to apply changes to your settings. Please find detailed information in
the Libraries 2275 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 109 section).
Click on a library node to edit the node settings
2284
in a new window.
Double-click on 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 on this PRTG server. For more information see
Libraries 2275 section.
18.11.2014
2445

2 Libraries
Right-click on a library's name to open a context menu 2478 . The following options are
available: Add, Edit , Delet e, Clone, 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
information see Libraries 2275 section.
Use the button Add Library to create a new library and the button for object history
view all changes to libraries.
184
to
Libraries Menu TabAdd Library

Click on the Add Library button to add a new library to a core server.
Depending on the current setting shown in the server selection 2435 bar in the upper right
corner, an (embedded) window will be opened immediately (if one specific server is selected),
or you will be prompted with a selection window, asking you to choose the core server you
want to add the new item to. Choose an installation to start.
Enterprise Console Serv er Selec tion Dialog
For details about adding a library, please see Libraries St ep By St ep
2446
2278
18.11.2014

3 Sensors
8.3.3
Sensors

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
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 object, sensor type, 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 on 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 available in your monitoring setup.
Select an entry to only show sensors of this type. The default value is All Ty pes.
18.11.2014
2447

3 Sensors
By St at us
The third drop down menu shows all possible sensor states. 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 on a sensor symbol in the page header bar 2435 , you can directly view a
sensor list filtered by the selected sensor state for the selected server.
If you have filtered out all sensors and the list below shows no entries, try removing 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.
sort by.
From this list view, you can select multiple items in order 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 hovering 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.
2448
18.11.2014

4 Alarms
8.3.4
Alarms

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
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 on Show as Gauges to show the sensors on the Alarms tab represented with gauges
124 .
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 in order to apply the same action to them, for
example, Edit | Check Now.
18.11.2014
2449

4 Alarms
You can select multiple items by the following means (you can also combine them):
Click and hold your left mouse key while hovering 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 121 )
and will not trigger 2227 any more notifications 2263 . Note: If the alarm condition clears, the sensor
usually returns into an Up status immediately with the next sensor scan.
To acknowledge an alarm, right-click on a sensor and choose Acknowledge Alarm... from the
context menu, enter a message and click the OK button. The message will appear in the last
message value of the sensor. You can choose between: Acknowledge Indefinit ely ...,
acknowledge For 5 Minut es..., For 15 Minut es..., For 1 Hour..., For 3 Hours..., For 1 Day ...,
or Unt il....
If you choose Unt il... a dialog box appears:

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 2248 .
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 2385 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 2385 , section
Account Cont rol.
2450
18.11.2014

5 Maps
8.3.5
M aps

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
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 selected map is displayed.
Single-click on a map's name to display it. In the tabs above the map, select from View Map,
Maps Designer 2317 , Set t ings 2323 , Get HTML 2325 , Comment s 2326 , and Hist ory 2326 . Each of
these tabs loads the respective functionality of the Ajax Web Interface 100 . Remember to
click the Save button to apply your settings. Please find detailed information in the Maps 2311
section.
Double-click on a map's name to open the map in the configured external web browser. You
can edit it using the Maps Designer 2317 , or add new maps on this PRTG server. For more
information see Maps 2311 section.
Right-click on a map's name to open a context menu
Add, Edit , Delet e, Clone, Open in Web Browser.
2478
. The following options are available:
Use the button Add Map to create a new map and the button for object history
all changes to maps.
18.11.2014
184
to view
2451

5 Maps
Maps Menu TabAdd Map

Click on the Add Map button to add a new map to a core server.
For details about adding a map, please see Maps St ep By St ep
2452
2314
18.11.2014

6 Reports
8.3.6
Reports

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
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 on it's name to open the respective report tabs. The page
will be split into two parts. On the left hand side you still see all available reports from one or
several servers, on the right hand side the options for the currently selected report are
displayed.
Single-click on a report's name in the list on the left to display its options. In the tabs above
the report, select from Run Now 2298 , St ored Report s 2300 , Set t ings 2301 , Select Sensors
Manually 2308 , Sensors Select ed by Tag 2310 , and Comment s 2310 . Each of these tabs loads the
respective functionality of the Ajax Web Interface 100 . Remember to click the Save button to
apply your settings. Please find detailed information in the Report s 2291 section.
Right-click on a report's name to open a context menu 2478 . The following options are
available: Add, Run Now, Edit , Delet e, Clone, Open in Web Browser.
Double-click on any report's name on the left side to return to the initial list view of all
reports.
Use the button Add Report to create a new report and the button for object history
view all changes to reports.
18.11.2014
184
to
2453

6 Reports
Reports Menu TabAdd Report

Click on the Add Report button to add a new report to a core server.
For details about adding a report, please see Report s St ep By St ep
2454
2295
18.11.2014

7 Logs
8.3.7
Logs

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
The Logs list shows all past activities and events of your PRTG monitoring setup. This is useful
to keep track of all important activities and, for example, to check whether messages were
sent, etc. In a typical setup, a huge amount of data is produced here. As the activity of every
single object is minuted, you can use this data to check exactly if your setup works as
expected.
There are two options to call the logs list: Either you click on the Log tab while viewing an
object's details in the Devices 2442 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 2462 setup,
simply select All PRTG Servers from the server selection in the upper right corner.
18.11.2014
2455

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 All Event s or a sensor status
121 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 146 .
sort by.
2456
18.11.2014

8 Tickets
8.3.8
Tickets

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
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 on the X 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.
18.11.2014
2457

8 Tickets
sort by.
Tickets Menu TabOpen Ticket

To open a new ticket, click on Open Ticket in the upper right corner or in the context menu.
Select a related object, click on Cont inue, and provide Subject , Assigned t o, Priorit y , and
Comment s. Once finished, click on Save and to create the ticket.
Open Tic ket Dialog in PRTG Enterprise Console
For details about working with PRTG's ticket system, please see section Ticket s
web interface.
2458
148
for PRTG's
18.11.2014

9 Setup
8.3.9
Setup

Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
Setup Menu Tab

In the Set up tab you can access all options available in the Set up 2327 menu of the Ajax web
interface. You can collapse resp. expand the sections by clicking on the - resp. + symbol.
For more information, please refer to the respective section in the web interface's
documentation.
Account Set t ings:
My Account
2329
Not ificat ions

Schedules
2334
2353
Sy st em Administ rat ion:

User Int erface
18.11.2014
2357
2459

9 Setup
Monit oring
2367
Not ificat ion Delivery

Core & Probes
2379
Administ rat ive Tools

Clust er
2394
2372
2396
(available in a cluster
81
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 2385 section.
User Groups:
You see a list of configured user groups. Select one to change settings. For details, please
see User Groups 2390 section.
PRTG St at us:
Sy st em St at us
Clust er St at us
Aut o Updat e
2401
2416
(available in a cluster
81
setup only)
2411
Licensing St at us and Set t ings
2418
Opt ional Downloads and Add-Ons:

Client App for Windows (Ent erprise Console)
Remot e Probe Inst aller
2421
2421
2421
Support :
Cont act Support
2460
2425
18.11.2014

10 Search Results
8.3.10 Search Results


Devices
2438
Libraries
Sensors
Alarms
Maps
2447
2449
2451
Report s
Logs
2445
2453
2455
Ticket s
Set up
2457
2459
Search Result s
2461
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 on a monitoring object in the results to show it in the Enterprise Console's
Devices 2438 tab.
Other objects, for example, chapters from the help file, are loaded in an external browser.
18.11.2014
2461
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.
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 on 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. If there is any
Background Act ivit y on the respective server, which can potentially affect performance and
response times, this is displayed as well.
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 on 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 2438 tab. There is also a context menu 2478 available for each server connection with the
options to Add a server, to Edit or to Delet e a server, to open the server in the Ajax web
interface, as well as Move Up and Move Down to change its position on the Devices 2438 tab.
To change the settings of an existing server in the list, open its context menu with right-click
and click Edit or click on the respective screwdriver symbol in the table. You can alternatively
use the context menu of a server on the Devices 2438 tab: There you can choose between Edit
PRTG Server Connect ion (opens the edit dialog), Deact ivat e PRTG Server Connect ion (this
server's monitoring data will not be shown in the Enterprise Console anymore; you can
activate it again later in the servers list 2462 ), or view Dependencies 91 .
2462
18.11.2014
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 web 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 or 2538 (Web Server) section. Please
make sure that the set values match.
Please make sure that the server is reachable (especially when using Network Address
Translation (NAT)) and no firewall settings are blocking the connection.
Port
Enter the port on which the PRTG web 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 or 2538 (Web Server) section. Please make sure that
the set values match.
Please make sure that the server is reachable (especially when using Network Address
Translation (NAT)) and no firewall settings are blocking the connection.
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 2385 section.
18.11.2014
2463
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
84 .
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 is loaded much faster.
You can create several connections that only differ in the Root ID value in order to quickly
switch between different views within your configuration, choosing different PRTG core
server connections in the Enterprise Console's Devices 2438 tab.
Display Name (opt ional)
Optionally enter a name that is displayed in the Server 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 on Cancel to discard them.
2464
18.11.2014
Part 8: Enterprise Console | 5 Options
8.5
Options
From the Windows menu

settings dialog.
2471
of the Enterprise Console, select File | Opt ions... to open the
You can choose from these options on the left hand side:
System
2465
SystemAlerting
Device Tools
2466
2467
Select External Browser

Proxy Settings
2469
2470
System
From the Windows menu 2471 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
St art wit h Windows

By default this setting is enabled.
With this setting enabled, the Enterprise Console will start up automatically when this
computer is started.
Show in Tray
18.11.2014
2465
By default this setting is enabled.

With this setting enabled, a PRTG icon will be shown in the Windows tray.
On mouse over, it will show a balloon info 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.
In order to use any alerting functionalities (see SystemAlerting 2466 section), you must
enable this option. If the tray icon is not shown, no alerting from the Enterprise Console will
be available.
Clear Tray Blink Not ificat ion aut omat ically
Whenever there are new entries in the Alarms 2449 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, it will keep blinking, even if all alarms should be cleared meanwhile.
Rest ore last viewpoint aft er applicat ion st art
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). It is written to the registry 2470
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 will be loaded.
Updat e Int erval(s)
Define the number of seconds that will be waited before the screen is refreshed.
Default value is 60.
Language
Choose the language for this program from the drop down menu. Default is English.
Depending on your installation, you may be able to choose other languages here.
This setting will influence the language of the Enterprise Console only.
SystemAlerting
2466
18.11.2014
You can define what the Enterprise Console will do in case of new Alarms, Log Ent ries, or
ToDos. The settings are the same for all of these three cases, but you can individually define
them for each case. On the left side, please select either Alert ing for new Alarms, Alert ing
for new Log Ent ries, or Alert ing for new ToDos and define the settings as follows.
Note: All alerting options only take effect when the Show in Tray option is enabled in the
system 2465 settings above; if the tray icon is disabled, there will be no alerting from the
Enterprise Console.
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 2465 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's 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 on the folder symbol 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 will be played only on the computer running the Enterprise Console.
Open GUI
Open the Enterprise Console if there are new items to be alerted for.
Device Tools
In the Device Tools settings you can define commands that will be available in the Windows
Menu 2471 and context menu 2478 of groups, devices, and sensors. A command to initiate a
remote desktop connection is already predefined.
18.11.2014
2467
Note: In order for the tool function to work with your Windows version, you may need to run
the Enterprise Console as administrator.
Please 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.
Name
Enter a custom name for your command as it will show up in the context menu.
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.
Paramet ers
Enter the parameters with which the command will be called.
You can use the placeholders (variables) shown in the window. Other placeholders are not
possible. During runtime, these placeholders will be replaced by the respective values set for
the object you have selected. For example, the %id placeholder will be replaced by the ID of
a group, a device, or a sensor, depending on which object you're executing the command
for.
Paramet ersAvailable placeholders
The following placeholders (variables) are available in the Enterprise Console.
2468
18.11.2014
Available
For
Groups
Available
For
Devices
Available
For
Sensors
The object's ID as shown in

brackets behind the name
The object's Name value.
The sensor's or device's IP

Address/DNS Name value
The sensor's Last Message

value
%value
The sensor's Last Result value
%type
The sensor's Ty pe value
Placeholder
%id
%name
%host
%message
Will Be Resolved To
If a placeholder is used 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
Then, click an object in the device tree and run the tool from the Tools option in the menu
(either Windows 2471 or context menu 2478 ).
Short cut
Select a key shortcut for the command. Choose an F-Key from the list or select None to not
use a key.
Select External Browser

18.11.2014
2469
With these settings you can define which browser the Enterprise Console will use when you
select a command which requires opening an external browser window, for example when
calling View | Open Web GUI.... 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:
Use sy st em default browser (browser.exe)
Use IE (Version: x)
Note: Only Microsoft Internet Explorer 10 or 11 is supported by the Ajax web interface!
Please do not use it with Internet Explorer 9 or earlier! We recommend using Google Chrome
38 or later (recommended) or Mozilla Firefox 33 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.
Choose between:
No Proxy
Use a direct connection to the servers.
Use Sy st em Set t ings
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 on the LAN set t ings button.
Manual Proxy Configurat ion
Manually enter a proxy configuration. Please 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 2611 .
2470
18.11.2014
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
2471
Edit
2471
View
Help
2475
2476
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
Connect ions
Show a list of all configured PRTG core server connections. For

detailed instructions, please see PRTG Servers 2462 settings.
Opt ions...
Open this dialog to set options and to configure one or more PRTG
core server connections. For detailed instructions, please see
Opt ions 2465 settings.
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 2465
settings.
Use Close to close the Enterprise Console window. Alerting is still
available via the tray icon then. You can also double click on 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 shown if the Show in Tray option is

enabled in the Opt ions 2465 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 2437 you are and whether
and which objects are selected within the Devices 2438 , Sensors 2447 , or Alarms 2449 tab.
18.11.2014
2471
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, data for all sensors in the object
hierarchy 83 underneath is queried.
Shortcut: Ctrl+K
Det ails
Open the overview tab for the selected object (probe, group,
device, or sensor).
Edit
Access the pages for editing Set t ings... 141 , Not ificat ions 141 ,
Access Right s... 95 , and Management 141 (not for sensors) of the
selected object. In addition, you can Rename... this object. Hover
to see available options.
Dependencies
This option is only available if you select the Root group, a probe,
or group. This function shows an overview of the dependencies 91
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 2256 .
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
209 .
Add Aut o-Discovery

Group...
which guides you through adding such a group. For detailed
instruction, please see section Aut o-Discovery 194 .
Add Device...
which guides you through adding a new device to the selected
probe or group. For detailed instructions, please see Add a
Device 215 .
2472
18.11.2014
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 224 .
Run Aut o-Discovery

starts an automatic search and adds new sensors to the selected
device. The search is running in background. If found, you will see
new sensors after a few minutes automatically. For more
information, please see Aut o-Discovery 195 (Run Aut o-Discovery
Now).
Creat e Device
Templat e...

opens an assistant in a new window which guides you through
creating a device template. This will then be available for autodiscovery 194 . For detailed instructions, please see Creat e Device
Templat e 2253 .
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 will be stored in the monitoring
configuration and cannot be revoked.
Acknowledge Alarm...
This option is only available if you select a sensor in a Down or

Down (Part ial) status 121 . Hover to see available options. For
details on how to acknowledge an alarm, please see Alarms 2450
section.
Delet e
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 2246 .
Move
Move the selected object(s) of the device tree (use the Ctrl or Shift
key to select multiple objects). Hover 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, resp. one entry up or
down.
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.
18.11.2014
2473
EDIT
Note: Please see section Devices
movements.
Pause
2444
for details about allowed
Pause and resume monitoring for the selected objects from the
device tree (use the Ctrl key to select multiple objects). Hover 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 will be resumed 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.
Simulat e Error St at us This option is only available if you select a sensor. Set the selected
sensor to a simulated error status. As for the paused state,
Resume will appear in the context menu if a the selected sensor is
already in a simulated error state.
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 159 .
Hist oric Dat a
Open the historic data tab of the selected object. Hover 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 134 (Menu).
When you select one or more sensors (hold the Ctrl or Shift key to
select multiple items), you can open the Compare Sensors 130
dialog. The graphs of all chosen sensors will be added to
comparison automatically. You can add additional sensors in the
comparison dialog.
For sensors, you can open the Similar Sensors Overview
2474
137
18.11.2014
EDIT
Device Tools
Call a tool command. All placeholders (variables) configured in a

tool command will be resolved for the currently selected object.
Hover to see all available tools configured in your Opt ions 2467
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 2467 .
For devices, additional options are available. They allow you to
connect to the Service URL value defined in the device's settings
2443 , 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 2592 .
Note: In order for the tool function to work with your Windows
version, you may need to run the Enterprise Console as
administrator.
Find Duplicat es
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 Sort ing
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 2444 .
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 in Web Browser
Open the currently selected object in the Ajax web interface. This
option is not available if you select multiple objects. The default
browser can be set in the Opt ions 2469 settings.
Note: This option is available in the Cont ext Menus
View 2475 in the Windows menu bar.
2478
and under
View
The View menu provides settings related to what the Enterprise Console shows.
18.11.2014
2475
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 2465 settings.
Shortcut: F5
Open Web GUI...
Open the welcome page 175 of the Ajax web interface in the
external browser. You can set the default browser in the Opt ions
2469 settings.
Large Single Graph
Change the view in Devices 2438 menu tab to large single graphs.
This option displays live graphs and graphs for three other time
spans in different tabs.
Shortcut: Ctrl+L
Small Mult iple Graphs Change the view in Devices 2438 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.
2258
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 2469 settings.
Help
This menu provides links to help and information.
2476
18.11.2014
HELP
Help Cent er
Open the Help and Support Cent er in the Ajax web interface.
HTML Manual
Ent erprise Console...
Open the Ent erprise Console

Ajax web interface.
PRTG Net work

Monit or Homepage...
Open http://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.
Cont act Support
Open the Cont act Support 2425 dialog box to leave feedback or to
ask for support by sending a support bundle.
Configurat ion Guru
Start the Configurat ion Guru

Enterprise Console.
About ...
Open an information window about the Enterprise Console

application with version number and copyright information.
2430
36
sections of this manual in the
in a new window of the
See Also
Short cut s Overview
18.11.2014
2479
2477
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 on object. 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 2471 .
Context Menu of a Dev ic e in the Enterprise Console
2478
18.11.2014
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 .
2465
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.
2465
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)
18.11.2014
2479
Part 8: Enterprise Console | 8 Shortcuts Overview
See Also
Windows Menu St ruct ure
2480
2471
18.11.2014
Part 9
Other User Interfaces
19.09.2014
2481
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
2483
Smart phone Apps
2486
Related Topics
100

Ent erprise Console
2482
192
2238
2430
19.09.2014
Part 9: Other User Interfaces | 1 Mobile Web GUI
9.1
Mobile Web GUI
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 100 , 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 installed 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 105 .
Login Screen
After loading the web interface, the login screen is shown.
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 on Login. For detailed information about different
credentials, please see the Login 102 section for the Ajax Web GUI.
19.09.2014
2483
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.
PRTG Mobile Web GUI
There are also different sensor top lists available underneath 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 100 . If you would like to have more options on your mobile devices, take a look at
our Smart phone Apps 2486 .
Using the Mobile Web GUI

The device tree and lists of sensors, alarms, logs, and tickets are available as usual, but in a
view 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 100 . 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 objects detail page, using the respective buttons.
Reports and Maps are accessible in view only mode.
2484
19.09.2014
You cannot edit system settings.

To save bandwidth, an automatic page refresh is only activated after dedicated 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.
You will just need a few minutes to get 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!
19.09.2014
2485
Part 9: Other User Interfaces | 2 Smartphone Apps
9.2
Smartphone Apps
You can access your PRTG installation on your mobile devices with several PRTG apps. We
provide apps for iOS devices, Android systems, Windows Phone, and BlackBerry. You can
download and use these apps for free. PRTG for iOS 2486 , PRTG for Android 2486 , PRTG for
Windows Phone 2487 , and PRTG for BlackBerry (beta) 2487 make it possible to monitor your
network while on the go.
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.
If there is no suitable PRTG app available for your mobile device, use the Mobile Web GUI
interface as an alternative.
2483
PRTG for iOS

PRTG for iOS is the iOS app for PRTG Network Monitor version 12 or later. You can use it on
iPhone, iPad, and iPod touch with iOS version 6 or later. Background notifications require iOS 7.
You can also use free push notifications 2340 with this app.
For more information and in order 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, or on a Kindle Fire. For full
functionality, we recommend using at least PRTG 13.x.4 and Android 4.1. You can also use free
push notifications 2340 with this app.
Android.
2486
18.11.2014
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.
Windows Phone.
PRTG for Windows Phone

Menu
Note: Push notifications are currently not supported with this app.
PRTG for BlackBerry

PRTG for BlackBerry (beta) is the BlackBerry app for PRTG Network Monitor 13.1 or later. This
app requires BlackBerry 10.2 or later (supported devices are BlackBerry Q5, Q10, Z10, Z30, and
P9982).
18.11.2014
2487
For more information and in order to download this app, please see or web page PRTG for
BlackBerry .
Note: This app is in beta status. You cannot deploy PRTG for BlackBerry via BlackBerry
Enterprise Service (BES) 10.
Sensor Details on
PRTG for Blac kBerry
Note: Push notifications are currently not supported with this app.
More
PRTG for iOS:
http://www.paessler.com/apps/iosapp
PRTG for Android:
http://www.paessler.com/apps/androidapp
PRTG for Windows Phone:
http://www.paessler.com/apps/windowsphoneapp
PRTG for Blackberry:
http://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?
2488
18.11.2014
Part 10
Sensor Technologies
19.09.2014
2489
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
2491
Monit oring via WMI
2495
Monit oring via SSH
2498

2502
Bandwidt h Monit oring Comparison

Monit oring Qualit y of Service
Monit oring Email Round Trip
Monit oring Backups
2505
2507
2512
2514
Monit oring Virt ual Environment s

Monit oring Dat abases
2515
2524
Monit oring Sy slogs and SNMP Traps
2490
2500
2526
19.09.2014
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, CPU load, etc. The queried devices must
support SNMP.
Network Monitoring v ia SNMP
When you use a sensor with this technology, PRTG sends small data packets to devices, for
example, querying routers, switches, and servers for the traffic counters of each port. These
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 hundred or thousands of sensors, we recommend you
to start with SNMP. Besides network usage monitoring, another well-known feature of SNMP is
the ability to also watch other network parameters such as CPU load, disk usage, temperature,
as well as monitoring many other readings, depending on the queried device.
SNMP Network Issues

To use Simple Network Management Protocol (SNMP) for monitoring purposes, it is imperative
that UDP packets can travel from the machine running PRTG to the device you want to monitor
and back. This is usually the case in LANs and intranets. For connections across the internet,
to a Demilitarized Zone (DMZ), or for Wide Area Network (WAN) connections, some changes to
the traversed firewalls may be necessary. Keep in mind that SNMP V1 and V2c are not secure
protocols so you should not use them across the internet or insecure data connections. Only
SNMP version 3 supports encryption.
18.11.2014
2491
Understanding SNMP Sensors

To better understand and set up SNMP sensors, you may want to learn more about the
principles of Object Identifiers (OID) and Management Information Base (MIB). For more
information about this topic, please refer to the Knowledge Base article in the More 2494 section
below.
For an overview and details about all SNMP sensors, please see the List of Available Sensor
Ty pes 307 section.
SNMP Versions
PRTG supports three versions of the SNMP protocol: Version 1, version 2c, and version 3.
SNMP Version 1
This is the oldest and most basic version of SNMP.
Pro: Supported by most SNMP-compatible devices; simple to set up.
Contra: Limited security because it only uses a simple password (community string) and
sends data in clear text (unencrypted). Because of this, you should it only use inside LANs
behind firewalls, but not in WANs; version 1 only supports 32-bit counters which is not
enough for high-load (gigabits/second) bandwidth monitoring.
SNMP Version 2c
This version adds 64-bit counters.
Pro: Supports 64-bit counters to monitor bandwidth usage in networks with gigabits/second
loads.
Contra: Limited security (same as with SNMP V1).
SNMP Version 3
This version adds authentication and encryption to SNMP.
Pro: Offers user accounts and authentication for multiple users and optional data packet
encryption, increasing available security; plus all advantages of Version 2c.
Contra: Difficult to configure. Not suitable for large networks (see below for more
information).
2492
18.11.2014
It is important to know that if you select an SNMP version that is not supported by the server
or device you want to monitor, you receive an error message. Unfortunately, in most cases,
these error messages do not explicitly point to the possibility that you use the incorrect SNMP
version. These messages provide minimum information only, such as cannot connect or similar.
Similar errors occur when community strings, usernames, or passwords do not match.
SNMP Overload and Limitations of the SNMP System

SNMP V1 and V2 scale directly with the performance of the hardware and the speed of the
network. In our labs we are able to monitor 30,000 SNMP V1 sensors at a 60 second interval
with one PRTG server (core and local probe) plus two remote probes with 10,000 sensors
each.
However, SNMP V3 has performance limitations due to the SSL encryption. The main limiting
factor is CPU power (as well as the other general limits for PRTG). Because of this limitation,
you can monitor only a limited number of sensors per second using SNMP V3. Currently, PRTG
is able to handle about 40 requests per second and computer core, depending on your
system. This means that, on a common 1.x GHz computer with two cores, you can run about
5,000 SNMP v3 sensors with a 60 seconds scanning interval; on a system with four cores, you
can monitor around 10,000 sensors with 60 seconds interval. The CPU load is at about 50%
then. We do not recommend more.
Furthermore, the PRTG core server and probes should run on different computers. If you
experience increased values in the Interval Delay SNMP or Open Requests channels of the
Probe Healt h 1014 sensor (values above 0 % indicate that the SNMP requests cannot be
performed at the desired interval), you need to distribute the load over multiple probes. SNMP
V1 and V2 do not have this limitation.
If you run into SNMP overload problems, you have three options:
Increase the monitoring interval of the SNMP V3 sensors.
Distribute the SNMP V3 sensors over two or more probes.
Switch to SNMP V1 or V2 if you can go without encryption.
What is the SNMP Community String?

The SNMP Community String is similar to a user ID or password that allows access to the
statistics of a router or another device. PRTG Network Monitor sends the community string
along with all SNMP requests. If the correct community string is provided, the device responds
with the requested information. If the community string is incorrect, the device simply discards
the request and does not respond.
Note: SNMP community strings are only used by devices that support SNMP V1 and SNMP V2c
protocols. SNMP V3 uses safer username/password authentication, along with an encryption
key.
By convention, most SNMP V1/V2c equipment ships with a read-only community string set to
the value public. It is standard practice for network managers to change all the community
strings to customized values during device setup.
18.11.2014
2493
More
Tools: Paessler MIB Importer and SNMP Tester
http://www.paessler.com/tools/
Knowledge Base: How do SNMP, MIBs and OIDs work?
Paessler White Papers: Introducing SNMP and Putting SNMP into Practice
http://www.paessler.com/press/whitepapers/introducing_snmp
German: Paessler White Paper: Einfhrung in SNMP und SNMP praktisch anwenden
http://www.de.paessler.com/press/whitepapers/introducing_snmp
Knowledge Base: The interface numbers on my switch keep changing. What can I do?
2494
18.11.2014
Part 10: Sensor Technologies | 2 Monitoring via WMI
10.2
Monitoring via WMI
Windows Management Instrumentation (WMI) is Microsoft's base technology for monitoring and
managing Windows based systems. PRTG uses this technology to access data of various
Windows configuration parameters and status values. However, sensors using the WMI
protocol generally have a high impact on the system performance. In addition to strict WMI
sensors, there are sensors which use another approach to monitor Windows systems with
less influence on the system performance.
Monitoring Windows Systems: Performance Counters

Besides sensors which monitor Windows systems only via WMI, PRTG provides sensor types
which use a hybrid approach. These sensors first try to query data via Windows Performance
Counters using Remote Registry Service. Querying Performance Counters needs less system
resources than monitoring via WMI. These Windows sensors use WMI as a fallback if
Performance Counters are not available or cannot be read out. When running in fallback mode,
PRTG re-tries to connect to Performance Counters after 24 hours. This is the default approach
and can be changed in the Windows Compat ibilit y Opt ions in the Device Set t ings 284 .
Though, it can be the case sometimes that these Performance Counters differ from the direct
method.
Note: You can identify these hybrid sensors by looking at their categories, for example, in the
add sensor dialog. Search direct ly for "windows" and select "Performance Counters" as
Technology Used. Among them are various sensors with "Windows" in the name, as well as
some Hyper-V sensors.
How WMI Works

WMI allows accessing data of many Windows configuration parameters, as well as current
system status values. Access can be local or remote via a network connection. WMI is based
on COM and DCOM and is integrated in Windows 2000, XP, 2003, Vista, 2008, Windows 7, and
Windows 8 (add-ons are available for Windows 9x and NT4). PRTG officially supports WMI for
Windows Vista or later.
In order to monitor remote machines, PRTG's WMI sensor needs Active Directory account
credentials to have access to the WMI interface. You can enter these credentials in PRTG for
the parent device or group, or in the Root 228 group. The sensor will then inherit these
settings.
Note: Sensors using the Windows Management Instrumentation (WMI) protocol generally have
high impact on the system performance! Try to stay below 200 WMI sensors per probe 77 .
Above this number, please consider using multiple Remot e Probes 2589 for load balancing.
For an overview and details about all WMI sensors, please see the List of Available Sensor
Ty pes 309 section.
19.09.2014
2495
Limitations of WMI on Windows Vista and Windows Server 2008 (R1)

You should be aware that performance of WMI based monitoring is drastically limited when the
monitoring station or the monitored client runs on Windows Vista or Windows Server 2008
(R1). When it comes to network monitoring via WMI, Windows Server 2008 R2 is many times
faster than Windows Server 2008 (R1) or Vista.
Note: These are not limitations of PRTG, but arise from the WMI functionality built into the
Windows operating systems mentioned.
The results of our tests are:
On Windows Server 2008 R2 or Windows 7 you can run about 10,000 WMI sensors with one
minute interval under optimal conditions (such as running the core and the target systems
exclusively under Windows Server 2008 R2 and being located within the same LAN segment).
Actual performance can be significantly less depending on network topology and WMI health
of the target systems - we have seen configurations that could not go beyond 500 sensors
(and even less).
On Windows Vista/Windows 2008 R1 you can run about 300 WMI sensors with one minute
interval.
The more Windows Vista/Windows 2008/Windows 7 client systems you have in your
network, the more WMI monitoring performance will be affected.
System performance (CPU, memory etc.) of virtualization does not strongly affect WMI
monitoring performance.
If you want to use WMI for network monitoring of more than 20 or 30 systems, please
consider the following rules:
Do not use Windows Vista or Windows 2008 R1 as monitoring stations for WMI-based
network monitoring.
If possible use Windows Server 2008 R2 for WMI based network monitoring (or Windows 7).
If you cannot run PRTG on Windows Server 2008 R2, consider setting up a remote probe for
the WMI monitoring. (You still get far better WMI monitoring performance with a remote
probe on a virtual machine running Windows Server 2008 R2 than on any bare metal system
running Windows Vista/Windows 2008.)
Consider switching to SNMP-based monitoring for large networks. Using SNMP you can easily
monitor 10 times as many nodes as with WMI (on the same hardware).
More
Knowledge Base: General introduction to WMI and PRTG
Tool: Paessler WMI Tester. A useful freeware tool to test WMI connections. Tests the
accessibility of WMI (Windows Management Instrumentation) counters in a quick and easy
manner.
2496
19.09.2014
http://www.paessler.com/tools/wmitester
CEO's Blog: Don't Use Windows Vista And Windows 2008 R1 for Network Monitoring via WMI!
19.09.2014
2497
Part 10: Sensor Technologies | 3 Monitoring via SSH
10.3
Monitoring via SSH
Monitoring via Secure Shell (SSH) enables you to gather performance and system data from
many Linux and Unix distributions, as well as from certain Mac OS X systems. If your system is
supported, this monitoring technology works without the need of additional software on the
target systems.
How Monitoring via SSH Works

In order to monitor remote machines via SSH, PRTG needs credentials (preferably root access)
of the devices. If you use PRTG's SSH sensors, you can enter the necessary credentials in PRTG
for the parent device or group, or in the Root 228 group, in the Credentials for Linux/Solaris/
Mac OS (SSH/WBEM) Systems section on the Set t ings 141 tab. The sensors then inherit these
settings by default.
With each scanning interval, PRTG logs into your devices and query data by executing specific
commands.
For an overview and details about all SSH sensors, please see the List of Available Sensor
Ty pes 310 section.
Limitations When Using SSH Monitoring

Due to the plurality of Linux/Unix derivatives, PRTG's SSH sensors cannot support all
distributions on the market. Also, only certain Mac OS systems are supported. For a detailed
list please see the More 2499 section below.
Authentication via SSH Private Key

PRTG supports authentication via password or via private key.
When you use a private key, please ensure the following:
Provide the key in OpenSSH RSA format.
The key may not be encrypted! PRTG does not support password protected keys.
The key must be provided as RSA key, you cannot use DSA keys with PRTG!
When you provide an unencrypted RSA private key in OpenSSH RSA format, please copy the
entire key, including the
-----BEGIN RSA PRIVATE KEY-----
and
-----END RSA PRIVATE KEY-----
lines, into the according text field in PRTG and Save your settings. Once you have pasted and
saved the private key, PRTG shows as
***************************
2498
19.09.2014
Part 10: Sensor Technologies | 3 Monitoring via SSH
Please make sure there exists a corresponding public key on the target device.
For a detailed description how to convert and use an existing SSH key, please see the More
2499 section below.
More
Knowledge Base: Which Linux or Mac OS distributions are supported by the Linux/Unix
sensors (SSH, SNMP, WBEM)?
Knowledge Base: How can I use private keys for my SSH sensors with PRTG?
Knowledge Base: How do I enable SSH on my Mac OS X system?
19.09.2014
2499
Part 10: Sensor Technologies | 4 Monitoring Bandwidth via Packet Sniffing
10.4
Monitoring Bandwidth via Packet Sniffing
Packet Sniffing comes into consideration if your network device(s) do not support SNMP or
xFlow to measure bandwidth usage and if you need to differentiate the bandwidth usage by
network protocol and/or IP addresses.
Note: Packet Sniffer sensors support Toplist s
2240
(Top Talkers, Top Connections, etc.).
How Packet Sniffing Works

If you need to know what applications or IP addresses cause the traffic in your network, you
can use a packet sniffer. A packet sniffer looks at every single data package that travels
through your network for accounting purposes.
Monitoring with PRTG v ia Pac ket Sniffer Sensors
PRTG can analyze the packets passing the network card of a PC or you can connected it to
the monitoring port of a switch. To calculate bandwidth usage, PRTG inspects all network data
packets either passing the PC's network card (shown on the left side in the schema above) or
the data packages that a monitoring port of a switch (right side) sends with its built-in packet
sniffer. Using remote probes, you can set up packet sniffers anywhere in your network (see
Add Remot e Probe 2588 section).
Comparing the four bandwidth monitoring technologies which PRTG provides (SNMP, WMI,
xFlow, and packet sniffer) this one creates the most CPU and network load, so you should
only use it in small to medium networks, on dedicated computers for larger networks or for
individual computers.
Reasons to Choose Packet Sniffing

It is important to understand that the packet sniffer can only access and inspect data packages
that actually flow through the network interface(s) of the machine running the PRTG probe
software. This is fine if you only want to monitor the traffic of this machine (e.g., your web
server). In switched networks, only the traffic for a specific machine is sent to each machine's
network card, so PRTG can usually not discern the traffic of the other machines in the
network.
2500
19.09.2014
Part 10: Sensor Technologies | 4 Monitoring Bandwidth via Packet Sniffing
If you also want to monitor the traffic of other devices in your network, you must use a switch
that offers a monitoring port or port mirroring configuration (Cisco calls it SPAN). In this case,
the switch sends a copy to the monitoring port of all data packages traveling through the
switch. As soon as you connect one of the PRTG probe system's network cards to the
switch's monitoring port, PRTG is able to analyze the complete traffic that passes through the
switch.
Another option is to set up the PC running PRTG as the gateway for all other computers in the
network.
Set Up Packet Sniffer Sensors

Find details on how to set up the different flow sensors in the following sections:
907
Packet Sniffer (Cust om) Sensor
916
Header Based Packet Sniffing

For packet sniffing, PRTG looks at the IP addresses and ports of source and destination to
assess the protocol. This is a very fast method which saves system resources.
Note: Sometimes, this method is not fully accurate. For example, it is not possible to identify
HTTP traffic on ports other than 80, 8080 and 443 as HTTP. HTTP traffic on non-standard ports
would not be accounted as such.
More
Tool: Paessler Card Packet Counter: Shows short term statistics about the network data
packets passing a local network card.
Sniffer sensors?
19.09.2014
2501
Part 10: Sensor Technologies | 5 Monitoring Bandwidth via Flows
10.5
Monitoring Bandwidth via Flows
Using flow protocols, you can monitor the bandwidth usage of all packets going through a
device. In PRTG, you can view Toplist s 2240 for all xFlow (NetFlow, IPFIX, sFlow, jFlow) sensors.
How xFlow Monitoring works

You can measure bandwidth usage by IP address or by application in a network, using one of
the xFlow (including IPFIX) protocols. They are the best choice especially for networks with
high traffic (connections with 100s of megabit or gigabits). For xFlow monitoring, the router
gathers bandwidth usage data (flows), aggregates them, and sends information about these
flows to PRTG using UDP packets. When you use sampling (mandatory for sFlow), only
information about every n-th packet is sent to PRTG which reduces CPU load a lot. Because the
switch already performs a pre-aggregation of traffic data, the flow of data to PRTG is much
smaller than the monitored traffic. This makes xFlow the ideal option for high traffic networks
that need to differentiate the bandwidth usage by network protocol and/or IP addresses.
NetFlow and IPFIX Monitoring

The NetFlow (and IPFIX) protocol is mainly used by Cisco devices. Once configured, the router
sends for each data flow a NetFlow or IPFIX packet to the monitoring system running on a
PRTG probe. You can be filter and evaluate the data in PRTG. There are different NetFlow and
IPFIX sensors available: The basic ones offer predefined channel definitions, the custom
variants enable you to define your own channels.
The advantage of using NetFlow or IPFIX:
Generates little CPU load on the router itself (according to Cisco 10,000 active flows create
about 7% additional CPU load; 45,000 active flows account for about 20% additional CPU load).
Generates less CPU load on the PRTG core system, compared to packet sniffer sensors.
Note: You must enable NetFlow or IPFIX export on the device you want to monitor. The device
must send a flow data stream to the IP address of the PRTG probe system on which you set up
the NetFlow or IPFIX sensor. You can monitor Juniper jFlow with the corresponding sensors as
well (basically they are adjusted NetFlow v5 sensors).
sFlow Monitoring
sFlow works similar to NetFlow monitoring. The router sends data flow packets to the
monitoring system running on a PRTG probe. The most obvious difference between the two
flow protocols: With sFlow, not all of the traffic is analyzed, but only every n-th packet. It is like
having a river of traffic and you take a cup of water out of it ever so often and analyze it.
The advantage is clear: There is less data to analyze, there is less CPU load needed, and less
monitoring traffic is generated. Nevertheless, you can get a good insight into your network
bandwidth usage. Note: Currently, PRTG supports sFlow version 5.
Set Up Flow Sensors

Find details on how to set up the different flow sensors in the following sections:
2502
19.09.2014
Net Flow V5 Sensor
846
Net Flow V5 (Cust om) Sensor

Net Flow V9 Sensor
865
Net Flow V9 (Cust om) Sensor

IPFIX Sensor
875
741
IPFIX (Cust om) Sensor

sFlow Sensor
856
751
1094
sFlow (Cust om) Sensor

jFlow V5 Sensor
1103
770
jFlow V5 (Cust om) Sensor
780
Limitations
On a powerful 2008 PC (Dual Core, 2.5 Ghz), you can process about 100,000 flows per second
for one xFlow stream. Using sampling, the number of actual flows can be much higher. When
using complex filters, the value can be much lower. For example, with a router sending about
2,000 flows/second (which corresponds to mixed traffic at gigabit/second level without
sampling) you can expect to configure up to 50 NetFlow sensors operating properly. PRTG
internally monitors its own NetFlow processing, and you will see a decreased values in the
Health channels of the Core Healt h 385 and Probe Healt h 1014 sensors as soon as NetFlow
packets are not processed due to an overload (you find these sensors on the local probe
device).
If you experience an overload, please consider using sampling or setting up multiple probes
and distribute the NetFlow streams to them. We do not recommend adding more than 400
NetFlow sensors per PRTG probe.
This sensor type cannot be used in cluster mode. You can set it up on a local probe or remote
More
Knowledge Base: Can I add custom channels to standard Packet Sniffer and NetFlow sensors?
Knowledge Base: What filter rules can be used for custom Packet Sniffing or xFlow (NetFlow/
sFlow) sensors?
Knowledge Base: How do the channel definitions for custom Packet Sniffing or xFlow
(NetFlow/sFlow) sensors work?
19.09.2014
2503
Knowledge Base: Does my Cisco device (Router/Switch) support NetFlow Export?

Knowledge Base: Do you have any configuration tips for Cisco routers and PRTG?
Knowledge Base: Is it possible to monitor Cisco ASA Firewalls using Netflow 9 and PRTG?
Knowledge Base: How to monitor Cisco ASA Firewalls using NetFlow 9 and PRTG?
Sniffer sensors?
Tools: NetFlow Generator and NetFlow Tester
2504
19.09.2014
Part 10: Sensor Technologies | 6 Bandwidth Monitoring Comparison
10.6
Bandwidth Monitoring Comparison
The following table shows the differences between PRTG's four methods available for
bandwidth monitoring:
WMI
SNMP
Packet Sniffer
xFlow (IPFIX ,
Net flow, sFlow,
jFlow)
Medium
Easy
Easy to Complex
(depending on
filter rules used)
Can be complex
(e.g., the switch
must be configured)
Traffic can be No
filtered
No
Yes
Yes
Differentiate
bandwidth
usage by
protocol or
IPs
No
No
Yes
Yes
PRTG can
show
Toplists (Top
Talker, Top
Connections
, Top
Protocols,
custom)
No
No
Yes
Yes
Filter
bandwidth
usage by IP
No
No
Yes
Yes
Filter
No
bandwidth
usage by
MAC address
No
Yes
No
Filter
bandwidth
usage by
physical
network
port
Yes
No
No
Setup
19.09.2014
Yes
2505
Part 10: Sensor Technologies | 6 Bandwidth Monitoring Comparison
WMI
SNMP
Packet Sniffer
xFlow (IPFIX ,
Net flow, sFlow,
jFlow)
Monitor
network
parameters
other than
bandwidth
usage
Yes
Yes
No
No
CPU load on
the machine
running
PRTG
Low
Low
Higher, depends
Higher, depends on
on the amount of the amount of
traffic
traffic
Excess
bandwidth
usage of
monitoring
Small
Small
None (except
when monitoring
switch ports are
used)
Depends on the
traffic
More
Knowledge Base: Should I use SNMP, xFlow (IPFIX/NetFlow/sFlow) or Packet Sniffing for my
monitoring?
Knowledge Base: How do I discern excessive bandwidth usage with PRTG?

2506
19.09.2014
Part 10: Sensor Technologies | 7 Monitoring Quality of Service and VoIP
10.7
Monitoring Quality of Service and VoIP
PRTG can monitor the Quality of Service (QoS) in a network with dedicated QoS sensors, as
well as Cisco IP Service Level Agreement (SLA) and Cisco Class Based Quality of Service
(CBQoS). Slight variations of network parameters like jitter, packet loss, or packet delay
variation (PDV) usually have only little effect on TCP based services (for example, HTTP, SMTP).
But for UDP based services like Voice over IP (VoIP) and video streaming, a steady stream of
data packets is crucial. The sound quality of a VoIP call drops dramatically when UDP packets
are not received in a timely fashion, or if packets are lost or out-of-order. As a rule of thumb
for good quality of service (in a VoIP perspective), you want low measurements for jitter (less
than 20 to 50 ms) and PDV (less than 100 ms), and preferably zero measurements for packet
loss, duplicated packets, or packets in wrong order.
For Quality of Service measurements, four sensors are available:
QoS (Qualit y of Service) Sensor 1020
Monitors VoIP relevant network parameters by testing network connection quality between
two probes.
QoS (Qualit y of Service) Round Trip Sensor 1027
Monitors VoIP relevant network parameters by testing network connection quality between
a probe and a target device at the endpoint of the connection. Traffic is measured
bidirectional.
Cisco IP SLA Sensor 358
Monitors VoIP relevant network parameters through IP SLA results from Cisco devices (via
SNMP).
SNMP Cisco CBQoS Sensor 1198
Monitors VoIP relevant network parameters by using Cisco's CBQoS (via SNMP).
QoS (Quality of Service) Sensors

The QoS Sensors monitor the quality of a network connection by measuring the following
parameters:
Jitter in ms according to RFC 3550
Packet delay variation (PDV) in ms according to RFC 3393
Lost packets in %
Out-of-order packets in %
Duplicated packets in %
The QoS sensors measure quality of service by sending UDP packets between two probes.
This means that you can test any network connection in your network by simply placing a
remote probe 2588 on (or near) each 'end' of the connection and measuring the connection
quality between them. This is the perfect tool to find network issues that can affect VoIP
sound quality or video streaming 'hiccups'.
Note: You can use the QoS Round Trip sensor also without installing a remote probe at the
connection endpoint. See section More 2511 .
19.09.2014
2507
Monitoring Quality of Serv ic e with PRTG
The measurements for QoS monitoring are taken between two probes. So the first step is to
place two PCs running a remote probe on (or near) both ends of the connection that you want
to monitor. As an alternative, the local probe on the PC running the PRTG core can also be
used as one end, or you can use the PRTG QoS Reflector (see section More 2511 ) to bounce the
packets when monitoring QoS roundtrips. If any firewalls, packet filters, or Network Address
Translation (NAT) systems are en route, you must configure them as necessary so that the UDP
packets can reach the target probe.
In PRTG, create a new QoS sensor on a Probe Device, or, if you use the roundtrip sensor, on
any device. Please find details about settings in the QoS (Qualit y of Service) One Way Sensor
1020 resp. QoS (Qualit y of Service) Round Trip Sensor 1027 section. With the settings for
number and for size of the packets, you can configure the test data stream. 1,000 packets of
172 bytes each is a good start, but if your applications use larger packets you may want to
enter other values here. Try to configure the test streams with parameters similar to that of
the UDP services you are using across this connection.
Cisco IP SLA Sensor

Wikipedia describes IP SLA as a feature included in the Cisco IOS Software that can allow
administrators the ability to Analyze IP Service Levels for IP applications and services. IP SLA
uses active traffic-monitoring technology to monitor continuous traffic on the network. This is
a reliable method in measuring over head network performance. IP-SLA is mostly used to
monitor the sound quality of VoIP traffic.
2508
19.09.2014
If you haven't done so already, add a device in PRTG for the Cisco device that you want to
monitor. Then create a new Cisco IP SLA sensor on this device. Please find details about
settings in the Cisco IP SLA Sensor 358 section.
This feature is only available in the more expensive Cisco devices. If you don't have IP SLA
capable routers/switches, you can still get similar information with PRTG's QoS sensor (see
above 2507 ) which does not require any special hardwarejust two PCs running Windows. If you
own hardware that supports IP SLA, then PRTG brings you probably the least-cost monitoring
solution for IP SLA. Most vendors charge extra for IP SLA support (a thousand bucks and
more). Following Paessler's long term policy, we simply include this as one of our sensor types.
With PRTG you can even use the Freeware Edition to monitor IP SLA!
PRTG monitors the following parameters: Calculated Planning Impairment Factor (ICPIF), Mean
Opinion Score (MOS), Average Jitter, Packets Lost, Packets Out Of Sequence, Packets Late,
Average Round Trip Time (RTT), DNS RTT, TCP RTT, Transaction RTT. Especially two of these
parameters are interesting for VoIP: Mean Opinion Score (MOS) and Calculated Planning
Impairment Factor (ICPIF).

Cisco Class Based Quality of Service (CBQoS) provides information about QoS of Cisco
network devices which support the Modular QoS command line interface (MQC). With Classed
Based QoS, you can obtain monitoring data that includes summary counts and rates by traffic
class before and after the enforcement of QoS policies, according to Cisco's CBQoS
Management Information Base (MIB) definition. PRTG determines CBQoS data via Simple
Network Management Protocol (SNMP). The corresponding sensor type is available out-of-thebox in PRTG version 13.x.5 or later. CBQoS is available in Cisco IOS by default as of version
12.4(4)T.
In order to monitor CBQoS, add a device to PRTG for the Cisco device that you want to
monitor. Then create a new SNMP Cisco CBQoS sensor on this device. Please see section
SNMP Cisco CBQoS Sensor 1198 for more details.
This sensor type supports the following CBQoS classes:
Class Map: statistical data about class maps, such as pre- and post-policy packets and sizes,
drop packets and size, as well as no-buffer drop packets
Mat ch St at ement : statistical data about match statement specific information, such as prepolicy packets and size
Queueing: statistical data about queuing actions, such as current and maximum queue
depth, drop packets, and drop size
You can select the desired CBQoS entries which you want to monitor while creating the
sensor in PRTG. The available entries are given with their particular connections, their
descriptions, and class types.
19.09.2014
2509
Voice over IP
For Mean Opinion Score (MOS) measurements, Cisco conducted a panel test where a wide
range of listeners judged the quality of voice samples sent using particular codecs, on a scale
of 1 (poor quality) to 5 (excellent quality). The Cisco device calculates the corresponding value
for the current network connection based on the network parameter measurements like jitter
and packet loss.
Note: The Cisco IP SLA sensor reads out the MOS directly from the Cisco device. For the QoS
and the QoS Round Trip sensor, PRTG calculates the MOS by itself. See section More 2511 for
details.
The values and their meanings are:
MOS
Qualit y
Expect ed Qualit y
Impairment
Excellent
Imperceptible
Good
Perceptible, but not annoying
Fair
Slightly annoying
Poor
Annoying
Bad
Very annoying
The second interesting parameter ICPIF is the sum of measured impairment factors minus a
user-defined access Advantage Factor that is intended to represent the user's expectations,
based on how the call was placed (for example, a mobile call versus a land-line call) (quoted
from Cisco's website).
2510
19.09.2014
Upper Limit for ICPIF
VoIP Call Communicat ion Qualit y
Very good
10
Good
20
Adequate
30
Limiting case
45
Exceptional limiting case
55
Customers likely to react strongly (complaints, change of

network operator)
More
Knowledge Base: Where can I find more information about Cisco IP SLAs, VoIP, and QoS?
Knowledge Base: How does PRTG calculate the MOS score for QoS sensors?
Knowledge Base: How can I monitor QoS roundtrips without using remote probes?
19.09.2014
2511
Part 10: Sensor Technologies | 8 Monitoring Email Round Trip
10.8
Monitoring Email Round Trip
Email Round Trip sensors ensure the end-to-end delivery of emails and make it possible to
monitor availability and performance of a complete email delivery process. There are two
sensor types for this task:
1151
1142
Both initially deliver an email to a mail server using SMTP. Afterwards the receiving mailbox is
scanned using Post Office Protocol version 3 (POP3) or Internet Message Access Protocol
(IMAP) until the email arrives. The test email contains a unique code in the topic which is used
to identify the email, such as PRTG Roundtrip Mail: {6D136420-5A3E-46CF-871A1DAF0C4F3D5D}.
When PRTG successfully received an email in this email round trip cycle, it marks the respective
message for deletion on the mail server. Usually, a mail server will then delete this email. For
best performance, we recommend using a dedicated email accounts for email round trip
sensors.
Monitoring an Email Round Trip
In the scenario shown above, there are three steps in the round trip:
St ep 1
PRTG delivers an email via the SMTP protocol to a mail server (just like an email client).
St ep 2
The SMTP server delivers the email to a POP3/IMAP server (which can be located at a remote
site, in your local LAN or on the same server as well).
2512
19.09.2014
Part 10: Sensor Technologies | 8 Monitoring Email Round Trip
St ep 3
Every few seconds PRTG connects to the POP3/IMAP server until the test email arrives.
Recommended Configuration
Here is a simple concept to check delivery of email out of and into your organization:
1. Create a dedicated email account for this test in your mail system.
2. Set up an external email account (hosted mail server, free mail service, etc.) and configure it
to send all emails back to this dedicated email account in your organization (which you
created in Step 1).
3. Set up PRTG's round trip sensor to send an email to the external email account (which you
created in Step 2) using your LAN's mail server and then check for the email account on your
mail system (which you created in Step 1) for arrival of the email.
With this technique you are testing multiple aspects of your email server setup. As long as the
sensor shows a green light, this means:
Your email server accepts emails via SMTP.
Emails are being sent to the outside world (internet connection works, MX lookups work
etc.).
Emails from external mail server can be delivered into your mail system (this includes aspects
like the fact that the MX records for your domain are correct, your mail server can be
reached from the outside world, your email filtering is working etc.).
Emails can be retrieved using POP3 (or IMAP).
Conclusion
These two sensor types are a great tool to ensure delivery of email from and to your mail
servers. Compared to the standard SMTP, POP3 and IMAP sensors - which only check the
availability of these services - the two roundtrip sensor types actually monitor the complete
transaction from accepting the mail on the first email server to delivery of the mail on the final
POP3/IMAP server.
19.09.2014
2513
Part 10: Sensor Technologies | 9 Monitoring Backups
10.9
Monitoring Backups
Monitoring your backup software enables you to be sure that your recent backups
succeeded. With PRTG you can check the email notifications of various backup jobs. You only
need two things for backup monitoring:
1. Configure your backup software to send emails to a dedicated email account, and
2. configure PRTG's IMAP Sensor
714
for backup monitoring.
PRTG will analyze the backup emails for you and set the status of the IMAP sensor accordingly.
This way you will see the states of all your backup jobs at a glance.
Bac kup Monitoring v ia Email
Setting up Backup Monitoring

Please refer to our Knowledge Base for a step-by-step tutorial to monitor your backup jobs:
Monit oring Backup Solut ions via Email
2514
19.09.2014
Part 10: Sensor Technologies | 10 Monitoring Virtual Environments
10.10 Monitoring Virtual Environments

A highly flexible IT infrastructure is a common need nowadays and virtualization has become an
important pillar of the IT all over the world. Applications in your network might be distributed
over many different servers, networks and locations. They might also be in the cloud, and your
computations can take place in data centers spread over the whole world. So, if your network
connection or any other corresponding hardware fails, hundreds of applications might be
unavailablean impact to your daily business processes which should be avoided at any costs.
Because of this, monitoring the physical infrastructure of your data center is still a must in
times of virtual environments. With the layer of virtualization in addition to your physical
equipment, your logical infrastructure needs also a close treatment. PRTG assists you to deal
with these advanced requirements and enables you to react proactively to issues before they
affect your whole system. With PRTG you can monitor all layers of your IT infrastructure in a
comprehensible way so you will reduce issues related to dynamic IT environments significantly.
Monitoring All Layers of Your IT Infrastructure

In general, you can assume that with the layer of virtualization you have to monitor a total of
four layers in your IT infrastructure:
Hardware (Server Racks): Usually you will set up your monitoring in the common way and
monitor most of the hardware components in your network with PRTG's SNMP sensors 307 .
You are able to gain monitoring data about many different device readings such as CPU load,
memory, disk space, etc. with this monitoring technology 2491 , as well as information about
network traffic and bandwidth usage of your routers and switches. It is absolutely mandatory
for a working IT environment to monitor all hardware components in order to be alerted if
something fails or hardware resources are running out. In addition, you can identify potential
bottlenecks affecting your virtualized infrastructure. You can set this monitoring up in usual
way.
Host Server Hardware: It is essential to monitor the host hardware of your virtualization
solution explicitly. If you have issues with your virtual machines (VMs), the origin might be a
host hardware failure. You should closely monitor your VM host servers to get alerted if the
status is other than "normal". Besides the out of the box hardware sensors, PRTG provides
specific sensors for various virtualization host servers; the following monitoring data of your
host servers will help you prevent issues in virtualized environments:
VMware: current reading and health status (via WBEM), a general status as shown in
vSphere (via SOAP), and disk space on ESX(i) (via SSH)
Hyper-V: host health critical values, deposited pages, network traffic, CPU usage of guests,
hypervisor, and in total
Citrix XenServer: CPU, memory, and network usage, the number of running virtual
machines on the host server, and load average
SCVMM: CPU usage, free memory (in bytes and percent), overall status, communication
status, cluster node status, virtual server status, computer status, and the number of VMs
19.09.2014
2515
VMs from t he "Out side": The virtual machines run on their particular host servers. PRTG can
show you the status of single virtual machines and several of their performance counters. It
might be helpful to know which resources a single VM uses and needs, but monitoring single
VMs is not advisable in every case because it has noticeable influence on the overall
performance. Often it will be sufficient to monitor only VMs which are critical for your
network. If a VM reaches its capacity limits, PRTG can alert you and you can conduct
according resolution steps like enhancing this VM's resources. Indicators for a healthy virtual
machine which you can monitor with PRTG out of the box are:
VMware: CPU and memory usage, disk read and write speed, read and write latency, and
network usage
Hyper-V: CPU usage, disk read and write speed
Citrix XenServer: CPU usage and free memory
SCVMM: CPU usage, disk read and write speed, and the status of the VM
Virtuozzo: disk space and network usage
VMs from t he "Inside" (Operat ing Sy st ems): You can monitor the Windows operating
system of a single VM with PRTG's standard WMI sensors 309 , for example. With this
technology 2495 you can access data of various Windows parameters. Other operating
systems like Linux/MacOS can make data available via SSH 2498 and SNMP 2491 . The status of the
operating systems on your VMs can indicate potential issues of the same, just like the
operating systems on your physical machines which are important for a reliably working IT
infrastructure: You can monitor these with the same attention, depending on your
application scenario, but be careful due to performance considerations. Especially many WMI
sensors can result in load problems, so monitor only really important systems "from the
inside". Furthermore, you do not need to monitor every item multiple times. For example, it
might be sufficient to monitor free disk space only from the outside of the actual VM.
Monitoring the Virtual Infrastructure

In order to monitor your IT infrastructure, best practice is to set up the monitoring of the
hardware layer of your data center first in PRTG, especially in order to find potential
bottlenecks which might have an impact on your virtual servers. Then you can start monitoring
your virtual environment itself. If you use several solutions for virtual hosting, it is also a good
idea to group related host servers, their virtual machines, and the operating systems together.
The screenshot below will give you an idea about how to organize this.
2516
19.09.2014
Grouped Virtual Components
The screenshot above shows you the particular group "Virtual Hosting" of an entire PRTG
setup. This is an example how monitoring of virtual environments can look like. The sample
group contains several subgroups for the virtualization solutions Citrix "XenServer", Microsoft
"Hyper-V", and VMware "vSphere". The vSphere group, for example, has three subgroups: we
monitor the vCenter VMs and the vCenter Windows system, the performance of the host
server, and the storage system of the host.
Devices for Physical Hosts

In PRTG, set up devices which represent the physical hosts of your virtual machines. For
example, for your VMware hosts, add devices which represent the ESX/ESXi servers, for HyperV add devices which represent your Hyper-V host servers, for Citrix add devices which
represent your Xen servers. If you manage these hosts with a Microsoft System Center Virtual
Machine Manager (SCVMM), you can also (or alternatively) add a device for the SCVMM.
Then you can add suitable and expressive sensors to the host server devices. Running PRTG's
auto-discovery 194 , many useful sensors will be created automatically. There are several preconfigured host hardware sensors available out of the box in PRTG:
19.09.2014
2517

Enterprise Management (WBEM)
1803
: monitors an ESX(i) server via Web-Based
VMware Host Hardware St at us (SOAP) Sensor

Simple Object Access Protocol (SOAP)
Object Access Protocol (SOAP)
1818
1810
: monitors a VMware host server via
: monitors a VMware host server via Simple
Hy per-V Host Sensor 681 : monitors via Windows Performance Counters or Windows
Management Instrumentation (WMI), as configured in the "Windows Compatibility Options" of
the parent device
Cit rix X enServer Host Sensor
365
: monitors via Hypertext Transfer Protocol (HTTP)
SCVMM Host Sensor 1058 : monitors, for example, a Hyper-V host, a VMware host, or a
XenServer host which is managed by a System Center Virtual Machine Manager (SCVMM)
These sensor types monitor hardware specific counters to ensure that no hardware issues
affect your actual virtual machines. Additional sensor types can monitor the host hardware via
SNMP (for example, traffic and custom requests) and SSH (for example, disk space of VMware
ESX(i) servers), as well as there are sensors for network adapters and storage devices which
are connected to a Hyper-V host server. You can also monitor Virtuozzo host servers with
sensors for network usage and disk space for each container.
Devices for Virtual Machines

In order to monitor your actual virtual machines, add them to your host servers in PRTG. For a
better overview, you might want to add another device to PRTG which represents your host
server and add sensors for your VM to there. The according sensors for virtual machines will
show you the performance of single VMs as well as their usage of resources. This will help you
identify VMs with poor performance and react proactively before one or more VMs crash. As
mentioned above, you can additionally monitor your particular VMs from the inside (i.e., the
operating systems on your VMs) if necessary. See the sections below for details about
particular virtualization solutions.
VMware Virt ual Machine

PRTG's VMware Virt ual Machine (SOAP) Sensor 1826 monitors VMs on a VMware host server via
Simple Object Access Protocol (SOAP). With the VMware system, the general idea is to add a
vCenter server as a device to PRTG and use the vCenter as parent device where you add the
sensors to for your virtual machines. So, in the case of vMotion when your VMs change their
host server, PRTG will be able to follow these movements and will never lose the monitored
VMs.
For this sensor type, you need the Microsoft .NET Framework with the latest update of version
4.0 running on the probe machine. If you use many VMware sensors, we also recommend
adjusting the settings on your VMware host server to accept more incoming connections.
2518
19.09.2014
v Sphere Group
This screenshot a sample vSphere group in PRTG. As recommended, the VMware virtual
machines are added to the vCenter device. There is also a dedicated device for the vCenter
Windows operating system with common WMI sensors for CPU, memory, disk, and network
usage. The ESXi host servers are organized in their own groups regarding performance and
storage. In this example, PRTG monitors the hosts with the standard SNMP hardware sensors
as well as with the specific VMware ESXi host sensors.
Microsoft Hy per-V Virt ual Machine

PRTG's Hy per-V Virt ual Machine Sensor 688 monitors VMs via Windows Performance Counters
or Windows Management Instrumentation (WMI), as configured in the "Windows Compatibility
Options" of the parent device. With this hybrid approach, the sensor first tries to query data via
performance counters and uses WMI as a fallback if there are no performance counters
available. Performance counters in general need less system resources than WMI. We
recommend using System Center Virtual Machine Manager (SCVMM) as parent device for this
sensor type, because when your VMs change their physical host with Live Migration, this
sensor will still be able to continue monitoring. You should also disable User Account Control
(UAC) in the Windows operating system of the VM.
19.09.2014
2519
Hy per-V Group
This screenshot shows a sample Hyper-V group in PRTG. There is a dedicated group for failover
clustering where two nodes are monitored with several SNMP and WMI sensors, as well as
Hyper-V Host Server sensors 681 and sensors for the Hyper-V virtual machines. This ensures
that Hyper-V and failover clustering works without any issues. The Hyper-V hosts are
monitored the same way, organized in a dedicated group for hosts.
Note that we recommend adding the particular virtual machines to the SCVMM server if
possible! We pointed out above that you should add the VMs to an SCVMM server to avoid
issues with Live Migration. You can see this in the group "System Center". The particular VMs
are added to the dedicated device "Hyper-V Guests". The SCVMM itself is monitored as
described below.
Cit rix X enServer Virt ual Machine

PRTG's Cit rix X enServer Virt ual Machine Sensor 373 monitors VMs via Hypertext Transfer
Protocol (HTTP). For this sensor type, you have to add a device to PRTG which represents a
Citrix XenServer with version 5.0 or later. Another requirement is the Microsoft .NET
Framework: You have to run the latest update of version 4.0 on the probe machine where you
add this sensor to.
In a XenServer pool, every host knows each running VM. Because of this, there is no central
instance which provides all available data so it does not matter on which host you query your
VMs. All queries on any host are automatically forwarded to the pool master which manages
the XenServer pool. So it is sufficient to create the desired sensors for your XenServer VMs
on a device that represents one host server of your pool. PRTG's XenServer sensors can
figure out by themselves which host is running and retrieve the according data.
2520
19.09.2014
XenServ er Group
This screenshot shows a sample XenServer group in PRTG. There are two devices for
XenServer hosts (Xen 1 and Xen 2), each with a Citrix XenServer Host sensor 365 and several
Citrix XenServer Virtual Machine sensors 373 for the particular VMs on this host. Furthermore,
the Windows operating system is represented as a dedicated device ("virtualcontrol") which is
monitored with several WMI sensors regrading CPU, disk, memory, and network usage.
Microsoft SCVMM Virt ual Machine

With the SCVMM Virt ual Machine Sensor 1067 you can monitor VMs which are managed by a
System Center Virtual Machine Manager (SCVMM), for example, Hyper-V or VMware.
Requirements for this sensor type to work are the Microsoft .NET Framework with version 4.0
and the latest update, Remote PowerShell 2.0, and the VMM PowerShell Plugin. If you add your
SCVMM server to PRTG, PRTG will be able to follow movements of your VMs automatically.
19.09.2014
2521
SCVMM Group
This screenshot shows a group for an SCVMM server in PRTG which manages Hyper-V virtual
machines. The SCVMM server is monitored with the SCVMM Host sensor 1058 which shows
several kinds of server states and usage parameters. Several virtual machines are added to the
"Hyper-V Guests" device (as SCVMM Virtual Machine sensors) so that PRTG can automatically
detect changed VM host devices.
The sensor types described in this section monitor virtual machine specific counters in order
to ensure that all your VMs have enough resources available. If a VM is overloaded, PRTG can
notify you immediately and you can proactively take care of issues before a particular VM has
an outage or other failures. Additionally, we have shown an idea for a structured virtual
monitoring with several recommendations.
You can find all available sensors for virtual servers and the according virtual machines in
section List of Available Sensor Ty pesVirt ual Servers Sensors 311 .
More
Knowledge Base: I run PRTG on VMware. How can I obtain best performance?
2522
19.09.2014
Paessler Blog: Virtualization and Network Monitoring

http://www.paessler.com/blog/2013/04/30/prtg/virtualization-and-network-monitoring
Paessler Blog: Virtualization and Network Monitoring: PRTG Supports the new VMware ESXi
5.5!
http://www.paessler.com/blog/2013/10/01/prtg/virtualization-and-network-monitoring-prtgsupports-the-new-vmware-esxi
2491
Monit oring via WMI
2495
Monit oring via SSH
2498

2502

Monit oring Backups
2505
2507
2512
2514

2515
2524
19.09.2014
2500
2526
2523
Part 10: Sensor Technologies | 11 Monitoring Databases
10.11 Monitoring Databases

Monitoring your databases enables you to ensure that, on the one hand, database queries are
processed in time, and, on the other hand, that the database itself performs within the defined
parameters. Furthermore, database monitoring with PRTG makes it possible to be alerted via a
corresponding sensor status if database queries return an unexpected result value.
PRTG comes with built-in native sensors for the most common databases:
Microsoft SQL servers
MongoDB servers
MySQL servers
PostgreSQL servers
Oracle SQL servers
However, it is possible to monitor many other database servers. For this concern, PRTG uses
the ActiveX Data Objects (ADO) interface in combination with the PowerShell scripting
language.
There are two types of database sensors:
Sensors monit oring dat abases direct ly 2524 : Monitor databases from the user perspective.
These sensors send a request to the database server and receive corresponding values. You
can optionally process data tables and show values in individual channels or monitor
transactions.
Sensors monit oring dat abase performance 2525 : Monitor databases with a more abstract
view on the servers. Usually, these sensors monitor performance counters via Windows
Management Instrumentation (WMI).
Sensors Monitoring Databases Directly

PRTG provides several sensors which can "look into" the content of databases. Sensors of this
type connect to the database server, execute a defined query, and show the execution time of
the whole request and the query. You can use these sensors to process the data table and
show requested values in individual channels.
The following sensor types are available for this kind of monitoring:
My SQL v2 Sensor
833
2524
: Monitor your Microsoft SQL server 2005 or later.
: Monitor your MySQL server version 5.0 or later.

Post greSQL Sensor
804
1001
894
: Monitor your Oracle database server version 10.2 or later.
: Monitor your PostgreSQL database version 7.x or later.
18.11.2014
Part 10: Sensor Technologies | 11 Monitoring Databases
For these sensor types, you can define valid SQL statements that the sensors send to the
database server. Define the queries in an SQL script file and store it into the respective
\Cust om Sensors\sql\ subfolder of your PRTG installation (see section Dat a St orage 2611 for
details). You can select this SQL script when you add the sensor to PRTG. With every scanning
interval 238 , the sensor executes this script with the defined query against the database and
the database returns corresponding values in individual channels. Use the Sensor Channels
Set t ings 2221 to define limits for specific values.
Note: These sensor types need .NET 4.0 or later installed on the computer running the PRTG
probe.
Alternatively, you can monitor almost all available database servers with the ADO SQL Sensor
332 via an ActiveX Data Objects (ADO) connection and a PowerShell script.
Note: Although you can still use the outdated sensor versions for Microsoft SQL 795 , MySQL 824
, and Oracle SQL 884 , we strongly recommend you to use the superseding sensor types ("v2")
for more information, higher stability, and better performance.
Sensors Monitoring Database Performance

Performance sensors for database servers have a more "abstract" view on databases and
regard performance "from the outside". They do not read out any values of the database,
neither do they send SQL queries to databases. This sensor type is only available for Microsoft
SQL and MongoDB servers.
The Microsoft SQL server sensors monitor performance via Windows Management
Instrumentation (WMI). You can manually set up different performance counters for your server
instances, for example, general statistics, access methods, buffer and memory manager, locks,
and SQL statistics. The MongoDB Sy st em Healt h Sensor 817 reads information about
connections and operations via HTTP and the MongoDB admin web console.
Microsoft SQL Server performance sensors are available for Microsoft SQL Server 2008, 2012,
and 2014:
2080
2091
2102
18.11.2014
2525
Part 10: Sensor Technologies | 12 Monitoring Syslogs and SNMP Traps
10.12 Monitoring Syslogs and SNMP Traps

PRTG is utilizable as a full scale syslog server and SNMP trap receiver. Every PRTG installation
includes this functionality so no additional software is needed. This manual section describes a
sample configuration for PRTG's syslog and SNMP trap receiver and gives you an idea about
how to use these features.
Syslog is a well-established standard for computer message logging. Many network devices
support sending syslogs to communicate informational, analysis, and debugging messages
which are intended for network management and security auditing. SNMP traps are
asynchronous notifications from SNMP-enabled devices and can be used to report important
incidents and data, just like syslog messages. Devices trigger these messages for various
reasons, such as system events, outages, critical conditions, and many more.
PRTG provides two dedicated sensor types which work as full scale syslog resp. SNMP trap
receivers:
Sy slog Receiver Sensor
1621
1760
Because both the syslog and the trap receiver are implemented as common sensor types, you
do not need to install software in addition to PRTG (for example, you do not need an extra
syslog server but only the PRTG web server). You can create the Syslog Receiver as well as the
SNMP Trap Receiver sensors in the usual PRTG way via the add sensor 224 dialog. Then
configure your syslog- or SNMP trap-enabled device(s) to send messages to PRTG.
PRTG is able to handle about 10,000 syslog and trap messages per second on a quad core
desktop machine. You can filter the incoming messages by various parameters so that PRTG
will process only specific messages and purge other data right away. Processed messages are
stored in an internal high-performance database on the particular probe machine and are
available for reviewing and analyzing via PRTG's web interface. The main limiting factor for
PRTG's syslog and trap receivers is the hard disk space on the machine running the PRTG probe
with these sensors.
Sample Configuration
Follow the steps below for a sample configuration of Syslog and SNMP Trap Receiver sensors.
You can apply these instructions to both the SNMP Trap Receiver as well as the Syslog
Receiver because the setup works in a similar way for both.
1. Adding the Receivers
2527
2. Configure the Source Devices

3. Collect Messages
2528
4. Review and Analyze Messages

5. Refine the Filters
2529
2530
6. Create Notification Triggers
2526
2527
2531
26.09.2014
St ep 1: Add a Sy slog Receiver or SNMP Trap Receiver sensor t o PRTG.

Both sensor types inherit an implicit filter by the IP address of the parent device. So, on the
one hand, it is possible to add these sensors to a probe device 85 . Then you will receive all
messages from the system running the probe and can optionally filter for specific sources
later. On the other hand, you can add these sensors directly to the source device. Then only
messages from this device will be processed.
Add the receiver sensors to the desired device in the common way, for example, via the
device's context menu 168 . We recommend leaving the sensor's default settings unchanged for
the first configuration (port, include and exclude filter, warning and error filter) to see what
data actually comes in.
Note: Adding the sensor to a network device directly will increase its speed in comparison to a
filter definition in the sensor settings. Distributing Syslog and SNMP Trap Receiver sensors
over different probes will make the overall performance scalable and gives you variability for
the place of data storage 2611 .
the proper sender. For example, if you want to receive syslog or trap messages 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.
Sy slog Rec eiv er Sensor in the Add Sensor Dialog
St ep 2: Configure y our net work device(s) which support sending sy slogs or SNMP t raps
appropriat ely .
Configure your syslog or SNMP trap ready devices to send syslogs or traps (see
documentations of the respective device vendors). They have to address the PRTG probe on
which your Syslog or SNMP Trap Receiver sensor runs. So specify the IP address of the
machine with the respective PRTG probe. If you keep your syslog or trap receiver's default
settings, use the port 514.
26.09.2014
2527
Note: The protocol is User Datagram Protocol (UDP).
Default Sensor Settings: Suffic ient for the First Configuration
St ep 3: St art collect ing sy slog or SNMP t rap messages from y our devices.
You do not have to accomplish any further configuration steps to use PRTG as a syslog server
or SNMP trap receiver. When your device(s) send syslogs or SNMP traps to the specified PRTG
probe machine, the messages will appear automatically in PRTG's web interface. After each
sensor scan (by default inherited from the parent device), PRTG will count the received syslogs
or traps in the according channels (total number of messages during the last interval, error and
warning messages, or dropped packets).
Let the syslog receiver or the SNMP trap receiver collect data for a while to see what comes in.
By default, the respective sensor will go into a Warning status if there was at least one
message with severity 4 and into an Error status if there was at least one message with
severity 3 or lower during the last sensor scan.
Note: Incoming messages are counted per scanning interval, so it might take a few moments
to see the received syslogs/traps, depending on the remaining time until the next sensor
scan. Of course, you can use Check Now via the sensor's context buttons 112 to perform an
immediate scan and see corresponding data. The sensor states are also defined per scan.
So, for example, a message which is classified as error will count for the error channel only for
one scanning interval; if there is no new error message in the following scanning interval, no
message is shown in the error channel anymore and the error status will disappear after the
next sensor scan. The syslog or trap itself will still be accessible on the Messages tab.
2528
26.09.2014
Sy slog Rec eiv er Sensor with Error Messages
St ep 4: Review and analy ze t he collect ed dat a.

All incoming messages which match the include filter are processed and stored in PRTG's
internal high-performance database. Review and analyze the received syslogs and traps via
PRTG's web interface. For details, see the respective manual sections of SNMP Trap Receiver
Sensor 1630 and Sy slog Receiver Sensor 1769 . Then you can decide about further filtering of the
incoming messages.
Note: The received data is also available in PRTG's data folder
is created per hour.
2611
as common files. One data file
Note: For the SNMP Trap Receiver sensor, you can add the Management Information Base (MIB)
files of your device(s) to the \MIB subfolder of PRTG. This will result in Object Identifier (OID)
resolution and makes trap messages more comprehensible.
26.09.2014
2529
Rec eiv ed Sy slogs on the Messages Tab
St ep 5: (Opt ionally ) refine t he filt ers.

In order to enhance the productivity with your PRTG syslog servers and trap receivers, you can
adjust the default filter settings. PRTG provides you a comprehensible formula system that you
can use to describe which kind of messages you want to process and which of them will count
as error or warning messages. You can configure the following filters for received messages in
the settings of the respective receiver:
Include filter: Process and store specific types of messages only.
Exclude filter: Do not process specific types of messages and discard them.
Warning filter: Define rules to categorize received messages as warnings.
Error filter: Define rules to categorize received messages as errors.
Use the syntax which is provided in the corresponding manual sections to define your
individual filter rules: SNMP Trap Receiver Sensor 1629 and Sy slog Receiver Sensor 1768 .
Note: You can create filter rules with a few mouse clicks using the Advanced Filt er on the
Messages tab of a specific sensor and copy these rules into the sensor settings to apply
them.
2530
26.09.2014
Adv anc ed Filter Created on the Messages Tab
St ep 6: (Opt ionally ) creat e not ificat ion t riggers.

By default, the warning and error channels of the Syslog and SNMP Trap Receiver sensors have
a very low upper warning resp. error limit (0.00000001). The reason for this is that even when
only one syslog or trap has been counted in the respective channel during a scanning interval,
the overall status of the sensor will show this with the corresponding status. This way, you will
always recognize if there is something wrong on the monitored system.
Because of this sensor behavior, best practice would be to add a St at e Trigger on the
Not ificat ions 2263 tab of the sensor if you want to get a notification 93 when a warning or
error message type comes in. Define a very low Down or Warning time condition to not miss
any warnings or errors to not miss any messages, for example 0 seconds. Another option
would be a Speed Trigger for notifications regarding messages per second.
Note: You can use syslog and trap specific placeholders in notification templates in order to
see the messages when you receive a notification. See the More 2532 section below for more
information.
26.09.2014
2531
State Trigger for a Sy slog Rec eiv er
More
2532
26.09.2014
2491
Monit oring via WMI
2495
Monit oring via SSH
2498

2502

Monit oring Backups
2505
2507
2512
2514

2515
2524
26.09.2014
2500
2526
2533
Part 11
PRTG Administrator Tool
19.09.2014
2535
Part 11: PRTG Administrator Tool |
11
PRTG Administrator Tool
With the application PRTG Administ rat or that you can launch from the Windows start menu,
you can edit administrative settings that affect your PRTG installation, the local probe running
with it, and remote probe installations. All settings will require a restart of the affected PRTG
Windows services to apply any changes on the configuration. Please see the following
sections for details.
If you start the PRTG Administrator tool on the PRTG core server, you can change settings
which affect your whole PRTG installation and your local probe. If you run the PRTG
Administrator on a system on which a remote probe runs, you can only change settings which
are related to this probe.
Note: You can also change many administrative settings via the Set up 2327 in the PRTG web
interface. For probes, settings are also available on the corresponding tab 259 in the web
interface.
PRTG System AdministratorTopics

2537
2560
Related Topics
Set up
2327
Failover Clust er St ep by St ep
2536
2605
19.09.2014
Part 11: PRTG Administrator Tool | 1 PRTG Administrator on Core Server System
11.1
PRTG Administrator on Core Server System
With the PRTG Administrator program you can define various system-oriented settings that
affect your PRTG installation, as well as restart services and view log information. You can
change many of these settings also via the system administration 2327 in the PRTG web
interface.
Note: To get familiar with the different components of PRTG, we recommend you to read the
Archit ect ure 77 section.
Note: All settings you define here are only valid for the local installation running on the
computer you open the program on. In order to change settings for another installation, for
example, another cluster node installation, please log in to this computer and open the
program there.
Note: This section describes the available settings in the PRTG Administrator when you open
the tool on the PRTG core server system (core resp. web server and local probe related). If
you open this program on a remote probe machine, only probe related settings 2560 are
available.
From the PRTG Net work Monit or group in Windows start menu, please select PRTG
Administ rat or to open the application. You can choose from these options in different tabs:
Web Server
Core Server
Cluster
2538
2541
2542
Administrator
License
2547
2549
Probe Settings for Core Connection

Probe Settings for Monitoring
Service Start/Stop
Logs and Infos
2549
2552
2552
2553
When you close the program with the Ok button after changing settings, you are asked to
restart the core server Windows service and/or probe service in order to save the settings.
Please confirm by clicking the OK button. Otherwise the changes are ignored.
19.09.2014
2537
PRTG Administrator: Restart Serv ic es
Web Server
Edit IPs, ports, access methods, and language for the Ajax
interfaces.
100
and Mobile Web GUI
2483
web
Note: You can change all settings which are on the Web Server tab also via the PRTG web
interface in the User Int erface 2357 settings.
PRTG Administrator: Web Serv er
2538
19.09.2014
WEB SER VER

Select TCP Port for
PRTG's Web Server
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:
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: 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.
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.
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.
Expert Configuration:
SSL Encryption

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.
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.
19.09.2014
2539
WEB SER VER

Expert Configuration:
Web Server Port

above. Enter the desired TCP port number you want the PRTG web
server to run on. Please enter an integer value.
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.
Select IP Address for

PRTG's 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 into PRTG by
simply pointing your browser to the specified IP address.
Choose between:
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.
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
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.
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.
2540
19.09.2014
WEB SER VER

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.
Select System
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 will influence the
language of the Ajax 100 and the Mobile Web GUI 2483 web
interfaces, as well as of the PRTG Administ rat or Tool 2536 .
Core Server
Define settings for the core server.
PRTG Administrator: Core Serv er
19.09.2014
2541
COR E SER VER

Probe Connection
Management
Define how PRTG will handle incoming connections from probes.

Choose between the following options:
Accept connect ions from t he Local Probe only (default
set t ing, does not allow remot e probes): This is the default
setting. Only local probe connections will be accepted by the
PRTG core server. You cannot use remote probes 2588 with this
setting enabled.
Accept connect ions from remot e probes on all IPs: Incoming
connections from remote probes will always be accepted, no
matter on which IP address of the core server they come in.
Accept connect ions from remot e probes on select ed IPs
only : Incoming connections from remote probes 2597 will only be
accepted 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.
Probe Connections
Port
Define on which TCP port number PRTG listens to for incoming

probe connections. Enter a port number. We recommend using the
default value.
Local Storage of Data

Files and Monitoring
Database
Define the data folder to which PRTG will store configuration and
monitoring data. Click on the ... button to choose another folder
on your system.
Note: Before changing the path, make sure you stop both services
and copy all data to the new location.
Click on the Revert t o default folder to reset to default.
Cluster
On the Clust er tab you can manually change how the current core installation will behave in a
cluster. Before changing settings here, please read Failover Clust er Configurat ion 2602
section.
2542
19.09.2014
PRTG Administrator: Cluster
CLU STER
Cluster Settings
Depending on the current cluster settings you will see different

information here.
Clust er Mode: Shows which cluster mode the current
installation is running. This setting is shown for your information
only and cannot be changed here. Possible values are
St andalone (no cluster mode), Clust er Mode: Mast er Node, or
Clust er Mode: Failover Node.
Clust er Port : This field is only shown when PRTG is running in a
cluster mode. This setting is shown for your information only and
cannot be changed here.
Clust er Access Key : This field is only shown when PRTG is
running in a cluster mode. This setting is shown for your
information only and cannot be changed here.
Own Node ID: This field is only shown when PRTG is running in a
cluster mode. This setting is shown for your information only and
cannot be changed here.
19.09.2014
2543
CLU STER
Cluster Mode Actions
Depending on the current cluster settings, you see different active

buttons here. For details, see below.
Follow these instructions to create or join a cluster, or to change its settings:

Creat e a PRTG Clust er...
Start creating a cluster by clicking this button. The current PRTG core server will then be the
Mast er Node of your cluster.
After you click this button, please confirm converting this installation into a master node by
clicking on the Yes button.
Conv erting an Installation into a Cluster Master Node
A new dialog box will appear.
PRTG Administrator: Creating a Cluster Master
Enter a Clust er Port . This is the port on which the internal communication between the
different cluster nodes is sent. Make sure connections between cluster nodes are possible
on the selected port.
2544
19.09.2014
Enter or paste a Clust er Access Key . This is a unique access key. All nodes in a cluster have
to be configured with the same cluster access key in order to join the cluster. Connection
attempts with the wrong access key will be rejected.
Save the Clust er Access Key so you have it at hand when configuring your Failover Node
(s).
After confirming your settings you will be asked to restart Windows services. Please do so in
order for your changes to take effect.
Join a PRTG Clust er...
Add this installation to an existing cluster which already has a Mast er Node, by clicking this
button. The current PRTG core server will then be a Failover Node in the cluster.
Note: This button is also available if you are currently running your PRTG installation in
Clust er Mode: Mast er Node. This option will then change your master node to a failover
node!
After you click this button, confirm converting this installation into a failover node by clicking
on the Yes button.
Conv erting an Installation into a Cluster Failov er Node
A dialog box will appear.
PRTG Serv er Administrator
19.09.2014
2545
Enter the cluster's Mast er IP address/DNS name. It must be reachable from the machine
running the failover node.
Enter the other settings as defined in your Mast er Node's settings. Please make sure you
use the same settings on all nodes in your cluster.
Change PRTG Clust er Set t ings...
If you are running your PRTG installation in cluster mode, you can change the settings here.
A new window will appear.
Please make sure you use the same settings on all nodes in your cluster.
Revert t o St andalone...
If you are currently running your PRTG installation in cluster mode, you can change it to
St andalone mode. If you do so, this node will no longer be part of a cluster.
2546
19.09.2014
Mast er Heart beat
This section is only visible if you are running your PRTG installation in cluster mode. The current
master can execute an external executable file on a regular basis. We call this a "heartbeat".
You can use this, for example, to report the IP address of the current master node to a
dynamic DNS provider, so a DNS name is always redirected to the current PRTG master node in
case the original master node fails and a failover node (running at a different IP address) takes
over the master role.
Choose between:
No heart beat : Do not execute a file on a regular basis.
Run t he following ext ernal execut able file every 5 minut es: Click on the ... button to
choose a file you want to execute. This can be, for example, a command line tool, or a batch
file. It will be executed on the current master node only, with a fixed interval of five minutes.
The interval cannot be changed.
Note: Please make sure the selected file is available under the same (local) path on all failover
nodes. In case one of your failover nodes becomes current master, the heartbeat can only be
executed reliably if the respective executable file exists on all of your failover nodes.
Administrator
Change PRTG System Administrator specific settings.
Note: You can change these settings also in the account settings
Administ rat or user in the PRTG web interface.
19.09.2014
2385
of the PRTG Sy st em
2547
PRTG Administrator: Administrator
LOGIN CR EDENTIALS FOR THE ADMINISTR ATOR ACCOU NT

Email Address
Enter a valid administrator's email address. By default, PRTG will

send notifications and important messages to this address.
Login Name
Enter a name for the PRTG Sy st em Administ rat or login; this is

your default login. You use it when you log into the PRTG web
interface or Windows Enterprise Console.
Note: The default login name is prt gadmin
Password
Enter a password for the PRTG Sy st em Administ rat or login; this

is your default login. You use it when you log into the PRTG Webor Windows Enterprise Console.
Note: The default password is prt gadmin
Confirm Password
2548
If you change your password, re-enter the password for the PRTG
Sy st em Administ rat or login to confirm it.
19.09.2014
License
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 Administrator: Lic ense
To make sure your key has been entered correctly please click on the Check Key button. A
popup box will either show success or denial of your license information. License information
is also checked if you change tabs.
In the Licensed Edit ion field you will see an accepted license key.
Note: You have to use the right edition for your license key. For example, the installer for trial
and Freeware edition does not accept any commercial keys. For more information, please see
Ent er a License Key 57 section.

Define general settings regarding the probe and probe connections.
19.09.2014
2549
PRTG Administrator: Probe Settings for Core Connec tion
PR OBE SETTINGS
Name of Probe
Enter a meaningful name to identify the probe. PRTG shows this

name, for example, in the device tree, and in all alarms by default.
Reconnect Time
Define the time that PRTG will wait until the probe tries to
reconnect to the core server if the connection fails. Please enter
an integer value.
CONNECTION TO PR TG COR E SER VER

These settings will affect how the probe will connect to the core server. A probe is either a
local probe or a remote probe. PRTG will automatically detect the type of probe and show
the correct setting options.
2550
19.09.2014

Server (IPv4 address or
DNS name)
If this probe is configured as the Local Probe of the PRTG core

installation, it will connect to the core via 127.0.0.1 which you
cannot change.
If this probe is configured as a Remot e Probe, enter the IP address
or DNS name of the core server.
Port
Define the Port number under which probe and core server will
communicate. Please enter an integer value. We recommend using
the default value.
Probe GID
The Probe GID is a unique identifier for the probe. We recommend

you to not change it.
Exception: Only if you substitute an existing probe from a different
computer, you have to copy the GID from the old probe to the
new probe. To do so, click on the Edit GID... button and confirm
the warning with Yes. You can then change the value.
Note: You can deny GIDs under Sy st em Administ rat ionCore &
Probes 2380 in the PRTG web interface.
Probe Access Key
You do not need an access key for Local Probe connections.

On a Remot e Probe, the Probe Access Key must match one of
the access keys configured in your PRTG core server installation. If
it does not match, the remote probe will not be able to connect to
the core server. Please see Sy st em Administ rat ionCore &
Probes 2380 section for more information.
Note: Also check allowed and denied IPs there to ensure that the
core server accepts the IP address of the remote probe.
Confirm Access Key
If you enter an access key for a remote probe, enter it in this field
again to assure correctness.
PATH FOR PR OBE DATA STOR AGE

Path
on your system.
19.09.2014
2551

Outgoing IPv4

Outgoing IPv6

section.
Service Start/Stop
You can stop and start PRTG Windows service manually. Click the St op Core Server resp.
St op Probe Service button to stop a service, and St art Core Server resp. St art Probe
Service to start it again. Both actions usually take from a few seconds up to several minutes
to complete. You can also restart the core server and probes via the PRTG web interface
under Administ rat ive Tools 2397 .
Note: If you want to schedule an automatic restart of Windows services for both core server
and probe service, define a schedule on the Set t ings tab of a probe, section Administ rat ive
Probe Set t ings 259 , in the PRTG web interface.
2552
19.09.2014
Logs and Infos

LOG FILES
Open Log Folder...
Open the PRTG Network Monitor data directory on your hard disk
drive to access all log files which PRTG creates.
Send Logs to
Paessler...
Open an assistant to send log files to the Paessler support team.

Please see below for details.
Note: You can send log files more easily with the support bundle
via Cont act Support 2427 in the PRTG web interface.
Open Support Ticket...
This will open the support form on Paessler's webpage in a

browser window. Note: If you need help, we recommend you to
use the Cont act Support 2427 option in the PRTG web interface
instead.
The About section shows information about the version of installed PRTG programs and
copyright.
Send Logs to Paessler

Note: You can send log files more easily with the support bundle via Cont act Support
19.09.2014
2427
in
2553
If you open a support ticket, Paessler support might ask you to send log files for further
analysis. With the Send Logs t o Paessler... button, PRTG will automatically collect, compress,
and send your log files.
SEND LOGS TO PAESSLER

Name
Enter your name.
Email
Enter your valid email address. You can provide any of your
addresses; however, recommended and default is the email
address of your PRTG account.
Ticket No.
This field is optional. If you have already opened a ticket at Paessler

support, please provide the ticket number you received. Your files
will then be associated with your ticket automatically.
Please enter the ticket number starting with PAE followed by four
or more digits, for example, PAE12345. If you do not have a ticket
number, leave this field empty.
2554
19.09.2014

Configuration
Define if your configuration file will be included in the data. PRTG

will remove all passwords from the config file before sending it to
our support team.
Click on the Send button to start data upload. Ensure that FTP and HTTP connections are
allowed on this machine.
PR OBE SETTINGS
Name of Probe

Reconnect Time
an integer value.

DNS name)

cannot change.
Port
the default value.
Probe GID

19.09.2014
2555

Probe Access Key

Confirm Access Key

Path
on your system.

2556
19.09.2014

Outgoing IPv4

Outgoing IPv6

section.
Service Start/Stop
Logs and Infos

LOG FILES
Open Log Folder...
Send Logs to
Paessler...

19.09.2014

instead.
2557
copyright.

2427
in

Name
Enter your name.
Email
2558
19.09.2014

Ticket No.

Configuration

our support team.
19.09.2014
2559
Part 11: PRTG Administrator Tool | 2 PRTG Administrator on Remote Probe Systems
11.2
PRTG Administrator on Remote Probe Systems
If you start the PRTG Administrator program on a system on which a PRTG Remot e Probe 2589
runs, you can define various probe related settings, restart services, and view log information.
You can change many of these settings also via the system administration 2327 and the probe
settings tab 259 in the PRTG web interface.
Note: To get familiar with the different components of PRTG, we recommend you to read the
Archit ect ure 77 section.
Note: All settings made here are only valid for the local installation running on the computer
you open the program on. In order to change settings for another installation, for example,
another remote probe installation, please log in to this computer and open the program there.
Note: This section describes the available settings in the PRTG Administrator when you open
the tool on a PRTG remote probe system. If you open this program on the PRTG core server,
you have also access to settings regarding your whole PRTG installation.
From the PRTG Net work Monit or group in Windows start menu, please select PRTG
Administ rat or to open the application. You can choose from these options in different tabs:
Service Start/Stop
Logs and Infos
2561
2563
2563
2564
When you close the program with the Ok button after changing settings, you are asked to
restart the probe service in order to save the settings. Please confirm by clicking the OK
button. Otherwise the changes are ignored.
PRTG Administrator: Restart Probe Serv ic e
2560
19.09.2014

Define general settings regarding the probe and probe connections.
PRTG Administrator: Probe Settings for Core Connec tion
PR OBE SETTINGS
Name of Probe

Reconnect Time
an integer value.
19.09.2014
2561

DNS name)

cannot change.
Port
the default value.
Probe GID

Probe Access Key

Confirm Access Key

Path
2562
on your system.
19.09.2014


Outgoing IPv4

Outgoing IPv6

section.
Service Start/Stop
19.09.2014
2563
Logs and Infos

LOG FILES
Open Log Folder...
Send Logs to
Paessler...


instead.
copyright.

2564
2427
in
19.09.2014

Name
Enter your name.
Email
Ticket No.

19.09.2014
2565

Configuration

our support team.
2566
19.09.2014
Part 12
Advanced Topics
19.09.2014
2567
Part 12: Advanced Topics |
12
Advanced Topics
In this section, we cover topics that address more advanced PRTG users. If you already gained
some experience with PRTG, you might want to learn more about the topics following.
Advanced Topics
Act ive Direct ory Int egrat ion
2569
2571
2572
Channel Definit ions for xFlow, IPFIX , and Packet Sniffer Sensors
Define IP Ranges
Define Lookups
2578
2579
Regular Expressions
Add Remot e Probe
2587
2588
Failover Clust er Configurat ion

Dat a St orage
2602
2611

2568
2576
2613
2615
19.09.2014
Part 12: Advanced Topics | 1 Active Directory Integration
12.1
Active Directory Integration
PRTG offers a detailed rights management via different user groups. For detailed information
please see User Access Right s 95 .
In order to make user management easier, you can integrate an existing Active Directory into
PRTG in four steps. During this process, you will connect an Active Directory (AD) group with a
user group in PRTG. All members of your AD group will then be able to log into PRTG using
their AD domain credentials.
Note: You cannot add single AD users to PRTG, but only allow access for entire groups. A PRTG
user will be created automatically for each AD user who logs in to PRTG successfully.
Step 1: Prepare Your Active Directory

In your Active Directory, please make sure that users you want to give access to PRTG are
member of the same AD group.
You can also organize users in different groups, for example, one group whose members will
have administrator rights within PRTG, and another one whose members will have read-only
rights within PRTG.
Step 2: Prepare Your PRTG Server

Make sure that the computer running PRTG is member of the domain you want to integrate it
to. You can check this setting in your machine's Sy st em Propert ies (for example, Cont rol
Panel | Sy st em and Securit y | Sy st em, click on Change set t ings link).
Step 3: Add Domain and Credentials (optional) to System Settings

In the PRTG web interface
settings.
100
, switch to the Sy st em Administ rat ionCore & Probes
2382
In the Active Directory Domain field, enter the name of your local domain. Note: You can only
integrate one AD domain into PRTG.
Optional: PRTG will use the same Windows user account used to run the "PRTG Core Server
Service". By default, this is the "local system" Windows user account. If this user does not
have sufficient rights to query a list of all existing groups from the Active Directory, you
should provide credentials of a user account with full AD access by using the Use explicit
credent ials option.
Save your settings.
Step 4: Add a New User Group

Switch to the User Groups tab (see Sy st em Administ rat ionUser Groups
2390
).
Click on the Add User Group button to add a new PRTG user group.
In the dialog appearing, enter a meaningful name and set the Use Active Directory setting to
Yes.
19.09.2014
2569
Part 12: Advanced Topics | 1 Active Directory Integration
From the Active Directory Group drop down menu, select the group of your Active Directory
whose members will have access to PRTG. If you have a very large Active Directory, you will
see an input field instead of a drop down. In this case, you can enter the group name only;
PRTG will add the prefix automatically.
With the New User Type setting, define the rights a user from the selected Active Directory
group will have when logging in to PRTG for the first time. You can choose between Read/
Writ e User or Read Only User (latter is useful to show data only to a large group of users).
Save your settings.
Done
That's it. All users in this Active Directory group can now log in to PRTG using their AD domain
credentials. Their user accounts will use the PRTG security context of the PRTG user group you
just created.
Notes and Limitations

Active Directory users can log in to the web interface 102 using their Windows username and
password (please do not enter any domain information in PRTG's Login Name field). When
such a user logs in, PRTG will automatically create a corresponding local account on the PRTG
core server. Credentials are synchronized every hour.
All requests to the Active Directory servers are cached for one hour, for performance
reasons. If a password is changed in the Active Directory, you must either wait for 1 hour or
clear the cache manually by clicking on the Clear Caches button on the Sy st em
Administ rat ionAdminist rat ive Tools 2397 page in the Set up 2327 menu).
By default, there are not set any rights for the new PRTG user group. Initially, users in this
group will not see any objects in the PRTG device tree. Please edit your device tree object's
settings 141 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 228 .
PRTG only supports explicit group rights. If your AD uses groups which are member of
another group, PRTG will not regard inherited implicit rights of the parent group and
therefore refuse login for members of those groups.
PRTG will ignore AD information about Organizational Units (OUs). These values cannot be
read by PRTG. However, if you use the AD in an auto-discovery group 196 , you can restrict the
search to computers which are part of an OU.
PRTG does not support SSO (single sign-on).
You can integrate only one AD domain into PRTG.
For very large Active Directories, you will see an input field instead of a drop down when you
add or modify a user group. In this case, you can enter the group name only; PRTG will add
the prefix automatically.
2570
19.09.2014
Part 12: Advanced Topics | 2 Application Programming Interface (API) Definition
12.2
Application Programming Interface (API) Definition
The PRTG Application Programming Interface (API) enables you to access monitoring data and
manipulate objects using HTTP requests, run your own written sensors and notifications,
implement Mini Probes, and customize the web interface.
Detailed HTTP API Documentation

An interactive documentation of the API is integrated into your PRTG installation: Login to the
web interface 102 and select Set up | PRTG API from the main menu.
PRTG API Doc umentation
In different tabs, the documentation provides information about:

HTTP API: Access monitoring data and manipulate monitoring objects using HTTP requests
(includes an interactive query builder).
Cust om Sensors: Create your own sensors for customized monitoring.
Cust om Not ificat ions: Create your own notifications to send alarms to external systems.
Mini Probe API: Create your own small probes to get monitoring data from any platform. See
section More 2571 below for sample usages of the Mini Probe interface.
Websit e St y ling: Customize the look and feel of PRTG by adding your own CSS statements.
See section More 2571 below for sample customizations.
You can also have a look at Paessler's PRTG demo installation's API documentation. But only
the documentation that comes with your PRTG installation fits exactly the PRTG version you
are using.
More
API Documentation in Paessler's PRTG Demo Installation
http://prtg.paessler.com/api.htm?username=demo&password=demodemo
Knowledge Base: Can you provide sample CSS, JavaScript, HTML for customizing PRTG's web
interface?
Knowledge Base: Where can I find PRTG Mini Probes which are ready to use?
19.09.2014
2571
Part 12: Advanced Topics | 3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
12.3
Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
Filter rules are used for the include, exclude, and channel definition fields of Packet Sniffer,
xFlow, and IPFIX sensors. They are based on the following format:
field[filter]
Valid Fields for All Sensors

IP
Possible values: IP address or DNS name (see Valid Data Formats
2574
below)
2574
below)
2574
below)
Port
any number
SourceIP
SourcePort
any number
Dest inat ionIP
Dest inat ionPort
any number
Prot ocol
Possible Protocol values: TCP, UDP, ICMP, OSPFIGP, or any number)
TOS
Type Of Service (any number)
DSCP
Differentiated Services Code Point (any number)
Additional Fields for Packet Sniffer Sensors Only

MAC
physical address (see Examples
2575
below)
SourceMAC
physical address
Dest inat ionMAC
physical address
Et herTy pe
Possible EtherType values: IPV4, ARP, RARP, APPLE, AARP, IPV6, IPXold, IPX, or any number
VlanPCP
IEEE 802.1Q VLAN Priority Code Point
VlanID
IEEE 802.1Q VLAN Identifier
2572
19.09.2014
TrafficClass
IPv6 Traffic Class (corresponds to TOS used with IPv4)
FlowLabel
IPv6 Flow Label
Additional Fields for NetFlow v5 and jFlow v5 Sensors Only

Int erface
any number
ASI
any number
InboundInt erface
any number
Out boundInt erface
any number
SenderIP
IP of the sending device. This is helpful if several devices send flow data on the same port,
and you want to divide the traffic of each device into a different sensor channel. Possible
values: IP address or DNS name (see Valid Data Formats 2574 below)
SourceASI
any number
Dest inat ionASI
any number
Additional Fields for NetFlow v9 and IPFIX Sensors Only

Int erface
any number
ASI
any number
InboundInt erface
any number
Out boundInt erface
any number
SenderIP
SourceASI
any number
Dest inat ionASI
any number
MAC
physical address
19.09.2014
2573
SourceMAC
physical address
Dest inat ionMAC
physical address
Mask
"Mask" values represent subnet masks in the form of a single number (number of contiguous
bits).
Dest inat ionMask
"Mask" values represent subnet masks in the form of a single number (number of contiguous
bits).
Next Hop (IP address)
2574
below)
VLAN
"VLAN" values represent a VLAN identifier (any number).
SourceVLAN
Dest inat ionVLAN
Additional Fields for sFlow Sensors Only

Int erface
any number
InboundInt erface
any number
Out boundInt erface
any number
SenderIP
MAC
physical address
SourceMAC
physical address
Dest inat ionMAC
physical address
Valid Data Formats

IP fields support wildcards (*), range (10-20) and hostmask ( /10, /255.255.0.0) syntax, as well
as DNS names.
Number fields support range (80-88) syntax.
2574
19.09.2014
Protocol and EtherType fields support numbers and a list of predefined constants.
For detailed information on IP ranges, please see Define IP Ranges
2578
section.
Examples
All of the following filter rules are valid examples:
SourceIP[10.0.0.1]
SourceIP[10.*.*.*]
SourceIP[10.0.0.0/10]
DestinationIP[10.0.0.120-130]
DestinationPort[80-88]
Protocol[UDP]
MAC[00-60-50-X0-00-01]
DSCP[46]
Complex expressions can be created using parentheses ( ) and the words and, or, or and not .
For example, this is a valid filter rule:
Protocol[TCP] and not (DestinationIP[10.0.0.1] or SourceIP[10.0.0.120-130])
Related Topics
2576
2500
2502
Sniffer sensors?
19.09.2014
2575
Part 12: Advanced Topics | 4 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
12.4
Channel Definitions for xFlow, IPFIX, and Packet Sniffer

Sensors
When adding Custom xFlow sensors, Custom IPFIX, or Custom Packet Sniffing sensors, you will
notice a field entitled Channel Definit ion. In this field you need to provide the channel
definitions in the following syntax (one entry per channel):
#<id>:<Name>
<Rule>
Syntax
<id> needs to be 1 or greater and must be unique for the sensor (i.e., each channel
definition must have a unique ID). Note: The maximum channel ID you can use is 2147483648
(2^31). Higher IDs are not supported. We recommend using channel IDs 1, 2, 3, etc.
The <id> is linked to the historic data: As soon as it has been changed, the history for this
particular channel is lost.
One rule can span multiple lines.
The next rule starts with a # as first character in a line.
<name> is the channel's display name.
The rules are processed top to bottom (the number doesn't matter) and the data is
accounted to the first match.
One Ot her channel is added automatically.
Behind the name a optional [<unit >] can be used to override the automatic unit based on
the source sensors.
The <Rule> syntax is identical to the one described in the Filt er Rules for xFlow and Packet
Sniffer Sensors 2572 section. Since data is accounted to the first match, please make sure to
start with the most specific rule at the top getting less specific to the bottom.
Note: We recommend writing the rule list in an external editor and paste it into the respective
PRTG field. Otherwise, if the rules contain an error, the entries will be removed when adding
the rules in case!
Example
General example:
#5:HTTP
Protocol[TCP] and
(SourcePort[80] or DestinationPort[80] or SourcePort[8080] or
DestinationPort[8080])
Channel definition example for differentiating by protocol:
2576
19.09.2014
Part 12: Advanced Topics | 4 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
#1:TCP
Protocol[TCP]
#2:UDP
Protocol[UDP]
#3:ICMP
Protocol[ICMP]
Related Topics
2572
2500
2502
More
Knowledge Base: Can I add custom channels to standard Packet Sniffer and NetFlow sensors?
19.09.2014
2577
Part 12: Advanced Topics | 5 Define IP Ranges
12.5
Define IP Ranges
In some setting fields, you can either enter a host name or single IP address, or you can define
IP ranges. PRTG follows a common syntax for this. IP ranges are available, for example, for
xFlow and Packet Sniffer sensors 306 , and for probes settings 2379 .
Note: For the syntax available for PRTG's automatic network discovery, please see Aut oDiscovery 196 (IP Selection Method setting).
Available Options
Opt ion
Descript ion
Sy nt ax
Example(s)
Simple
Enter a fixed IP
address.
a.b.c.d
10.0.10.9
Hostname
Enter a hostname.
PRTG will resolve it to
an IP address in your
network.
hostname
device-xyz
Enter a hostmask. A
hostmask defines the
relevant bits of the IP
address.
a.b.c.d/h or
a.b.c.d/e.f.g.h
10.0.0.0/255
a.b.c.d
10.0.0.1-20 or
10.*.0.* or 10.0.050.*
Hostmask
Range
Enter an IP address
range. Please replace
each of a, b, c, d by
either
* (asterisk) for any
value; corresponds
to 0-255
or
x-y for any range
between 0 and 255.
2578
19.09.2014
Part 12: Advanced Topics | 6 Define Lookups
12.6
Define Lookups
PRTG uses lookups for some sensor types with custom channels. In general, lookups map
status values as returned by a device (usually integers) to more informative expressions that
show you the status of a monitored device as a clear message. Additionally, lookups can
define the sensor status 121 that will be shown for certain status codes (similar as sensor
channel limits 2221 can define a sensor status, too). For example, for a printer, PRTG can show a
sensor in a yellow Warning 121 status with channel values like "Toner Low" instead of simple
status codes.
Lookups can be customized individually; you can define your own texts that will be shown in a
sensor's channel. See section Cust omizing Lookups 2583 below.
Note: If a channel uses lookups, we strongly recommend you to control the sensor status
only via the lookup definition and not to use channel limits! See also section Sensor Channels
Set t ings 2221 .
Note: Lookups do not change data in PRTG's database, but they merely change the way sensor
channels are shown. Any change to lookup definition files will apply to historic data as well as
to live data.
Requirement: Channel Unit "Custom"

All channels with enabled Value Lookup need to use the channel Unit "Custom". For details,
refer to section Sensor Channels Set t ings 2221 .
Gauges of Lookup Channels

PRTG can display gauges for channels which use lookups. We recommend staying below 120
lookup values in order to display informative gauges for primary channels. Non-primary
channels have an upper limit of around 40 lookup values.
A Gauge Showing the Status of a Lookup

Channel
Lookups Directory and Format

Lookups are defined in XML format in files ending in .ovl. PRTG's standard lookup files are
located in the PRTG program directory 2611 in a sub folder named lookups. These files are
maintained by PRTG itself. In each of the files lookups are defined for one or more sensors.
Furthermore, the lookups folder contains a sub folder named cust om to store your
customized lookups.
19.09.2014
2579
The files follow a basic principle. For each numeric value you can define:
A message that will be looked up and shown instead of the value
The status the sensor will show
Example
The following code illustrates the lookup definition for the toner status of the SNMP HP
LaserJet Hardware 1309 sensor:
<?xml version="1.0" encoding="UTF-8"?>
<ValueLookup id="oid.paessler.hplaserjet.tonerstatus" desiredValue="1" xmlns:xsi="http://www.w3.org/2001/XM

<Lookups>
<SingleInt state="Ok" value="0">
Toner Okay
</SingleInt>
<SingleInt state="Warning" value="1">
Toner Low
</SingleInt>
<SingleInt state="Error" value="2">
No Toner Cartridge Loaded
</SingleInt>
</Lookups>
</ValueLookup>
The schema in the example provides an insight how lookups are defined:
The <?xml> tag in the first line defines the content as XML.
The <ValueLookup> tag in the second line contains:
The ID which will be shown in the Sensor Channels Set t ings
2220
The desiredValue 2584 attribute contains the value which will be used for the calculation of
the "Coverage". In this example, 1 is defined.
The xsi attributes refer to PRTG's predefined XML schema definitions (which allow easy
editing of lookup files with supported editors). We recommend using the default value.
Between the tags <Lookups> and </Lookups> the particular lookups for the sensor data
are defined:
A lookup entry starts with a tag containing the type of the status value, the lookup type
(in this example, this is always <SingleInt >).
Separated by whitespace, the st at e attribute defines the status the sensor will show.
Allowed values are: Ok, Warning, Error, and None ("None" will not trigger a status change).
The value attribute defines which numeric value will trigger the lookup. This is the value
that PRTG will receive from the device.
2580
19.09.2014
The t ext defines the substitution text that will be shown instead of the value. For
example, this can be a status message.
The same way all other possible lookups are defined. The lookup definitions are closed by
the tag </Lookups>. The file closes with </ValueLookup>.
In our example, the lookup file will have the following effect:
Value as
Report ed from
HP Print er
Value Shown in PRTG (Sensor

Channel)
Sensor St at us Shown by PRTG
Toner Okay
Up
Toner Low
Warning
Down
The XML Schema

An overall schema of the XML files containing the lookups definitions can be sketched like
this:
<ValueLookup id="..." desiredValue="..." xmlns="..." xsi="...">
<Lookups>
<SingleInt state="..." value="...">
status text
</SingleInt>
<BitField state="..." value="...">
status text
</BitField>
<Range state="..." from="..." to="...">
status text
</Range>
[several other lookup definitions]
</Lookups>
</ValueLookup>
19.09.2014
2581
Element
Descript ion
At t ribut es, Value Assignment ,

and Cont ent
<?xml>
content
This is the XML declaration.

Every XML file begins with it.
version and encoding are

"1.0" resp. "UTF-8"
content:
<ValueLookup>contentValueL
ookup</ValueLookup>
<ValueLookup>
contentValueLookup
</ValueLookup>
id: specifies how the name of

Defines the ID of the channel,
the lookup file is shown in the
what desiredValue is used, and
Sensor Channels Set t ings 2220
links to PRTG's predefined
schema definitions, which
desiredValue 2584 : please see
allow easy editing of lookup
below
files with supported editors.
xmlns:xsi/xsi: refers to
predefined XML schema
definition
contentValueLookup: lookup
definitions
<Lookups>contentLookups</
Lookups>
<Lookups>
contentLookups
</Lookups>
Defines the particular lookups

for the sensor data.
contentLookups: one or more

lookup entries, see below
<SingleInt >
status text
</SingleInt >
Each element defines one

lookup entry. There can be
one or more entries in this
format. SingleInt, BitField, and
Range are lookup types 2584 .
st at e: defines the state the

sensor will show; allowed
values: Ok, Warning, Error,
None
<Bit Field>
status text
</Bit Field>
<Range>
status text
</Range>
value: defines the value which

triggers the lookup. Please
enter an integer value. Note:
Range needs always both
values "from" and "to".
status text: defines a st at us
t ext that will be used as
substitution text and shown
instead the integer value. For
example, a status message.
Since all the XML files containing lookup definitions are delivered in a pre-given schema as
indicated above, it will be easy and comprehensible for you to customize lookups.
2582
19.09.2014
Customizing Lookups
There is a subfolder named \lookups\cust om located in the PRTG program directory 2611 . In
order to customize existing lookups, copy the desired lookup file from the lookups folder to
the cust om folder or create a new .ovl file there. When using the same ID in the ValueLookup
tag, the files in the \lookups\cust om folder will have a higher priority than the original files in
the lookups folder. This way, your customizations will be handled preferably by PRTG instead
of the original lookup settings. If you want to use custom lookup definitions in addition to the
existing lookups, define a new ID in the lookup file which is not used by another lookup file.
PRTG identifies lookup definitions via this ID, it does not use the file name.
Open the file with an XML or text editor and adjust the lookups to your personal preferences.
You can define your own messages as well as you can customize sensor states for the
particular return values. For example, if you do not want an "Error" status (i.e. a sensor Down
status) for the return value "2" but only a warning, then you can replace "Error" with "Warning".
Note: The possible states are given in the LookupSt at e.xsd file in the custom directory.
Following the schema of the XML files that are delivered with PRTG enables you to edit the
lookups in a safe way.
Example for Lookups Cust omizat ion

For example (just for illustration purposes), imagine you would like to add the status "None" to
the example 2580 above and change the status for the return value "2" from "Down" to "Warning".
Then do the following:
Copy the file oid.paessler.hplaserjet.tonerstatus to the \lookups\cust om subfolder of your
PRTG installation.
Open this file with an editor.
Leave the ID value unchanged to prioritize the customized lookup to the original file.
Replace "Error" with "Warning" for value "2".
Add a a "SingleInt" element with status "None" for the (hypothetical) return value "3".
Save the file and reload
2585
the custom lookup folder in PRTG.
The customized lookup file will finally look like this:
19.09.2014
2583
<ValueLookup id="oid.paessler.hplaserjet.tonerstatus" desiredValue="1" xmlns:xsi="http://www.w3.org/2001/XM

<Lookups>
<SingleInt state="Ok" value="0">
Toner Okay
</SingleInt>
Toner Low
</SingleInt>
</SingleInt>
<SingleInt state="None" value="3">
Unknown status of toner
</SingleInt>
</Lookups>
</ValueLookup>
desiredValue Attribute
It is necessary to define a desiredValue in the lookup files. The desiredValue corresponds to a
status value triggering a lookup. PRTG calculates the percentage of time this specific state has
been monitored. The result is displayed for all data tables and graphs that show averaged
values.
Considering the example above where the desiredValue is "1", PRTG will calculate the
percentage of time the toner status has been "Warning". If in a time span of five minutes four of
five sensor scans returned a "Warning" status, PRTG would show an average of 80% for this
time span, because in 80% of the time the sensor showed a "Warning".
Lookup Types: SingleInt, BitField, Range

Beside the lookup type SingleInt as seen above, there are two other lookup types: Bit Field
and Range. Using these types you can define lookup values beyond simple integers.
2584
19.09.2014
Lookup Ty pe
Descript ion
Sy nt ax
SingleInt
Uses an int eger to define a

lookup for one status value.
value="int"
Uses a bit field for multiple

status values.
Should only be used if you have

basic knowledge about
bitmasks. Please see More 2586
below for a general
introduction. Note: Every value
has to equal a power of two
(e.g., 1, 2, 4, 8, 16, 32, 64, etc.).
BitField
Range
from="int" to="int"
Uses an inter range from-t o
to define a lookup for several
status values.
Note: Using ranges, the

parameters "from" and "to" always
have to be defined. If you want
to query only one single value in
a range file, this value must be
set as parameter for "from" and
"to" (e.g., from="2" to="2").
Note: You can use only one kind of lookup type in one lookup file. For example, only
SingleInts, BitField, or Ranges. Different lookup types in one file are not allowed.
Define Lookup Files in Sensor Channel Settings

For each sensor with a custom channel you can define a lookup file that will be used. This is
done in a sensor's channel settings with an option called "Value Lookup". This option is visible
for many SNMP sensors, some applicat ion sensors, and always for the following sensor
types:
EX E/Script Sensor
483
EX E/Script Advanced Sensor

SNMP Cust om Sensor
494
(if a Cust om unit is defined)
1243
For details, please see the Sensor Channel Set t ings
2220
section.
Loading Lookups
You can (re)load the defined lookups in the custom folder by clicking the Load Lookups
button. This button can be found in PRTG under Set up | Sy st em Administ rat ion |
Administ rat ive Tools 2396 .
19.09.2014
2585
DebuggingWhat will happen if...?

A return value is defined in the lookups that never will be returned by a device because the
value is not assigned: The value will never be triggered, so PRTG will simply ignore this entry.
PRTG receives a return value that is not defined for lookups: No substitution message can be
found. PRTG will just show the return value.
Different lookup types are in one lookup file: This is not allowed and PRTG will discard this
lookup definition. If you use miscellaneous lookup types in one file, for example, ranges and
singleInts together, the PRTG system will create a ticket when loading lookups or restarting
the PRTG server with the following error message: Value lookup file "[...]" could not be
loaded ("" is not a valid integer value)".
Incorrect XML code: PRTG will create a new ticket when loading lookups or restarting the
PRTG server with a corresponding error message and discard this lookups definition.
More
Wikipedia: Masks (computing)
http://en.wikipedia.org/wiki/Bit_mask
2586
19.09.2014
Part 12: Advanced Topics | 7 Regular Expressions
12.7
Regular Expressions
For some sensors, you can use regular expressions to match a search pattern. PRTG will use
PCRE-RegExp. In the following, we will provide examples for the most common patterns.
Common Search Patterns

Find matches containing the word error or alarm:
\b(error|alarm)\b
Find matches containing the words error and alarm in any order:
(?=.*\berror\b)(?=.*\balarm\b).*
Find matches containing all of the words t ree, flower, leaf, and bug, in any order:
(?=.*\btree\b)(?=.*\bflower\b)(?=.*\bleaf\b)(?=.*\bbug\b).*
Example
The search pattern
(?=.*\berror\b)(?=.*\balarm\b).*
will match the following expressions:

alarm error
error alarm
I am an error and I evoke an alarm
I am an alarm and I indicate an error
An alarm combined with an error indeed!
An error combined with an alarm, too!
More
Regex Tester: Test Regular expressions interactively
http://www.regexpal.com
Wikipedia: Regular expression
http://en.wikipedia.org/wiki/Regular_expression
19.09.2014
2587
Part 12: Advanced Topics | 8 Add Remote Probe
12.8
Add Remote Probe
To monitor different sub-networks that are separated by a firewall, to keep an eye on remote
locations, or for several other scenarios, you can extend your monitoring by installing one or
more Remot e Probes.
Monitoring Remote Loc ations v ia Remote Probes
Extend Your Monitoring Now

Installing remote probes is easy and done in a few minutes. Please see the sections linked
below for further instructions.
Background: Remot e Probes and Mult iple Probes
Installing: Remot e Probe Quick Inst all
Step by Step: Remot e Probe Set up
2589
2592
2597
More
Video Tutorial: Core Server and Remote Probes
http://www.paessler.com/support/video_tutorials/distributed_monitoring
2588
19.09.2014

1 Remote Probes and Multiple Probes
12.8.1 Remote Probes and M ultiple Probes

Upon installation, PRTG creates the first probe automatically, called the Local Probe. It runs on
the same machine as the PRTG core server and monitors all devices from this system, using the
sensors you have configured. Working with only one local probe should suffice for Local Area
Network (LAN) monitoring and if you want to monitor one location only.
Scenarios Requiring Remote Probes

However, there are several situations making it necessary to work with Remot e Probes in the
same LAN or in remote locations. Among these situations are the following:
You have more than one location and you need to make sure that services are available from
all locations.
Your network is separated in several LANs by firewalls, and the local probe cannot monitor
specific services across the firewalls.
You need to monitor systems in a Virtual Private Network (VPN) across public or in-secure
data lines.
You want to sniff packets on another computer.
You want to monitor NetFlow data on another computer.
You experience performance issues with CPU intensive sensors like packet sniffer or
NetFlow sensors and need to distribute the load over more than one PC.
The following chart shows an example for a remote probe scenario.
Monitoring a Distrubuted Network with PRTG (Illustration Also Av ailable as Video Tutorial)
The PRTG core server inside the Corporate LAN (bottom right) is able to monitor:
Services inside the Corporate LAN using the Local Probe.
Services behind a firewall in the Corporate LAN using Remot e Probe 1.
Secured services inside the Branch Office (top left) using Remot e Probe 2.
19.09.2014
2589

Secured services on Mail Server and Web Server using Remot e Probe 3 and Remot e Probe
4 installed directly on these servers.
Public services on the internet using any of the probes.
How Probes Work

As soon as a probe is started, it automatically connects to its core server 78 , downloads the
sensor configuration, and begins its monitoring tasks. The core server sends new
configuration data to a probe as soon as the monitoring configuration is changed by the user.
Probes monitor autonomously and send the monitoring results back to the core server for
each check they have performed.
If the connections between core and probe fails for any reason (for example, a reboot of the
computer running the core server) the probe continues its monitoring and stores the results.
During a connection loss a buffer stores a maximum of 500,000 sensor results in RAM memory
of the remote probe system (up to 50 - 200 MB). This means that for 100 sensors with one
minute interval the monitoring results of up to 3 days can be buffered (or 52 minutes for
10,000 sensors with one minute interval). The probe automatically reconnects to the core as
soon as it is available again and transmits all monitoring results gathered during the connection
loss.
The connection between probe and core is initiated by the probe, secured using Secure
Sockets Layer (SSL). This means that the data sent back and forth between core and probe is
not visible to someone capturing data packets. The core server provides an open TCP/IP port
and waits for connection attempts from probes. If a new probe connects for the first time, the
administrator will receive a ToDo ticket 148 and will then see the new probe in the device tree.
As a security precaution, the probe must be manually acknowledged by the administrator in
the device tree before any sensors can be created and monitored. The administrator can also
deny a probe which will then be disconnected. No further connection attempts will be
accepted and the probe IP is added to the Deny IPs list in the probes system settings (see
Sy st em Administ rat ionCore & Probes 2379 section). This ensures that unauthorized probes
cannot connect to a core server.
Because the probe initiates the connection, you must ensure that a connection can be
established from the outside world onto your core server. For example, you may need to
open any necessary ports in your firewall and you may need to specify a Network Address
Translation (NAT) rule for your network. The process is the same as if you wanted to allow
access to the web server provided by the PRTG core server via port 443, for example. Usually
it is sufficient to open or forward TCP port 23560 (default) on the machine that runs the core
server; on probe side it is not necessary to open any port in most cases.
Automatic Probe Update

Whenever a new version of PRTG is installed on the core server, all remote probes will
automatically download and install the updated version of the probe as soon as they
reconnect to the updated core installation.
2590
19.09.2014

The local probe has already been updated during the core installation. All remote probes are
automatically downloading the new binaries using the SSL-secured probe/core connection.
The download of the 4 MB file takes between a few seconds (in a LAN) and a few minutes (via
internet connections), depending on the available bandwidth. As soon as the update has been
downloaded the probe disconnects, installs the update and reconnects to the core server.
This takes between 20 and 100 seconds. Please note that during the update phase the
monitoring of the local probe can be affected due to the bandwidth required for the
downloads.
More
Remot e Probe Quick Inst all
Remot e Probe Set up
2592
2597
19.09.2014
2591

2 Remote Probe Quick Setup
12.8.2 Remote Probe Quick Setup

PRTG provides an easy, semi-automatic install mechanism for a new Remote Probe. You can
perform a remote installation of a probe directly in PRTG's web interface by right-clicking on a
device in the PRTG device tree. Note: This is an experimental feature. It is possible that direct
installation does not work in all situations. In this case, please see Debugging 2596 and Remot e
Probe Set up Using Inst aller 2597 .
In order to install a Remote Probe directly from the web interface, follow the steps below:
Step 1: Meeting Requirements
Step 2: Preparing Core Server
Step 3: Providing Credentials
2592
2592
2594
Step 4: Installing Remote Probe
2594
Step 5: Approving New Remote Probe
2595
Please look carefully at the requirements in the first three steps.
Step 1: Meeting Requirements

There are some conditions which have to be met in order to install a probe remotely on
another computer. Please ensure the following:
The target computer must be running with operating system Windows (7 or later).
The target computer must be accessible through Remote Procedure Call (RPC). This is usually
the case when your PRTG server and the target computer are located in the same LAN
segment. Otherwise, open Windows services.msc on the target computer. Start the Remote
Procedure Call (RPC) service.
You cannot install a remote probe on a probe device.
You have to permit programs to communicate through your Windows Firewall. Open the
settings of your Firewall and choose Allow programs t o communicat e t hrough Windows
Firewall. Mark the checkbox for Remot e Service Management , and the checkbox Public in
the corresponding line.
You cannot install a remote probe on the computer where PRTG's Core Server runs.
The IP address setting for probe connections to the core server must not be 127.0.0.1.
Please see Step 2 2592 how to prepare the Core Server.

Before remote probes can connect to the core server, you have to edit the relevant settings
in Sy st em Administ rat ionCore & Probes 2379 .
By default, a core server accepts connections from t he Local Probe only (this is, IP address
127.0.0.1). This setting does not allow for remote probes. It is the most secure setting. In
order to allow external probes to connect, please choose Set up | Sy st em Administ rat ion |
Core & Probes from the main menu, and in the Probe Connect ion IPs section, choose one of
the following options:
2592
19.09.2014

All IPs available on t his comput er: We recommend using this setting for easy setup (this is,
IP address 0.0.0.0).
Specify IPs: Specify the IP addresses that will accept incoming connections.
As Probe Connect ion Port , you can leave the standard port number, even when configuring
several probes. Please make sure this port is not blocked by firewall rules on your core
server's side.
Probe Connec tion Settings in Sy stem Administration
When you are done, click Save to save your settings. The core server process must be
restarted so that the changes take effect.
users of PRTG's web interface, of the Ent erprise Console 2430 , or of Smart phone Apps 2486 will
be disconnected. After clicking on the Save 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
For detailed information about these settings, please see Sy st em Administ rat ionCore &
19.09.2014
2593

Step 3: Providing Credentials

If not done yet, add a device 284 to PRTG that represents the target computer where you want
to install the remote probe on. You have to set the correct Windows credentials for this
device.
Open the Device Set t ings
284
In the Credent ials for Windows Sy st ems section, provide Domain or Comput er Name,
Username, and Password for the target computer.
You can also inherit
88
the credentials from its parents' settings.
Please make sure that this user account has administration rights on the target computer.
Step 4: Installing Remote Probe

In the device tree overview, open the context menu
168
of the target device.
Choose Device Tools > Inst all Remot e Probe....

The install assistant will appear on a new page.
Remote Probe Installation Assistant
The install assistant is divided into four sections:
2594
19.09.2014

Experimental feature notice and short introduction

Det ails: overview about the device, this is, name, status, priority, parent probe, parent
group, and sensor states in place with their number
Prerequisit es: for details, see Step 1
2592
St art Probe Inst allat ion: time estimation for installation and installation start button
If prerequisites are not met, you cannot start the installation process. Open requirements will
be highlighted in red. Please correct these to continue!
Installation Unable to Start bec ause Prerequisites Are Not Met
If all prerequisites are met, you can install the remote probe on the target computer by clicking
the button Inst all Remot e Probe on "[device name]". Wait until the process has ended. If
installation was successful, the following message will appear in the St art Probe Inst allat ion
section: Done. Result is: OK.
Note: Every time you start an installation, no matter if it is successful or not, a key will be
added automatically to Access Key s in Sy st em Administ rat ionCore & Probes 2379 .
Step 5: Approving New Remote Probe

If installation was successful, further instructions are given after the result message. As
indicated, go back to the device tree 109 and acknowledge the new probe. The approval button
will appear at the bottom of the devices list. You will also get a new ToDo ticket 149 .
Approv ing New Remote Probe
Click on Approve new probe to acknowledge the created remote probe. You can also discard
the new probe by clicking Deny new probe.
19.09.2014
2595

Note: When denying or removing a remote probe, this device's global ID (GID) will be entered
to Deny GIDs in Sy st em Administ rat ionCore & Probes 2379 .
Note: Denying the remote probe in the PRTG device tree does not uninstall the probe, but only
denies access to the core server. The probe will continue to run on the target system until
you uninstall it manually.
After approving, the approval button will turn into a Working status. Please wait while the
probe connects. Once approved, PRTG automatically creates a set of sensors for the probe to
ensure that bottle-necks on the probe will always be noticed. We recommend keeping these
sensors. You are able now to create groups, devices and sensors for monitoring via the new
probe.
Debugging
Please be aware that installing a remote probe from PRTG's web interface is an experimental
feature. Thus, it can be the case that this approach is not possible in all situations.
However, please follow the steps of this chapter closely when encountering problems with the
Remote Probe Quick Install. Especially consider the conditions as described in Step 1 2592 of this
chapter like Windows Firewall settings.
If the quick installation procedure described in this section does not work with your setup,
please install your remote probes manually; see section Remot e Probe Set up Using Inst aller
2597 .
2596
19.09.2014

3 Remote Probe Setup Using Installer
12.8.3 Remote Probe Setup Using Installer

This section will guide you through the steps to set up a remote probe using the Remote
Probe Installer. For a semi-automatic installation of a Remote Probe directly from PRTG's web
interface, see section Remot e Probe Quick Set up 2592 .
2597
Step 2: Download and Install Remote Probe
2599
Step 3: Configure Remote Probe Connection
2599
Step 4: Approve New Probe and Start Monitoring

Debugging Probe Connection Problems
2600
2600
There are preparations to do on the core server, so it accepts incoming remote probe
connections. Then you log in to the computer you want to install the remote probe on,
download the installer from your PRTG web interface, and install it.

Before remote probes can connect to the core server you must edit the relevant settings in
the Sy st em Administ rat ionCore & Probes 2379 . Login to the Ajax web interface 102 . From
the main menu, select Set up | Sy st em Administ rat ion | Core & Probes to access the probes
settings.
By default, a core server accepts connections from t he Local Probe only (this is, IP address
127.0.0.1). This setting does not allow for remote probes. It is the most secure setting. In
order to allow external probes to connect, please choose Set up | Sy st em Administ rat ion |
Core & Probes from the main menu, and in the Probe Connect ion IPs section, choose one of
the following options:
All IPs available on t his comput er: We recommend using this setting for easy setup (this is,
IP address 0.0.0.0).
Specify IPs: Specify the IP addresses that will accept incoming connections.
As Probe Connect ion Port , you can leave the standard port number, even when configuring
several probes. Please make sure this port is not blocked by firewall rules on your core
server's side.
19.09.2014
2597

Probe Connec tion Settings in Sy stem Administration
From the Access Key s field, copy one access key you will use for the remote probe
connection. You can also enter a new access key with arbitrary signs and length if you like.
In any case save the correct access key for later use.
In the Allow IPs field, enter the IP address of the computer you will install a remote probe on.
To make things easier, you can also enter the word any ; this will set the core server to
accept remote probes connecting from any IP address. Note: If you use any , please make
sure you write the word in lower case only! Any other variations will not be recognized!
Make sure the IP address of the computer you will install a remote probe on is not listed in
the Deny IPs field.
When you are done, click Save to save your settings. The core server process must be
restarted so that the changes take effect.
users of PRTG's web interface, of the Ent erprise Console 2430 , or of Smart phone Apps 2486 will
be disconnected. After clicking on the Save 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
For detailed information about these settings, please see Sy st em Administ rat ionCore &
2598
19.09.2014

Step 2: Download and Install Remote Probe

From the computer you want to install a remote probe on, connect to the Ajax web interface
102 , download the setup file, and install it. For detailed instructions, please see Inst all a PRTG
Remot e Probe 62 section. Note: You cannot install a remote probe on a system already
running a PRTG core installation.
At the end of the remote probe installation the PRTG Administ rat or Tool
(or you can start it manually from the Windows start menu later).
2536
will be started
Step 3: Configure Remote Probe Connection

In the PRTG Administ rat or 2560 on the Windows system you have installed the remote probe
on, configure the connection to the core server.
Remote Probe Settings in PRTG Administrator
In the Connect ion t o PRTG Core Server section, you can then edit the following settings:
Server: Enter the IP address or DNS name of the core server the remote probe will connect
to. If Network Address Translation (NAT) is used, this must be the IP address that is externally
visible, as the remote probe will connect from outside of your network.
19.09.2014
2599

Port : Enter the port number the remote probe will connect to on the core server. This
number must match the one set in Step 1 2597 .
Probe Access Key and Confirm Access Key : Enter the access key the probe will send to
the core server. You have saved this key in Step 2 2599 . This key has to match exactly the one
shown in the web interface's probes settings, so a connection can be established.
For detailed information about these settings, see PRTG Administ rat or
Ok button to confirm your settings and to start the probe service.
2560
section. Click the
Step 4: Approve New Probe and Start Monitoring

When a new probe connects to the core server for the first time, a new ToDo ticket 149 will be
created and the probe will show up as a new object in the device tree of your setup.
Please click on Approve new probe to fully enable the probe. You have to do this once for
every new probe. Once approved, PRTG automatically creates a set of sensors for the probe to
ensure that bottle-necks on the probe will always be noticed. We recommend keeping these
sensors. You can now create groups, devices and sensors for monitoring via the new probe.
You can also discard the new probe by clicking Deny new probe.
Note: When denying or removing a remote probe, this device's global ID (GID) will be entered
to Deny GIDs in Sy st em Administ rat ionCore & Probes 2379 .
Note: Denying the remote probe in the PRTG device tree does not uninstall the probe, but only
denies access to the core server. The probe will continue to run on the target system until
you uninstall it manually.
Debugging Probe Connection Problems

If you have trouble with the setup of remote probes please look at the probe's log files.
The probe process writes log files with a file name in the format PRTG Probe Log (x).log.
Please open the one with the most recent date.
For a correct connection the probe log should look similar to this:
11.08.2012 16:15:15 PRTG Probe Server V12.3.2.5101
11.08.2012 16:15:15 Starting Probe on "WINXPVMWARE"
11.08.2012 16:15:15 Data Path: C:\documents and settings\All Users\a[...]
11.08.2012 16:15:15 Local IP: 0.0.0.0
11.08.2012 16:15:15 Core Server IP and Port: 10.0.2.167:23560
11.08.2012 16:15:15 Probe ID: -1
11.08.2012 16:17:01 Connected to 10.0.2.167:23560
11.08.2012 16:17:06 Login OK: Welcome to PRTG
2600
19.09.2014

If the connection fails, for example, due to an incorrect Access Key , or due to incorrect IP
settings (see St ep 2 2599 ), you will see:
11.08.2012 16:31:02 Try to connect...
11.08.2012 16:31:02 Connected to 10.0.2.167:23560
11.08.2012 16:31:07 Login NOT OK: Access key not correct!
19.09.2014
2601
Part 12: Advanced Topics | 9 Failover Cluster Configuration
12.9
Failover Cluster Configuration
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.
Illustration of a Single Failov er Cluster
For setting up a cluster you need two or more servers and there is one core installation 51
necessary on each of themwith different settings configured for each type of node. In return,
you benefit from seamless high-available monitoring with automatic failover and/or multilocation monitoring.
In a cluster, you can run:
1 Mast er Node
On the master node, you set up your devices and configuration. Also notifications, reporting,
and many other things are handled by the master node.
Up t o 4 Failover Nodes
You can install one, two, three, or four additional nodes for fail-safe, gapless monitoring. Each
of these nodes can monitor the devices in your network independently, collecting their own
monitoring data. The data can be reviewed in a summarized way, enabling you to compare
monitoring data from different nodes.
Note: During an outage of one node, you will see data gaps for the time of the outage on that
node. However, data for that time span will still be available on all other cluster nodes.
Before Getting Started

Configuring a cluster with one failover node is the most common way to set up a seamless
network monitoring with PRTG. You will need two servers running any Windows version (Vista
or later); your servers can be real hardware (recommended!) or virtual machines.
Please make sure the following:
Your servers must be up and running.
Your servers must be similar in regard to the system performance and speed (CPU, RAM
memory, etc.).
2602
18.11.2014
In a cluster setup, each of the cluster nodes will individually monitor the devices added to
the Clust er Probe. This means that monitoring load will increase with every cluster node.
Please make sure your devices and network can handle these additional requests. Often, a
larger scanning interval for your entire monitoring is a good idea. For example, you could set
a scanning interval of 5 minutes in the Root Group Set t ings 228 .
We recommend installing PRTG on dedicated real-hardware systems for best performance.
Please bear in mind that a server running a cluster node may in rare cases be rebooted
automatically without notice (e.g. for special software updates).
Both servers must be visible for each other through the network.
Communication between the two servers must be possible in both directions. Please make
sure that no software- or hardware firewall is blocking communication. All communication
between nodes in the cluster is directed through one specific TCP port. You will define it
during cluster setup (by default, it is TCP port 23570).
A Failover Master will send notifications in case the Primary Master is not connected to the
cluster. In order for mails to be delivered in this case, please make sure you configure the
Not ificat ion Delivery 2372 settings in a way they can be used to deliver emails from your
Failover Node as well (for example, using the option to set up a secondary Simple Mail
Transfer Protocol (SMTP) server).
Make your servers safe! From every cluster node, there is full access to all stored credentials
as well as other configuration data and the monitoring results of the cluster. Also, PRTG
software updates can be deployed through every node. So, please make sure you take
security precautions to avoid security attacks (hackers, Trojans, etc.) You should secure
every node server the same careful way as the master node server.
Run the nodes in your cluster either on 32-bit or 64-bit Windows versions only. Avoid using
both 32-bit and 64-bit versions in the same cluster, as this configuration is not supported
and may result in an unstable system. Also, ZIP compression for the cluster communication
will be disabled and you may encounter higher network traffic between your cluster nodes.
If you run cluster nodes on Windows systems with different timezone settings and use
Schedules 2353 to pause monitoring of defined sensors, schedules will apply at the local time
of each node. Because of this, the overall status of a particular sensor will be shown as
Paused every time the schedule matches a node's local system time. Please use the same
timezone setting on each Windows with a cluster node in order to avoid this behavior.
We recommend you to stay below 10,000 sensors per cluster for performance reasons.
The following sensor types cannot be used in cluster mode but only on a local or remote
probe:
IPFIX
741
and IPFIX (Custom)
jFlow V5
770
751
and jFlow V5 (Custom)
780
NetFlow V5
846
and NetFlow V5 (Custom)
856
NetFlow V9
865
and NetFlow V9 (Custom)
875
Packet Sniffer
sFlow
1094
907
and Packet Sniffer (Custom)
and sFlow (Custom)
SNMP Trap Receiver

Syslog Receiver
18.11.2014
916
1103
1621
1760
2603
Start Now!
Ready to get started? Please go to Failover Clust er St ep by St ep
2605
More
Knowledge Base: What are the bandwidth requirements for running a PRTG Cluster?
Knowledge Base: What is a Failover Master and how does it behave?
Knowledge Base: I need help with my PRTG cluster configuration. Where do I find step-by-step
instructions?
Knowledge Base: PRTG Cluster: How do I convert a (temporary) Failover Master node to be the
Primary Master node?
2604
18.11.2014

1 Failover Cluster Step by Step
12.9.1 Failover Cluster Step by Step

This section will guide you through a step-by-step process to set up a failover cluster. Please
follow these instructions carefully, in order to successfully integrate two or more PRTG
installations into one failover cluster.
Note: Before getting started, please make sure you consider the information in section
Failover Clust er Configurat ion 2602 .
Step 1: Install Core Servers

We will start with setting up a single failover cluster, consisting of two PRTG core server
installations, each running on an individual server. Please use your license key twice to install
the PRTG core server on two different computers.
If you already run an installation of PRTG, this will be your future Master Node. In this case,
please install a second core server on another computer only. Make sure you use the same
license key for both installations.
Before you begin to set up a cluster, please make sure you run exactly the same PRTG version
(build number) on all (future) nodes (install updates for existing installations, if necessary).
Note: Once the cluster is established, any updates you install on one node will be deployed to
all other cluster nodes automatically.
For details about the installation process, please see Inst all a PRTG Core Server
51
Step 2: Configure Master Node

Decide which of your PRTG core server installations will be your future Master Node. If you
already run an installation of PRTG in your network for some time, this should be your master,
so your existing monitoring configuration is being kept.
On the Master Node server, from the Windows start menu, open the PRTG Administ rat or
program. In the Cluster tab, click on the following button:
2542
Creat e a PRTG Clust er...

Start creating a cluster by clicking this button. The current PRTG core server will then be the
Mast er Node of your cluster.
After you click this button, please confirm converting this installation into a master node by
clicking on the Yes button.
20.11.2014
2605

Conv erting an Installation into a Cluster Master Node
A new dialog box will appear.
PRTG Administrator: Creating a Cluster Master
Save the Clust er Access Key so you have it at hand when configuring your Failover Node
(s).
Step 3: Configure Failover Node

On the server that will be your Failover Node, from the Start menu, open the PRTG
Administ rat or 2542 program. In the Cluster tab, click on the following button:
Join a PRTG Clust er...
2606
20.11.2014

Add this installation to an existing cluster which already has a Mast er Node, by clicking this
button. The current PRTG core server will then be a Failover Node in the cluster.
Note: This button is also available if you are currently running your PRTG installation in
Clust er Mode: Mast er Node. This option will then change your master node to a failover
node!
After you click this button, confirm converting this installation into a failover node by clicking
on the Yes button.
Conv erting an Installation into a Cluster Failov er Node
A dialog box will appear.
Enter the cluster's Mast er IP address/DNS name. It must be reachable from the machine
running the failover node.
Enter the other settings as defined in your Mast er Node's settings. Please make sure you
use the same settings on all nodes in your cluster.
20.11.2014
2607

Step 4: Confirm Failover Node

Now you need to confirm the new failover node by setting it to Act ive in the master node's
settings.
In a browser window, log into PRTGs web interface
102
of the Master Node server.
In the Sy st em Administ rat ionClust er 2394 settings, you will see your Master Node server in
the first line of the cluster list and your Failover Node server below.
Sy stem Setup Cluster Settings
For the Failover Node, set the radio button for Node St at e to Act ive and Save the changes.
The nodes will now connect and exchange configuration data. This may take a few minutes.
Step 5: Check Cluster Connection

In two browser windows, log into PRTGs web interfaces of both of your PRTG installations.
Open the cluster status page in both windows by clicking on the narrow cluster information
bars at the top of each window. You should see a cluster status with your two nodes in a
Connect ed state after a few minutes.
PRTG Cluster Status
2608
20.11.2014

PRTG Cluster Status
Step 6: Trouble Shooting

Having any problems? If your nodes cannot connect, please see
the Cluster Log entries on the PRTG St at usClust er St at us
2416
page of the web interface
the core server log file, a text file in the logs directory of your PRTG data folder (see Dat a
St orage 2611 ).
In the latest entries of these logs, you can see messages about any errors that might have
occurred. These will give you hints on where to find a solution.
If you encounter connection problems between the two cluster nodes, please make sure that
no software- or hardware firewall is blocking communication on the cluster port defined during
cluster setup. Communication between the nodes must be possible in both directions in order
for the cluster to work properly.
Step 7: Done! Move Sensors to the Cluster Probe Now

Thats it. Youve now successfully set up your failover cluster. All devices that are created or
moved under the Clust er Probe will be monitored by both servers.
In order t o monit or y our exist ing configurat ion via all clust er nodes, on y our mast er
node, please move y our groups, devices, and sensors from t he local probe t o t he
clust er probe! Objects, including their settings, will then be transferred to all cluster nodes
automatically.
Add More Failover Nodes

If you want to add an additional failover node to your cluster, you will need an additional
license key for two and three failover nodes, and two additional license keys to run four
failover nodes.
20.11.2014
2609

Note: In a cluster, only core servers running on the same size of license 19 can be combined.
For example, you can use several "PRTG Unlimited" licenses or several "PRTG 1000" licenses in
one cluster.
To add another failover node to your cluster, please set up a new PRTG core server installation
on a new server, using an additional license key. Then proceed with St ep 3 2606 and following.
Note: Use a second license key to set up both your second and third failover node, and use a
third license key to set up your fourth failover node. The "Corporate Country" license can be
used to install an unlimited number of core servers within one corporation in one country and
the "Corporate 5 Core Global" license can be used to install up to five core servers within one
corporation worldwide. The "Enterprise Unlimited Site" license (no longer available for
purchase) can be used to install an unlimited number of core servers within one corporation.
Each failover cluster is technically limited to five cluster nodes: As a maximum, you can run one
master node and four failover nodes in one cluster.
Note: We recommend you to stay below 10,000 sensors per cluster for performance
considerations.
More
Knowledge Base: My PRTG Cluster is messed up. How can I start over?
Advanced Topics
Act ive Direct ory Int egrat ion
2569
2571
2572
Define IP Ranges
Define Lookups
2578
2579
Regular Expressions
Add Remot e Probe
2587
2588
Failover Clust er Configurat ion

Dat a St orage
2602
2611

2610
2576
2613
2615
20.11.2014
Part 12: Advanced Topics | 10 Data Storage
12.10 Data Storage

PRTG stores the monitoring configuration, monitoring data, logs, tickets, and reports, as well as
support and debug data into different folders on the core server or the system running a
Remot e Probe 2588 . Additionally, there is data from PRTG in the program directory (for example,
scripts for your custom sensors 2217 ) and in the Windows registry.
You can find data in different locations. For a detailed information please see the article linked
in the More 2612 section below.
PRTG Program Directory

32 bit systems:
%programfiles%\PRTG Network Monitor
64 bit systems:
%programfiles(x86)%\PRTG Network Monitor
Note: These are the default paths. If you specified another installation directory, you will find
your data there.
PRTG Data Folder

On Windows Vista, Windows 7, Windows 2008, Windows 8, and Windows 2012:
%programdata%\Paessler\PRTG Network Monitor
On Windows XP and Windows Server 2003 (Note: Both operating systems are not officially
supported.):
%ALLUSERSPROFILE%\Application data\Paessler\PRTG Network Monitor
Note: These are the default paths, depending on your Windows version. If you specified a
custom path for data storage, please look it up in the PRTG Administ rat or 2541 : Open this
application and switch to the Core Server tab. You will find the path there.
Windows Registry
System settings on 32 bit systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor
18.11.2014
2611
Part 12: Advanced Topics | 10 Data Storage
System settings on 64 bit systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor
Enterprise Console settings:

HKEY_CURRENT_USER\Software\Paessler\PRTG Network Monitor\WinGUI
More
2612
18.11.2014
Part 12: Advanced Topics | 11 Using Your Own SSL Certificate with PRTG's Web Server
12.11 Using Your Own SSL Certificate with PRTG's Web Server
This section will give you a brief overview on how to use your own trusted SSL certificate files
with the PRTG web server.
What is SSL?
PRTG supports Secure Sockets Layer (SSL) to encrypt all data entered and shown in the Web
Int erface 100 , in the Ent erprise Console 2430 , or in the Smart phone Apps 2486 . That ensures that
no sensitive information can be intercepted when sending data between the PRTG core server
and your client software.
By default PRTG is already delivered with an SSL certificate so you can use secure connections
to your PRTG core server. However, these certificate files are not signed by a valid authority,
which is why browsers show an SSL Cert ificat e Warning 105 when you try to access the web
interface. Despite this warning your connection is still encrypted successfully.
To remove the browser warning you can obtain a certificate that is valid for your own domain
name and signed by a valid authority. The certificate must be provided in the correct format
and can then be copied to your PRTG program directory (see Dat a St orage 2611 ).
PRTG Needs PEM Encoded Format and Unencrypted Key

There are many different issuers for certificates, and there are different formats certificates can
be provided in.
PRTG needs three different files, named correctly, containing data in the expected encoding
and format:
prt g.crt : This is the certificate for your PRTG server. It has to be stored in PEM encoded
format.
prt g.key : This is the private key matching your server certificate. It has to be stored in PEM
encoded format and may not be encrypted! Please make sure that you provide this file in
decrypted format! The best way to check this is to open the file in a text editor. If you find a
line containing the word "ENCRYPTED", the file still needs to be decrypted before you can use
it with PRTG. Please decrypt using an SSL tool (e.g. OpenSSL) and your key password.
root .pem: This is the public root certificate of your certificate's issuer. It has to be stored in
PEM encoded format and must contain all necessary root certificates of your issuer in one
file. If there is more than one PEM encoded root certificate, please use a text editor to copy
all of them into a single file (the order does not matter).
Note: PEM encoded files must not contain Unix line breaks! Only Windows line breaks are
supported.
Once ready, copy these three files to the /cert sub folder of your PRTG program directory
(please backup existing files) and restart your PRTG core server service (see PRTG
Administ rat or 2552 ). Note: PRTG services won't restart if the files are not provided in exactly
the expected format!
18.11.2014
2613
Part 12: Advanced Topics | 11 Using Your Own SSL Certificate with PRTG's Web Server
For detailed instructions and examples, installation descriptions for various certificates
(including Wildcard certificates), as well as links to certificate tools and converters, please see
the More 2614 section below.
More
Knowledge Base: How can I establish a secure web interface connection to PRTG?
Knowledge Base: How can I use a trusted SSL certificate with the PRTG web interface?
2614
18.11.2014
Part 12: Advanced Topics | 12 Calculating Percentiles
12.12 Calculating Percentiles

Wikipedia describes a percentile as the value of a variable below which a certain percent of
observations fall. Providers often use it in their billing models, for example, when determining
the used bandwidth. With percentile calculation, you can cut off a certain percent of peak
values from an amount of values.
In PRTG, you can calculate percentiles when creating general reports (see Report s 2291 section),
or creating historic data reports of a certain sensor (see Hist oric Dat a Report s 133 section). If
you activate the Percent ile Result s option in your reports' settings, the according values are
added to the tables. You can customize the following settings:
Percent ile: Enter the percentile number you want to calculate. If you choose, for example,
to calculate the 95th percentile, enter "95" here and 5 % of peak values will be discarded.
Percent ile Average: This is the averaging interval in seconds, which is used for percentile
calculation. Default value is 300 which is equivalent to 5 minutes.
Percentile Mode
Choose between Discret e and Cont inuous mode. Continuous percentile interpolates
between discrete values, whereas discrete percentile chooses the next smaller discrete value.
Discret e percentile means that the value must be a member of the data set. For this kind of
calculation you require a discrete distribution. The median of a discrete distribution can not
be defined, as such, meaning that the 50th discrete percentile may not necessarily be the
median if the value does not belong to an odd number of measurements. Discrete
percentiles, as such, should not be used for billing applications.
Cont inuous percentile basically means that the measurements are treated as a statistical
population and the value is determined by interpolating a value when it isn't present. This
means that values are interpolated between actual measurements that are varying around
the "perfect" center of the measurements.
More
Knowledge Base: What are percentiles?
18.11.2014
2615
Part 13
Appendix
19.09.2014
2617
Part 13: Appendix |
13
Appendix
Please find further information in the following sections.

Glossary
2619
List of Abbreviat ions
2623
Support and Troubleshoot ing

Legal Not ices
2618
2626
2627
19.09.2014
Part 13: Appendix | 1 Glossary
13.1
Glossary
This section explains special words used in the context of PRTG Network Monitor. Note: Here,
only explanations are given. For information on where to find detailed instructions for a
specific key word, please see the Index section.
Channel
The monitoring data of a sensor 2622 is shown in sensor channels. For example, for sensors that
measure network traffic, there is one channel each for traffic in and traffic out. You can set
various triggers for each channel, enabling you to set sensor status changes or notifications
based on the monitoring data received.
Cluster
PRTG can be configured as a failover cluster for fail-safe monitoring. In a cluster, one or more
core servers 2619 work together in one configuration. Every node can monitor all devices in a
network for gapless monitoring, additionally enabling you to compare monitoring results
measured from different perspectives.
Cluster Node
Sometimes used as synonym for Node
2621
Cluster Probe
When running PRTG in cluster mode, a cluster probe is automatically created. All objects 2621
created on the cluster probe, or below it in the device tree 2620 , are monitored by all nodes in
the cluster. Create or move objects 2621 there to monitor them fail-safely. If one node fails, the
other nodes will continue to monitor them. You can add groups 2620 and devices 2620 to the
probe. On a PRTG installation, the cluster probe runs as part of this installation's local probe 2620 .
Remote probes 2621 cannot be connected to a cluster probe, but only to one local probe of
one PRTG installation.
Core Server
The central unit of PRTG. It receives monitoring data from the probe(s) 2621 and handles
reporting and notifications, provides the web server for the user interfaces, and many other
things. In a cluster 2619 , one core server is installed on every node.
Dashboard
In the Home menu of the web interface there are several pre-configured dashboards available
which show a quick overview of the overall status of your monitoring configuration. Custom
dashboards can be created using the Maps 2621 function.
19.09.2014
2619
Device
A device in PRTG represents a physical device in the network. For an easily understandable
tree structure, you usually create one PRTG device for each physical device you want to
monitor (exceptions apply to some sensors that can only be created on the local probe 2620
device, and for sensor types that are not bound to a certain device, such as HTTP sensors,
which are also usually created on the local probe). You can add one or more sensors 2622 on
every device.
Device Tree
PRTG's configuration is represented in a hierarchical tree structure, called device tree,
containing all objects 2621 . While building the tree, you can relate to your network's topology to
make your monitoring setup easy to understand.
Failover Master (Node)

If the primary master 2621 node fails, a failover node 2620 is promoted to current failover master
and takes over the master role until the primary master node re-joins the cluster 2619 .
Failover Node
In a cluster 2619 a failover node monitors all sensors 2622 on the cluster probe 2619 , providing
monitoring data for the core server 2619 . Additionally, it serves as a backup in case the master
node 2621 fails.
Group
A group is an organizational unit in your PRTG tree structure that helps to arrange your
devices. To existing groups, you can add devices, or additional sub-groups. This way you can
model your physical network's topology within the PRTG configuration.
Library
Libraries are a way to show parts of your device tree 2620 in a different layout or with different
filters enabled. There is an editor available that allows creating libraries directly in your
browser.
Local Probe
The local probe is installed together with the core server 2619 . All objects 2621 created on the
local probe, or below it in the device tree 2620 , are monitored by the local core system. You can
add groups 2620 and devices 2620 to the probe.
2620
19.09.2014
Map
Maps (sometimes referred to as "dashboard 2619 ") are a way to present monitoring the way you
want to arrange it. There is an editor available that allows creating maps directly in your
browser.
Master Node
In a cluster 2619 , the master node controls the settings and cluster management. It also takes
over notifications. All changes to the monitoring configuration are made on the master node.
Node
In a cluster 2619 there is one master node 2621 and one or more failover nodes 2620 . On each node,
one PRTG core server 2619 installation is running independently. All nodes are connected to
each other, exchanging configuration and monitoring data.
Object
All different items in the device tree 2620 are generally referred to as objects. An object can be
a probe 2621 , a group 2620 , a device 2620 , or a sensor 2622 .
Primary Master (Node)

The primary master node in a cluster 2619 is the node 2621 that is master by configuration. Only if it
fails, one of the failover nodes 2620 becomes failover master 2620 and takes over the master role
until the primary master node re-joins the cluster.
Probe
On a probe, the actual monitoring takes place. A probe can run as local probe 2620 on the local
system where the core server 2619 is installed. There are also cluster probes 2619 and remote
probes 2621 .
Remote Probe
A remote probe is a small piece of software installed on a computer in the local or remote
network. It scans the network from there and sends monitoring results to the core server 2619 .
Once the connection is established, the remote probe is shown in the PRTG tree structure. All
objects 2621 created on the remote probe, or below it in the device tree 2620 , are monitored by
the remote system running the remote probe. You can add groups 2620 and devices 2620 to the
probe. In cluster 2619 , remote probes can only be connected to the master node 2621 , not to one
of the failover nodes 2620 .
19.09.2014
2621
Sensor
A sensor monitors one aspect of a device 2620 . For example, monitoring if a device responds to
a Ping request is done by one sensor. Monitoring the traffic of one ethernet port of a router
device is done by another sensor. For monitoring the CPU load of the local system yet another
sensor is set up, and so on. A sensor's data is shown in channels 2619 .
Sensor Tree
Sometimes used as synonym for device tree
2620
Tickets
Ticket s 148 are created by the system or a PRTG user and contain important messages or
action steps to take for the administrator or another specific user. Every ticket should be
viewed to take appropriate actions. You can access the list of tickets from the main menu.
xFlow
Paessler designates all kinds of flow protocols as xFlow. Currently, PRTG supports NetFlow V5
and V9, sFlow V5, and jFlow V5.
2622
19.09.2014
Part 13: Appendix | 2 List of Abbreviations
13.2
List of Abbreviations
In the following, please find a list of the most common abbreviations used in this
documentation.
ADO: ActiveX Data Objects (ADO)
ADSL: Asymmetric Digital Subscriber Line (ADSL)
AJAX: Asynchronous Java Script and XML (AJAX)
API: Application Programming Interface (API)
CoS: Class of Service (CoS)
CSV: Comma Seperated Values (CSV)
DHCP: Dynamic Host Configuration Protocol (DHCP)
DMZ: Demilitarized Zone (DMZ)
DSCP: Differentiated Services Code Point (DSCP)
DNS: Domain Name Service (DNS)
GUI: Graphical User Interface (GUI)
GUID: Globally Unique Identifier (GUID)
HTTP: Hypertext Transfer Protocol (HTTP)
ICMP: Internet Control Message Protocol (ICMP)
IMAP: Internet Message Access Protocol (IMAP)
IPsec: Internet Protocol Security (IPsec)
JSON: JavaScript Object Notation (JSON)
LAN: Local Area Network (LAN)
LDAP: Lightweight Directory Access Protocol (LDAP)
MoID: Managed Object ID (MoID)
MIB: Management Information Base (MIB)
19.09.2014
2623
MOS: Mean Opinion Score (MOS)

NAT: Network Address Translation (NAT)
NTLM: NT LAN Manager (NTLM)
PDF: Portable Document Format (PDF)
PDV: Packet Delay Variation (PDV)
POP3: Post Office Protocol version 3 (POP3)
QoS: Quality of Service (QoS)
RADIUS: Remote Authentication Dial-In User Service (RADIUS)
REST: Representational State Transfer (REST)
RMON: Remote Monitoring (RMON)
RPC: Remote Procedure Call (RPC)
SASL: Simple Authentication and Security Layer (SASL)
SLA: Service Level Agreement (SLA)
S.M.A.R.T.: Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.)
SMB: Server Message Block (SMB)
SMTP: Simple Mail Transfer Protocol (SMTP)
SNMP: Simple Network Management Protocol (SNMP)
SNTP: Simple Network Time Protocol (SNTP)
SOAP: Simple Object Access Protocol (SOAP)
SPAN: Switched Port Analyzer (SPAN)
SQL: Structured Query Language (SQL)
SSH: Secure Shell (SSH)
SSL: Secure Sockets Layer (SSL)
TFTP: Trivial File Transfer Protocol (TFTP)
2624
19.09.2014
UNC: Uniform Naming Convention (UNC)

UPnP: Universal Plug and Play (UPnP)
UUID: Universally Unique Identifier (UUID)
VoIP: Voice over IP (VoIP)
VPN: Virtual Private Network (VPN)
WAN: Wide Area Network (WAN)
WBEM: Web-Based Enterprise Management (WBEM)
WMI: Windows Management Instrumentation (WMI)
WQL: Windows Management Instrumentation Query Language (WQL)
WSUS: Windows Server Update Services (WSUS)
XML: Extensible Markup Language (XML)
19.09.2014
2625
Part 13: Appendix | 3 Support and Troubleshooting
13.3
Support and Troubleshooting
Need help with PRTG? There are several ways to get support and trouble shooting.
Video Tutorials
A video says more than a thousand wordswatch tutorials for PRTG from Paessler and other
PRTG users.
Paessler Knowledge Base

In the Knowledge Base you can search in hundreds of articles about PRTG. You can post your
own questions and answers, too!
http://www.paessler.com/knowledgebase/
Open a Support Ticket

Users that have purchased a license can open support tickets which will usually be answered
by Paessler's staff in less than 24 hours on business days.
http://www.paessler.com/support/openticket
2626
19.09.2014
Part 13: Appendix | 4 Legal Notices
13.4
Legal Notices
Build using Indy Internet Direct (http://www.indyproject.org/). This product includes

cryptographic software written by Eric Young (eay@cryptsoft.com). Uses the net-SNMP library,
see "netsnmp-license.txt". Uses the DelphiZip library distributed under the GNU LESSER
GENERAL PUBLIC LICENSE (http://www.delphizip.net/). Uses FastMM (http://sourceforge.net/
projects/fastmm/), TPLockBox (http://sourceforge.net/projects/tplockbox) and Delphi
Chromium Embedded (http://code.google.com/p/delphichromiumembedded/) under the
Mozilla Public License 1.1 (MPL 1.1, available from http://www.mozilla.org/MPL/MPL-1.1.html).
Soundfiles from http://www.soundsnap.com. Uses Public Domain regional maps from the "CIA
World Factbook" webpage of the CIA (https://www.cia.gov/library/publications/the-worldfactbook/docs/refmaps.html). Uses the "wkhtmltopdf" (http://code.google.com/p/
wkhtmltopdf/) library distributed under the GNU LESSER GENERAL PUBLIC LICENSE (see
wkhtmltopdf_lgpl-3.0.txt). Icons from http://www.androidicons.com. Uses the IPMIUTIL library
under the BDU 2.0 license, see "ipmi_bsd-2.0.txt". Uses PhantomJS, see "phantomjslicense.bsd".. Uses the Npgsql - .Net Data Provider for Postgresql library (for license information
see ipmi_bsd-2.0.txt).
All trademarks and names mentioned herein belong to their respective owners.
Last manual export: Freitag, 21. November 2014 11:10:00
19.09.2014
2627
Last change to this manual (YYYY-MM-DD): 21.11.2014
2628
30.12.1899

PRTG Manual

Încărcat de

Informații document

Descriere 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

PRTG 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

Exchange Mail Queue (Powershell) Sensor

PerfCounter IIS Application Pool Sensor

SNMP IBM System X Logical Disk Sensor

WSUS Statistics Sensor

Part 7 Ajax Web InterfaceAdvanced Procedures

Part 8 Enterprise Console

Part 9 Other User Interfaces

Part 10 Sensor Technologies

Monitoring via SNMP

Part 11 PRTG Administrator Tool

Part 12 Advanced Topics

Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors

Part 1: Welcome to PRTG Network Monitor |

Welcome to PRTG Network Monitor

Why Network Monitoring is Important

Monitoring Networks with PRTG Network Monitor

Part 1: Welcome to PRTG Network Monitor | 1 About this Document

About this Document

section. For more

Part 1: Welcome to PRTG Network Monitor | 2 Key Features

What PRTG Can Be Used For

What PRTG Includes

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

Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses

There are four different PRTG flavors available.

Part 1: Welcome to PRTG Network Monitor | 4 Available Licenses

Can monitor maximum number of sensors (from 100 to unlimited).

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

VMware Monit oring

Knowledge Base: Planning Large Installations of PRTG Network Monitor

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Detailed Sy stem Requirements

Running PRTG on Virt ual Machines

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

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Part 1: Welcome to PRTG Network Monitor | 5 System Requirements

Large Inst allat ion

Large Inst allat ion B Net book

DELL Inspiron Mini

Intel Core2 QuadCore

Intel Xeon QuadCore

Intel Atom Z520

Windows 2003 64Bit

Scanning Int erval

Average CPU Load

Average CPU Load

Average Memory Used